🚀 go-pugleaf

In article <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?
>
The quick fix is to upgrade to the OS/2-specific port of KA9Q, available 
on ftp.demon.co.uk/pub/os2/netos2.

For DOS programs in general, open the settings notebook and go to the 
DOS settings screen. Somewhere on there you will find the 
IDLE_SENSITIVITY, which defaults to 75. I have found quite a few DOS 
programs (including this text editor) which really hog the CPU at that 
setting. Turn it down to 10 or 20 and things will improve. Running the 
pulse.exe CPU monitor is useful for checking this - it will show when 
something is taking all the CPU time and you can usually work out which 
program it is by simple elimination. As a guide, many of the problem DOS 
programs use a mouse.....

Dave
--
djh@sectel.com
Tel +44 1285 655 766
Fax +44 1285 655 595