[Coco] NitrOS-9 boot configuration tool

[Bill Pierce]

Nick... that's exactly what the NitrOS9 repo does... build bootdisks form Linux or Windows (using MinGW or CYGWin)
To get it build anything other than what is already offered, you must download and modify the sources in your own local copy of the repo and build it.... but wait... that's a bigger can of works than making a bootdisk in OS9 from preassembled files... a MUCH bigger can of worms... more like a barrel of rattlesnakes!
In this case you will be ASSEMBLING ALL the files in the repo and need to know what each file is, what it does, what machine/system it's being used own as the repo builds for Coco 1, 2, 2b, Deluxe, & 3,  Dragon64, Dragon Alpha, and Atari, all in L1 & L2 all from one set of sources!
The makefile alone could scare the hell out of geek with a Masters in Computer Science as it is written in uncommonsensaneese :-P

 

Bill Pierce
"Today is a good day... I woke up" - Ritchie Havens
 

My Music from the Tandy/Radio Shack Color Computer 2 & 3
https://sites.google.com/site/dabarnstudio/
Co-Webmaster of The TRS-80 Color Computer Archive
http://www.colorcomputerarchive.com/
Co-Contributor, Co-Editor for CocoPedia
http://www.cocopedia.com/wiki/index.php/Main_Page
E-Mail: ooogalapasooo at aol.com


 
 
-----Original Message-----
From: Nick Marentes <nickma2 at optusnet.com.au>
To: CoCoList for Color Computer Enthusiasts <coco at maltedmedia.com>
Sent: Sat, Nov 8, 2014 2:58 pm
Subject: Re: [Coco] NitrOS-9 boot configuration tool


On 9/11/2014 3:24 AM, L. Curtis Boyle wrote:
> Heh.. this is something else that Bill and I had planned for NitrOS9 and never 
got to. We were going to have the user making the bootfile pick out the device 
descriptors they needed (this is where the database part would come in… to show 
which version of /d0 one was picking for example: Floppy, no Halt Disto floppy, 
no halt Sardis floppy, etc.)), but it would use the device descriptor itself to 
figure out which driver and file manager was required for each, since the names 
of those is stored in the descriptor already anyways (and used by the OS 
itself).
> Of course, there are “fixed” ones that every normal boot would need (RBF, SCF, 
IOMAN, etc.) that would always automatically be put in (maybe an option for 
“customized” versions).
>
> L. Curtis Boyle
> curtisboyle at sasktel.net
>
>

Is it possible to write a program on the PC to build the NitOS-9 boot 
image(dsk)?

All the require drivers and modules would be collected in a folder on 
the PC hard disk and a program listing everything that the user simply 
"tick's a box" on the drivers/modules he wants?

The program would generate a DSK file with a NitrOS-9 boot image all 
configured and this can be run on an emulator or used by Drivewire, SDC etc.

That way users can easily and quickly create custom boot disks whenever 
needed.

Nick

-- 
Coco mailing list
Coco at maltedmedia.com
https://pairlist5.pair.net/mailman/listinfo/coco