Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!samsung!uunet!sequent!ogicse!milton!serval!proton.tricity.wsu.edu!msmith From: msmith@proton.tricity.wsu.edu (Mark Smith) Newsgroups: comp.os.msdos.misc Subject: Re: Somebody...Anybody...HELP!!! Message-ID: <1991Jun29.222605.1447@serval.net.wsu.edu> Date: 29 Jun 91 22:26:05 GMT References: <1991Jun28.230626.3676@morrow.stanford.edu> Sender: news@serval.net.wsu.edu (USENET News System) Distribution: usa Organization: Washington State University Lines: 41 In article <1991Jun28.230626.3676@morrow.stanford.edu> GD.SAR@forsythe.stanford.edu (Sandy Rockowitz) writes: >In article <1991Jun27.203539.6354@sj.ate.slb.com>, >poffen@sj.ate.slb.com (Russ Poffenberger) writes: >>I had similar problems when using my SCSI controller (Adaptec AHA1542B), qemm, >>loading smartdrv high, then running windows. This messed up the disk something >>awful. >> >>The solution is to not load smartdrv high. Also the latest driver from >>Adaptec is supposed to work correctly. I am still waiting for the update. >> > >Russ, > >I too had a similar problem trying to load SMARTDRV high with 386MAX >5.1 and Windows 3.0/DOS 4.01. The drive containing my Windows files >were trashed, and I had to restore from tape. > >For what it's worth, this was with a Conner IDE drive, to I don't >think that the fact that you have a SCSI drive is a factor. > >I've not had the nerve to try again with DOS 5.0. > I've just installed 5.0 a couple of nights ago and fired up win 3.0 in enhanced mode. No problems. System: Generic 386-25 (AMI BIOS dated mid '90) 4 Meg RAM 80 meg Maxtor IDE. SVGA (512K) Software: Win 3.0 DO$ 5.0 QEMM386 OOPS, forgot to mention. The DO$ 5.0 manual specificly states that you MUST use the smartdrv.sys that comes with 5.0 and NOT the one with windows. Also, If you use the EMM386.sys and HIMEM.sys that came with windows, you'd also need to change your config.sys to use the DO$ 5.0 ones also. This is according to the Bible according to Microsoft. V. 5.0 that is.