Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!caen!news.cs.indiana.edu!noose.ecn.purdue.edu!en.ecn.purdue.edu!stevew From: stevew@en.ecn.purdue.edu (Steven L Wootton) Newsgroups: comp.binaries.ibm.pc.d Subject: Re: 4dos misfeature? Message-ID: <1991Mar8.160701.6463@en.ecn.purdue.edu> Date: 8 Mar 91 16:07:01 GMT References: <1991Mar6.192824.9889@en.ecn.purdue.edu> Organization: Purdue University Engineering Computer Network Lines: 36 In an attempt to end the speculation about my particular machine, here are the relevant details: config.sys ---------- buffers=40 files=20 device=c:\sysfiles\ramdrive.sys /e1024 device=c:\sysfiles\himem.sys device=c:\sysfiles\keystack.sys device=c:\sysfiles\nnansi.sys device=c:\f-prot\f-driver.sys shell=c:\4DOS.COM /P /S:X autoexec.bat ------------ f-prot\f-lock f-prot\f-popup f-prot\f-oschk 8506 13069 45533 59622 60262 set path=c:\dos;c:\bin;c:\4dos set prompt=$p$g vgazap This is a 286/12, 4M ram, 32M RLL disk, vga. MS-DOS 3.30, 4dos 3.02a. That is it. I ran CHKDSK, and it did not report any errors. I have no disk cache, and I don't use fastopen. The error seems to have been an entirely random act, caused by a wayward cosmic particle which just happened to strike my disk controller at just the precise moment to cause such havoc. Steve Wootton stevew@ecn.purdue.edu stevew@pur-ee.uucp stevew%ecn.purdue.edu@purccvm.bitnet