Path: utzoo!utgpu!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!unmvax!ncar!ames!pasteur!ucbvax!kepler.Berkeley.EDU!me128-aw
From: me128-aw@kepler.Berkeley.EDU (me128 student)
Newsgroups: comp.sys.amiga
Subject: Re: Ami crashes, RAD:
Message-ID: <27071@ucbvax.BERKELEY.EDU>
Date: 8 Dec 88 20:53:19 GMT
References: <27024@ucbvax.BERKELEY.EDU> <111400012@uxa.cso.uiuc.edu>
Sender: usenet@ucbvax.BERKELEY.EDU
Reply-To: me128-aw@kepler.Berkeley.EDU (me128 student)
Organization: University of California, Berkeley
Lines: 15

In article <111400012@uxa.cso.uiuc.edu> sc00250@uxa.cso.uiuc.edu writes:
>
>I've been using rad: and vd0: in conjunction with each other since early June.
>One of the other responses indicated the need to copy files into vd0:, mount
>Rad:, then copy form vd0: to rad:, and finally delete the stuff from vd0:.
>Forgive my bluntness, but this is totally convoluted.  There is absolutely 
>no reason to do this. 
>

 have had problems when i try to diskcopy to rad: with vd0: existing.  If I
do so, then both ramdisks will show the contents I just diskcopied, not just
RAD:.   Sometimes vd0: will also lose its name, and the system will just
crash.  It continues to crash until I turn the machine off and then on again.
I haven't tried it in some time, as I wasted a few hours on it some time
ago.