[Coco] NitrOS9 EOU edition MD ?

L. Curtis Boyle curtisboyle at sasktel.net
Sun Apr 5 01:08:00 EDT 2020


On Apr 4, 2020, at 8:12 PM, coco at jechar.ca wrote:
> 
> 
> I was looking at the modules that make up Nitros EOU.
> 
> ident -s /h0/OS9Boot
> 
> All pretty standard or self explanatory,
> except WHAT's MD why would you need so many V devices and
> why no drive wire support in OS9Boot file?
> 
Ok, to answer each:
1) MD is a development tool device descriptor for monitoring/modifying all of the Coco’s RAM, using any disk editor. It’s more for our internal testing, or for people who are comfortable doing that.

2) That was to allow multiple CoVDG programs to run at once (games, etc.). That will be changing in Beta 5, to be released this month. /Verm will be staying (that’s for level 1 patched program compatibility), but the others (V1-V7) will be removed, and replaced with W8-W15 instead. The new GShell will change /Wxx descriptors to be CoVDG when told to, so they won’t be necessary.

3) That is because neither Bill nor I have had time to get to the drivewire modules yet. There are updated (especially for the 6809 version) Krn, KrnP2 and IOMan all coming in Beta 5. Existing Drivewire from the repository I believe work, but we want to add some improvements to the rest of the operating system before we start adding drivewire, to help make debugging at this stage simpler (Drivewire has so many features and devices that it talks to, that it would be much more difficult to figure out if bugs are in other system modules, or mixed in with Drivewire). We do plan on going through it and putting it in when we finish with the rest of the “Core” NitrOS-9 modules.




More information about the Coco mailing list