CompuServe Thread

RAD:-Help!

10 messages in this thread
#11833From: Dick BalaskaJul 5, 1991 4:16 PM
Help! I am having some problems w/rad: My machine/harddisk fails to reboot whenever i have used rad: (i think it tries to boot rad:) This would be OK except that AmiDos won't allow me to install rad: (must be df0-3:). Booting floppies works OK (but slowwww). What to do…What to do… Oh yes, i read here about jd0:. Is this preferred over rad: and what are the differences. – For Sale: one state (CT) Cheap! HandyMan's Special!
#11868From: Joe WylotJul 6, 1991 8:26 PM
Hi Richard, Have you modified the entry for RAD: in devs/mountlist perhaps? The only reason I can think of for the Amiga trying to boot of RAD: is if BootPri has been altered. If you include the line BootPri= -129 in the mountlist entry there is no way your machine will try to boot off it. Don't know about jd0: but have a look at RRD:. I've been using it for several months now without problems although some virus killers complain about the changed pointers. It does everything Rad: does but frees up memory which is not required. Can be recoverable/bootable and can even be formated like a floppy! Hope this helps. Joe Wylot – via Whap!
#11983From: David HammJul 10, 1991 9:53 PM
Richard, I've been using RAD: for years now, but don't ask me why 🙂 ! Actually, I use it with almost every boot… If you follow Joe's advice, everything otta work out for ya. It may help to read some AmigaDOS manual telling ya how to set up… Add the mountlist entry and then mount the RAD: device when ya boot up. – Uhmmm… VD0: is a recoverable RAM disk (like RAD:), but it has the ability to expand with usage (like RAM:). I think ASDG are the ones that make VD0: I may switch to VD0: in the near future. The RAD: device just does not have the same robust capabilities that it had before the AGNUS chip set upgrade. – Dave
#12034From: John PendergrassJul 13, 1991 10:49 PM
Actually VD0: does not -expand- its memory as it requires, it -limits- its memory as required. What this means is that you can specify a 1meg ram disk (for example) and if you only have a 25K file in it, it only takes up 25K of memory (plus a real minor amt for bookkeeping). If you later add a 500K file it grows to accomodate it. If you tried to add a 1500K file, however, it would run 'out of space'. If you declare a 1meg ram disk with RAD, on the other hand, 1meg is used up regardless of how much the disk actually holds. ASDG's VD0 is far superior, in my book. –jp–seattle–
#12048From: Michael GerardJul 14, 1991 11:43 AM
JP: Does ASDG's VD0: work with WB 2.0? – Whapping from the North Coast Michael
#12057From: John PendergrassJul 14, 1991 1:01 PM
Well, I don't really know. I don't think it is 'officially' said to run under 2.0, but I have used it with 2.0 on my system with no obvious problems so far. I run 2.0 rarely, however, so I can't say it has been tested to any hard degree. When 2.0 hits the streets big-time, I sure -hope- that there is an 'official' ram disk that works like VD0, that I can trust like I trust VD0. I've heard that there is a 'supported' 2.0 ram disk device out there now, that functions much the same as ASDG's VD0, but it is limited to a 1meg ram disk size (too small for me I'm afraid). Forgot the name of it though. (maybe if ALL the people who use VD0 would suddenly send in their $10.00 registration fee, ASDG would consider reworking it to be guaranteed under 2.0?) –jp–seattle–
#12059From: Black Belt SystemsJul 14, 1991 5:40 PM
0Might be something to direct to Perry in the Vendor forum. But I *think* he considers it a bit moot, with RAD: and etc out there. Ben Amateur Radio Callsign is A A 7 A S
#12063From: John PendergrassJul 14, 1991 8:36 PM
Yeah, he has as much as said that it's never going to be updated, but there still is a vital need for it, IMHO. I'd sorely miss ASDG's VD0 if I had to give it up. [I had to for a couple of months once, and you know what? – it's true, you never know what you had till you lose it 🙂 ] –jp–seattle–
#12125From: Betty Clay/SYSOPJul 16, 1991 11:45 PM
I read on a local BBS that VDK: works well with 2.0, so you might look into that one. I don't know if there has been an update, or if they were speaking of the one that has been around a long time. I know that VDK was written by Neil Katin, and was not freely distributable, but it came free with something I bought from Expansion Technologies, if memory serves. I think it only cost about $10, though.
#12129From: John PendergrassJul 17, 1991 12:21 AM
Thanks, I'll check fileFinder for VDK:; maybe it will be the ticket. I'd gladly pay $10 for a usable ram-efficient ram drive. –jp–seattle–