Path: utzoo!utgpu!watserv1!watmath!att!pacbell!pacbell.com!ucsd!usc!wuarchive!zaphod.mps.ohio-state.edu!think.com!linus!linus!mwunix.mitre.org!jcmorris
From: jcmorris@mwunix.mitre.org (Joe Morris)
Newsgroups: comp.windows.ms
Subject: Re: Windows 3.0 kick's out on my system...
Keywords: Windows
Message-ID: <118481@linus.mitre.org>
Date: 29 Aug 90 13:03:26 GMT
References: <*6-%Y?#@rpi.edu>
Sender: usenet@linus.mitre.org
Reply-To: jcmorris@mwunix.mitre.org (Joe Morris)
Organization: The Mitre Corporation
Lines: 31

In a recent article dorsai@pawl.rpi.edu (G. Donald Moncreaff) writes:
 
>	i just recently upgraded by disk subsystem from a 40M st251-1
>with a 2f/2hd Adaptek controller to an 80M st296n and a WD 7000-Fasst2
>controller.  my problem is that windows will not load properly with the
>new disk sub-system.  windows seems to install correctly but won't run
>again after you exit installation.  attempts to run produce a flurry of
>disk activity followed by the windows logo followed by more disk activity
>a video change mode, a little more disk then a return to dos prompt.

There's a note in the README file for WIN3 which calls for you to
change the [386enh] section of SYSTEM.INI if you have a SCSI hard
disk which uses DMA.  The change is to add the line:

   VirtualHDIRQ=FALSE

anywhere in the section.  Also, it requires that you use SmartDrive 
WITHOUT specifying the /B- option.  See line 773ff of README.TXT.

Of course, this may be a necessary but not sufficient solution.  I was
repeatedly told to make this change while I was pounding on Microsoft
to find a way to make the CD-ROM they marketed work under WIN3.  It
turned out that the problem was that their vendor (Denon America) had
changed the driver and shipped new copies to internal Microsoft sites
but hadn't ever bothered to inform users in the field...and when they
did the documentation was wrong.  The symptoms I saw suggest that
the change to SYSTEM.INI could be what you need, especially since the
problem occurs only in 386 enhanced mode, but you might also check
with WD to see if they have a new driver for WIN3 users.

Joe Morris