🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: comp.windows.ms
Article #12323

Re: Strange memory errors in Windows?

#12323
From: Raul Baragiola
Date: Wed, 29 May 1991 13:09
46 lines
2697 bytes
In article <1991May29.065802.22317@trl.oz.au> stevens@shiva.trl.OZ.AU (Tony Stevens) writes:
>mjf@cunixb.cc.columbia.edu (Michael J Flory) writes:
>
>I have had similar experiences with Windows copying what appeared to be
>junk to a floppy drive - 1.2Mbyte, 360kbyte, 5 1/4 or 1.4Mbyte 3 1/2.
>
>>Some time ago I posted with a strange and dangerous error I got running
>>DISKCOPY in a DOS window with a .pif asking for all 640 K if it could get
>>it.  In short, the diskcopy operation miscopied a couple of sectors every
>>dozen-and-a-half or so (the number varied).  But although VERIFY was on,
>>I got no error message -- I discovered it through DISKCOMP.
>
>In my case the errors in a dos window occur when I run a batch file
>containing a XCOPY or COPY statement, and produce FF hexidecimal for
>every forth byte of the file. 
>
>>Now, running XTREE GOLD 2.0 under windows, I have discovered that the 
>>beginning parts of whole sets of files copied to a floppy are sometimes
>
>     some deleted
>
>The problem was first noticed using XTREE GOLD 1.3 (I think this is the
>version).  
>
>One of my solutions was to set the following in the SYSTEM.INI file in
>the [386Enh] section:
>
>   EMMExclude=A000-DFFF    required because of Paradise VGA Driver 256
>                           colors.
>   VirtualHLRD=off         suggested somewhere ?? if you have drive
>                           problems.
>
>These fixed my problems both with XTGOLD and dos window in most cases.
>
>The problem still occurs sometimes if I try doing an add or update
>operation to ZIP file on the floppy drive or if the file being copied is
>very large 800kbytes.
>

I have the same problems writing to floppies.  I feel that it is more
likely to occur with large files just because more bytes are written.
I will also like to know why this happens and how to fix it.   
--
Raul A. Baragiola                               \Internet: raul@virginia.edu
Dept. Nuclear Engnr. and Engnr. Physics          \Phone: (804)-982-2907
University of Virginia, Charlottesville, VA 22901 \ Fax: (804)-924-6270
Technical Details
Message-ID: <1991May29.130902.17809@murdoch.acc.Virginia.EDU>
Path: arc1-ca.pugleaf.net!utzoo!utgpu!news-server.csri.toronto.edu!rpi!think.com!zaphod.mps.ohio-state.edu!wuarchive!udel!haven.umd.edu!uvaarpa!murdoch!kelvin.seas.Virginia.EDU!rb9a
References: <1991May29.005554.10290@cunixf.cc.columbia.edu> <1991May29.065802.22317@trl.oz.au>

Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!utgpu!news-server.csri.toronto.edu!rpi!think.com!zaphod.mps.ohio-state.edu!wuarchive!udel!haven.umd.edu!uvaarpa!murdoch!kelvin.seas.Virginia.EDU!rb9a
From: rb9a@kelvin.seas.Virginia.EDU (Raul  Baragiola)
Newsgroups: comp.windows.ms
Subject: Re: Strange memory errors in Windows?
Message-ID: <1991May29.130902.17809@murdoch.acc.Virginia.EDU>
Date: 29 May 91 13:09:02 GMT
References: <1991May29.005554.10290@cunixf.cc.columbia.edu> <1991May29.065802.22317@trl.oz.au>
Sender: usenet@murdoch.acc.Virginia.EDU
Organization: University of Virginia
Lines: 46