Path: utzoo!attcan!uunet!super!udel!rochester!cornell!mailrus!cwjcc!hal!nic.MR.NET!tank!sphinx.uchicago.edu!arxt
From: arxt@sphinx.uchicago.edu (patrick  palmer)
Newsgroups: comp.sys.amiga
Subject: rad: versus vd0:
Keywords: rad:,vd0:
Message-ID: <894@tank.uchicago.edu>
Date: 22 Nov 88 22:31:00 GMT
Sender: news@tank.uchicago.edu
Reply-To: arxt@sphinx.uchicago.edu (patrick  palmer)
Distribution: na
Organization: University of Chicago Computing Organizations
Lines: 28


I installed 1.3 and autobooting last weekend.  It was very easy, thanks to
Go Amigo and GVP.  I have a question about rad:

I used to use vd0:.  In spite of space being alloted to vd0:, Workbench always
indicated the total amount free, counting only what was actually used in vd0:
, not what was assigned in mountlist.  (I was always curious about what would 
happen if I filled ram: so that less space was left than was assigned to vd0:,
but it never happened so I never found out.)  With 1.3, the space assigned to
rad: is deducted from the available free ram (in the workbench top line - I 
really should learn the names of these things).  If vd0: really was so 
flexible as to allow more ram: to be used when vd0: was not full, I would 
prefer to use vd0: - I think.

My questions:
	1. Was vd0: as flexible as it appeared to be to the naive user?
	2. Is there a good reason to use rad: instead anyway? (I do not
	   need it for autobooting.)
	3. When I tried to install vd0: under 1.3, I screwed everything up
	   so badly that a warm reboot would not recover.  I had just copied
	   the relevant part of mountlist from 1.2, copied vdisk.device
	   to the devs directory, and mounted vd0: in my startup sequence as I
	   had under 1.2.  Is there something else that needs to be 
	   changed to install vd0: under 1.3?  Or did I just screw up?

Pat Palmer   email:  arxt@sphinx.uchicago.edu  (bitnet or arpanet)