🚀 go-pugleaf

 In article <817314142_OASIS_@bpfd.demon.co.uk>
  steve@bpfd.demon.co.uk (Steve Taylor) said:-

>My (clunky) solution to this was to install "LOW_MEM.PRG" as 
>single-tasking under MagiC, and whenever I want to do any "live" 
>netting I run Low_mem instead of Oasis. However NOS does not then run 
>in a window which would obviously be highly desirable.
>
>I can't say whether it was the single-tasking element or the Low_mem 
>element which "cured" the problem, but I find this the best 
>compromise.

Oasis appears to use a wierd method of invoking NOS. I found the 
command line in Oasis (using Knife-ST) which invokes NOS. It gets 
built wrong under MagiC because it duplicates the drive letter (like 
GG:\OASIS\NOS.TTP) which can be cured. After messing around doing this 
I discovered it still would not invoke NOS (for some other reason) and 
I gave up, preferring to execute NOS directly from Ease.

From this, I would guess that LOW_MEM.PRG cured the fault by building 
a sensible command line rather than it being single tasking which did 
it.

I have two versions of NOS. One is NOS.PRG which single tasks and 
works well. The other is NOS.TTP which runs in a window (same code, 
different extenders).

NOS.TTP does work 95% of the time, momentarily corrupting the screen 
as it starts, and terminates ok. However, it does seem to set off a 
hang or crash "time bomb" which may happen quite soon or ages after.

Btw, it seems quite amazing how many different problems and solutions 
there seem to be - our different desktop programs must be adding 
another layer of complexity to this.


__

Guy Harrison

guy@swampdog.demon.co.uk