Path: utzoo!attcan!uunet!mailrus!cornell!rochester!udel!sbcs!sbstaff2!altman
From: altman@sbstaff2.cs.sunysb.edu (Jeff Altman)
Newsgroups: comp.windows.ms
Subject: Re: EMM386.SYS and conflict with SCSI d
Message-ID: <1990Jul22.145539.284@sbcs.sunysb.edu>
Date: 22 Jul 90 14:55:39 GMT
References: <151252@<1990Jul21> <118500047@uxa.cso.uiuc.edu>
Sender: usenet@sbcs.sunysb.edu (Usenet poster)
Organization: State University of New York at Stony Brook
Lines: 26

The SCSI drive I installed runs perfectly fine with Win3.  So fine
in fact that I even keep my permanent swap file on the drive.
The conflict is between the Expanded Memory Management utility
EMM386.SYS and the SCSI, independent of Windows.  Even without
starting Windows, any access to the SCSI drive while EMM386.SYS 
is installed will crash the system.  

If I try to get around the EMM386.SYS problem by using my hardware
to create Expanded Memory, then Win3 won't run in Enhanced Mode.
Windows requires a recognized Expanded Memory Manager (EMM386.SYS)
in order to run in Enhanced Mode with externally created Expanded 
Memory.

(Remember, the original problem was that Paradox Personal Programmer
does not accept the Windows generated Expanded Memeory.)

As far as the conflicts with Disk Manager goes, the problem is that
the ddvice driver provided by DM in order to use extended partitions
bypasses the BIOS calls (which Win3 uses directly) and therefore 
causes problems for the drive.  Setting VirtualHDIRQ=FALSE in the 
386enh section of system.ini tells Win3 not to write directly to the
BIOS routines and use DOS instead allowing the DM driver to work.
This of course reduces performance dramaticly.  The solution is to
use DOS 4.01 and generate your large partitions with FDISK.

- Jeff (jaltman@ccmail.sunysb.edu)