Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!ucsd!ucbvax!agate!web-1e!c60c-3fz
From: c60c-3fz@web-1e.berkeley.edu (In Sik Rhee)
Newsgroups: comp.windows.ms
Subject: Re: Windows + SCSI + SuperPcKwik Cache + QEMM + SDK = HUGE MESS!!!
Message-ID: <1990Oct30.200102.5773@agate.berkeley.edu>
Date: 30 Oct 90 20:01:02 GMT
References: <1990Oct29.075111.7414@agate.berkeley.edu> <1990Oct29.101457@star.enet.dec.com> <5542@hsv3.UUCP>
Sender: usenet@agate.berkeley.edu (USENET Administrator)
Distribution: usa
Organization: University of California, Berkeley
Lines: 24


Ok, now I've centralized the problems...

1> Super Pc-Kwik does not like my HD AT ALL ... I'm pretty sure it actually
	slowed down some of the processes...

2> I have to configure QEMM more correctly...  (something about a db=4 
	setting in my CONFIG.SYS)

3> Yes I do have a permanent, and no, Norton does not flake with my windows

4> the central cause of the problem is the SCSI host adapter, because
	it's got its own BIOS...

my hypothesis is that QEMM wont work because it tries to loadhi stuff
	into memory in places where it will cause a conflict with the 
	SCSI BIOS...  SuperPcKwik, now, that's something I'm not sure of...


Right now, I'm running windows with QEMM 5.11, without loading anything into
himem (yet), with Smartdrv...  things are back to normal (I can even compile
my windows stuff...)   tonight I'm going to try to get QEMM to load stuff
into himem... if that's a success, then my only problem is finding the
right cache program (is Hyperdisk (hypercache?) 4.0 any good?)