Date:	Wed, 3 Nov 1999 09:56:24 +0200 (IST)
From:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender:	eliz AT is
To:	Francisco Pastor Gomis <Francisco DOT Pastor AT uv DOT es>
cc:	djgpp AT delorie DOT com
Subject:	Re: __dpmi_yield and WinNT
In-Reply-To:	<7vm851$pp6$1@talia.mad.ttd.net>
Message-ID:	<Pine.SUN.3.91.991103095558.29562H-100000@is>
MIME-Version:	1.0
Reply-To:	djgpp AT delorie DOT com
X-Mailing-List:	djgpp AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

On Tue, 2 Nov 1999, Francisco Pastor Gomis wrote:

> __dpmi_yield seems like well in OK in Win98, but in WinNt, when I run may
> program in a DOS command window, it appear a process called NTVDM that spend
> all the CPU (not the procees related to the command prompt that spend no CPU
> time in the NT Task Manager).

Does this mean that the Task Manager shows 100% CPU used during this
time?

> When the program is in backgroud, I feel that the system run slowly.
> 
> >Which version of NT do you have installed?
> 
> My version is Win NT 4.01, Service Pack 5.

I tested this on NT 4SP3, and the Task Manager shows a negligible
amount of CPU used when programs like Less and Info wait for a user to
type something.  Both of these programs call __dpmi_yield in their
idle loop.

Are you sure you call __dpmi_yield correctly?  Perhaps it is
worthwhile to try Less and/or Info on your NT system: if they, too,
cause 100% of CPU time to be used, then this is something specific
either to your version of NT or to its configuration.

- Raw text -