MKWINOS/2 Readme

1. Introduction
MKWINOS/2 is a commercial OS/2 program that creates the equivalent of your Windows Program Manager as an OS/2 Desktop folder named "Program Manager Desktop Equivalent". Your Windows groups and the program entities within each group are used to create OS/2 folders and program objects respectively within the Program Manager Desktop Equivalent folder. MKWINOS/2 is equally effective with OS/2 Warp or OS/2 2.1 and 2.11.

The MKWINOS/2 main program (MKWINOS2.CMD) creates a REXX program (MKWINRUN.CMD) which you run to build the OS/2 objects. You can alter the contents of MKWINRUN.CMD and the program can be rerun as desired.

Each OS/2 folder (the Desktop folder along with the group folders) will be the same size and in the same relative screen position as they exist on your full screen Windows display. The OS/2 folders created from the Windows program groups will contain the same Windows and DOS programs as the originals. Each program is setup as a Win-OS/2 object.

<-- Windows   MKWINOS/2 -->

Each program object created by MKWINOS/2 uses the default settings you have established with the WIN-OS/2 Setup option found in your OS/2 System Setup settings notebook. MKWINOS/2 then adjusts these settings for the particular program with the settings found in MKWINOS2.DBX (an updated version of the DATABASE.TXT file provided with OS/2).

1.1 OS/2 OS/2 Warp Blue Box vs. Red Box and MKWINOS/2
If you have OS/2 for Windows or OS/2 Warp (Red box) then MKWINOS/2 creates OS/2 Desktop objects to mirror your Windows Program Manager - nothing in your Windows directory is altered.MKWINOS/2 performs additional functions for OS/2 full pack (FP) systems (including Warp "Blue box", Warp Connect, Warp Server, OS/2 2.1, and 2.11) with WIN-OS2 support. Control information and files from your Windows configuration is "merged" into the OS/2 \WINOS2 files and directories. Hence, the program MKWINBAK.CMD is provided to create a backup repository of your \WINOS2 directory and all subordinate directories. A procedural .CMD file (R-WINOS2.CMD) is dynamically created to allow restoration of the WINOS2 files and directories in the event that it is necessary.

1.2 How MKWINOS/2 differs from Warp's Add Programs
MKWINOS/2 is significantly different from the Add Programs (or OS/2 2.1 Migrate Programs) facility in OS/2 since it creates program objects for just those applications that you had setup under Windows. MKWINOS/2 maintains the "look and feel" of your Windows Program Manager. MKWINOS/2 does not search your drives looking for possible candidates.Add Programs will either put all of the Windows group and program entries into a single folder or ask you to select the entries you want added to your Desktop on a program-by-program basis. The appearance of your Windows Program Manager is lost. Since Add Programs selects programs by their name, it will include all copies of a Windows program it finds, regardless of it being a backup or archive copy or a needed, running copy. These unnecessary objects which are created as a result of running Add Programs add additional burden to the OS/2 .INI files - a result that can effect overall system performance including that of native OS/2 applications and the operating system itself.MKWINOS/2 uses the value of the system WIN-OS2 default settings by merging those settings with any settings it uses that are specific to that program. On the other hand, Add Programs ignores the WIN-OS2 setup values.Any Windows groups and programs that Add Programs processes that contain errors (bad paths, non-existent .EXE files, etc.) result in the entire group being ignored with nothing more than a meaningless error message, "MIGRATE ERROR: Items in GROUP file damaged." being written to a file (\OS2\INSTALL\MIGRATE.LOG) or, in some instances, a folder with a meaningless name being created. MKWINOS/2 will create an object as best it can and identify that object as being in error. In addition, the error condition is recorded as part of the MKWINOS/2 report file.Any previously created OS/2 Windows-related objects remain unchanged and can be removed at your discretion. Beyond simply creating OS/2 objects, MKWINOS/2 merges Windows files and properties into WINOS2 on an OS/2 fullpack system. The backup facility described above is provided to allow restoration of the WINOS2 files and directories in the event that it is necessary.

1.3 Additional MKWINOS/2 functions
Windows group folders that are open when MKWINOS/2 is run receive special attention on Warp. An option is provided at the end of MKWINRUN to shadow these folder and program objects to the OS/2 Startup folder. A positive user reply is required to add these objects to the OS/2 Startup folder; they are also immediately opened on the OS/2 system. In either case, the Program Manager Desktop Equivalent folder is opened when MKWINRUN completes.MKWINOS/2 has an optional debugging log facility. The debugging facility is enabled for the initial release of MKWINOS/2. In subsequent releases this debugging facility would be activated by the presence of either -d or /d on the command line. Enabling the debugging facility, intended primarily for support use, results in the file MKWINOS2.LOG being created. Previous MKWINOS2.LOG files are overwritten.

2. Installation & Execution
If you downloaded this program from a software repository the program is a demo version, not Shareware, that has been restricted to processing a limited number of Windows group folders. Only the programs within the Accessories group, the Main group, and the Startup group will be processed by the un-enabled, demo version. MKWINOS/2 processes all of the programs in all of the groups when the demo version is enabled with a key. The details for obtaining the key to enable the program appear later in this readme.htm file.

If you received an enabled copy, the .ZIP file contains the file MKWINOS2.KEY created just for you, Please do not pass this file or its contents on to others as you will be depriving not only the program's authors but the sales, distribution, and support organizations of their due revenue.

In either case, simply unzip the .ZIP file you received into its own directory (the suggested directory name is MKWIN). Either the DOS PKUNZIP or OS/2 UNZIP may be used to decompress the file. There is no restriction on where this directory resides. After the distribution file is unzipped, the program is ready to run. The program name is MKWINOS2 and it can be run from a full screen or windowed OS/2 command line session with the MKWIN (or directory of your choice) as the current directory. No changes are necessary to any files or other components on your system. (This assumes you have the current directory indication, ".;", in your LIBPATH statement.)

Running MKWINOS2 creates a REXX program file named MKWINRUN.CMD in the same directory where MKWINOS2.CMD exists. MKWINRUN is the program you run to actually build the Windows equivalent objects. MKWINRUN may be altered and re-run as frequently as desired. However, we don't anticipate that most users will want to change the MKWINRUN program.

The subject Windows system defaults to the Windows directory used by your OS/2 System. With OS/2 Red box (OS/2 2.1 for Windows), this is your actual Microsoft Windows directory. The subject Windows system for OS/2 Blue box (OS/2 2.1 Full Pack), is the ?:\OS2\MDOS\WINOS2 directory.

There are two ways of altering the pointer to the default Windows directory. If you have an enabled version of MKWINOS/2, you already have a file named MKWINOS2.KEY. If you are running the demo version, it will be necessary for you to create an ASCII text file called MKWINOS2.KEY in the MKWIN directory. MKWINOS/2 checks the first line of this file to see if it contains an enabling key, if you have one. All other data within this file is structured in a key word=value format and the position within the file, case, and white space is irrelevant. To specify a specific Windows directory for MKWINOS/2, add the line: Windows=path where path is the drive letter and path of the directory that contains the Windows PROGMAN.INI file. Generally, this line will be: Windows=c:\windows The other means of specifying an alternate Windows directory is by including it as a command line parameter when you run MKWINOS/2. For example: mkwinos2 c:\windows The command line specification overrides any Windows path stored in the MKWINOS2.KEY file.

2.1 Quick Start Summary
1) Unzip MKWINOS/2 .ZIP file into a directory of your choice - MKWIN suggested. The .ZIP file name is MKWINOS2.ZIP (or MKWINnnn.ZIP for beta or other interim releases).

2) If you are running a Full Pack version of OS/2 (original OS/2 2.1 or Warp Blue box - including Connect and Server), run MKWINBAK to create a backup of the subdirectories and contents your \OS2\MDOS\WINOS2 directory. (This step is not necessary for OS/2 warp Red box or OS/2 2.1 for Windows since there are no \OS2\MDOS\WINOS2 files to concern yourself with.)

3) If you have an enabling key, create the file MKWINOS2.KEY in the MKWIN directory with the key value as the first or only line of this file. White space and case is irrelevant.

4) Run MKWINOS2 to build MKWINRUN.CMD. If you are running a Full Pack system, specify the path to your \WINDOWS directory on the command line. Alternately, you can add the line: '''. This 6 character value includes a two digit value representing the relative group number with the Desktop folder being group 00, two digits representing the relative program number within the group (group entries contain 00), and a two digit sequential number. This style was carefully chosen to provide a user not familiar with REXX an intuitive means of generally identifying the contents of the MKWINRUN.CMD program. The sequence numbers are informational only and need not be maintained if you choose to alter the contents of MKWINRUN.CMD.

5. MKWINOS/2 Error Messages
The following error messages can occur when running MKWINOS/2:
 * MK001 Unable to locate PROGMAN.INI file in ?:\...
 * The program was unable to locate PROGMAN.INI using the following criteria in decreasing priority:
 * 1) Command line
 * 2) Key file (MKWINOS2.KEY)
 * 3) WINOS2_LOCATION value in OS2.INI.


 * MK002 Unable to find the Order= string in PROGMAN.INI
 * The string Order= could not be found in the PROGMAN.INI file.


 * MK003 Unable to find the [Groups] string in PROGMAN.INI
 * The string [Groups] could not be found in the PROGMAN.INI file.


 * MK004 Error processing Group#= line in PROGMAN.INI (nnn).
 * A line in the [Groups] stanza could not be recognized. The numeric value indicates the absolute byte position in the file where the line was in error.


 * MK005 .GRP file name missing. Group is ignored.
 * The file name shown for the indicated group number in PROGMAN.INI can not be found. The group is ignored.


 * MK006 File_name is not a valid .GRP file
 * Parsing of the .GRP file was omitted or may be in error because of one of the following:
 * 1) Bytes 1-4 do not contain PMCC.
 * 2) Unable to find "Tag Data" at end of .GRP file


 * MK007 Unable to locate MKWINOS2.DBX
 * This is our version of DATABASE.TXT.


 * MK008 Unable to locate [WINDOWS] in MKWINOS2.DBX
 * MK009 Unable to locate [OS2] in MKWINOS2.DBX
 * MK010 Unable to locate the object WIN.INI file in ?:\...
 * Could not locate WIN.INI in the WINOS2 path.


 * MK011 Unable to locate WIN.INI file in ?:\...
 * The program was unable to locate WIN.INI using the following criteria in decreasing priority:
 * 1) Command line
 * 2) Key file (MKWINOS2.KEY)
 * 3) WINOS2_LOCATION value in OS2.INI.


 * MK012 REXXLIB is at an obsolete level.
 * This should not occur, as a correct level of REXXLIB is included in the MKWINOS2.ZIP package. Check your LIBPATH= for a path that contains an older copy of REXXLIB.


 * MK013 External REXX data queue error.
 * Queue synchronization error. This is an internal program error that It appears to be caused by the RXQUEUE('DEL') function intermittently not deleting the queue. Testing has shown that the program can be rerun without error.


 * MK014 Unable to locate SYSTEM.INI file in ?:\...
 * The program was unable to locate SYSTEM.INI using the following criteria in decreasing priority:
 * 1) Command line
 * 2) Key file (MKWINOS2.KEY)
 * 3) WINOS2_LOCATION value in OS2.INI.


 * MK015 Error while parsing source / object WIN.INI file.
 * This is an internal programming error that It is suffixed by a sequential number to indicate its source.


 * MK016 Unable to locate MKWINOS2.FIL file.
 * MK017 MKWINOS2 source code has been altered.
 * It is necessary that this REXX program be run in the form it was received.

6. Windows file processing - Full Pack only
Many Windows programs require .INI files to hold data specific to a program or groups of programs. MKWINRUN.CMD handles this by identifying those .INI files contained in the subject Windows path that do not exist in the WINOS2 path. This situation only occurs in an OS/2 Warp Blue box (or original OS/2 2.1 - full pack) environment. MKWINRUN copies these .INI files to the WINOS2 directory if either; a) the .INI files does not exist; or b) the .INI file in the WINOS2 directory pre-dates the copy in the subject Windows directory. INI files which are part of the Windows program itself (e.g. CONTROL.INI, PROGMAN.INI, SYSTEM.INI, WIN.INI) are not copied.

If any Windows group windows are open or if there are programs in the Windows Startup group when MKWINOS/2 is run, MKWINRUN provides you with the option to shadow the equivalent OS/2 objects into the OS/2 Startup folder (). The default is not to create these shadows and a 30 second time is permitted to reply to MKWINRUN in order to change the default from No to YES.

7. Enabling MKWINOS/2
The demo version of MKWINOS/2 is transformed into the full, commercial version by providing an enabling key as the first line of the MKWINOS2.KEY file. The retail price of MKWINOS/2 key is 19.95 USD (if you require diskette distribution add $7.00). All of the vendors listed below accept credit cards (MasterCard, Visa, Discover, and American Express) or a check payable in US dollars and drawn on a US bank. Credit card numbers should NOT be sent via the Internet. CompuServe members can securely E- mail orders to CompuServe addresses.

7.2 Updates and service
The latest version of MKWINOS2.ZIP is available on the Internet via a World Wide Web browser from , via FTP from , or from CompuServe in Library 1 of the OS2AVEN forum. Updates to the current version of MKWINOS/2 will be available at no additional charge from these electronic repositories. Though MKWINOS/2 is also available from other BBS and online services, C F S Nevada, Inc. only maintains the home sites.

MKWINOS/2 is a trademark of C F S Nevada, Inc. OS/2 is a registered trademark of IBM Windows is a registered trademark of Microsoft Corp.

Compliments of NetMind's URL-minder, you can automatically be notified via E-mail when this page changes: Your E-Mail address: