I have posted this before with no joy. It "must" be affecting others!
Some of our (and others) programmes appear to either "crash" or "pause" if they are left running for around 30 minutes or more. This is especially apparent in our programmes which have a screen saver feature. The screen saver routine is pretty simple and does some screen writes, keyboard idle loop, and some Novell semaphore checking. It does also occur in some other programmes which while just sitting there also do behind the scenes stuff like keyboard checking. I haven't determined conclusively what happens but sometimes the programmes get "stack overflow" errors, sometimes just lock permanently, sometimes get a network error (DOSEMU still OK), and other times the programmes appear to "freeze" and then magically come back into life after 10+ minutes (and show key presses which had been stored while the programme had "froze"). Some more tidbits :- 1 When the session is "frozen" (temp or perm) DOSEMU debugs of keyboard / network activity etc still go on looking reasonably "normal". 2 When the session is "frozen" and I press a key to do something (eg get out of screen saver or something else) the CPU util in TOP for that DOSEMU session goes up to >90%. Tracing system calls, it repeats a sequence of vm86() calls over and over. 3 I think I have seen the situation whereby if you leave a dosemu session empty for 30 minutes and then try to load a programme it will also freeze. This used to happen with older dosemu versions and now has crept back. While a fix for this behaviour would be good a "fudge" such as putting some kind of dumby key press in the dosemu keyboard source may get around this. This would need to be some kind of innocuous key that doesn't actually do anything except stop the triggering of whatever is causing the problem. Can anyone point me in the direction of what to do here? David
<<attachment: winmail.dat>>
