Kbase 18603: Migration 6.3x to 8.3A Setting OPSYS var on NT for char clnt
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
2/17/1999 |
|
Migration 6.3x to 8.3A Setting OPSYS var on NT for char clnt
DRAFT COPY - Currently under review and edit.
KnowledgeBase Number: 18603
Creation Date: 02/17/1999
Modified Date:
This Document Applies to: Migrating, Migration
OPSYS
WindowsNT
16-bit to 32-bit
Version: 6.x to 8.x conversion
Summary:
Migrating 6.3 to 8.3A - Changing the OPSYS variable on WinNT
So 16-bit Character app continues to work.
Customer will continue to run a character client until the application
can be ported to a 32-bit platform.
Searching for OPSYS, it was not found in the registry. And it could
Not be set a an NT environment variable.
OPSYS defines the OS format i.e. for interpreting path formats etc.
Their goal is to have the system return a path, for example, in MSDOS
style format i.e.\\ in path instead of // in path like UNIX
Step by Step procedure:
An entry can be made to the registry
Open the Registry Editor:
go to -- HKEY_LOCAL_MACHINE
-- software
-- PSC
-- Progress
-- 8.3A
-- WinChar Startup
In this folder are key names - DLC, PROBUILD, etc.
Right click in the Right panel of the editor. The word new appears.
Pointing at the word NEW reveals a menu - Choose String Value
Fill in the word OPSYS in the resulting field ("New Value #1")
Right click on this new entry, OPSYS and choose Modify
In the resulting dialogue box fill in the value MSDOS
Close the Registry Editor.
Reboot the system it will respond appropriately. The V6 application
will now communicate with the system as it did before the upgrade.
References and On-Line Utilities:
* KBase #'s 15666, 16581, 16444, and 16733
* Windows Registry Configuration Editor