timrha
asked on
NTVDM peaks to 100% CPU utilization with DOS.
I am in a real bind here. The environment I work in is mixed Novell 4.x and Windows NT 4 Server environment.
We are transitioning off of this 16 bit application that communicates with an old Btrieve database that resides on a Novell 4.x server.
We have shortcuts to batch file that launches a DOS app. When the DOS box launches the processor (machines are Compaq Evo 500s 2.4Ghz) pegs out to 100% and the application just sits there. If you open up the task manager you can see the NTVDM.EXE is the process that's eating up all of the processors resources.
We are transitioning off of this 16 bit application that communicates with an old Btrieve database that resides on a Novell 4.x server.
We have shortcuts to batch file that launches a DOS app. When the DOS box launches the processor (machines are Compaq Evo 500s 2.4Ghz) pegs out to 100% and the application just sits there. If you open up the task manager you can see the NTVDM.EXE is the process that's eating up all of the processors resources.
We found that this is not only a WinNT problem but also Win2000. There is a fix existing (NTVDM.EXE at Microsoft)The ntvdm update is mentioned in Microsoft KB article 320694. http://support.microsoft.com/default.aspx?scid=kb;en-us;320694.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
The same Procedure with an old Application from me. Detail shows that its not NTVDM, nor wowexec - its a part of the real Application.
Microsoft told me that error would disappear with SP3 for WIN2K - a Programmer told me to use the NTVDM from the .NET Server.
I´ve tried both without any Result.
Maybe with SP4, or throw away that old Application!
regards Mike
Microsoft told me that error would disappear with SP3 for WIN2K - a Programmer told me to use the NTVDM from the .NET Server.
I´ve tried both without any Result.
Maybe with SP4, or throw away that old Application!
regards Mike
Unless your application is actully malfunctioning, I wouldn't worry about it. Windows can't tell when your DOS program is actually doing something (or not), so it allows the ntvdm to have any spare time i.e. time that would otherwise be idle time. If you start another program e.g. Internet Explorer, then it should run OK, and less time is used by your DOS app.