CompuServe Thread

VD0: Help!

10 messages in this thread
#68289From: G. KlughOct 4, 1989 10:32 PM
Well, Hmmmmmm I took the (R) out of the startup, and did a COLDBOOT, and still got nothing!!!!! what can I be doing??? have you tried this new one??(july version?) Thanks for telling me about the R though!!! any more ideas?? My rad works just fine! but this VD0: is a killer! Greg 71456,702
#68314From: Brian BartlettOct 5, 1989 7:01 AM
Greg, one of the local users here had a similiar problem, and his solution was to load one of the two first. Unfortunately, I cant remember the order that he loaded it in, but there was a specific order that it HAD to be done in, or it wouldn't work. I _think_ it was VD0: first, then RAD:, but I'm not sure. Brian J. Bartlett
#68362From: Ray LewisOct 5, 1989 6:43 PM
Brian: I mount my ASDG vd0: after my Rad:. That works for me. So, maybe that's the problem? Greg — are you doing rad: first? Ray Lewis
#68425From: G. KlughOct 5, 1989 11:39 PM
Thanks BRIAN, I will try both orders, but the Docs said that the Rad should be started first!??? Greg 71456,702
#68991From: Matthew J. W. RatcliffOct 9, 1989 4:18 PM
Off the track a little, but the CLI command avail will tell how much CHIP and FAST RAM are present.
#68361From: Ray LewisOct 5, 1989 6:43 PM
Greg: Try changing your Mountlist so it can use any ram for the vd0: (0 or 1, I think). Make sure that you don't have the high cylinder value for the vd0: in the mountlist so high that, after it load the rad, there isn't enough room for the vd0: Then, remember my older message — make sure that right after you mount vd0:, you also cd to vd0:. You can then immediately cd back to whatever floppy or hd segment you use as your boot disk. Ray Lewis
#68426From: G. KlughOct 5, 1989 11:39 PM
I am using a 1 for the memory thing, and the high cycle 19 What next???? 🙂 Greg 71456,702
#68926From: G. KlughOct 8, 1989 11:47 PM
Well, from what I have heard, the NEW ASDG was a BAD UPLOAD!!! and I have now downloaded the OLD version, and it works FINE!!!, But I have kept the MEMram thing or whatever at 5, cause the DOCS say so!!!!! dod you use yours on 1?? does it work? why would the writter say use only 5 or 3?? Greg 71456,702
#69025From: Ray LewisOct 9, 1989 6:54 PM
Well, 3 = chip only and 5 = fast only. So, I guess the way they set it up, you must be specific, rather than use 0 or 1 (which is either one). I was just trying to figure out what your problem might be. The only time anyone should use the R option on setpatch is if they have the Obese Agnus. If you have an Obese agnus on a 1 meg system, all your memory is CHIP ram, so you don't have any fast ram. If you don't have fast ram, then you can't have a vd0: that works ONLY in fast ram. On the other hand, if you don't have the obese agnus, it should work so long as you don't have a vd0: set for more than 512K. (BTW, if that's the case, you shouldn't be using the r switch on setpatch). Anyway, I'm glad you have it working! Ray Lewis
#69906From: G. KlughOct 16, 1989 1:07 AM
I have the OLD small angus! Greg 71456,702 Ps. Thanks for all of the GREAT HELP!