Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!uunet!spool.mu.edu!news.cs.indiana.edu!att!pacbell.com!tandem!netcom!ergo
From: ergo@netcom.COM (Isaac Rabinovitch)
Newsgroups: comp.windows.ms
Subject: Re: Windows & Comm programs
Message-ID: <24151@netcom.COM>
Date: 15 Feb 91 08:13:23 GMT
References: <1991Feb13.233743.1@acad3.alaska.edu>
Organization: UESPA
Lines: 16

I've had some of the same trouble with various DOS programs that do a
lot of I/O.  I think the basic problem is that they always look "busy"
to Windows, when all they're doing is waiting for the last input or
output to finish -- so they end up being allocated a bigger share of
the CPU than they need.

Even if my explanation is bogus, my solution seems to work:  lower the
priority of the DOS program.  This is one of the "advanced" options in
the PIF file.
-- 

	ergo@netcom.com 			Isaac Rabinovitch
	netcom!ergo@apple.com			Silicon Valley, CA
	{apple,amdahl,claris}!netcom!ergo

   (specific statement withheld at this time for operational reasons)