shawn@pnet51.cts.com (Shawn Stanley) (10/07/88)
Recently, I posted a message concerning my problems with getting GS/OS to
recognize my Apple 20SC hard drive. I have solved this problem. Apparently,
there was an Apple SCSI ROM (revision C) upgrade that I had been unaware of,
and after calling around and locating a dealer with the upgrade in-stock (I'm
impatient after receing my GS/OS disks and not being able to use them right
away! :-), I had the upgrade done and am currently happy with the results.
GS/OS likes my Apple hard drive!
However, I have a request. There's no documentation available to end-users
on the cache yet, but I would very much like the ability to have more control
over it. Specifically, I place certain files in the /RAM volume to speed up
some abilities of my BBS. However, with the cache invoked, it also caches
the /RAM volume, thus slowing down /RAM file access times. Can something be
done about this that wouldn't hinder the "application transparent" /RAM
media? If caching could be turned off for certain drives, it would be a
wonderful addition.
UUCP: {rosevax, crash}!orbit!pnet51!shawn
INET: shawn@pnet51.cts.commvs@meccsd.MECC.MN.ORG (Michael V. Stein) (10/09/88)
In article <9885@srcsip.UUCP> shankar@columbus.UUCP (Subash Shankar) writes: >Another potential improvement would be to cache a whole track when reading >a block since the track is read anyway. I believe that the Applied Eng. >GSRAM cache does this, and it makes a great difference when copying files >and disks. Keith? This probably wouldn't be very helpful. With GS/OS the FST can tell the device driver that it wants to read N blocks starting from a particular block. -- Michael V. Stein - Minnesota Educational Computing Corp. - Technical Services {bungia,uiucdcs,umn-cs}!meccts!mvs or mvs@mecc.MN.ORG