didier@seismo.CSS.GOV@lasso.UUCP (02/11/87)
I have had no success whatsoever when trying to resize the recently posted
eternal2 ramdisk. It resizes alright, but loses its contents. Not very
useful.
Also, I have noticed that with a ramdisk installed, say in drive C, whenever
I save the desktop, the desktop.inf goes in the C ramdisk, not in the A floppy.
Is this a desirable feature ? It certainly is a bit annoying, since it requires
an extra copy from C to A.
Didier Giralt LAAS-CNRS
7 av du Colonel Roche
...!seismo!mcvax!inria!lasso!didier 31077 Toulouse Cedex
Francefranco@iuvax.UUCP (02/12/87)
The eternal2 ramdisk that I posted does have its limitations. The first limitation that you pointed out is indeeed annoying but I find the ramdisk is still quite useful since I often do not need the contents of the ramdisk when I resize. I believe ETERNAL2 is superior to the INTERSECT ramdisk which I had been using in order to get resizing. Now I have freed up some space since I no longer need it. I intend to code up a ramdisk which resizes itself automatically (lots of little details to take care of here) and takes care of the limitation mentioned. Maybe someone can beat me to it (hopefully). I will have to check out the second limitation. I did not test for that. Finally, I should have mentioned this before but you can use any shift key to zero the ramdisk on reset (I guess an appreciation for symetry got the best of me).
mdoerr@uklirb.UUCP (02/19/87)
When the DESKTOP notices that there's a drive C: available, the DESKTOP.INF gets stored on that drive, instead of drive A:. As a RAMdisk looks like a HD to the DESKTOP, this even makes sense: When using a harddisk drive C: is usually your boot device containing all the nice AUTO-stuff, accessories and DESKTOP.INF. I know that it's inconvienient to manually copy DESKTOP.INF from a ramdisk to the floppy in drive A:, but it's a nice feature when having a selfbooting HD. Michael Doerr, Uni. Kaiserslautern ...!seismo!unido!uklirb!mdoerr