[Coco] Re: Re: Nitros9 Startup Problem

[Charlie]

Hi. Boisy.

I tried the script as you posted and it works great. I get the 3, 80 collum
windows and a VDG window just like I want.

However, there is still the issue of getting the error #184.
View 4.4 gives this error.
The game Smash gets this error. Thexder the screen clears and returns to the
shell prompt.
Like I said in another post if I boot Nitros9 with ONLY a Term window
everything seems to work fine.

Is this a confirmed problem or is it something I'm missing?

Thank you for your help and patience.

And Thank you also Robert, (if you read this) for the suggestions.

Charlie

"Boisy G. Pitre" <boisy at boisypitre.com> wrote in
message news:BDCCF000-EC63-11D8-8FDE-0003939F08E6 at boisypitre.com...
>
> On Aug 11, 2004, at 11:22 PM, Robert Gault wrote:
>
> > Charlie wrote:
> >> I left out a line in the startup file.
> >> link shell
> >> load ultipak 1
> >> wcreate /w2 -s=2 0 0 80 24 00 02 02
> >> shell i=/w2&
> >> wcreate /w3 -s=2 0 0 80 24 00 02 03
> >> shell i=/w3&
> >> xmode /w4 par=1
> >> shell i=/w4&
> >> merge /d0/sys/stdfonts
> >> merge /d0/sys/stdpats_2
> >> merge /d0/sys/stdpats_4
> >> merge /d0/sys/stdpats_16
> >> merge /d0/sys/stdptrs
> >> display 1b 32 0 11 33 2 1b 34 2 c
> >> this makes the system lock up as I said earlier.
> > ><snip>
> >
> > There are several problems with your startup file. Starting with the
> > simplest and going to the hardest:
> >
> > current                         correct or better/works
> > xmode /w4 par=1                  xmode  /w4 pau=1
> > display 1b 32 0 11 33 2 1b 34 2 c  display 1b 32 0 1b 33 2 1b 34 2
>
> Actually the xmode /w4 par=1 is correct.  I believe Charlie is trying
> to create a VDG window in /w4.
>
> The display command is incorrect.
>
> Charlie, I tried your problem script file.  It behaves the same way on
> my computer (I take issue with your use of the term "lock up" which
> implies a solid crash.  The CoCo 3 doesn't crash; you can still hit the
> CLEAR key and switch windows, except there is no shell and you can't
> type any commands).
>
> I've traced the problem to a issue with shell+ and how grfint and
> windint handle window I/O.  I'm not sure why it's a problem at the
> moment.
>
> Here's an altered version of your original startup script, with
> Robert's recommendations, as well as my own:
>
>
> link shell
> load utilpak1
> wcreate -z
> /w2 -s=2 0 0 80 24 0 2 2
> /w3 -s=2 0 0 80 24 0 2 3
>
> display c>/w2
> display c>/w3
> shell i=/w2&
> shell i=/w3&
> xmode /w4 par=1
> shell i=/w4&
> chd sys
> merge stdfonts stdptrs stdpats_2 stdpats_4 stdpats_16
> display 1b 32 0 1b 33 2 1b 34 2 c
>
> Notice the display c commands sent to /w2 and /w3.  Just this single
> byte of output to the window appears to abate the problem.
>
> Also, the blank line after the second wcreate command is important.
> This tells wcreate (which is running at that point) to stop.
>
> Try this and let us know.
>
> Boisy
>
>
>
>
> > many merge statements
> >                    chd sys
> >                    merge stdfonts stdptrs stdpats_2 stdpats_4
> > stdpats_16
> > multiple wcreate statements in file
> >                                  wcreate -z
> >                                  /w2 -s=2 0 0 80 24 0 2 2
> >                                  /w3 -s=2 0 0 80 24 0 2 3
> >
> >                                  * The above blank line is needed
> >                                  shell i=/w2&
> >                                  shell i=/w3&
> >
> > If you don't like wcreate which is quirky, just use
> > display 1b 20 ... >/w#
> >
> >
> > -- 
> > Coco mailing list
> > Coco at maltedmedia.com
> > http://five.pairlist.net/mailman/listinfo/coco
> >
>
>
> -- 
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco
>