🚀 go-pugleaf

In <840142188snz@copse.demon.co.uk>, Eoin Woods <Eoin@copse.demon.co.uk> writes:
>I am having a few "interesting" times with a DOS program which I use (under
>Warp) to connect to my ISP (it's a bundle of software based on KA9Q for those
>interested).
>
>The program is a *terrible* CPU hog - when it is running it takes more and
>more of the CPU until the rest of the system is crawling along.  Is there
>a way of limiting a DOS program's share of the CPU under OS/2?  All the stuff
>I've read is about giving DOS programs MORE - my problem is the opposite! I 
>understand that given OS/2's CPU scheduling algorithm the more CPU something
>asks for, the more (over time) it will be given.  Is there a way of putting
>an upper bound on it?
>
>A secondary question is about stability.  Now and again (usually when the
>phone line is hung up abruptly) this program gets in a tangle and corrupts
>some internal data structures.  Usually this causes a trap and OS/2 stops
>the program (as you would expect).  A few days ago, this happened again, and
>the program froze OS/2 SOLID! (No Ctl-Alt-Del or Ctl-Alt-W to WatchCat 
>possible).  How can this happen?  I've had LOTS of system hangups and freezes
>when running MS Office programs in seamless mode (Word6 being the prime
>culprit) - but a DOS program??  Is there something terribly wrong with my
>system?
>
>If a DOS program can (1) Hog the CPU and (2) Hang OS/2 solid, this doesn't
>say much for the OS/2 crash protection!  My GOOD experiences with it over
>the last few years suggest otherwise - which is why I'm after some advice
>as to anything I may have done to destabilise it!

I'm not the type who can answer your question from a technical standpoint, but 
I don't believe that this app you describe debunks the notion of crash protection. 
There are *always* programs which can cause trouble for a system (ANY system, 
as I have seen written in the newsgroups).  You already commented on how many 
times OS/2 Has saved your skin . . .  

Without any knowledge regarding the app, I can only say what makes sense to me - 
shoot the program and go native!  Why stick with something which is lousy??

Kenward