home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 8 Other
/
08-Other.zip
/
cfgmt100.zip
/
cm2.inf
(
.txt
)
< prev
next >
Wrap
OS/2 Help File
|
1999-04-06
|
172KB
|
778 lines
ΓòÉΓòÉΓòÉ 1. Introduction ΓòÉΓòÉΓòÉ
ConfigMaint/2 (CM/2)
(c) 1999 by Kai Evers
CM2CFG.DAT and HOWTO.DAT by Klaus Staedtler
ConfigMaint/2 is a Config.Sys analyzer/optimizer/information tool for PM.
CM2CFG.DAT is based on OS2CFG11.DAT for ConfigInfo 4.0 by Rick Meigs but is
being maintained now by Klaus Staedtler (stadt@ibm.net), as Rick Meigs no
longer (since 1995) 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.
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 stadt@ibm.net.
Note: REXX must be installed on your system to run properly.
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 and HOWTO data for additional
information'.
Remarks:
We are aware that there is a commercial IBM software named
'Communications Manager/2' shortened to 'CM/2'.
We mention only FREE software as CM/2 is build only with Freeware.
This is 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 this saves your money to buy commercial OS/2 software. Support
OS/2 by buying native OS/2 software!
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,
German reading users may also wish to know about other OS/2 FAQ at
http://www.on-line.de/
If no other URL is quoted in CM2CFG.DAT the places for downloading the
mentioned software are:
Hobbes
OS2Supersite
Link Everything Online (LEO)
For mentioned drivers look first at the OS/2 Device Driver Pack at
http://service.software.ibm.com/os2ddpak/html/
ΓòÉΓòÉΓòÉ 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 files 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.
Note: Using ObjectRexx will significantly slow down processing ConfigMaint/2.
To compare with ClassicRexx, performance is ways slower so we suggest to use
ClassicRexx if you don't have any good reason to do not.
For best results, install this program on your hard drive. The partition should
not matter, since its local.
To install:
Unzip the files to a 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 its 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.
Note: If you want to make sure that CM/2 finds the program related files
(*.DAT, *.DLL), be sure to add the CM/2 path to your PATH and LIBPATH statement
in CONFIG.SYS (for command line use) or add the proper work directory to your
program object (for GUI use).
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 #2 (middle
one) and excerpts from the CM2CFG.DAT into window #3 (bottom one). The selected
line of your config.sys is in window #1 (edit field, top one) for editing.
Once CM2.EXE has loaded both files, click on any CONFIG.SYS statement in window
#2; if available, a description of that item appears in window #3, 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 analyzes your CONFIG.SYS file, and
do more besides.
Incidentally, CM2CFG.DAT and HOWTO.DAT are plain text files, 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 sometime. This process is
signalized by a growing blue bar at the bottom in the message window.
Warning: 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 middle window #2.
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 #3 shows the suggestions for
this line found in the cm2cfg.dat. You can search this specific suggestion by
pressing the 'SEARCH' -Button. A pop-up 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 pop-up.
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 the line is inactive.
RED CROSSES
Are signalizing errors in the line, e.g. the
path could not be found, the driver is not available...
Warning: When the line contains a variable (e.g.%N) CM/2 shows an error
although everything is okay!
Editing a line is quite easy: The with a single mouseclick selected line
appears into window #1 at the top. There you can edit the line. After editing
press the 'APPLY' button. When you press the 'APPLY'-Button the corresponding
line in the loaded config.sys will be overwritten with the new line. The middle
window #2 shows your updated config.sys.
Note: All changes are not really written to your config.sys. This only happens
when you press the 'SAVE CONFIG FILE' button.
If you do a singleclick on a line and then a 'right mouse button' click you'll
get a pop-up with three entries: 'TOGGLE REM', 'VIEW INFO' 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. 'DELETE LINE' deletes
the line.
'VIEW INFO' does the same as pressing 'Return' on your keyboard or a
mousedoubleclick on a line:
There are shown some file information's, like size, vendor, build level,
additional informations or the creation date (Y2K tested;-) if available in
window #3. Selecting another line reverts to the informations in cm2cfg.dat.
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.
'RELOAD' reloads the current selected config file without saving any changes.
This is usefull if you have made mistakes and want to get rid of them.
Pressing the 'SAVE CONFIG FILE' button applies all of your changes and rewrites
your config.sys.
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 notebook with the setting pages
where you can select how the sorting and the save should be done.
See next chapter.
Pressing 'REPORT' gives you a quick summary on all detected errors in your
Config.Sys.
Pressing the 'SHOW HOWTO'S... TIPS&TRICKS' button loads the howto.dat and
displays it in window #3.
Pressing the 'EDIT RECOVERY OPTIONS/ MULTIPLE CONFIG FILES' button opens a
pop-up-menu see one of the following chapters for a detailed description.
Pressing the 'INFORMATIONS' button opens a notebook with the info pages. On the
first page you'll find some informations about the program. On the second page
you can find informations about the current config file. You can change or edit
comments to be stored in .COMMENTS Extended Attribute of the config file for
additional informations and timestamping, which can also be made automatically
when saving. See CONFIGURE CM/2 for more details.
Pressing the 'EXIT PROGRAM' button exits CM/2 and saves preferences.
ΓòÉΓòÉΓòÉ 4.1.2. Configure CM/2 ΓòÉΓòÉΓòÉ
PAGE ONE
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.
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 red cross 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).
Note: If you select the 'thinkpad mode' the start of CM/2 will be slightly
slower. But don't mind, this should not be a real big deal.
PAGE TWO
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 everywheredictions produce contradictions... - so have a test). If
you select 'SAVE BACKUP' CM/2 save's your config.sys in the corresponding
directory as config.cm2. 'SAVE .COMMENTS EA' timestamps config files when they
are saved.
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'.
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 window #2 or on window #3. Both informations will be
preserved when restarting.
ΓòÉΓòÉΓòÉ 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 that 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'.
Warning: Whenever you want to add a line keep in mind that the sum of all lines
in altf1top.scr, altf1mid.scr, altf1bot.scr together 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 two 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 an 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'.
Note: ? IS ALWAYS 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 chosen on your keyboard. OS/2 will then boot with your specific
configuration file.
ΓòÉΓòÉΓòÉ 4.1.4. Reading the CM2CFG and HOWTO data 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 information's in CM2CFG.DAT or HOWTO.DAT. This is STRONGLY recommended FOR
ALL USERS cause you'll maybe find some useful information's you never have been
aware, which can stabilize your OS/2, add new features... brighten your teeth
;-)
ONCE AGAIN: CM2CFG.DAT DOESN'T CONTAIN ALL POSSIBLE INFORMATIONS TO BE FOUND IN
YOUR CONFIG.SYS. PLEASE HAVE A LOOK ON THE OS2 INFORMATIONS DELIVERED WITH WARP
ALSO. FURTERMORE HAVE A LOOK ON ANY DOCUMENTATION DELIVERED WITH YOUR HARD- AND
SOFTWARE. Naturally we want to be as complete as possible: so mailing us
informations you have, but are not found in cm2cfg.dat, increases the
information for all users.
For a somewhat easier use we have build in some reading capabilities.
If you click on the dropdown list on the left side of the window a menu opens
where you can select the following chapters:
CONTEXT
Shows the entry for the line selected in window #3.
ALL
Shows the complete CM2CFG.DAT.
GENERAL
shows all information's about 'general' settings (e.g. PATHS,
PROTSHELL...)
IFS
shows all information's about Installable File Systems
Note: There are quite more Installable File Sytems, e.g. by
Zipstream for encryption and/or compression of drives and another
for CD-Jukeboxes. There are also plans for developing a PSION IFS.
Please write me (stadt@ibm.net) when you want these file systems
also mentioned in cm2cfg.dat. As I have none of them it would be
quite nice if you'd add some informations.
SET
shows all information's about SET Commands
DEVICE
shows all information's about DEVICES and BASEDEVICES
Note: Not all are listed, either cause they are unstable (e.g.
danis506.add), very uncommon or outdated, or I don't know them.
RUN
shows all information's about RUN, START and CALL statements
DOS
shows all information's about DOS statements
DOS DRIVERS
shows all information's about DOS DRIVERS
TCP/IP
shows all information's about TCP/IP statements
JAVA
shows all information's about JAVA
NOVELL
shows all information's about a NOVELL NETWORK
LAN
shows all information's about the LAN SERVER
HOW TO
shows some HOW TO's. E.g how to protect against 'ping of death'.
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 the leaked first non public release (v0.92) no bugs are known.
According to some response there were problems with ObjectRexx and editing
larger lines than 255 chars.
This has been fixed.
Furthermore parsing of paths like "..\DLL" etc. gave errors.
This has been fixed.
Furthermore lines with values after "=" and blanks (e.g. "DEVICE=
E:\OS2\BOOT\DOS.SYS") makes them to be ignored.
This has been fixed.
Furthermore saving under 4OS2 appended the edited config.sys to the original
one.
This has been fixed.
Furthermore a screen-resolution with 640X480 wasn't supported.
This has been fixed.
As of this release (v1.00) one bug is known:
Using PRexx 3 as Rexx environment is at this time not a supported one.
ConfigMaint/2 has been coded and tested under ClassicRexx with some tests under
ObjectRexx. Both worked fine.
CAUTION:
Using ObjectRexx will significantly slow down processing ConfigMaint/2. To
compare with ClassicRexx, performance is ways slower so we suggest using
ClassicRexx if you don't have any good reason to do not.
ΓòÉΓòÉΓòÉ 6. Contact ΓòÉΓòÉΓòÉ
For suggestions and bug reports concerning CM2.EXE please contact
KAI EVERS via e-mail: ke@lb.maus.de (or visit www:
http://www1.stuttgart.netsurf.de/~kevers/)
For suggestions, additional information's, and bugs concerning CM2CFG.DAT,
HOWTO.DAT and this documentation don't hesitate to contact
KLAUS STAEDTLER via e-mail: stadt@ibm.net
ΓòÉΓòÉΓòÉ 7. Recommended maintenance programs ΓòÉΓòÉΓòÉ
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 BootOS/2, the latest version is btos2917.zip
There is also a very useful 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
Warning: 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
a look on them also. There are the great FREE WPS-TOOLS by Henk Kelder for a
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. History ΓòÉΓòÉΓòÉ
+ : New function/feature
- : Changes
v0.92:
First Release (should not have leaked to public)
v0.93с:
- Fixed problem with ObjectRexx and editing of large lines (>= 255 chars).
- Parsing of paths like "..\DLL" etc. gave errors. Fixed.
- Lines with values after "=" and blanks (e.g. "DEVICE= E:\OS2\BOOT\DOS.SYS")
make them to be ignored. Fixed.
+ Automatic searching for alternative text editor (config).
v0.94с:
+ cm2cfg.dat: Some enhancements and corrections
v0.95:
Release
v0.96с:
- Fixed output when paths with more than one semicolon found.
v0.97с:
+ cm2cfg.dat: The 'usual' enhancements and corrections. BASEDEV part
reworked, now individual entries for every device. XFree86 settings added.
IFS Part reworked and cleaned. Howto's seperated from cm2cfg.dat, now in
howto.dat. Thanks now only in this information file.
- Rewrite of file handling routines to match names containing blanks.
- Double retrieving of file specific stuff fixed.
+ Cosmetic changes, one more line for display of Config.Sys.
v0.98с:
+ cm2cfg.dat: Many enhancements and corrections.
+ External howto.dat to speed up things.
+ Display of single BASEDEV items.
+ Howto button added.
- Internal changes to match slightly changed cm2cfg.dat format.
- Finally more file informations on systems with newer BLDLEVEL.EXE installed.
Previous versions worked ok (e.g. the one from FP#1), but output parsing of
later ones was wrong. Fixed.
- Fixed hang on exit using close button and other dialog open.
- Fixed bug in "thinkpad" mode where no other additional informations
were shown except from BASEDEVs.
+ Slightly improved installer, docs, related files.
v0.98:
Release
v0.99с:
- Font handling: Internal changes.
- Dialog design reworked.
v0.99.1с:
- Complete GUI reworked.
v0.99.2с:
+ Combining various dialogs in one notebook.
v0.99.3с:
- Bug when saving original *.org file fixed.
- Failed deletion of files under 4OS2 fixed.
- Notebook changes.
+ Comments for the config.sys implemented (.COMMENTS EA).
v0.99.4с:
- Smarter looking smaller dialog design for 640x480 support.
- New bitmaps.
+ Saving of default font of Config.Sys container.
+ saving of .COMMENTS EA with SAVE and SORT.
v0.99.5с:
+ More program infos, options extended (EA).
v0.99.6с:
- Fixed bug when searching for dupes in Config.
+ Report of summary of all detected errors implemented.
- Some Search logic reworked.
v0.99.7с:
- Internal changes with clipboard related stuff.
+ Storing size of notebook in cm2.ini.
+ Storing size of main dialog in cm2.ini.
+ cm2cfg.dat: Small corrections, pcmcia entries enlarged, some new entries.
+ howto.dat: Partition-id table, Notes 4.6x client added.
+ Slightly improved docs, related files.
v1.00:
Release
ΓòÉΓòÉΓòÉ 9. TO DO ΓòÉΓòÉΓòÉ
- Smarter clipping of selected portions, not just the whole bunch
- Probably more functionality when editing
- Database with tips for optimizing
- ...
- Your suggestions?
ΓòÉΓòÉΓòÉ 10. Thanks ΓòÉΓòÉΓòÉ
Thanks to those who supported us by testing the inofficial beta versions
Ulrich MФller: Developer of XFolder, do we need to say more?
Jerry Pedone
Chuck McKinnis: IBM Senior Specialist
Goran Ivankovic: Developer of many useful free apps.
Kovacs Istvan: Member of TeamOS/2 one of the best sources for
undocumented.
Marcus Specht: Member of TeamOS/2 and Webmaster of buntspecht.de.
BTWb: From http://www.buntspecht.de ConfigMaint/2 has been
downloaded in february more than 1100 times :-).
Andrew Stephenson: for parts in this file corrected to colloquial
english.
Kim Kruse Hansen: for creating wp2ipf. A rather outdated, but
nevertheless very useful free tool for creating inf files out of
WordPerfect files.
Special thanks for reporting problems, comprehensive suggestions and friendly
mail:
OS/2 Inside, deplorably no loger published
CT, a german computer magazine
OS/2 Voice, the OS/2 online-magazine
Mark Paulus
Oliver Poggensee
Greg Bruce
Les Clark
Steve Wendt
Judy McDermott
Jan van Wijk
Stefan Milcke
Denis Tonn
Dan Carter
Doug Boulter
Keith Medcalf
Dan Leitner
Jim Jaworski
Dwight Huffman
Dr. Martin Senftleben, aka Dr.Martinus
Roland Sambain
Erik Bracke
Chuck Fischer
Leigh Bunting
Cheng Ming Long
Michael Mahoney
Jack Troughton
Lowell A. Douglas
Klaus Lehmann
Carlos Andre R. Mercier
Albert M. Svoboda
David Mediavilla
Jon Harrison
Rainer Feuerstein
and everyone we forgot ;-)