[Coco] NitrOS-9 sc6551 driver

[Roger Taylor]

At 06:09 PM 4/1/2009, you wrote:
>If you want any hope of loading a driver rather than adding it to 
>the OS9Boot file, you must merge the driver and descriptors into a 
>single file with attributes of e and/or pe. You probably will still 
>get 207 errors on occasion but it should work partially.

I'm aware of merging modules.  I'm beyond the memory error now and 
the drivers are in the boot.

How fun does this sound?  Right now I'm using the Rainbow IDE to 
build an OS-9 floppy image with the 6551 stuff.  I hope to whip up a 
6551 boot module by tonight but I've got a lot more going on so it 
might take several days to get to it.  Since I'm in the 
NitrOS-9/DriveWire environment for these tests (plug to Boisy), I 
just mount the disk as Drive 1 and from NOS type dir /x1 and there's 
my stuff ready to load or use in a new boot disk.  os9asm.exe seems 
to be doing a good job from Windows if I have the right defs files available.

In order to do this I had to get some of the NitrOS-9 source files 
over into my Rainbow project folder, like os9defs, scfdefs, 
boot_common.asm, etc. which were just copied from the SourceForge CVS 
files.  All this development stuff just to write a new boot file in 
luxury. Whew.

The result is that I can now click Go in the IDE and see the files in 
NitrOS-9 pretty much right away.  The only catch is that DriveWire 
keeps a .dsk open so that nothing else can use it, so os9.exe from 
the IDE reports ERROR 214 if you try to build the project/disk again 
while DW3 has the same disk image mounted.  CoCoNet gets around this 
by opening/closing images for every sector, yet it's still blazing 
fast!  I ask of Boisy to at least consider doing this so that the 
Toolshed stuff can write to DW3-mounted disks.  No major problem, 
though.  Just being able to build OS-9 and NitrOS-9 floppies with 
actual content from Windows using Rainbow IDE is cool enough as it is.  ;)

-- 
Roger Taylor

http://www.wordofthedayonline.com