[Coco] Need help using ram drive as default drive

[Boisy G. Pitre]

Robert/Ed,

I read the posts subsequent to my initial post.  Yes, by using a RAM disk, data persists as long as the CoCo is not turned completely off, in which case, the process of copying all needed files to the RAM disk must be done again.

Assuming your RAM disk was volatile, or that you didn't mind copying files each time you rebooted, you would need, as Robert indicated, to use the ram disk booter.

Ed, I highly suggest that you abandon the use of cobbler and look at Disk 2 of the NitrOS-9 disk set.  It has scripts to all the work of creating a track file and a boot file, and your customization can be done there.  For starters, see this link:

http://sourceforge.net/apps/mediawiki/nitros9/index.php?title=Getting_Started_with_NitrOS-9#Customizing_Your_System

It explains how to customize your system using this scripting process.


--
Boisy G. Pitre
http://www.tee-boy.com/

On Jun 22, 2011, at 7:19 AM, Robert Gault wrote:

> Vanderberg Family wrote:
> 
>> I boot to NitOS9 from /d0
>> Format /r0 and then backup /d1 to /r0 from a prebuilt ram disk image with CMDS, SYS, sysgo, startup, etc.
>> chx /r0/cmds
>> 
> 
> Ed,
> 
> OK, now that makes sense. It also means that any reboot problems which then occur without turning off the system are the result of the wrong modules in the OS9Boot file on /r0 (but see below). Any problems with programs going to /d0 for information are the result of those programs being hard coded for /d0.
> 
> You must set up the /r0 disk so that the boot module on track 34 reads from /r0 not /d0. You should make the /dd descriptor module on /r0 be identical to the descriptor for /r0 except with an internal name of /dd. Modules Init and Sysgo can stay as they are as long as they refer to /dd and /dd is now /r0.
> 
> There is one other problem which you seem to have solved but not stated how. If you were to boot from /d0 and then backup /d1 to /r0, any reboot would have the /d0 data in memory and you would not be making use of /r0 for rebooting.
> 
> There are two ways around that problem. You could use a utility to change the Boot module in memory so that it accessed /r0. You could start a RAM disk from Basic and boot from the RAM disk rather than /d0.
> 
> The above can give you clues for solving the problems yourself. The only way to get more exact answers would be to make available your /r0 disk so others could test it.
> 
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco