[Coco] How to import source code into NitrOS-9?

[Stephen Pereira]

Hi Bill,

Thanks very much for chiming in.

I am not really inclined to fabricate my own custom OS9Boot file.  As you read, that came about because I was using an incorrect NitrOS-9 boot disk to begin with and I couldn’t get the dw server commands to work properly due to missing modules…

Now that I have discovered that the latest NitrOS-9 boot disk Becker port flavor is the proper boot disk for me to use Drivewire with my CoCo3FPGA to its fullest extent, I am quite happy.  I hope that I will not have to delve into the finer points of constructing a boot disk again in the near future!  I’m happy to have learned a few things, but this is not my main area of interest.

Thanks again.  I appreciate your attention and advice.

smp
--
Stephen M. Pereira
Bedford, NH  03110
KB1SXE


> On Oct 10, 2015, at 8:23 PM, Bill Nobel <b_nobel at hotmail.com> wrote:
> 
> Hey Stephen,  I have been a lurker on this thread.  I think I figured out what your problem is,  the OS9Boot file you mention IS the bootfile.  The command to identify what is in that file use the utility ‘ident’ from the CMDS directory, i.e. ‘ident /dx/os9boot -s’ changing x to the drive where your os9boot file is.  This will produce a list of the system modules merged together to make up the OS9Boot file.  That file is the one you need to edit with any of the boot file editors available, to have it contain what you need.  My favourite is ‘ kwikgen' from Wes Gale.  The core of OS9 is a little trickier to modify.  KRN has extra data outside of itself that map to the very top of RAM for the Reset and IRQ vectors.  Also the boot track must be perfectly padded to achieve boot. 
> 
> As William Astle, in a post in another thread says… “if you actually trace the boot process, it's pretty clear that the original form of OS9 Level II was a hack piled on top of a kludge.”
> 
> Bill Nobel
>