🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: comp.os.os2.apps
Article #5080

Re: DOS program CPU hogs

#5080
From: Joe Stevenson
Date: Fri, 16 Aug 1996 00:00
48 lines
2778 bytes
In message <840211651snx@sectel.com> - David Hough <dave@sectel.com>Fri, 16
Aug 96 09:07:31  GMT writes:
:>
:>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

Another thing you can do is run TAME before running DOS apps.
The reason why DOS apps use up so much CPU power is that
they constant poll the keyboard.  Tame stop the programs polling 
request until that window is in focus (active window), and even 
limits its requests after a certain amount of time of inactive input
activity.  at least this is how I understand it. 
it works.  I belive this is a t hobbes (ftp-os2.nmsu.edu)


JoeS/2  
::Just say NO to Microsoft::
Technical Details
Message-ID: <32145ede.0@news.nni.com>
Path: arc1-ca.pugleaf.net!unknown!not-for-mail
References: <840142188snz@copse.demon.co.uk><840142188snz@copse.demon.co.uk> <840211651snx@sectel.com>

Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 112d6c,e6b7f138a953844
X-Google-Attributes: gid112d6c,public
X-Google-Thread: 104dc3,e6b7f138a953844
X-Google-Attributes: gid104dc3,public
From: sabre@nni.com (Joe Stevenson)
Subject: Re: DOS program CPU hogs
Date: 1996/08/16
Message-ID: <32145ede.0@news.nni.com>
X-Deja-AN: 174526581
references: <840142188snz@copse.demon.co.uk><840142188snz@copse.demon.co.uk> <840211651snx@sectel.com>
content-type: text/plain; charset="iso-8859-1"
mime-version: 1.0
newsgroups: comp.os.os2.apps,demon.ip.support.os2