NoStop said:
From his spyware and virus infected Windoze box, "Lanny Bender" <lambserve
(AT)cox(DOT)net> had this to say:
Why would you care about what bit rate an application is running in,
provided it runs and does the job you want it to do? What's so magical
about 32-bit applications other than the fact they can address more memory
and are generally just more bloatware?
Wesley Vogel pointed me to a KB that answered my question, and apparently
yours as well. I quote from the KB: " 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."
Talk about memory bloat. When you get through running a 16-bit application,
both wowexec.exe and Ntvdm.exe usually stay in memory. Hence, my 2nd
question: "Is there a way to identify all 16-bit applications on my system?"
I just wanted to know when to remove wowexec.exe and Ntvdm.exe from memory.
I usually multitask a lot and frequently I run out of 512MB memory. So I
have to activate Task Manager to see what applications I can delete. I just
wanted to know beforehand what my 16-bit applications were.
Oh well, I guess I have to buy more RAM. BTW, my system STAYS free of
malware.
Lanny