kim@amdahl.UUCP (01/25/87)
[ ... go ahead, eat my bits ... ]
First, I want to thank Perry for posting the Recoverable Ram Disk program
and support utilities! It works great, and will save alot of time and
frustration on future trips to Guru-land. And yes, I will become a "registered"
owner before the week is out.
Now for a couple of observations and questions. I have a 1-Meg C.Ltd board,
and have been using the normal RAM: device since adding it to my system. In
addition to copying the c: and s: directories (about 60 files, or so) out
to ram:c and ram:s, my Startup-Sequence fires off MenuClock (by Mike Meyer),
and installs the resident utilities GRABBiT and AnyTime (Discovery Software),
and PopCLI (Software Distillery). Also, I have "shell" (v2.05m, Matt Dillon/
Steve Drew) running from the CLI. Oh yeah, I also do AddBuffers 30 for both
df0: and df1:.
With the above configuration using the RAM: device, immediately after booting,
the memory display in MenuClock shows I have 396K Chip, and 447K Fast memory
available. The Avail command shows similar (though not identical) numbers.
Using the exact same configuration, but using the VD0: device, I end up with
396K Chip, and 319K Fast memory available. This is after making sure that
VD0: has been "squeezed" by running CleanRamDisk, and doing a few "dir vd0:c"
commands, etc. Again, Avail confirms these numbers shown by MenuClock.
This seems like an awful lot of "overhead" (~128K !) to support the 60 or so
files and 5 directories that are in VD0: ... is this a "typical" amount?
Can you comment on the allocation scheme, Perry? I've also tried installing
the resident stuff and loading VD0: in different sequences, but that hasn't
made any difference. BTW, I set HighCyl = 111 (for 896K), if that should
matter.
A couple of other checks ... the Info command shows:
with RAM: 438K 875 used 0 free
with VD0: 896K 879 used 911 free
and from shell's "dir" command, dir c: shows:
with RAM: 819 blocks 376752 bytes 54 files
with VD0: 854 blocks 376752 bytes 54 files
Don't get me wrong, I'm not flaming the Recoverable Ram Disk, or anything.
I *am* trying to figure out if I have a problem with the way I've installed
it, or have things configured, etc. Or maybe it just takes more overhead
than I was expecting.
Thanks again, Perry ... any light you can shed on this will be appreciated!
/kim
P.S. I do have one suggestion for SysMon ... in a future release, could
you just use regular text for the labeling? With the particular
Preferences I use (amber type on black, with blue cursor and creme
4th color), the shaded block "font" in SysMon is all but impossible
to read. I'm sure not everyone uses the stock Preferences settings
(do they?)
--
UUCP: kim@amdahl.amdahl.com
or: {sun,decwrl,hplabs,pyramid,ihnp4,seismo,oliveb,cbosgd}!amdahl!kim
DDD: 408-746-8462
USPS: Amdahl Corp. M/S 249, 1250 E. Arques Av, Sunnyvale, CA 94086
CIS: 76535,25
[ Any thoughts or opinions which may or may not have been expressed ]
[ herein are my own. They are not necessarily those of my employer. ]