Jump to content

CONFIG.SYS RUN Statements: Difference between revisions

From EDM2
No edit summary
 
No edit summary
Line 1: Line 1:
[[The Config.sys Documentation Project|Return to The Config.sys Documentation Project Main Page]]
[[The Config.sys Documentation Project|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=Batserv.exe=
This is used by the Watcom C/C++ Compiler.
  RUN=C:\Apps\Watcom_C\Binp\batserv.exe
<b>Platform Support:</b>
{| class="wikitable" style="text-align:center" border="1"
|-
!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.
* /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
<b>Platform Support:</b>
{| class="wikitable" style="text-align:center" border="1"
|-
!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
<b>Platform Support:</b>
{| class="wikitable" style="text-align:center" border="1"
|-
!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.
<b>Platform Support:</b>
{| class="wikitable" style="text-align:center" border="1"
|-
!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
<b>Platform Support:</b>
{| class="wikitable" style="text-align:center" border="1"
|-
!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
<b>Platform Support:</b>
{| class="wikitable" style="text-align:center" border="1"
|-
!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.
<b>Platform Support:</b>
{| class="wikitable" style="text-align:center" border="1"
|-
!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 [[The Config.sys Documentation Project/IFS Statements#IFS.3DHFS.IFS|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.
<b>Platform Support:</b>
{| class="wikitable" style="text-align:center" border="1"
|-
!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
<b>Platform Support:</b>
{| class="wikitable" style="text-align:center" border="1"
|-
!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
<b>Platform Support:</b>
{| class="wikitable" style="text-align:center" border="1"
|-
!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
<b>Platform Support:</b>
{| class="wikitable" style="text-align:center" border="1"
|-
!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
<b>Platform Support:</b>
{| class="wikitable" style="text-align:center" border="1"
|-
!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
<b>Platform Support:</b>
{| class="wikitable" style="text-align:center" border="1"
|-
!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
<b>Platform Support:</b>
{| class="wikitable" style="text-align:center" border="1"
|-
!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
<b>Platform Support:</b>
{| class="wikitable" style="text-align:center" border="1"
|-
!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
<b>Platform Support:</b>
{| class="wikitable" style="text-align:center" border="1"
|-
!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
<b>Platform Support:</b>
{| class="wikitable" style="text-align:center" border="1"
|-
!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
<b>Platform Support:</b>
{| class="wikitable" style="text-align:center" border="1"
|-
!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
<b>Platform Support:</b>
{| class="wikitable" style="text-align:center" border="1"
|-
!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
<b>Platform Support:</b>
{| class="wikitable" style="text-align:center" border="1"
|-
!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
<b>Platform Support:</b>
{| class="wikitable" style="text-align:center" border="1"
|-
!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
<b>Platform Support:</b>
{| class="wikitable" style="text-align:center" border="1"
|-
!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
|}

Revision as of 15:47, 21 January 2007

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

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

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