[Coco] Need help using ram drive as default drive

[Vanderberg Family]

yes, sysgo is in both /d0 which is /dd and /r0 just in case something works & it looks there.

I saw some of your posts about modifying init & tried changing /dd to /d0 in both init and sysgo where I also found it.  I attempted to boot with each single change with all else the same and also with both files modded.  As far as I could tell, there was no diff in behavior or boot failure regardless of the permutation.  Both files are back to orig.  Any hints for the next step?

Understand I am way beyond my knowledge level here, but that just makes it more fun.


-----Original Message-----
>From: "Boisy G. Pitre" <boisy at tee-boy.com>
>Sent: Jun 21, 2011 5:36 PM
>To: CoCoList for Color Computer Enthusiasts <coco at maltedmedia.com>
>Subject: Re: [Coco] Need help using ram drive as default drive
>
>Ed,
>
>It's good to see you're back in love with NitrOS-9.
>
>As per your error, do you have the sysgo module in the root directory of the ram disk?
>--
>Boisy G. Pitre
>http://www.tee-boy.com/
>
>On Jun 21, 2011, at 9:24 PM, Ed & Donna Vanderberg wrote:
>
>> 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
>> 
>> --
>> Coco mailing list
>> Coco at maltedmedia.com
>> http://five.pairlist.net/mailman/listinfo/coco
>
>
>--
>Coco mailing list
>Coco at maltedmedia.com
>http://five.pairlist.net/mailman/listinfo/coco


________________________________________
PeoplePC Online
A better way to Internet
http://www.peoplepc.com