[Coco] My Windows Readme

Luis Antoniosi (CoCoDemus) retrocanada76 at gmail.com
Fri Apr 3 08:28:39 EDT 2015


Which manual ?

[Getting_Started_with_NitrOS-9]
[The_NitrOS-9_Windowing_System]
[NitrOS-9_Commands_Reference]
[NitrOS-9_Level_2_Development_System]
[NitrOS-9_Technical_Reference]
[The_NitrOS-9_Boot_Process_Explained]

??

Luis Felipe Antoniosi



On Thu, Apr 2, 2015 at 10:04 PM, Bob Devries <devries.bob at gmail.com> wrote:

> Luis,
>
> would you PLEASE read section 3 of the OS-9 manual (pages 3-1ff)
>
> Although not specifically mentioned, you can use <>>>.1 I believe you can
> also create a window by using /W. It grabs the next available window
> descriptor.
>
> If all else fails, RTFM !
>
> Regards, Bob Devries
> Dalby, QLD, Australia
>
>
>
>
> On 3/04/2015 11:58 AM, Luis Antoniosi (CoCoDemus) wrote:
>
>> For example, I made a cp/m emulator and I want to prepare some disks. Some
>> applications need kaypro_ii terminal others vt-52, so I need -k or -v
>> option. In order to avoid confusion I wan to make the disks with a run
>> script on its root. I gave up taking the current directory. No one could
>> give me a direction on that. Then my run script for wordstar would be:
>>
>> path=/d0/cmds /d1/cmds /d2/cmds
>> cpm -k ws.com
>>
>> My problem: This thing won't work because CP/M won't receive my keyboard,
>> it loads and then hangs. I need to redirect the /term to it and I don't
>> know how to do it. But what if the user runs it from /w7 for example ? Or
>> /term ?
>>
>> I don't want to make ML programs for each separate pack. this is
>> ridiculous. If so, the os-9 scripting is pure garbage. Yeah, getting
>> pissed
>> off it now....why people tell me there is no problem here ? What I didn't
>> get about OS-9 ?
>>
>>
>>
>>
>>
>>
>>
>> Luis Felipe Antoniosi
>>
>>
>>
>> On Thu, Apr 2, 2015 at 8:31 PM, Stephen H. Fischer <
>> SFischer1 at mindspring.com
>>
>>> wrote:
>>>
>>
>>       This set of sources will build the following set of windows.
>>>
>>>      Please note that the Tvdg, V1, V2, V3 and V4 files produce
>>>      a set of device descriptors that will not match the TANDY
>>>      ones. Either someone has been very sloppy or something strange
>>>      is going on. Tvdg has been tried, but not V1-V4.
>>>
>>>      As the source is here, you can change the colors to your liking.
>>>      Suggest that Window_Com be studied before any changes.
>>>
>>>      9           TERM -  (80 x 25) White   on Blue    with Blue    Border
>>>      0           W1   -  (80 x 25) White   on Blue    with Green   Border
>>>      /           W2   -  (80 x 25) White   on Blue    with Yellow  Border
>>>      1           W3   -  (80 x 25) White   on Blue    with Cyan    Border
>>>      1           W4   -  (40 x 25) White   on Blue    with Red     Border
>>>      /           W5   -  (80 x 25) White   on Blue    with Black   Border
>>>      2           W6   -  (80 x 25) White   on Blue    with Magenta Border
>>>      9           W7   -  (80 x 25) White   on Blue    with White   Border
>>>                  W8   -  (40 x 25) White   on Blue    with White   Border
>>>                  W9   -  (40 x 12) Black   on Green   with -W14-   Border
>>>                  W10  -  (80 x 12) Black   on Cyan    with Red     Border
>>>                  W11  -  (80 x 12) Blue    on White   with -W10-   Border
>>>                  W12  -  (40 x 13) Blue    on Yellow  with -W10-   Border
>>>                  W13  -  (40 x 13) White   on Magenta with W10-W14 Border
>>>                  W14  -  (40 x 25) Yellow  on Blue    with Cyan    Border
>>>                  W15  -  (40 x 25) Black   on White   with -W14-   Border
>>>
>>>    ***************   *****************   ****************
>>> *****************
>>>    *             *   *               *   *       *      *  *       *
>>>    *
>>>    *     W10     *   *      W10      *   *       *  W9  *  *       *
>>>    *
>>>    *             *   *               *   *       *      *  *       *
>>>    *
>>>    ***************   *****************   *  W14  ********  *  W14  *
>>> W15  *
>>>    *             *   *       *       *   *       *      *  *       *
>>>    *
>>>    *     W11     *   *  W12  *  W13  *   *       * W13  *  *       *
>>>    *
>>>    *             *   *       *       *   *       *      *  *       *
>>>    *
>>>    ***************   *****************   ****************
>>> *****************
>>>
>>>      NOTE! Window  W11      must be started from W10.
>>>            Windows W12      must be started from W10.
>>>            Window  W13      can  be started from either W10 or W14.
>>>            Window  W9       must be started from W14.
>>>            Window  W15      must be started from W14.
>>>
>>>
>>> I hope this post looks right, finally it does for me at least. (The
>>> Courier New monospaced font.)
>>>
>>>
>>> This is the readme for the OS-9 Windows I created.
>>>
>>> Looking at the makefile NitrOS-9 Shellplus will not allow asm of the
>>> source due to the file append bug I reported again today.
>>>
>>> If someone wishes to try, I can supply the asm source and the makefile.
>>> (SHF97, 80T 2S DNS=3)
>>>
>>> It appears that I did not allow for four (4) windows on the same screen.
>>> (I ran out of Windows Numbers.)
>>>
>>>
>>> SHF
>>>
>>>
>>>
>>> --
>>> Coco mailing list
>>> Coco at maltedmedia.com
>>> https://pairlist5.pair.net/mailman/listinfo/coco
>>>
>>>
>>
> --
> Coco mailing list
> Coco at maltedmedia.com
> https://pairlist5.pair.net/mailman/listinfo/coco
>


More information about the Coco mailing list