Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!sdd.hp.com!wuarchive!udel!rochester!rutgers!cbmvax!darren
From: darren@cbmvax.commodore.com (Darren Greenwald)
Newsgroups: comp.sys.amiga.programmer
Subject: Re: What happened to RAD: ?
Keywords: RAD
Message-ID: <21338@cbmvax.commodore.com>
Date: 7 May 91 14:38:11 GMT
References: <4871.tnews@tower.actrix.gen.nz> <15940@helios.TAMU.EDU> <15941@helios.TAMU.EDU>
Reply-To: darren@cbmvax.commodore.com (Darren Greenwald)
Organization: Commodore, West Chester, PA
Lines: 18

In article <15941@helios.TAMU.EDU> aaron@stat.tamu.edu (Aaron Hightower) writes:
>In article <15940@helios.TAMU.EDU> aaron@stat.tamu.edu (Aaron Hightower) writes:
>>A while ago I found that the RAD: device, while listed in the mountlist, does
>>not work on the Amiga 3000.  This is one of the luxuries that I had while I
>
>After changing the size of the rad device, I got the thing to mount.  I would
>have expected a more meaningful message like "not enough memory to mount RAD:
>device" if that was the problem.  Well, I am even more confused now.  It
>seems that the RAD: device does not use the device driver that it refers to
>called "ramdrive.device" in the devs: directory.  What's the story on this?
>

It does; ramdrive.device is part of Kickstart 2.0 (for now); you won't find it
in the DEVS: directory on your WB disk.  You could see it with a tool like WACK.

Yea, the default mountlist is for a floppy disk sized RAD; perhaps a bit too large
for a default, though also the most useful size for those that don't know how
to edit their mountlists.