[Coco] Ownership of NitOS-9

[Bill Pierce]

David, the only downshot of "config" is that it requires knowledge of the system files and what they do from the start. Also, it wouldn't cover all the current "additions" and configurations available in NitrOS9 these days. I used config as well for years, at least untill I got "ezgen" and I've never "os9gen"ed another boot since. I just "cobbler" my boot to the new disk, then use "ezgen" to add/delete what I want. Again... requires the knowledge of the system and what you want/need.
What Nick is referring to is a "KISSable" boot creator that will do the work for you with no system knowledge, which is similar to a project I have going right now.
 

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: David Gettle <david17361 at gmail.com>
To: CoCoList for Color Computer Enthusiasts <coco at maltedmedia.com>
Sent: Thu, Nov 6, 2014 6:41 pm
Subject: Re: [Coco] Ownership of NitOS-9


There was a utility in the Tandy distro of OS-9level2 that would let a user
select modules to be included in a new boot file, and then create the boot
file, if I remember correctly they simply called it config (I haven't
booted my CoCo in over a year, but have used an emulator), it created the
build list for OS9Boot, then called OS9Gen to create the file, then called
attr to set the required file attributes for the boot file. I have used it
to create OS-9Level1, OS-9Level2 and NitrOS-9 boot files, but it requires
all of the modules to be in the same directory, unlike the way the NitrOS9
distros are set up.

Sorry for the late reply to all of this but I finally read through it all.