[comp.sys.amiga] rad: versus vd0:

arxt@sphinx.uchicago.edu (patrick palmer) (11/23/88)

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)

                     

ecphssrw@solaria.csun.edu (Stephen Walton) (11/24/88)

In article <894@tank.uchicago.edu> arxt@sphinx.uchicago.edu (patrick  palmer) writes:
>
>	1. Was vd0: as flexible as it appeared to be to the naive user?

Yes.  The ASDG-RRD is really a very good product, though I know Andy Finkel
isn't too fond of some of the things it does with the system free memory
list (the reason vd0: is trashed by FastMemFirst is that it gets its ram
from the END of the free list, which FastMemFirst makes the 0xC00000 block
complete with destructive detection).

>	2. Is there a good reason to use rad: instead anyway? (I do not
>	   need it for autobooting.)

Well, if you don't want to autoboot from RAD: you can install FFS on it.
Makes it a lot faster (format it first, copy the GlobVec, Mount, DosType,
and FileSystem lines from the FAST: entry in the sample MountList with 1.3).

>	3. When I tried to install vd0: under 1.3, I screwed everything up
>	   so badly that a warm reboot would not recover.

Probably you ran FastMemFirst before mounting VD0:.  See above.
-- 
Stephen Walton, Dept. of Physics & Astronomy, Cal State Univ. Northridge
RCKG01M@CALSTATE.BITNET       ecphssrw@afws.csun.edu
swalton@solar.stanford.edu    ...!csun!afws.csun.edu!bcphssrw