Thanks for the suggestion.

No matter what the pif properties are, when the various programs run,
the system seems to think it is running ntvdm.exe. Therefore if I
change the properties from within a running program, the changes end
up being applied to all of my dos programs which open via shortcut /
pifs.

As an example, I have a shortcut which points to
"C:\WINDOWS\system32\cmd.exe". If I run that shortcut and then click
on properties from the running window, the property page for
:C:\windows\system32\ntvdm.exe" is presented.

I understand that ntvdm is the NT Virtual Dos Machine and apparently
it runs anytime a 16 bit dos program is run. Therefore all of my 16
bit dos programs currently run with the same property settings. If I
change the properties from within a program it is actually changing
the ntvdm properties and applies to future 16 bit programs

On Thu, 5 Jan 2006 14:03:36 -0700, "Wesley Vogel"
<123WVogel955@comcast.net> wrote:

>Type: create a pif in the Search box in Help and Support.