OS/2 Shareware BBS: 8 Other/08-Other.zip/cfgmt100.zip/cm2cfg.dat

Text File | 1999-04-05 | 192KB | 5,006 lines


-----------------------------------------------------------------
1. GENERAL

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. TSHELL is IBM EWS-Software to be found
 on ftp://ftp.pc.ibm.com/pub/pccbbs/os2_ews/

 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.

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.

LIBPATH=C:\NETSAPE\JAVA11;C:\NETSCAPE;.;C:\OS2\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. This means also before the above mentioned period ".".
 If you use Staroffice 4.0 check if thats correct, if
 not move the Staroffice Path behind Netscape and install
 Servicepak 2 for Staroffice or higher otherwise the Staroffice
 Browser wont function.

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.

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."

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 or FAT formatted removable disks a lot, then
 a reduced BUFFERS setting could impact the performance of these
 drives. (Thanks to Andrew Stephenson for reminding me to integrate
 removable drives also).

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.

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 5. 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.
 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.

 <<=NOTE=>> From the IBM Fixpak40. TRAP 000E WITH REMOVEABLE MEDIA
 This trap will happen to anyone who uses DevIoCtl that does
 things like EJECT, PROTECT, etc for Removeable Media and has
 removed all FAT cache from CONFIG.SYS.
 Workaround is to add DISKCACHE=64,LW to CONFIG.SYS.
 This problem will be fixed in Fixpak 41 and above.

 <<=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 which is shown
 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 1 ================================

 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 howto.dat 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.

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.

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.

 <<=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. This
 setting will also speed-up drives attached to the parallel
 port (e.g. Zip-Drives). On systems with less than 6MB of
 RAM, don't increase the size of these buffers.

 <<=TIP=>> If you need more than three LPT-Ports get the
 LPT49.ZIP Package from http://www.kellergroup.com.
 See also the command DEVICE=C:\path\LPT49.SYS under
 Device later in this file.

 The following REXX-Script also adds additional printer ports
 4-9 by generating the spooler-queues LPT4-9 in the OS2SYS.INI

   /*LPT4-LPT9 in OS2SYS.INI*/
   Call RxFuncAdd 'Sys.ini','RexxUtil','Sys.ini'
   do i=4 to 9
   call Sysini'System','PM SPOOLER PORT','LPT'||i,';'||'00'x
   end
   exit

 <<=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.

RESERVEDRIVELETTER=x

 New in Warp 4, Warp 3 with Fixpaks higher 24.
 Note: Multiple RESERVEDRIVELETTER statements are allowed but only the
 last one is used. Valid Driveletters are D - Z.

 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).

PROTECTONLY=YES/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."

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.

DEVINFO=SCR,VGA,C:\OS2\VIOTBL.DCP

 The same as DEVINFO=SCR,VGA,C:\OS2\BOOT\VIOTBL.DCP

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 2 for character set codes.

 =============== Table 2 ===================

   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
 ==========================================

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.

 <<=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 3 =======================================

 <<=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

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)

SUPPRESSPOPUPS=x

 SUPPRESSPOPUPS=0 will restore behavior of WARP3 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

 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,OFF,n

 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.

 <<=NOTE=>> IPE ON BOOT AFTER FIXPAK 35 INSTALLED ON UNI SYSTEMS
 If you experience a kernel trap (black screen trap) or get a messages
 stating that device drivers (such as CLOCK01.SYS) were not able to
 install at boot time add the following statement to the end
 of CONFIG.SYS: TRACE=OFF,6

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

 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.

 OLD TRAPDUMP=xx,d, prior to fixpak 29 for WARP 3.0

 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)."

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.

VIRTUALADDRESSLIMIT=2048

 Allows max memory allocated 2 Gigs of shared RAM. Only
 useful for developers.

 You must have a hard disk that can accomodate the swap
 file. UW2SCSIs are recommended for the swap disk unless you
 wish to see your computer behave like a washing machine in
 spin dry mode.

 <<=NOTE=>> The OS/2 Warp Server Adavanced Smp addendum
 states that this number can go to 3 Gigs.
 However the OS/2 Warp Server for E-Business (Aurora)
 docs say only 2 gigs can be allocated. No experience what is
 correct.

-----------------------------------------------------------------
2. IFS

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 128MB 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.

 <<=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, fdisk and much more.

 <<=TIP=>> For undeleting files on HPFS Drives use the great IBM
 EWS Tool File Phoenix (Rel. 1.35) by Joe DiAdamo.

 <<=Tip=>> /QUIET will give you access to dirty partitions, too.
 This is new to the 32-bit CHKDSK which will only run on Warp 3 and 4.
 There is an option /FORCE, I have seen it explained somewhere, but
 can't find out where.

 ========================== Table 4 ==============================

 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.

IFS=C:\IBM386FS\HPFS386.IFS /A:*

 The 386 High Performance File System is an enhancement of the regular
 HPFS and normally sold togehter with the LAN-Server. In contrary
 to HPFS it is not written in C but in Assembler and consists of an
 optimized Ring 0 SMB processor tightly coupled with a bootable
 installable file system. This architecture provides a much better
 file I/O performance, because the whole data flow operates within the
 Ring 0 privilege level

 <<=NOTE=>> With LAN-Server 3.0 the parameter 'useallmem' has to be set
 as parameter of HPFS386.IFS in the config.sys

 <<=NOTE=>> If you use the 'useallmem' parameter it is important that the
 hardware components within your machine have the ability to address memory
 above 16 MB. E.g the IBM 16/4 token ring adapter doesn't have this
 capability.

 <<=NOTE=>> On a very busy server system, it is possible to run out of
 heap space. If this occurs there may be a noticeable degradation in
 performance, and server requests may fail. If this happens freeup some
 memory on the server. ATTENTION: the heap can only grow to it's defined
 size, but never shrink unless the machine is rebooted.

 <<=TIP=>> Using a dedicated server with 32MB of RAM try using as much as
 20MB of cache on the machine. The LAN Server Tuning assistant tool can
 calculate a recommended value for you. There is no need to specify the
 threshold limits, as this is dynamically managed by LAN Server.

 <<=TIP=>> Consult the IBM reedbooks at http://publib.boulder.ibm.com
 or the wsonw4pdf. available at: http://rheooptik.fmf.uni-freiburg.de
 /www/faq/remmedia.htm

 <<=TIP=>> See also the howto.dat for an explanation how to
 install and tune the HPFS386.IFS.

 <<=ATTENTION=>> Some HPFS Tools (e.g. Partition Magic) have problems with
 the ACLs.

IFS=C:\OS2\BOOT\CDFS.IFS /C:4

 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.

 /V  Verbose.

 /w  enables Joliet support, new in Fixpaks.

DEVICE=C:\OS2\JFS.IFS /CACHE:(XX) /AUTOCHECK:D

 OS/2 Warp Server for e-business includes a new file system, the
 Journaling File System. This new file system is a file system available
 with IBM's AIX premier Unix-type operating system. What it offers,
 among other things, is the ability to manage volumes that exceed the
 space on one hard disk. For instance, a volume may consist of pieces
 from one or more physical hard disks which are seamlessly integrated into
 one volume. In addition to being able to set up very large volumes, a
 volume can be expanded at any time so it is larger than it was in
 real time.

 The default JFS cache size is 12.5% of the system's physical
 memory size. To change the JFS default cache size from its default
 value, edit the JFS.IFS statement.

 Because JFS allows fragmentation, a utility, DEFRAGFS, is included
 with JFS. All these abilities are enabled when formatting a volume
 with the FORMAT command. The below is the output of a "FORMAT /?"
 command.

 FORMAT drive [/ONCE][/4][/T:tracks][/N:sectors][/F:xxxx][/FS:xxxxx]
              [/L][/V[:label]][/BS:blocksize][/LS:logsize][/S]
     where:

     drive Specifies the drive to be formatted.
     /ONCE Specifies that only 1 disk, diskette, or disc is
      to be formatted and no prompt is to be displayed.
     /4 Formats a 360KB diskette in a 1.2MB drive.
     /T:tracks Specifies the number of tracks per disk side.
     /N:sectors Specifies the number of sectors per track.
     /F:xxxx Specifies the size to which the diskette is to be
             formatted. For example: 360, 720, 1.2, 1.44, 2.88.
     /FS:xxxxx Specifies the file system to use to format the
                disk. For example: FS:FAT or FS:HPFS or FS:JFS.
     /L Specifies long format procedure for optical read-write
        disks.
     /V:label Specifies the volume label.
     /BS:blocksize Specifies, in bytes, the block size desired
         for the file system. For JFS 512 bytes, 1024, 2048, or
         4096 bytes are valid.
     /LS:logsize Specifies, in megabytes, the size journal log
         to create for the file system.
     /S Specifies that files on the device will be sparse files.
        JFS has two file allocation schemes, these being "sparse"
        and "dense." Sparse allocation is the amount of space
        allocated to a random-access file when a block written
        may not be within the earliest portion of a file.
        Dense allocation allocates all the space prior to the block being
        written when the block is written. For instance, if a random-access
        file has 5120 bytes (ten 512 byte blocks), and the fifth block
        is written to, the resulting usage with sparse allocation is 512
        bytes. With dense, the resulting usage will be 2550 bytes, even
        though the first 2048 bytes are not yet being used. The sparse
        method is server efficient; only the space used is allocated to
        the file but this would presumably lead to fragmentation,
        since when another block is written, the sparse allocation will
        cause the data to not be in sequentially ordered sectors.

 JFS is a very powerful addition to OS/2; it eliminates
 any limiting factors and make OS/2 Warp Server the best
 option for serving files, and applications. A file size can be two (2)
 terabytes (two thousand gigabytes), the maximum volume size. This,
 along with OS/2 Warp Server's ability to extend beyond just one
 processor by using up to 64 processors, makes OS/2 Warp Server
 the most advanced operating system of its kind for the Intel
 processor.

 LVM.EXE is the new version of the FDISK command. It provides both
 logical and physical views of the hardfiles installed on the system.
 With LVM (Logical Volume Manager), users can

  Create Compatibility Volumes (partitions) which can be seen by
    pre-LVM releases of OS/2

  Create or delete Logical Volumes which span physical disks
    Extend file systems (JFS only)

  Delete Compatibility Volumes (partitions)

  Recover read or write failures from a portion of the disk
    going bad (JFS only)

 <<=ATTENTION=>> FDISK is no longer usable for managing partitions once
 the LVM has been used to create JVS Volumes.

 <<=NOTE=>> OS/2 needs for booting a HPFS or a FAT (better not) partition
 it can't boot from JFS.

IFS=X:\PATH\EXT2-OS2.IFS

 Ext2-os2 is a file system driver that allows OS/2 seamlessly access
 Linux native partitions (formatted with ext2) in read and write mode.

 Developed by Matthieu Willm

 You can find the latest version of the free ext2-os2 at:
 http://www.geocities.com/SiliconValley/Bay/5313.

 <<=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.

 For the use of EXT2-OS2 read the EXT2-OS2.IFS carefully

IFS=x:\OS2\FAT32.IFS

 Henk Kelder has developed a FREE FAT32.IFS
 it is available at http://www.os2ss.com/information/kelder/index.html
 as OS2FAT32.ZIP; Latest version is 0.88.

 (Install this one AFTER IFS=HPFS.IFS)

 The following options are supported:

 /Q           Quiet, not messages.

 /CACHE:nnnn  specifies the cache size in kilobytes. If omitted the default
              cache size is 1024KB. Maximum cache size is 2048KB.
                                     *NOTE*
              Cache memory is allocated as FIXED memory, so if you have less
              than 16MB I suggest you set this option to 512KB or less.

 /MONITOR     Set monitor ON by default. If omitted monitor is OFF. See
              MONITOR.EXE for more information.

 /RASECTORS:n Read Ahead Sectors.
              Specifies the minimum number of sectors to be read per read
              action and placed in the cache.
              If omitted the default differs per volume and equals the
              number of sectors per cluster times 2.
              The maximum treshold value used is the number of sectors per
              cluster times 4.

              You should note that the actual sector IO per read action is
              NOT determined by an application, but by the IFS. For FAT access
              single sector reads are done. For Directory and Files IO reads
              are done on a cluster base. By setting the RASECTORS you can
              define the minimum number of sectors the IFS will read from disk
              and place in the cache.

 /EAS         Make FAT32.IFS support EXTENDED ATTRIBUTES.

 see also CALL=x:\OS2\CACHEF32.EXE and BASEDEV=PARTFILT.FLT for more
 information

 <<=NOTE=>> For Warp 4 with fixpak 10 you need at least ver.0.88 or higher

IFS=C:\PATH\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 and
 RUN=C:\HFSDIR\HFS.EXE in the config.sys

 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 a 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/

IFS=C:\OS2\TVFS.IFS

 The T(oronto)V(irtual)F(ile)S(ystem)

 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.
 It is FREE IBM EWS. 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

IFS=X:\PATH\RAM64.IFS

 SEE RAM.IFS

IFS=X:\PATH\RAM.IFS

 RAMFS by Karl Olson is a "remote file system" (as opposed to a
 "local file system").

 Features

 Create as many RAM drives as you want, using the drive letters that
 you want

 Size only limited by available RAM and swap disk space

 Allocates swappable RAM from OS/2 as necessary when files are created,
 and releases it again when files are deleted

 Long file name support like in HPFS.  Case isn't significant, but
 preserved like in HPFS. Files with long names are not visible from DOS
 and WINOS2 programs.

 Extended Attributes - up to 64 KB total for each file/directory (HPFS
 supports up to 64 KB for each EA, up to 256 KB total for each file/
 directory)

 RAM is allocated in units of one page (4 KB)

 use RAMDISK.EXE to create a RAM drive. To create a drive R:, type
 RAMDISK R:, see also RUN=RAMDISK.EXE

 freely available at http://home3.inet.tele.dk/kro

IFS=X:\PATH\FTP.IFS

 Add following line to your startup.cmd
 start D:\PATH\R3COMM.EXE>d:\path\logfile
 Reboot

 With FTP.IFS you may map any ftp host you
 like to a drive letter and use all the utilities you have
 with FTP host. Any archiver, any File Manager, any BackUp program.
 Developed by Vitalij Timchishin ([e-mail]).
 Unfortunately it is no more FREEWARE, but shareware.

IFS=X:\PATH\CDWFS.IFS

 File System by the RSJ CD writing solution

 The file system CDWFS.IFS only provides the background process
 CDWFSD.EXE with commands contrary to earlier versions. The complete
 configuration?????? are no longer registered in the CONFIG.SYS file
 under "IFS=...\CDWFS.IFS" but in the CDWFSD_S.CMD" file in the
 installation register.

 <<=NOTE=>> I would need here some help of users cause I don't have
 the RSJ CD-Writer. Klaus Staedtler.

IFS=X:\PATH\NFS200.IFS

 The NFS (Network File System) for OS/2

IFS=E:\SRVIFS\SRVIFSC.IFS MONTAGE /S:5  /T  /A:0

 The ThinIFS by IBM.

 <<=TIP=>> Ideal for CID-Installations

-----------------------------------------------------------------
3. SET STATEMENTS

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 a 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
     ...

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 with
 the FREE 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.

 <<=NOTE=>> See the cm2.inf for FREE INI-maintenance programs.

 <<=TIP=>> You can also make a 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 with the FREE 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 the Presentation Manager is
 loaded and operating. It closes upon shut down.

 <<=NOTE=>> See the cm2.inf for FREE INI-maintenance programs.

 <<=TIP=>> You can also make a 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 a 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 a 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 /Parameter

 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.

 Parameters:

 /K C:\PROGRAM
 Starts cmd.exe together with a program (program could be any
 executable program).

 /S
 Disables CTRL+C. No interrupt for programs possible.

 /Q
 NO ECHO

 /C PROGRAM
 Starts a second command processor with a program. After execution of the
 program (e.g. DIR A:) return to the first command processor.

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 a 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.

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.

 <<=TIP=>> By Ulrich Moeller: You can perform a "shut down"
 from a command line. To do a shut down type SHUTDOWN and
 press enter. This starts the WPS. Once the WPS is open,
 you'll be asked to close all sessions and if you really
 want to shutdown. This command is also helpful if you are
 writing WPS-Programs and if you want to test WPS-DLLs.
 So you can easily restart the WPS by typing PMSHELL at the
 command-line. When you switch back to the commmand-line and
 press CTRL+C the WPS will be closed.

 <<=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.

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

 Sets the directory for temporary files

SET TMP=C:\TEMP

 Sets the directory for temporary files

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\SYSTEM and - if you want to
 execute Dos-Sessions - \OS2\MDOS.

 <<=TIP=>> In Warp4 without fixpak peerinst.exe doesn't work
 correct if the path exceeds 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 PROMPT=$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 formerly 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.
 Since Warp 4 you can find this command in all object-settings
 notebooks.

 <<=TIP=>> A Great enrichment for the menues, and a lot of
 other useful enhancements can be achieved by using the
 FREE XFolder, by Ulrich Moeller, available at http://www2.rz.
 hu-berlin.de/~h0444vnd/os2.htm, current release is 0.85

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 a 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.

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 KILLFEATUREENABLED=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)

 <<=NOTE=>> Does the same as the more common SET SCKILLFEATUREENABLED=1

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 SCPRETTYCLOCK=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, since Fixpak 5
 for Warp4.

SET PM_ASYNC_FOCUS_CHANGE=ON | ON x | OFF

 WARP 3 only,

 <<=ATTENTION=>> in Warp 4 these settings can be found unter [System Setup,
 System] on your Desktop. Together with Warp 4 this setting should not
 appear in your config.sys.

 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)

 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 [System Setup, 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.

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

 SOMIR is an acronym for IBMs System Object Model Interface Repository.
 These are the databases of all installed Classes and Methods etc.
 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;

 By default OS/2 puts a REM in front of the undelete directory
 To use OS/2s UNDELETE command, you must first UNREM the
 SET DELDIR to store the deleted files.

 This command points OS/2 to the directory you (means the statement
 can point to ANY directory you want), or OS/2 by default created
 to place deleted files in. It also indicates the maximum K bytes of
 files that will be stored in the DELDIR 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 a FREE IBM EWS Tool.

 <<=TIP=>> There is also some McIntosh like Trashcans. One 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 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

SET BOOKSHELF=C:\OS2\BOOK

 This command points to the on-line documentation (INF files)
 provided with OS/2 or other OS/2 programs and is used by
 view.exe when.

 <<=TIP=>> If you have a 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.

 <<=TIP=>> You can also start the inf-files by typing 'view *.inf'
 at the command-line (*=desired information file. If you set a
 parameter like e.g SET PMREF=pm1+pm2+pm3 then 'view pmref' all
 three inf-files will be shown.

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 DMIPATH=C:\DMISL\BIN

 Sets the Path for the Desktop Management Interface

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

SET VIDEO_DEVICES=VIO_SVGA

 Theses settings are for a SVGA video card.

SET VIO_SVGA=DEVICE(BVHVGA, BVHSVGA)

 Theses settings are for a SVGA video card.

SET VIDEO_DEVICES=VIO_VGA

 Theses settings are for a VGA video card.

SET VIO_VGA=DEVICE(BVHVGA)

 Theses settings are for a VGA video card.

SET VIDEO_DEVICES=VIO_MGA

 These settings are for a Matrox video card

SET VIO_MGA=DEVICE(BVHVGA,BMGAX64)

 These settings are for a Matrox video card

SET LANG=en_US

 Sets up the language and the country for applications
 that are using Unicode character sets, also for applications
 with a runtime library that supports "locales".

 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)

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 a 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)

 The complete variable is: SET TZ=SSS[+|-]nDDD[,sm,sw,sd,st,em,ew,
 ed,et,shift]

 SSS   Standardtimezonedescriptor, default EST
       positive values are west of 0 degree length
       negative values are east of 0 degree length

 n     Difference to Greenwich Mean Time in Hours, default 5

 DDD   Daylightsavingsdescriptor, default EDT

 sm    Month in which Summer Time starts, default 4

 sw    Week in which Summer Time starts, default 1
       postive values are counted from the beginning
       negative values are counted from the end of the month

 sd    Day at which Summer Time starts, default 0
       0 is sunday ( 1 monday ...) if the week is
       unequal zero (0), when the week is zero
       it counts the day of the month (1 to 31).

 st    Time of Summer Time start in seconds, default 3600

 em    Month in which Summer Time ends, default 10

 ew    Week in which Summer Time ends, default -1
       see sw for description

 ed    Day at which Summer Time end, default 0
       see sd for description

 et    Time of Summer Time end in seconds, default is 7200

 shift Size of the Time shift in seconds, default 3600

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

 IBM Works is a 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
 To reregister simply run the ibmwdesk.cmd in the IBMWORKS
 directory (under Warp 3 and 4).

 <<=TIP=>> If you only need a PIM get the FREE IBM EWS
 Excal.zip latest version is 3.0m

SET SPCH_MAINLANG=XX_XX

 Sets the desired language for voicetype if there are more
 languages installed. See also SET LANG

SET ULSPATH=C:\LANGUAGE;

 Sets the path for unicode language files and for applications
 with a runtime library supporting "locales".

 <<=TIP=>> By Bob Goode: If you use Communicator 4.04 and you get
 a 'no DNS entry' putting a space after the semicolon should
 resolve the problem.

SET OCRNOTES=C:\Faxworks\Calera

 SET OCRNOTES supports the optical character reader software from
 Calera.

SET PWRCHUTE=X:\PWRCHUTE

 Sets the path for the Powerchute Pro APC UPS

 <<=NOTE=>> Make sure that upsd.exe is in your STARTUP.CMD
 If you have a LAN the the following line must be in your
 IBMLAN.INI under [services]: ups=x:\pwrchute\upsd.exe, add
 net start ups to your STARTUP.CMD.

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 a folder or by a manual update using 'view,
 refresh'. Only available under Warp 4

 <<=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. Whitout this setting objects
 are ALLWAYS IN MEMORY. This means as longer the WPS runs, the
 more memory will be used.

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

 These 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 BEGINLIBPATH=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.

SET ENDLIBPATH=C:\OS2

 See Beginlibpath=C:\OS2 above

SET SOMDTHREADPEER=1

 setting by Lotus Smartsuite for Warp 4

SET LOTUS_CLS=D:\LOTUSW4\compnent

 setting by Lotus Smartsuite for Warp 4

SET SOMBASE=C:\OS2

 setting used by Lotus Smartsuite for Warp 4, the Toolkit and VAC++ 3.0.

SET SOMRUNTIME=C:\OS2\DLL

 setting used by Lotus Smartsuite for Warp 4, the Toolkit and VAC++ 3.0.

 <<=TIP=>>If you experience intermittent hangs of your system, check your
 LIBPATH statement in CONFIG.SYS to see if SOM.DLL is in a directory other
 than, and ahead of, OS2\DLL. If yes, either change the LIBPATH statement
 to move the directory after OS2\DLL or try renaming SOM.DLL to SOM.DLO.
 One known cause of this is VisualAge C++. It has a version of SOM.DLL in
 its DLL library and the installation puts this library ahead of OS2\DLL
 in the LIBPATH statement.

SET DSQCOMMTRACE=OFF

 setting by Lotus Smartsuite for Warp 4

SET DSSDIR=D:\LOTUSW4\ARBEIT\APPROACH

 setting by Lotus Smartsuite for Warp 4

SET DSSPATH=D:\LOTUSW4\APPROACH\

 setting by Lotus Smartsuite for Warp 4

SET ODBC_PATH=X:\PATH\

 Sets the path for Open DataBase Connectivity.
 The odbcinst.ini lists the installed drivers and
 the odbc.ini lists the registered databases.

 <<=TIP=>> Some applications like Lotus Approach copy
 the odbcinst.ini and the odbc.ini to \OS2. If you have
 other database applications which are using this setting
 ODBC won't function correct. In this case 1. copy all listed
 applications with keys and values out of the odbcinst.ini
 in \OS2 into the odbcinst.ini in the path defined by the
 set command. You can use any ini-editor for this operation.
 2. to actualize the list of drivers copy all keys and values
 inside the 'application' ODBC Drivers from the odbcinst.ini
 out of the \OS2 directory into the odbcinst.ini in the directory
 defined by the SET command. 3. copy the updated odbcinst.ini to
 the \OS2 directory.

SET TRIDENT_ENDIVE=OFF

 Disables endive with TRIDENT graphics chips

SET HW_CURSOR=OFF

 Disables the hardware cursor.
 Useful if you have a black box cursor with some graphic cards.

SET OGL_BIT_COUNT

 used by OpenGL to replace the bits-per-pixel report from the
 graphics device driver. Primary use is for when 32 bpp(non-packed)
 setup actually reports 24 bpp (packed).Do not use them unless you
 are having trouble.

SET OGL_SCANLINE_SIZE

 used by OpenGL to replace the scanline size report from
 the graphics device driver. Do not use them unless you are having trouble.

SET OGL_OVERRIDE_COLORS

 used by OpenGL to override the PM colors in the color
 palette. Only applicable when running in 8 bit.
 Do not use them unless you are having trouble.

SET X11SHELL=C:\OS2\CMD.EXE

 This identifies the shell or command interpreter to be used
 with XFree86/OS2. If you are using the default CMD.EXE as your
 OS/2 shell, this line isn't needed. Other shells that can be specified
 here are tcsh and ksh. Unfortunately 4OS2 doesn't work as a shell for
 XFree86/OS2.

SET SANE_CONFIG_DIR=X:\OS2SANE

 Points to the installation directory of the OS/2 SANE driver
 (Scanner Access Now Easy, http://www.mostang.com/sane for information;
 http://www.geocities.com/SiliconValley/Peaks/4320/sane2.html for the
 OS/2 binaries).

SET DISPLAY=hostname:0.0

 This tells the X server where to display its wonders.
 One might think that of course it should be displayed
 upon the screen attached to the video card of your PC and that
 is what OS/2 does. But remember that X was designed from the outset
 to be networked and makes no assumptions about where clients and
 servers are located. Normally, this should be set to the local host name
 with a :0.0 attached; this will do what you think should be done by default
 i.e. display on your monitor. You could have an IP address or full internet
 name instead of your hostname for remote display.
 Every X server has a display name of the form:

      hostname:displaynumber.screennumber

 The displaynumber and screennumber will change from :0.0 on multiuser,
 multidisplay systems.

SET XSERVER=X:/XFree86/bin/XF86_SVGA.EXE

 This is the hardware dependent portion of X as it identifies the
 specific X server to use with your hardware.
 You should set this to the specific server that supports your video
 card, this will be identified when you run the xf86config.exe program.
 The SVGA server is somewhat misnamed now as it is almost a catchall server
 for many video cards (e.g. from Matrox). You can find out which particular
 server you need to install from the xf86config program. Note that SVGA does
 not mean unaccelerated.

SET LOGNAME=user

 LOGNAME is there for the benefit of some programs that may
 need such settings. The documentation for XFreeOS/2 indicates
 that they may be used in the future. It should both be set to the
 same name as SET USER.

SET HOME=D:\user

 This is to point to the home directory of the user. X comes from a
 multiuser environment and uses each users home directory to store
 their individual program configuration and initialization files.

SET X11ROOT=D:

 This is an essential setting, pointing to the location of the
 \XFree86 directory. The recommended configuration is to have
 \XFree86 as a subdirectory directly off the root directory; in which
 case, the X11ROOT variable should point to the drive where XFree86/OS2
 is installed. It is possible to have \XFree86 elsewhere
 (e.g. D:\unix\emx\X\XFree86 with X11ROOT set to D:\unix\emx\X) but this
 isn't recommended as it may confuse some poor programs that assume the
 standard installation tree.

SET MANPATH=D:/XFree86/man

 This identifies the location of the man (manual) pages for XFree86.
 They can be displayed by the xman program. Man pages are
 brief and terse descriptions of the use of programs, generally
 describing the various invocation switches. They are part of the
 optional features of XFree86/OS2.

SET C_INCLUDE_PATH=c:/emx/include

 Sets the path for EMX if you want to develop programs on a
 drive different from the drive where emx is installed

SET LIBRARY_PATH=c:/emx/lib

 Sets the path for EMX if you want to develop programs on a
 drive different from the drive where emx is installed

SET CPLUS_INCLUDE_PATH=c:/emx/include/cpp;c:/emx/include

 Necessary if you want to compile C++ programs with EMX

SET PROTODIR=c:/emx/include/cpp/gen

 With EMX the genclass utility needs this environment variable

SET OBJC_INCLUDE_PATH=c:/emx/include

 Necessary if you want to compile programs with EMX written in
 the Objective C language

SET GCCLOAD=n

 n=time in minutes

 When compiling projects with GCC consisting of many modules
 (such as libraries) under OS/2, you can speed up compilation
 if you have enough memory by keeping GCC in memory.
 For example, to keep GCC in memory for 5 minutes, use

SET GCCOPT=-pipe

 Makes GCC use pipes instead of temporary files

SET TERM=mono or ansi

 For using GDB (the GNU debugger) and info (the GNU info browser)
 and other programs like e.g XFREE that use termcap
 This setting is needed by some programs. It sets the "preferred terminal
 type for the xterm or editor to be used". As you will find out,
 a xterm is a command line window in X, equivalent to an OS/2 window
 session. Other term types are available; they are described in your
 termcap file.

SET TERMCAP=D:/XFree86/lib/X11/etc/termcap.x11

 This is the "terminal capabilities" file that is searched to
 determine the settings for the terminal type indicated in the
 SET TERM variable. You will also have one (named termcap.dat)
 in \emx\etc. Either can be used. They are text files; have a look
 in them to see what terminal types are available. Not all may work in
 XFree86/OS2 as they may depend upon a DOS driver.

 SET TERMCAP=c:/emx/etc/termcap.dat

 For using GDB (the GNU debugger) and info (the GNU info browser)
 and other programs that use termcap

SET INFOPATH=c:/emx/info

 Sets the INFOPATH environment variable in EMX

SET GS_LIB=D:/GSTOOLS/GS5.50/FONTS;C:/PSFONTS

 Sets the fontpath with Ghostscript. OS/2 comes with some Adobe
 Type Manager fonts. If you wish to use these with Ghostscript,
 you should replace the FONTMAP file with FONTMAP.OS2, and add
 this environment variable

SET GS_LOAD=10

 Setting for Ghostscript, determines how long GSOS2.EXE and
 GSPMDRV.EXE will stay in memory for the number of minutes
 specified in the environment variable

SET EMXBOOK=emxdev.inf+emxlib.inf+emxgnu.inf

 Defines the books for emx. You also have to add the directory
 where the books reside - e.g. C:\emx\book - to the SET BOOKSHELF
 environment variable.

SET BA2_SCSI_LOGFILE=C:\SCSILOG.TXT

 This will create with BackAgain/2 a logfile of scsi-related
 messages. Good for testing errors.

SET ENSBROWSER=X:\directory\yourbrowser.exe

 Sets the default browser for the EmTec Suite

SET OBJD_AUTOTILENAV=1

 <<=TIP=>> By Frank Vos: Enables the use of two object navigators
 with Object Desktop in one window. You can also move files
 between two directories.

SET TELNET.PASSWORD.ID=XYZ

  Sets your Telnet Password

SET NFS.PERMISSION.BITS=775

 Setting for the Network file system NFS

SET NFS.PERMISSION.DBITS=775

 Setting for the Network file system NFS

SET DESKTOP=<path>

 Set the path for the Desktop

 After rebooting run the following REXX script to make the
 necessary changes to the INI files (for working copy it into a
 file and name it e.g Fixdesktop.cmd) :

 /*FIX BROKEN DESKTOP WITH ENVIRONMENT VARIABLE*/
    call RxFuncAdd 'SysLoadFuncs', 'REXXUTIL', 'SysLoadFuncs'
    call SysLoadFuncs
    call SysSetObjectData value('DESKTOP',,'OS2ENVIRONMENT'),,
    'OBJECTID=<WP_DESKTOP>'
 EXIT

 <<=TIP=>> If the SET DESKTOP variable is not in your config.sys
 you can use this REXX script to fix a broken desktop (You have to edit
 line 4: insert instead of e.g.D:\DESKTOP the drive and directory
 where your Desktop resides, for working copy it into a
 file and name it e.g Fixdesktop.cmd).

 /* FIX BROKEN DESKTOP*/
 call RxFuncAdd 'SYSLOADFUNCS', 'REXXUTIL', 'SYSLOADFUNCS'
 call SysLoadFuncs
 call SysSetObjectData '<Desktop directory, e.g. D:\DESKTOP>',
 'OBJECTID=<WP_DESKTOP>'
 SAY ' BROKEN DESKTOP FIXED.'
 EXIT

 <<=NOTE=>> For German users: Desktop is 'Arbeitsoberfläche', this
 is an exciting experiment in using 'German Umlauts' for an important
 part of an OS.

-----------------------------------------------------------------
4. DEVICES

 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, but I've included
 most common and all additionally basedev's of the fixpaks):

 The basedev's are loaded according to their extensions in the
 following order:

 SYS
 BID
 VSD
 TSD
 ADD
 I13
 FLT
 DMD

 This means all basedevices with the extension SYS are loaded first and
 those with DMD last. This could also the reason for some trouble you
 might have.

 For Warp 3 and 4 BASEDEV's must reside either in the root or in the
 \os2\boot directory. A rule IBM itselfs disregards e.g. with the IBM
 Thinkpad drivers. They are installed in \os2. If BASEDEVICE Drivers
 are not in these three directories (\;\os2;\os2\boot;) they will fail
 to work. In General it is recommended to copy all BASEDEVICE Drivers
 ONLY to your \os2\boot directory. If any installation routine copies
 them to another place please move them to \os2\boot.

 <<=TIP=>> You can identify Driver failures by pressing ALT F2 during
 boot as long as the screen displays OS/2 in the upper left corner.

 <<=TIP=>> Adding the /V (=Verbose) switch to drivers could tell
 you some useful information. Example BASEDEV=IBM1S506.ADD /V

 <<=TIP=>> Updated and new drivers can be found at:
 http://service.software.ibm.com/os2ddpak/html/ or at your
 hardware vendors site.

BASEDEV=PRINT01.SYS /IRQ

 supports attached printers on non-Micro Channel PC's.

 <<=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."

BASEDEV=PRINT02.SYS

 supports attached printers on Micro Channel PC's.
 See also BASEDEV=PRINT01.SYS for additional tips.

BASEDEV=IBM2FLPY.ADD

 supports diskette drives on Micro Channel PC's.
 See also BASEDEV=IBM1FLPY.ADD for additional tips

BASEDEV=IBM1FLPY.ADD

 supports diskette drives on non-Micro Channel PC's.

 <<=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.

 The correct setting for e.g. a IBM Thinkpad 560 with external
 floppy disk is (see the Warp Refernce book for a detailed
 description):
 BASEDEV=IBM1FLPY.ADD /A:0 /FORCE:2 /U:0 /F:1.44MB /U:1 /F:1.44MB

BASEDEV=IBM2SCSI.ADD

 supports SCSI disk drives on Micro Channel PC's.

 <<=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).

BASEDEV=IBM1S506.ADD

 supports (E)IDE disk drives, non-Micro Channel PC's.

 It is important to use IBMIDECD.FLT with the
 IBM1S506.ADD driver. If you are using the /BM or
 !BM parameters to enable or disable busmaster; you
 MUST specify the adapter with /A:x. You can also
 specify the unit on that adapter with /U:z.
 For example:

 BASEDEV=IBM1S506.ADD /A:0 /U:0 /!BM or /A:0 /!BM
 to disable BUS Master DMA

 BASEDEV=IBM1S506.ADD /A:0 /U:0 /BM or /A:0 /BM
 to enable

 Use the /V parameter to view what mode the drives
 are set to. For example:
 BASEDEV=IBM1S506.ADD /V /A:0 /U:0 /!BM

 In newer versions there is also the /W switch,
 it pauses the config.sys after displaying the verboses.

 <<=TIP=>> If you have an IBM Thinkpad 760E/ED/ELD/EL that exhibits
 sluggish harddisk behavior (pausing intermittently with hard drive
 light on) after FixPaks have been applied, add the /!BM parameter to
 the BASEDEV=IBM1S506.ADD statement (if present) in your CONFIG.SYS.
 This will disable the Bus Mastering function whose default has been
 changed from OFF to ON.
 Example: BASEDEV=IBM1S506.ADD /A:0 /!BM /U:1 /ATAPI /FORCE

 <<=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.

BASEDEV=IBMKBD.SYS

 The keyboard driver

 Together with the switch /NONE OS/2 starts even when no keyboard
 is attached. Useful for unsupervised operation.

 <<=TIP=>> For the mostly sold so called 'Win95-Keyboards' (how ironic, as
 with windows9x you can only loose) there are two replacement drivers
 One by Robert Muchsel ([e-mail]), Release is Ver 2.00 available
 under winkey02.zip, and a newer one available at:
 http://os2.avi.kiev.ua/ Release is ver.021

 <<=TIP=>> By Kovacs Istvan: If you try BASEDEV=IMBKBD.SYS /NUMON numlock
 could turned on like with the utility 'jshifter'. Works only with some
 releases of the IBMKBD.SYS delivered with Warp. According to the mails
 I've got it seems that the switch doesn't work on nearly most keyboards,
 so you have still to use 'jshifter' available at:
 http://www.gbar.dtu.dk/~c948129

 <<=TIP=>> If you prefer a so called Dvorak keyboard layout (a keyboard
 which tends to arrange the characters more ergonomic than the qwerty
 type - which was a need when constructing mechanical typewriters at
 the end of the 19.th century): since Fixpak 8 for Warp 4 (maybe
 earlier, but this was the first time I was aware of its existance)
 go to your keyboard settings in the System Setup folder and simply
 select Dvorak (for left and righthanded !, but only in english).
 Now you only need a keyboard with a Dvorak layout (or one of these
 old but beautiful IBM keyboards with a 'klick' and 'solid as a rock',
 here you can pull the caps and place em where you want).
 This is another new goodie in OS/2 IBM never speeks of.

BASEDEV=RESERVE.SYS

 This driver reserves hardwareressources for drivers, especially for
 those who are not recognized by the ressourcemanager.

 Arguments:

 /V
 /IO:
 /P:
 /DW:
 /EXC
 /MUL
 /MEM:
 /SHA
 /DMA:
 /IRQ:

 Switch . Format   . Example       . Description
 /IO:   . /IO:x,x  . /IO:340,4     . Reserve IO ports.
                                   . The first number is the base
                                   . port in HEX, and is followed by
                                   . the length (number of ports) in
                                   . HEX.

 /P:    . /P:x,x   . /P:340,4      . same as /IO:

 /MEM:  . /MEM:x,x . /MEM:CA00,100 . Reserve Memory.
                                   . The first number is the base
                                   . memory address in HEX, with the
                                   . assumption that the address is
                                   . XXXX:0, and is followed by the
                                   . length (number of address) in HEX.

 /DMA:  . /DMA:x   . /DMA:2        . Reserve DMA Channel
                                   . The number is in decimal format.

 /IRQ:  . /IRQ:x   . /IRQ:13       . Reserve IRQ.
                                   . The number is in decimal format.

 /EXC   . /EXC     . /EXC          . Exclusive resource attribute.

 /MUL   . /MUL     . /MUL          . Multiplexed resource attribute.

 /SHA   . /SHA     . /SHA          . Shared resource attribute.

 /DW:   . /DW:x    . /DW:10        . Decode width of IO address.
                                   . Valid numbers are 10 and 16.
                                   . Only valid with /IO: switch.

 More than one resource attribute per-resource entry is an error and
 is not allowed. If no attribute or decode width is set, the default
 is EXCLUSIVE and 16 respectively. For example, to reserve an IRQ 13
 EXCLUSIVE, DMA 0 SHARED, MEMORY CA00:0 for 1000 hex-bytes shared,
 IO ports 340 for 10 hex-ports EXCLUSIVE and with a decode width of 16,
 and IO ports 300 for 64 hex-ports with a decode width of 10, the
 following is specified:
 BASEDEV=RESERVE.SYS /IRQ:13 /DMA:0 /SHA /MEM:CA00,1000 /SHA /IO:340,10
 /IO:300,64 /DW:10

 <<=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=>> 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.

BASEDEV=AIC7870.ADD

 supports SCSI on Adaptec 7870 controllers (e.g. 2940)

 <<=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.
 It seems that the version 2.2 of the Adaptec 2940 driver
 does not work correctly with RSJ, but version 2.11 works fine.

BASEDEV=TMSCSIW.ADD [/Universal switch] [/Adapter ID [/Unit switch]]

 supports the following Tekram adapters :

 - DC-390W:   max 20MB/sec 16-Bit Fast Wide SCSI
 - DC-390U:   max 20MB/sec  8-Bit Ultra SCSI
 - DC-390F:   max 40MB/sec 16-Bit Ultra Wide SCSI
 - DC-390U2B: max 80MB/Sec 16-Bit Ultra 2 SCSI

 [Universal switch] - An option that applies to all adapters.

 [Adapter ID] - A:x, where x(start from 0) is the order number of the
 adapter that was found in the system.

 [Unit switch] - An option that applies to device(s) unit.

 Unit switches :

 I - Ignore the specified adapter.

 DM - Enable DASD manager support (default).

 !DM - Disable DASD manager support.

 SM - Enable SCSI manager support (default).

 !SM - Disable SCSI manager support.

BASEDEV=IBMINT13.I13

 Supports generic disk adapters supported by the bios.
 Using this driver is very slow, but it works with every
 harddisk supported by your bios, even scsi.

BASEDEV=CHKDSK.SYS

 New with Fixpaks supports large disks

BASEDEV=CMPXCHG8.SYS

 New with Fixpaks fixes the Pentium F00F bug

BASEDEV=TIMER0.SYS

 New with Warp4, Hardware timer for correct sound timings

BASEDEV=MWDD32.sys

 32-bit device driver support by Matthieu WILLM (Win32-OS/2
 and many IFS's rely on it). Part of the EXT2-OS2.ZIP package

BASEDEV=USBUHCD.SYS

 USB Universal Host Controller Driver

 <<=NOTE=>> On IBM 365 System you have to add the parameter /FS

BASEDEV=USBUHCD2.SYS

 USB Controller Driver for IBM DockSatation III

BASEDEV=USBD.SYS /REQ:USBUHCD$

 Basic USB Driver

BASEDEV=USBHID.SYS

 USB Human Interface Driver

BASEDEV=AHA152X.ADD

 supports SCSI on Adaptec 152x/1510 controllers.

 <<=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.

BASEDEV=AHA154x.ADD

 supports SCSI on Adaptec 1540/1542 controllers.

 <<=TIP=>> By Prof. C.W. Fischer Physics Department Director
 CPES Micro-Computer Lab. Users may be interested in a undocumented
 switch on the adaptec AHA154x.add file i.e /DBUFF. Anyone using
 this SCSI adapter will loose access to RAM above 16M.
 It's a Bus mastering problem on ISA (thanks to Steven Levine).

BASEDEV=SYM8XX.ADD

 supports the following Symbios host adapters:

 SYM53C810, SYM53C810A, SYM53C810AE (SYM8100S, SYM8100ASP)
 SYM53C815 (SYM815XS, SYM8150SP)
 SYM53C825, 53C825A (SYM8250S, SYM8251S, SYM8251D, SYM8250ASP,
 SYM8251ASP,SYM8251AD)
 SYM53C860, SYM53C860AE (SYM8600SP)
 SYM53C875, SYM53C875E (SYM8750SP, SYM8751SP, SYM8751D)
 SYM53C876 (SYM22801, SYM22802)
 SYM53C885
 SYM53C895 (SYM8951U)

 It may be that the drive does not support synchronous or tagged
 command queing. Use /!SN or /!Q on the driver.
 e.g. BASEDEV=SYMC8XX.ADD /V /!SN /!Q

BASEDEV=SYM_HI.ADD

 supports the Symbios host adapter: SYM53C896 (SYM22910)

BASEDEV=OS2CAM.ADD

 Old NCR SCSI Driver.

 <<=TIP=>> Replaced by newer ones from Symbios. Check for
 an update.

BASEDEV=AUTODRV2.SYS

 Autoconfigurator supports PCMCIA modems.

BASEDEV=PCM2ATA.ADD /S:2 /!DM /NOBEEP

 supports PCMCIA ATA devices.
 For the switches consult the pcmcia manual

BASEDEV=PCMCIA.SYS

 Card Services for PMCIA-Cards.

 <<=ATTENTION=>> Must be in front of all other PCMCIA Drivers

 See the howto.dat for identifying the correct socket
 services driver.

BASEDEV=IBM2SS01.SYS

 IBM Thinkpad 750 (and others) Socket services

 <<=ATTENTION=>> Must be in front of all other PCMCIA Drivers, but
 after PCMCIA.SYS

BASEDEV=IBMDSS01.SYS

 IBM ThinkPads Socket services

 <<=ATTENTION=>> Must be in front of all other PCMCIA Drivers, but
 after PCMCIA.SYS

BASEDEV=IBMDSS02.SYS

 IBM ThinkPad 720 Socket services

 <<=ATTENTION=>> Must be in front of all other PCMCIA Drivers, but
 after PCMCIA.SYS

BASEDEV=SSDPCIC1.SYS

 Intel PCIC compatibles Socket services

 <<=ATTENTION=>> Must be in front of all other PCMCIA Drivers, but
 after PCMCIA.SYS

BASEDEV=SSDTCIC1.SYS

 DataBook TCIC compatibles Socket services

 <<=ATTENTION=>> Must be in front of all other PCMCIA Drivers, but
 after PCMCIA.SYS

BASEDEV=IBM2SS14.SYS

 Socket Services driver for IBM Thinkpad

 <<=ATTENTION=>> Must be in front of all other PCMCIA Drivers, but
 after PCMCIA.SYS

BASEDEV=TPIC95SS.SYS

 Socket Services driver for Chembook 2600

 <<=ATTENTION=>> Must be in front of all other PCMCIA Drivers, but
 after PCMCIA.SYS

BASEDEV=CL6832SS.SYS

 Socket Services driver for Toshiba Tecra

 <<=ATTENTION=>> Must be in front of all other PCMCIA Drivers, but
 after PCMCIA.SYS

BASEDEV=ICRMU01.SYS

 PCMCIA Ressource Management. Only needed for OS/2 2.1

BASEDEV=XDFLOPPY.FLT

 supports IBMs 1.8mb OS/2 installation disk format.

 <<=TIP=>> After installation you can put a REM in front of the
 XDFLOPPY.FLT, as it's only needed for the installation disks and
 Fixpak disks.

BASEDEV=IBMIDECD.FLT

 Support for ATAPI CD-ROM drives attached to an IDE Port.

BASEDEV=IBMATAPI.FLT

 New with Fixpaks since Fixpak 6/35 supports ATAPI Removable Media
 like Zip100, LS120 attached to an IDE Port.

 <<=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 a detailed removable media FAQ.

BASEDEV=PARTFILT.FLT <options>

 PARTFILT.flt is a filter device driver for OS/2 that makes it possible to
 load an IFS for linux partitions. (Without this filter you must patch the
 partition table. On many systems doing so may cause LILO to fail.)

 The filter now is NOT specific for Linux.
 In addition this driver is capable to control in what order drive letters
 are assigned to partitions on fixed disks. It will also allow you to access
 hidden primary partitions under OS/2.

 PARTFILT.FLT supports the following options:

 /Q      Load quietly
 /W      Enables Writing to the faked partitions.
         Without this option the faked partitions are read-only.
 /A      This option does two things:
          - Disables OS/2 to access all partitions, but:
          - Virtualizes (or fakes) all known partitions.
            Known partitions are the normal FAT partitions,
            IFS (=mainly HPFS) partitions and the partitions specified
            with the /P option.
            All primary partitions of known types are also virtualized,
            and will be accessable from OS/2.

        This option must be used in conjunction with the /M option.

        When this option is specified, the /W option is automatically set,
        because otherwise OS/2 will not boot.

 /M <mountlist> - Specifies the order in which partitions must be mounted.
        Must be used with the /M option.

        WARNING: Incorrect usage of the /A and /M options could make your
                 system unbootable.

  => USING THE /A and /M OPTIONS is not advised! <=

     if you need more information on these options please see:

        http://ourworld.compuserve.com/homepages/hkelder

 /P <partition types to fake>

   This is option is used to tell PARTFILT which partition type are to
   be faked. You should NOT use partition types already supported by
   OS/2 since this would result in a single partition being mounted
   two times. The list should consist of partition type numbers (in
   hexadecimal), separated by comma's. See Howto.dat for a almost
   complete list of partition type numbers.

 To make PARTFILT.FLT fake a FAT32 partition the /P option should be /P 0B.
 To make PARTFILT.FLT fake a FAT32X partition the /P option should be /P 0C.
 To make PARTFILT.FLT fake a LINUX partition the /P option should be /P 83.
 Or you can use a combination of the types e.g. /P 0B,0C

 <<=NOTE=>> The best location in the config.sys seems to differ depending
 on your configuration. Some state FAT32.IFS will only work is PARTFILT is
 the first basedev, other claim it only works if PARTFILT is the last one.
 A specific problem was reported when using a SCSI powersave basedev that
 only seemed to work if PARTFILT was the last basedev.

 <<=NOTE=>> See also the howto.dat for dealing with the falsly recognized
 NTFS.

BASEDEV=HFSFLT.FLT

 Part of the HFS.IFS for accessing HFS formatted Apple Disks

BASEDEV=EXT2FLT.FLT <options>

 ext2flt.flt is a filter device driver for OS/2 that makes it possible to
 load an IFS for linux partitions. (Without this filter you must patch the
 partition table. On many systems doing so may cause LILO to fail.).
 Ext2flt.flt is part of the EXT2-OS2.ZIP package. Together with you can also
 hide the falsly recognized NTFS, see howto.dat for explanation.

 In addition this driver is capable to control in what order drive letters
 are assigned to partitions on fixed disks. It will also allow you to access
 hidden primary partitions under OS/2.

 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.)

BASEDEV=RSJIDECD.FLT

 Modified IBMIDECD.FLT for the RSJ CD-Toasting software since V 2.70 that
 works correct with writing commands and command timeouts. Will be removed
 as soon as a corrected IBMIDECD.FLT is available.

BASEDEV=LOCKCDR.FLT -Parameter

 Some CD recorders claim to be CDROM drives. As OS2CDROM.DMD allocates
 all CDROM drives at bootup, those recorders cannot be accessed by
 additional software, including the RSJ CD Writer File System. To
 correct this behavior, the filter device driver LOCKCDR.FLT is added
 to the file CONFIG.SYS; all already known CD recorders will be
 converted to WORM devices automatically.

 parameter -a: Filters all commands. Solves problems with the SCSI
 Bus reset after a session.

 parameter -i:"Recorder Name" can be used to specify the device name of
 the unknown CD recorder.

 Example:
    BASEDEV=LOCKCDR.FLT -i:"IMS CDD2000"

 In this example, the Philips recorder CDR2000 is added to the built-in
 list of CD recorders. During bootup, the OS/2-internal device tables
 are modified such that the CD recorder is treated as a WORM device
 instead of a CDROM.

 The name of all connected CDROM devices as well as whether they have
 been converted to WORM devices is printed to the screen while the
 system is booting.

 <<=Note=>> It is not necessary to specify the complete device name.
 In the example above, specifying -i:"IMS" would do the same job.
 However, the more complete the device names are specified, the
 less likely it is that a CDROM drive is converted to a WORM
 device accidentally.

BASEDEV=DSKSLEEP.FLT

 The SCSI Disk Sleeper Filter by Vitus Jensen.
 Spins down the Harddisk after a adjustable time.

BASEDEV=OS2SCSI.DMD

 SCSI Device Manager supports non-disk SCSI devices.

BASEDEV=OS2DASD.DMD

 Device Manager, is a general purpose driver for disk drives,
 and is always needed.

 Together with the 'new' OSDASD.DMD since fixpak 6/35 parameters are:

  /RF (removable to fixed) Together with this switch it is possible
      to handle formerly only as 'superfloppy' available removable
      disks as partitionized disks.

  /OF (optical to fixed) Like /RF but for MO (MagnetoOptical) Drives.

  /LF Forces all removable devices to be treated as Large Floppy
      rather than partitioned media.

  /MP Used to support allocating a predetermined number of drive
      letters for a partitioned removable media device. Note
      that this option only applies to partitioned removable
      devices, and is ignored for any other device type.

BASEDEV=OS2ASPI.DMD /SHARE /ALL

  ASPI Device Manager for drivers according the ASPI specification
  by Adaptec. Replaces the ASPI4OS2.SYS by Adaptec.

 <<=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. Also needed by PMSANE.
 If you are using RSJ CD Writer 2.7 you can add unsupported drives

BASEDEV=OS2PCARD.DMD

 PC-Card Device Manager

 <<=ATTENTION=>> Must be after $ICPMOS2.SYS. If no $ICPMOS2.SYS installed
 it has to be the last line in the config.sys.

DEVICE=C:\OS2\BOOT\TESTCFG.SYS

 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\BOOT\DOS.SYS

 A device driver used to communicate between DOS and OS/2
 applications running on the same system.

DEVICE=C:\OS2\BOOT\PMDD.SYS

 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 a 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

DEVICE=D:\OS2\BOOT\ASPIROUT.SYS

 The interface of ASPI Router merely is an extension of
 the interface of OS2-ASPI.DMD
 Needed by the FREE CDRECORD/2 V1.8a15 by Chris Wohlgemuth
 available at: http://www.geocities.com/SiliconValley/Sector/5785/
 And by the FREE SANE (Scanner Acess Now Easy) By Yuri Dario available
 at http://www.geocities.com/SiliconValley/Peaks/4320.

DEVICE=C:\OS2\WIN32OS2\WIN32K.SYS

 Win32k - Win32-OS/2 driver, description in WIN32.TXT of the w32os2
 package.

DEVICE=C:\OS2\BOOT\LPTDD.SYS

 This driver is for the LPTools, a 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

DEVICE=C:\OS2\BOOT\APM.SYS /Switch

 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. See also
 RUN=C:\OS2\BOOT\APMDAEMN.EXE

 Switches are:

 /B favorizes the direct connection to the APM-BIOS support
 /D favorizes the device-driver connection of the APM support
 /V x.y forces the compatibility to APM Version x.y (e.g. 1.0)

 Together with the APMDAEMN.SYS these settings can also be done
 by using the Power-Symbol in your System Setup Folder.

DEVICE=C:\THINKPAD\$ICPMOS2.SYS

 Driver supports energy management.

 <<=ATTENTION=>> Must be after all other listed drivers in the
 config.sys.

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\BOOT\OPTICAL.DMD

 New with Warp4 Device Manager for Optical devices like MO

 <<=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 a detailed removable media FAQ.

DEVICE=C:\OS2\BOOT\OS2CDROM.DMD /Q

 OS/2 driver used on many, but not all CD-ROM's.

 The /Q switch supresses error messages.

DEVICE=C:\OS2\BOOT\USBKBD.SYS

 The driver for the Universal Serial Bus Keyboard

DEVICE=C:\OS2\BOOT\POINTDD.SYS

 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\BOOT\PCLOGIC.SYS SERIAL=COM2

 Provides mouse support for Genius, Logitech, PC Mouse Systems
 ATTENTION: Must reside between POINTDD.SYS and MOUSE.SYS

DEVICE=C:\OS2\BOOT\MOUSE.SYS SERIAL=COM2 QSIZE=10 TYPE=X RELAXED

 Lets you use a mouse or track ball. This line also identifies
 the device dependend type of mouse you have and which COM port
 it is on. In this case, the device dependent mouse driver is
 loaded in your OS/2 CONFIG.SYS through a standard "DEVICE="
 line, before the MOUSE.SYS driver is loaded, and then on the
 MOUSE.SYS line there is the parameter "TYPE=", with a reference
 to the device name of the device. 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.

 ATTENTION: Together with an device independent Mouse (e.g. a IBM
 PS/2 Mouse) NO PARAMETERS are needed.

 The supported device dependent Types are:

 PCLOGIC$ for Genius, Logitech, PC Mouse Systems, Driver: PCLOGIC.SYS
 MSBUS$   for Microsoft Bus-Mouse,                Driver: NONE
 MSINP$   for Microsoft-Inport,                   Driver: NONE
 VISION$  for Visi-On:                            Driver: VISION.SYS

 <<=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.

 <<=TIP=>> If you have a so called scroll-mouse (e.g. from IBM,
 or Logitech get the scrollms.exe package from the OS/2 Device
 Driver Pack. If you want to have a 'scrolling-feature' with
 normal mice there is the FREE hots11.zip package by Samual
 Audet available at the authors internet side
 http://WWW.CAM.ORG/~guardia/programs.html

 <<=TIP=>> If you want to have animated mouse pointers (very nice);
 Christan Langanke has developed a FREE Version to get as AMPTR101.ZIP
 from the autors side at: http://www.online-club.de/m1/clanganke

DEVICE=C:\OS2\BOOT\USBMOUSE.SYS

 Enables the support for a USB (Universal Serial Bus) Mouse.

DEVICE=C:\OS2\BOOT\EXMOUSE2.SYS

 Kensington mouse driver for OS/2.

DEVICE=C:\OS2\RODENT\RODENT.SYS COM=1 BUTTONS=3

 Device driver for the shareware mouse driver call Rodent.

DEVICE=C:\OS2\BOOT\COM.SYS

 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. Older versions of COM.SYS are limited to
 57600 Baud, newer ones (e.g. deliverd with Warp 4) are able
 to do 115200 Baud.

 <<=TIP=>> There are two very good replacement drivers for
 COM.SYS\VCOM.SYS called SIO.SYS\VSIO.SYS. If you utilize
 communications software on a regular basis at high speeds
 (e.g. 57,600).

 <<=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. The 'normal adress for COM1 is 3F8 and IRQ 4, for
 COM2 2F8 and IRQ3.

 <<=TIP=>> With ThinkPads should the address be added.
 e.g: DEVICE=C:\OS2\BOOT\COM.SYS (1,3F8,4) (2,2F8,3)

DEVICE=C:\OS2\BOOT\COM02.SYS

 For IBM PS/2 model 90 & 95 only.

 Lets you use the communications ports COM1 and COM2.
 See also DEVICE=C:\OS2\BOOT\COM.SYS

DEVICE=C:\OS2\BOOT\USBCOM.SYS

 USB modem driver.

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. 57,600), 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. and
 DEVICE=C:\OS2\BOOT\COM.SYS

DEVICE=C:\OS2\BOOT\QCOM.SYS

 Quatech (www.quatech.com) asynchronious serial device driver for the
 Quatech ISA and PCI boards

  * High baud rates to 921,600 bits per second, depending on UART type.

  * Support for 16750 UARTs and their 64-byte FIFOs.

  * Up to 32 serial ports

DEVICE=C:\MGA\OS2\KMGAX64.SYS

 Driver for the Matrox Video Cards

DEVICE=C:\MMOS2\MVPRODD.SYS /I11 /D3 /S:1,220,1,5 /N:PAS161$

 Driver 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.

DEVICE=C:\MMOS2\ES1868DD.SYS /B:220 /D:1 /F:3 /I:5 /C:4 /M:300
       ,7 /N:ES18681$

 Sounddriver for the ESS1868pnp (many soundcards)

 <<=TIP=>> If you need a Mixer for this soundcard try the FREE
 MINIMIX2.ZIP by Marco G. Salvano ([e-mail]).

DEVICE=C:\MMOS2\ES1688DD.SYS /B:220 /D:1 /I:5 /N:ES16881$

 Sounddriver for the ESS1688

DEVICE=C:\MMOS2\SB16D2.SYS 1 1 5 5 220 4 330 /N:SBAUD1$ /Q

 Driver 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.

 <<=TIP=>> Look for the SB163264.ZIP package which contains
 all drivers for the soundblaster cards including those for the
 AWE 64.

 <<=TIP=>> If you are in search for a Mixer supporting the soundblaster,
 Christoph Bratschi has developed the FREE Mixomat 1.01b, for SB 16/32/64,
 and the newer one Mixomat 2.0 (unfortunately no more free), available
 at http://www.datacomm.ch/~cbratschi/

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$

 <<=TIP=>> Look for the SB163264.ZIP package which contains
 all drivers for the soundblaster cards including those for the
 AWE 64.

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:\MMOS2\CWAUDIO.SYS /N:BSAUD1$ /X1:0 /X2:0 /L:0 /LCAPT:MX

 Sound Drivers for the Crystal CS4232
 The switches are explained in the README of the driver.

 <<=TIP=>> If you have problems with the Yamaha OPL3-SAx chipset:
 According to a user, instead of using the Yamaha OPL-3 SAx drivers
 for the same audio chipset, using the driver for Crystal CS4232 works
 fine without any limitations.

DEVICE=C:\TP\MWave224\BIN\mwaveVDD.sys

 Driver for the MWAVE-DSP in Thinkpads

 <<=ATTENTION=>> The MWAVEVDD.SYS must placed before VEMM.SYS

DEVICE=C:\MMOS2\SSMDD.SYS

 Any information ? If yes tell me

DEVICE=D:\MMOS2\SPKRDD.SYS

 The Speaker audio device driver provide support for playing digital
 audio waveform files on the standard PC speaker by using the
 MMPM/2 audio system. The speaker driver provides support for
 PCM waveform files that are (8-bit/16-bit, stereo/mono, 11Khz-44khz).

 <<=ATTENTION=>> The standard PC speaker was not intended to play
 digitized waveform sound. In order to produce a reasonable
 approximation of the sound contained in .WAV files, the device
 driver requires exclusive use of the CPU for an extended period
 of time. This may have undersirable effects on performance critical
 multitasking.
 --> BETTER DON'T USE IT, if you need (or want) sound on a regular base
 better buy one of those cheap soundcards using e.g. a ESS 1868 Chip

DEVICE=C:\MMOS2\R0STUB.SYS

 Any information ? If Yes tell me please.

DEVICE=C:\MMOS2\MIDI.SYS

 Real Time Midi Driver new with Warp 4

DEVICE=C:\MMOS2\VCSHDD.SYS

 Any information ? If Yes tell me please

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

DEVICE=C:\OS2\PDITOU01.SYS

 See DEVICE=C:\OS2\TOUCH.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.

DEVICE=D:\BACKMAST\FTDVR.SYS

 Drivers of Backmaster tape backup system.

DEVICE=D:\BACKMAST\TC15DVR.SYS

 Drivers of Backmaster tape backup system.

DEVICE=D:\BACKMAST\PTDVR.SYS

 Drivers of Backmaster tape backup system.

DEVICE=D:\SVDISK\SVDISK.SYS

 Driver for the Super Virtual Disk by Albert J. Shan

DEVICE=C:\OS2\APPS\SYSIOS2.SYS

 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

DEVICE=C:\OS2\BOOT\VDISK.SYS 512

 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.

 <<=TIP=>> Better use the RAM(64).IFS by Karl Olson, see IFS.

DEVICE=C:\OS2\BOOT\LPT49.SYS

 Devicedriver out of the LPT49.ZIP package available for free
 at http://www.kellergroup.com.
 The LPT49 utility includes a device driver (LPT49.SYS) and command
 file (LPT49.CMD) for creating additional LPT ports on your system
 (LPT4 through LPT9). You can then install the fax printer object on
 any of these LPT ports. You can also create multiple fax printer
 objects on different LPT ports (set on the Output page of the printer
 object's Settings notebook), and each printer object can have
 different job properties (set with the Job properties button on the
 Printer driver page of the printer object's Settings notebook).
 Keller Group Inc. is the developer of PMFax and Faxworks.

DEVICE=C:\OS2\BOOT\IRDD.SYS 2F8 3

 Installs the Infrared Device Driver at COM2
 To print through that port, the driver INFRARED.PDR
 needs also to be installed.

 <<=TIP=>> For Thinkpads the adress and the IRQ should be added.

DEVICE=C:\XFREE86\LIB\XF86SUP.SYS

 Driver for XFree86

DEVICE=C:\OS2\PCMSSDIF.SYS

 PCMCIA Storage Driver for OS/2 (Interface)

DEVICE=C:\OS2\PCM2SRAM.SYS

 PCMCIA Storage Driver for OS/2 (SRAM)

DEVICE=C:\OS2\FLSH2MTD.SYS

 Storage Driver for OS/2 (FLASH MTD)

DEVICE=C:\OS2\PCM2FLSH.SYS

 Storage Driver for OS/2 (FLASH)

DEVICE=X:\PATH\CDMGRDRV.SYS

 Driver of the FREE CD-Rom Manager for Plextor SCSI CD-ROM
 drives. Developed by Markus and Christian Mueller. Available
 at http://ourworld.compuserve.com/homepages/mjm5

DEVICE=X:\PATH\RSJSCSI.SYS

 The device driver RSJSCSI.SYS provides simplified access to SCSI
 devices. The CD Writer File System uses this device driver to access
 the CD Recorder.

 Syntax:
   DEVICE=<Path>\RSJSCSI.SYS [-q] [-n<Driver Name>] [-x]
   where <Path> is to be replaced by the installation path.

  The optional parameters have the following meaning:
     -q While booting, ask user for confirmation before installing the
        device driver.

     -x This option allows using memory above the 16MB line. This
        works together with true 32-bit SCSI adapters, only (e.g. most
        EISA and PCI adapters).

DEVICE=X:\PATH\THESEUS2.SYS

 Driver for the memory analysis tool THESEUS/2 by IBM
 downloadable for free at:
 ftp://hobbes.nmsu.edu/pub/os2/util/system/t2spm.zip

DEVICE=E:\SRVIFS\SRVIFS.SYS

 Part of the ThinIFS by IBM

DEVICE=F:\PPM242A\ECRDRV.SYS

 Driver for PolyPM a Remote Service Management Solution
 http://www.iss2you.com

DEVICE=F:\PPM242A\RSMVDWO.SYS

 Driver for PolyPM a Remote Service Management Solution
 http://www.iss2you.com

DEVICE=F:\DCAF13\EQNRCSH.EXE

 Part of DCAF (Distributed Console Access Facility)

 <<=ATTENTION=>> If you have not the IBM Internal Y2K fix
 it won't work after 31.12.1999

DEVICE=F:\DCAF13\EQNVKBD.SYS

 Part of DCAF (Distributed Console Access Facility)

 <<=ATTENTION=>> If you have not the IBM Internal Y2K fix
 it won't work after 31.12.1999

-----------------------------------------------------------------
5. RUN, START AND CALL

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:ON|OFF|n 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.
     The new parameters in Warp 4 are LAZY:n (in Warp 3 it
     only allowed ON & OFF)

     <<=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.

     <<=NOTE=>> Nearly everybody has his own recommodations
     about the correct size, so don't bother if you find different
     recommodations. Better try what is working best on YOUR system.

     <<=TIP=>> These settings can also easily done by using Warp'nGO or
     Xfolder Ver.080 and higher. Available at http://www2.rz.hu-berlin.
     de/~h0444vnd/os2.htm

     <<=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.

   /READAHEAD:ON|OFF|n Turns read ahead on, off or set to 'n'
     read ahead workers. Only in Warp 4.0

 <<=TIP=>> According to the OS/2 Guild running Voicetype in Warp 4.0
 is speeded up with /READAHAED:ON

 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.

 ========================= Table 4 =============================

   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

 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).

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=>> A REM in front of RUN=C:\OS2\SMSTART.EXE will stop
 the following processes: SMSTART.EXE, DMISL.EXE the desktop management
 Interface service layer, ERLOGGER.EXE the error logger and
 FFST.EXE the first failure support technology.
 This is advised for all 'normal' users.

RUN=C:\MMOS2\MIDIDMON.EXE

 This is for MIDI

RUN=C:\OS2\CALIBRATE.EXE-C C:\OS2CALIBRAT.DAT

 See DEVICE=C:\OS2\TOUCH.SYS

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.

RUN=C:\MMOS2\QRYMMCD.EXE

 Queries the Audio CD

RUN=X:\IBMLAN\NETPROG\CACHE386.EXE

 Enables the cache for HPFS386. Only valid for the OS/2 Warp server advanced

 <<=ATTENTION=>>This entry has to be done manually. If this statement is not
 added you'll get the following error 'Net 3091: the Cache386.exe is not
 running. The server cannot be started.

 Adding the parameter /STATS will display the statistic usage cache
 usage. This will help you to size the cache to a size where the
 minimum sized cache achieves the maximum hit rate.

RUN=C:\OS2\RSRV.EXE

 By older versions of IBM Open32 for Warp3. Should be deleted
 after applying Fixpak 26 for Warp3.

RUN=d:\path\RAMDISK R:

 Creates a RAM drive together with RAM(64).IFS every boot.

RUN=C:\HFSDIR\HFS.EXE

 Part of the HFS.IFS for accessing HFS formatted Apple Disks

CALL=C:\OS2\CMD.EXE

 With this statement you can 'delay' the initializiation of the
 presentation manager. The effect is the same as if you would press
 'ALT F1' during boot (as long 'OS/2' is visible on the left upper
 corner of  the display) and then selecting the command-line option
 (F2 in Warp4). After typing 'exit' the command-line will be closed
 and boot-up finishes. Useful if you have to delete locked files
 (specially locked dll's).

CALL=C:\OS2\CHKDSK.COM D: /C

 This CALL statement will call the new 32-bit CHKDSK.COM, and will
 tell it what drive to check. This CALL statement must appear after
 the LIBPATH=, SET PATH=, and SET DPATH= statements, but before any
 other CALL statements in your CONFIG.SYS file.
 The /C option tells CHKDSK to check the drive only if it is "dirty" and
 it needs checking. It needs BASEDEV=CHKDSK.SYS loaded.

CALL=x:\OS2\CACHEF32.EXE

 CACHEF32.EXE is a helper program for FAT32.IFS with the following
 functions:
 - Check DISK state on boot, run CHKDSK if needed.
 - Start the LAZY WRITE daemon.
 - Set CACHE and READ-AHEAD parameters.
 - Set Longname behaviour.
 - Load a CP to UNICODE translate table for longnames and the default
   codepage.

 When run in the foreground and CACHEF32 is already running, it displays
 the CACHE parameters and allows you to modify the values. If no other
 copy of CACHEF32 is running, it detaches a background copy.

 When run in the background (detached), CACHEF32 will act as lazywrite daemon.

 CACHEF32.EXE supports the following options:

 /?    Shows help.

 /Q    Terminates CACHEF32. CacheF32 will be unloaded from memory, lazy
       writing will stop. (Performance will degrade).

 /N    Runs CACHEF32 without starting the deamon in the background.

 /D:nn Sets the DISKIDLE value. See OS/2 online help on CACHE.

 /B:nn Sets the BUFFERIDLE value. See OS/2 online help on CACHE.

 /M:nn Sets the MAXAGE value. See OS/2 online help on CACHE.

 /R:d:,n Set RASECTORS for drive d: to n.

 /L:ON|OFF Set lazy writing ON or OFF, default is ON

 /FS   Use short names internally.

 /FL   Use long names internally (default).
      (see LONG FILENAMES IN OS/2 AND DOS SESSIONS below)

 /P:1|2|3|4 Set priority for lazy writer. 1 is lowest, 4 is highest.
      Default 1 (= idle-time). This might be handy if the lazy-writter
      doesn't seem to get any CPU due to heavy system load.

 Note 1: the /T option has been removed in version 0.83.

 Note 2: if you notice that the /P options has any effect on your
        situation please let me know.

CALL=E:\SRVIFS\SRVATTCH.EXE M: CIDSRVM

 Part of the ThinIFS by IBM

CALL=F:\PPM242A\PPS242A.EXE

 Part of PolyPM Remote Service Management Solution

CALL=F:\DCAF13\EQNINNEW.EXE

 Part of DCAF (Distributed Console Access Facility)

 <<=ATTENTION=>> If you have not the IBM Internal Y2K fix
 it won't work after 31.12.1999

CALL=F:\DCAF13\EQNRCLD.EXE

 Part of DCAF (Distributed Console Access Facility)

 <<=ATTENTION=>> If you have not the IBM Internal Y2K fix
 it won't work after 31.12.1999

-----------------------------------------------------------------
6. DOS SPECIFICS

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.

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.

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.

LOADHIGH C:\OS2\MDOS\TSR.EXE

 LH does the same as LOADHIGH.
 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.

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.

-----------------------------------------------------------------
7. DOS DRIVERS

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\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\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.

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\MDOS\VPCMCIA.SYS

 Virtual Card Services driver for PCMCIA

DEVICE=C:\OS2\MDOS\VCDROM.SYS

 This is a CD-ROM device driver that provides support in DOS
 sessions.

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.

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.

DEVICE=C:\OS2\MDOS\VMGAX64.SYS

 Driver for the Matrox Video Cards

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\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.

DEVICE=C:\OS2\MDOS\QVCOM.SYS

 Quatech (www.quatech.com) asynchronious serial device driver for the
 Quatech ISA and PCI boards

  * High baud rates to 921,600 bits per second, depending on UART type.

  * Support for 16750 UARTs and their 64-byte FIFOs.

  * Up to 32 serial ports

DEVICE=C:\MMOS2\AUDIOVDD.SYS Parameter

 Dos Soundcard-Driver
 Parameter:
 PAS161$  for the MediaVision's ProAudio Spectrum Soundcard
 SBAUD1$  for the Sound Blaster 16 sound card

DEVICE=C:\MMOS2\VAUDDRV.SYS Parameter

 Dos Soundcard-Driver
 Parameter:
 ES16881$  for Soundcards with ESS 1688 chip
 ES18681$  for Soundcards with ESS 1868 chip

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.

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.

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=X:\OS2\MDOS\VPICPARM.SYS irq9_off

 Some applications like PCAS (and some terminal emulators) have problems
 sharing IRQ9 in a VDM. Since the DOS Virtual Device drivers are not
 loaded out of CONFIG.SYS, a new device driver VPICPARM.SYS has been added
 starting with Warp 3 FixPak 38 and Warp 4 FixPak 8.

 To prevent sharing of IRQ9 in a VDM, add the device in config.sys:
 Next, in the settings for the program that requires exclusive access to
 IRQ9, set the DOS setting HW_SHARE_IRQ9 to ON.
 When you next boot your system, VDMs will not share IRQ9.

DEVICE=D:\OS2\MDOS\VASPIDD.SYS

  Adaptec ASPI device drivers for SCSI support.

DEVICE=D:\OS2\MDOS\VASPI.SYS

  Adaptec ASPI device drivers for SCSI support.

DEVICE=C:\OS2\MDOS\VW32S.SYS

 WIN32s program support driver.

 You need additionally the whole win32s package.

-----------------------------------------------------------------
8. TCP\IP

DEVICE=C:\MPTN\PROTOCOL\SOCKETS.SYS /Parameter

 Part of the TCP/IP Protocol Drivers

 Parameters:

 /c:#        Failuresearch, COMPORT-Number; Standard = 2
 /v          Verbose
 /uis:0      disable ID for select(); Standard = ON
 /mem:#      amount of 4KB Clusters. Standard = 75;
             valid Range = 30 - 32766
 /gdt:#      max. amount of 64KB Blocks the Stack can arrange; Standard = 80

 <<=TIP=>> According to IBM there is the undocumented parameter
 /UIS:0 for use on 3172 Offload System to improve the
 performance. This parameter is only intended for use on a 3172
 Offload System and turns off the process id : thread id
 processing on select () calls in the stack

DEVICE=C:\MPTN\PROTOCOL\AFOS2.SYS

 Part of the TCP/IP Protocol Drivers

DEVICE=C:\MPTN\PROTOCOL\IFNDIS.SYS

 Part of the TCP/IP Protocol Drivers

DEVICE=C:\MPTN\PROTOCOL\AFINET.SYS

 Part of the TCP/IP Protocol Drivers

DEVICE=C:\TCPIP\BIN\INET.SYS

 TCP/IP Drivers for SLIP (Serial Line Internet Protocol)
 OS/2 TCP/IP Version 2 from the Warp 3 Internet Access Kit.

 <<=TIP=>> To get PPP (Pont to Point Protocol) download
 ftp://ftp.ibm.net/pub/PPP/PPP.ZIP

DEVICE=C:\TCPIP\BIN\IFNDISNL.SYS

 TCP/IP Drivers for SLIP (Serial Line Internet Protocol)
 OS/2 TCP/IP Version 2.00 IFNDIS Null Driver from
 the Warp 3 Internet Access Kit.

 <<=TIP=>> To get PPP (Pont to Point Protocol) download
 ftp://ftp.ibm.net/pub/PPP/PPP.ZIP

DEVICE=C:\MTPN\BIN\VDOSTCP.VDD

 DOS API Driver for the TCP/IP protocol

 <<=TIP=>> If you don't need TCP/IP support in DOS sessions
 REM this line:

DEVICE=C:\TCPIP\BIN\VDOSTCP.SYS

 DOS Driver for the TCP/IP protocol

 <<=TIP=>> If you don't need TCP/IP support in DOS sessions
 REM this line:

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

RUN=C:\MPTN\BIN\VDOSCTL.EXE

 DOS TCP/IP Stack processing

 <<=TIP=>> If you don't need TCP/IP support in DOS sessions
 REM this line:

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.

SET ETC=C:\MPTN\ETC

 Sets the environment variable for TCPIP. Defines where the configuration
 files (e.g. *.ini) and log-files for TCPIP are stored. Needed by many
 TCPIP applications.

 <<=TIP=>> If this setting is missing some applications won't start. You
 can also type 'echo %ETC%' at the command line to show where ETC is loacted.

SET NLSPATH=C:\MPTN\MSG\NLS\%N;C:\TCPIP\msg\DEDE850\%N;

 Sets the path for the language specific messages in TCP\IP V.4.1

SET TCPLANG=de_DE

 Sets the Language for TCP/IP V4.1

SET HOSTNAME=xyz.ab

 Sets the variable for the Hostname

SET USE_HOSTS_FIRST=1

 USE_HOSTS_FIRST determines whether the system will try to resolve names
 using the %etc\hosts file before asking the name server. It's often
 used in conjunction with the loopback, because you can place the line
 127.0.0.1 localhost in the hosts file, and any references to 'localhost'
 will be translated to IP address 127.0.0.1 without the name server.
 Needed by many programs (e.g. Visual Age for Java, XFREE86) or if a
 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 a 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 a command line

 <<= TIP =>> the necessary configuration can also be done by using the
 TCP/IP Notebook.

SET REXECDTIME=X

 X  = time in seconds
 -1 = never timeout

 Sets the timeout period for rexecd

 <<=NOTE=>> Works only when REXECD is started under the INETD. If not
 you can use the command:
 REXECD -t X (X = time in seconds, x = -1 will set to never timeout)

SET LPR_SERVER=server

 Name of the LPR-Server when using the LPD-Protocol (Line Printer
 Daemon) for printing via TCP/IP over a network (e.g using a LINUX
 Print-server). This setting can also be done by using the TCP/IP
 settings notebook. See also your TCP/IP-Reference.

 For networkprinting there are under OS/2 two functioning (unlike to
 windows, but thats nothing surprising) solutions: LPRMON and LPRPORTD.

 <<=TIP=>> If you don't need network printing for dos/windows it is strongly
 recommended to use the LPRPORTD, cause it doesn't use port redirection,
 so spooling is done on the server and not on your local machine.
 This means you should install the printer as a network-printer.
 It is useful to 'autostart' the LPRPORTD by select this option in the
 TCP/IP settings notebook.
 When printing is slow you have to upgrade the LPRPORTD. The upgrade is
 available at ftp://ftp.software.ibm.com/ps/products/tcpip/fixes/v4.0os2/
 latest/print/.

 <<=NOTE=>> When using the LPRMON you have to select the port-redirection
 of an lpt-port otherwise you'll get an error message like 'Queue contains
 more data'. In WinOS you have to select the LPTx.OS2 port not LPTx (like
 this should be done for every printer under WinOS). LPRMON is also needed
 when using a Samba-Server.
 Using LPRMON means you have to install the printer as a local-printer
 and then redirect the LPTx Port to the printing queue.
 Unfortunately OS/2 is limited to three LPT-Ports. Keller Group Inc. (the
 developers of PMFax and Faxworks) has developed a free-to-use solution to
 add up to 9 printerports. The software is available under LPT49.zip at
 http://www.kellergroup.com

SET LPR_PRINTER=printer

 Name of the printing queue when printing via TCP/IP. This setting can also
 be done by using the TCP/IP settings notebook.
 See also your TCP/IP-Reference.

SET LPR_USER=user

 Undocumented command to set the username under lpr-printing
 different from the default 'pc-user'. This setting can only be
 done by an entry in the config.sys. There is NO command line
 option.

SET USER=user

 Sets the name of the user under lpr-printing with TCP/IP V.4.1.
 If not set, default is 'pc-user'.

-----------------------------------------------------------------
9. JAVA

SET LIB=C:\JAVA11\LIB;

 Sets the Path for the Java Libaries

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.

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.

-----------------------------------------------------------------
10. NOVELL NETWARE NETWORK SUPPORT.

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.

DEVICE=C:\NETWARE\NMPIPE.SYS

 Loads the support for client-only Named Pipes support.

DEVICE=C:\NETWARE\NPSERVER.SYS

 Loads support for your workstation to function as a Named
 Pipes server.

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.

 <<=TIP=>> If you do not use NETBIOS applications, you can remove
 the NETBIOS driver from the config.sys and the NETBIOS section
 from the PROTOCOL.INI to remove some of the confusion this creates.
 You should also remove the virtual netbios drivers at the same time
 since these bind onto the NETBIOS driver and not the LM10 interface
 (which is why they appear after the NETWKSTA.SYS driver, so it can
 "eat" its resources first, then what is left over is assigned to
 NETBIOS.SYS). [<- Note: this should be NETBIOS.OS2]
 (The mentioned virtual NETBIOS drivers are
 \IBMCOM\PROTOCOL\LANPDD.OS2 and LANVDD.OS2)

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.

-----------------------------------------------------------------
11. LAN

DEVICE=C:\IBMCOM\PROTMAN.OS2 /I:C:\IBMCOM

 IBM OS/2 LAN Protocol Manager

DEVICE=C:\IBMCOM\LANMSGDD.OS2 /I:C:\IBMCOM /S

 The only thing I know about this is, that it writes a log named LANTRAG.LOG
 into X:\IBMCOM

DEVICE=C:\IBMCOM\MACS\IBMTOK.OS2

 IBM kompatible Token-Ring-Networkadapter

DEVICE=C:\IBMCOM\MACS\IBMNE200.OS2

 Eagle Technology NE2000plus Ethernet Adapter

DEVICE=C:\IBMCOM\MACS\NULLNDIS.OS2

 IBM NULL MAC-Treiber

 Installed if you have NO Network Adapter.

DEVICE=C:\IBMCOM\MACS\PMAC.OS2

 SSW-Parallelportdriver for Adapter without NIC

 <<=TIP=>> See also Howto.dat for an advice how to do a network
 for two Computers via the parallel port.

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)."

DEVICE=C:\IBMCOM\PROTOCOL\NETBIOS.OS2

 <<=TIP=>> By Roland Sambain. The conventions wisdom about IFS
 statements coming at the beginning of config.sys seems not to
 apply. i.e. for netbios to load correctly the device statement
 must comes before the IFS as below.
 IFS=C:\IBMLAN\NETPROG\NETWKSTA.200 /I:C:\IBMLAN /N
 I don't pretend to understand why but trial and error have proved
 this to be the case.

RUN=C:\IBMCOM\LANMSGEX.EXE

 Any help needed by you.

CALL=C:\IBMCOM\PROTOCOL\NETBIND.EXE

 IBM OS/2 LAN Netbind

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.

SET CSFUTILPATH=C:\CSF

 Needed setting if you want to speed up FixPak installation or setup
 a FixPak on a LAN drive for use by others (Redirected Install)
 together with CSF (Corrective Service Facility) 0.140.
 Indicates where you've installed the CSF files.

SET CDFCDROMDIR=X:\DIRECTORY

 Needed setting if you want to speed up FixPak installation or setup
 a FixPak on a LAN drive for use by others (Redirected Install)
 together with CSF (Corrective Service Facility) 0.140. Indicates
 where the FixPak can be found.

//END//