IFS FTP.IFS
[Table of contents] [Index] [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.

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

IFS HFS.IFS
[Table of contents] [Index] [IFS]

Loads the Installable File System for reading Apple HFS-Drives and disks.

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/

IFS HPFS.IFS
[Table of contents] [Index] [IFS]

The H(igh) P(erformance) F(ile) System.
If you don't have any good reason not to install this should be the standard file system for OS/2.

Parameters:

/CACHE:nnn (in kb) sets up a disk cache and its size. The default on most systems is low in my opinion.

<<=Warning=>> Keep this one truth in mind about cache size: an excessive cache takes memory available for programs and therefore could have a negative impact on overall system performance. But today, when most systems have 32MB+ the problem is more the restriction of the cache to 2MB.

OS/2s Command Reference and other IBM sources indicate that the maximum cache size for HPFS is currently 2MB (2048), but IBM does not recommend using a cache larger than 1.5MB (1536). Personally, I have 128MB of RAM and have my HPFS cache set to the max: 2048.

If this parameter is omitted, the default is 10% of the available RAM on systems with more than 8MBs of RAM.

/FORCE will give you access to dirty partitions. This is new to the 32-bit CHKDSK which will only run on Warp 3 and 4.

/QUIET suppresses all messages from CHKDSK.

/CRECL sets the maximum record size for caching, from 2k to 64k in multiples of 2k with a default of 4k. This parameter may not exceed 1/4 of the total cache size set with the /cache parameter.

/AUTOCHECK:drive tells the system to check each drive noted to see if it was shut down properly. If not, it will run CHKDSK on only the drives indicated.

/F:n indicates the level of CHKDSK to be used when automatically checking the drives at startup when AUTOCHECK is activated. If no parameter is specifed, /F:2 is the default.

<<=NOTE=>> A /F:3 parameter will be ignored unless you formatted your hard drive with the /L parameter.

You can get better performance from your system by using your available RAM in the most efficient and effective way. Select the case that best describes the file system or amount of RAM you use.

CASE 1: You use only HPFS or only FAT, but not both.

HPFS only. FAT only.
System memory of at least: Set CACHE to: Set DISKCACHE to:

16 MB+ 2048 2048

CASE 2: You use both HPFS and FAT with HPFS active and FAT passive.

System memory of at least: Set CACHE to: Set DISKCACHE to:

16 MB+ 2048 512 -1024

CASE 3: You use both HPFS and FAT with HPFS passive and FAT active.

System memory of at least: Set CACHE to: Set DISKCACHE to:

16 MB+ 1024 2048

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

IFS HPFS386.IFS
[Table of contents] [Index] [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

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

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

IFS JFS.IFS
[Table of contents] [Index] [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.

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.

IFS MCM.IFS
[Table of contents] [Index] [IFS]

IBM's Mobile Office Services' Mobile Cache Manager IFS

IFS NDFS.IFS
[Table of contents] [Index] [IFS]

Net Drive File System Driver

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.

IFS NETWKSTA.200
[Table of contents] [Index] [IFS]

=drive:\IBMLAN\NETPROG\NETWKSTA.200 /I:drive:\IBMLAN /N

Installable Network File system for the LAN Requester.

<<=ATTENTION=>> For netbios to load correctly the NETBIOS.OS2 driver must come before. When you sort the config.sys you have to edit it manually and move this IFS behind.

IFS NFS200.IFS
[Table of contents] [Index] [IFS]

The NFS (Network File System) for OS/2

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.

IFS NFS300.IFS
[Table of contents] [Index] [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.

IFS NWIFS.IFS
[Table of contents] [Index] [IFS]

This installs the networks Installable File System. It enables OS/2 to see the network drives just the same as local drives.

IFS RAMFS.IFS
[Table of contents] [Index] [IFS]

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

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://home3.inet.tele.dk/kro

<<=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\RAMFS64.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).

▒╛. Б═╙╕╔:

IFS RAMFS64.IFS
[Table of contents] [Index] [IFS]

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

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://home3.inet.tele.dk/kro

<<=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\RAMFS64.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).

IFS SRVIFSC.IFS
[Table of contents] [Index] [IFS]

The ThinIFS by IBM.

<<=TIP=>> Ideal for CID-Installations cause it can be used from installation disks.

IFS STUBFSD.IFS
[Table of contents] [Index] [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 and is available for FREE at http://www.geocities.com/SiliconValley/Sector/5785/index.srcl

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.

IFS TONIGY.IFS
[Table of contents] [Index] [IFS]

Tonigy is a program that maps tracks of Audio CD into WAV or RAW files.

http://tonigy.hypermart.net

IFS TVFS.IFS
[Table of contents] [Index] [IFS]

The T(oronto)V(irtual)F(ile)S(ystem)

Author: Mark D. Leitch

The TVFS provides a virtual OS/2 file system that combines symbolic links, search paths, and permissions. Through the TVFS, local and remote file systems may be combined into a single, virtual file system. It is FREE IBM EWS. Latest version is 2.11

<<=Tip=>> Kai Evers has developed an easy to use FREE PM-Interface for controlling and using the TVFS. It is available at http://www1.stuttgart.netsurf.de/~kevers/

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

IFS UDF.IFS
[Table of contents] [Index] [IFS]

DVD-ROM- and DVD-RAM-Filesystem for OS/2 Warp Server for e-Business.

The following DVD-Drives are supported:

TOSHIBA SD-M1202
HITACHI GD-2500
CREATIVE LABS DVD-5240E
PHILIPS DRD-5200
SONY DDU-220E
PANASONIC LF-D100
AOpen DVD-520S

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

<<=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 fixpak13 for WARP 4 which can adress 4 GB.

IFS VFAT-OS2.IFS
[Table of contents] [Index] [IFS]

Vfat installable file system with early NTFS support

As this is alpha (since long) here only the Warning from the read.me

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