Nicholas
April 8th 03, 11:08 PM
Because most Windows 3.x-based programs run properly =20
under Windows XP, it's sometimes difficult to tell 16-bit=20
and 32-bit applications apart. Here are two methods for=20
determining whether an application is 16-bit or 32-bit:=20
right-click the program's executable file and then choose=20
Properties. If you see a Version tab, it's a 32-bit program.=20
Or, if the program is running, press Ctrl+Alt+Del to open=20
Windows Task Manager. On the Processes tab, look in the=20
Image Name column for the name of the program's executable=20
file. If any 16-bit programs are running, you'll find an entry for=20
Ntvdm.exe, the virtual DOS machine. Just above it in the list,=20
you'll see indented entries for Wowexec.exe (the Windows on=20
Windows subsystem) and the executable name of each 16-bit=20
program running in that virtual machine.=20
By default, Windows XP treats each running 16-bit application=20
as a thread within a single virtual machine. If you're running=20
multiple 16-bit applications, they share a common memory space,=20
and a crash in one Windows 3.x-based application will typically=20
bring down all the others with it-causing you to lose any unsaved=20
information in all 16-bit applications. If you regularly run multiple=20
16-bit applications and one of them hangs or crashes frequently,=20
you should run it in a separate memory space. To do so, follow these=20
steps:=20
Create a shortcut to the program, right-click the shortcut icon, and=20
then choose Properties.=20
On the Shortcut tab, click the Advanced button.=20
Select the Run In Separate Memory Space check box.=20
Click OK, and then close all open dialog boxes to apply the change.=20
A program running in separate memory space can't cause problems for =
other=20
16-bit programs running at the same time.=20
Before deciding to run multiple 16-bit applications in separate virtual =
machines,=20
you should weigh the tradeoffs. The downside is that this approach uses =
extra=20
memory. (Windows Task Manager can help you measure the exact differences =
in RAM consumption for each scenario. However, there are several =
benefits, =20
including preemptive multitasking, better responsiveness, and the =
ability to run=20
multiple instances of applications that normally do not allow you to do =
so. In=20
general, this option is best reserved for mission-critical legacy =
applications.
--=20
Nicholas
--------------------------------------------------------------
"Don" > wrote in message: =20
...
| Nicholos sent a reply to me on 4/8 7:45 pm, but it's=20
| contents wouldn't open so it couldn't be read.
| Nicholos, please resend it. Thanks
under Windows XP, it's sometimes difficult to tell 16-bit=20
and 32-bit applications apart. Here are two methods for=20
determining whether an application is 16-bit or 32-bit:=20
right-click the program's executable file and then choose=20
Properties. If you see a Version tab, it's a 32-bit program.=20
Or, if the program is running, press Ctrl+Alt+Del to open=20
Windows Task Manager. On the Processes tab, look in the=20
Image Name column for the name of the program's executable=20
file. If any 16-bit programs are running, you'll find an entry for=20
Ntvdm.exe, the virtual DOS machine. Just above it in the list,=20
you'll see indented entries for Wowexec.exe (the Windows on=20
Windows subsystem) and the executable name of each 16-bit=20
program running in that virtual machine.=20
By default, Windows XP treats each running 16-bit application=20
as a thread within a single virtual machine. If you're running=20
multiple 16-bit applications, they share a common memory space,=20
and a crash in one Windows 3.x-based application will typically=20
bring down all the others with it-causing you to lose any unsaved=20
information in all 16-bit applications. If you regularly run multiple=20
16-bit applications and one of them hangs or crashes frequently,=20
you should run it in a separate memory space. To do so, follow these=20
steps:=20
Create a shortcut to the program, right-click the shortcut icon, and=20
then choose Properties.=20
On the Shortcut tab, click the Advanced button.=20
Select the Run In Separate Memory Space check box.=20
Click OK, and then close all open dialog boxes to apply the change.=20
A program running in separate memory space can't cause problems for =
other=20
16-bit programs running at the same time.=20
Before deciding to run multiple 16-bit applications in separate virtual =
machines,=20
you should weigh the tradeoffs. The downside is that this approach uses =
extra=20
memory. (Windows Task Manager can help you measure the exact differences =
in RAM consumption for each scenario. However, there are several =
benefits, =20
including preemptive multitasking, better responsiveness, and the =
ability to run=20
multiple instances of applications that normally do not allow you to do =
so. In=20
general, this option is best reserved for mission-critical legacy =
applications.
--=20
Nicholas
--------------------------------------------------------------
"Don" > wrote in message: =20
...
| Nicholos sent a reply to me on 4/8 7:45 pm, but it's=20
| contents wouldn't open so it couldn't be read.
| Nicholos, please resend it. Thanks