[Coco] Just learning OS-9 - Questions

[Wayne Campbell]

When it comes to boot disk creation, I always used config. I never learned it under level 1 because I had a coco2 for less than a year and when I got it a friend helped me make a boot disk separate from the master (but the same as far as the boot file was concerned.

I got a Tandy 2000 that I took the 2 360k floppies and the 20 meg hd from for use with my coco3. I used the hd for storing the files on all the disks. From then on I used config to make custom boots.

By the time I came back to os9 I couldn't remember how to make a boot disk. Aaron Wolfe helped me get set up again and I have not tried to make another boot floppy for lack of need.

Wayne


nickma at optusnet.com.au wrote:

>>You quickly run into trouble, not all "OS-9 modules/driver/commands
>known to 
>>mortal man" are known by one person, or even a large group of
>persons.
>
>And this raises another suggestion.
>
>Yes, it will be difficult to obtain every driver "known to mortal man"
>but my suggestion is that a set of install disks that contain most of
>these drivers/modules be supplied with updates occurring as new
>drivers are submitted.
>
>One disk with CMDS, another with Device Drivers etc.
>
>Then, as part of the "smarts" in the installer program, it would look
>at these folders/disks, tally up what's there automatically and
>present the options for selection.
>
>Or, a system where new modules are added to the archive and the
>details appended to a bootlist or "registry" file that the main
>installer reads.
>
>Maybe as part of the installer, a sub-menu to allow user additions to
>the main bootlist which asks the user what the new driver is, what
>it's called and where it's to be stored. Then the main installer will
>know about the new addition to present to the user when doing a main
>system install.
>
>It can be done.
>
>Nick
>
>-------------------------
>Email sent using Optus Webmail
>
>--
>Coco mailing list
>Coco at maltedmedia.com
>http://five.pairlist.net/mailman/listinfo/coco