Microsoft OS/2 Version 1.x Entries in the Registry

The Microsoft OS/2 version 1.x subsystem starts whenever a user starts an OS/2 character-based application on an Intel-based computer. The Registry entries for the OS/2 subsystem are found under this key:

HKEY_LOCAL_MACHINE\System
\CurrentControlSet
\Control
\Session Manager
\SubSystems

The OS2 entry in this subkey describes the path to the executable file used to start the OS/2 subsystem. The directory path for the OS/2 library is the Os2LibPath value defined under the Session Manager\Environment subkey.

When Windows NT is installed on a computer, if Setup finds a copy of Config.sys for OS/2, a copy is placed in the Systemroot\System32 directory. This information is used to configure the OS/2 subsystem whenever an OS/2 application is started. If a Config.sys file is not found, a substitute is created in the Registry, with the following values:

PROTSHELL=C:\os2\pmshell.exe c:\os2\os2.ini c:\os2\os2sys.ini
    %Systemroot%\system32\cmd.exe
SET COMSPEC=%Systemroot%\system32\cmd.exe

The OS/2 Config.sys information is stored in the following Registry entry:

HKEY_LOCAL_MACHINE\Software
\Microsoft
\OS/2 Subsystem for NT
\Config.sys

The other subkeys under the OS/2 Subsystem key do not contain entries.

If you subsequently edit the C:\Config.sys file by using a text editor, the LIBPTH=, SET PATH=, and SET WINDIR= entries are appended to the end of the file from the Windows NT environment. Any changes made to the path or environment variables take effect after the system is shut down and restarted.

For details about managing this environment under Windows NT, see Appendix B, "Other Application Environments," in Windows NT Server Concepts and Planning.

You can disable an OS/2 subsystem in Windows NT and still run a bound application under a VDM. Many bound applications run better under a VDM than under the OS/2 subsystem.

To disable the OS/2 subsystem in Windows NT

· In Registry Editor, change the value of GlobalFlag to 20100000 in the following Registry path:

HKEY_LOCAL_MACHINE\System
\CurrentControlSet
\Control
\SessionManager

You can also use Forcedos.exe, a utility supplied with Windows NT in the Systemroot\System32 subdirectory. This enables you to run a bound application under a VDM. To see how to use the Forcedos utility, type forcedos /? at the command prompt.