Path: utzoo!attcan!uunet!samsung!usc!snorkelwacker!apple!mips!sjsca4!poffen
From: poffen@sj.ate.slb.com (Russ Poffenberger)
Newsgroups: comp.windows.ms
Subject: Re: SCSI drivers & 386 Enhanced mode
Message-ID: <1990Jun12.214008.1132@sj.ate.slb.com>
Date: 12 Jun 90 21:40:08 GMT
References: <1990Jun11.062719.22834@Neon.Stanford.EDU>
Reply-To: poffen@sj.ate.slb.com (Russ Poffenberger)
Organization: Schlumberger Technologies, San Jose, CA.
Lines: 29

In article <1990Jun11.062719.22834@Neon.Stanford.EDU> minakami@Neon.Stanford.EDU (Michael K. Minakami) writes:
>
>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?
>

Windows 3.0 works fine with my Adaptec 1542B SCSI controller. This controller
needs no drivers, the system recognizes it as a standard MFM or RLL drive. In
fact, it will even work with another MFM or RLL controller in the system at
the same time.


Russ Poffenberger               DOMAIN: poffen@sj.ate.slb.com
Schlumberger Technologies       UUCP:   {uunet,decwrl,amdahl}!sjsca4!poffen
1601 Technology Drive		CIS:	72401,276
San Jose, Ca. 95110             (408)437-5254