[Coco] Ownership of NitOS-9

[L. Curtis Boyle]

Well, technically, Bill and I did get 225 scanlines for 40 and 80 column text screens going - although, we only made it 25 lines, but with an extra scanline between lines (to space the lines out more), which made it much easier to read. the graphics modes did x25 text lines (199 scanlines, which should have been 200, but the GIME didn’t do that properly).
:-p

There were also different versions of REL in the kernal that let you boot up in 32, 40 or 80 columns for the main boot screen. The TERM device descriptor in your OS9/NitrOS9 boot determines what mode the first actually running shell comes up in, which you can make any size/colors you want.

Autoexec is already in there, unless someone has removed that functionality of the years since I last worked on it. It was part of CC3Go, in stock OS-9 and Nitros9 (rename any executable to “autoex” and it would run automatically).

We had started some research into getting the 225 line graphics modes working (by mapping another 8K block into GrfDrv’s MMU map), but we never did finish that before we ended up not having time to develop NitrOS9 anymore.

L. Curtis Boyle
curtisboyle at sasktel.net



> On Nov 5, 2014, at 3:28 PM, Nick Marentes <nickma2 at optusnet.com.au> wrote:
> 
> On 6/11/2014 7:12 AM, Darren A wrote:
>> On Wed, Nov 5, 2014 at 1:24 PM, Nick Marentes <nickma2 at optusnet.com.au>
>> wrote:
>> 
>>  <snip>
>>> Right from the get up and go, I 've run into problems regarding /d0 /sd0
>>> (I'm using the SDC build). I was following the manuals starting at chapter
>>> 1 and found that both /d0 and /sd0 access the same directories and I was
>>> wondering why, after a few directory reads, I kept getting ERROR #247 and
>>> couldn't read any drive.
>>> 
>>> I have since learned that I should only be using /sd0 (an LBA device) and
>>> that /d0 should not have even read the /sd0 device.
>>> 
>>> This is using the SDC build of NitOS-9 and is a problem of a "bug" in this
>>> version and a lack of documentation.
>>> 
>> 
>> 
>> It sounds like a firmware update for the CoCo SDC is needed. I guess a
>> mechanism should be added to allow the OS9 driver to lock out the
>> controller's floppy emulation capability so that /d0 and /d1 aren't
>> recognized.
>> 
>> Darren
>> 
> 
> No! Can you make them both work?
> 
> I find that I need to mount the /sd0 and be able to access a normal dsk image in the second drive.
> 
> I copy things from /d1 to /sd0.
> 
> Or am I doing this wrong?
> 
> I want to eventually copy the files off my standard MultiVue 40 track DSK to the /SD0. Or does this use /SD1?
> 
> If your planning an update, how about the ability to set a startup video mode and colorset (Width 80/40)?
> 
> What about an AUTOEXEC feature on startup (run a predefined program on start).
> 
> And if you're really game... add a command switch between 225 and 192 scanlines (40/80x27 text, 320/640x225 graphics).
> 
> (See what happens when you give me an inch? I take a mile!)
> 
> Nick
> 
> 
> 
> -- 
> Coco mailing list
> Coco at maltedmedia.com <mailto:Coco at maltedmedia.com>
> https://pairlist5.pair.net/mailman/listinfo/coco <https://pairlist5.pair.net/mailman/listinfo/coco>