[Coco] Nitros9 v3.3.0

Fri May 9 00:36:52 EDT 2014

I agree,  Myself and Curtis created this, so it’s a matter of finding the right combo.

 I tried new krn & krnp2 with old boot and I see it may be krn under v3.3.0 that is causing issue.  For now I will use old boot track and 3.3.0 boot and live with it, but still curious.

Bill Nobel

On May 8, 2014, at 10:27 PM, CoCoList for Color Computer Enthusiasts <coco at maltedmedia.com> wrote:

> On Friday 09 May 2014 00:17:49 CoCoList for Color Computer Enthusiasts did 
> opine
> And Gene did reply:
>>  I noticed that Gene, but I’ve tried different combos of the old to
>> new boottrack and find it’s either boot or krn that cause the issue. 
>> REL loads and performs fine, boot or krn seem to be problem.  Old boot
>> and krn work fine. New boot & krn slow down and the “.” go forever.
> 
> krn has had some functions moved in and out, trading places with things in 
> krn2.  Your combination could be something doubled, missing or both.  
> Basically, the krn you use should come from the 3.3.0 kit so they match 
> each other.
> 
> That may not be it Bill, but its a thought.  In any event, I'm headed for 
> the rack & some zz's.  Good luck, I am sure you will find it.
> 
>> Bill Nobel
>> 
>> On May 8, 2014, at 9:57 PM, CoCoList for Color Computer Enthusiasts 
> <coco at maltedmedia.com> wrote:
>>> On Thursday 08 May 2014 23:22:26 CoCoList for Color Computer
>>> Enthusiasts did opine
>>> 
>>> And Gene did reply:
>>>> Ok new question for Nitros9 under Mess.  I have v3.3.0 of Nitros9
>>>> 
>>>> 6309.  I have a problem writing the boot track for it.  OS9Boot file
>>>> is fully 3.3.0, but when I use the new REL, BOOT & KRN I lose the
>>>> boot load.  REL keeps showing “.” forever.
>>> 
>>> There are several versions of the boot module, each for the specific
>>> disk controller.  There are also several versions of REL, each
>>> expecting a different Term format.  Things can easily go all aglay
>>> if they are miss- matched.  For instance, for the TC^3 controller,
>>> there are 3 bytes immediately in front of the modules crc that need
>>> to be fixed to match the address of the controller since it has at
>>> least 2, and the MPI slot it lives in, see the docs for scsidesc.asm
>>> which may shed some illumination on that.  Other controllers that I
>>> don't have, may have similar idiosynchrocy's but I'm not an expert
>>> on them.
>>> 
>>>> Is it my Mess emulator (which is messmenu under mac), or did
>>>> 
>>>> something change in BOOT from previous version?
>>> 
>>> That boot may be yet another variation.  I have a b09 utility on my
>>> web site, "KRNL2DIR" that will make a root directory entry pointing
>>> at the kernel track.  Satisfies dcheck too.
>>> 
>>> Once that is done, my "vfy", also on my web page, can split the track
>>> up into its individual modules PLUS the RSBASIC header, and the
>>> trailing list of IRQ vectors, making 5 files it will make, using the
>>> -sk syntax.  From those boot and rel modules, you can then edit the
>>> MB script to use those, and that should get you a working boot.
>>> 
>>> Good luck, and I hope I've been helpful.
>>> 
>>>> I have the kernel track under old version and things work fine with
>>>> new OS9BOOT file, but am curious if anybody else has this issue?
>>>> 
>>>> Bill Nobel
>>>> 
>>>> 
>>>> --
>>>> Coco mailing list
>>>> Coco at maltedmedia.com
>>>> http://five.pairlist.net/mailman/listinfo/coco
>>> 
>>> Cheers, Gene
>> 
>> --
>> Coco mailing list
>> Coco at maltedmedia.com
>> http://five.pairlist.net/mailman/listinfo/coco
> 
> 
> Cheers, Gene
> -- 
> "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
> http://five.pairlist.net/mailman/listinfo/coco