Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!usc!zaphod.mps.ohio-state.edu!wuarchive!dogie.macc.wisc.edu!vms.macc.wisc.edu
From: anderson@vms.macc.wisc.edu (Jess Anderson)
Newsgroups: comp.sys.ibm.pc
Subject: Re: Windows/386 vs SCSI controller
Message-ID: <3479@dogie.macc.wisc.edu>
Date: 14 Apr 90 02:57:58 GMT
Sender: news@dogie.macc.wisc.edu
Distribution: usa
Organization: University of Wisconsin Academic Computing Center
Lines: 26

In article <641@cohesive.UUCP>, ballard@cohesive.UUCP (John Ballard) writes...

]I am having a problem getting Windows/386 to run on my system. I have 
]an Everex Step 386/33 with 4Meg of memory and 128K of cache. I have
]a Logix VGA card and an adaptec 1542A SCSI/floppy disk controller.
]The tech support people at microsoft are currently guessing that there
]is an interaction between windows/386 and my SCSI controller, they say
]that windows/386 is very hardware sensitive. They seem to think that
]anything other than a standard AT compatible MFM/RLL controller is very
]unusual. Any help or suggestions would be appreciated.

I have a WD7000FASST SCSI controller in a Club Hawk 1 
(386/33MHz, 128K cache, 8MB memory), and I had problems
with Windows/386.  My calls to Microsoft yielded results
similar to yours.  My controller comes with software from
Columbia Data Products, and one of the drivers has options
for use with Windows.  I tried all possible combinations.
Some didn't work at all, some worked kind of, none worked
reliably.  I went back to Windows/286, which at least ran
in a reasonably stable way.  Windows 3 better fix all this
or I will be truly annoyed.

==Jess Anderson===Academic Computing Center=====Univ. Wisconsin-Madison=====
| Work: Rm. 2160, 1210 West Dayton St., Madison WI 53706, Ph. 608/263-6988 |
| Home: 2838 Stevens St., 53705, 608/238-4833   Bitnet: anderson@wiscmacc  |
==Internet: anderson@macc.wisc.edu====UUCP:{}!uwvax!macc.wisc.edu!anderson==