Jump to content

CONFIG.SYS RUN Statements: Difference between revisions

From EDM2
← Older editNewer edit →
Ak120 (talk | contribs)
35,819 edits
Ak120 (talk | contribs)
35,819 edits
No edit summary
Line 4: Line 4:


*[[ACPIDAEMON.EXE]] - ACPI support
*[[ACPIDAEMON.EXE]] - ACPI support
 
*[[ACTVCOLL.EXE]] - Process Commander
==ACTVCOLL.EXE==
*[[AEFSDMN.EXE]] - The AEFS daemon
Executable from Process Commander.
*[[AFNBINI.EXE]]
The ACTVCOLL line gathers resource use information about sessions.
*[[APMDAEMN.EXE]] - APM 1.2
 
*[[ASP4INIT.EXE]]
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.
*[[ATKINIT.EXE]]
 
*[[BATSERV.EXE]] - Watcom
{|class="wikitable"
*[[CACHE.EXE]] - HPFS cache
|+Platform Support:
*[[CACHE386.EXE]] - HPFS 386 cache
!OS/2 2.x
!OS/2 3.0
!OS/2 4.0
!OS/2 4.5x
|-
|Yes
|Yes
|Yes
|Yes
|}
 
==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 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.
 
{| class="wikitable"
|+Platform Support:
!OS/2 2.x
!OS/2 3.0
!OS/2 4.0
!OS/2 4.5x
|-
|Yes
|Yes
|Yes
|Yes
|}
 
==AFNBINI.EXE==
This daemon monitors/setups Netbios.
 
{|class="wikitable"
|+Platform Support:
!OS/2 2.x
!OS/2 3.0
!OS/2 4.0
!OS/2 4.5x
|-
|*
|C
|Yes
|Yes
|}
 
==APMDAEMN.EXE==
New in Fixpaks, fixes some errors when using APM 1.2.
RUN=C:\OS2\APMDAEMN.EXE
 
'''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).
 
{|class="wikitable"
|+Platform Support:
!OS/2 2.x
!OS/2 3.0
!OS/2 4.0
!OS/2 4.5x
|-
|?
|?
|Yes
|Yes
|}
 
==ASP4INIT.EXE==
Vortex AU8820 OS/2 initialization.
{| class="wikitable"
|+Platform Support:
!OS/2 2.x
!OS/2 3.0
!OS/2 4.0
!OS/2 4.5x
|-
|
|Yes
|Yes
|Yes
|}
 
==ATKINIT.EXE==
From LAN Server for Macintosh.
 
{| class="wikitable"
|+Platform Support:
!OS/2 2.x
!OS/2 3.0
!OS/2 4.0
!OS/2 4.5x
|-
|*
|C
|Yes
|Yes
|}
 
==BATSERV.EXE==
This is used by the [[Watcom C/C++]] Compiler.
RUN=\Watcom_C\BINP\batserv.exe
 
{|class="wikitable"
|+Platform Support:
!OS/2 2.x
!OS/2 3.0
!OS/2 4.0
!OS/2 4.5x
|-
|Yes
|Yes
|Yes
|Yes
|}
 
==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=\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:'''
{| class="wikitable"
|-
!OS/2 2.x
!OS/2 3.0
!OS/2 4.0
!OS/2 4.5x
|-
|Yes
|Yes
|Yes
|Yes
|}
 
==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:'''
{| class="wikitable"
|-
!OS/2 2.x
!OS/2 3.0
!OS/2 4.0
!OS/2 4.5x
|-
|Yes
|Yes
|Yes
|Yes
|}


==CALIBRATE.EXE-C==
==CALIBRATE.EXE-C==
Line 308: Line 30:
|}
|}


==CBSSVR.EXE==
*[[CBSSVR.EXE]]
Runtime part of the ZipStream/CryptStream compressed/secure file system products.
*[[CDWFSD.EXE]]
 
'''NOTE:''' Should normally be at the end of config.sys
 
==CDWFSD.EXE==
Starts the background process for the RSJ CD-Writer, responsible for writing of data on the CD.
RUN=C:\PROGRAMS\RSJCD\CDWFSD.EXE -p "C:/var/temp" -c20000 -b2048 -t2 -i3 -s0
 
'''Parameter:'''
* -q - Request confirmation
* -d - All accesses to the file system are protocolled at the serial interface COM2.
 
{| class="wikitable"
|+Platform Support:
!OS/2 2.x
!OS/2 3.0
!OS/2 4.0
!OS/2 4.5x
|-
|*
|Yes
|Yes
|Yes
|}


==CFOSD2.EXE==
==CFOSD2.EXE==
Line 367: Line 66:
|}
|}


==CNTRL.EXE==
*[[CNTRL.EXE]]
It controls the stack for TCP/IP. 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:
*[[CWCUTIL.EXE]]
*IP input processing
*[[CWDAEMON.EXE]]
*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=\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:'''
{| class="wikitable"
|-
!OS/2 2.x
!OS/2 3.0
!OS/2 4.0
!OS/2 4.5x
|-
|
|C
|Yes
|Yes
|}
 
==CWCUTIL.EXE==
Crystal DSP manager utility application.
RUN=\MMOS2\CWCUTIL.EXE
 
'''Platform Support:'''
{| class="wikitable"
|-
!OS/2 2.x
!OS/2 3.0
!OS/2 4.0
!OS/2 4.5x
|-
|Yes
|Yes
|Yes
|Yes
|}
 
==CWDAEMON.EXE==
Crystal OS/2 application for WinOS2 audio.
RUN=\MMOS2\CWDAEMON.EXE
 
{| class="wikitable"
|+Platform Support:
!OS/2 2.x
!OS/2 3.0
!OS/2 4.0
!OS/2 4.5x
|-
|Yes
|Yes
|Yes
|Yes
|}


==DB2UPM.EXE==
==DB2UPM.EXE==
Line 477: Line 103:
|}
|}


==DMISL.EXE==
*[[DMISL.EXE]]
This is the service layer used by SNMP to map local errors to SNMP alerts. Used by Network Manager and Netfinity, among others, to manage client errors by an administrator.
 
'''NOTE:''' It is not needed, if you doen't have a LAN or you are not using these management tools.
 
{| class="wikitable"
|+Platform Support:
!OS/2 2.x
!OS/2 3.0
!OS/2 4.0
!OS/2 4.5x
|-
|
|Yes
|Yes
|Yes
|}


==DTAD.EXE==
==DTAD.EXE==
Line 511: Line 121:
|}
|}


==EPW.EXE==
*[[EPW.EXE]]
This is the generic alerter, where the operating system detects errors and can send messages to other machines.
*[[EPWROUT.EXE]]
RUN=\OS2\EPW.EXE
 
{| class="wikitable"
|+Platform Support:
!OS/2 2.x
!OS/2 3.0
!OS/2 4.0
!OS/2 4.5x
|-
|*
|Yes
|Yes
|Yes
|}
 
==EPWROUT.EXE==
Part of First Failure Support in Warp Server for e-business.
RUN=C:\OS2\EPWROUT.EXE 1
 
{| class="wikitable"
|+Platform Support:
!OS/2 2.x
!OS/2 3.0
!OS/2 4.0
!OS/2 4.5x
|-
|No
|No
|No
|Yes
|}


==EVFSCTL.EXE==
==EVFSCTL.EXE==
Line 580: Line 159:
|}
|}


==EXTENDFS.EXE==
*[[EXTENDFS.EXE]]
Part of [[JFS.IFS]] in Warp Server for e-business. Automatically extends all file systems so they use the entire partition on which they reside. This is only the case when you extend the size of a volume using LVM and do not run extendfs afterwards. This entry ensures that at the next reboot at least, the file systems are extended according to the corresponding volume sizes.
*[[GENAUDD.EXE]]
RUN=\OS2\EXTENDFS.EXE *
*[[GSVDAEMN.EXE]] - Intel SpeedStep
 
*[[HELPERW.EXE]] - GenMAC helper
{| class="wikitable"
*[[HFS.EXE]] - Mac HFS
|+Platform Support:
*[[HYBERSET.EXE]]
!OS/2 2.x
*[[IBMCSFLK.EXE]] - Corrective service file lock
!OS/2 3.0
*[[IBMLANLK.EXE]]
!OS/2 4.0
!OS/2 4.5x
|-
|No
|No
|No
|Yes
|}
 
==GENAUDD.EXE==
Generic WinOS/2 Audio Driver Daemon component.
 
{| class="wikitable"
|+Platform Support:
!OS/2 2.x
!OS/2 3.0
!OS/2 4.0
!OS/2 4.5x
|-
|No
|No
|No
|Yes
|}
 
==GSVDAEMN.EXE==
SpeedStep Daemon executable that performs CPU state changes. This is part of the software support package for Intel's SpeedStep dynamic frequency scaling technology (codenamed Geyserville). By changing CPU state, lower heat and power consumption may be attained, while dynamically adjusting to changing processing needs (throttling).
RUN=\OS2\GSVDAEMN.EXE
 
'''NOTE:''' As GSVDAEMN relies on communication with [[APM.SYS]], it is not recommended to use this driver with ACPIDAEMON, which provides its own CPU throttling.
 
{| class="wikitable"
|+Platform Support:
!OS/2 2.x
!OS/2 3.0
!OS/2 4.0
!OS/2 4.5x
|-
|No
|Yes
|Yes
|Yes
|}
 
==HELPERW.EXE==
Network driver helper application for GENMAC (Generic MAC Wrapper Driver) by ''Willibald Meyer''
It's job is reading and loading the Win32 drivers into memory.
RUN=\GENMAC\DRIVER\HELPERW.EXE
 
User List: http://dir.gmane.org/gmane.org.netlabs.genmac.user
 
{| class="wikitable"
|+Platform Support:
!OS/2 2.x
!OS/2 3.0
!OS/2 4.0
!OS/2 4.5x
|-
|No
|No
|No
|Yes
|}
 
==HFS.EXE==
Helper application used by the [[The Config.sys Documentation Project/IFS Statements#IFS.3DHFS.IFS|Hfs.ifs]] installable file system.
RUN=\OS2\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.
 
{| class="wikitable"
|+Platform Support:
!OS/2 2.x
!OS/2 3.0
!OS/2 4.0
!OS/2 4.5x
|-
|Yes
|Yes
|Yes
|Yes
|}
 
==HYBERSET.EXE==
This is part of the support for the dedicated DOS/Windows session feature.
RUN=C:\OS2\System\Hyberset.exe
 
{| class="wikitable"
|+Platform Support:
!OS/2 2.x
!OS/2 3.0
!OS/2 4.0
!OS/2 4.5x
|-
|
|Yes
|Yes
|Yes
|}
 
==IBMCSFLK.EXE==
Exchanges locked files during boot. Normally this is only installed during reboot. If you see this entry the replacement of locked files may have failed. Please check \os2\install\ibmcsflk.lst
 
{| class="wikitable"
|+Platform Support:
!OS/2 2.x
!OS/2 3.0
!OS/2 4.0
!OS/2 4.5x
|-
|Yes
|Yes
|Yes
|Yes
|}
 
==IBMLANLK.EXE==
Exchanges locked files during boot. Normally this is only installed during reboot. If you see this entry the replacement of locked files may have failed. Please check \os2\install\ibmlanlk.lst
 
{| class="wikitable"
|+Platform Support:
!OS/2 2.x
!OS/2 3.0
!OS/2 4.0
!OS/2 4.5x
|-
|Yes
|Yes
|Yes
|Yes
|}


==IOMGSYNC.EXE==
==IOMGSYNC.EXE==
Line 776: Line 217:


==ISOFSDMN.EXE==
==ISOFSDMN.EXE==
The isofsdmn program is the file system daemon for the ISOFS installable file system (see IFS STUBFSD.IFS)
It is typically started in CONFIG.SYS by a RUN statement (NOT a CALL statement) or from a script using the detach command.
'''Values:'''
--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
{| class="wikitable"
|+Platform Support:
!OS/2 2.x
!OS/2 3.0
!OS/2 4.0
!OS/2 4.5x
|-
|
|Yes
|Yes
|Yes
|}


==KBFAST.EXE==
==KBFAST.EXE==
Line 853: Line 267:
|}
|}


==LOGDAEM.EXE==
*[[LOGDAEM.EXE]] - system error logging
This executable is the daemon process for the system error logging.
note: You must have also installed the log.sys driver
RUN=\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.
'''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: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
 
'''NOTE:''' Use SYSLOG.EXE from an OS/2 command line prompt to view your log file.
 
{|class="wikitable"
|+Platform Support:
!OS/2 2.x
!OS/2 3.0
!OS/2 4.0
!OS/2 4.5x
|-
|Yes
|Yes
|Yes
|Yes
|}


==LSDAEMON.EXE==
==LSDAEMON.EXE==
Line 1,041: Line 419:
|}
|}


==NBTCP.EXE==
*[[NBTCP.EXE]]
Three programs, NBTCP.EXE, RFCADDR.EXE and TCPBEUI.OS2, make up the primary runtime components of this NetBIOS over TCP/IP implementation.
 
NBTCP.EXE is a ring3 module that creates threads for socket processing. This module also processes the two routing extension data files: RFCBCST.LST and RFCNAMES.LST. When NBTCP is invoked it runs RFCADDR.EXE to process these two files. If you modify these files and wish to have the changes take effect without restarting the system, you can run RFCADDR.EXE from the OS/2 command line. RFCADDR.EXE then informs TCPBEUI.OS2 of the changes. This happens, of course, only if you have created one of the other of these two data files and have them specified in the PROTOCOL.INI configuration file. 
RUN=\IBMCOM\PROTOCOL\NBTCP.EXE
 
{| class="wikitable"
|+Platform Support:
!OS/2 2.x
!OS/2 3.0
!OS/2 4.0
!OS/2 4.5x
|-
|*
|C
|Yes
|Yes
|}


==ND.EXE==
==ND.EXE==
Line 1,110: Line 471:
|}
|}


==NETBIND.EXE==
*[[NETBIND.EXE]]
This process binds the protocols to the adapter driver that the NDIS Protocol Manager (Protman.os2) tells it to.
RUN=\IBMCOM\PROTOCOL\NETBIND.EXE  
 
{| class="wikitable"
|+Platform Support:
!OS/2 2.x
!OS/2 3.0
!OS/2 4.0
!OS/2 4.5x
|-
|*
|C
|Yes
|Yes
|}


==NMPBIND.EXE==
==NMPBIND.EXE==
Line 1,249: Line 595:
|}
|}


==RSRV.EXE==
*[[RSRV.EXE]] - registry server
Registry server from older versions of IBM Open32 for Warp3. Should be deleted after applying Fixpak 26 or higher for Warp3.
*[[SMSTART.EXE]]
 
{| class="wikitable"
|+Platform Support:
!OS/2 2.x
!OS/2 3.0
!OS/2 4.0
!OS/2 4.5x
|-
|
|Yes
|
|
|}
 
==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
 
'''TIP:''' A REM in front of RUN=drive:\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.
 
{| class="wikitable"
|+Platform Support:
!OS/2 2.x
!OS/2 3.0
!OS/2 4.0
!OS/2 4.5x
|-
|
|Yes
|Yes
|Yes
|}


==SPDAEMON.EXE==
==SPDAEMON.EXE==
Line 1,440: Line 748:
|}
|}


==VDOSCTL.EXE==
*[[VDOSCTL.EXE]]
This statement is used in TCP/IP and provides support for DOS and Windows TCP/IP applications.
RUN=\TCPIP\BIN\VDOSCTL.EXE
 
'''TIP:''' If you don't need TCP/IP support in DOS sessions REM this line.
 
{|class="wikitable"
|+Platform Support:
!OS/2 2.x
!OS/2 3.0
!OS/2 4.0
!OS/2 4.5x
|-
|*
|C
|Yes
|Yes
|}


==VFAT-LW.EXE==
==VFAT-LW.EXE==
Line 1,476: Line 767:
|}
|}


==VFBWC.EXE==
*[[VFBWC.EXE]]
Applies Write-Combining to Video Frame Buffer Aperture during startup.
 
FBWC.exe - Video Frame Buffer to Write-Combining for P6K7MTRR.sys Copyright 1999-2001 Takayuki 'January June' Suwa.
 
'''Options:'''
 
-1 rounds Pages up to 1MB granule
-a applies settings to MTTRs actually
-b rings beep when setting is applied
-d goes into daemon mode, waits until APM suspend resuming and re-apply
-i turns to invalid settings to video frame buffer aperture /uncacheable to VGA region
-v also applies write-combining to VGA region
-? displays this message
 
{| class="wikitable"
|+Platform Support:
!OS/2 2.x
!OS/2 3.0
!OS/2 4.0
!OS/2 4.5x
|-
|
|Yes
|Yes
|Yes
|}


==VLANINIT.EXE==
==VLANINIT.EXE==
Line 1,537: Line 802:
|}
|}


==VPCKBMON.EXE==
*[[VPCKBMON.EXE]]
Virtual PC Keyboard Monitor. Virtual PC comes with a keyboard monitor driver (vpckbmon.exe) that can be installed to CONFIG.SYS to allow Virtual PC to intercept certain OS/2 system key combinations (Ctrl-Esc, Alt-Esc, Alt-Tab, C-A-D). It can be selected during installation. The keyboard monitor will be active when a virtual machine receives input focus and can be configured through the Virtual PC preferences.
*[[WATCHCAT.EXE]]
 
Note that the Virtual PC keyboard monitor might not be compatible with certain other keyboard monitors. Most often, you find keyboard monitors in remote control applications like PolyPM/RSM, NetOp, Tivoli, etc. In case you experience system hangs starting Virtual machines or using your remote control application, it is recommended to remove either the remote control application or the Virtual PC keyboard monitor. This can be achieved through the Virtual PC Setup application.
 
{| class="wikitable"
|+Platform Support:
!OS/2 2.x
!OS/2 3.0
!OS/2 4.0
!OS/2 4.5x
|-
|
|
|Yes
|Yes
|}
 
==WATCHCAT.EXE==
WatchCat 2.1 main program. WatchCat is a program to recover OS/2 from a hanged Presentation Manager by killing applications. It can also display all PStat-info about modules, processes, threads etc.
 
Developed by Felix von Normann and Thomas Opheys. Watchcat is FREE for private use.
 
'''NOTE:''' As Watchcat hasn't been updated since 1995 I first suggest the use of SCKILLFEATUREENABLED=YES together with Warp4. There is also the FREE Task Buster ver 2.0 by Jostein Ullestad available at http://www.powerutilities.no. Both can unfortunately only act with a working P(resentation)M(anager), but as long you're not a developer who has to 'fight' with corrupt applications who are blocking the message queue these two should do in nearly every case, cause since Fixpak 17 for Warp 3 the "SIQ" feature allows the user to take focus away from an application that is monopolising the message queue.
 
'''TIP''' by Rainer Feuerstein: Around Christmas the WatchCat Icon wears a Santa Cap :).
 
'''NOTE''' by Timur Kazimirov: In FP13 for Warp 4 there is a new program PSFILES that shows all opened files (with a lot of the info including mode, PID of process, handle, size, attributes, and etc).
 
{| class="wikitable"
|+Platform Support:
!OS/2 2.x
!OS/2 3.0
!OS/2 4.0
!OS/2 4.5x
|-
|Yes
|Yes
|Yes
|Yes
|}
 
==WCCAD.EXE==
==WCCAD.EXE==
WatchCat 2.1 CAD Package Control Program.
WatchCat 2.1 CAD Package Control Program.

Revision as of 23:13, 14 March 2017

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:

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

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

CLKBASIC.EXE

eCS Clock Daemon. eCS Clock is developed by Mark Eckstein and intended to run only on eComStation.

Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
No No No eCS

DB2UPM.EXE

Runs the U(ser) P(rofile) M(anager) from DB2.

Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
No Yes Yes Yes

DDAEMON.EXE

This daemon process is required for the Netware requester. 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. 

RUN=\Netware\DDaemon.exe <parameter>
Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

DTAD.EXE

Streaming Data Transport Agent (DTA) daemon for eComStation.

Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
No No No eCS

EVFSCTL.EXE

RUN=\ECS\BIN\EVFSCTL.EXE
Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
No No No eCS

EXT2_LW.EXE

This driver is needed by the ext2 file system driver. 

RUN=\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
Yes Yes Yes Yes

IOMGSYNC.EXE

Necessary for the Iomega Tools protect, lock, iomgfmt, remount, unitinfo, addman and readme

Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
? Yes Yes Yes

IP2XDMN.EXE

Dualstor Backup Daemon.

Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

IRDNDS.EXE

Needed to run IBM Infrared NDIS MAC Driver

Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

ISOFSDMN.EXE

KBFAST.EXE

Runs keyboard enhancer to speed up keyboard.

Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

LANDLL.EXE

This starts the TCPIP/peer Stack.

Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
C Yes Yes

LANMSGEX.EXE

This is part of the messaging system in MPTS. 

RUN=\IBMCOM\LANMSGEX.EXE
Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
C Yes Yes

LSDAEMON.EXE

This is part of the OS/2 File and Print Client. 

RUN=\IBMLAN\NETPROG\Lsdaemon.exe
Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
C Yes Yes

LT_MON.EXE

Lucent Technologies Modem Monitor An older version is available at http://www.drmartinus.de/notebook2/notebook.htm

Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes

LVMALERT.EXE

Part of the L(ogical) V(olume) M(anager) in Warp Server for e-business

Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
No No No Yes

MIDIDMON.EXE

This is for MIDI. 

RUN=C:\MMOS2\mididmon.exe
Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
2.1 Yes Yes Yes

MMFIX.EXE

This help to solve the repeating system sounds problem with SND.DLL. (Reference eComStation bug 2874). By David Azarewicz. 

RUN=C:\MMOS2\MMFIX.EXE
Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
No No No eCS

MMHELPDD.EXE

This is for MIDI. 

RUN=C:\MMOS2\MMHELPDD.EXE
Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes

MSENSIT.EXE

From the FM-Utils, accelerates the mouse.

Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

MWSTART.EXE

Daemon for the MWAVE Modem for IBM Thinkpads

Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
* Yes Yes Yes

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
C Yes Yes

ND.EXE

To mount NDFS at startup add this complete line 

RUN=\ndfs\nd.exe automnt drive:\fullpath\to\resconfig.ndc
Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes

NDCTL.EXE

Starts Netdrive Control Program. Netdrive is a new utility for OS/2 users which allows to mount an ftp site or a local directory or a network resource to a virtual volume.

Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes

NET.EXE

Starts the requester immediately and not with startup.cmd, the startup folder or with logon. 

RUN=\IBMLAN\NETPROG\NET.EXE START REQ
Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
* C Yes Yes

NMPBIND.EXE

Named Pipe used by the Watcom C/C++ compiler. 

RUN=\Watcom_C\Binp\Nmpbind.exe
Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

NPDAEMON.EXE

This statement provides NamedPipes NetBIOS support for Netware. 

RUN=\Netware\Npdaemon.exe
Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
* C Yes Yes

NVCSRV2.EXE

Part of Norman Antivirus.

Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes

NWDAEMON.EXE

This statement provides IPX packet exchange. 

RUN=\NETWARE\NWDAEMON.EXE
Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
* C Yes Yes

PC.EXE

Executable from Process Commander

Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

RAMDISK.EXE

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

Variable:

driveletter: - creates a Ramdisk called driveletter:

Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes

REXINIT.EXE

Makes sure that rexx is loaded and ready to process the MultiDesk2 rexx scripts. MultiDesk2 (available at http://guadagnino.tripod.com) adds Multi User capability - separate Desktop and Sound Scheme for each User.

Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

SPDAEMON.EXE

This statement starts the Netware daemon to handle the SPX packets. 

RUN=\NETWARE\SPDAEMON.EXE
Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
* C Yes Yes

SSESCTL.EXE

RUN=C:\ECS\SYSTEM\SESS\bin\ssesctl.exe --source <path 1>?<path 2> --

ex: RUN=C:\ECS\SYSTEM\SESS\bin\ssesctl.exe --source C:\ECS\SYSTEM\SESS\etc\passwd?C:\ECS\SYSTEM\SESS\etc\acls --

Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
No ? Yes Yes

START_S0.EXE

For Teles ISDN Cards.

Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

STHDAEM.EXE

Daemon for StHWMon, a temperature/fan/voltage monitor for W83781D/W83782D/VIA 82C686 chips.

Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes

TVCTL.EXE

Starts the TVFS control program.

Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

ULTRADMN.EXE

Run statement for Gravis Ultra Soundcard (discontinued)

Must be used to get MIDI sounds to work with Gravis Ultra Soundcards drive:\ULTRAPNP or drive:\ULTRASND is location for MIDI patches.

Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
2.1 Yes Yes Yes

UNICHECK.EXE

Unimaint background daemon.

Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

UPDSIG.EXE

The tool UpdSig adds or updates adjustable intervals in at most 10 different signature files for mailers and/or newsreaders.

Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

USBMON.EXE

USB daemon to detect add and removals of devices.

Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
No Yes Yes Yes

VFAT-LW.EXE

This driver is needed by the Vfat file system driver. 

RUN=\OS2\VFAT-LW.EXE
Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

VLANINIT.EXE

Part of OS/2 Virtual LAN Kernel.

Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
* C Yes Yes

VNRMINIT.EXE

This statement is used by the File and Print Client. 

RUN=\IBMLAN\NETPROG\VNRMINIT.EXE
Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
* C Yes Yes

WCCAD.EXE

WatchCat 2.1 CAD Package Control Program.

Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

WIPEBOOT.EXE

BocaSoft WipeOut/2 screen saver program.

Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes Yes Yes

ZANDA.EXE

Loads Norman Ver. 5.2 Antivirus engine ZANDA.EXE, part of suite.

Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes

ZLITE.EXE

Part of Norman Antivirus.

Platform Support:
OS/2 2.x OS/2 3.0 OS/2 4.0 OS/2 4.5x
Yes Yes
Retrieved from "https://www.edm2.com/index.php?title=CONFIG.SYS_RUN_Statements&oldid=45619"