Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!soleil!synapse!jvnc.net!princeton!att!linac!pacific.mps.ohio-state.edu!zaphod.mps.ohio-state.edu!samsung!olivea!uunet!stanford.edu!morrow.stanford.edu!news
From: GD.SAR@forsythe.stanford.edu (Sandy Rockowitz)
Newsgroups: comp.os.msdos.misc
Subject: Re: Somebody...Anybody...HELP!!!
Message-ID: <1991Jun28.230626.3676@morrow.stanford.edu>
Date: 28 Jun 91 23:06:26 GMT
Sender: news@morrow.stanford.edu (News Service)
Distribution: usa
Organization: Data Center, Stanford University, California, USA
Lines: 23

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.

Sandy Rockowitz
gd.sar@forsythe.stanford.edu