Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!samsung!know!zaphod.mps.ohio-state.edu!brutus.cs.uiuc.edu!ux1.cso.uiuc.edu!ux1.cso.uiuc.edu!uxa.cso.uiuc.edu!mms00786
From: mms00786@uxa.cso.uiuc.edu
Newsgroups: comp.windows.ms
Subject: Re: EMM386.SYS and conflict with SCSI d
Message-ID: <118500047@uxa.cso.uiuc.edu>
Date: 22 Jul 90 04:34:00 GMT
References: <151252@<1990Jul21>
Lines: 24
Nf-ID: #R:<1990Jul21:151252:uxa.cso.uiuc.edu:118500047:000:1099
Nf-From: uxa.cso.uiuc.edu!mms00786    Jul 21 23:34:00 1990


On a similar note - I just upgraded my 65 Meg RLL drive to 105 Meg IDE
running with ontrack's DiskManager. Only way I can run windows now is
to set VirtualHDIRQ=FALSE in the 386enh section of system.ini. I am
fairly sure this will solve the problem with the SCSI. However, I would
like to know :
   a) is *my* problem caused by the size of the drive or DiskManager?
   b) I have read about problems between DiskManager and Win3 - are
      these severe? Is *anyone* using DiskManager and windows in enh
      mode? Or is this problem related to the direction of the local
      cosmic ray source?

On an unrelated note, I have a Paradise + 16 that came with my Tristar
computer purchased last year. My friend just bought an OEM version of
Paradise 1024. We are both hooked to a NEC 3D. However, on his card, we
both feel that the letters are fuzzier, and the colors less vibrant.
Could it actually be possible that cards using basically the same chips
could generate different output? We can't see any adjustable analog
components on either card. Or are we just imagining things?

Thanks!

Milan
.