There's more going on here than what meets the eye. First, Ed was correct in saying that NTVDM.EXE is a Virtual DOS Machine, specifically for 16 bit DOS applications. NT handles them differently than a true 32 bit apps because they expect direct access to hardware. That is not possible under NT. That is why NT has NTVDM.EXE and in addition to that, WOWEXEC.EXE (for Windows On Windows) for 16 bit Windows Apps. Is what is happening is this 16 bit app is either looking for a DOS version or has some flaky code or possibly an old dll file. Regardless, more information is required to troubleshoot your problem.

Hope that explains the NTVDM.EXE though. :-) Good Luck



>>>Problems with NT
>>>
>>>If i start a program example setup.exe
>>>
>>>The program will not startup
>>>If i look into the Taskmanager
>>>NTVDM.EXE takes 100 % CPU time
>>>
>>>Does someone know how to solve this
>>
>>NTVDM creates a Virtual DOS machine; there are a number of things, such as a lack of memory or corrupted files that can cause NTVDM to hang.
>>
>>First, does this only happen when running a DOS .EXE or Win16 application?
>>
>>Second, what do you have in the machine for memory resources; both physical RAM and swap file space?
>>
>>Third, what other applications are running at the same time?
>
>The problem is solved
>it was caused by long path setting in the evironment
>
>i also set extra statement in the config.nt
>
>shell=%systemroot%\system32\command /e:2048
>
>kind regards
>
>Jan