Path: utzoo!utgpu!news-server.csri.toronto.edu!clyde.concordia.ca!uunet!samsung!uakari.primate.wisc.edu!sdd.hp.com!elroy.jpl.nasa.gov!ames!eos!shelby!neon!minakami
From: minakami@Neon.Stanford.EDU (Michael K. Minakami)
Newsgroups: comp.windows.ms
Subject: SCSI drivers & 386 Enhanced mode
Message-ID: <1990Jun11.062719.22834@Neon.Stanford.EDU>
Date: 11 Jun 90 06:27:19 GMT
Sender: minakami@Neon.Stanford.EDU (Michael K. Minakami)
Organization: Computer Science Department, Stanford University
Lines: 25


A while ago I posted a message asking if anyone got Windows to work with
a SCSI drive. Here's more specifics: Windows 3 *will* acknowledge the
drive if it's run in real or standard mode. When it starts up in 386
Enhanced mode, any access to it results in a 'Cannot read from drive
x' message. I suspect this may have to do with the problems reported here
by others who can't get Windows to work with non-standard partitions...
the virtual drives off of my SCSI are not stand ard DOS partitions
either. 

Does anyone have a fix for this? Why does this happen only in 386
enhanced mode and not in standard or real? Is there a way to force
Windows to use installed drivers? I remember someone posting an 
undocumented command line switch for Windows 2.1 forcing it to use
"standard" disk access (whatever that is). Maybe this exists for
3.0 too?

Thanx in advance...
Michael


-- 
-----------------------------------------------------------------------
The child can explain the man better than  | Michael K. Minakami     
      the man can explain the child.       | minakami@neon.stanford.edu