xpe ntvdm.exe 100% processor use

[alex]

i want to run on clipper aplicattion and the use cpu it´s 100% . It´s
possible one solution for this?, Regard, Alejandro Ludeña

 

[KM]

alex,

I am not sure what your question is about.
Do you see the same behavior if you run your app under XP Pro?

The 100% CPU usage is fairly common with 16-bit programs (ntvdm) under NT/2K/XP. Normally it results from a program sitting in a
loop and polling the keyboard. In fact it may not be using or needing the CPU time but because it preempts the 'idle process' it is
seen as using all the processor time.

 

[alex]

Yes in XP Pro it´s the same problem. Yesterday looking in the web i
found one program called tamedos. With this program don´t charge the
ntvdm and the procesor use it´s normal. But with ntvdm it´s possible
configure for processor use normally time?, Regards, Alex

 

[KM]

Alex,

I don't understand your question.
If it is the app problem and easy to repro on XP Pro, you should first fix the app. There is no issues with XPe for you yet.

You can use tools like Task Manager or Process Explorer (http://www.sysinternals.com/ntw2k/freeware/procexp.shtml) to change a
process priority on the fly.

If you are a programmer and can change the app code, use APIS like SetPriorityClass to lower the priority class for the process.

 

[alex]

i want to run on clipper aplicattion and the use cpu it´s 100% . It´s
possible one solution for this?, Regard, Alejandro Ludeña

Yes in XP Pro it´s the same problem. Yesterday looking in the web i
found one program called tamedos. With this program don´t charge the
ntvdm and the procesor use it´s normal. But with ntvdm it´s possible
configure for processor use normally time?, Regards, Alex

 

[alex]

The problem it´s not only in this aplication . For example with qpw
5.0 application windows but 16 bits, or wordperfect 6 (16 bits it´s
the same problem. Always the cpu work at 100% . In www.temedos.com say
that this problem it´s from NT 4.0.

Regards, Alex

 

[KM]

alex,

I guess it is www.tamedos.com as you corrected the link on the next post (btw, why creating one more thread?).
Did you try there trial version? I wonder how it helps with ntvdm.

Unless you plan to do your own version of the fix, or you plan to integrate the Tame into your XPe image, I don't see how this all
relates to the XPe itself?
Remember that XPe is based on XP Pro binaries and your problem is easy to repro on XP (and, btw, very known for a while on NT
branch). So, when you fix this on XP Pro, you can get the fix and integrate it in to your XPe images.