Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!samsung!balrog!ctron.com
From: dj@ctron.com (DJ Delorie)
Newsgroups: comp.binaries.ibm.pc.d
Subject: Re: What disk caches work with djgcc?
Message-ID: <1502@balrog.ctron.com>
Date: 16 May 91 12:28:48 GMT
References: <1991May15.150542.24705@syd.dit.CSIRO.AU>
Sender: news@balrog.ctron.com
Reply-To: dj@ctron.com
Organization: None whatsoever
Lines: 24
Nntp-Posting-Host: bragi

In article <1991May15.150542.24705@syd.dit.CSIRO.AU>, evans@syd.dit.CSIRO.AU (Bruce.Evans) writes:
> djgcc uses the "vdisk method" for cooperative access to extended
> memory. I have not found a disk cache that uses this method (I
> only tried smartdrv and hyperdisk). djgcc is very slow without
> extended memory (it swaps all the time) and fairly slow without
> a cache in 7MB extended memory (it accesses the disk a lot).

> What disk caches use the vdisk method?


I don't "use" the VDISK method - I "allow" it.  If VDISK is
installed, I'll avoid using that memory.  I also check int 15h
and XMS to see where else memory might be used.  After all this,
whatever is left is MINE.  If XMS is installed, I'll register with
it that I'm taking the memory.

I use Super PC-Kwik for a disk cache, but I've used SmartDrive.  You
just have to tell them to not use all the extended memory.  I find
that 1.5M of extended memory free, and the rest for cache, leaves
enough for most compiles and runs.  If you use PC-Kwik, don't use the
Q option, as it can't handle the protected mode interrupt latency.

DJ (author of go32)
dj@ctron.com