info about WOWEXEC

  • Thread starter Thread starter dave xnet
  • Start date Start date
D

dave xnet

Hello all,
quick question. How can I find out on behalf of which
task/program ntvdm and wowexec are running?

Thanks,
Dave
 
Hello all,
quick question. How can I find out on behalf of which
task/program ntvdm and wowexec are running?

Thanks,
Dave
Click to expand...

Google


---
avast! Antivirus: Outbound message clean.
Virus Database (VPS): 0606-4, 02/10/2006
Tested on: 2/11/2006 9:41:46 PM
avast! - copyright (c) 1988-2005 ALWIL Software.
http://www.avast.com
 
Google
Click to expand...
well, I know the basics.
I'm aware that the 16 bit tasks are single threaded under this task.
The info I found from MS shows that the running subtask will be found
in Task Manager. In my case it wasn't present.

I had noticed a general slggishness, navigating from screen to screen
and opened the task manager. CPU was not spiking, and I had
a task for ntvdm/wowexec, but no subtask identified.
I assume this to mean that something *had* run but was finished.

I made this post in the hope that some of the experts may have some
further insite. I'm not a usenet newbie. I've assisted many, many
others in the past and present.
Dave
 
dave xnet said:
Hello all,
quick question. How can I find out on behalf of which
task/program ntvdm and wowexec are running?

Thanks,
Dave
Click to expand...


SysInternals' ProcessExplorer
 
[[3. If any 16-bit programs are running, you see an entry for Ntvdm.exe,
which is the virtual DOS machine that is provided by Windows XP. You also
see wowexec.exe (the Windows on Windows subsystem), and the executable name
of each 16-bit program that is running in that WOW virtual machine. As a
helpful visual aid, wowexec.exe and the 16-bit executable file names are
indented. ]]
from...
HOW TO Identify a 16-bit Program in Windows XP
http://support.microsoft.com/?id=320127

However, ntvdm.exe and wowexec.exe will tend to stay open after a 16-bit
program has been closed.

WOW Environment Remains in Memory After Quitting 16-Bit Program
http://support.microsoft.com/kb/181333

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In
 
SysInternals' ProcessExplorer
Click to expand...
Thanks, I had tried that, couldn't find anything - perhaps it's
that 16 bit task had ended, and wowexec.exec just stays open.

Saying that, I think this problem was related to a demo of wavelab 5
I installed. The question arises, however, why is such a recent
release using 16 bit programs?
Dave
 
Back
Top