13th March 2002
We've all been told how 16-bit programs don't work as well in full 32-bit operating systems. For the most part, it's true. But how can you tell, specifically in Windows NT-based OSes, when 16-bit code is running? Pull up the Task Manager whenever you suspect something is wrong. If you see a "WOWEXEC.EXE" process running, you've got some 16-bit code to get rid of. Make note of any programs that you were recently running to track down the culprit. If the utility depends on a VxD, it will not work properly (in Windows 2000 or XP). If you can't live without the 16-bit application, consider running it in a "protected" memory space. Create a shortcut to the EXE, pull up its Properties sheet, flip to the Shortcut tab, press the Advanced button, then place a checkmark in the "Run in separate memory space" option. This should keep it from mingling with any other processes. By now, most of your installed programs should be 32-bit. If not, I'd suggest holding onto Windows 9x and running the older apps in there (instead of Windows 2k/XP). The OS will thank you for it.