[Coco] Ownership of NitOS-9

[Bill Pierce]

Nick... OS9 already does all that... it's done in the "startup" file. To have a program "autostart" on bootup... rename it to 'autoex". Then that program will run on startup automatically...
The screen mode/colors you start with are determined by the default settings of "term" and can be changed to suit you needs... BUT a new boot will have to be made to make it work "all the time". Or you can create scripts in the startup to change them on startup. Most things you can do from the command line, can be done in startup as well. Yes... it's a lot of work but to say a screen should start up in this mode or that when the next person will want the opposite.... So a "standard" black/green screen is chosen then set it up the way you want it. For instance... ALL my Cocos and emulators start up with "term" as black on white and /w1 as white on black and /w2 as green on black. This way I always know what window I'm in and Term is always constant. All my window descriptors have been set to 80 column harware text so when I need an extra window for something, I just type
shell i=/w& (it's in the manual)
and I have a new text window. Most programs that need graphics create them anyway. If not, one command will get me a graphics window of my choice and off I go.
OS9 is not a matter of choices, it's a matter of knowledge. I still read the manuals as often now as I did in the 80s. I have some pages inshrined in plastic... the graphics codes, the key codes etc.
 

Bill Pierce
"Today is a good day... I woke up" - Ritchie Havens
 

My Music from the Tandy/Radio Shack Color Computer 2 & 3
https://sites.google.com/site/dabarnstudio/
Co-Webmaster of The TRS-80 Color Computer Archive
http://www.colorcomputerarchive.com/
Co-Contributor, Co-Editor for CocoPedia
http://www.cocopedia.com/wiki/index.php/Main_Page
E-Mail: ooogalapasooo at aol.com


 
 
-----Original Message-----
From: Nick Marentes <nickma2 at optusnet.com.au>
To: CoCoList for Color Computer Enthusiasts <coco at maltedmedia.com>
Sent: Wed, Nov 5, 2014 4:28 pm
Subject: Re: [Coco] Ownership of NitOS-9


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
https://pairlist5.pair.net/mailman/listinfo/coco