mms00786@uxa.cso.uiuc.edu (07/22/90)
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
.altman@sbstaff2.cs.sunysb.edu (Jeff Altman) (07/22/90)
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)