Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!swrinde!cs.utexas.edu!sun-barr!rutgers!bobsbox!graphics!elund
From: elund@graphics.rent.com (Eric W. Lund - Subop)
Newsgroups: comp.sys.ibm.pc.misc
Subject: Re: Command.com in ramdisk
Message-ID: <9o8X13w164w@graphics.rent.com>
Date: 25 Apr 91 07:23:07 GMT
References: <cs352a41.672535168@zippy>
Organization: The Graphics BBS (2D,3D,GIF,Animation) +1 908/469-0049
Lines: 27

cs352a41@cs.iastate.edu (Adam Goldberg) writes:

> Thanks to all who've sent me mail suggesting that I use a disk cache.  I'm
> trying one out now, and it's kinda fun.  I don't see the 900% improvement
> that some claim, but a little bit of improvement is ok, too...384k just
> sitting there at 10000h is a bit of a waste, so I'm better off now.

I use my extra 384 for a cache, and most applications I notice a speedup.  
It is particularly helpful when running animation, for example an Autodesk 
Animator FLI file under 384k in size.  After one pass through the animation, 
the disk access stops, the animation speeds up, and becomes much smoother.

The extra 384k *IS* extended memory (XMS), not expanded (EMS).  It can 
emulate expanded, by use of a driver (I have many), but I do not advise it.  
Expanded memory works by using a "window" through which data can be 
transferred.  All the EMS->XMS drivers I've seen create a 64k window in MAIN 
system memory (<640k).  That's a waste of main memory -- main memory is 
precious to programs that DON'T use expanded memory.  And I have used 
several programs that use expanded, but need a good deal of system ram 
wether you've got that expanded installed or not!  (Those who have tried to 
use Wing Commander on a 1 meg system with XMS->EMS drivers will know what 
I'm talking about.)

If you can, put the CACHE in a batch file, with an appropriate uninstaller 
batch file if possible.  PCTOOLS 4.5 and above have this, including the 
uninstall feature.  (Of course, I'm afflicted with TSR-fright.  I even have 
my mouse in a batch file.)