[Coco] Need help using ram drive as default drive
Ed & Donna Vanderberg
vanderfamily at peoplepc.com
Tue Jun 21 22:24:24 EDT 2011
I do not know if this post will even make it to the list as I am still in the process of joining but here goes ...
In my old age I became interested in Picaxe microcontrollers which eventually led to uncrating my old CoCo equipment to attempt interfacing the two systems. As an old OS9 newbie (if that makes sense) I wanted to make a proc that monitors the bitbanger port for Picaxe I/O to provide acces to I2C & other chips (RTC, 8/10 bit ADC, DAC, unlimited digital I/O, etc.) for CoCo (and enhanced display & disk capabilities and floating point math to my Picaxe network). I immediately ran into NitrOS9 and fell in love again with the CoCo. Actually, since I successfully booted NitrOS9 in April, I haven't even turned on the Picaxe - love that OS9.
I have read almost the entire archive of the CoCo list but I have a problem enabling a ramdisk as the default drive at boot. The ramdrive successfully retains my CMDS and SYS through a boot (even a failed boot - sweet) but if I use the /DDR0 driver my boot fails:
...Clock Clock2 Sysgo i2xtot*j
based on posts from Boisy I interpret ths as module not found - great - which module? It would appear to me it is not the /term as seemed to be the case in a previous post but rather choking on the /ddr0_192.dd. As an added wrinkle, I have Dmoded the /ro to match my 5 1/4" parameters so on boot I can slam the CMDS & SYS to the ramdrive using backup and avoid dsave (slow slow and noisy) but cannot get the /ddr0 descriptor loaded so I cannot dmode it to match floppy. Can anyone offer any advice on booting from /d0 of course but ending with ramdrive as /DD?
The main reason that I want the ramdrive to be /DD is so that the commands, help and error info are immediate (and quiet - my 3 1/2" is noisy). So close. Hence my need to post a question to the list.
By the way, it amazes me how many CoCo superstars of the 80's that I used to follow are on this list - love to see so many still involved.
Ed Vanderberg
More information about the Coco
mailing list