[Coco] Re: Re: Re: Nitros9 Startup Problem

[Robert Gault]

Charlie wrote:

> Boisy,
> 
> Sorry for the double posts, I don't know why they didn't show up till I
> replied from another computer.
> I even refreshed the lists to check, but anyway....
> 
> 
>>In another post that I read this morning, you said that sometimes it
>>doesn't work.  Is that the case?
> 
> 
> Yes, it hangs with no shell. I can press reset on the back of the coco and
> it might or might not work when trying again.
> 
> Also, If any other window is created I am plagued with #184 errors, launched
> from TERM or any other window.
> Say I run smash from term, (the screen is white on all black because of the
> display command in startup) it starts to run, and then errors out with 184,
> and the screen changes colors back to the default black on all green.
> 
> Charlie
> 
> 
> 
> "Boisy G. Pitre" <boisy at boisypitre.com> wrote in
> message news:5EBCA1A2-ED1A-11D8-8FDE-0003939F08E6 at boisypitre.com...
> 
>>On Aug 12, 2004, at 6:13 PM, Charlie wrote:
>>
>>
>>>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.
>>
>>In another post that I read this morning, you said that sometimes it
>>doesn't work.  Is that the case?
>>
>>
>>>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.
>>
>>What window are you forking these programs from when they fail?  Surely
>>not TERM, because all three programs run fine on the V03.02.04 system I
>>test on.
>>
>>I have a suspicion that this problem is a shell+ issue.  Rename
>>cmds/shell to shellplus and cmds/shell_21 to shell, then reboot and try
>>the tests to see how they work.
>>
>>Boisy

Here is more info on this problem. View44 looks for available windows 
using the /w  window name. This procedure will only work when there are 
no windows with type/par set to 1 for vdg windows. The startup script 
you are using convert /w4 into a vdg window type with par=1. This does 
cause view44 to fail an is not a "fault" of NitrOS-9.

There is another method for finding the next available window which is 
much more complex than just using /w. One of the programs which I wrote 
getnw (ie. get next window) uses this method and skips over vdg type 
windows. It involves looking through the system device table and reading 
descriptors to look at window types.

Short of a significant modification to the system so that a call to Open 
a path to /w bypasses vdg types, don't create any vdg windows before 
using view44.