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.
RUN AFNBINI.EXE
[Table of contents] [Index] [RUN, START AND CALL]
This daemon monitors/setups Netbios
RUN APMDAEMN.EXE
[Table of contents] [Index] [RUN, START AND CALL]
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).
RUN ASP4INIT.EXE
[Table of contents] [Index] [RUN, START AND CALL]
Vortex AU8820 OS/2 initialization
RUN BATSERV.EVE
[Table of contents] [Index] [RUN, START AND CALL]
Executable from WATCOM C/C++ Version 11.0
Information by Wm D Loughman (wdlkhl@attglobal.net)
RUN CACHE.EXE
[Table of contents] [Index] [RUN, START AND CALL]
=drive:\OS2\CACHE.EXE /Parameter
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.)
Parameters:
/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 parameter 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 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.
/MAXAGE:n (in milliseconds) 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. The default is 5000 or about 5 seconds.
/DISKIDLE:n (in milliseconds) Sets how long your hard disk must be idle before it will accept data from the cache. Default is 1000 or about one second. The minimum value must be greater than the value specified in the BUFFERIDLE parameter.
/BUFFERIDLE:n (in milliseconds) Sets how long the cache buffer must be idle before its contents MUST be written to your hard disk. Default is 500 or about 1/2 second.
/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. "Mr. HPFS" Doug Azzarito of IBM - Austin recommends them for testing only.
/DIRTYMAX: 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: 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).
<<=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.src
<<=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.
RUN CACHE386.EXE
[Table of contents] [Index] [RUN, START AND CALL]
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.
RUN CALIBRATE.EXE-C
[Table of contents] [Index] [RUN, START AND CALL]
See DEVICE TOUCH.SYS
RUN CBSSVR.EXE
[Table of contents] [Index] [RUN, START AND CALL]
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
[Table of contents] [Index] [RUN, START AND CALL]
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.
RUN CFOSD2.EXE
[Table of contents] [Index] [RUN, START AND CALL]
CFOS Deamon
RUN CNTRL.EXE
[Table of contents] [Index] [RUN, START AND CALL]
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 CWCUTIL.EXE
[Table of contents] [Index] [RUN, START AND CALL]
=drive:\MMOS2\CWCUTIL.EXE
Crystal DSP manager utility application
RUN CWDAEMON.EXE
[Table of contents] [Index] [RUN, START AND CALL]
=drive:\MMOS2\CWDAEMON.EXE
Crystal OS/2 application for WinOS2 audio
RUN DB2UPM.EXE
[Table of contents] [Index] [RUN, START AND CALL]
Runs the U(ser) P(assword) M(anager) from DB2
RUN DDAEMON.EXE
[Table of contents] [Index] [RUN, START AND CALL]
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 EPW.EXE
[Table of contents] [Index] [RUN, START AND CALL]
Enables First Failure Support in Warp Server for E-Business
RUN EPWROUT.EXE
[Table of contents] [Index] [RUN, START AND CALL]
Part of First Failure Support in Warp Server for E-Business
RUN EXT2_LW.EXE
[Table of contents] [Index] [RUN, START AND CALL]
Part of the ext2-os2.ifs, an installable file system to read/write ext2 (the Linux filesystem) filesystems.
RUN EXTENDFS.EXE
[Table of contents] [Index] [RUN, START AND CALL]
Part of JFS.IFS in Warp Server for E-Business
RUN GENAUDD.SYS
[Table of contents] [Index] [RUN, START AND CALL]
Generic WinOS/2 Audio Driver Daemon component
RUN HFS.EXE
[Table of contents] [Index] [RUN, START AND CALL]
Part of the HFS.IFS for accessing HFS formatted Apple Disks
RUN HYBERSET.EXE
[Table of contents] [Index] [RUN, START AND CALL]
Runs Hybernation Memory Tab
<<=TIP=>> The command "hybernat" run as either an icon, or from an OS/2 prompt, will put your laptop (caution, or your PC) into hybernation mode.
RUN IOMGSYNC.EXE
[Table of contents] [Index] [RUN, START AND CALL]
Necessary for the Iomega Tools protect, lock, iomgfmt, remount, unitinfo, addman and readme
RUN IP2XDMN.EXE
[Table of contents] [Index] [RUN, START AND CALL]
Dualstor Backup Daemon
RUN IRDNDS.EXE
[Table of contents] [Index] [RUN, START AND CALL]
Neded to run IBM Infrared NDIS MAC Driver
RUN ISOFSDMN.EXE
[Table of contents] [Index] [RUN, START AND CALL]
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
RUN KBFAST.EXE
[Table of contents] [Index] [RUN, START AND CALL]
Runs keyboard enhancer to speed up keyboard
RUN LANDLL.EXE
[Table of contents] [Index] [RUN, START AND CALL]
This starts the TCPIP/peer Stack.
RUN LANMSGEX.EXE
[Table of contents] [Index] [RUN, START AND CALL]
Part of the MPTS messaging system.
RUN LOGDAEM.EXE
[Table of contents] [Index] [RUN, START AND CALL]
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.
Parameters:
/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 parameter. The default size is 64k, but with this switch you can set the value from 4k to 64k.
<<=NOTE=>> Use SYSLOG.EXE from an OS/2 command line prompt to view your log file.
RUN LSDAEMON.EXE
[Table of contents] [Index] [RUN, START AND CALL]
The Lan Server Daemon also needed by the OS/2 File and Print Client
provide support for LAN Server.
RUN LT_MON.EXE
[Table of contents] [Index] [RUN, START AND CALL]
Lucent Technologies Modem Monitor
An older version is available at http://www.drmartinus.de/notebook2/notebook.src
RUN LVMALERT.EXE
[Table of contents] [Index] [RUN, START AND CALL]
Part of the L(ogical) V(olume) M(anager) in Warp Server for E-Business
RUN MIDIDMON.EXE
[Table of contents] [Index] [RUN, START AND CALL]
This is for MIDI
RUN MSENSIT.EXE
[Table of contents] [Index] [RUN, START AND CALL]
From the FM-Utils, accelerates the mouse
RUN MWSTART.EXE
[Table of contents] [Index] [RUN, START AND CALL]
Daemon for the MWAVE Modem for IBM Thinkpads
RUN NBDAEMON.EXE
[Table of contents] [Index] [RUN, START AND CALL]
Loads the NETBIOS daemon process.
RUN NBTCP.EXE
[Table of contents] [Index] [RUN, START AND CALL]
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 NDCTL.EXE
[Table of contents] [Index] [RUN, START AND CALL]
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.
RUN NMPBIND.EXE
[Table of contents] [Index] [RUN, START AND CALL]
Executable from WATCOM C/C++ Version 11.0
Information by Wm D Loughman (wdlkhl@attglobal.net)
RUN NPDAEMON.EXE
[Table of contents] [Index] [RUN, START AND CALL]
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.
RUN NWDAEMON.EXE
[Table of contents] [Index] [RUN, START AND CALL]
Another daemon program, provides IPX packet exchange.
RUN PC.EXE
[Table of contents] [Index] [RUN, START AND CALL]
Executable from Process Commander
RUN QRYMMCD.EXE
[Table of contents] [Index] [RUN, START AND CALL]
Queries the Audio CD
RUN RAMDISK.EXE
[Table of contents] [Index] [RUN, START AND CALL]
Creates a RAM drive together with RAM(64).IFS every boot.
Variable:
driveletter: - creates a Ramdisk called driveletter:
RUN RSRV.EXE
[Table of contents] [Index] [RUN, START AND CALL]
By older versions of IBM Open32 for Warp3. Should be deleted after applying Fixpak 26 or higher for Warp3.
RUN SMSTART.EXE
[Table of contents] [Index] [RUN, START AND CALL]
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=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.
RUN SPDAEMON.EXE
[Table of contents] [Index] [RUN, START AND CALL]
Loads a daemon process that handles SPX packets.
RUN START_S0.EXE
[Table of contents] [Index] [RUN, START AND CALL]
For Teles ISDN Cards
RUN ULTRADMN.EXE
[Table of contents] [Index] [RUN, START AND CALL]
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
RUN USBMON.EXE
[Table of contents] [Index] [RUN, START AND CALL]
USB daemon to detect add and removals of devices.
RUN VDOSCTL.EXE
[Table of contents] [Index] [RUN, START AND CALL]
DOS TCP/IP Stack processing
<<=TIP=>> If you don't need TCP/IP support in DOS sessions REM this line:
RUN VFAT_LW.EXE
[Table of contents] [Index] [RUN, START AND CALL]
Used Bye the VFat Filesystem driver
RUN VNRMINIT.EXE
[Table of contents] [Index] [RUN, START AND CALL]
needed by the OS/2 file and print client of Lanserver 4.0.
RUN WATCHCAT.EXE
[Table of contents] [Index] [RUN, START AND CALL]
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).
RUN WCCAD.EXE
[Table of contents] [Index] [RUN, START AND CALL]
WatchCat 2.1 CAD Package Control Program
