PC Online 1999 April/PCO0499.ISO/filesbbs/os2/cfgmaint.arj/CFGMAINT.ZIP/CM2.INF

OS/2 Help File | 1999-01-27 | 119.2 KB | 496 lines

ΓòÉΓòÉΓòÉ 1. INTRODUCTION ΓòÉΓòÉΓòÉ

             ConfigMaint/2 (CM/2)
             (c) 1999 by Kai Evers
           CM2CFG.DAT by Klaus Staedtler

ConfigMaint/2 is a new FREE application which succeeds ConfigInfo by Rick
Meigs. As ConfigInfo has some bugs and is no more maintained by Rick Meigs
there was the need to build a new Config.sys analizer and information tool.

Naturally ConfigMaint/2 has some more fortunities compared to ConfigInfo.

CM2CFG.DAT is based on OS2CFG11.DAT by Rick Meigs but is being maintained now
by Klaus Staedtler ([e-mail]), as Rick Meigs no longer seems to support
it. ATTENTION: The OS2CFG.DAT file can't be used together with CM/2, as the
CM2CFG.DAT can't be used together with ConfigInfo.

Sources of tips'n'tricks other than ConfigMaint/2 include V.O.I.C.E.
newsletters to be found at
http://www.os2voice.org/newsletters.html and OS2-EZINE at http://www.os2ss.com/

'Surviving with OS/2 Warp in a sea of Windows' by Robert "RokNroB" Thomas at
http://www.flash.net/~roknrob/sea.htm, although it should better be renamed to
'a desert of windows' ;-)

German reading users may also wish to know about other OS/2 FAQ at
http://www.on-line.de/

CM2CFG.DAT is unlikely ever to be complete; but it can improve, gradually, as
people send us the missing data, and as we have the time to make the necessary
changes.
You can help by mailing all your tips'n'tricks to [e-mail]

BTW, we mention only FREE software as CM/2 is build only with Freeware. We are
also aware that there is a commercial IBM software named 'Communications
Manager' shortened to CM/2.

This is 1. not because we have anything against commercial products, but more
to support those developers around the world who create great software
solutions without expecting financial reward.

And 2. this saves your money to buy commercial OS/2 software.
Support OS/2 by buying native OS/2 software!

PLEASE NOTE PARTICULARLY:

REXX must be installed on your system.
ConfigMaint/2 only supports Warp 3 and 4.
OS/2 2.X is no longer supported (but CM/2 should run, though).

It is strongly recommended to read everything in this information file and in
cm2cfg.dat.
See also chapter READING THE CM2CFG.DAT FOR ADDITIONALINFORMATION


ΓòÉΓòÉΓòÉ 1.1. DISCLAIMER ΓòÉΓòÉΓòÉ

REALISTICALLY, WE CANNOT BE HELD RESPONSIBLE FOR WHAT YOU DO WITH OR TO YOUR
SYSTEM OR YOUR CONFIG.SYS FILE BASED UPON WHAT YOU MAY LEARN FROM INFORMATION
PROVIDED IN THIS PROGRAM OR THROUGH USE OF THIS PROGRAM. BE WARNED: NO WARRANTY
OR FITNESS FOR ANY PURPOSE IS IMPLIED. INFORMATION AND PROGRAM ARE PROVIDED ON
AN "AS IS" BASIS TO BE USED AT YOUR OWN RISK.

THE AUTHORS SHALL IN NO EVENT BE LIABLE FOR THE ACCURACY OF THE RETRIEVED DATA
AND THE PROGRAM CODE OR FOR ANY DAMAGE THAT THE SOFTWARE MIGHT CAUSE DIRECTLY
OR INDIRECTLY.

This whole process started in 1992 when Rick Meigs began researching what many
of the config.sys file commands in OS/2 were for.
The data file used by this program is the result of this still ongoing
research. All current versions of this program are Freeware.

ConfigMaint/2 (c) 98/99 by Kai Evers
Data compilation, documentation by Klaus Staedtler


ΓòÉΓòÉΓòÉ 2. INSTALLATION ΓòÉΓòÉΓòÉ

REXX MUST BE INSTALLED ON YOUR SYSTEM TO RUN THIS PROGRAM.

For best results, install this program on your hard drive. The partition should
not matter, as long as its local.

To install:

Unzip the files to an temporary directory or where you want to reside CM/2 and
run install.cmd.
The installation process will NOT modify your Config.Sys or system INI files.
To deinstall you can safely delete all files and ConfigMaint/2 is gone.

If you use Warp 3 or 4 it's a good idea to 'pack' the executable and the DLL
with 'lxlite' by Andrew Zabolotny to save some space on your HD.


ΓòÉΓòÉΓòÉ 3. TO LAUNCH ΓòÉΓòÉΓòÉ

Double click on the program icon to launch the program, by default it loads
your config.sys from root on your boot drive.

You can also launch the program from within it's folder by double clicking on
the ConfigMaint/2 icon.

Further more you can also drop a config.* file on the ConfigMaint/2 Icon to
start ConfigMaint/2 with the selected file.

Naturally you can also start the program by command line.

In this case you can simply start ConfigMaint/2 with any
config.* file you want; e.g. cm2.exe d:\backup\config.bak.

As you see starting ConfigMaint/2 can be done in the way
you like it ;-).


ΓòÉΓòÉΓòÉ 4. USING IT ΓòÉΓòÉΓòÉ

CM2.EXE is a CONFIG.SYS information and editing utility.
When launched, the program loads your CONFIG.SYS file into Window #1 (top one)
and excerpts from the latest CM2CFG.DAT into Window #2 (bottom one).

Once CM2.EXE has loaded both files, click on any CONFIG.SYS statement in Window
#1; if available, a description of that item appears in Window #2, along with
tips, notes, warnings and other information. Not all items can be covered but
much is.

The program also lets you edit, back up and analyse your CONFIG.SYS file, and
do more besides.

Incidentally, CM2CFG.DAT is a plain text file, worth reading on its own for the
good stuff in it. The program is not needed for access. A plain text editor is
enough but be careful not to make unintentional changes.


ΓòÉΓòÉΓòÉ 4.1. DETAILED DESCRIPTION ΓòÉΓòÉΓòÉ

On the next pages you'll find a detailed description how to make use of
ConfigMaint/2 when optimizing your config.sys


ΓòÉΓòÉΓòÉ 4.1.1. EDITING YOUR CONFIG SYS ΓòÉΓòÉΓòÉ

When CM/2 starts for the first time it automatically makes a backup of your
config.sys as config.org. This file is stored in the subdirectory 'backup' of
the CM/2-directory. So if anything should go wrong, you have the possibility to
restore your original config.sys by copying this file over the edited
config.sys. For doing this you have to copy the file config.org to your
root-directory on your boot drive and rename it to config.sys.

TIP: you can also start CM/2 instead of the default config.sys from the boot
drive with any config.* file as a command line parameter, or simply drop a
config.* file on the CM/2 icon.

During the load of the config.sys CM/2 tries to analyze it for inconsistencies
and double entries, so don't worry if this takes some time. This process is
signalized by a growing blue bar at the bottom in the message window.
ATTENTION: CM/2 normally only parses the \os2\boot
directory, in some case you'll see a lot of errors. This appears when
BASEDEVICE DRIVERS are stored in the \os2 directory (e.g. with IBM THINKPADS)
or in the root. If this happens you first have to customize CM/2. How to do
this see the chapter CONFIGURE CM/2.

As soon CM/2 is ready it shows 'Done' in the message window and your config.sys
is shown in the upper window #1.

The message window at the bottom displays also the significance of every button
used in CM/2 as detailed text whenever your mouse pointer is over a button.

If you singleclick on any line the lower window #2 shows the suggestions for
this line found in the cm2cfg.dat. You can search this specific suggestion by
pressing the 'SEARCH' -Button. A popup opens and you can insert the term you
are searching for by pressing an arrow-symbol. The 'UP'-Arrow searches upwards,
pressing the 'DOWN'-Arrow searches downwards.

The message window directly near the entry filed for the search terms shows how
often the term is found and as many you have seen.

Pressing the 'CLOSE' button closes the search popup.

You can also clip the whole suggestions to your clipboard by pressing the
'CLIP'-Button.

The SIGNS in front of every line of your config.sys signalize the following:

GREEN HOOKS
are signalizing that the line seems to be okay.

BLUE DASHES
are signalizing lines with a REM in front, this  means theline is inactive.

RED CROSSES
are signalizing errors in the line, e.g. the
path could not be found, the driver is not available ...
ATTENTION: When the line contains a variable (e.g.%N) CM/2 shows an error
although everything is okay !

Editing a line is quite easy: Doubleclick with your left mouse button on a line
and you'll get a popup window showing the line, a window with suggestions and
some buttons. You can now edit this line.
As soon as you press the 'APPLY'-Button the corresponding line in your
config.sys will be overwritten with the new line. When you press 'CLOSE' the
popup will be closed and the upper window #1 shows you updated config.sys.

If you do a singleclick on a line and then a 'right mouse button'-click you'll
get a popup with three entries: ' TOGGLE REM', 'EDIT' and 'DELETE LINE'. Left
clicking on 'TOGGLE REM' either puts a 'REM' in front of this line to
deactivate it, or removes a 'REM' to activate the line. Left clicking on 'EDIT'
opens the edit popup as described before. 'DELETE LINE' deletes the line.

While in edit mode there are shown some file informations, like size, vendor,
build level, additional informations or the creation date (Y2K tested ;-).

Pressing the 'SAVE CONFIG FILE' button applies all of your chances and rewrites
your config.sys

CM/2 defaults to your config.sys on your boot drive and starts with it
automatically. If you want to edit any other configuration file (e.g. a
config.*) click on the 'LOAD CONFIG FILE' button. This opens a file-dialog
where you can select an alternating file from an alternating drive or
directory.

If you press the 'SORT CURRENT CONFIG FILE' button your config.sys will be
sorted and stored as 'config.srt' in your CM/2-Directory. To make it active
copy this file to your boot drive and rename it to 'config.sys'.

Pressing the 'CONFIGURE PROGRAM' button opens a popup where you can select how
the sorting and the save should be done.
See next chapter.Pressing the 'EDIT RECOVERY OPTIONS/ MULTIPLE CONFIG FILES'
button opens a popupmenu see one of the following chapters for a detailed
description.

Pressing the 'EXIT PROGRAM' button exits CM/2.


ΓòÉΓòÉΓòÉ 4.1.2. CONFIGURE CM/2 ΓòÉΓòÉΓòÉ

EDITOR SECTION

You can define an alternate editor if you don't want to use e.exe delivered
with OS/2.
BTW. using EPM.EXE is not such a good idea because of the way in which OS/2s
Enhanced PMeditor (EPM.EXE) handles word wrapping and its restricted line
length.

SAVE SECTION

If you select 'CONVERT TO UPPERCASE' all letters are written in CAPITALIZED,
normally this should be the correct mode how entries are made in the config.sys
(but like everywhere dictions produce contradictions ... - so have a test). If
you select 'SAVE BACKUP' CM/2 saves your config.sys in the corresponding
directory as config.cm2

SORT SECTION

All entries here affect only the config.srt file

'IFS.FIRST' moves the installable file systems on the first
place in the config.srt. This is advised as the normal case.
E.g if you have a HPFS formatted drive as boot drive OS/2
won't boot without the hpfs.ifs line at first.

If you check 'delete REM' all lines carrying a REM in front are deleted.

You can also select to convert the letters to 'UPPERCASE'.

BASEDEVICE DRIVERS SECTION

Here you can define the directories where CM/2 parses for the
BASEDEVICE drivers.

In OS/2 V3 and V4 normally only the root directory and the \OS2\BOOT directory
are 'allowed' places for storing basedevice drivers, but ...

As the root directory isn't such a good place for basedevice drivers CM/2
doesn't parse it for drivers. If you get an error message about a missing
basedevice driver - you'll get a redcross in front of the corresponding line -
check if all drivers are in \OS2\BOOT or if some rest in the root directory.

By default CM/2 only searches in \OS2\BOOT, but for special cases you can also
define \OS2 - like in OS/2 Ver 2.X - , or a 'thinkpad mode' where CM/2 parses
the \OS2 and \OS2\BOOT directories for BASEDEVICES (necessary for e.g IBM
THINKPADS, cause the THINKPAD Driver Installer installs the drivers in \OS2).

ATTENTION: If you select the 'thinkpad mode' the start of CM/2 will be
significantly slower!

Additionally you can select the desired font (e.g. if you want to have a non
proportional font) for the description field. Simply drop the font out of the
fontpalette on the listbox.


ΓòÉΓòÉΓòÉ 4.1.3. EDIT RECOVERY OPTIONS MULTIPLE CONFIG FILES ΓòÉΓòÉΓòÉ

Pressing the 'EDIT RECOVERY OPTIONS/ MULTIPLE CONFIG FILES' button opens a new
window showing a screen which is similar to the one you get after pressing 'ALT
F1' during bootup.

In fact CM/2 loads the altf1top.scr, altf1mid.scr, altf1bot.scr and displays
them. The altf1top.scr-file is stored as 'ALTF1TOP.ORG' in the backup directory
of CM/2, so you can revert all chances you've done.
This screen is good for 'personalizing' your boot options:
YOU CAN BUILD MULTIPLE BOOT OPTIONS e.g. boot with voicetype, boot without
Dos/Win ...

Click on a line loads it into the line-editor on top of the window.
You are now able edit the line according to your wishes. When you press 'APPLY'
the line is rewritten and stored in the 'altf1top.scr' file in your
'\OS2\BOOT'- Directory.
Additionally you are able to 'PROMOTE' the line by pressing the 'UP' arrow,
'DEMOTE' the line by pressing the 'DOWN' arrow. Delete the line by pressing
'DEL' or to add a new empty line by pressing 'INS'.

ATTENTION: Whenever you want to add a line keep in mind that the sum of all
lines in altf1top.scr, altf1mid.scr, altf1bot.scr togehter should not exceed 25
lines. Therefore adding a line will move the first line out of the visible area
(so you have to delete lines whenever you add lines).

CM/2 reflects this limitation by showing

1.the number of lines and
2.signalizing in red letters that the 1.line (2. ...) will not be shown!

The lines showing your archives cannot be modified! (They are part of the
altf1mid.scr)

The lines showing Fn (n=1,2,3 ...) and ESC should not be modified, they are
reserved for system use.

All other lines can be edited.

When you edit or insert a line in the following way you are able to build your
own individual boot options:
A line starting with a character and to blanks, followed by adash (e.g. '?  -';
? = any allowed character) you are inserting a command for an alternate
configuration file (e.g. config.D) selectable during bootup.
As characters all characters are allowed except:
C, M, V, X, 1, 2, and 3, with Warp 3
C, M, V, X, 1, 2, 3, 4, 5 and 6 with Warp 4

After pressing 'APPLY' the altf1top.scr will be rewritten and you are able to
select a configuration file by pressing 'EDIT'. This opens the defined
external-editor (default e.exe). Here you can load a config-file (e.g. the
config.sys from your boot-drive) edit it to your needs and store it as config.?
(? = the character you've selected) into your \OS2\BOOT-Directory.
Pressing the 'SAVE'-Button will write a altf?.cmd file in your
OS2/BOOT-directory containing the following:
'copy\OS2\BOOT\CONFIG.? \CONFIG.SYS'

TIP: Naturally you can load the once generated config.? file in CM/2 and edit
it to your needs and wishes.

Once a config.? is defined it can also be deleted by pressing 'DEL' or an
alternative file can be selected by pressing 'SEL'.

? IS ALLWAYS MEANT AS VARIABLE FOR THE ALLOWED CHARACTER

Now you are able to select an alternating configuration by pressing 'ALT F1'
during bootup and then selecting the configuration by pressing the Character
you've choosen on your keyboard. OS/2 will then boot with your specific
configuration file.


ΓòÉΓòÉΓòÉ 4.1.4. READING THE CM2CFG DAT FOR ADDITIONAL INFORMATION ΓòÉΓòÉΓòÉ

Normally CM/2 shows in the suggestion window #2 the context found in
CM2CFG.DAT.

Whenever you want to know something about statements not found in your
config.sys, want to read special tips 'n tricks or how to's you have to read
the informations in CM2CFG.DAT. This is STRONGLY RECOMMENED FOR ALL USERS cause
you'll maybe find some useful informations you never have been aware, which can
stabilize your OS/2, add new features ...

For a somewhat easier use we have build in some reading capabalities.

If you click on the dropdown list on the left side of the window a menu opens
where you can select the following chapters:

ALL
shows the complete CM2CFG.DAT.

GENERAL
shows all informations about 'general' settings (e.g. PATHS, PROTSHELL ...)

IFS
shows all informations about Installable File Systems

SET
shows all informations about SET Commands

DEVICE
shows all informations about DEVICES and BASEDEVICES

RUN
shows all informations about RUN, START and CALL statements

DOS
shows all informations about DOS statements

DOS DRIVERS
shows all informations about DOS DRIVERS

TCP/IP
shows all informations about TCP/IP statements

JAVA
shows all informations about JAVA

NOVELL
shows all informations about a NOVELL NETWORK

LAN
shows all informations about the LAN SERVER

HOW TO
shows some HOW TO'sTHANKS
shows the names of person who have given useful informations.

You can search these individual chapters or the whole database for informations
by using the 'SEARCH' button as described before. If you press 'VIEW' e.exe (or
the editor defined by you in 'CONFIGURE PROGRAM') starts with CM2CFG.DAT at the
selected chapter.


ΓòÉΓòÉΓòÉ 5. KNOWN BUGS AND LIMITATIONS ΓòÉΓòÉΓòÉ

As of this release (v0.92) no bugs are known


ΓòÉΓòÉΓòÉ 6. CONTACT ΓòÉΓòÉΓòÉ

For suggestions and bug reports concerning CM2.EXE please contact
KAI EVERS via e-mail: [e-mail] (or visit www:
http://www1.stuttgart.netsurf.de/~kevers/)

For suggestions, additional informations, and bugs concerning CM2CFG.DAT and
this documentation please contact
KLAUS STAEDTLER via e-mail: [e-mail]


ΓòÉΓòÉΓòÉ 7. RECOMMENDED MAINTENTANCE PROGRAMMS ΓòÉΓòÉΓòÉ

Here is a short list of some programs.
They have been proofed by us and they are recommended for the maintenance of
OS/2:

For creating maintenance disks and partitions there is the very useful FREE IBM
EWS Tool Bootdisk, the latest version is btos2917.zip

There is also a very usefull FREE IBM EWS TOOL
called Warp'n Go for handling the config.sys. It works
normally only together with WARP 3. You can use it in WARP4
when you insert in OS2VER the following lines:
23=WARPNGO.EXE
23=WARPNGO.DLL
ATTENTION ! using Warp'n Go together with WARP 4 deletes the
WARPCENTER Statement from SET AUTOSTART, but you can copy a
Shadow of the WarpCenter into the Autostart Folder, this
solves additionally some problems reported with WarpCenter
started by the config.sys.

As for OS/2 the both ini's OS2.INI and OS2SYS.INI are of great importance have
an look on them also. There are the great FREE WPS-TOOLS by Henk Kelder for an
backup, restore and check of these files, they can be found on many servers, or
on the authors homepage http://www.os2ss.com/information/kelder/

For editing the INI Files you can make use of Regedit/2
supplied with newer Fixpacks for Warp 4.
There is also a somewhat faster FREE Editor by Kai Evers called mINI available
at http://www1.stuttgart.netsurf.de/~kevers/
Or use the FREE INIEDIT by Goran Ivankovic available at
http://members.tripod.com/~Goran_Ivankovic/


ΓòÉΓòÉΓòÉ 8. TO DO ΓòÉΓòÉΓòÉ

- Clip/View when editing
- evtl. more functionality when editing
- database with optimizing tips
- ...
- Your suggestions?


ΓòÉΓòÉΓòÉ 9. THANKS ΓòÉΓòÉΓòÉ

Thanks to those who supported us by testing the inofficial beta versions

Ulrich MФller
Jerry Pedone
Chuck McKinnis
Goran Ivankovic
Kovacs Istvan
Marcus Specht
Kim Kruse Hansen for creating wp2ipf. A rather outdated,
         but nevertheless very useful free tool for
         creating inf files out of wordperfect files