[Coco] NitrOS9 Bootfile Dependacy Tree

Sun Nov 9 12:56:35 EST 2014

Gene, I did them in my local repo... or actually on my vhd in NitrOS9 in which I create all my boots for my Starter Kits. They are not in the repo, in fact, some of the combos listed in the list are not imediately available without knowledge of where they are, EmuDsk being a good example, it's in the repo, it is built when you "make" the whole repo, but it and it's descriptors are not included on any disk in the distro. Another is Burke and Burke which I didn't include...
I was going to include the Burke & Burke drivers, but the descriptors have to be made specifically for each drive model, type and size and it would be too much for the "easy to use", point-n-click system I'm developing. Again... simplicity.
I figure if they have a Burke & Burke system, then they most likely know how to set it up.
My "BootMajik" system will provide a complete distro of modules with the system as well as a way to update them as they change.

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: Gene Heskett <gheskett at wdtv.com>
To: coco <coco at maltedmedia.com>
Sent: Sun, Nov 9, 2014 12:27 pm
Subject: Re: [Coco] NitrOS9 Bootfile Dependacy Tree

On Sunday 09 November 2014 12:14:50 Bill Pierce via Coco did opine
And Gene did reply:
> Gene, in my BootMajik I'm supplying "pre-set" descriptors for the
> simple reason that the average user can't read and therefore will not
> read the MyRam docs (or so it seems :-P) That's the only reason I
> included these. I know it can be set to any size from the cmd line...
> I do it all the time :-) Again... the whole idea is to make user input
> non-existent, therefore error free operation and most of all.... No
> questions that the docs would have answered in the first place had
> they read them.
> 
> 
> Bill Pierce
> "Today is a good day... I woke up" - Ritchie Havens

Oooohkaaaay, but who is going to generate those descriptors, or are you 
doing it on the fly by forking dmode for each variation?  My point being 
that they are not in the repo unless added in the last 10 days or so. 
> 
> 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: Gene Heskett <gheskett at wdtv.com>
> To: coco <coco at maltedmedia.com>
> Sent: Sun, Nov 9, 2014 12:03 pm
> Subject: Re: [Coco] NitrOS9 Bootfile Dependacy Tree
> 
> 
> On Sunday 09 November 2014 09:03:32 Bill Pierce via Coco did opine
> 
> And Gene did reply:
> > Ok, I've completed the dependacy tree but only for NOS9 L2. This
> > should be usable on 6809 & 6309 machines as all of these files exist
> > for both versions (though some are just 6809) and are all on both
> > distro disks formats. I included the dependacies for EmuDsk and it's
> > descriptors even though they are not included on the distro disks,
> > but are compiled with the repo and can be found at
> > "3rdparty/drivers'emudsk". These really should be moved to the
> > modules folders as they are used as much as any driver there. I
> > suspect there are many more emulator users than real Coco users.
> > Here is the list
> > https://dl.dropboxusercontent.com/u/23059963/NitrOS9/NitrOS9_L2_BootF
> > il e_Dependacy_Tree.txt
> 
> This part is wrong:
> 	myram.dr
> 	MyRam Dynamic Ramdisk Driver by Gene Heskett
> 
> 		(1 required for myram.dr)
> 		myram_r0_24k.dd
> 		MyRam Ramdisk Drive descriptor 24k - /r0
> 
> 		myram_r0_48k.dd
> 		MyRam Ramdisk Drive descriptor 48k - /r0
> 
> 		myram_r0_96k.dd
> 		MyRam Ramdisk Drive descriptor 96k (512k only) - /r0
> 
> 		myram_r0_128k.dd
> 		MyRam Ramdisk Drive descriptor 128k (512k only) - /r0
> 
> 		myram_r0_256k.dd
> 		MyRam Ramdisk Drive descriptor 256k (512k only) - /r0
> 
> 		myram_r0_512k.dd
> 		MyRam Ramdisk Drive descriptor 512k (1-2 meg only) - /r0
> 
> *
> 
> The only descriptor needed is mr0.dd. Use dmode and adjust the cyl= to
> control its size which is incremented in 8kdat image blocks. s/b a doc
> file explaining that, someplace.  If not, the readme and the whole
> package is on my web page.  Those descriptors are for "rammer" I
> believe.
> 
> > I will try to put together the same for L1 and the different Coco 1 &
> > 2 models soon, and No, I will not be doing the Dagon trees at the
> > moment as I have no Dragon and know very little about them. If I get
> > froggy and decide to play with XRoar's Dragon emulation, I may do
> > that list too as I know it's a little different.
> > 
> > 
> > Please take a look at the list and see if anything is wrong or needs
> > to be changed and I will make edits.
> > 
> > 
> > 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
> 
> Cheers, Gene Heskett

Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page <http://geneslinuxbox.net:6309/gene>
US V Castleman, SCOTUS, Mar 2014 is grounds for Impeaching SCOTUS

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