NTVDM is the virtual dos machine for NT. The error typically occurs when running 16 bit application on Windows 2000 or XP when the processor does not have complete support for virtual mode extensions (VME). If your processor is not fully VME compliant, certain combinations of hardware, drivers, memory, and application usage may cause the error.

I have typically seen this when command.com is the wrong version or not available in the dos mode FPD is running in. I would check the shortcut path to your app and also the date/time of command.com and the environment path to it when your app runs as a start. You can also verify the the startup files are set correctly.

Make sure that the default windows items in the Config.NT and Autoexec.NT files exist and are loaded in the correct order:

In Windows XP, CONFIG.NT contains the following default commands:

dos=high, umb
device=%SystemRoot%\system32\himem.sys
files=40

AUTOEXEC.NT contains the following default commands:
@echo off
lh %SystemRoot%\system32\mscdexnt.exe
lh %SystemRoot%\system32\redir
lh %SystemRoot%\system32\dosx
SET BLASTER=A220 I5 D1 P330 T3

Change the config.nt files=40 line to files=100 as a test unless your setting is already higher than that. Also add a buffers=40,8 line just BEFORE The files=100 line for testing purposes.

Just some ideas from past experience. Hope you get it resolved!






>I have a Fox2.5 app running on a Win2k machine. This application parses text files all day every day. There is one particular file which while processing drops out to dos and pops up an NTVDM error box. It is repeatable on several machine for this file. It is happening on a line of code which is select tableName.
>Of the machines on which I have seen this happen, the first is win2k, the second is winxp and the third is win2k with tame dos. The last doesn't bother to popo up the message.
>I have tried making sure all the temp directories are local in the config.fp file, limiting the memory and changing the variable count.
>
>Any ideas?