I have found various suggestions on handling misbehaving DOS applications on a TSE/MT1.8 server, but there does not seem to be much on what to do with a misbehaving Windows App.
I have a windows terminal emulation program which takes up 49% of CPU time for each instance it's started. So open it twice and the CPU is at 100%.
The tricks for DOS apps does not seem to work with Windows apps. Any one got any suggestions?
Many Thanks
I have a windows terminal emulation program which takes up 49% of CPU time for each instance it's started. So open it twice and the CPU is at 100%.
The tricks for DOS apps does not seem to work with Windows apps. Any one got any suggestions?
Many Thanks