fredc@umriscc.tmc.edu (Fred Clauss) (11/02/90)
I have recently switched over my workbench to ARP 1.3, and I am having a bit of a problem, although it is not currently affecting everyday use. When I got VD0: from a Fish disk some time back, I followed the directions in the documentation which said to relabel it as RAM: (not knowing why I should do so). This worked fine until I switched everything over to ARP. Now the relabel doesn't seem to work. For the time being, I just repaired my startup-sequence to work around not having a RAM: drive (used for T:, ENV:, and CLIPBOARDS: ), but consider that to be an inferior solution. Has anyone overcome this problem? Will I have to go back to the original relabel command? While I am on the subject, what is this CleanRamDisk program? I have yet to have memory problems since I added 2 meg, but I probably will once I start writing programs. Also, is VDK available as shareware? I also might be interested in RRamDisk if it isn't too expensive. -- Fred Clauss INTERNET: fredc@isc.umr.edu (preferred) P.O. Box 815 or fredc@ee.umr.edu Rolla, MO 65401 BITNET: S081192@UMRVMA
FelineGrace@cup.portal.com (Dana B Bourgeois) (11/04/90)
CleanRamDisk forces everything off the VD0: ramdrive. It cleans it. I don't use it myself because I have enough memory (like you) but it is there for people who want to force the ramdisk smaller. Just deleting files from VD0: doesn't do it because the space is not reclaimed when the files are deleted. The disk stays the same size and shrinks only as other programs need memory. This was explained as a performance thing. Why take the time to give memory back to the system if no one else needs it and the ramdisk is likely to ask for it again later. The gradual shrinking is because unused ramdisk space is given back to the OS slowly as other memory deallocations are made. No big performance hit there. Course I could be all wet since this is from my memory of the docs. Please correct me where I got off course. Dana Bourgeois @ cup.portal.com