aaron@stat.tamu.edu (Aaron Hightower) (05/07/91)
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 was programming on my Amiga 1000 before I had a hard drive. The RAD: drive is the only device that would be faster than the hard drive, and it has the ability to recover frequently when the system crashes. I haven't worried too much about it, and I haven't complained. The only reinforcement that RAD: actually does not work on the A3000 is in the AmigaDOS 2.0 manual from AmigaWorld. In this book, it mentions that commodore left some file out of the original distribution. Well, is there somewhere I can obtain this missing file, or will I never have a RAD: device to work on unless I go back to Workbench 2.0? Was there some other reason besides the possibility that the file was simply left out? Is it still being worked on?(!) *** WHY? *** (Excuse me...) Aaron "I must have missed something" Hightower
aaron@stat.tamu.edu (Aaron Hightower) (05/07/91)
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? >*** WHY? *** (Excuse me...) > >Aaron "I must have missed something" Hightower Aaron "again" Hightower
darren@cbmvax.commodore.com (Darren Greenwald) (05/07/91)
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.
kholland@hydra.unm.edu (Kiernan Holland) (05/20/91)
Matt, I want you to know that you are the only I guy I listen to. Not that I ignore everyone else but I do do a "/Matthew/h:s" everytime I'm in readnews. Don't try sending me mail, I am losing my account today. Later