Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!wuarchive!swbatl!texbell!moxie!texsun!sundc!newstop!male!mutchler From: mutchler@zule.EBay.Sun.COM (Dan Mutchler) Newsgroups: comp.windows.ms Subject: Re: Windows + SCSI + SuperPcKwik Cache + QEMM + SDK = HUGE MESS!!! Message-ID: Date: 30 Oct 90 17:22:47 GMT References: <1990Oct29.075111.7414@agate.berkeley.edu> Sender: news@male.EBay.Sun.COM Distribution: usa Lines: 34 In-reply-to: c60c-3fz@e260-3f.berkeley.edu's message of 29 Oct 90 07:51:11 GMT In article <1990Oct29.075111.7414@agate.berkeley.edu> c60c-3fz@e260-3f.berkeley.edu (In Sik Rhee) writes: Ok, just 2 short days ago, I was very content with my system, which was running MFM 80mb... I had a delicate balance to my system (4MB memory)... QEMM 5.1, SuperPcKwik 3.57, SDK, and Windows all coexisted in a delicate balance, even leaving me with 550K+ DOS, letting me do wonderful things like run nmake within windows... The next morning, I got my new Priam 738 (330MB) SCSI drive along with the Adaptec 1542a controller... then my life turned into hell. When I first installed windows, everything was dandy... himem and smartdrv worked, etc etc... then I loaded up the QEMM and the SuperPckwik... then it happened... windows would not run in 386 enhanced mode... it'd boot up, give me the blue windows 3.0 screen, and blank out.. just before the silly icon appeared, I got dumped to dos... I had this problem with my SCSI, regardless of the disk caching that I use. The PROM manufacturer gave me the following work around. In system.ini under the [386enh] section add the following lines: VirtualHDIRQ=False EMMExclude=A000-EFFF This seemed to fix the problem that I was experiencing. -- Dan Mutchler | ARPA/Internet: mutchler@zule.EBay.Sun.COM Sun Federal System Engineer | UUCP: ...!sun!mutchler -------------------------------------------------------------------------- There is no such thing as sanity. And that is the sanest fact. --Mark Knopfler