CONFIG.SYS RUN Statements
Return to The Config.sys Documentation Project Main Page
The Run statement in your config.sys file is used to run a program during boot up. Programs started by Run are executed in the background. The following pages describe these entries:
RUN=ACTVCOLL.EXE
Executable from Process Commander. The ACTVCOLL line gathers resource use information about sessions.
NOTE: By Mikus Grinbergs: For activity collection to work with FP12 systems and beyond, EXEPATCH must have been used to "hook" Process Commander into DOSCALL1.DLL.
Platform Support:
OS/2 2.x | OS/2 3.0 | OS/2 4.0 | OS/2 4.5x | eCS 1.x | eCs 2.x |
---|---|---|---|---|---|
Yes | Yes | Yes | Yes | Yes | Yes |
RUN=AEFSDMN.EXE
The AEFS daemon.
The syntax is: aefsdmn *
It is typically started in CONFIG.SYS by a RUN statement (NOT a CALL statement) or from a script using the detach command.
You can change the options of a running daemon with aefsparm. The syntax is the same. The parameters given to aefsparm are sent verbatim to the daemon. Error messages appear in the log file (if there is one).
The options are:
- --logfile Write log messages to the file specified by . By default, messages are written to standard error (which is the nul device if the daemon is started from CONFIG.SYS or using detach).
- --loglevel Set the severity threshold of log messages. Only messages with a severity lower than or equal to the log level are actually written to the log file. The levels are:
- 1 Fatal
- 2 Evil (i.e. not fatal but worse than a `normal' error)
- 3 Error
- 4 Warning
- 9 Debug
- --cache Set the maximum size of the cache per volume in 512-byte units. The default is 4096, or 2 megabytes per volume.
- --storagefiles Set the maximum number of open storage files per volume. To speed up access to the encrypted files AEFS keeps the most recently used ones open. The default is 16. This number should not be made too high; otherwise the daemon might run into the open file limit of the C runtime library (use emxbind -a aefsdmn.exe -h to change this).
- --files Set the maximum number of files for which AEFS may cache sectors. Every file in the cache has a slight overhead; hence the limit. The default is 4096 files.
- --lastaccess=[active|lazy] Specify whether the last-accessed fields of files should be updated always (`active') or only if other fields have changed as well (`lazy'). The default is `active'.
- --lazy=[on|off] Specify whether lazy-writing (or `write-behind') should be enabled. The default is `on'. If lazy-writing is enabled, AEFS will flush every volume every 5 seconds. This interval cannot currently be changed.
- --quit Kill the daemon. Useful for debugging. Detach all attached volumes first.
- --info Print statistics about the memory allocation of the daemon and about every attached volume. These appear in the log file.
NOTE: most options do not take effect for volumes that are already attached, only for volumes attached after aefsparm is run.
Platform Support:
OS/2 2.x | OS/2 3.0 | OS/2 4.0 | OS/2 4.5x | eCS 1.x | eCs 2.x |
---|---|---|---|---|---|
Yes | Yes | Yes | Yes | Yes | Yes |
RUN=AFNBINI.EXE
This daemon monitors/setups Netbios.
Platform Support:
OS/2 2.x | OS/2 3.0 | OS/2 4.0 | OS/2 4.5x | eCS 1.x | eCs 2.x |
---|---|---|---|---|---|
Yes | Yes | Yes | Yes | Yes | Yes |
RUN=APMDAEMN.EXE
New in Fixpaks, fixes some errors when using APM 1.2
NOTE: Using APMDAEMN could lead into inaccessability of attached drives on Thinkpads after 'awakening' from sleep mode (e.g. the Floppy-Disk of the TP560 refuses to work).
Platform Support:
OS/2 2.x | OS/2 3.0 | OS/2 4.0 | OS/2 4.5x | eCS 1.x | eCs 2.x |
---|---|---|---|---|---|
Yes | Yes | Yes | Yes | Yes | Yes |
RUN=ASP4INIT.EXE
Vortex AU8820 OS/2 initialization.
Platform Support:
OS/2 2.x | OS/2 3.0 | OS/2 4.0 | OS/2 4.5x | eCS 1.x | eCs 2.x |
---|---|---|---|---|---|
Yes | Yes | Yes | Yes | Yes | Yes |
RUN=ATKINIT.EXE
From Lanserver for Macintosh.
Platform Support:
OS/2 2.x | OS/2 3.0 | OS/2 4.0 | OS/2 4.5x | eCS 1.x | eCs 2.x |
---|---|---|---|---|---|
Yes | Yes | Yes | Yes | Yes | Yes |
RUN=BATSERV.EXE
This is used by the Watcom C/C++ Compiler.
RUN=C:\Apps\Watcom_C\Binp\batserv.exe
Platform Support:
OS/2 2.x | OS/2 3.0 | OS/2 4.0 | OS/2 4.5x | eCS 1.x | eCs 2.x |
---|---|---|---|---|---|
Yes | Yes | Yes | Yes | Yes | Yes |
RUN=CACHE.EXE
This entry controls the behavior of the HPFS cache. It is normally not set in your config.sys. Set it only if you want to change the default settings. If you encounter any problems with this statement then delete it from your config.sys file and set it up in your startup.cmd file.
RUN=C:\OS2\Cache.exe Parameters
Default settings:
- LAZY: ON (use 1 thread)
- BUFFERIDLE: 500 ms
- MAXAGE: 5000 ms
- DISKIDLE: 1000 ms
- READAHEAD: ON
Parameters:
You can use the "/" or the "-" at the beginning of each parameter.
- /LAZY:value
Value can be ON or OFF or in the range from 0 to 64 . Default = ON If this parameter is not set it defaults to 3 . The OS/2 online help says: "If this parameter is set no other parameters are allowed." This depends on your system, some user reported me that two lines gives errors at boot.
o /LAZY:ON Lazy writing is on, three threads are used.
o /LAZY:OFF Lazy writing is turned Off.
o /LAZY:n n lazy write threads are used.
- /DISKIDLE:value
Value can be in the range from 0 to 65535 . Default= 1000 The value is expressed in milliseconds. This is the amount of time that the disk is idle before data can be written from cache to disk.
- /BUFFERIDLE:value
Value can be in the range from 0 to 65535 . Default= 500 The value is expressed in milliseconds. This is the amount of time that the cache-buffer can be idle before the cache data must be written to disk. The OS/2 Online help says that the BUFFERIDLE time must be smaller than the DISKIDLE time. I think this is wrong!
- /MAXAGE:value
Value can be in the range from 0 to 65535 . Default= 5000 The value is expressed in milliseconds. This is the time data waits in the cache before the data is written to disk.
- /READAHEAD:value
Value can be ON or OFF or 0 or 1 . This Parameter enables the read ahead buffer. Only from Warp 4.0
- /DIRTYMAX:value
Value can be in the range from 0 to 65535 . The value is expressed in milliseconds.
- /WRITECACHE:value
Value can be in the range from 0 to 65535 . The value is expressed in kilobytes.
See the examples below.
If you want to turn lazy writing off, add this line to your config.sys:
RUN=C:\OS2\CACHE.EXE /LAZY:OFF
If you want to turn lazy writing on and set bufferidle to 4 seconds, add this line to your config.sys:
RUN=C:\OS2\CACHE.EXE /BUFFERIDLE:4000
If you want to turn readahead off, add this line to your config.sys:
RUN=C:\OS2\CACHE.EXE /READAHEAD:OFF
TIP: Lazy writes can also be turned ON or OFF at an OS/2 command prompt.
WARNING: If you include the /LAZY parameter, then the CACHE statement will IGNORE ALL OTHER PARAMETERS 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.
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.
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. "Mr. HPFS" Doug Azzarito of IBM - Austin recommends them for testing only.
NOTE: Nearly everybody has his own recommendations about the correct size, so don't bother if you find different recommendations. 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
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.
NOTE: The full line of options must be on one line. If split into more than one line, the options split off will be ignored.
Platform Support:
OS/2 2.x | OS/2 3.0 | OS/2 4.0 | OS/2 4.5x | eCS 1.x | eCs 2.x |
---|---|---|---|---|---|
Yes | Yes | Yes | Yes | Yes | Yes |
RUN=CACHE386.EXE
Enables the cache for HPFS386. Only valid for the OS/2 Warp server advanced otherwise CACHE386.EXE is started by the following command:
CALL=C:\OS2\CMD.EXE /Q /C C:\IBM386FS\CACHE386.EXE >NUL
Call to the cache program for HPFS386
options for CACHE386 (x is an optional drive letter):
- /OPTIONS[:x]
Display current configuration
- /STATS[:C|:D]
Display, clear, or dynamically display statistics
- /LAZY[:x][:ON|:OFF]
Enable or disable lazy writing
- /MAXAGE[:x]:n
Change msDataAge to n milliseconds
- /BUFFERIDLE[:x]:n
Change msIdleBuf to n milliseconds
If no drive (x) is given, the option will apply to all HPFS drives.
Each option may be abbreviated to a single letter, for example:
CACHE386 /B:D:1000 (sets BufferIdle to 1000 for drive D)
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.
Platform Support:
OS/2 2.x | OS/2 3.0 | OS/2 4.0 | OS/2 4.5x | eCS 1.x | eCs 2.x |
---|---|---|---|---|---|
Yes | Yes | Yes | Yes | Yes | Yes |
RUN=CALIBRATE.EXE-C
See DEVICE TOUCH.SYS
Platform Support:
OS/2 2.x | OS/2 3.0 | OS/2 4.0 | OS/2 4.5x | eCS 1.x | eCs 2.x |
---|---|---|---|---|---|
Yes | Yes | Yes | Yes | Yes | Yes |
RUN=CBSSVR.EXE
Runtime part of the ZipStream/CryptStream compressed/secure file system products. For more information visit www.carbonbased.com.au
NOTE: Should normally be at the end of config.sys
RUN=CDWFSD.EXE
Starts the background process for the RSJ CD-Writer, responsible for writing of data on the CD.
Parameter:
- -q
Request confirmation
- -d
All accesses to the file system are protocolled at the serial interface COM2.
Platform Support:
OS/2 2.x | OS/2 3.0 | OS/2 4.0 | OS/2 4.5x | eCS 1.x | eCs 2.x |
---|---|---|---|---|---|
Yes | Yes | Yes | Yes | Yes | Yes |
RUN=CFOSD2.EXE
Starts the Cfos-Daemon.
RUN=C:\Cfos\Cfosd2.exe
Platform Support:
OS/2 2.x | OS/2 3.0 | OS/2 4.0 | OS/2 4.5x | eCS 1.x | eCs 2.x |
---|---|---|---|---|---|
Yes | Yes | Yes | Yes | Yes | Yes |
RUN=Cntrl.exe
It controls the stack for TCP/IP.
RUN=C:\Mptn\Bin\Cntrl.exe Parameter
Parameters:
- /V
This option enables the pointer and parameter verification by MPTS.
- /SM value
Number of small mbufs that MPTS allocate at initialation. Small mbufs are 256 bytes long. Value can be in the range from 512 to 4096 in multiplies of 128. Other values are rounded up to the nearest multiple of 128. Default = 512
- /LM value
Number of large mbufs that MPTS allocate at initialation. Large mbufs are 4096 bytes long. Value can be in the range from 64 to 180 in multiplies of 2. Default = 144
All data sectors received by MPTS are stored in buffers called mbuf, or clusters. There are two types of mbufs. Small mbufs and large mbufs. If needed MPTS can dynamically allocate additional mbufs.
Platform Support:
OS/2 2.x | OS/2 3.0 | OS/2 4.0 | OS/2 4.5x | eCS 1.x | eCs 2.x |
---|---|---|---|---|---|
Yes | Yes | Yes | Yes | Yes | Yes |
RUN=DDaemon.exe
This daemon process is required for the Netware requester.
RUN=C:\Netware\DDaemon.exe parameter
Platform Support:
OS/2 2.x | OS/2 3.0 | OS/2 4.0 | OS/2 4.5x | eCS 1.x | eCs 2.x |
---|---|---|---|---|---|
Yes | Yes | Yes | Yes | Yes | Yes |
RUN=Epw.exe
This is the generic alerter, where the operating system detects errors and can send messages to other machines.
RUN=C:\OS2\Epw.exe
Platform Support:
OS/2 2.x | OS/2 3.0 | OS/2 4.0 | OS/2 4.5x | eCS 1.x | eCs 2.x |
---|---|---|---|---|---|
Yes | Yes | Yes | Yes | Yes | Yes |
RUN=Ext2_lw.exe
This driver is needed by the ext2 file system driver.
RUN=C:\OS2\Fs\Ext2\Ext2_lw.exe
note: This program has no parameters.
Platform Support:
OS/2 2.x | OS/2 3.0 | OS/2 4.0 | OS/2 4.5x | eCS 1.x | eCs 2.x |
---|---|---|---|---|---|
Yes | Yes | Yes | Yes | Yes | Yes |
RUN=Hfs.exe
Helper application used by the Hfs.ifs installable file system.
RUN=C:\OS2\Fs\Hfs\Hfs.exe parameters
Parameters:
- /FN:mode
The Hfs file system allows some characters to be used which are in OS/2 are not allowed. This option controls how these characters should be handled. Mode can be CP850 , 8BIT or 7BIT . The default value is CP850.
- /NOSYNC
With this option you can decrease the performance, but you have to use the Sync utility before you remove a volume from the drive.
Platform Support:
OS/2 2.x | OS/2 3.0 | OS/2 4.0 | OS/2 4.5x | eCS 1.x | eCs 2.x |
---|---|---|---|---|---|
Yes | Yes | Yes | Yes | Yes | Yes |
RUN=Hyberset.exe
This is part of the support for the Dedicated DOS/Windows session feature.
RUN=C:\OS2\System\Hyberset.exe
Platform Support:
OS/2 2.x | OS/2 3.0 | OS/2 4.0 | OS/2 4.5x | eCS 1.x | eCs 2.x |
---|---|---|---|---|---|
Yes | Yes | Yes | Yes | Yes | Yes |
RUN=Lanmsgex.exe
This is part of the messaging system in MPTS.
RUN=C:\Ibmcom\Lanmsgex.exe
Platform Support:
OS/2 2.x | OS/2 3.0 | OS/2 4.0 | OS/2 4.5x | eCS 1.x | eCs 2.x |
---|---|---|---|---|---|
Yes | Yes | Yes | Yes | Yes | Yes |
=RUN=Logdaem.exe This executable is the daemon process for the system error logging. note: You must have also installed the log.sys driver
RUN=C:\OS2\LOGDAEM.EXE [parameter]
Parameters:
- /E:filename
This is the file in which the log messages are stored and must be a fully qualified filename.
- /W:value
Sets up the size of the error log file. Value can be in the range from 4 Kbytes to 64 Kbytes . Default = 64 Kbytes
note: You can also change the parameters with the Syslog program.
See the example below.
To use C:\OS2\LOG\ERROR.LOG as the error log file with a size of 48 Kbytes, add this line to your config.sys file:
RUN=C:\OS2\LOGDAEM.EXE /E:C:\OS2\LOG\ERROR.LOG /W:48
Platform Support:
OS/2 2.x | OS/2 3.0 | OS/2 4.0 | OS/2 4.5x | eCS 1.x | eCs 2.x |
---|---|---|---|---|---|
Yes | Yes | Yes | Yes | Yes | Yes |
RUN=LsDaemon.exe
This is part of the OS/2 File and Print Client.
RUN=C:\Ibmlan\Netprog\Lsdaemon.exe
Platform Support:
OS/2 2.x | OS/2 3.0 | OS/2 4.0 | OS/2 4.5x | eCS 1.x | eCs 2.x |
---|---|---|---|---|---|
Yes | Yes | Yes | Yes | Yes | Yes |
RUN=NbDaemon.exe
This statement loads the Netware NetBIOS daemon.
RUN=C:\Netware\NbDaemon.exe
Platform Support:
OS/2 2.x | OS/2 3.0 | OS/2 4.0 | OS/2 4.5x | eCS 1.x | eCs 2.x |
---|---|---|---|---|---|
Yes | Yes | Yes | Yes | Yes | Yes |
RUN=NetBind.exe
This process binds the protocols to the adapter driver that the NDIS Protocol Manager ( Protman.os2 ) tells it to.
RUN=C:\Ibmcom\Protocol\Netbind.exe
Platform Support:
OS/2 2.x | OS/2 3.0 | OS/2 4.0 | OS/2 4.5x | eCS 1.x | eCs 2.x |
---|---|---|---|---|---|
Yes | Yes | Yes | Yes | Yes | Yes |
RUN=NmpBind.exe
This is used by the Watcom C/C++ compiler.
RUN=C:\Apps\Watcom_C\Binp\Nmpbind.exe
Platform Support:
OS/2 2.x | OS/2 3.0 | OS/2 4.0 | OS/2 4.5x | eCS 1.x | eCs 2.x |
---|---|---|---|---|---|
Yes | Yes | Yes | Yes | Yes | Yes |
RUN=NpDaemon.exe
This statement provides NamedPipes NetBIOS support for Netware.
RUN=C:\Netware\Npdaemon.exe
Platform Support:
OS/2 2.x | OS/2 3.0 | OS/2 4.0 | OS/2 4.5x | eCS 1.x | eCs 2.x |
---|---|---|---|---|---|
Yes | Yes | Yes | Yes | Yes | Yes |
RUN=NwDaemon.exe
This statement provides IPX packet exchange.
RUN=C:\Netware\Nwdaemon.exe
Platform Support:
OS/2 2.x | OS/2 3.0 | OS/2 4.0 | OS/2 4.5x | eCS 1.x | eCs 2.x |
---|---|---|---|---|---|
Yes | Yes | Yes | Yes | Yes | Yes |
RUN=Smstart.exe
This statement loads and controls following system management daemons:
- Ffst.exe
- Erlogger.exe
- Dmisl.exe
- remoterr.exe
If one of the daemons dies, the Smstart starts over.
RUN=C:\OS2\Smstart.exe
Platform Support:
OS/2 2.x | OS/2 3.0 | OS/2 4.0 | OS/2 4.5x | eCS 1.x | eCs 2.x |
---|---|---|---|---|---|
Yes | Yes | Yes | Yes | Yes | Yes |
RUN=SpDaemon.exe
This statement starts the Netware daemon to handle the SPX packets.
RUN=C:\Netware\Spdaemon.exe
Platform Support:
OS/2 2.x | OS/2 3.0 | OS/2 4.0 | OS/2 4.5x | eCS 1.x | eCs 2.x |
---|---|---|---|---|---|
Yes | Yes | Yes | Yes | Yes | Yes |
RUN=Vdosctl.exe
This statement is used in TCP/IP and provides support for DOS and Windows TCP/IP applications.
RUN=C:\Tcpip\Bin\Vdosctl.exe
Platform Support:
OS/2 2.x | OS/2 3.0 | OS/2 4.0 | OS/2 4.5x | eCS 1.x | eCs 2.x |
---|---|---|---|---|---|
Yes | Yes | Yes | Yes | Yes | Yes |
RUN=Vfat-lw.exe
This driver is needed by the Vfat file system driver.
RUN=C:\OS2\Fs\Vfat\Vfat-lw.exe
Platform Support:
OS/2 2.x | OS/2 3.0 | OS/2 4.0 | OS/2 4.5x | eCS 1.x | eCs 2.x |
---|---|---|---|---|---|
Yes | Yes | Yes | Yes | Yes | Yes |
RUN=Vnrminit.exe
This statement is used by the File and Print Client.
RUN=C:\Ibmlan\Netprog\Vnrminit.exe
Platform Support:
OS/2 2.x | OS/2 3.0 | OS/2 4.0 | OS/2 4.5x | eCS 1.x | eCs 2.x |
---|---|---|---|---|---|
Yes | Yes | Yes | Yes | Yes | Yes |