CONFIG.SYS - IFS Statements

Return to The Config.sys Documentation Project Main Page

IFS means "Installable File System". This are the drivers to read different file systems like FAT, FAT32 or HPFS.

IFS=ANDREW.IFS

The Andrew File System (AFS)

AFS is a very scalable, highly available, and secure file system with a very robust data management model for ease of administration (Says IBM).

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

IFS=CBS.IFS

IFS for the ZipStream/CryptStream/SecureZipstream compressed/secure file system products. For more information please visit http://www.carbonbased.com.au

  IFS=CBS.IFS

NOTE: Should normally be at the end of config.sys

It is an OS/2 Installable File System (IFS) that mirrors access to existing OS/2 File Systems, and simultaneously provides automatic, transparent file compression and decompression.

Its 32 bit implementation exploits OS/2's pre-emptive multi-threaded processing capabilities, which allows for complex processing to be carried out in the most optimum manner.

ZipStream's transparent background compression operations and intelligent caching techniques means there is no noticeable loss in system performance.

ZipStream's Features

• Supports HPFS and FAT File Systems.

Any OS/2 supported file system can be utilised.

• Supports Diskettes.

Diskettes don't have to be specially formatted, just attach and compression is available.

• Supports LAN File Systems.

Any LAN file system that is mapped as a drive letter can be used for compression operations. Additionally, there are no Server overheads, as all compression operations are performed by the workstation.

• Supports Long File Names.

No restrictions are imposed other that those imposed by OS/2's native File Systems.

• Supports Extended Attributes.

Full support of Extended attributes and compatible with OS/2's Workplace Shell.

• Automatic Compression of New Files.

Newly created files or any files copied to the compressed drive letter are automatically and transparently compressed.

• File Based Compression not Disk Based.

Being file based, you have complete control of what files are compressed and what are not, that is, uncompressed files can reside on the compressed drive.

• Ultra High Compression Ratios.

Using state of the art and background compression techniques yields compression ratios equal to that of popular archiving programs.

• Native OS/2 32 bit Application.

This isn't a port of a DOS compression application, it's been built specifically for OS/2 and designed to get the most out of OS/2.

• Outstanding Performance.

Background compression and 32 bit code gives real pay offs in performance.

• No Reformatting Required.

Just attach to a driver letter or path and compression is available.

• No Container Files.

Using existing File systems means reliability and safety.

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

IFS=CDFS.IFS

The CDFS.IFS enables support for CDROMs. Without this, you can't use your CDROM drive.

IFS=C:\OS2\BOOT\CDFS.IFS [parameters]

Default settings:

• IFS=C:\OS2\BOOT\CDFS.IFS /C:2 /M:8

Parameters:

• /C:value

This sets the size of the cache. Value is expressed in blocks of 64 Kbytes.

• /M:value

This sets up the maximum number of file sectors read at the same time.

• /P:value

Defines the debug output port (COM1 or COM2). Value can be 1 or 2

• /K

Enables the volume descriptor by kanji.

• /Q

Disables error message at boot up.

• /V

Shows the used settings at boot up.

• /W

Enables support for the Joliet CDROM format. This parameter is new with Warp 3 fixpack 32 and Warp 4 fixpack 5. Currently not all versions of the Joliet CDROM format are supported.

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

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

 IFS=CDWFS.IFS

Parameters

• -Q

Installation request

• -D

All accesses are protocolled at 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
No	Yes	Yes	Yes	Yes	Yes

IFS=Ext2-os2.ifs

The Ext2-os2.ifs driver installs support for the Linux ext2 file system. You also need following drivers installed: Ext2flt.flt , Ext2_lw.exe and Mwdd32.sys

  IFS=C:\OS2\fs\ext2\Ext2-os2.ifs parameters

WARNING: Although it is possible to install OS/2 on an EXT2 Partition it is not recommended to do so, as extended attributes are not supported.

NOTE: Seems no longer to work with kernel 2.2.X

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

Parameters:

All parameters are case insensitive and you can use a "/" instead of the "-". Use any logical combination of the parameters.

• -q

This parameter turns off the banner during boot up.

• -cache:value

The cache parameter sets up the maximum disk cache size. This value is the maximum amount of physical memory ext2-os2.ifs can dynamically allocate for the disk cache. Value can be in the range from 240 to the value of the installed RAM . This value is expressed in Kbytes. If this parameter is not set, it defaults to 240 .

• -rw

Use this parameter if you want to have write access to the disk. If this parameter is not set, you have read access only to the disk. note: You must also enable the write access on the Ext2flt.flt driver.

• -no_auto-fsck

Prevents ext2-os2 from forcing Linux to run e2fsck on partitions "touched" by OS/2. The default is to force Linux to run e2fsck.

• -case_retensive

This option makes the ext2 file system behave like HPFS. With this option set you can access a file by the name of the file no matter what case you use. The default is case sensitive. That means that you can access a file only if you use the right case.

• -IFS trace entry point

Traces one or more specific IFS entry points. Ext2-os2.exe generates than an output whenever the specified entry point is entered.An example of this parameter would look like this: IFS=ext2-os2.ifs -FS_Copy -FS_Delete

Here is a list of the available entry points:
o FS_AllocatePageSpace
o FS_ChDir
o FS_ChgFilePtr
o FS_Close
o FS_Commit
o FS_Copy
o FS_Delete
o FS_DoPageIO
o FS_Exit
o FS_FileAttribute
o FS_FileInfo
o FS_FindClose
o FS_FindFirst
o FS_FindFromName
o FS_FindNext
o FS_FlushBuf
o FS_FsInfo
o FS_IOCtl
o FS_MkDir
o FS_Mount
o FS_Move
o FS_NewSize
o FS_OpenCreate
o FS_OpenPageFile
o FS_PathInfo
o FS_ProcessName
o FS_Read
o FS_RmDir
o FS_ShutDown
o FS_Write 

• -no_strat2

Use this option to turn off the extended I/O operations. Turn the extended I/O only off, if you have any problems with it. If you use Os2dasd.dmd as your block device driver it should work fine. If this parameter is not set up, the default is to use the extended I/O on every fixed disk.

• -errors=value

Here you can set up what ext2 should do when it finds an error in the file system. Value can be panic or continue . If set to panic the system will halts immediately. You must boot Linux and run e2fsck to repair your file system. Use the continue option to go on with your work after an error where detected. Ext2 marks this partition as bad and forces Linux to run e2fsck on the next Linux reboot.

• -output=comport

Redirect the ext2 messages to the specified comport. It is only necessary for tracing or debugging Comport can be com1 or com2 .

• -tz=value

Specifies the timezone in minutes from UTC (GMT). This parameter is used to have the same date and time for files as Linux. Value can be in the range from -1440 to +1440 . 0 is the same as GMT.

• -force_strat2:drive-number

Ext2 normally use extended disk I/O only on fixed disk, but not on removable media. With this option set removable media can use extended disk I/O, if available. This will improve your performance. But you must first use the unmount.exe utility before you can remove the drive. Drive-number can be in the range from 0 to 26 . A "0" for the drive-number means drive "A", a "1" means drive "B" and so on.

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

IFS=FAT32.ifs

Gives support for the FAT32 file system under OS/2.

IFS=Fat32.ifs parameters

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=C:\OS2\CACHEF32.EXE and BASEDEV=PARTFILT.FLT for more information

NOTE: For Warp 4 with fixpak 10 you need at least ver.0.88, for Warp for e-business (Aurora) at least ver.0.89.

TIP: Since Fixpak 12 for Warp4 Fdisk can handle FAT32. To boot update the OS/2 Bootmanager (by first deleting, and new installation).

Parameters:

• /Q

Disable the messages shown at boot up.

• /Cache:value

Speficies the cache size in kilobytes. Value can be in the range from 0 to 2048 . if not set it defaults to 1024 Kbytes.

• /Monitor

This option is needed by the Monitor.exe program.

• /RASectors:value

efines the numbers of sectors which should be read per read action and

• /EAS

Gives support for the Extended Attributes (EAs).

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

IFS=FTP.IFS

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.

  IFS=FTP.IFS

Developed by Vitalij Timchishin (tvv@sbs.kiev.ua). Unfortunately it is no more FREEWARE.

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

IFS=HFS.IFS

Hfs-ifs is an installable file system for reading/writing Macintosh Hfs (Hierarchical File system) -Media, transparently in OS/2. Be it a floppydisc, CDom or even a harddisc. To get Hfs support you need have installed the BASEDEV=Hfsflt.flt and the RUN=Hfs.exe drivers.

IFS=C:\Os2\Fs\Hfs\Hfs.ifs Parameter

Parameters:

• /Q

Prevents the Ifs from displaying the startup logo during the boot.

note: If you intend to use HFS-CDRoms you must place the Hfs.ifs line in front of the Cdfs.ifs line.

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/

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

IFS=HPFS.IFS

This command installs the High Performance File System. Without this command you can't access any HPFS formatted drives.

  IFS=C:\OS2\HPFS.IFS [parameter]

NOTE: You can have multiple partitions, they will all be serviced by the same cache, so you may have 2 HPFS and 3 FAT partitions for example. For purposes of the table above, "active" and "passive" are descriptors for the way a cache is used. If it is seldom used, it is "passive." If a lot of disk intensive I/O occurs with the cache, it is "active."

NOTE: HPFS is more efficient than FAT, you should therefore attempt to transfer all the most frequently used applications to an HPFS drive, and also locate your SWAPPER.DAT on an HPFS drive. This will mean that HPFS is "active", and FAT "passive"

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.

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 parameter in this command, the system will not boot.

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

Tip: Use HPFS386.IFS if you have an license. It brings an significant performance boost into your system.

Tip: For analysing 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. It is reported that it fails on partitions greater than 2Gb or with HPFS 2.3 (not verified).

Parameters:

• /C:value or /CACHE:value

Determines the cache size. Value can be D or in the range from 1 to 2048 . If set to D the cache size is 10% of RAM up to the maximum of 2048 Kbytes. Default is D This value is expressed in Kbytes.

• /CRECL:value

Specifies the maximum file size to be cached. If a file is greater than this value the file is not cached. Value can be in the range from 2 to 64 in multiplies of 2. Default = 4 This value is expressed in Kbytes.

• /AC:drives

The AC parameter specifies which drives should be checked by chkdsk.exe during start up after an improper shut down. Add only the drive letter without the colon. If you want to run chkdsk.exe on a drive at every start up add a plus sign (+) in front of the drive letter.

• /F:level

Indicates on which level chkdsk.exe should be run. Level can be in the range from 1 to 3 . Default is 2

• /Quiet

If this option is set up, the Hpfs.ifs driver will show no error messages at boot up. This parameter can not be the last parameter!

• /Force

With this option set you can get access to a disk that is marked as bad and is not in the Autocheck list (the /AC: parameter). But beware there are may errors in the file system, so run chkdsk as soon as possible.

The following line sets up a two megabyte cache size, allows only files which are not greater than 32 Kbytes to be cached and autochecks drive C: and drive D: after an improper shut down:

IFS=C:\OS2\HPFS.IFS /CACHE:2048 /CRECL:32 /AC:CD 

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

IFS=HPFS386.IFS

The 386 High Performance File System is an enhancement of the regular HPFS and normally sold together with the LAN-Server. In contrary to HPFS it is not written in C but in Assembler and consists of an optimised 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

  IFS=HPFS386.IFS

NOTE: Usage of EARLYMEMINIT=YES produces a trap on boot. Plese remove this parameter.

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 redbooks at http://publib.boulder.ibm.com or the wsonw4pdf. available at: http://rheooptik.fmf.uni-freiburg.de/www/faq/remmedia.htm

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

INSTALL AND TUNE THE HPFS386.IFS

To install HPFS386 do the following:

remove the HPFS.IFS line you have already: for example:

  REM IFS=C:\OS2\HPFS.IFS

Now add

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

if your boot drive isn't C: change it to correct drive

Next still in config.sys, add the directory C:\IBM386FS somewhere in each of your PATH, DPATH and LIBPATH.

Next still in Config.SYS, if you have a RUN=CACHE.EXE line, comment it out with a REM.

Insert CALL=C:\OS2\CMD.EXE /Q /C C:\IBM386FS\CACHE386.EXE >NUL

Save the config.sys.

This is it, you are ready to shutdown and reboot.

try a cool cache monitor in cache386 bye typing this:

CACHE386 /STATS:D this will show a constantly updated display of all the cache statistices, reads, writes, cache hits, percentages etc. Press CTRL-C to stop.

Do not use CACHE.EXE anywhere, it's not made for this

TIP: You should also create bootdisks or a maintanance partition with HPFS386 by using btos2. For tuning the HPFS386.IFS you have to set the HPFS386.INI

here's one example:

.;===========================================================================

This file contains the initialization parameters for the 386 HPFS. The

parameters are grouped into components. The component groups start with the

component name enclosed in square brackets. Each component name appears on

a line by itself (a comment is allowed). The components include the

following

[filesystem] ; General file system parameters

[lazywriter] ; Lazy writer parameters

[DASD_Limits] ; DASD Limits parameters

[UltiMedia] ; UltiMedia parameters (added when LAN Server Ultimedia

; is installed)

General rules

- The component names and parameters are not case-sensitive. They can be

entered in upper case, lower case, or a mixture of upper and lower case.

- Wherever a blank appears in the syntax for a parameter, it can be left out

or additional blanks can be added. For example, the following syntaxes

are all valid

parameter = yes

parameter=yes

parameter= yes

- Any text after a semicolon (;) up to the end of the line is treated as a

comment.

- All components and parameters are optional. If you do not specify a

parameter, the 386 HPFS uses a default setting for the parameter.

===============================================================================

[filesystem] useallmem = YES lanroot = D:\IBMLAN cachesize = 8192

-------------------------------------------------------------------------------

The [filesystem] section specifies general file system parameters. If you

make any changes to these parameters, they do not take effect until you

reboot the system.

useallmem = [yes|no]

This parameter specifies whether the 386 HPFS should use memory above the

16M boundary, provided this system is configured with more than 16M.

Some adapters, for example the IBM Token Ring Busmaster Server/A, cannot

do direct memory access (DMA) to memory above the 16M boundary. If you

have a LAN or disk adapter that cannot do DMA to memory above the 16M

boundary, the 386 HPFS must use only memory below 16M so that the adapter

can put data into the file system buffers. Set useallmem to yes if all

of your adapters can access memory above the 16M boundary. Set useallmem

to no if any of your LAN or disk adapters cannot access memory above the

16M boundary. If useallmem is not specified, the default setting is no.

cachesize = nnnn

This parameter specifies how many kilobytes of memory the 386 HPFS should

claim for its cache. The cache size must be a minimum of 256KB. The

maximum value is determined by the size of available memory. If

cachesize is not specified, the default is to use 20% of available

memory, if the amount of available memory is below 20MB, or 60% of

available memory, if the amount of available memory is 20MB or more.

maxheap = nnnn

This parameter sets a limit on the size of the heap. nnnn is the maximum

number of kilobytes to which the heap can grow. The 386 HPFS allocates

heap memory as needed. If this parameter is used, the 386 HPFS only

allocates memory for the heap up to the amount specified. If this

parameter is not used, there is no limit on the heap size. Use this

parameter only if you need to reserve memory on the system for other

applications that may be running. The minimum value is 64KB. The

maximum value is determined by the size of available memory minus the

size of the cache. If maxheap is not specified, the default is to have

no limit on the heap size.

lanroot = d

\path

This parameter specifies the drive and path of the directory for the LAN

Server software. The installation program fills in this parameter for

you. You do not need to change this parameter.

fsprealloc = nn

This parameter specifies how many big buffers to allocate when the file

system is initialized. If neither fsprealloc nor srvprealloc are used,

the file system allocates big buffers as needed. The allocation of big

buffers can take a little time. Allocating the big buffers at

initialization improves the performance of the first requests that need

big buffers. The buffers are not freed until the system is shut down.

The minimum value for fsprealloc is 2. The maximum is 64. If both

fsprealloc and srvprealloc are specified in this file, fsprealloc is used

and srvprealloc is ignored.

srvprealloc = nn

This parameter specifies how many big buffers to allocate when the server

is started rather than when the file system is initialized. This

parameter, like the fsprealloc parameter, can improve the performance of

the first requests that need big buffers. The buffers are freed when

the server is stopped. The minimum value for srvprealloc is 2. The

maximum is 64. If both fsprealloc and srvprealloc are specified in this

file, fsprealloc is used and srvprealloc is ignored.

-------------------------------------------------------------------------------

[lazywriter] lazy = *: ON maxage = *: 5000 bufferidle = *: 500

-------------------------------------------------------------------------------

The [lazywriter] section specifies settings for the lazy writer. If you

make any changes to these parameters, they do not take effect until you

reboot the system. You can use the CACHE386 program to change the internal

setting of these parameters while the system is running. When you reboot

the system, the parameters are set to the values in this file.

lazy = [drives

] on|off

This parameter specifies whether the lazy writer is to be turned on or

off for the specified drives. The [drives

] can be a series of drive

letters. For example, "lazy = cdfg

on" would turn on the lazy writer

on drives c

, d:, f:, and g:. It would not change the settings for drive

e

or h:. An asterisk (*) can be used for the drive letter to indicate

that all drives are to have the setting. This line can be used multiple

times to achieve the settings you want for your drives. If lazy is not

specified, the default value is to turn the lazy writer off for all

drives.

maxage = [drives

] nnnn

This parameter specifies the maximum number of milliseconds that can pass

before the lazy writer writes the contents of a buffer to the disk. The

[drives

] can be a series of drive letters. For example,

"maxage = cdfg

5000" would set the maximum buffer age to 5000ms on

drives c

, d:, f:, and g:. It would not change the settings for drive e:

or h

. An asterisk (*) can be used for the drive letter to indicate that

all drives are to have the setting. This line can be used multiple times

to achieve the settings you want for your drives. The minimum value is

0. The maximum value is 1000000. If maxage is not specified, the

default value is 10000 for all drives.

bufferidle = [drives

] nnnn

This parameter specifies the maximum number of milliseconds during which

a buffer is not used before the lazy writer writes the buffer contents to

the disk. The [drives

] can be a series of drive letters. For example,

"bufferidle = cdfg

500" would set the buffer idle time to 500ms on

drives c

, d:, f:, and g:. It would not change the settings for drive e:

or h

. An asterisk (*) can be used for the drive letter to indicate that

all drives are to have the setting. This line can be used multiple times

to achieve the settings you want for your drives. The minimum value is

0. The maximum value is 500000. If bufferidle is not specified, the

default value is 1000 for all drives.

-------------------------------------------------------------------------------

[DASD_Limits] ThreshAlertNames = *: ADMINS ThreshAlertDelay = *: 10 ThreshAlertUser = *: yes DirFullAlertNames = *: ADMINS DirFullAlertDelay = *: 10 DirFullAlertUser = *: yes

-------------------------------------------------------------------------------

The [DASD_Limits] section specifies settings of parameters for the DASD

Limits function. If you make any changes to these parameters they do not

take effect until you restart the server. (To stop and restart the server,

at an OS/2 command prompt, enter the command "net stop server" and then the

command "net start server".)

ThreshAlertNames = [drives

] [user1] [user2] [group1] [group2] ...

This parameter lists the users or groups that are to be notified when a

DASD Limits threshold is crossed on the specified drives. Any mixture of

user names or group names can be used. All of the names must appear on

one line. This line can be used multiple times to achieve the settings

you want for your drives. If ThreshAlertNames is not specified, the

default is to have no user or group names.

ThreshAlertDelay = [drives

] nn

This parameter specifies how many minutes to wait before sending another

alert for a threshold that was previously crossed on the specified

drives. If a threshold is crossed more than once within the delay

period, an alert is sent only for the first occurrence. An alert is sent

if a higher threshold is crossed during the delay period. This parameter

is used to cut down on the number of alerts that can be generated when

there is a lot of disk activity and the disk size is within the

threshold. This line can be used multiple times to achieve the settings

you want for your drives. If ThreshAlertDelay is not specified, the

default is 10 minutes on all drives.

ThreshAlertUser = [drives

] yes|no

This parameter specifies whether to send an alert to the user whose disk

usage caused a threshold to be crossed on the specified drives. This

line can be used multiple times to achieve the settings you want for your

drives. If ThreshAlertUser is not specified, the default is yes for all

drives.

DirFullAlertNames = [drives

] [user1] [user2] [user3] ...

This parameter lists the users or groups that are to be notified when a

DASD limit is reached. Any mixture of user names or group names can be

used. All of the names must appear on one line. This line can be used

multiple times to achieve the settings you want for your drives. If

DirFullAlertNames is not specified, the default is to have no user or

group names.

DirFullAlertDelay = [drives

] nn

This parameter specifies how many minutes to wait before sending another

alert for a DASD limit that was previously reached. If a DASD limit is

reached more than once within the delay period, an alert is sent only for

the first occurrence. This parameter is used to cut down on the number

of alerts that can be generated when there is a lot of disk activity and

the DASD limit is reached several times. This line can be used multiple

times to achieve the settings you want for your drives. If

DirFullAlertDelay is not specified, the default is 10 minutes on all

drives.

DirFullAlertUser = [drives

] yes|no

This parameter specifies whether to send an alert to the user whose

request failed because a DASD limit was reached. This line can be used

multiple times to achieve the settings you want for your drives. If

DirFullAlertUser is not specified, the default is yes for all drives.

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

IFS=JFS.IFS

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.

  IFS=JFS.IFS

Parameter:

• /CACHE:

Specifies the size of the JFS buffer cache in Kilobytes. By default, this size is set to 12.5 percent of real memory.

• /AUTOCHECK:drive[drive...]

Specifies a list of JFS file systems, identified by driver letter, to be included in automatic recovery by CHKDSK at the time of JFS initialization. If an asterisk (*) is specified instead of a drive letter list, all JFS file systems will be included in automatic recovery during JFS initialization. If any drive letter is preceded by an arithmetic plus sign (+), CHKDSK will perform a full integrity check on the drive even if journal log replay has restored the drive to an apparently consistent state. If the list of drive letters ends with plus-asterisk (+*), CHKDSK will perform a full integrity check on all JFS file systems not specified in the list even if journal log replay has restored them to an apparently consistent state.

• /L:OFF

Specifies the lazy write parameters in seconds. OFF forces all to be synchronous. (JFS ignores any characters between the L (or l) and the colon, so valid flags are /L: /LAZY: /LW: /lazywrite: etc.)

• /L:

Synctime is the interval at which the sync thread runs, default is 64. Maxage is the longest time that a modified file is kept in cache, default is synctime*4. Bufferidle is the time indicating a "recent" change. Changes newer than this value are not written unless the last write was older than maxage, default is Min(1, synctime/8).

The cachejfs.exe command allows the lazywrite parameters to be changed immediately. The syntax is to the IFS line, except that the /L: prefix is optional. In addition, the cachejfs command can modify the minimum and maximum number of free cache buffers to be maintained. Calling cachejfs with no parameters reports the current settings.

CACHEJFS [[/LAZYWRITE:]{OFF|syncTime[,maxAge[,bufferIdle]]}] /MINFREE:minfree /MAXFREE:maxfree

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]

Parameter: 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.

NOTE: JFS is also availabel.for Linux. To create an OS/2 compatible partition use the -O paramter. Format 3rd partition on 2nd hard disk with the volume label "JFS_hdb3" and OS/2 compatibilty:

  mkfs.jfs -L -O JFS_hdb3 /dev/hdb3

Parameter for mkfs.jfs:

• -c Check the device for bad blocks before building the file system.
• -j journal_device Set the journal device. (Experimental)
• -L volume_label Set the volume label for the file system.
• -O Provide case-insensitive support for compatibility with OS/2.
• -q Quiet execution - do not ask for confirmation before creating the file system.
• -s log_size Set the log size (in megabytes). If the -s option is not used, the default is 0.4% of the aggregate size.
• -V Print version information and exit (regardless of any other chosen options).

Platform Support:

OS/2 2.x	OS/2 3.0	OS/2 4.0	OS/2 4.5x	eCS 1.x	eCs 2.x
No	No	No	Yes	Yes	Yes

IFS=MCM.IFS

This is the installable file system for Mobile File Synchronization (MFS).

IFS=C:\Mfs\Dll\Mcm.ifs 

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

IFS=NDFS.IFS

Net Drive File System Driver

  IFS=NDFS.IFS

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	eCS 1.x	eCs 2.x
Yes	Yes	Yes	Yes	Yes	Yes

IFS=Netwksta.200

This is the LAN Redirector. This installable file system allows File and Print Network drives to be seen as local drives.

IFS=C:\Ibmlan\Netprog\Netwksta.200 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

IFS=NFS200.IFS

The NFS (Network File System) for OS/2

  IFS=NFS200.IFS

The Network File System (NFS) allows you to manipulate files on remote TCP/IP for OS/2 hosts as if they reside on your local host. NFS is based on the NFS protocol, and uses the Remote Procedure Call (RPC) protocol to communicate between the client and the server. The files to be accessed reside on the server host and are made available to the user on the client host.

NFS supports a hierarchical file structure. The directory and subdirectory structure can be different for individual client systems.

For more information about NFS, see RFC 1094.

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

IFS=NFS300.IFS

The Network File System (NFS) allows you to manipulate files on remote TCP/IP for OS/2 hosts as if they reside on your local host. NFS is based on the NFS protocol, and uses the Remote Procedure Call (RPC) protocol to communicate between the client and the server. The files to be accessed reside on the server host and are made available to the user on the client host.

   IFS=NFS300.IFS

NFS supports a hierarchical file structure. The directory and subdirectory structure can be different for individual client systems.

For more information about NFS, see RFC 1094.

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

IFS=NTFS.IFS

Installabe File System for the NTFS file system - new with eCS 1.1.

  IFS=NTFS.IFS

Parameter:

• /AUTOCHECK:*

not used

• /CACHE:xxxxx

Specifies the size of the NTFS buffer cache in bytes. By default, this size is set to 12.5 percent of real memory.

• /RO:x

All volumes are accessed in Read Only mode, check disk is read only too. x may be letter(s) of volume or symbol '*'. Mean is as swicth /AUTOCHECK. Note: If DirtyFlag is set and /RO selected then the system doesn't mounted it.

• /FR:xx

reference file number to show in root directory. xx may be 5..20. Use it to hide system files ($MFT, $MFTMirr, etc) in root directory. Default is 10;

• /V

detailed report of chkdsk on startup

• /Q

don't show copyright on startup

Platform Support:

OS/2 2.x	OS/2 3.0	OS/2 4.0	OS/2 4.5x	eCS 1.x	eCs 2.x
No	No	Yes	Yes	Yes	Yes

IFS=NWIFS.IFS

This is the Netware installable file system and allows OS/2 to see the Netware network drives like it sees the local drives.

IFS=C:\Netware\Nwifs.ifs 

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

IFS=RAMFS.IFS

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

  IFS=RAMFS.IFS

Parameter:

• /Q

disables messages at boot

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://karl.myip.org

Tip: By Ulrich Moeller: Some applications have trouble with TEMP being set to the root directory of a drive. So if you set TEMP to the RAM disk, have a \temp directory created thru the following statement in CONFIG.SYS:

  IFS=drive:\common\ifs\RAMFS.IFS
  CALL=drive:\common\ifs\RAMDISK.EXE R:
  RUN=drive:\OS2\CMD.EXE /C md R:\temp

(replace R: with your system's paths, of course).

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

IFS=RAMFS64.IFS

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

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

IFS=SRVIFSC.IFS

The ThinIFS by IBM.

TIP: Ideal for CID-Installations cause it can be used from installation disks.

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

IFS=STUBFSD.IFS

ISOFS is an installable file system for OS/2 to access ISO rawfiles suitable for burning on CD. It allows transparent access to the contents of the raw file. Currently only Joliet filenames are supported but this may change in the future.

Developed by Chris Wohlgemuth.

or with Parameter 'AEFS':

AEFS is a cryptographic file system for OS/2. It allows transparent access to encrypted files stored on any file system supported by OS/2. The user can encrypt data using a number of block cipher algorithms (currently, Twofish and Rijndael). It supports long file names and extended attributes. It's also reasonably fast.

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

IFS=TONIGY.IFS

Tonigy Installable File System

Tonigy is an Audio/Video/Data CD IFS for OS/2 that maps tracks of Audio CD into WAV or RAW files, tracks of Video CD into MPG files and tracks of Data CD into ISO files. Use it for accessing audio, video and data tracks like ordinary files. Also Tonigy allows to access files of CD-I disks.

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

IFS=TVFS.IFS

The Toronto Virtual File System (TVFS) is not a filesytem with that you can format a harddisk, it is virtual. It is used to collect a selecteable amount of files and directories from different drives on one TVFS drive.

IFS=C:\Os2\fs\Tvfs\TVFS.IFS /LOGO

TIP: Kai Evers has developed an easy to use FREE PM-Interface for controlling and using the TVFS.

TIP: See also TVFS-RM by Jrgen Dankoweits at http://www.geocities.com/SiliconValley/Way/3792

Parameter:

• /LOGO

Enables the short message at boot time.

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

IFS=UDF.IFS

CD-RW, DVD-ROM and DVD-RAM-Filesystem

To work correct you must also use the updated OS2CDROM.DMD which is delivered with the UDF Package or any newer build.

For correct operation make sure that DEVICE=drive:\OS2\BOOT\UNICODE.SYS is in your config.sys too.

TIP: To view DVD-Videos with Warpvision make sure UDF.IFS resides before CDFS.IFS

NOTE: The UDF Driver is only available via Software-Choice if you have a subscription for it.

ATTENTION: UDF.IFS runs only with Warp Server for e-Business and fixpak>13 for WARP 4 which can adress 4 GB.

Tested drives with version 2.01:

• TOSHIBA SD-M1202
• HITACHI GD-2500
• CREATIVE LABS DVD-5240E
• PHILIPS DRD-5200
• SONY DDU-220E
• PANASONIC LF-D100
• PANASONIC LF-D201
• AOpen DVD-520S
• HEWLETT-PACKARD 8200
• HEWLETT-PACKARD 9100
• HEWLETT-PACKARD 9200
• SONY SPRESSA CRX100E/X
• MATSUSHITA UDJA-310
• SONY CDX-700E
• TOSHIBA SD-R2002
• TOSHIBA SD-2302
• SONY CRX200E-A1

Parameter:

• /Q

Disables messages at boot up.

Platform Support:

OS/2 2.x	OS/2 3.0	OS/2 4.0	OS/2 4.5x	eCS 1.x	eCs 2.x
No	Yes	Yes	Yes	Yes	Yes

IFS=VFAT-OS2.ifs

The Vfat-os2.ifs driver installs support for the Windows Vfat file system. You need also following drivers installed: Vfat_lw.exe and Mwdd32.sys :Note. The Vfat-os2.ifs includes also support for the Linux ext2 file system. To enable it you need to add BASEDEV=EXT2FLT.FLT to your config.sys file.

IFS=C:\OS2\fs\Vfat\Vfat-os2.ifs parameters

ATTENTION: vfat-os2 is a FILE SYSTEM DRIVER. Being a driver it runs at the most privileged level of the OS/2 operating system, known as "kernel mode". IN KERNEL MODE THERE IS NO MORE CRASH PROTECTION. It means that if a bug occurs in the driver IT CAN CAUSE A HANG OR A SYSTEM HALT, AND THUS CAN CAUSE LOSS OF DATA. I STRONGLY SUGGEST YOU TO MAKE A BACKUP OF ALL YOUR DATA (EVEN IF THEY ARE NOT LOCATED ON A VFAT PARTITION) PRIOR TO USE THIS DRIVER. DON'T USE THIS DRIVER ON A PRODUCTION MACHINE, OR IF YOU MANIPULATE CRITICAL DATA. IF HUMAN LIFE DEPENDS ON YOUR SYSTEM, DON'T INSTALL THIS DRIVER ON IT. USE IT AT YOUR OWN RISKS, AND ONLY ON A MACHINE YOU ACCEPT TO CRASH AND REINSTALL.

Parameters:

All parameters are case insensitive and you can use a "/" instead of the "-". Use any logically combination of the parameters.

• -q

This parameter turns off the banner during boot up.

• -VFAT:value

Specifies which VFAT partition should be supported. Value can be * , one or more drive letters or one or more drive letters with a plus sign . To use all recognized FAT partition as VFAT you need to add this: -VFAT:* To use a list of recognized FAT partition as VFAT you need to add the driver letters to the -VFAT: parameter. For example use drive E and F as Vfat use this option: -VFAT:EF To force a FAT partition as VFAT when not automatically recognized add a plus sign after the drive letter: -VFAT:E+

• -cache:value

The cache parameter sets up the maximum disk cache size. This value is the maximum amount of physical memory Vfat-os2.ifs can dynamically allocate for the disk cache. Value can be in the range from 240 to the value of the installed RAM . This value is expressed in Kbytes. If this parameter is not set it defaults to 240 .

• -rw

Use this parameter if you want to have write access to the disk. If this parameter is not set you have only read access to the disk. note: You can also use the vfat-os2.exe program to enable a limited write access.

• -no_auto-fsck

Only available with ext2flt.flt . Prevents vfat-os2 from forcing Linux to run e2fsck on partitions "touched" by OS/2. The default is to force Linux to run e2fsck.

• -case_retensive

ext2flt.flt . This option makes the ext2 file system behave like HPFS. With this option set you can access a file by the name of the file no matter what case you use. The default is case sensitive. That means that you can access a file only if you use the right case.

• -IFS trace entry point

Traces one or more specific IFS entry points. Vfat-os2.exe generates than an output whenever the specified entry point is entered.An example of this parameter would look like this: IFS=vfat-os2.ifs -FS_Copy -FS_Delete

Here is a list of the available entry points:
o FS_AllocatePageSpace
o FS_ChDir
o FS_ChgFilePtr
o FS_Close
o FS_Commit
o FS_Copy
o FS_Delete
o FS_DoPageIO
o FS_Exit
o FS_FileAttribute
o FS_FileInfo
o FS_FindClose
o FS_FindFirst
o FS_FindFromName
o FS_FindNext
o FS_FlushBuf
o FS_FsInfo
o FS_IOCtl
o FS_MkDir
o FS_Mount
o FS_Move
o FS_NewSize
o FS_OpenCreate
o FS_OpenPageFile
o FS_PathInfo
o FS_ProcessName
o FS_Read
o FS_RmDir
o FS_ShutDown
o FS_Write 

• -no_strat2

Use this option to turn off the extended I/O operations. Turn the extended I/O only off, if you have any problems with it. If you use Os2dasd.dmd as your block device driver it should work fine. If this parameter is not set up, the default is to use the extended I/O on every fixed disk.

• -errors=value

Here you can set up what vfat should do when it finds an error in the file system. Value can be panic or continue . If set to panic the system will halts immediately. You must boot Windows/Linux to repair your file system. Use the continue option to go on with your work after an error where detected. Ext2 marks this partition as bad and forces Linux to run e2fsck on the next Linux reboot.

• -output=comport

Redirect the ext2 messages to the specified comport. It is only necessary for tracing or debugging Comport can be com1 or com2 .

• -tz=value

ext2flt.flt . Specifies the timezone in minutes from UTC (GMT). This parameter is used to have the same date and time for files as Linux. Value can be in the range from -1440 to +1440 . 0 is the same as GMT.

• -force_strat2:drive-number

Vfat normally use extended disk I/O only on fixed disk, but not on removable media. With this option set removable media can use extended disk I/O, if available. This will improve your performance. But you must first use the unmount.exe utility before you can remove the drive. Drive-number can be in the range from 0 to 26 . A "0" for the drive-number means drive "A", a "1" means drive "B" and so on.

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

IFS=VMMAP.IFS

This driver comes with Microsoft Virtual Machine Additions for OS/2 for MS Virtual PC 2007. This the OS/2 Additions Shared Folders File System Driver. This allows to share folders from Windows to OS/2 VM.

 IFS=C:\VM\VMMAP.IFS

Parameters:

• /Q

Quiet Mode: Disable messages at boot.

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