In message <a0fdd7284e.pnyoung(a)pnyoung.ormail.co.uk>
Dr Peter Young <pnyoung(a)ormail.co.uk> wrote:
If I go back to the old setting in Keystroke, I now get a different
error message, and the computer doesn't lock up. Best demonstrated by
what happens if I shift-drag NetSurf's full filename into a task
Cannot open <Wimp$ScrapDir>.WWW.NetSurf.Log for I/O redirection
This is exactly the message I get with an attempt to run NS the second
time from the incorrect keystroke.
However, even odder:
If I do the same shift-drag into a task window when NS isn't already
running, I get a separate error window from NS saying "Window manager
is already in use".
Should I tell the bug tracker about this?
No, at least not for me. Those error messages are very explainable and
don't mean there is a hidden & serious problem. The first one is because the
output of NetSurf is redirected to the file <Wimp$ScrapDir>.WWW.NetSurf.Log
and when trying to start a 2nd instance of NetSurf, you can't write to
the same file.
And the 2nd one is because you can't start a Wimp task in another Wimp task
(TaskWindow) just like you are doing.
I'm really after a reproducable "UnixLib detected recursion of signal
SIGSEGV." case if there is still such a case.
John Tytgat, in his comfy chair at home BASS
John.Tytgat(a)aaug.net ARM powered, RISC OS driven