command prompt process not closing

[Lisa]

Hi all,

I have the weirdest problem...I have a webserver running
on windows 2k server, Cold Fusion, and Macromedia
Generator 2. Everytime the generator runs..it runs in a
command prompt, but the process does not close????


I have to manually close all the instances of
NTVDM.exe. Does anyone have any ideas?????

THANKS


..

 

[Bill Stewart]

I have the weirdest problem...I have a webserver running on windows 2k
server, Cold Fusion, and Macromedia Generator 2. Everytime the generator
runs..it runs in a command prompt, but the process does not close????

I have to manually close all the instances of NTVDM.exe. Does anyone
have any ideas?????

Hi Lisa,

Does this happen on one server or more than one server?

Has it always acted like this, or did it just start recently? If recently,
what changed? If it always does this, are you sure you haven't made a
configuration error?

Does the software vendor have any information about this problem?

Bill

 

[Matthias Tacke]

I have the weirdest problem...I have a webserver running
on windows 2k server, Cold Fusion, and Macromedia
Generator 2. Everytime the generator runs..it runs in a
command prompt, but the process does not close????

I have to manually close all the instances of
NTVDM.exe. Does anyone have any ideas?????

May be there is an underlying .pif file were you have to check
close window after terminating?

 

[Guest]

This problem is directly caused by using Macromedia
Generator on Win200k. When the generate.exe is
called...it runs in a command prompt. Win2k leaves the
process open..for every instance of generate.exe. I have
to manually end the process...at this point it is upwards
of 30 instances a day that I am closing.

 

[Bill Stewart]

This problem is directly caused by using Macromedia Generator on Win200k.
When the generate.exe is called...it runs in a command prompt. Win2k
leaves the process open..for every instance of generate.exe. I have to
manually end the process...at this point it is upwards of 30 instances a
day that I am closing.

Is it an actual MS-DOS (real mode) program (highly unlikely), or is it a
Win32 console-mode program (more likely)?

If it's a Win32 console program, why is it starting ntvdm? Is your COMSPEC
environment variable incorrectly pointing to command.com instead of
cmd.exe?