home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 11 Util
/
11-Util.zip
/
cfginfo7.zip
/
os2cfg16.dat
< prev
next >
Wrap
Text File
|
1998-10-11
|
164KB
|
3,951 lines
--------------------------------------------------------------------
OS/2 CONFIG.SYS DESCRIPTION - Version 16 - Oktober, 1998
--------------------------------------------------------------------
os2cfg16.dat is partly rewritten, as computers and their
use have changed significantly since the release of
CONFIGINFO in the year 1995.
New commands by Klaus Staedtler (stadt@ibm.net)
The informations here aren't complete.
I'll maybe in the future add them when I have the time
and get the informations (K.S.).
Look also at Chapter 7. sample where the use of other IFS
(Windows NTFS/FAT32 Apple HFS Linux EXT) is discussed
Additionally I've added an instruction (see Chapter 11)
how to install Warp 4 over an laplink cable,
also good for networking over an parallel cable.
To shorten the file I've moved all thanks at the end in
Chapter 12.
AS RICK MEIGS SEEMS TO SUPPORT CONFIGINFO NO MORE SEND YOUR
IFORMATIONS PLEASE TO KLAUS STAEDTLER stadt@ibm.net THANKS
ENCOURAGEMENT: This ASCII file may be freely distributed (and
you're encouraged to do so) but you may not charge for the program,
Further, the copyright notice may not be removed nor may the file
be modified. This file is Freeware (that means you can use it at
no cost and pass it on to your friends), but it is not in the
public domain.
VIEWING FILE: Regardless of what editor you use, for best
results turn word wrap OFF and use a monospaced (like System
Monospaced) font.
PRINTING FILE: In enhanced JB format for easy printing and
viewing. Print file using your favorite text editor.
-----------------------------------------------------------------
1. CAUTION, WARNING AND DISCLAIMER.
<<=CAUTION=>> Because of the way in which OS/2s Enhanced PM
editor (EPM.EXE) handles word wrapping and its restricted line
length, using it to edit your config.sys file is unwise. For
best results, use OS/2s System Editor (E.EXE).
<<=WARNING=>> If you plan on changing any line in your current
config.sys file, please be sure to create a backup --BEFORE--
you start experimenting! This has saved me more than once.
Remember, make the backup --BEFORE-- you change your config.sys
file. If you are viewing this information using CNFGINFO.EXE,
use its backup option before you proceed any further.
A procedure for restoring a damaged config.sys is included
at in Chapter 8. of this file also an advise how to use
multiple configuration. If you are using WARP, refer to your
user manual on WARPs archive feature first.
<<=TIP=>> For creating maintenance disks and partitions there
is the very useful FREE IBM EWS Tool Bootdisk, the latest
version is btos2915.zip
If you plan to install warp 4 over an laplink cable there's
an instruction in chapter 11.
<<=TIP=>> There is also an 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 an
Shadow of the WarpCenter into the Autostart Folder, this
solves additionally some problems reported with WarpCenter
started by the config.sys.
<<=TIP=>> The new xfolder ver. 0.80 by Ulrich Moeller has
also some settings for the config.sys. Available at
http://www2.rz.hu-berlin.de/~h0444vnd/os2.htm
For the moment the Beta has some problems so be careful.
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, bbs or on the
authors homepage http://www.os2ss.com/information/kelder/
latest version is WPTOOL26.ZIP
For editing the INI Files you can make use of Regedit/2
supplied with newer Fixpacks for Warp 4, there is also an somewhat
faster FREE Editor called mINI by Kai Evers available at
http://www1.stuttgart.netsurf.de/~kevers/
<<=DISCLAIMER=>> I CAN'T BE RESPONSIBLE FOR WHAT YOU DO WITH
YOUR SYSTEM OR YOUR CONFIG.SYS FILE BASED UPON WHAT YOU MAY
LEARN FROM THE INFORMATION PROVIDED IN THIS FILE. EVERY EFFORT
HAS BEEN MADE TO MAKE THIS FILE AS ACCURATE AS POSSIBLE, BUT
NO WARRANTY OR FITNESS IS IMPLIED. THE INFORMATION IS PROVIDED
ON AN "AS IS" BASIS. USE IT AT YOUR OWN RISK.
-----------------------------------------------------------------
2. COMMENTS.
This whole process started in 1992 when Rick Meigs began researching
what many of the config.sys file commands were for. This ever
growing file is the result of that ongoing research. It briefly
describes most of the common and some of the more obscure
commands. Naturally, not all possible commands are listed
(especially the many hardware device drivers), but there is a
lot here for you to work with. Version 6 was the first version
updated for OS/2 2.1 and version 9 was the first updated for
OS/2 Warp 3. Version 12 was the first updated for Warp 4.
Naturally this information file can't be complete otherwise it
would have the size of some Meg's and the people working at
helpdesks would loose their job ;-)
-----------------------------------------------------------------
3. IMPORTANT NOTE AND WARNING
Unlike the DOS config.sys file which is read sequentially, OS/2
reads the entire file before it invokes the commands listed.
Therefore, except for several exceptions which have been noted,
it really doesn't matter where a command is placed. On several
of the "nets" and in a file called CNFGSORT.ZIP it has been
suggested that if you organize your config.sys file in a certain
way, you can significantly shorten the boot time of OS/2. I
find this sorting to be of little or no help for the vast
majority of OS/2 users. Further, you can cause yourself
problems if you do it incorrectly. So be very careful and have
a backup config.sys file ready. Sorting your config.sys file
DOES make sense for those who wish to organize it for readability
and management purposes.
Despite this warning of Rick I've added the last available version
of Configsort (K.S.).
-----------------------------------------------------------------
4. BEGINNING OF CONFIG.SYS FILE DESCRIPTION.
IFS=C:\OS2\HPFS.IFS /CACHE:512 /CRECL:16 /AUTOCHECK:CDE /F:2
IFS stands for "Installable File System". This OS/2 command
installs the High Performance File System (HPFS). The syntax
is IFS=DRIVE:PATH\FILENAME,SWITCHES. There are three switches:
/CACHE:nnn sets up a disk cache and its size. The default on
most systems is low in my opinion.
<<=Warning=>> Keep this one truth in mind about cache size:
an excessive cache takes memory available for programs and
therefore could have a negative impact on overall system
performance. But today, when most systems have 32MB+ the
problem is more the restriction of the cache to 2MB.
OS/2s Command Reference and other IBM sources indicate that
the maximum cache size for HPFS is currently 2MB (2048), but
IBM does not recommend using a cache larger than 1.5MB (1536).
Personally, I have 16MB of RAM and have my HPFS cache set to
the max: 2048.
If this switch is omitted, the default is 10% of the available
RAM on systems with more than 8MBs of RAM.
<<=TIP=>> Use HPFS386.IFS if you have an license. It brings
an significant performance boost into your system. If you
plan to use HPFS386.IFS look for the serverfaq.zip at
http://www.w-4.de/~tbaumann, unfortunately its only in german
<<=TIP=>> At the end of the file is a detailed discussion how
to set the cache with system less than 32 MB
<<=TIP=>> For analyzing HPFS formatted drives there is the FREE
Tool DFsee by Jan van Wijk, available at http://www.fsys.demon.nl
DFSee can also undelete files and much more.
<<=TIP=>> For undeleting files on HPFS Drives use the great IBM
EWS Tool File Phoenix (Rel. 1.35) by Joe DiAdamo, available
at many servers or BBS.
<<=Tip=>> /QUIET will give you access to dirty partitions, too.
It's mentioned in the readme.1st file of Warp4 FP5.
There is an option /FORCE, I have seen it explained somewhere, but
can't find out where.
========================== Table 1.0 ===========================
You can get better performance from your system by using your
available RAM in the most efficient and effective way. Select
the case that best describes the file system or amount of RAM
you use.
CASE 1: You use only HPFS or only FAT, but not both.
HPFS only. FAT only.
System memory of at least: Set CACHE to: Set DISKCACHE to:
16 MB+ 2048 2048
CASE 2: You use both HPFS and FAT with HPFS active and FAT
passive.
System memory of at least: Set CACHE to: Set DISKCACHE to:
16 MB+ 2048 512 -1024
CASE 3: You use both HPFS and FAT with HPFS passive and FAT
active.
System memory of at least: Set CACHE to: Set DISKCACHE to:
16 MB+ 1024 2048
<<=NOTE=>> For purposes of the table above, "active" and
"passive" are descriptors for the way a partition is used.
If it is seldom used, it is "passive." If a lot of disk
intensive I/O occurs on the partition, it is "active."
================================================================
/CRECL sets the maximum record size for caching, from 2k to 64k
in multiples of 2k with a default of 4k. This parameter may not
exceed 1/4 of the total cache size set with the /cache parameter.
/AUTOCHECK:nn tells the system to check each drive noted to see if
it was shut down properly. If not, it will run CHKDSK on only the
drives indicated.
<<=Tip=>> /C will only run CHKDSK if the file system is dirty (new);
/AuToChEcK (case-sensitive!!!) will make CHKDSK process locked drives
(undocumented).
You can speed up checking volumes situated on separate physical drives
by using something like
IFS=C:\OS2\HPFS.IFS /CACHE:2048 /CRECL:64 /AUTOCHECK:C
and then running the CHKDSK's in parallel for each physical drive:
start CHKDSK D: /F /AuToChEcK
start CHKDSK E: /F /AuToChEcK
and so on. Some have reported performance improvements of 250%.
<<=NOTE=>> If you place a plus sign (+) in front of any drive
letter, the drive will be checked every time the system starts,
even if shut down properly.
<<=WARNING=>> If you don't include the AUTOCHECK switch in this
command, the system will not boot.
/F:n indicates the level of CHKDSK to be used when automatically
checking the drives at startup when AUTOCHECK is activated. If
no parameter is specifed, /F:2 is the default.
<<=NOTE=>> A /F:3 parameter will be ingnored unless you formatted
your hard drive with the /L switch.
<<=TIP=>> If you are using only FAT partitions, then you should
REM this IFS statement and save yourself some RAM. How much?
I've seen figures from 130k to 500k, but the HPFS.IFS file is
136k in size.
<<=TIP=>> If you have drive partitions larger than 80MB, then
HPFS should give you better performance than FAT. On partitions
of less than 80MB, most authorities indicate that there is only a
small performance difference between HPFS and FAT. Consider the
following when comparing the relative merits of the HPFS versus
FAT: On large partitions of identical size, the HPFS will
generally give you about 15% more space and improve performance
by about 28%.
<<=NOTE=>> Lazy write is on by default. If you want lazy write
off, see the RUN=C:\OS2\CACHE.EXE command later in this file.
PAUSEONERROR=YES
This command tells OS/2 to pause after it finds any error in your
config.sys and displays an error message. If you don't include
this statement in your config.sys file, the default will be YES.
This is generally the best choice since the error message will
appear and scroll off the screen so quickly with a NO setting that
you may not notice it.
PROTSHELL=C:\OS2\PMSHELL.EXE
This OS/2 command tells OS/2 what program you want to use as the
protect mode shell (the program that determines what your user
interface looks like and how it operates.) This is the first
program OS/2 will execute. PMSHELL.EXE is the program which
initializes OS/2 Presentation Manager. If you delete this line
from your config.sys file, OS/2 will load PMSHELL.EXE by default.
<<=NOTE=>> There are several alternatives to PMSHELL.EXE.
One is OS/2s own CMD.EXE. If you replace PMSHELL.EXE with
CMD.EXE, you will get a full screen OS/2 session only and will
not be able to run PM programs. A second alternative is
TSHELL.EXE. TSHELL is a text-based, protected-mode shell for
OS/2. Any one remember OS/2 1.x? TSHELL makes OS/2 look
something like OS/2 1.0. OS/2 1.0 did not have a graphical
user interface.
With TSHELL you can start and switch full-screen sessions only.
These can be OS/2, DOS, or WINOS2 sessions depending on your
systems configuration. You use Alt+Esc to switch around
sessions and Ctrl+Esc to pop up the task list. But please note,
like OS/2 1.0, there is no Presentation Manager. Thus, OS/2 PM
applications will not work. You can download TSHELL.ZIP from
most OS/2 BBSs.
SET COMMAND: The SET command in the config.sys file sets up
environment variables for the entire system. These
environment variables are stored by OS/2 in memory and are
shared by any applications which calls on them.
<<=TIP=>> If you want to see what variables are set in your
system, at an OS/2 command prompt type the word SET and press
<enter>. You'll get a list like the following:
WP_OBJHANDLE=87103
USER_INI=C:\OS2\OS2.INI
SYSTEM_INI=C:\OS2\OS2SYS.INI
OS2_SHELL=C:\OS2\CMD.EXE
AUTOSTART=PROGRAMS,TASKLIST,FOLDERS
RUNWORKPLACE=C:\OS2\PMSHELL.EXE
COMSPEC=C:\OS2\CMD.EXE
PATH=C:\OS2;C:\OS2\SYSTEM;C:\OS2\MDOS\WINOS2;
C:\OS2\INSTALL;C:\;C:\OS2\MDOS;
DPATH=C:\OS2;C:\OS2\SYSTEM;C:\OS2\MDOS\WINOS2;
C:\OS2\INSTALL;C:\;C:\OS2\BITMAP;
PROMPT=$E[1;33m[$P]$G
HELP=C:\OS2\HELP;C:\OS2\HELP\TUTORIAL;
GLOSSARY=C:\OS2\HELP\GLOSS;
DIRCMD=/ON /P
IPF_KEYS=SBCS
KEYS=OFF
SOMIR=C:\OS2\ETC\SOM.IR;C:\OS2\ETC\WPSH.IR;
...
SET USER_INI=C:\OS2\OS2.INI
Tells OS/2 the name and locations of the file that contains
your desktop setup information and the options saved from
various OS/2 applications. OS2.INI is the default file name.
<<=NOTE=>> OS2.INI is a critical file for the proper operation
of OS/2 and should not be deleted or modified. It is not an
ASCII file and, if it should become damaged, cannot be modified
with an ASCII editor. You should consider backing up this file
by using the CALL lines shown in HOW TO MAKE A BACKUP COPY OF
YOUR INI FILES (if you are using CNFGINFO to view this file,
select the How To Restore..." option) or with a program such as
WPSBKUP out of the WPTOOLS by Henk Kelder. You can also use
MAKEINI.EXE, which ships with OS/2, to build a new set of INI
files. See your OS/2 documentation on how to do this.
<<=TIP=>> For editing the INI Files you can make use of Regedit/2
supplied with newer Fixpacks for Warp 4, there is also an somewhat
faster FREE Editor called mINI by Kai Evers available at
http://www1.stuttgart.netsurf.de/~kevers/
<<=TIP=>> You can also make an seperate directory for your OS2.ini,
e.g. SET USER_INI=X:\INI\OS2.INI, useful for reinstallations etc.
SET SYSTEM_INI=C:\OS2\OS2SYS.INI
Tells OS/2 the name and location of OS2SYS.INI. This file
tells OS/2 what kind of equipment your system uses. NOTE:
OS2SYS.INI is a critical files and should not be deleted or
modified. It is not an ASCII file. You should consider backing
up this file by using the CALL line shown in HOW TO MAKE A BACKUP
COPY OF YOUR INI FILES (if you are using CNFGINFO to view this
file, select the How To Restore..." option) or with a program
such as WPSBKUP, part of the WPTOOLS by Henk Kelder.
You can also use MAKEINI.EXE, which ships with OS/2, to build
a new set of INI files. See your OS/2 documentation on how
to do this.
This file remains open the entire time OS/2 is booted and
operating. It only closes upon shut down.
<<=TIP=>> For editing the INI Files you can make use of Regedit/2
supplied with newer Fixpacks for Warp 4, there is also an somewhat
faster FREE Editor called mINI by Kai Evers available at
http://www1.stuttgart.netsurf.de/~kevers/
<<=TIP=>> You can also make an seperate directory for your
OS2SYS.ini, e.g. SET SYSTEM_INI=X:\INI\OS2SYS.INI, useful for
reinstallations etc.
SET EPFINSTDIR=C:\OS2\INSTALL\
Sets the path for the IBM-Installer
<<=TIP=>> Make an own directory for the installer (e.g. SET EPFINSTDIR
=X:\INI\) use not the default and move all files like epfi* to this
directory, if you have to make an new installation of OS/2 there is an
clean way to update or delete the programms who are using the IBM-Installer
SET OS2_SHELL=D:\OS2\CMD.EXE
OS2_SHELL directs OS/2 to load the command line shell (CMD.EXE)
when you ask for an OS/2 command line from the WpS.
<<=WARNING=>> Be careful with this line, OS/2 will not start
without it.
<<=TIP=>> If you wish to run some other command line shell,
such as 4OS2, change this line and the SET COMSPEC=C:\OS2\CMD.EXE
line, substituting the appropriate EXE file for CMD.EXE.
<<=TIP=>> If you have a need to have a .CMD file invoked when
you launch any OS/2 full screen or windowed session, just as
AUTOEXEC.BAT is invoked for DOS sessions, modify this command
line as shown below and it will cause AUTOEXEC.CMD to be invoked
each time you start an OS/2 session.
SET OS2_SHELL=C:\OS2\CMD.EXE /k C:\AUTOEXEC.CMD
You can choose any file name you wish for the CMD file.
AUTOEXEC.CMD is used just as an example.
SET AUTOSTART=PROGRAMS,TASKLIST,FOLDERS,CONNECTIONS,LAUNCHPAD,WARPCENTER
The AUTOSTART command contains a list of WpS components which
will be started (or restarted) when the system is booted up.
There are currently six possible options:
PROGRAMS: Tells OS/2 to start applications, that were running
when the system was shut down, to restart. This
options will be ignored if SET RESTARTOBJECTS=NO.
TASKLIST: This parameter enables the OS/2 task list that appears
when you press Ctrl+Esc.
FOLDERS: Opens the desktop and any other folder which was open
when the system was shut down.
<<=WARNING=>> If you remove the FOLDERS statement,
OS/2 will not open your desktop (which is a folder).
CONNECTIONS: This parameter restarts any network connections
that were in use when the system was shut down.
<<=NOTE=>> This parameter can be removed if your
system is not connected to a network. Leaving it
in your config.sys file will NOT cause any problems.
LAUNCHPAD: Restarts the new Lauchpad supplied with Warp.
<<=NOTE=>> This parameter can be removed if you don't
want to autostart the launchpad.
WARPCENTER: Restarts the Warpcenter supplied new with Warp4
<<=NOTE=>> can be removed if you don't want to
autostart the WarpCenter
<<=TIP=>> It is reported that in some cases the
autostart of the WarpCenter by the config.sys crashes
the WPS. If this appears, delete WarpCenter, and
make instead an reference in the autostart folder.
See also the WarpCenter SET options in this file
<<=TIP=>> Don't use other activity monitors (e.g. like
the one delivered with Describe, or Pulse) together with
the enabled activity monitor in WarpCenter.
SETBOOT /T:5
This command lets you set up the Boot Manager in OS/2. There
are a number of switches available including:
/T:x Number of seconds that the Boot Manager menu will
remain on the screen before the default system starts. A
0 (zero) setting causes the menu to be bypassed. A NO
(as in /T:NO) causes the menu to remain displayed until
a selection is made.
/Q Queries the currently set startup environment, and
displays the default logical disk alias, timeout value,
mode, and drive letter assignments for each system index.
/X:x Sets the system startup index to indicate the partition
that the Boot Manager should start, where x is from 0 to 3.
For complete information and other switches available, refer to
the online OS/2 Command Reference.
SET RUNWORKPLACE=C:\OS2\PMSHELL.EXE
This line tells the system what interface program is to be
used. In this case it is the Workplace Shell.
<<=TIP=>> If you want to run OS/2 with only a command line
interface, you can do so by changing this line to read
SET RUNWORKPLACE=C:\OS2\CMD.EXE. This brings OS/2 up without
the WpS and gives you one screen session. You can start other
sessions using the START or DETACH command. Otherwise,
operated just like you were in DOS. If you have started more
than one session, switch between them using Alt+Esc. For those
who want the power of OS/2 and like to work only from a command
line, give this a try. I'm running in this mode as I write this
as a test and it appears to work fine.
<<=WARNING=>> You can't perform a "shut down" from a command
line. To do a shut down type PMSHELL and press enter. This
starts the WpS. Once the WpS is open, you should be able to
perform a standard shut down. You can also download one of
several shut down programs available on most OS/2 specific
BBSs. I use one called SHUT32.ZIP.
<<=TIP=>> MSHELL.EXE is another alternative. It is a simple
mini shell for OS/2 that uses the replaceable shell
architecture of the WpS. MSHELL is a program launcher which
provides one list of programs to start. This list can be
modified by creating a plain text file called MSHELL.INI. In
addition to starting programs, MSHELL can save the desktop,
interact with the spooler, and do a system shut down.
MSHELL is IBM Employee Written Software and can be downloaded
from most OS/2 specific BBSs or ftp.cdrom.com.
SET RESTARTOBJECTS=YES
This command tells OS/2 what applications to start after you
suspend operations with or without doing a shut down. If this
statement is not in your config.sys, then the default is YES,
i.e., start all objects that were running at the time of shut
down or reboot. Other options are:
NO = do not start any applications that were running at time
of shut down or reboot.
STARTUPFOLDERSONLY = start objects only in the Startup
folder. This parameter is also handy for another
purpose. Lets assume you have one or more programs in
your Startup folder and do a shut down without closing
those programs. If you have Restartobjects set to yes,
OS/2 will restart the programs left open AND the Startup
folder will start another copy of the same programs.
Thus you will have two copies running. Using this
parameter eliminates this.
REBOOTONLY = Start objects only if the OS/2 WpS is starting
from a reboot (Ctrl-Alt-Del) or at power on. Objects
will not restart if the WpS is restarted as a result of
its own error correction recycling.
<<=TIP=>> You can also circumvent the auto-starting of
programs by holding down Left/Ctrl-Left/Shift-F1 all at the
same time during boot. It must be done right after the clock
appears just before the desktop loads, but before any icons
appear.
SET COMSPEC=C:\OS2\CMD.EXE
This line identifies what OS/2 command line shell is to be used
and its location. In DOS, COMMAND.COM is equivalent to CMD.EXE.
<<=TIP=>> If you wish to run some other command line shell,
such as 4OS2, change this and the SET OS2_SHELL=C:\OS2\CMD.EXE
line, substituting the appropriate EXE file for CMD.EXE.
SET TEMP=C:\TEMP
SET TMP=C:\TEMP
Sets the directory for temporary files
LIBPATH=.;C:\OS2\DLL;C:\OS2\MDOS;C:\;C:\OS2\APPS\DLL;
Tells OS/2 where to locate Dynamic Link Libraries (DLLs).
LIBPATH is similar to DPATH and PATH, but the statement can
only be used in the config.sys file and OS/2 does not search the
current directory for DLLs unless you include it in the LIBPATH
statement. You don't need to use the SET command with LIBPATH.
It is not an environment variable.
<<=TIP=>> To reduce the search time, be sure that the various
PATH statements contain the correct path to your program and
other files. You can also have OS/2 search the current directory
by including a period "." right after the equal "=" symbol. This
causes OS/2 to look in the current logged directory first.
One final item that will reduce search time: Be certain that
the PATH, LIBPATH and DPATH statements in the config.sys are
arranged with the most frequently accessed sub directories
listed first.
<<=WARP TIP=>> With Warp, IBM has introduced the ability to
dynamically change LIBPATH using two new environment variables:
BEGINLIBPATH and ENDLIBPATH. These commands are most useful
in CMD or BATCH files, but can be used in your config.sys.
Any directories that appear in the BEGINLIBPATH variable are
searched before directories in LIBPATH, and directories that
appear in the ENDLIBPATH variable are searched after those
in LIBPATH. The correct syntax is SET BEGINLIBPATH=C:\OS2.
<<=NETSCAPE TIP=>> Netscape must be in the first place of the
Libpath, if you use Staroffice 4.0 check if thats correct, if
not move the Staroffice Path behind Netscape and install
Servicepak 2 or higher otherwise the Staroffice Browser wont
function.
SET PATH=C:\OS2;C:\OS2\SYSTEM;C:\OS2\MDOS\WINOS2;C:\OS2\INSTALL;
Just like in DOS, it tells OS/2 where to find programs. For DOS
sessions, set the PATH in your Autoexec.bat file.
<<=WARNING=>> Your path statement should contain at least the
following directories: \OS2, \OS2\MDOS, \OS2\SYSTEM.
<<=TIP=>> In Warp4 peerinst.exe doesn't work correct if the path
contains more than 256 Characters, if this happens make a copy
of your config.sys and shorten the path temporarily
SET DPATH=C:\OS2;C:\OS2\SYSTEM;C:\OS2\MDOS\WINOS2;C:\OS2\INSTALL;
This is an OS/2 command. It tells OS/2 programs where to look
for data files. It is similar to the DOS APPEND command, but
unlike APPEND, DPATH only works with programs designed to use
it.
SET PROMPT=$E[1;33m[$P]$G
Like the same DOS command, this line sets how your OS/2 command
prompt will appear. (This is for OS/2 only. Set the DOS PROMPT
default in your AUTOEXEC.BAT file.) In the setting shown here,
the command prompt will appear showing the current directory of
the default drive enclosed in [] followed by the greater than
symbol, i.e. [C:\]>. Having brackets [] around the drive and
directory information lets you quickly know when you are at an
OS/2 command line verse a DOS command line.
If you type PROMPT without a parameter, OS/2 will return its
default prompt.
Options include:
$A = will substitute the '&' character
$B = The | character
$C = The open parenthesis (
$D = Current date
$E = ASCII code 27 (escape) so you can work with ANSI.
See <<=TIP=>> below.
$F = The close parenthesis )
$G = The "greater than" > symbol
$H = BACKSPACE over the previous character
$I = Turns help line on
$L = The "less than" < character
$N = Default drive
$P = Current directory of default drive
$Q = The equal = character
$R = will substitute the returncode for the previous command
$S = The space character
$T = Current time
$V = OS/2 version number
$_ = Carriage return or line feed
<<=TIP=>> You can also add ANSI control sequences to your
prompt. For example, to help me know visually whether I'm
working with an OS/2 command line, I've add $E[1;33m to my
prompt line, i.e. SET PROMPT=$E[1;33m[$P]$G. This sets text
to display in bold yellow characters. SET PROMP=$E[30;47m
$E[K[$P] deletes the settings done by other programs and sets
text to display black on white.
SET HELP=C:\OS2\HELP;C:\OS2\HELP\TUTORIAL;
Tells OS/2 where the help files are located. OS/2 will only
look for its help files in the path shown.
SET GLOSSARY=C:\OS2\HELP\GLOSS;
Tells OS/2 where Glossary and Master Help files are located.
SET MENUSTYLE=SHORT
An undocumented SET command which controls the amount of
information presented to you when you activate a pop-up
menu. For example, the standard pop-up menu on my OS/2
desktop menu provides 13 menu items. With this SET
command in my config.sys, I only have 10 items. The items
not presented are Help, Create Shadow, and Find.
<<=TIP=>> An Great enrichment for the menues, and a lot of
other useful enhancements can be achieved by using the
FREE XFolder, by Ulrich Möller, available at http://www2.rz.
hu-berlin.de/~h0444vnd/os2.htm, current release is 0.80
SET DIRCMD=/ON /P
An undocumented command that is the OS/2 equivalent of the DIR
command in DOS. Since DOS 5, you can tell DIR how to present
file information. To do this in OS/2, use the DIRCMD command.
For example: SET DIRCMD=/ON /P tells OS/2 to display the DIR
information in alpha order and place a pause at the end of each
page.
<<=NOTE=>> This is for OS/2 only. Set the DOS default in your
AUTOEXEC.BAT file.
Options include:
/A list files with specific attributes. E.g. /AH list only
hidden files. Other options are S A & R. If you place a
negative (-) sign in front of your specified attribute,
all files will list except those with the attribute
specified. E.g. /A-H-S will display all files except
hidden and system files.
/B list directories and files without heading and summary
information.
/F list files with the full drive and path information.
Date, time and size are omitted.
/L displays information in lowercase.
/N lists files on a FAT drive in the same format used for a
HPFS drive, i.e. date, time, size, name.
/O list files according to sort option specified. Sort
options are:
G = Display directories first.
N = alphabetize by file name
-N = reverse-alphabetizes by name
E = alphabetize by extension
-E = reverse-alphabetizes by extension
D = by date, oldest first
-D = by date, newest first
S = by file size, smallest first
-S = by file size, largest first
/P pauses after a full screen of files is listed.
/R displays long file names if applicable.
/V shows the size seperated by an point e.g 1000.000kb
/S searches and displays all directories.
/W displays file names across the screen. Date, time and
size are omitted.
<<=TIP=>> If you install Lotus SmartSuite 96 from a CDROM under WARP 4
it will hang at about 85%. You can load the word processor separately
but Freelance Graphics causes the hang. Lotus told that the cure was to
REM out the SET DIRCMD= line in the config.sys, reboot, install, remove
the REM and reboot.
SET SHELLHANDLESINC=nn
This will increase the number of available filehandles, default 20, for
the SHELL process with the specified number 'nn'.
This setting is also inheritted by child-processes and can avoid some
out-of-handles errors.
<<=Note=>> This became more important because the later (Workplace) shell
keeps more handles open for its own use, leaving less for started processes
to open. This has caused problems in several compiler/build environments.
LASTDRIVE=H
Specifies the maximum number of drives that are accessible.
The value you specify with LASTDRIVE represents the last valid
drive that is recognized.
SET IPF_KEYS=SBCS
The character set for most languages can be represented as data
using an 8-bit byte since their characters sets are each less
than 256 characters. These are called single-byte character sets
(SBCS). Languages such as Japanese (Kanji), Korean and Chinese
(both Traditional and Simplified) can only be represented using
two 8-bit bytes or 16-bits. These are double-byte character
sets (DBCS).
This command tells the Information Presentation Facility (INF
and help files) which type of character set is being used, i.e.,
Single or Double Byte Character Set. This is an environment
variable. Removing it from my system did not seem to have any
impact.
SET SCKILLFEATUREENABLED=1
ON, does the same as 1
Allows to kill misbehaving programs with a Ctrl/left click on the WarpCenter
task list (second button from the left)
SET SCKILLCONFIRMDISABLED=1
ON does the same as 1
Disables the the security question for the kill feature in Warpcenter
use with care !
SET SCFINDUTILITY=C:\OS2\APPS\PMSEEK.EXE
Replaces 'find objects' in WarpCenter by a faster and more useful program
SET SCUSEPRETTYCLOCK=1
ON does the same as 1
Changes the appearance of the WarpCenter clock
SET MENUSFOLLOWPOINTER=ON
Enables cascading menus in Warpcenter like in Windows 95
SET PM_ASYNC_FOCUS_CHANGE=ON | ON x | OFF
WARP 3 only, in Warp 4 these settings can be
found unter [Systemconfiguration, System] on your Desktop
The "SIQ" feature is new with FixPak XR_W017. It allows the user to
take focus away from an application that is monopolizing the message
queue. When the FixPak is installed, the SIQ feature is disabled
(OFF).
The parameters to the SET command are:
The default is OFF (disabled).
To turn it on (enable) put the following in the CONFIG.SYS file and
reboot:
SET PM_ASYNC_FOCUS_CHANGE=ON
To change the timeout value put the following in the CONFIG.SYS file
and reboot:
SET PM_ASYNC_FOCUS_CHANGE=ON x
where x is in milliseconds (default is 2000 (2 seconds))
SET QUEUE_SIZE_THRESHOLD=x
Warp3 only (since FixPak 17), in Warp 4 these settings can be
found unter [Systemconfiguration, System] on your Desktop
puts the size of the message queue to x. Default was 100 prior
to Fixpack #17, and 3000 from it.
SET PM_DYNAMIC_DRAG=ON
Warp 3 only (since FixPak 17), in Warp 4 these settings can be
found unter [Systemconfiguration, System] on your Desktop
enables (=ON) or disables (=OFF, default) the full window drag
for PM windows. Don't use it with slow graphic cards.
PRIORITY_DISK_IO=YES
This command determines whether programs running in the fore-
ground have priority access to disks. The default is YES. If
you want a program running in the background, like a BBS, to
have equal access to your disks, then change this statement to
NO. If you change this command to no and then find that your
communications program does not work, change back to yes.
PRIORITY=DYNAMIC
OS/2 automatically assigns processing priorities to each thread
of a program as it begins processing. A thread running in the
foreground will generally have priority over a thread running
in background. Thread priorities are adjusted, generally based
upon how active they are, by OS/2 on an ongoing basis to make
sure each thread has adequate processing time. On the rare
occasion that you need to run a program which must never change
in priority, you should set PRIORITY=ABSOLUTE, otherwise, don't
mess with it.
<<=NOTE=>> This command does not have to be in your config.sys.
If it isn't, OS/2 defaults to PRIORITY=DYNAMIC.
"To summarize: The highest priority thread always has the
machine. If there are two equally high threads, they timeslice
having the machine. Note that there are many Operating System
threads, like the scheduler itself, that are higher priority
than any program. Now, if PRIORITY=ABSOLUTE in the config.sys
file, that's all there is to it. But usually, PRIORITY=DYNAMIC,
and OS/2 keeps gradually increasing the priority of a starved
thread until it gets to run. Maxwait determines the maximum
time, in seconds, before the scheduler intervenes to raise a
low priority thread up high enough to run."
FILES=20
This is a standard DOS command which sets the maximum number
of files that DOS can access at the same time. OS/2 sets the
install default is 20, but some DOS programs may require an
increased number. The maximum parameter is 255. The FILES
command is for DOS only and has no effect on OS/2 sessions
which can have up to 64,000 files open at the same time.
DEVICE=C:\OS2\TESTCFG.SYS
DEVICE=C:\OS2\BOOT\TESTCFG.SYS <---- In Warp
TESTCFG.SYS is used during the install process to test your
systems configuration. It is also used by the Selective Install
process and during device driver installations.
<<=NOTE=>> Because this driver is used by the Selective Install
process, it should not be deleted.
DEVICE=C:\OS2\DOS.SYS
DEVICE=C:\OS2\BOOT\DOS.SYS <---- In Warp
A device driver used to communicate between DOS and OS/2
applications running on the same system.
DEVICE=C:\OS2\PMDD.SYS
DEVICE=C:\OS2\BOOT\PMDD.SYS <---- In Warp
OS/2 loads and uses this driver to provide pointer draw support
along with POINTDD.SYS.
<<=WARNING=>> OS/2 will not start without this line in your
config.sys file.
DEVICE=C:\OS2\BOOT\PAUSE.SYS /w:NNN
where: NNN = seconds to wait (default = 30 seconds)
Pauses the config.sys for an given time
Useful for maintenance purposes
the driver can be found at the IBM Device Driver Pak Online site.
<<=TIP=>> Together with BASEDEV=IBM1S506.ADD the /W switch does
the same
BUFFERS=30
Tells OS/2 how many disk buffers to set aside. Range is from 3
to 100. Each buffer takes up to 512 bytes of RAM. The install
default usually works well. If you are using HPFS only, see
<<=Tip=>> below.
Disk buffers are blocks of memory set aside by OS/2 for use in
reading and writing blocks of data. For example, if a program
wants to change 80 bytes of a file, it needs to read the 512
byte sector that contains the original data, change the infor-
mation and then write the corrected 512 byte sector back out.
A "buffer" is the 512 byte temporary staging area for this
partial sector operation. According to a source at IBM, "OS/2
allows multiple simultaneous I/O operations to be queued up for
both diskette and hard disk. Each 'concurrent' operation may
need a buffer. If there are not enough buffers, overlap can be
inhibited. Because OS/2 has more 'simultaneous' queued I/O
than DOS, it needs more buffers."
<<=TIP=>> Generally, if you are running FAT on one or more of
your hard drives, you can speed up your system by increasing
the number of BUFFERS. But, keep in mind that as you increase
the number, you reduce available memory. Be careful about using
a lower number unless you only have 4MB of RAM. With 4MB of RAM
you may wish to set BUFFERS to 20.
<<=TIP=>> If you are using only HPFS (i.e., no FAT partitions),
try setting BUFFERS to 3. With HPFS you generally don't need
BUFFERS. Remember that 3 is the minimum parameter. If you set
BUFFERS to 1 or 2, OS/2 will default to 30 since 1 and 2 are out
of range. There is one exception to this tip. If you access
your floppy disks a lot, then a reduced BUFFERS setting could
impact floppy performance.
IOPL=YES
When set to YES, this command lets programs that need to bypass
OS/2 (and its device drivers) and work directly with hardware
devices, to do so. One example is Lotus 123/G. YES means
that all programs can access the hardware directly. NO means
that no program can access the hardware directly. YES is the
default and is generally best, since its hard for most of us to
know when a program is written is such a way as to need direct
access to hardware.
IOPL stands for Input/Output Privilege Level.
<<=TIP=>> You can also specify a list of programs that are
allowed to work directly with the hardware. For example,
IOPL=WS.EXE,123.EXE would allow only these two programs to
access hardware directly.
RUN=C:\OS2\CACHE.EXE /MAXAGE:7500 /DISKIDLE:60000 /BUFFERIDLE:60000
This line runs CACHE.EXE which allows you to modify the
parameters for the HPFS cache. CACHE.EXE is only used for
HPFS partitions. (The DISKCACHE command sets up a cache for
FAT.) There are four switches for CACHE.EXE:
/LAZY: Determines if lazy writes is ON or OFF, that is,
whether the contents of the cache will be written to your
hard disk immediately (/LAZY:OFF) or when your hard disk
is idle (/LAZY:ON). The default is ON. I like lazy
writes ON because it improves performance, but keep in
mind that since the system delays writing data to your
hard disk, you can lose data if your system should crash.
In the config.sys file line above no switch is specified
therefore the default remains in effect, which is ON.
<<=TIP=>> Lazy writes can also be turned ON or OFF at an
OS/2 command prompt.
<<=WARNING=>> If you include the /LAZY switch, then the
CACHE statement will IGNORE ALL OTHER SWITCHES in the
line. Therefore, if you want to turn lazy writes off (or
on) and also change some other parameter, you will need
two RUN statements.
<<=TIP=>> This conform with all online
document i've read for OS/2. But it is not true. On my
system I have a line RUN=D:\OS2\CACHE.EXE /LAZY:12
/BUFFERIDLE:60000 /DISKIDLE:60000 /MAXAGE:64000 /READAHEAD:1
And it works very fine. Trying to separate this line into
two statements causes my system to stop during boot with
the message "please press a key to continue".
<<=WARNING=>> There is a bug in OS/2 version 2.1 which
does not appear to have been fixed in Warp. You
can't turn lazy writes off from the config.sys file. The
WpS always turns lazy writes ON when it loads regardless
of what your CACHE.EXE command sets. So, if you want lazy
writes off, you will need to run the CACHE command AFTER
the WpS starts. Create a CMD file to turn it off and place
it in your Startup folder. The WpS has already done it's
thing when the objects in the Startup folder are opened.
You can also turn it off from a command prompt.
/MAXAGE: Sets how long data waits in the cache before it is
moved to another area of the cache where less used
information is stored, or how long data waits in the
cache before it is written to the hard disk. It is
expressed in milliseconds. The default is 5,000 or about
5 seconds. In the config.sys file line above, the wait
is set at 7,500 milliseconds or about 7 1/2 seconds.
/DISKIDLE: Sets how long your hard disk must be idle before
it will accept data from the cache. Express in
milliseconds and the default is 1,000 or about one
second. The minimum value must be greater than the value
specified in the BUFFERIDLE parameter. In the config.sys
file line above no switch was specified so the default
remains in effect.
/BUFFERIDLE: Sets how long the cache buffer must be idle
before its contents MUST be written to your hard disk.
Express in milliseconds and the default is 500 or about
1/2 second. In the config.sys file line above no switch
was specified so the default remains in effect.
According to one source at IBM, there are two other
undocumented parameters.
/DIRTYMAX: The threshold number of dirty buffers before
immediately flushing of least recently used (LRU) data
blocks.
/WRITECACHE: The threshold number of bytes that HPFS will
cache for a lazy write.
<<=NOTE=>> The HPFS IFS config.sys file line sets up the
cache and uses the system defaults. This config.sys file
line is only used to modify the cache parameters.
<<=TIP=>> You can check to see what parameters the HPFS cache
is currently set at by going to an OS/2 command prompt and
keying in the word CACHE and pressing the enter key.
<<=TIP=>> Table 2.0 contains information on optimum settings
for each of the main parameters.
========================= Table 2.0 ===========================
Parameters: LAZY WRITES /LAZY:ON
MAXAGE >7,500
DISKIDLE 60,000
BUFFERIDLE 60,000
===============================================================
<<=TIP=>> Warp 4 Cache info direct from "Mr HPFS" Doug Azzarito of
IBM - Austin
Doug: CACHE.EXE shouldn't be used in CONFIG.SYS, it should be put
in STARTUP.CMD. If you type CACHE ? you will see:
The specified option, ?, is incorrect.
Correct usage: cache [OPTIONS]
where OPTIONS is one or more of:
-DISKIDLE:n Sets disk-idle time before write to n
milliseconds.
-MAXAGE:n Sets maximum age of cache buffer to n
milliseconds.
-BUFFERIDLE:n Sets buffer idle time to n milliseconds.
-Lazy:ON|OFF|n Turns lazy writing on, off or set to 'n'
lazy writers.
-READAHEAD:ON|OFF|n Turns read ahead on, off or set to 'n'
read ahead workers.
The new parameters are LAZY:n (in Warp 3 it only allowed ON & OFF)
and -READAHEAD. The -n in READAHEAD isn't used, but will accept 0
or 1, and turn that into an ON or OFF.
Ron: Do you know of the /DirtyMax and /WriteCache switches?
Doug: They're not very useful - I use them in testing only.
The DIRTYMAX switch sets a maximum number of dirty buffers -
if this limit is reached, the lazy-writer wakes up and cleans
up the cache. It is set at 80% of the cache.
WRITECACHE is a parameter that sets the maximum size of a WRITE
that will be put in cache. It is set to the maximum size of a
write operation (64K).
DISKCACHE=D,LW,32,AC:CD+E
If you are using one or more FAT partitions on a hard drive,
this command sets up a disk cache for those partitions. The
default cache size used by OS/2 during installation is based on
how much RAM your system contains. See Table 3.0. The minimum
cache size is 64k and the Maximum FAT cache size is 14MB.
<<=IMPORTANT NOTE=>> Under Warp, during installation the
letter "D" is used instead of the usual numeric value. On the
"nets", several users have reported that their disk I/O was
significantly reduced when they replaced the "D" with a value
as was the case in OS/2 2.x. I suggest you change this setting
based on the optimum cache sizes as shown in Table 1.1 above.
If you leave the "D" setting, then OS/2 will set your FAT
diskcache based upon the amount of RAM you have as follows:
7 or 8MB of RAM, "D" is set to 512k; and
more than 8MB, "D" is set to 10% of RAM.
<<=NOTE=>> This command is for hard drives only. DISKCACHE
does not cache FAT based floppy drives.
<<=TIP=>> If you have the RAM, increase the size to improve
system performance, but don't get carried away by using to much
of your RAM; this can hurt performance. See the information on
optimum cache sizes contained in Table 1.1 which is repeated
below.
<<=TIP=>> If you are only using HPFS, then you should REM
this statement and save 64k of RAM (don't delete, you may need
or want it later). If you have a FAT partition on your hard
drive and you REM this statement, OS/2 will automatically set
up a 64k cache by default.
========================= Table 3.0 ===========================
If you have formatted your hard drive(s) with only FAT partitions,
the default cache size in this statement will be that noted under
ONE FILE SYSTEM. If you have both FAT and HPFS partitions,
then OS/2 defaults to the cache size noted under TWO FILE SYSTEM.
The file system which uses the greatest amount of your disk space
gets the larger default value.
MEMORY SIZE IN MB TWO FILE SYSTEM ONE FILE SYSTEM*
10 - 16 512/512 1024
17 - 32 1024/1024 2048
* Defaults in Warp are different and are shown as the second
number. On systems with more than 8MBs of RAM, the default
is 10% of available RAM to a maximum cache of 4MB.
<<=TIP=>> See the end of the file for an detailed discussion how
to set the cache for less powered systems.
===============================================================
LW: Enables lazy writes. If you don't want lazy write enabled,
then remove ",LW".
<<=NOTE=>> Lazy-writing provides significant performance
improvements to your system. If you disable this feature, the
performance of your system will suffer.
32: Sets the threshold size. It is express in number of sectors
which are 512 bytes each. Data requests from your disk that are
larger than this number will not be cached. The default is 4.
Thirty two (32) is said to be an optimum number. One hundred
twenty eight (128) is the maximum allowable. This setting has
no impact on RAM.
AC:CD+E: If you want CHKDSK to automatically check any partition
after an improper shut down, then add this switch to end of the
DISKCACHE command: AC:n where n is the partition(s) to check,
e.g. AC:C. If you add a + (plus) sign before any drive letter,
OS/2 will automatically run CHKDSK on that drive each time
you boot.
=================== Table 1.1 Repeated ========================
You can get better performance from your system by using your
available RAM in the most efficient and effective way. Select
the case that best describes the file system or amount of RAM
you use.
CASE 1: You use only HPFS or only FAT, but not both.
HPFS only. FAT only.
System memory of at least: Set CACHE to: Set DISKCACHE to:
16 MB+ 2048 2048
CASE 2: You use both HPFS and FAT with HPFS active and FAT
passive.
System memory of at least: Set CACHE to: Set DISKCACHE to:
16 MB+ 2048 512 -1024
CASE 3: You use both HPFS and FAT with HPFS passive and FAT
active.
System memory of at least: Set CACHE to: Set DISKCACHE to:
16 MB+ 1024 2048
<<=NOTE=>> For purposes of the table above, "active" and
"passive" are descriptors for the way a partition is used.
If it is seldom used, it is "passive." If a lot of disk
intensive I/O occurs on the partition, it is "active."
===============================================================
MAXWAIT=3
This command sets the longest period a program will have
to wait to execute before OS/2 ups its priority. This makes
sure that no program is put on hold forever while some other
program hogs the system. You can set MAXWAIT from 1 to 255
seconds. The default is 3 seconds.
<<=TIP=>> When running heavy background programs, such as a
BBS, change the setting to 1, i.e. MAXWAIT=1. This will keep
the BBS software or other background programs running at top
speed. For general use, it appears that setting MAXWAIT=2
makes the system a little livelier.
<<=NOTE=>> MAXWAIT only has an effect if PRIORITY=DYNAMIC.
<<=NOTE=>> The smaller the number you use, the more system
overhead there will be.
MEMMAN=SWAP,PROTECT
OS/2 can run more programs and use more data than can actually
be stored in memory at any given time. This is done by swapping
large amounts of memory to your hard disk and then reading the
data back into memory when needed. This is called virtual memory.
For example, if you have 4MB of memory you will see lots of disk
activity while you are working with your system. A lot of this is
OS/2 swapping memory to and from your hard disk. Lots of memory
swapping slows down your system and can cause your hard disk to
fragment quicker than normal.
The MEMMAN command controls the swap process. The syntax is
MEMMAN=s,m,PROTECT,COMMIT where s=SWAP or NOSWAP; m=MOVE or NOMOVE.
The default is to have virtual memory on. To turn off virtual
memory, which is NOT recommended, the config.sys file line should
read: MEMMAN=NOSWAP. See <<=CAUTION=>> below.
PROTECT allows the allocation and use of protected memory for
certain DLLs. This is done to protect those DLLs from being
trashed by an errant program. Unless you are a programmer who
needs this set to NOPROTECT, leave the default.
<<=NEW PARAMETER=>> A new parameter with version 2.1 is COMMIT.
With this parameter included, OS/2 will allocate space in the swap
file whenever a program commits memory, i.e., a page in the swap file
is allocated for every page of memory committed by a program, even
if the data never actually gets swapped out. Your system should be
more stable, but it will be slower also, since your swap file will
grown when it doesn't have to. If you use this parameter, increase
the size of your SWAPPER.DAT file (see SWAPPATH line below) by
the amount of memory you are likely to use when using the COMMIT
parameter. Most people "in-the-know" suggest that COMMIT not be
used unless it is required by 16-bit OS/2 applications.
<<=TIP=>> You can also use the COMMIT parameter another way.
Without COMMIT set, the minimum free noted in you SWAPPATH
specified the point at which OS/2 gives you a message warning that
your disk space is running low. When you set COMMIT, the minimum
free value noted in your SWAPPATH statement becomes the amount of
hard disk space that will always remain free on the swap file
partition. Thus, with COMMIT set, you can never run out of disk
space on your swap file partition.
<<=CAUTION=>> When messing with the MEMMAN line, I changed it to
MEMMAN=NOSWAP. As a result, I had to boot from my OS/2 installa-
tion disk and recover my backup config.sys file to get the system
to boot. According to Blake Stover, "The reason MEMMAN=NOSWAP,
PROTECT chokes is because of the hat tricks OS/2 does while
loading the WpS, Desktop, Bitmaps, Folders, Cache buffers, MMPM/2,
etc.. OS/2 likes to load all of these, then swap or discard the
inactive code. If there is no where to swap to it dies during
boot, unable to initialize the resources it needs. NOSWAP,PROTECT
should only be used for boots from floppy to do maintenance, in
most cases. (People who use TSHELL on a machine with a good
amount of RAM may also use it to speed operations). IBM does
not recommend that you set MEMMAN to NOSWAP unless you have more
than 8MB of RAM.
<<=NOTE=>> The MOVE/NOMOVE parameter is only provided for
OS/2 1.x compatibility.
<<=NOTE=>> NOPACK PARAMETER. When OS/2 initially loads a 16-bit
OS/2 application, it packs the segments into pages and copies
them to the swap file for faster recovery when needed. This can
be disabled by using the NOPACK option on the MEMMAN line. How-
ever, the performance decrease and larger working set will rarely
offset the potential of a reduced swap file size.
<<=NOTE=>> DELAYSWAP. No information at this time. SWAPDOS and
NOSWAPDOS parameters from OS/2 1.x are not valid in OS/2 2.0 and
later.
SWAPPATH=C:\OS2\SYSTEM 512 4096
OS/2 can allocate more memory than it actually has available.
It does this by swapping memory to a hard disk file called
SWAPPER.DAT.
The syntax is SWAPPATH=DRIVE,PATH,mmm,nnn where DRIVE,PATH is
the location where you want the SWAPPER.DAT file to be placed and
mmm is a number from 512 to 32767 which specifies how large the
SWAPPER.DAT file can grow before it stops consuming hard disk
space. The size is stated in the negative. In other words, if
you have the mmm set to 512, then the SWAPPER.DAT file can grow
until there is only 512k left on your hard disk. The variable
nnn is the starting size of the SWAPPER.DAT file.
<<=TIP=>> When your swap file grows beyond the initial size you
have specified, OS/2 starts to manage the swap file. This
increased overhead can negatively impact your systems performance.
Therefore, if your swap file always exceeds its initial size,
consider increasing the files initial size. For example, if your
swap file usually grows to 8MB, set the initial size of 8MB.
<<=TIP=>> Normal operation of OS/2 can involves considerable
disk activity as operating system functions are loaded and pages
are moved in and out of the swap file. Here are a couple of tips
to improve performance. (1) Consider dedicating a separate
partition for the swap file. This helps avoid fragmentation of
the swap file, because other files will not be added or deleted
from the dedicated partition. (2) If you have both FAT and HPFS
partitions, put the swap file on the HPFS partition to take
advantage of the better performance of HPFS. (3) If you have a
system with two hard disk controllers, put the swap file on a disk
managed by the least used controller. (4) Keep your swap file on
the MOST used partition of the LEAST used hard drive.
<<=WARNING=>> Never put your swap file on a networked drive.
<<=NOTE=>> Your swap file will grow (in 1MB increments), but it
also shrinks when two conditions are met. One, when the amount
of free space in the swap file is greater than 1.5MB, the swap
file will be compressed during system idle time. (It will not
shrink if there is a constant "hit" on the drive by a program such
as a swap file monitor.) Two, during the compression, free space
is moved to the end of the swap file. When this free space at the
end of the swap file exceeds 1MB, the swap file will be shrunk.
<<=NOTE=>> See the discussion of the new COMMIT parameter for the
MEMMAN config.sys line including the <<=TIP=>>.
<<=WARP NOTE=>> Your swap file in Warp will be larger than in
earlier versions of OS/2. This is normal. The most significant
change that has been made is how system DLL's get loaded and what
is now valid data for swapping. System DLL's include: DISPLAY,
SOM, PMMERGE, PMWP, DOSCALL1, PMATM, PMMLE, IBMDEV32, PMCTLS,
PMSPL, IBMVGA32, PMGPI, and PMVIOP.
In the previous versions of OS/2, dll code was never copied to
the swapper file. In WARP, code for system dll's can be written
to the swapper file and, in adition, during boot, PMMERGE,
DOSCALL1, PMGPI, PMWP and PMVIOP will be swapped out. This
means that there will be an overall increase in swapper size.
This was done to increase overall system perfomance.
BREAK=OFF
For DOS programs only. Many DOS programs can be stopped by
holding down the Ctrl key and then pressing the Break key.
BREAK controls how quickly DOS programs stop when you interrupt
them with the Ctrl+Break sequence. If BREAK=OFF, DOS will stop
the program only when the programs next reads a character from
the keyboard or writes to the screen or printer. With BREAK=ON,
DOS will check for the Ctrl+Break on a more frequent basis.
Remember that this extra checking can make your DOS programs run
slower.
THREADS=256
OS/2 programs can have several different processes running at
the same time. These are called threads. This command sets
the maximum number of threads (from 32 to 4095 in OS/2 2.x and
from 64 to 4095 in Warp 3) that OS/2 can run at the same time.
If this command is not included in your config.sys file, OS/2
will default to 64. Jim Gilliland commented on what happens
if OS/2 runs out of Threads: "If an application tries to start
a new thread, and OS/2 has all of its threads already in use,
then OS/2 will generate an error. It may result in a popup, or
it may return the error information to the application."
<<=TIP=>> If you have more than 8MB of RAM and run lots of OS/2
specific programs, you may be able to improve system responsive-
ness by increasing the number of threads. Why? Because well
written OS/2 programs will use threads to improve program per-
formance. Therefore, the more well written OS/2 programs in use,
the more threads that could be needed. But still keep in mind
that this only holds true only when you are using a fair number
of OS/2 specific programs at the same time. Even when I opened
the Enhanced Editor, AmiPro for OS/2, ZOC, and KWQ Mail/2, I was
only using 57 threads. The most threads I've ever recorded at
one time was 76.
<<=SERVER NOTE=>> On a server it is generally considered better
to have 512 threads.
PRINTMONBUFSIZE=2048,134,134
This command sets the size of the print buffers for your
parallel ports. The syntax is PRINTMONBUFSIZE=LPT1,LPT2,LPT3
where LPT1 is the buffer size for the parallel port LPT1, LPT2
is the buffer size for LPT2 and LPT3 is the buffer size for
LPT3. The default and minimum is 134 bytes and the maximum is
2048 bytes.
<<=Note=>> You must define a buffer for LPT2 and LPT3 even if
you don't use these ports. You will get an error message at
start up if you don't.
<<=TIP=>> You may be able to improve printer throughput by
increasing buffer size. I have my LPT1 set to 2048. On systems
with less than 6MB of RAM, don't increase the size of these
buffers.
<<=TRIVIA=>> Ever wonder where IBM got a parameter like 134?
I did and Lynn Nash passed along the following in response to
my question:
"Obviously you have no background on the big iron or it has
disappeared into historical memory :-).
"Mainframe line standard of 132 columns plus 2 for carriage
return and line feed characters. That is why all the wide
carriage dot matrix printers also had 132 column lines, to be
able to use that wide green bar paper. Anyone that had an early
Okidata 83 dot matrix even had an electronic format tape, but
that is a story for another time."
COUNTRY=001,C:\OS2\SYSTEM\COUNTRY.SYS
Customizes your system for the country you wish to use. It
establishes which defaults to use when it comes to decimal
separators, date and time formats, currency symbols, etc. The
syntax is COUNTRY=xxx,PATH,FILE NAME. xxx is a three-digit code
number that tells what country to use. The number is usually
(but not always) the same as the international telephone dialing
prefix for the country desired. If in doubt consult your OS/2
online-reference.
SET KEYS=OFF
When using the command line, KEYS tells CMD.EXE whether to
remember previous keystrokes so they can be recalled with the
up arrow key. OS/2 maintains a 64k buffer for storing
keystroke history. KEYS can be ON or OFF. To find out
whether KEYS is on or off, simply type KEYS without a
parameter from an OS/2 command prompt. To list all of
KEYS commands, type KEYS LIST.
<<=NOTE=>> With KEYS=ON, ANSI extended keyboard sypport in
OS/2 sessions will be disabled by the system.
SET SOMIR=C:\OS2\ETC\SOM.IR;C:\OS2\ETC\WPSH.IR;C:\OS2\ETC\WPDSERV.IR;SOM.IR
SOM is an acronym for IBMs System Object Model. OS/2s object
orientation is based upon this technology and in Warp, the
Workplace Shell is built on SOM Version 2 with Distributied
SOM enabled. This SET statement sets the path to various IR
files.
SET SOMDDIR=C:\OS2\ETC\DSOM
SOM is an acronym for IBMs System Object Model. OS/2s object
orientation is based upon this technology and in Warp, the
Workplace Shell is built on SOM Version 2 with Distributied
SOM enabled. This SET statement sets the path to the DSOM
directory.
SET DELDIR=C:\DELETE,512;
To use OS/2s UNDELETE command, you must first establish a
directory to store the deleted files. To do this, create
a directory called DELETE on each partition you have and then
remove the "REM" from this config.sys file line.
This command points OS/2 to the directory you created to place
deleted files in. It also indicates the maximum K bytes of
files that will be stored in the DELETE directory. If the
number of deleted files exceeds the maximum K bytes that you
specified, then files are automatically removed from the
directory on a first-in-first-out basis.
<<=WARNING=>> Using this command will have an impact on system
performance. File operations in particular will be slower.
I don't recommend the use of DELDIR at all.
<<=TIP=>> Better make use of the File Phoenix 1.35 by Joe
DiAdamo an FREE IBM EWS Tool available at many servers and bbs.
<<=TIP=>> There is also an McIntosh like Trashcan by Kai
Sommerfeld (with sounds, bells and whistles), and FREE
ones by Andrea Henicke and Mark Kimes (unfortunately with
very ugly icons that can't be substituted, they also don't
seem to work correct together with Warp 4)
SET HOSTNAME=xyz.ab
Sets the variable for the Hostname
SET USE_HOSTS_FIRST=1
Enables the loopback-interface needed by many programs (e.g. Visual
Age for Java, XFREE86) or if an nameserver works in your LAN.
You also have to edit the file x:\mptn\bin\setup.cmd and insert
after all other 'ifconfig' statements the line
'ifconfig lo 127.0.0.1', then generate an file named 'hosts' in the
directory x:\mptn\etc or x:\tcpip\etc and insert 127.0.0.1 localhost;
the correct directory can be found out by typing the command
'echo %etc%' at an command line
<<= TIP =>> the necessary configuration can also be done by using the
TCP/IP Notebook.
SET LOTUS_BROWSER=X:\Path\Browser.exe
To make Lotus Freelance for Warp 4 use the web browser you want
you'll need to set this, otherwise Netscape will be used
BASEDEV=
BASEDEV installs a base device driver used by OS/2 when it is first
started. The statement cannot contain either a drive or path
because OS/2 cannot process such information at the stage at which
these statements are loaded. These base device drivers include
(not all delivered or available drivers are listed):
PRINT01.SYS supports attached printers on non-Micro Channel PC's.
PRINT02.SYS supports attached printers on Micro Channel PC's.
IBM1FLPY.ADD supports diskette drives on non-Micro Channel PC's.
IBM2FLPY.ADD supports diskette drives on Micro Channel PC's.
IBM2SCSI.ADD supports SCSI disk drives on Micro Channel PC's.
OS2SCSI.DMD supports non-disk SCSI devices.
IBM1S506.ADD supports non-SCSI disk drives, non-Micro Channel PC's.
OS2DASD.DMD is a general purpose driver for disk drives.
IBM2ADSK.ADD supports non-SCSI disk drives on Micro Channel PC's.
IBMINT13.I13 supports non-Micro Channel SCSI adapters.
OS2CDROM.DMD supports CD-ROM drives.
FD16-700.ADD support driver for Future Domain 16xx SCSI.
FD8XX.ADD supports Future Domain FD8XX devices.
AHA154X.ADD supports SCSI on Adaptec 1542C controllers.
AHA174X.ADD supports SCSI on Adaptec 1742 controllers.
OS2ASPI.DMD Adaptec ASPI support.
AIC7870.ADD supports SCSI on Adaptec 7870 controllers (e.g. 2940)
ULTRA14.ADD supports Ultrastor SCSI controller.
XDFLOPPY.FLT supports IBMs 1.8mb OS/2 installation disk format.
AUTODRV2.SYS supports PCMCIA modems.
ICMEMCDD.SYS & ICMEMMTD.SYS supports PCMCIA flash memory.
PCM2ATA.ADD supports PCMCIA ATA devices.
OPTICAL.DMD New with Warp4 Support for Optical devices like MO
RESERVE.SYS New with Warp4, for not PnP aware adapters; see tip
TIMER0.SYS New with Warp4, Harware timer for correct sound timings
CHKDSK.SYS New with Fixpaks supports large disks
ATAPI.FLT New with Fixpaks supports Removable Media like Zip100, LS120
CMPXCHG8.SYS New with Fixpaks fixes the Pentium F00F bug
MWDD32.sys 32-bit device driver support by Matthieu WILLM
(Win32-OS/2 and many IFS's rely on it)
<<=TIP=>> Try adding the following switches to the
BASEDEV=IBM1S506.ADD line: BASEDEV=IBM1S506.ADD /A:0 /U:0 /SMS,
and use /V (/V=verbose) to see if the /SMS works. This will
improve performance on those IDE drives that support the SMS
feature. It will not work on all IDE drives, but it will not
damage anything either. See your Command Reference INF file
for more information on these and other parameters for this
driver. If you have problems with the busmuster feature in
newer versions of IBM1S506.ADD (this occurs e.g. on some
Thinkpads) disable the feature by adding !BM. In newer versions
there is also the /W switch, it pauses the config.sys after
displaying the verboses.
<<=TIP=>> If you wish to prevent users from using the
floppy drives under OS/2 (to keep them from loading non-
authorized programs or in a workstation situation), REM the
BASEDEV=IBMxFLPY.ADD line (where x is 1 for ISA and EISA
machines, or 2 for Microchannel).
<<=NOTE=>> In Warp, the install program may have placed both
IBM1FLPY.ADD and IBM2FLPY.ADD BASEDEV drivers in your
config.sys. Remove IBM2FLPY.ADD if you don't have a Micro
Channel PC.
<<=WARP TIP=>> With Warp, the default transmission protocal use
by PRINTO1.SYS and PRINTO2.SYS is the polling transmission
method. The protocal used by previous versions of OS/2 was the
interrupt transmission method. In Warp, you can change back
to the interrupt method by adding the /IRQ switch.
<<=TIP=>> From Paul Kurr: "Since I'm running on a LAN at work
here, I have no need for direct printer support of any kind since
this is taken care of by my NOS (LAN Server). So I have REM'd
BASEVEV=PRINT01.SYS to save some RAM."
<<=Tip=>> By Sam Detweiler: "for adapters that are not PnP and do not
have a legacy detector, one can use the DOCUMENTED approach of adding
a BASEDEV=RESERVE.SYS /p:2e8,8 to the config.sys and re-running hard-
ware detection at the next boot. It causes the reserve.snp to pre-
allocate the defined resources so that PnP adapters can't use them.
<<=TIP=>> If Warp doesn't recognize the AIC7870 Driver add the
parameter /A:n n=Number of Controller and /TAG:n n=number of
PCI-Slot to AIC7870.ADD
<<=TIP=>> By Paul F.Grobler: The tablet / enhanced mouse driver by
M. Finney was broken by the GA code of Merlin but i found a work-around.
The symptoms i got was an error free driver load (including vmouse.sys),
a mouse cursor on the first graphic mode screen but the mouse pointer
was static ie it would not move. All that was required was to put
a "basedev=reserve.sys /IO:3f8,8 /IRQ:4" as the first line of my config.
sys. You will note that the values correspond to normal com1 as this is
were my tablet is connected. By modifying the values to /IO:2f8,8 and
/IRQ:3 this should work for com2.
<<=TIP=>> If you want to use SCSI Hardisks together with (E)IDE-Disks
and to boot from SCSI first, make sure that the SCSI-Drivers are in
front of the IDE-Drivers (normally IBM1S506.ADD).
<<=TIP=>> After installation you can put an REM in front of the
XDFLOPPY.FLT, as it's only needed for the installation disks and
Fixpak disks.
<<=TIP=>> If you have removable media drives (MO, IOMEGA, SYQUEST
and others) look at http://rheooptik.fmf.uni-freiburg.de/www/faq/
remmedia.htm for an detailed removable media FAQ.
<<=TIP=>> If you are using RSJ CD Writer 2.59 or above you may
add the parameter /ALL to BASEDEV=OS2ASPI.DMD.
After booting your machine, the recorder will be usable as a standard
CDROM drive, and you will nevertheless be able to attach the CD to our
filesystem. But please ensure that you're not using the CDROM drive
letter at the same time when the CDR is attached to RSJ's filesystem,
otherwise this will result in errors.
It seems that the latest version of the Adaptec 2940 driver (ver 2.2)
does not work correctly with RSJ, but version 2.11 works fine.
If you are using RSJ CD Writer 2.7 you can add unsupported drives
BY RSJ Homepage: In order to add support for other drives than the
models listed above, look into the file CDDRV.INF and copy an entry
which resembles your drive according to the write speed and the RW
capabilities. Change the SCSI-ID string to the one reported by your
SCSI adapter and set the column "Compatible-ID" to the ID string of
the drive used as template for the new entry. Finally, add the ID
string to LOCKCDR.FLT in CONFIG.SYS as follows:
"BASEDEV=LOCKCDR.FLT -i:"VENDOR MODEL". [...]«
<<=TIP=>> If you are using an Adaptec SCSI Card you can also use
BASEDEV=AHA152X.ADD /V /F:x to force the target SCSI ID x. The host
adapter will assume that the target ID x is connected to SCSI Bus.
RESERVEDRIVELETTER=x
New in Warp 4, Warp 3 with Fixpaks higher 35
Note: Multiple RESERVEDRIVELETTER statements are allowed but only the
last one is used.
During the processing of CONFIG.SYS, OS/2 allocates drive letters for
all BASEDEV= statements. In general, the only BASEDEV= statements that
allocate drive letters are those for the Disk Device Driver, which
will allocate 1 drive letter sequentially for each local disk
partition. Three local disk partitions would allocate C:,D:,E:.
After processing BASEDEV= statements, the system will honor the
RESERVEDRIVELETTER statement(s). If the RESERVEDRIVELETTER statement
conflicts with any drive letter already assigned to a local disk
partition, an error message will be generated and that
RESERVEDRIVELETTER statement will be ignored.
The next processing occurs for DEVICE= statements. DEVICE= statements
for local block mode devices will assign drive letters, starting
sequentially immediately after the highest drive letter specified in a
RESERVEDRIVELETTER statement. Examples of local devices which use
drive letters are CDROM, R/W OPTICAL, TAPE, Virtual Disks (VDISK).
SET BOOKSHELF=C:\GAMMA32;C:\OS2\BOOK
This command points to the on-line documentation (INF files)
provided with OS/2 or other OS/2 programs. I have the
GAMMATECH utilities installed on my system which contains
on-line documentation.
<<=TIP=>> If you have an HPFS partition, copy all of your
on-line documentation (INF files) to this partition. Then
change this parameter to reflect the new path. You will
notice a substantial improvement in search speed since HPFS
is much faster than FAT.
SET EPMPATH=C:\OS2\APPS
Replaced SET EPATH=C:\OS2\APPS in version 2.0. According to
one source in IBM, EPMPATH is used by the Enhanced Editor
(EPM.EXE) to locate its files.
SET HELPNDX=FILE1.NDX+FILE2.NDX+...+FILEn.NDX
The HELPNDX variable points to the index files which
are used by the EPM editor and possibly by some
other programming editors. With EPM, you can mark
a keyword in your text and press CTRL + H. EPM
then searches the index files for the marked word
and if it is found, shows the online document for the
keyword. The index files must be in a path defined
by the BOOKSHELF or EPMPATH variable.
SET NOWIN32LOG=1
Quoting the README of the w32os204 package:
Although the output generated in win32os2.log very useful for
debugging,it slows things down quite a bit.
You can disable it by adding the following variable to your
environment:
SET NOWIN32LOG=ANY VALUE
DEVICE=D:\OS2\VASPIDD.SYS
DEVICE=D:\OS2\VASPI.SYS
Adaptec ASPI device drivers for SCSI support.
DEVICE=C:\OS2\APPS\SASYNCDB.SYS
DEVICE=C:\OS2\APPS\SASYNCDA.SYS
This device driver loads communications support for the PM
Terminal applet. The PM Terminal applet, and this
device driver, were dropped in OS/2 Warp.
<<=TIP=>> If you don't use PM Terminal, REM this line to
save a little memory. In fact, if you are not using PM
Terminal applet you may wish to consider deleting the files
to save some disk space also.
DEVICE=C:\OS2\WIN32OS2\WIN32K.SYS
Win32k - Win32-OS/2 driver, description in WIN32.TXT of the w32os2
package.
DEVICE=X:\LPTOOL\LPTDD.SYS
This driver is for the LPTools an parallel to parallel port
solution like laplink.
<<=NOTE=>> The FREE LPTool is developed by Jan van Wijk, and
can be downloaded at his homepage http://www.fsys.demon.nl
PROTECTONLY=NO
Allows you to choose between a shared DOS and OS/2 operating
environment or just an OS/2 environment. If you plan to run
only OS/2 programs, then set PROTECTONLY=YES. If you plan to
run DOS programs (including Windows), then set PROTECTONLY=NO.
<<=NOTE=>> Jonathan de Boyne Pollard relayed the following:
"Part of the difficulty of talking about OS/2 2.x, as opposed
to OS/2 1.x, is that *all* processes run in *protected mode*.
The 386 never runs in real mode in OS/2 2.x.
"Virtual DOS Machines are run in v8086 mode, which is still
*protected mode*, as the paging mechanism is still active.
The major difference between v8086 and normal protected mode
is that the segment base addresses in linear memory are
fixed, instead of being determined by the entries for each
selector in the LDT and GDT.
"So PROTECTONLY in OS/2 2.x means *don't use v8086 protected
mode*. For a while there we thought that it meant *don't use
real mode* and so was useless to OS/2 2.x, but it seems after
all that it retains its original OS/2 1.x semantics, if not
its original mechanism."
SHELL=C:\OS2\MDOS\COMMAND.COM C:\OS2\MDOS /P
This line identifies and loads the DOS command processor
COMMAND.COM which you must have to make DOS sessions work. The
/p switch keeps the command processor in memory until shut down.
<<=NOTE=>> This is the line where you can also specify the size
of the DOS environment variable. The range is 160 through 32768.
For example, to set a 1024 byte environment you would add the
following to the end of the SHELL command line: /E:1024
<<=TIP=>> You can also load and run other command processor's
such as 4DOS. To do so, just put 4DOS in your MDOS directory
and change the SHELL line to read 4DOS.COM instead of
COMMAND.COM.
FCBS=4,2
File Control Blocks (FCBS) are an outmoded holdover from old
versions of DOS. The blocks are an internal holding area for
data about concurrently open files. In newer versions of DOS,
these FCBS have been replaced by File Handles, but some DOS
programs still use them and you need this statement for com-
patibility. The command tells an OS/2 VDM how many FCBS can
be open at once, or, when DOS needs to open more FCBS than are
available, how many currently open but not active FCBS may be
closed to make room for new ones.
The syntax is FCBS=a,b where a=the number of FCBS that DOS can
have open at one time and b=the number of FCBS DOS cannot close
to make room for new FCBS. "a" can be as high as 255. "b" can
have a value of 0 to 254, but must be less than "a". Unless
you get some kind of error message when running a DOS program
that tells you the program doesn't have enough FCBS, leave the
default as set.
<<=TIP=>> You may wish to experiment with a smaller number.
If you can get by with a smaller number, you will get back a
little memory in each of your DOS sessions. My suggestions is
that you set it to 4,2. If you make this change and then load
a DOS program that says it can't open a file, increase the
first value, reboot, and see if the error message goes away.
You can also increase or change the value in the DOS programs
Settings notebook.
RMSIZE=640
This is a DOS command and sets the amount of memory available
for use by each DOS session. The maximum is 640k. Since some
DOS programs require 640k, its best to have RMSIZE set to 640.
<<=TIP=>> If you need maximum memory (more than 640k), see
tip under DOS=LOW,NOUMB.
DEVICE=C:\OS2\MDOS\VEMM.SYS
VEMM.SYS lets DOS programs use expanded memory unless you
override it by changing a DOS programs SETTINGS.
Three of its switches are:
/S=n Sets the limit of EMS memory in blocks of 1024k.
Default is 2.
/L=n Size of conventional memory that can be remapped.
Default is none.
/F=nnnn Memory frame address to be used to map EMS.
Default is AUTO.
<<=NOTE=>> Settings you specify in a DOS session will
override these switches.
<<=NOTE=>> The VEMM.SYS device must be listed in your
config.sys file before the VXMS.SYS device.
DEVICE=C:\OS2\MDOS\VMOUSE.SYS
Identifies and loads the mouse driver to let you use a mouse
with DOS. Mouse support for OS/2 is loaded below.
<<=NOTE=>> If you don't have this line (or you REM'd it), you
will not have mouse support in your DOS sessions.
DOS=LOW,NOUMB
This is a standard DOS command that lets you control how DOS
uses memory. The default is DOS=LOW,NOUMB and is considered
by many to be the best setting for it conserves memory
for OS/2. DOS=HIGH (including ,UMB) reduces available memory
for OS/2, but increases the available memory in EVERY DOS
session. Few DOS sessions need maximum memory. Also remember
that you can move DOS HIGH for a specific program by changing
that programs Settings. This is done in the programs Settings
Notebook and is likely the better way to go. Finally, keep in
mind that in OS/2 many device drivers are not taking up room in
your 640k DOS area. So you generally have more memory in the
typical OS/2 DOS session than in a standard DOS session.
The following is the amount of memory my system reports in each
DOS session with DOS=LOW,NOUMB. The vast majority of all DOS
programs will run just fine with this amount of memory.
655360 bytes total memory
655360 bytes available for DOS
618208 largest executable program size <---- About 604k.
With DOS=HIGH, the amount of memory reported is:
655360 bytes total memory
655360 bytes available for DOS
643632 largest executable program size <---- About 629k.
<<=TIP=>> If you need the maximum available RAM in a DOS
session and can get by on CGA or MONO, in the DOS Settings of
your applications Settings Notebook, change VIDEO_MODE_RESTRICTION
to CGA or MONO. (Note that there are some reports from users
that this procedure does not work on their hardware.) A final
note: For this to work on some systems, you may need to change
RMSIZE command to 639 (RMSIZE=639). See description of this
parameter under RMSIZE. This is the result of a bug in OS/2. I
have not verified if this bug is still in Warp. Any one care to
verify if it is still around?
The amount of memory reported after doing this on my machine is:
752640 bytes total memory
752640 bytes available for DOS
740656 largest executable program size <---- About 724k.
LOADHIGH C:\OS2\MDOS\TSR.EXE
LH C:\OS2\MDOS\TSR.EXE
This command is for DOS sessions and loads TRS programs into
upper memory blocks if they are available. If upper memory
blocks are not available, the TRS will be loaded into
conventional memory.
DEVICE=C:\OS2\APM.SYS
DEVICE=C:\OS2\BOOT\APM.SYS <--- in WARP
Device driver for ADVANCED POWER MANAGEMENT system used with
laptop systems. Not using a laptop? Then REM or delete the
statement. If you are using a laptop, see the OS/2 README
file for more details on its operation.
RUN=\OS2\BOOT\APMDAEMN.EXE
New in Fixpaks, fixes some errors when using APM 1.2
RUN=C:\OS2\SMSTART.EXE
This belongs to the error logging system, which no normal
user will ever have use for.
The output is only decipherable for REAL experts, so it is
probably meant as a goodie for the IT people in large
corporations, with their own software etc.
<<=TIP=>> An REM in front of RUN=C:\OS2\SMSTART.EXE will stop
the following processes: SMSTART.EXE, DMISL.EXE, ERLOGGER.EXE
FFST.EXE. This is advised for all 'normal' users.
RUN=C:\MMOS2\MIDIDMON.EXE
This is for MIDI
RUN=C:\MPTN\BIN\CNTRL.EXE
TCP/IP Stack processing. CNTRL.EXE is a very important component
of the stack. CNTRL.EXE provides threads for proper running of
the stack. It provides a thread for each of the following: - IP
input processing - TCP slow timeout processing - Debug thread for
IP - ARP timeout processing - Ifndis debug thread - Watchdog thread
for the adapter status - Loopback IP packets processing CNTRL.EXE
is normally started from CONFIG.SYS with a RUN=statement. It should
be the first program to begin executing when TCP/IP is started.
CNTRL.EXE for Version 4 is different from that in the Version 2.0
stack
DEVICE=C:\MPTN\PROTOCOL\IFNDIS.SYS
Part of the TCP/IP Protocols
DEVICE=C:\MPTN\PROTOCOL\AFINET.SYS
Part of the TCP/IP Protocols
CALL=C:\OS2\CMD.EXE /Q /C C:\MPTN\BIN\MPTSTART.CMD >NUL
The file named MPTSTART.CMD contains Socket/MPTS
configuration information for a workstation. Socket/MPTS
creates and updates a MPTSTART.CMD file, based on your
configuration selections using the Socket/MPTS window
interface or using the response files.
MPTSTART.CMD is automatically started when the
workstation is restarted by a call statement in the
CONFIG.SYS file.
DEVICE=C:\OS2\MDOS\VXMS.SYS /UMB
VXMS.SYS is a device driver that provides Extended Memory
management to DOS sessions. XMS allows DOS programs to access
more than one MB of memory.
There is a total of five switches available.
/UMB Upper memory block support in DOS sessions.
/NOUMB No upper memory block support.
/XXMLIMIT=m,n Indicates the total system wide memory limit.
/HMAMIN=m Sets the minimum request size for high memory,
from 1k to 63k.
/NUMHANDLES=m Sets the number of handles in each DOS session,
from 1 to 128.
<<=NOTE=>> The VXMS.SYS device must be listed in your
config.sys file after the VEMM.SYS device.
DEVICE=C:\OS2\MDOS\VDPX.SYS
Driver required when using VDPMI in the config.sys line
below. One authority said that this driver "provides V86 to
Protected Mode translation for DPMI memory". Well that's
enough to lose me.
DEVICE=C:\OS2\MDOS\VDPMI.SYS
Provides "virtual" DPMI (DOS Protect Mode Interface) memory
for DOS and Window sessions. I don't know much about this,
but I've been told not to remove it.
DEVICE=C:\OS2\MDOS\VWIN.SYS
Assists in the process of providing seamless Windows support.
DEVICE=C:\OS2\EXTDSKDD.SYS
EXTDSKDD.SYS supports external disk drives. There are five
switches available. See your online Command Reference for
complete details on these switches.
DEVICE=C:\OS2\PCMCIA.SYS
DEVICE=C:\OS2\MDOS\VPCMCIA.SYS
These two drivers were new beginning with version 2.1. They
provide support for computers that have PC Memory Card
International Association (PCMCIA) adapters.
<<=TIP=>> If you don't have any PCMCIA devices, then you
should REM these drivers to save a little RAM.
<<=NOTE=>> If you are using PCMCIA adapters and you find that
your communications ports (COM1 - COM4) are not working
properly, place these two device drivers after the COM.SYS and
VCOM.SYS statements.
DEVICE=C:\OS2\MDOS\VCDROM.SYS
This is a CD-ROM device driver that provides support in DOS
sessions.
<<=TIP=>> If you don't have a CD-ROM installed, then you should
REM this line to save a little RAM.
IFS=C:\OS2\CDFS.IFS /C:4
IFS=C:\OS2\BOOT\CDFS.IFS /C:4 <---- In Warp
This OS/2 command is needed if you have a CD-ROM. It installs
CDFS.INF which is the "Installable File System" for CD-ROMs.
Your CD-ROM is not going to run without it.
<<=TIP=>> You can add cache to your CD-ROM IFS by adding the
/C:n switch. The variable "n" is a number which represents
units of 64kb of memory. For example, /C:4 would set up a
256kb cache (4 x 64kb = 256kb).
Other switches include the following:
/P: Indicates the debug output port. The values can be 1 (COM1)
or 2 (COM2).
/K Indicates the supplemental volume descriptor with KANJI.
/M:n Where n indicates the maximum number of file sectors to
read at a time. The default is 8.
/Q Suppresses initialization messages.
/w enables Joliet support, new in Fixpaks
DEVICE=C:\OS2\OS2CDROM.DMD /Q
DEVICE=C:\OS2\BOOT\OS2CDROM.DMD /Q <---- In Warp
OS/2 driver used on many, but not all CD-ROM's.
DEVICE=C:\OS2\MDOS\VW32S.SYS
WIN32 program support driver.
DEVINFO=SCR,VGA,C:\OS2\VIOTBL.DCP
DEVINFO=SCR,VGA,C:\OS2\BOOT\VIOTBL.DCP
This command prepares your monitor to display information based
upon the CODEPAGE specification. VIOTBL.DCP is the file that
contains the video fonts for displaying characters for each of
the CODEPAGES supported by OS/2. See the CODEPAGE command line
below.
DEVICE=C:\OS2\MDOS\VVGA.SYS
Your config.sys file will contain various device drivers for
various devices based upon your systems hardware configuration.
This device driver for supporting VGA video cards in DOS sessions.
SET VIDEO_DEVICES=VIO_SVGA
SET VIO_SVGA=DEVICE(BVHVGA, BVHSVGA)
DEVICE=C:\OS2\MDOS\VSVGA.SYS
Your config.sys file will contain various device drivers for
various devices based upon your systems hardware configuration.
These device driver are for a SVGA video card.
SET VIDEO_DEVICES=VIO_VGA
SET VIO_VGA=DEVICE(BVHVGA)
DEVICE=C:\OS2\MDOS\VVGA.SYS
Your config.sys file will contain various device drivers for
various devices based upon your systems hardware configuration.
These device driver are for a VGA video card.
SET VIDEO_DEVICES=VIO_MGA
SET VIO_MGA=DEVICE(BVHVGA,BMGAX64)
DEVICE=C:\MGA\OS2\KMGAX64.SYS
These are the device driver for a Matrox video card
DEVICE=C:\OS2\POINTDD.SYS
DEVICE=C:\OS2\BOOT\POINTDD.SYS <---- In Warp
Provides mouse-pointer draw support. Text modes 0, 1, 2, 3, and
7 and graphic modes D, E, F, and 10 are supported. For graphic
modes D, E, F, and 10, the correct graphic device driver must
also be installed.
<<=WARNING=>> In order for MOUSE.SYS to work effectively, this
driver must be loaded by OS/2 before MOUSE.SYS. Do not remove
it from your config.sys file.
DEVICE=C:\OS2\MOUSE.SYS SERIAL=COM1 QSIZE=10
DEVICE=C:\OS2\BOOT\MOUSE.SYS SERIAL=COM1 QSIZE=10 <-- In Warp
Lets you use a mouse or track ball. This line also identifies
the type of mouse you have and which COM port it is on. QSIZE
is a number from 1 to 100 which indicates how many mouse
actions are to be saved when you execute mouse actions
faster than your system can handle them. There is also a
RELAXED parameter which you would place after QSIZE. It can
be used with any mouse when the pointer is jumping randomly
about the screen. IBM does not suggest you use this parameter
unless you are experiencing this problem.
<<=NOTE=>> The MOUSE.SYS statement must come before COM.SYS, but
after POINTDD.SYS, because COM.SYS will take over any unused COM
port. If COM.SYS takes over the COM ports before MOUSE.SYS is
loaded, MOUSE.SYS will not have any COM ports available, thus no
mouse support.
DEVICE=C:\OS2\RODENT\RODENT.SYS COM=1 BUTTONS=3
Device driver for the shareware mouse driver call Rodent.
DEVICE=C:\OS2\COM.SYS
DEVICE=C:\OS2\BOOT\COM.SYS <---- In Warp
Lets you use the communications ports COM1 and COM2. If you
want to use COM3 or COM4 or change the IRQ of any COM port,
see <<=TIP=>> below. This line MUST appear after any driver
that uses a communications port. Use COM02.SYS for IBM PS/2
model 90 and 95.
<<=TIP=>> There are two very good replacement drivers for
COM.SYS\VCOM.SYS called SIO.SYS\VSIO.SYS. It can be obtained
on most OS/2 BBSs. If you utilize communications software on a
regular basis at high speeds (e.g. 14,400), I recommend you
consider SIO.SYS. Replace VCOM.SYS with VSIO.SYS which
comes with SIO.SYS. SIO.SYS and VSIO.SYS are Shareware, not
Freeware. Register them if you use them!
<<=TIP=>> To add support for COM3 and COM4 at location 3E8 with
IRQ 4 and 2E8 with IRQ 3 respectively, add (3,3E8,4) (4,2E8,3)
to the DEVICE line, e.g. DEVICE=C:\OS2\COM.SYS (3,3E8,4)
(4,2E8,3). You can also use this method to change a COM ports
assigned IRQ.
DEVICE=C:\OS2\COM02.SYS
DEVICE=C:\OS2\BOOT\COM02.SYS <---- In Warp
For IBM PS/2 model 90 & 95 only.
Lets you use the communications ports COM1 and COM2. If you
want to use COM3 or COM4 or change the IRQ of any COM port,
see <<=TIP=>> below. This line MUST appear after any driver
that uses a communications port.
<<=TIP=>> To add support for COM3 and COM4 at location 3E8 with
IRQ 4 and 2E8 with IRQ 3 respectively, add (3,3E8,4) (4,2E8,3)
to the DEVICE line, e.g. DEVICE=C:\OS2\COM02.SYS (3,3E8,4)
(4,2E8,3). You can also use this method to change a COM ports
assigned IRQ.
DEVICE=C:\OS2\MDOS\VCOM.SYS
Lets you use the communications ports for DOS and Windows
sessions. Must appear after the COM.SYS driver.
<<=NOTE=>> If you are using COM3 and/or COM4, add the
appropriate parameters to the COM.SYS line above only. It is
not necessary to add any parameters to this line. VCOM.SYS
inherits its parameters from the COM.SYS line.
<<=TIP=>> See TIP under DEVICE=C:\OS2\COM.SYS regarding
SIO.SYS.
DEVICE=C:\SIO\SIO.SYS
Excellent replacement driver for COM.SYS. If you utilize
communications software on a regular basis at high speeds
(e.g. 14,400), then the SIO drivers are the way to go.
SIO.SYS must reside in the config.sys after MOUSE.SYS !
Be sure you have REM'd out COM.SYS when using. SIO.SYS and
VSIO.SYS are Shareware, not Freeware. See also VSIO.SYS.
DEVICE=C:\SIO\VSIO.SYS
Excellent replacement driver for VCOM.SYS. If you utilize
communications software on a regular basis at high speeds
(e.g. 14,400), then the SIO drivers are the way to go.
Be sure you have REM'd out VCOM.SYS when using. SIO.SYS and
VSIO.SYS are Shareware, not Freeware. See also SIO.SYS.
MODE
MODE is a multipurpose command that allows you to control
printer ports, serial ports, modems, video monitors and disks.
For example, if you want to "lock" in the baud rate on COM2,
add the following MODE command to your config.sys file:
MODE COM2 baud (where baud is the rate you want to lock)
DEVICE=C:\MMOS2\MVPRODD.SYS /I11 /D3 /S:1,220,1,5 /N:PAS161$
DEVICE=C:\MMOS2\AUDIOVDD.SYS PAS161$
These two drivers are for MediaVision's ProAudio Spectrum
sound card. The first driver is set for IRQ 11, DMA 3 with
Sound Blaster support on IRQ 5 and DMA 1.
<<=Warp TIP=>> MediaVison's technical support indicates that
the only correct settings for the PAS 16 in Warp is IRQ 11
and DMA 3. If you are experiencing static or white noise
during bootup, MediaVison indicates that this is caused by
using an IRQ other than 11 and DMA 3. They also indicate that
the two device driver lines must be the last lines in your
config.sys file. Note that this information didn't solve the
static problem for all users I've talked with, but it did for
some. Others have indicated that adding the /T:1 switch solved
their "white noise" problem.
My experience has been that any change to the MVPRODD.SYS
parameters will solve this problem, until you have to reset
your system without a proper shut down. Then the "white
noise" returns, so I add or subtract the /T:1 parameter.
There are new drivers in the Warp FullPak which solved the
"white noise" problem for me.
<<=Warp NOTE=>> I've heard that there may be a bug in Warp
which causes problems in WIN-OS2 "seamless" mode. A solutions
is contained in SNDWOR.ZIP which can be downloaded from many
OS/2 BBSs.
DEVICE=C:\MMOS2\ES1868DD.SYS /B:220 /D:1 /F:3 /I:5 /C:4 /M:300
,7 /N:ES18681$
DEVICE=C:\MMOS2\VAUDDRV.SYS ES18681$
These are the sounddrivers for the ESS1868pnp (many soundcards)
DEVICE=C:\MMOS2\SB16D2.SYS 1 1 5 5 220 4 330 /N:SBAUD1$ /Q
DEVICE=C:\MMOS2\AUDIOVDD.SYS SBAUD1$
These two drivers are for Sound Blaster 16 sound card.
Regarding the SB16D2.SYS driver, Doug Boulter comments that:
- the first number is the device number, in this case 1;
- the second number is the 8-bit DMA channel, also 1;
- the third number is the 16-bit DMA channel, in this case 5;
- the fourth number is the interrupt, IRQ 5;
- the fifth number is the base I/O address, 220H;
- the sixth number is the buffer size; and
- the seventh number is the MIDI base I/O address, 330H.
DEVICE=C:\MMOS2\SBAWED2.SYS /C:1 /D:1 /H:5 /I:5 /A:220 /M:330 /N:SBAUD1$
/Q /P /G
This driver is for Sound Blaster AWE32 sound card.
<<=TIP=>> According to OS/2-Inside the statement can be shortened to:
SBAWED2.SYS /N:SBAUD1$
DEVICE=C:\MMOS2\JAZZDD.SYS /I:5 /D:1 /E:5 /T:330 /Q:10 /P:220 /N:JAZZ1$
Support driver of Creative Labs Jazz16 card.
DEVICE=C:\OS2\MDOS\ANSI.SYS
This is the traditional DOS command most are familiar with.
It only affects DOS sessions. This line is not added to your
config.sys file by default. If you want it, you need to add it.
OS/2 sessions have ANSI support by default. If you are unsure
if ANSI is on or off in an OS/2 session, go to an OS/2 command
prompt and type ANSI. You will get a message like: "ANSI
extended screen and keyboard control is on." For an OS/2
session, turn ANSI off or on by typing ANSI OFF or ANSI ON at
an OS/2 command prompt.
There is two switches:
/X Redefines keys with extended dey values as distinct keys.
/K Disables extended keyboard capabilities. You would use
this switch if an application does not support extended
keyboard.
SET ETC=C:\TCPI\ETC
SET TMP=C:\TCPIP\TMP
DEVICE=C:\TCPIP\BIN\INET.SYS
DEVICE=C:\TCPIP\BIN\IFNDISNL.SYS
DEVICE=C:\TCPIP\BIN\VDOSTCP.VDD
DEVICE=C:\TCPIP\BIN\VDOSTCP.SYS
RUN=C:\TCPIP\BIN\CNTRL.EXE
RUN=C:\TCPIP\BIN\VDOSCTL.EXE
Provides TCP/IP support for Warp's InterNet tools provided in the
Bonus Pack.
<<=TIP=>> If you don't need TCP/IP support in DOS sesions, and you
don't if you are using the Bonus Pack tools, REM the following
lines:
DEVICE=C:\TCPIP\BIN\VDOSTCP.VDD
DEVICE=C:\TCPIP\BIN\VDOSTCP.SYS
RUN=C:\TCPIP\BIN\VDOSCTL.EXE
Remember that Windows is a DOS based system.
DEVICE=C:\OS2\TOUCH.SYS
(From OS/2s online documentation)
Implements support for touch devices. For a touch device to be
effectively used, the POINTDD.SYS device driver and appropriate
mouse device-driver support must be loaded. In addition, these
statements must be included in the CONFIG.SYS file in the
following order:
o A device-dependent statement that gives the name of the
file containing the information for the touch device you use.
o A device-independent statement that identifies the touch
device to TOUCH.SYS
If during installation, OS/2 detects a touch device installed on
your system, the Install program automatically loads the required
device-driver support necessary to enable the touch device. The
touch device shares the auxiliary device (mouse) port on the
system with the mouse by allowing the mouse to connect to the
touch device, which is then connected to the system.
The Install program automatically adds the following statements
to the CONFIG.SYS file:
DEVICE=C:\OS2\PDITOU0x.SYS CODE=C:\OS2TOUCO21.BIN INIT=C:TOUCH.INI
DEVICE=C:\OS2\TOUCH.SYS TYPE=PDITOU$
RUN=C:\OS2\CALIBRATE.EXE-C C:\OS2CALIBRAT.DAT
DEVICE=C:\OS2\MOUSE.SYS TYPE=PDIMOU$
"x" is 1 or 2 depending on the bus architecture of your system.
TOUCO21D.BIN is the touch-device microcode binary file and
TOUCH.INI is a text file containing default parameter settings.
The RUN=CALIBRAT.EXE statement is to activate the Calibration
program. This program performs the dual actions of downloading
calibration-constant data to the touch device each time the
system is started, and enabling recalibration of the touch
device at initial setup, and when the device is moved to a new
location.
To recalibrate the touch device, enter the following at an OS/2
command prompt:
x: (where "x" is your OS/2 boot drive.)
CD \OS2
CALIBRAT -U
RUN=C:\OS2\CALIBRATE.EXE-C C:\OS2CALIBRAT.DAT
DEVICE=C:\OS2\PDITOU01.SYS
DEVICE=C:\OS2\PDITOU02.SYS
See DEVICE=C:\OS2\TOUCH.SYS
DEVICE=C:\OS2\LOG.SYS
This optional device driver installs OS/2s error log file. If
you want a log of errors that occur on your system, then add
this and the next line to your config.sys file. If you are
interested in such things, you may wish to play with it, but
be forewarned, the error log information is cryptic and
incomplete. See note below. To learn what these codes mean,
you need to have IBMs Systems Network Architecture Formats
(GA27-3136-12) or, for a reasonable overview, get OS/2 2.1
Unleashed, 1993, SAMS Publishing.
The switch /E:nn sets the size of the error log buffer. The
range is from 4kb to 64kb with 8kb as the default.
You will get a short and quick message during boot up
indicating that Logging has been installed and what the buffer
size is.
<<=NOTE=>> LOG.SYS has its limitations. It will not log an
application error unless the application has been written to make
use of LOG.SYS. Some routine system errors will not log either
because OS/2 opens an error message box on screen to report
these.
RUN=C:\OS2\SYSTEM\LOGDAEM.EXE /E:C:\OS2\LOGFILE.DAT /W:16
This RUN command starts the logging process and must appear
AFTER you have installed the LOG.SYS driver noted in the
config.sys line above. The two switches are:
/E:path\filename This is the path and file name of the
test file where the errors will be logged. You can place
it anywhere you want and call it anything you wish.
NOTE: Like the OS/2 INI files, this file is "locked" and
you will not be able to access it with your standard text
editor or the OS/2 System Editor. You will get a
"violation error". The Enhanced Editor will open the file.
/W:nn This is the size of the file named with the /E
switch. The default size is 64k, but with this switch
you can set the value from 4k to 64k. I've set the file
size at 16k in the example line above.
<<=NOTE=>> Use SYSLOG.EXE from an OS/2 command line prompt to
view your log file.
CODEPAGE=437,850
Lets you use the alphabet of various countries and languages.
The syntax is CODEPAGE=ppp,sss, where ppp is the number of the
primary national alphabet to be used and sss is a secondary
alphabet number. From an OS/2 command line, you can use the
CHCP command to switch between these two code pages. This can
be useful in order to type, display or print data in a
different language from the version installed. CHCP can be
used either without a parameter to query the current code
page, or with one parameter in order to switch between primary
and secondary code pages. CHCP cannot be used to change to a
code page not defined in the CODEPAGE= config.sys line.
437=US English alphabet and 850=multinational alphabet. The
multinational alphabet contains most of the accented letters
used in various European languages. Several other alphabets
that can be supported by your version of OS/2. See Table 6.0.
<<=WARNING=>> Japan, Korean and Chinese require a special
version of OS/2 and special hardware.
<<=WARNING=>> The choice of code page is made at installation
time and should only be changed by using Selective Install.
<<=NOTE=>> If there is not a CODEPAGE statement in your
config.sys, your keyboard will use an alphabet based on
the COUNTRY statement found earlier in your config.sys,
but your screen and printer will use their built in defaults.
<<=TIP=>> Holger Granholm of Helsinki, Finland provided the
following excellent commentary on CODEPAGE=437,850.
"I would like to point out that the 437=US English alphabet also
contains most of the accented letters used in various European
languages as also shown by their secondary code page listing.
"Code page 850 is missing a lot of the mathematical and
electronics symbols and quite many of the graphic characters
contained in the extended (128 - 256) ASCII character set.
"Ever since I found out (in 1986) that I had to set my Epson
printer to the US character set to be able to print the accented
characters I have only used code page 437 on my computers.
"The newer DOS versions force on you NLSFUNC, DISPLAY.SYS, CHCP
and what not as soon as they learn that you use anything else
than english. All these can be deleted to save memory. Also OS/2
puts code page 850 ahead of 437 when you choose another country
or keyboard than US/English.
"One of the first things I did to the OS/2 CONFIG.SYS file was
to change those around."
================== Table 6.0 =====================
<<=NOTE=>> The Table is according to Warp 4 your system may vary
COUNTRY PRIMARY SECONDARY ALTERNATIVE
CODE PAGE CODE PAGE CODE PAGE
Albania 850 437
Austria 850 437 1004
Arabic-speaking 864 850 437
Asia (English) 437 850
Australia (English) 850 437 1004
Baltic Countries 921
Belgium 850 437 1004
Bosnia 852 850
Brazil 850 437 1004
Bulgaria 915 850 855
Canada (French) 850 863 1004
Czech 852 850
Croatia 852 850
Denmark 850 865 1004
Estland 922 850
Finland 850 437 1004
France 850 437 1004
Germany 850 437 1004
Great Britain 850 437 1004
Greek 869 850 812
Hebrew-speaking 862,850 437
Hungary 852 850 1004
Iceland 850 861 1004
Ireland 850 437 1004
Italy 850 437 1004
Israel 862 850 437
Japan 943 850 942
Korea 949 850 944
Kroatia 852 850
Kyrillic 855
Latin America 850 437 1004
Latin 1 Multlingual 850
Latin 2 Eastern Eurpe 852
Lettland 921 850
Mazedonia 855 850 915
Netherlands 850 437 1004
New Sealand 850 437 1004
Nordic Lands 865
Norway 850 865 1004
Peoples Republic of 1381 850 946
China
Poland 852 850
Portugal 850 860 1004
Rumania 852 850 1004
Russia 866 850 915
Serbia/Montenegro 855 850 915
Slovak 852 850
Slovenia 852 850
Spain 850 437 1004
South Africa 850 437 1004
Sweden 850 437 1004
Switzerland (French) 850 437 1004
Switzerland (German) 850 437 1004
Taiwan 950 850 948
Thailand 874 850
Turkey 857 850 1004
United Kingdom 850 437
United States 437 850
Windows Latin 1 1004
<<=NOTE=>> Arabian, Greek, Hebrew, Thai and DBCS Codepages are only
fully supported in OS/2-Versions developed for those countries.
<<=TIP=>> In Warp 4 are many new Codepages, Codepage 1004 is according
to the WINDOWS ANSI Standard, this is important for an correct
interpretation of german 'umlauts' and to convert dokuments between
Windows and OS/2
SET LANG=en_US
Sets up the language and the country for applications
that are using Unicode character sets.
Here is a list of available settings:
Albania (sq_AL)
Arabic-speaking (ar_AA)
Australia (en_AU)
Austria (de_AT)
Belgium dutch (nl_BE)
Belgium French (fr_BE)
Bosnia (sh_BA)
Brazil (pt_BR)
Bulgaria (bg_BG)
Canada english (en_CA)
Canada french (fr_CA)
China (zh_CN)
Croatia (hr_HR)
Czechoslovakia (cs_CZ)
Denmark (da_DK)
Finland (fi_FI)
France (fr_FR)
Germany (de_DE)
Great Britain (en_GB)
Greece (el_GR)
Hungary (hu_HU)
Iceland (is_IS)
Ireland (en_IE)
Israel (iw_IL)
Italy (it_IT)
Japan (ja_JP)
Korea (ko_KR)
Latin America (es_LA)
Netherlands (nl_NL)
New Zealand (en_NZ)
Norway (no_NO)
Poland (pl_PL)
Portugal (pt_PT)
Romania (ro_RO)
Russia (ru_RU)
Slovak (sk_SK)
Slovenia (sl_SL)
South Africa (en_ZA)
Spain (es_ES)
Sweden (sv_SE)
Switzerland german (de_CH)
Switzerland french (fr_CH)
Switzerland italian (it_CH)
Taiwan (zh_TW)
Thailand (th_TH)
Turkey (tr_TR)
United States (en_US)
DEVINFO=KBD,US,C:\OS2\KEYBOARD.DCP
Tells the keyboard which international character set to use and
where to find the file KEYBOARD.DCP which translates keystrokes.
The syntax is DEVINFO=KBD,cc,DRIVE,PATH,FILENAME. The parameter
cc equals the character set to be used, e.g. US = United States.
See Table 7.0 for character set codes.
=============== Table 7.0 ================
LANGUAGE COUNTRY CODE
Arabic AR
Belgian BE
Canadian French CF
Czech/Czech CS243
Czech/Slovak CS245
Danish DK
Dutch NL
Finnish SU
French FR
German GR
Hebrew HE
Hungarian HU
Icelandic IS
Italian IT
Latin American LA
Norwegian NO
Polish PL
Portuguese PO
Spanish SP
Swedish SV
Swiss (French) SF
Swiss (German) SG
Turkish TR
United Kingdom UK
United States US
Yugoslavian YU
==========================================
SET ZOCDEVICE=COM4
Command used by older versions of ZOC,
the excellent OS/2 communications Shareware program from Germany.
SET SPEALOGO=OFF
Use this if you have an Spea Graphics-Card to disable the Logo
SET MGA=C:\MGA\OS2
Sets the default installation directory for Matrox Video Cards
SET IBMAV=C:\IBMAV
Sets the default path for IBMAV
SET TZ=MEZ-1 MSZ,3,-1,0,3600,10,-1,0,3600,3600
Sets the Timezone correctly for Germany with daylight savings
<<=TIP=>> As the correct setting of the TZ Parameters is somewhat
delicate use the excellent FREE-tool TZCALC by Norbert Dey
(at the moment tzcalc03.zip)
DEVICE=D:\BACKMAST\FTDVR.SYS
DEVICE=D:\BACKMAST\TC15DVR.SYS
DEVICE=D:\BACKMAST\PTDVR.SYS
Drivers of Backmaster tape backup system.
DEVICE=C:\OS2\APPS\SYSIOS2.SYS <<--- new with Warp
This device driver is required by the System Information Tools
provided in the "BonusPak" that comes with OS/2 Warp. If you plan
on using these tools, do not delete this driver.
DEVICE=D:\FAX\FMD.SYS
This driver is required by Faxworks lite 2.* in Warp 3 or the Pro
Versions of Faxworks/PMFax
SET DSPPATH=C:\MMOS2\DSP;
An environment variable used by various sound devices that support
digital signal processors (DSPs). This is a "path" statement. It
tells the device where to retrieve DSP modules. If you don't have
a sound device which supports DSP, like M-Audio adapter or the
Sound Blaster 16 CSP, you can REM this line.
SET MMBASE=C:\MMOS2;
An environment variable which indicates the path to OS/2s
multimedia programs.
SET NCDEBUG=4000
In both Lotus 123 and Excel, users can record and play back audio
and video annotations for specific cells. NCDEBUG is an
environment variable required for this to work in Lotus 123.
Excel does not need. If you do not have a need for this support,
or have Lotus 123, you may REM this line.
SET IBMWORKS_INI=C:\IBMWORKS <<--- new with Warp
IBM Works is an intergrated package of programs including a word
processor, database and spreadsheet which is included with OS/2
Warp's BonusPak. This statement tells the system where the
IBM Works' INI file is located.
<<=TIP=>> Many Warp users who have installed IBMWORKS from the
BonusPak report that system performance is greatly enhanced by
running IWDEREG.CMD program contained in the IBMWORKS folder.
This program deregisters IBMWORKS and releases a large amount
of RAM back to your system. Yes, IBMWORKS will still work, but
you may lose some functionality between applications.
To do this in Warp 4, use the REXX script available at
ftp://eepjm.newcastle.edu.au/freeware/IWDEREG.CMD
SET SPCH_MAINLANG=XX_XX
Sets the desired language for voicetype if there are more
languages installed
SET ULSPATH=C:\LANGUAGE;
Sets the path for unicode language files, needed for Java
SET CLASSPATH=C:\NETSCAPE\JAVA11\JEMPCL10.ZIP;....\
Sets the path for the Java Classes
SET JAVA_CONSOLE=1
All Java Programs and Applets run in an console
SET JAVA_NLS_SBCS=1
Specifies that Java should run in single-byte character set
(SBCS) mode even in double-byte character set (DBCS) environments.
SET JAVA_NL_DBCS=1
Java uses in double-byte environments only one byte
SET JAVA_NOPRINTDLG=1
Specifies that Java should suppress display of the
printer properties dialog box before printing.
This allows jobs to print, without user intervention,
using the default printer properties.
SET JAVA_AUDIO_RATE=n
Sets the preferred playback sample rate for audio.
A value of 8 for n sets the playback rate to 8000 samples
per second. Use a value of 11 for 11025 samples per second.
The Java runtime normally tries a sample rate of 8000 first,
which matches the incoming data stream rate, and then 11025.
<<=TIP=>> Some drivers, such as some ThinkPad 701C drivers
dated prior to October 1995, appear to support a sample rate
of 8000 but then fail; they can be made to work by setting a
playback sample rate of 11025.
SET JAVA_AUDIO_VOLUME=v
Adjusts the volume level for the audio output. v is the
percentage of the maximum volume, from 0 to 100.
The default is 75.
SET JAVA_COMPILER=<xyz>
Specifies the name of the just-in-time (JIT) compiler to load.
The default JIT is JAVAX.
<<=TIP=>> To disable the JIT, specify the name of a non-existent
DLL. ATTENTION, this will heavily decrease the speed of Java
SET JAVA_CONSOLE=1
Specifies that Java programs started by JAVA and APPLET are run
with a Java console.
SET JAVA_HOME=<dir>
Specifies the path to the shared Java runtime directories.
SET JAVA_NOPRINTDLG=1
Specifies that Java should suppress display of the printer
properties dialog box before printing. This allows jobs to
print, without user intervention, using the default printer
properties.
SET JAVA_USER=<dir>
Specifies the path to the directory for user-specific files
such as the hotjava\property file.
SET JAVA_WEBLOGS=<dir>
Specifies the path to the directory where weblog files for
each started Java process are written.
DEVICE=C:\OS2\VDISK.SYS 512
DEVICE=C:\OS2\BOOT\VDISK.SYS 512 <<--- In Warp
As in DOS, this driver installs a RAM disk. In this example,
the RAM disk is 512k with the sectors and directories parameters
set at the default level (64-byte sectors and 64 directory
entries). With DOS, a RAM disk could significantly improve
system performance, but because OS/2 handles your memory far
more efficiently than DOS and has its own sophisticated caching
routines, using a RAM disk is not recommended.
<<=CAUTION=>> Because a RAM disk takes available memory away
from OS/2, you may negatively impact system performance on
systems with less than 12MB of RAM. Unless you have lots of
RAM or have a very specific need, don't install a RAM disk.
<<=NOTE=>> If you do install VDISK.SYS and you also have
EXTDSKDD.SYS installed, VDISK.SYS must be placed after
EXTDSKDD.SYS in your config.sys file. Check your on-line
Command Reference for information on EXTDSKDD.SYS.
DEVICE=C:\OS2\MDOS\VNPX.SYS
This device driver works _with_ your systems math coprocessor.
If you do not have a math coprocessor, this driver will not load.
Some have suggested that if you add it to your config.sys you
will see an enhancement in your systems performance. Not so.
There is no reason for it to be added to your config.sys
file. IF YOU HAVE A MATH COPROCESSOR, OS/2 WILL LOAD THIS
DRIVER AUTOMATICALLY. If you add it to your config.sys file,
a second copy of the driver will be loaded. In doing so, many
have reported that no DOS programs would run. DO NOT ADD THIS
STATEMENT TO YOUR CONFIG.SYS FILE.
SET OCRNOTES=C:\Faxworks\Calera
SET OCRNOTES supports the optical character reader software from
Calera.
-----------------------------------------------------------------
5. NOVELL NETWARE NETWORK SUPPORT.
Novell's NetWare is the most popular PC Network software around
today. We use it at work and I've used our config.sys file
entries as the basis for this section of information.
<<=NOTE=>> I'm not very knowledgeable about networks, so if
someone would like to expand on this information and send it to
me, I'd love to give you credit and include it here.
REM --- NetWare Requester statements BEGIN ---
DEVICE=C:\NETWARE\LSL.SYS
Loads Link support Layer driver. It is the lowest layer in
the Novell Open Data Link Interface model and is required at
all times for the requester to be active.
RUN=C:\NETWARE\DDAEMON.EXE
A daemon is a background process that usually carries out
administrative tasks for the system without you knowing it.
This "daemon" is required for the requester to be active.
DEVICE=C:\NETWARE\TOKEN.SYS
This line differs depending on the network board you have.
DEVICE=C:\NETWARE\ROUTE.SYS
No information available.
DEVICE=C:\NETWARE\IPX.SYS
Provides Novell IPX protocol support and is required for
access to a NetWare server.
DEVICE=C:\NETWARE\SPX.SYS
Provides Novell SPX protocol support. It is my understanding
that this command is required for some Novell printing
utilities, but is optional in most cases.
RUN=C:\NETWARE\SPDAEMON.EXE
Loads a daemon process that handles SPX packets.
REM DEVICE=C:\NETWARE\NMPIPE.SYS
Loads the support for client-only Named Pipes support.
REM DEVICE=C:\NETWARE\NPSERVER.SYS
Loads support for your workstation to function as a Named
Pipes server.
REM RUN=C:\NETWARE\NPDAEMON.EXE NP_COMPUTERNAME
This line is required for either the client or the server
NetBIOS support to be active and is a daemon program that is
part of the Named Pipes support.
DEVICE=C:\NETWARE\NWREQ.SYS
This is the CORE REQUESTER MODULE. This line must follow any
lines that support IPX, SPX, or Named Pipes.
IFS=C:\NETWARE\NWIFS.IFS
This installed the networks Installable File System. This IFS
enables OS/2 to see the network drives just the same as local
drives.
RUN=C:\NETWARE\NWDAEMON.EXE
Another daemon program, but I'm not sure for which process.
DEVICE=C:\NETWARE\NETBIOS.SYS
Loads support for the NETBIOS protocol.
RUN=C:\NETWARE\NBDAEMON.EXE
Loads the NETBIOS daemon process.
DEVICE=C:\NETWARE\VIPX.SYS
Loads support for multiple virtual DOS machine support. It is
required both to have multiple DOS boxes on the network and to
run the NetWare DOS based utilities.
DEVICE=C:\NETWARE\VSHELL.SYS
Loads the network shell. It is automatically used for all DOS
and WIN-OS/2 sessions that require it.
REM --- NetWare Requester statements END ---
-----------------------------------------------------------------
5a. OTHER ITEMS
DEVICE=C:\IBMCOM\PROTMAN.OS2 /I:C:\IBMCOM
RUN=C:\IBMCOM\PROTOCOL\NETBIND.EXE
DEVICE=C:\IBMCOM\MACS\IBMTOK.OS2
These commands are added to your config.sys file when you install
LAN Adapter and Protocol Support (LAPS). LAPS may also add other
commands if other protocols like NETBIOS and IEEE 802.2 are
loaded.
DEVICE=C:\CMLIB\VHAPI.OS2
Paul Kurr wrote the following. "This provides for Virtual HLLAPI
support within VDM's (not sure about VMB's). This allows DOS
programs that use the HLLAPI to access the HOST sessions running
at the OS/2 level under comm mgr. So you can actually watch your
comm mgr sessions in one window and your DOS program in another
while they interact."
DEVICE=C:\IBMLAN\NETPROG\VNETAPI.OS2
Paul Kurr wrote: "This sets up the virtual network support API
within the VDM's (not VMB's). This allows DOS programs running
within a VDM to "see" that the network is loaded, and interact
with it (get/set redirections and such). If VDOLANAPI support
is required in a VMB the device driver VNETAPI.SYS needs to be
loaded within the VMB (this is found in \IBMLAN\NETPROG)."
RUN=C:\IBMLAN\NETPROG\VNRMINIT.EXE
SET NWDBPATH=C:\IBMLAN\NETPROG
SET DLSINI=C:\IBMLAN\NETPROG\NETGUI.INI
SET INIT_FILE_NAMES=netgui
SET INIT_FILE_RANGES=200
SET WPS_COMMUNICATION=YES
SET LOCPATH=C:\IBMLAN\XPG4\LOCALE
SET LANG=ENUS437
DEVICE=C:\IBMLAN\NETPROG\RDRHELP.200
IFS=C:\IBMLAN\NETPROG\NETWKSTA.200 /I:C:\IBMLAN /N
RUN=C:\IBMLAN\NETPROG\LSDAEMON.EXE
Items with \IBMLAN provide support for LAN Server. According to
Paul Kurr, the SET statements are for LS 4 GUI support.
-----------------------------------------------------------------
END OF CONFIG.SYS FILE DESCRIPTION
-----------------------------------------------------------------
6. OBSCURE CONFIG.SYS SETTINGS.
What follows are some very obscure config.sys settings. They
are here only for informational purposes. Unless you have a
very specific need and know what you're doing, please don't
experiment with these.
SET SHELLEXCEPTIONHANDLER=OFF
The WpS has its own exception handling routines which allow it
to recover from most errors, but when programming your own
objects, you want to see all errors as they occur. You can turn
WpS "exception handling" off with this command. Could be useful
when debugging a Workplace Shell object.
SET AUTOREFRESHFOLDERS=NO
with this environment setting the WPS doesn't automatically refresh
folders (autorefresh happens to every folder which has been ever
accessed and therefore slows the system). They are only refreshed after
closing and opening an folder or by an manual update using 'view,
refresh'.
<<=TIP=>> Especially for Fileservers this Statement is very useful, also
for slow systems.
SET OBJECTSNOOZETIME=45
Useful when programming certain types of object DLLs. The
default setting for the snooze time is 90 seconds. Unless you
are programming your own Workplace Shell objects, you should
not change the default setting.
SET SCROLLUP=1
Enables slow scrolling of the WarpCenter, only in Warp4 Beta
SET SHAPIEXCEPTIONHANDLER=OFF
This command disables the WpS API exception handler, and all
WpS exceptions are handled by OS/2.
SET VIDEO_APERTURE=xxx
This command allows you to set the address for video memory
refresh buffers, where xxx is a hexadecimal number. E.g for
PCI A00
SET MMBUF=49152
This increases the size of the read buffer. The default is 32768.
It can be set even higher, but movies will take longer to load.
SET MMSTREAM=/H:256
This increases the heap space for the stream manager to 256K, which
allows more movies to be open at once and may improve performance.
The default is 64K, and 256K is the maximum.
SET COPYFROMFLOPPY=1
If OS/2 should install updated drivers during an installation from the
Installation disks and not from CD this statement must reside in the
config.sys on Installationdisk 1
SET CONNECT_DASD=OFF
Disables the test for free space during the installation
SET CONNECT_PREREQ=OFF
Disables the check of installed software during installation
SET CONNECT_SNIFF=OFF
Disables the recognition of network-cards during installation
Thes settings are only useful for installing problems with warp4
and must be done in the config.sys on the installation diskettes
SET SCCANBENUKED=1
Enables the deleting of the Warpcenter Icon
<<=TIP=>> This REXX-Script reestablishes the Icon if it is deleted,
/* Recreate Warpcenter */
call RxFuncAdd 'SysLoadFuncs',,
'RexxUtil', 'SysLoadFuncs'
call SysLoadFuncs
/*Code*/
rc = SysCreateObject("SmartCenter", "WarpCenter", "<WP_OS2SYS>",
"OBJECTID=<WP_WARPCENTER>","F")
if rc = 0 then
say "New WarpCenter Created."
else say "Warpcenter creation failed! RC=" rc
<<=TIP=>> You can also use the FREE tool 'ObjectReCreator'
(orc.zip) by Kai Evers available at http://www1.stuttgart.
netsurf.de/~kevers/ It can recreate all standard Desktop Objects
who are lost or deleted
SET JAVA_CLOCK_RESOLUTION = 1
Sets the Minimum of the timer resolution in JavaApps using
currentTimeMillis to 1 Millisecond (the highest resolution).
The best Java-Speed using currentTimeMillis can be achieved
with JAVA_CLOCK_RESOLUTION = 32.
This can be important for Java-Benchmark-Tests.
SUPPRESSPOPUPS=x
SUPPRESSPOPUPS=0 will restore behavior to pre-FixPak 29 behavior. That
is, to disable logging and to have trap screens displayed unless
specifically overridden by an application's use of the DosError API.
SUPPRESSPOPUPS=x: will disable trap screen display for all processes and
will log trap screens in x:\POPUPLOG.OS2, where x: is a drive or
partition.
If SUPPRESSPOPUPS is omitted then the behavior is as described above
under "Automated Trap Screen Logging".
<<=NOTE=>> The log file name cannot be overridden.
REIPL=ON <---- new with Warp.
This command automatically restarts the system when a system
trap or internal processing error occurs. Parameter is ON or
OFF. Default is OFF.
<<=TIP=>> This command along with the SUPPRESSPOPUPS command
can be very useful to those running a BBS. If a trap or internal
processing error occurs while your BBS is unattended, having
these two command in your config.sys will cause your system to
log the error and then restart the system, so your BBS is back
online.
TIMESLICE=128,256
This command allows you to manually control the minimum and
maximum amount of processor time any thread can receive at
once. The syntax is TIMESLICE=x,y where x is the minimum time
slice (in milliseconds and must be at least 32) and where y is
the maximum length (must be less than 65536).
Jim Gilliland once posted: "The Timeslice parameter controls the
minimum and maximum timeslice that OS/2 will allow an application
to use. If you make the timeslice longer, OS/2's dispatching
overhead will be reduced, but the system's multitasking operation
will be "choppier". Increasing the length of the maximum
timeslice (the second parameter) will allow OS/2 to gradually
increase the length of the timeslice used by an application when
it is not competing with any other apps for CPU time (that is,
when it is the only app running or all others are blocked)."
<<=TIP=>> OS/2 handles time slicing dynamically. This means
that the system is adjusting the time slice values based on
the actual processes active on the system as the workload
changes. Therefore, it is best not to attempt to manually
set TIMESLICE. OS/2 can handle this process far better than
most of us can.
TRACE=ON
The system trace facility is used to record a sequence of
system events, function calls, or data. The record is usually
produced for program debugging purposes. After the trace data
is recorded, the System Trace Formatter is used to retrieve it
from the system trace buffer (see TRACEBUF below) and format
the data to either your display, printer, or to a file. Start
tracking system problems by turning TRACE on which will
establish a 4KB default buffer. (You can increase this using
the command TRACEBUF) to store tracing data. You can also
start TRACE from an OS/2 command prompt.
<<=NOTE=>> You can turn TRACE=ON and then set TRACE=OFF for
major or minor codes. For example, TRACE=OFF 24,50,98.
TRACEBUF=x
This command sets the size of the trace buffer. If any valid
TRACE statement is in your config.sys, the default size of
the trace buffer will be 4KB. You can modify this size with
the TRACEBUF command. Maximum size is 63KB. "x" is a specific
number from 1 to 63, representing a multiple of 1024 bytes.
TRAPLOG [x: | NOLOG] [POPUPS | NOPOPUPS]
The TRAPLOG command allows dynamic control of trap information logging.
where:
■ x: specifies that trap information is to be logged in
x:\POPUPLOG.OS2, x: being any partition drive letter.
■ NOLOG disables logging of trap information.
■ POPUPS enables the trap information pop-up message (SYS3175).
■ NOPOPUPS disables the trap information pop-up message.
TRAPDUMP=xx,d
Parameters are: OFF,drive letter
ON,drive letter
R0,drive letter
Indicates when a stand alone dump is to be taken and where the
dump is to be placed. The default value is OFF and the default
drive is "A".
If you are sending a memory dump to hard disk, you must first
create a FAT partition labeled SADUMP and give it a size
greater than the amount of physical memory in your system.
The drive you specify in the TRAPDUMP statement must contain
the SADUMP partition. Any existing data in this partition
will be overwritten. The system will restart after the TRAPDUMP
process has been completed.
<<=NOTE=>> If REIPL=ON is specified in the config.sys file, the
system will restart automatically and no dump will be taken when
a system trap or internal processing error occurs.
Luca Regoli, Societa' Italiana Autori Editori, provides the
following information on this command.
"This way whenever a trap occurs you don't get anything on the
screen. The PC beeps and [responds] as if you had depressed
CTRL+ALT+NUMLOCK / NUMLOCK.
"Not very useful though I don't know how to get traps infor-
mation from the dump disk (and don't want to download all 20Mb
dump of memory any time I get a trap)."
NEW TRAPDUMP
The TRAPDUMP command allows the conditions under which a trap will
initiate a System Dump to be set dynamically. Prior to Warp 3.0 FixPak
29, the System Dump setting could only be manipulated from CONFIG.SYS by
use of the TRAPDUMP statement.
Use of this command should be made under the direction of service
personnel.
Warning: The initiation of a System Dump causes an immediate termination
of the system without any shutdown. No file system shutdown is performed.
The system behaves as if a fatal crash has occurred, thus under rare
circumstances data can be lost.
The command syntax is:
TRAPDUMP [[ON] | [OFF] | [R0]] [x:] [/NOCHECK]
where:
■ ON enables all application and system traps to initiate a System Dump.
■ OFF disables automatic dump initiation.
■ R0 enables only Ring 0 traps to initiate a System Dump.
■ x: specifies the Dump Partition.
■ NOCHECK overrides the system level check for WARP 4.0, since use of
this command on a system level prior to FixPak 29 is equivalent to the
SYSDUMP command.
SYSDUMP
The SYSDUMP command forces a System Dump to be initiated, regardless of
the TRAPDUMP settings. This command is provided for the use of service
personnel to allow Dump Initiation to be automated through use of a
command file.
Warning: The initiation of a System Dump causes an immediate termination
of the system without any shutdown. No file system shutdown is performed.
The system behaves as if a fatal crash has occurred thus under rare
circumstances data can be lost.
The command syntax is:
SYSDUMP [/NOPROMPT]
where:
■ NOPROMPT allows the Dump to proceed without the prompt and response to
message:
"Do you want to force a system dump? (Y/N)"
DUMPPROCESS=x
Activates the Dump Process. Any application process that traps
will cause a process dump. The information will be written to
a dump file named PDUMP.xxx where xxx is an index that is
incremented each time a new process dump is created. This dump
file resides in the root directory of drive specified in "x".
PROTECT16
Haven't found out about this one yet. Comments?
AUTOFAIL=YES
This command does not appear in your config.sys. If not set to
Yes, OS/2 default is No. In the default setting, when an error
occurs, OS/2 will only display a window informing you of the
problem. If you wish to see the actual error code information,
set AUTOFAIL to Yes.
<<=NOTE=>> This command can't be run from an OS/2 prompt.
<<=TIP=>> Paul Kurr writes: "I set this value to YES on my
machine so that I'm not interrupted with those pesky drive not
ready popups and such. AUTOFAIL=YES takes the "first" option
in those windows presented (usually return error code to program).
"This can be seen most easily when running WIN-OS2 with a CDROM
installed--either empty or with a music CD in the drive. With
AUTOFAIL=NO (default) OS/2 pop's up the window stating that my
drive "E" is not ready. With AUTOFAIL=YES, the first "selection"
from that error is executed -- returning the failed drive status
to WINOS2, which just keeps running fine."
VME=NO
If you attempt to run WIN-OS2 and see the error message DOS 5
Error, you may need to add this command. Paradox V4.5 for DOS
and Turbocadv3.2 for DOS under Warp 3 are known to need this
command in some cases. The code to support Virtual Mode
Extensions on Pentium machines will occasionally causes problems
with Warp. This command generally solves the problem.
SET BEGINLIBPATH=C:\OS2
SET ENDLIBPATH=C:\OS2
With Warp, IBM has introduced the ability to dynamically change
LIBPATH using two new environment variables: BEGINLIBPATH and
ENDLIBPATH. These commands are most useful in CMD or BATCH
files, but can be used in your config.sys. Any directories that
appear in the BEGINLIBPATH variable are searched before
directories in LIBPATH, and directories that appear in the
ENDLIBPATH variable are searched after those in LIBPATH.
-----------------------------------------------------------------
7. SAMPLE CONFIG.SYS FILES.
-------------------------------------------------------------------
I deleted the old samples as nobody I know is working nowadays with
4MB or 8MB, but its possible if you like slow systems :-)
Also is the config on every system very different from others.
In the times of large memory - 64MB and up - it is not necessary
to save 3KB of Ram by optimizing the config.sys when every simple
Office needs 32 MB or more (K.S.)
Instead I've inserted here some useful tips to speed up your
system by removing 'unwanted' or 'unneeded' and how to use other
Installable File Systems (for Windows, Linux, Apple, TVFS) - the
Zipstream.IFS is not mentioned here as great drives with lots of
empty space are so cheap today that the use of an Disk-Compression
is no more advised (if it was ever).
The best way to optimize your system is
1. to use only HPFS
2. Use OS/2 without dos and windows sessions (so you get also
rid of those nasty little algorithms called virus)
3. Don't use voicetype if you don't need it, you can also make
different boot options (with and without VT) see Chapter 8.
4. Use small apps (like Papyrus) and not those Ram-Hogs like
Staroffice
5. Use native apps (not Java, Windows, Mirrorports like Word-
perfect for OS/2)
6. Delete the OpenDoc-Part by using 'selective-delete', as
OpenDoc is deplorably death.
Btw. when you compare the speed of windows and OS/2 on the same
system, remember that windows can only boot from the first partition,
the one which is on most drives the fastest !
Using removable media together with OS/2 and newer Fixpaks slows
bootup significantly. As an bargain (compared to windows, all
versions) you get dynamically assigned drive letters, an feature
that saves you from the drive-letter chaos in Windows whenever
you change an partition, drive etc.
------------------------------------------------------------------
If your only internet connection is via a modem, then you
can comment out (or delete) the following lines from CONFIG.SYS
in Warp 4
------------------------------------------------------------------
REM DEVICE=C:\IBMCOM\LANMSGDD.OS2 /I:C:\IBMCOM /S
REM DEVICE=C:\IBMCOM\PROTMAN.OS2 /I:C:\IBMCOM
REM RUN=C:\OS2\SMSTART.EXE
REM CALL=C:\IBMCOM\PROTOCOL\NETBIND.EXE
REM RUN=C:\IBMCOM\LANMSGEX.EXE
REM DEVICE=C:\MPTN\PROTOCOL\AFOS2.SYS
REM DEVICE=C:\MPTN\PROTOCOL\IFNDIS.SYS
REM CALL=C:\OS2\CMD.EXE /Q /C C:\MPTN\BIN\MPTSTART.CMD >NUL
REM DEVICE=C:\IBMCOM\MACS\NULLNDIS.OS2
------------------------------------------------------------------
If you don't run DOS/Windows TCP/IP programs, then you can remove
the DOS TCP/IP support. The relevant lines in CONFIG.SYS are:
------------------------------------------------------------------
REM DEVICE=C:\tcpip\bin\vdostcp.vdd
REM DEVICE=C:\tcpip\bin\vdostcp.sys
REM RUN=C:\tcpip\bin\VDOSCTL.EXE
------------------------------------------------------------------
If you don't use Voicetype remove the following
------------------------------------------------------------------
Remove all statements in LIBPATH, SET PATH, SET DPATH and SET HELP
pointing to Voicetype (normally they start with x:\vt)
Then delete the following lines:
SET SPCH_RUN=X:\VT\SPCH_RUN
SET SPCH_RO=X:\VT\SPCH_RO
SET SPCH_RW=X:\VT\SPCH_RW
SET SPCH_BIN=X:\VT\SPCH_BIN
SET SPCH_PATH=X:\VT\SPCH_RO\LANGS\%L\POOLS
SET SPCH_TRN=X:\VT\SPCH_DBF
<<=TIP=>> You can also make two different configurations and
boot them alternately by pressing ALT-F1 see Chapter 8. or
how to restore a damaged Config.sys file from a backup copy
-----------------------------------------------------------------
Removing Artchron and other 'unwanted' autostarts
-----------------------------------------------------------------
There is an clean way of removing the register program from your
system. Navigate *through the Drives ICON* to /OS2/install/Installed
Objects and double click on "Install Object - Inventory". Then
check the box next to "art" and then click on "uninstall" and then
select "art" in the next box that opens and then "uninstall"
again...this will totally uninstall the "art" directory and all
components relating to registration.
Some applications (like Staroffice, Smartsuite, Amipro) install
some 'reminders' or 'speeders' in the autostart-folder
remove or delete them, they are normally not needed.
-----------------------------------------------------------------
OS/2 and other Operationsystems
-----------------------------------------------------------------
OS/2 and Linux
There is an excellent FREE EXT.IFS by Matthieu Willm
You can find the latest version of ext2-os2 at the ext2-os2 home page :
http://www.geocities.com/SiliconValley/Bay/5313, or many other
bbs and servers
ext2-os2.ifs is a file system driver that allows OS/2 to
seamlessly access Linux native partitions (ext2fs partitions)
in both read and write modes. Once installed, Linux partitions
appear as standard OS/2 drive letters, one per Linux partition.
It is a port of the original Linux ext2fs kernel code.
ext2-os2 can even be used without Linux, as it can format or
check ext2 file systems directly from OS/2. This can be useful
for people who need huge cache sizes, for large compilations for
instance ; it can also be useful for people wanting long file
names on removable media.
<<=WARNING=>> Although it is possible to install OS/2 on an
EXT2 Partition it is not recommended to do so, as extented
attributes are not supported.
-----------------------------------------------------------------
OS/2 and Windows NT
OS/2 recognizes NTFS formatted drives falsly as HPFS
Using the FREE EXT2FS necassary for Linux the NTFS partition
can be hidden by inserting
BASEDEV= EXT2FLT.FLT <options>
to your config.sys file. The following command line options are allowed:
/Q Quiet install. Prevents the filter from displaying messages.
/V Verbose install. Displays some diagnostic messages.
/W Allows the virtual partitions to be written to.
/A Virtualize all partitions found. The only good reason to use
this is along with the /M option when you want to control
the mounting order of all the partitions. You must use the
/W option if you use the /A option; otherwise OS/2 may crash
when it tries to write to the partition.
PLEASE NOTE: Using the /A option may change your drive
letters causing the your system to be unbootable. Use
the /M option together with /A. (This may change in the
future.
/M <mount list> Mounts the partitions in the order specified in the mount
list, which should be a list of numbers separated by commas.
The partitions are numbered 0 on a first come basis. (Not
the OS/2 uses.)
E.g. if you have one disk, the OS/2 Bootmanager installed and NT is on
the first partition the correct options are
BASEDEV=EXT2FLT.FLT /A /W /M 1
<<=TIP=>> Windows NT 4.0 can use HPFS-Partitions if you have
the pinball.sys out of NT 3.51 and the utility hpfs_nt4.zip
by Chris Behnken, available at http://www.htc.net/~nbehnken.
ATTENTION pinball.sys can only operate with disks or partitions
up to 4GByte.
<<=TIP=>> There is also an ALPHA NTFS.IFS by Daniel Steiner,
available at http://npw.cgnet.de/dsteiner
-----------------------------------------------------------------
OS/2 and Windows 98 or Windows 95
Henk Kelder has developed an FREE FAT32.IFS
it is available at http://www.os2ss.com/information/kelder/index.html
and many other websides and bbs under OS2FAT32.ZIP
Latest version is 0.81
There is also an ALPHA of an VFAT.IFS, by Daniel Steiner,
see above Tip.
-----------------------------------------------------------------
OS/2 and Apple Hfs
IFS=C:\HFSDIR\HFS.IFS
Loads the Installable File System for reading Apple HFS-Drives
and disks
IF you make use of this IFS it must reside in front of the CDFS.ifs
there are also needed the commands
BASEDEV=HFSFLT.FLT in the config.sys, HFSFLT.FLT must reside in the
OS2/BOOT directory
and
RUN=C:\HFSDIR\HFS.EXE
The FREE HFS-Package by Marcus Better can be found at
http://www.student.nada.kth.se/~f96-bet/HFS
Unfortunately Marcus Better has stopped all development for OS/2
There is also iHPFS by Marcus Better an package to make under
plain old Dos HPFS formatted drives readable.
See also the FREE HFS Utilities from the same author at http://
www.student.nada.kth.se/~f96-bet/hfsutils/
-------------------------------------------------------------------
OS/2 and T(oronto)V(irtual)F(ile)S(ystem).IFS
Author: Mark D. Leitch
The TVFS provides a virtual OS/2 file system that combines symbolic links,
search paths, and permissions. Through the TVFS, local and remote file
systems may be combined into a single, virtual file system.
The FREE IBM EWS is available at many servers and BBS
Latest version is 2.11
<<=Tip=>> Kai Evers has developed an easy to use FREE PM-Interface for
controlling and using the TVFS. It is available at
http://www1.stuttgart.netsurf.de/~kevers/
<<=TIP=>> See also TVFS-RM by Jürgen Dankoweits at http://www.geocities.com
SiliconValley/Way/3792
-------------------------------------------------------------------
OS/2 Ramdisk IFS
Karl Olsen has developed an great FREE RAMFS-IFS available at
http://home3.inet.tele.dk/kro
-----------------------------------------------------------------
8. HOW TO RESTORE A DAMAGED CONFIG.SYS FILE FROM A BACKUP COPY.
I moved the advice for OS/2 2.1 at the end as most users use
Warp with his built-in backup option, instead you can find an
advise how to get multiple configurations in Warp. (K.S.)
In OS/2 Warp, IBM provides an archive feature which
can be activated by opening your Desktop settings, click on the
Archive Tab, and then click on "Create archive at every system
restart". With this feature activated, you can simply press
Alt+F1 at boot and be presented with a menu which will allow you
to boot with an alternate (backup) config.sys file. See your
user documentation for details.
-----------------------------------------------------------------
HOW TO GET MULTIPLE CONFIGURATION FILES IN WARP 3 or 4
-----------------------------------------------------------------
Save your config.sys
Make an ALTF1x.CMD file in /OS2/BOOT with the following content
'copy \os2\boot\config.x \config.sys'
Copy your Config.sys to \OS2\BOOT\CONFIG.X
Edit CONFIG.X
Repeat for ALTF1y.CMD ...
Repeat for ALTF1z.CMD ...
Now edit ALTF1TOP.SCR in \OS2\BOOT
Insert 'X - Start config.x'
'y - Start config.y'
'z - Start config.z'
ATTENTION ! for every line you insert you have to delete one !!
for x and y you can use every letter that is not occupied by the
Boot-Menu
<<=TIP=>> The alternative config.* files can be easily edited by
using configinfo, simply make an right mouseclick in the upper
configinfo window and choose alternative config.sys
Here's one sample for an German Warp 4
WIEDERHERSTELLUNGSOPTIONEN
Waehlen Sie die zu verwendende Systemkonfigurationsdatei aus, oder
geben Sie die Option ein, die dem gewuenschten Archiv entspricht.
ESC - Der Systemstart wird mit der ungeaenderten Datei \CONFIG.SYS
fortgesetzt.
F2 - Eine Befehlszeile wird aufgerufen (keine Dateien werden ersetzt,
die urspruengliche Datei CONFIG.SYS wird verwendet).
F3 - Der Primaerbildschirm wird auf VGA eingestellt, und das System
wird neu gestartet.
F4 - Das System ueber die Option 'Installation anpassen' starten.
F5 - Die Hardwareerkennung wird aktiviert.
F6 - Die Hardwareerkennung wird inaktiviert.
D - Mit Dos und Windoze
P - OS/2 Pur (ohne Dos und Win)
Durch Auswahl eines Archivs aus untenstehender Liste werden die aktuelle
Datei CONFIG.SYS, das Verzeichnis der Arbeitsoberflaeche und INI-Dateien
durch aeltere Dateien ersetzt. Diese aelteren Versionen koennen sich von
den aktuellen Dateien unterscheiden. Die aktuellen Dateien befinden
sich im Verzeichnis \OS2\ARCHIVES\CURRENT.
-----------------------------------------------------------------
HOW TO MAKE A BACKUP COPY OF YOUR Config and INI FILES in 2.X
-----------------------------------------------------------------
A. Boot OS/2 from the OS/2 Installation Disk.
B. Insert OS/2 Disk #1 when asked.
C. Press the ESC key when you get the first text screen. By
doing this you will be put into OS/2s command line mode.
D. Assuming that your backup copy of config.sys is in the root
directory of "C" drive and is named CONFIG.SAV, enter the
following command:
COPY C:\CONFIG.SAV C:\CONFIG.SYS
Press the ENTER key.
E. Remove OS/2 Disk #1 and reboot the system.
What if you didn't make a backup copy? IBM thought about you.
When OS/2 was first installed on your system, the installation
program made a backup copy of your original config.sys file.
It stored this file in C:\OS2\INSTALL. To restore from this
file follow the same steps above, EXCEPT, in step "D" enter the
following command instead of the one shown:
COPY C:\OS2\INSTALL\CONFIG.SYS C:\CONFIG.SYS
<<=TIP=>> Replace the config.sys file saved by the OS/2
installation program in the INSTALL directory with your most
current version, thus allowing you to restore from it. If you
are viewing this information using CNFGINFO.EXE, the Backup
option is set to do this for you.
CALL=C:\OS2\XCOPY.EXE C:\OS2\INSTALL\*.BK1 C:\OS2\INSTALL\*.INI /T /R /O
CALL=C:\OS2\XCOPY.EXE C:\OS2\*.INI C:\OS2\INSTALL\*.BK1 /T /R /O
Two files are essential to the operation of OS/2: OS2.INI and
OS2SYS.INI. If these files should get trashed, OS/2 isn't going
to function. Backing them up is very important. In OS/2
version 2.0, once booted, OS/2 will not let you access or copy
these critical files. One way to circumvent this is to create
your backups BEFORE OS/2 is booted. This CALL will do the trick.
It creates first a backup of your backup and then creates a
backup of the original files. This gives you a two generation
backup. This process will add time to your system boot.
Generally OS/2 does not care where you place something in the
config.sys file. This CALL is an exception in version 2.0. It
must appear before any other line because you need to complete
this backup process before OS2.INI AND OS2SYS.INI load.
<<=NOTE=>> In version 2.1, the INI files can be copied after
the system is booted by using OS/2s COPY command, but you may
wish to consider adding this CALL to your config.sys file to
automate the process.
<<=TIP=>> OS2.INI and OS2SYS.INI can also be reconstructed at
boot by holding down Alt-F1 during boot BEFORE the OS/2 logo
appears. You may need to hold the keys down for at least 20
seconds. During your initial installation of OS/2, the
installation process stored a copy of its original INI files
in the folder called INSTALL. When you press Alt-F1 at boot,
OS/2 moves these "backup" files into the OS/2 folder to
replace the current versions. The "CALL" shown above keeps
the INI files in your INSTALL folder current.
<<=WARNING=>> If you are using a version of OS/2 before Warp,
use the Alt-F1 key combination as a last resort because you may
lose all customizing and changes you have made to the WpS.
<<=NOTE=>> The switches used mean the following:
/T -- allows xcopying of files with System attribute
/R -- allows xcopying of files with Read-only attribute
/O -- allows xcopying *onto* a file which has System,
Read-only, or Hidden attribute.
-----------------------------------------------------------------
9. REXX SUPPORT FROM WITHIN THE CONFIG.SYS FILE.
The question of whether REXX programs can be called from within
the config.sys file has been asked by a number of people.
Russ Williams wrote to All:
RW> Can anyone tell me what restrictions there are on running
RW> REXX programs from config.sys (via "CALL=")? It doesn't
RW> work for me, and the on-line help is no help.
You cannot. The DLLs required to support Rexx are not loaded
until Presentation Manager is loaded. If you require Rexx
support earlier, look for a program call SRVREXX at a fine BBS
near you.
Adding the line RUN=SRVREXX.EXE to the config.sys will
immediately initialize Rexx. You will then be able to access
Rexx with or without PM being loaded.
-----------------------------------------------------------------
10. How to set the cache in system with less RAM
======================== Table 1.0 =============================
If you have formatted your system with only HPFS partitions, the
cache size in this statement, as set by OS/2 during installation,
is that noted under ONE FILE SYSTEM in the table below. If you
have both FAT and HPFS partitions, then OS/2 sets the cache
sizes to those noted under TWO FILE SYSTEM. The file system
which uses the greatest amount of your disk space gets the larger
default value.
MEMORY SIZE IN MB TWO FILE SYSTEM ONE FILE SYSTEM*
4 128/64 128/48
5 128/64 128/48
6 256/64 256/128
7 256/128 256/512
8 256/256 384/512
9 256/256 384
10 - 16 512/512 1024
17 - 32 1024/1024 2048
* Defaults in Warp are different and are shown as the second
number. On systems with more than 8MBs of RAM, the default
is 10% of available RAM to a maximum cache of 4MB.
========================== Table 1.1 ===========================
You can get better performance from your system by using your
available RAM in the most efficient and effective way. Select
the case that best describes the file system or amount of RAM
you use.
CASE 1: You use only HPFS or only FAT, but not both.
HPFS only. FAT only.
System memory of at least: Set CACHE to: Set DISKCACHE to:
16 MB+ 2048 2048
12 MB 1536 1536
8 MB 1024 1024
CASE 2: You use both HPFS and FAT with HPFS active and FAT
passive.
System memory of at least: Set CACHE to: Set DISKCACHE to:
16 MB+ 2048 512 -1024
12 MB 1536 256 - 512
8 MB 1024 128 - 256
CASE 3: You use both HPFS and FAT with HPFS passive and FAT
active.
System memory of at least: Set CACHE to: Set DISKCACHE to:
16 MB+ 1024 2048
12 MB 768 1536
8 MB 512 1024
<<=NOTE=>> For purposes of the table above, "active" and
"passive" are descriptors for the way a partition is used.
If it is seldom used, it is "passive." If a lot of disk
intensive I/O occurs on the partition, it is "active."
---------------------------------------------------------------------
11. Jerry Rowe's Warp Remote Install Page
This page is a preliminary FAQ about installing OS/2
Warp 4 over a laplink cable from a Server to a Client.
First, you must set the Server up to use the parallel port
(SSW Parallel MAC driver) network driver. You do this from
MPTS [just type MPTS at the command line]. Select the driver,
and add Netbios as a protocol.
Then Edit the SSW Parallel MAC driver in MPTS and Note its
address. It should be 40000000000A.
Then open up the OS/2 Warp Remote Install object.
Create the remote install disks. Be sure to use the same
SSW Parallel MAC driver.
Then edit the protocol.ini file on the 2nd disk. Inside it,
insure that the MAC address is something
other than 40000000000A. Using 40000000000B will work fine.
Save the file.
Now, shutdown and reboot the machine.
Then examine \ibmcom\lantran.log and look for the reference
to the Adapter # for the parallel port adapter. If you have
another adapter in the Server, the number may be 1,
otherwise it will be 0.
Find Server Adapter #
Note that the Adapter #=1 in the file below. If your parallel port
is setup for adapter #=0, then lantran.log will be different.
==file lantran.log=========================================
PARALLEL PORT MAC V 1.0 by Savant Software Inc. Copyright (C) 1994, 1995
SAVANT SOFTWARE: PORT ADDRESS(ES): LPT1
SAVANT SOFTWARE: PORT ADDRESS CONFIGURED: LPT1(378)
IBM LANVDD is loaded and operational.
IBM OS/2 LAN Netbind
IBM LANDD is accessing IBM 802.3 LAN Interface.
Adapter 1 was initialized and opened successfully.
Adapter 1 is using node address 40000000000A. The Token-Ring
format is 02000000
IBM LANDD was successfully bound to MAC: pmac_nif->VECTOR.
==end file lantran.log=========================================
Install service.exe and other files.
If they were not installed during the Warp install,
follow these instructions.
Given that my CDRom drive is I:, and My Warp 4 drive is H:,
issue this command:
[H:\]I:\CID\SRVIFS\thinsrv /s:. /t:h:\cid\SRVIFS
/r:h:\ibminst\tables\service.ini /tu:h:\
THINSRV completed successfully.
This creates a line in startup.cmd and creates startup.cmd
if necessary.
START H:\CID\SRVIFS\SERVICE.EXE /INI=SERVICE
Thinsrv also adds:
h:\cid\SRVIFS;
to the PATH and DPATH statements in CONFIG.SYS.
Because these changes will not take effect until a reboot,
the command in STARTUP.CMD will not work until then.
However, you can:
cd \cid\srvifs service /ini=service
to start it right away from the command line.
You will probably want to remove the commands from Startup.cmd
at this time to prevent the Server facility from running
all the time.
You may also want to create another cmd file with the service
command in it if you would like to run it interactively.
Edit h:\cid\service.ini
Note Alias's and Path near bottom. Should be correct for the CD
Note Adapter #. Should match # from Lantran.log.
=============================================================
;SRVIFS INI file for OS/2 Warp Remote Install Server - 7CPESGDV
Name = 7CPESGDV
GroupName = NO
Adapter = 1
MaxClients = 5
MaxFiles = 9999
ClientWorkers = 8
Path = I:\
Alias = ReadOnly,Single,CDROM,I:\
Alias = ReadWrite,Single,STATUS,H:\IBMINST\RSP\REMOTE
==============================================================
With these changes made, shut down the computer and reboot.
After it comes up, the GUI front
end for the Remote install should work.
===Config.sys on disk 1 ===================
CALL=A:\SRVATTCH.EXE z: \\7CPESGDV\CDROM
DEVICE=A:\SRVIFS.SYS
IFS=A:\SRVIFSC.IFS * /T
CALL=A:\SRVATTCH.EXE w: \\7CPESGDV\STATUS
RUN=Z:\CID\LOCINSTU\SRVREXX.EXE
libpath=.;\os2\install;\os2\dll;z:\cid\locinstu;
set os2_shell=cdboot.exe
set oemprogram=\ibminst\npconfig.exe
set exitwhendone=1
set ADAPTER_NIF=PMAC.NIF
set SRVNAME1=7CPESGDV
set SAVECONNECT=1
================================================
Now, change to H: [warp 4 drive] and start server.
cd \cid
SERVICE.EXE /INI=SERVICE
Now, boot the client off the disk set.
Should work. If it does not, check the hardware
configuration of the parallel ports and insure they
are set to bi-directional if that option is offered.
I successfully installed Warp 4 on a Thinkpad using
this method.
After the install, you should also be able to network
between the two computers over the laplink
cable using OS/2 Peer.
---------------------------------------------------------------------
12. THANKS
Judy McDermott from Judy's Warped World at
http://www.gt-online.com/~bri
Kovacs Istvan <kofa@alarmix.net>
Proportional Software and the DCF/2 development team.
Jan van Wijk, author of DFSee, LPTool.
Stefan Milcke
Denis Tonn
Oliver Poggensee the developer of Tyra/2
The Config.sys editor for OS/2; tyra2@gmx.net
Dan Carter (dan.carter@deathsdoor.com)
Doug Boulter
OS/2 Inside
Keith Medcalf
//END//