[Coco] nitros9 level3

Stephen H. Fischer SFischer1 at Mindspring.com
Mon Oct 15 23:37:08 EDT 2012


Hi,

Gene, could this mutate into a new release of NitrOS-9, one that would be as
good as the OS-9 system I and others had at about the end of Delphi and CIS?

There is a lot of good work that did not make it into NitrOS-9.

Changes could be made and people would need to adapt just like if Tandy
released a new OS-9 Level-II version.

The new Windows I am talking about, four (4) 80 Track 2 Sided disks,
Shellplus restored back to it's glory (Parts just are not in NitrOS-9 that
are part of Shellplus) and so many other thing that I see are missing.

-----------------------

If anyone thinks that this is a good idea, or have items that you would like
to see in a new release, please send an e-mail to:



mailto:SFischer666 at Mindspring.com


Please bear with me, setting up a new mailbox is a Devil of a job. Please
keep trying until I get it right.


If you read this message very late, please respond anyway regardless of
other discussions, I would like to know what others think may not have been
included and should be.

They might be added to my disk of missing parts.

-----------------------

SHF


"Gene Heskett" <gheskett-ouEgS7marmk at public.gmane.org> wrote in message
news:201210131430.37039.gheskett at wdtv.com...
> Greetings all;
>
> Sick of being always out of system ram, I just went into my local 3.2.9b
> repo, and after setting all the path $ env vars in the appropriate
> .bashrc's, made the coco3_6309 .dsk's for level 3.
>
> Then in dw I mounted the single disk version .dsk, and made a new
> /dd/nitros9/L3install directory, and dsaved the whole thing to
> /dd/nitros9/l3install.
>
> It has apparently been 16 years since Alan DeKok last worked on the
> Level3.doc file, and I half expected that somewhere along the line, he or
> someone might have committed some mb scripts in the SCRIPTS directory, and
> some L3.bl's in the BOOTLISTS directory. Sadly, both directories of the
> install are empty. So all I have to go by in composing an L3.bl, is the
> ident -s of a bootfile Alan was using in 1996!
>
> Lots, I dare say at least 1/2 (not counting descriptors of course) of
> nitros9 has now been renamed as its been broken up into smaller modules
> with hopefully less duplication of efforts, so arriving at a compatible
> L3.bl is going to be a confusing and frustrating under taking.
>
> So, the $64k question is, has anyone but Alan ever made this actually
> work?
>
> If so, or if Alan is copying the mail here, it would be appreciated if
> they
> would speak up and offer some guidance as to how best to translate what
> was, into the more modern dialect of a bootlist for 3.2.9.
>
> Secondary silly Q: A fav technique to keep from having to rewrite the
> wheels that make all this work, is to 'dot source' an included file. I
> have in mind if this is possible using shell+, to make a master bl that
> looks like this:
>
> nitro
> . scf.bl (read in the list of scf related modules here)
> end
> . rbf.bl (read in the rbf related modules here)
> end
> . remaining.bl (etc, starting with krnp3, init, yadda yadda)
>
> sort of a list. Is this possible with our shells?
>
> Cheers, Gene




More information about the Coco mailing list