Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!samsung!munnari.oz.au!bruce!trlluna!titan!aduncan
From: aduncan@titan.trl.OZ.AU (Allan Duncan)
Newsgroups: comp.sys.amiga.misc
Subject: Re: WARNING!  RRamDisk may be bad for your files' health!
Message-ID: <3459@trlluna.trl.oz>
Date: 5 May 91 22:21:33 GMT
References: <1991May3.063511.4135@daffy.cs.wisc.edu>
Sender: news@trlluna.trl.oz
Lines: 20

From article <1991May3.063511.4135@daffy.cs.wisc.edu>, by pochron@cat51.cs.wisc.edu (David Pochron):
...
> further checking with DiskX, I discovered the ramdisk.device seems to be
> consistently erasing the first track (both sides) of the virtual floppy RAM
> disk space!  In other words, any files that used keys 2 through 21 were
> always trashed because those tracks were getting cleared.
> 
> It didn't matter whether I used the FAST: device entry or the DISK:
> device entry that came in the .lzh file mountlist - both lost data.
> 
> Varying the original mountlists that came in RRamDisk.lzh had no effect.

Did that include setting reserved=22 ?  To my understanding, this should
leave the first 22 blocks unused (and hence unclobberable).  This will
stop trashing, but not raise confidence in the integrity of the
program.
Allan Duncan	ACSnet	 a.duncan@trl.oz
(+613) 541 6708	Internet a.duncan@trl.oz.au
		UUCP	 {uunet,hplabs,ukc}!munnari!trl.oz.au!a.duncan
Telecom Research Labs, PO Box 249, Clayton, Victoria, 3168, Australia.