CONFIG.SYS - Other Information

Adding LVM to Warp 4
If you have Warp 4 >FP13 installed you may want to add the Logical Volume Manager.

The following steps add the support for LVM to your OS/2 Warp 4 partition: That's it. From now on you can use LVM within Warp 4.
 * 1) Copy these from the boot partition of to the corresponding directories of the Warp 4 partition:
 * 2) * \OS2\BOOT\OS2DASD.DMD
 * 3) * \OS2\BOOT\OS2LVM.DMD
 * 4) * \OS2\DLL\LVM.DLL
 * 5) * \OS2\SYSTEM\LVM.MSG
 * 6) * \OS2\SYSTEM\LVMH.MSG
 * 7) * \OS2\LVM.EXE
 * 8) Add to the CONFIG.SYS directly after BASEDEV=OS2DASD.DMD
 * BASEDEV=OS2LVM.DMD

CONFIG.SYS Optimisation
You can also create multiple configurations for specific optimisations, and then select the appropriate configuration at system boot by pressing ALT-F1. See how to get multiple configuration files in Warp 3 or 4.

If your only internet connection is via a modem, then you can REM (or delete) the following lines in the CONFIG.SYS in Warp 4: REM DEVICE=C:\IBMCOM\LANMSGDD.OS2 /I:C:\IBMCOM /S REM DEVICE=C:\IBMCOM\PROTMAN.OS2 /I:C:\IBMCOM REM RUN=C:\OS2\SMSTART.EXE REM CALL=C:\IBMCOM\PROTOCOL\NETBIND.EXE REM RUN=C:\IBMCOM\LANMSGEX.EXE REM DEVICE=C:\MPTN\PROTOCOL\AFOS2.SYS REM DEVICE=C:\MPTN\PROTOCOL\IFNDIS.SYS REM CALL=C:\OS2\CMD.EXE /Q /C C:\MPTN\BIN\MPTSTART.CMD >NUL REM DEVICE=C:\IBMCOM\MACS\NULLNDIS.OS2

If you don't run DOS/Windows TCP/IP programs, then you can remove the DOS TCP/IP support. The relevant lines in CONFIG.SYS are: REM DEVICE=C:\TCPIP\BIN\VDOSTCP.VDD REM DEVICE=C:\TCPIP\BIN\VDOSTCP.SYS REM RUN=C:\TCPIP\BIN\VDOSCTL.EXE

If you don't use VoiceType remove the following:
 * Remove all statements referring to VoiceType (normally they start with x:\vt) in your various path statements (don't forget your autoexec.bat)
 * LIBPATH
 * SET PATH
 * SET DPATH
 * SET HELP
 * Then delete the following lines:
 * SET SPCH_RUN=X:\VT\SPCH_RUN
 * SET SPCH_RO=X:\VT\SPCH_RO
 * SET SPCH_RW=X:\VT\SPCH_RW
 * SET SPCH_BIN=X:\VT\SPCH_BIN
 * SET SPCH_PATH=X:\VT\SPCH_RO\LANGS\%L\POOLS
 * SET SPCH_TRN=X:\VT\SPCH_DBF

Creating Maintenance Disks
The probably easiest way to create Maintenance Disks or Partitions is the use of BOOTOS2 a free IBM EWS utility.

Together with FP13 and up the creation fails due to some enlarged files. If this happens get additionally LXLite so the files will be compressed.
 * 1) Backup your original config.sys and create one with only the absolute necessary drivers in it. If you use DANIATAPI.FLT don't forget to shorten it to DANIATAP.FLT in your config.sys and also make a shortened copy in \OS2\BOOT.
 * 2) Start Bootos2 with the parameter: '2DISK LX'
 * 3) When Bootos2 asks to insert 'Target Disk 1' copy sysinstx.com from \OS2\INSTALL\BOOTDISK to the \BOS2TEMP subdirectory where BOOTOS2 is installed before proceeding. This will overwrite the old sysinstx.com from your original Warp4 Installation disks.
 * 4) Now proceed with inserting 'Target Disk 1'.
 * 5) After finishing the Maintenance Disks you may want to copy systinx.com to 'Target Disk 2' in the \OS2 subdirectory, so you will be able to install Warp4.
 * 6) Make a third Disk with some utilities on it e.g. FC/2, or DFSEE or other VIO maintenance programs. As some tools need additional DLLs make a \OS2\DLL subdirectory on this disk and copy: moncalls.dll, moucalls.dll, msg.dll, nsl.dll, quecalls.dll and viocalls.dll from your \OS2\DLL directory into.
 * 7) Don't forget to copy the backed-up original config.sys back to config.sys in your boot-drive

Enable REXX in the CONFIG.SYS
The question of whether REXX programs can be called from within the CONFIG.SYS file has been asked by a number of people. Russ Williams wrote to All: RW> Can anyone tell me what restrictions there are on running RW> REXX programs from config.sys (via "CALL=")? It doesn't RW> work for me, and the on-line help is no help. You cannot. The DLLs required to support Rexx are not loaded until Presentation Manager is loaded. If you require Rexx support earlier, look for a program call SRVREXX at a fine BBS near you.

Adding the line RUN=SRVREXX.EXE to the CONFIG.SYS will immediately initialize Rexx. You will then be able to access Rexx with or without PM being loaded.

Installing HPFS386 (from Warp Server Advanced) on Warp 4
With kindly permission by Al Savage

IBM has said that, if you own Warp Server Advanced (WSA) or another product which uses the HPFS386 file system, it's OK with them for you to also install HPFS386 on any other Warp system you have.

First Steps: To install HPFS386 on a Warp4 (non-LAN Server) box, you must have access to a WSA box that has the optional HPFS386 file system installed, for these files.

On the W4 box, create: x:\IBM386FS Copy the contents of the WSA box's x:\IBM386FS directory to the W4 box.

On the W4 box, if you do not have File & Print Services ("Peer Networking") installed, create: x:\IBMLAN

On the W4 box, create: x:\IBMLAN\NETPROG Copy these files from WSA box's x:\IBMLAN\NETPROG dir to the W4 box: CACHE386.exe CACH.msg CAC.msg

Edit CONFIG.sys: Place a 'REM' in front of IFS=E:\OS2\HPFS.IFS Add IFS=x:\IBM386FS\HPFS386.IFS /A:* /AU Add x:\IBMLAN\NETPROG; to LIBPATH Add x:\IBMLAN\NETPROG; to DPATH Add x:\IBMLAN\NETPROG; to HELP Add RUN=x:\ibmlan\netprog\cache386.exe

This last is absolutely required if you have Peer Networking installed.

If you do not add this line to your CONFIG.SYS, you will get the following error whenever you start the File and Print server: Net 3091: the CACHE386.exe is not running, The server cannot be started. You can start CACHE386.EXE manually from a command prompt. However, it is recommended that you edit the CONFIG.SYS and add the above statement.
 * Edit x:\IBM386FS\HPFS386.ini:
 * Edit "lanroot = x:\IBMLAN" to match your install drive.
 * Edit "cachesize = 32000" (or whatever the number is) to match your desires.

There are a bunch of other parameters you can reset as well. Don't, unless you think you know what you're doing.

Update HPFS386 files with WSA update IP08532 (from IBM) Running the CSF on this update won't work, because it will only update half the files. Something about it not being a "real" LS box, though CSF won't complain. It'll pretend to update HPFS386, but fails to update CACHE386.exe, so it's better to apply the update file-by-file. Use the Fastkick/DSKXTRCT method to unpack disks 4, 5, and 6 from:
 * IP08532.4dk
 * IP08532.5dk
 * IP08532.6dk

[directory structure of IP08532]

This will create a directory structure like this:

Unpack (using UNPACK.exe, in Fastkick package) these files FIX\HFS.3\BOOTSH.EX_ FIX\HFS.3\HPFS386.IF_ FIX\SRV.10\HPFS386.DL_ FIX\SRV.10\CACHE386.EX_ Move BOOTSH.exe & HPFS386.ifs to x:\ibm386fs

Move HPFS386.dll to x:\os2\dll (this file may not be needed, but this has not been tested)

Move CACHE386.exe to x:\ibmlan\netprog

If you are running HPFS386 at this time, you may have to boot without loading CACHE386.exe to replace the old copy. If you are using a process killer (or have "SET SCKILLFEATUREENABLED=ON" in your CONFIG.SYS) you can kill the running CACHE386.exe and then copy over it.

Reboot!

Create HPFS386 Boot Diskettes
Create Warp4 Boot diskettes normally, or copy the installation diskettes and update them as necessary for modern, large HDDs.

On Disk1 (ie the second diskette), edit CONFIG.SYS: Add "A:\;" to the beginning of the "PATH=", "LIBPATH=", and "DPATH=" lines.

Modify the line ifs=hpfs.ifs /c:64 to read IFS=HPFS386.IFS /AUTOCHECK:*

Modify the line protshell=sysinst1.exe to read PROTSHELL=BOOTSH.EXE CMD.EXE

On Disk2 (ie the third diskette):

Delete these files: This frees up space to add the following files.
 * HPFS.IFS
 * MARKETNG.MSG
 * FDISK.COM
 * TEDIT.HLP
 * TEDIT.EXE
 * RMVIEW.EXE

Copy these files from x:\IBM386FS to A:\:
 * BOOTSH.EXE
 * BSH.MSG
 * BSHH.MSG
 * HFS.MSG
 * HFSH.MSG
 * HPFS386.IFS
 * IBMLN386.DAT

Create directory A:\IBM386FS

Copy x:\IBM386FS\HPFS386.ini (on HDD) to A:\IBM386FS

Copy x:\IBM386FS\HPFS386.ini to A:\IBM386FS

Edit A:\IBM386FS\HPFS386.ini and make the cache size reasonable for your system.

Create a Disk 3 (ie a fourth diskette) for utilities, and copy these files to it (ideally, from a FP15+ HDD installation):
 * TEDIT.HLP
 * TEDIT.EXE
 * FDISK.COM
 * CHKDSK.COM
 * CHKDSK32.DLL
 * NLS.DLL
 * UHPFS.DLL
 * VIOCALLS.DLL
 * ZIP.EXE
 * UNZIP.EXE
 * UNZIP32.DLL
 * SHPIINST.DLL

Done! Use Disk 3 if you need to run CHKDSK or FORMAT.

Installing Iomega Parallel Drives
Installing the OS/2 Warp drivers for the Iomega Zip drive.

Try first the new BASEDEV=PPAOS2.ADD it should work with all Zip drives (100, 100+ and 250), if this doesn't work use the following steps, but keep in mind that the original Iomega driver only works with Zip 100 and there also only with older models.


 * 1) Obtain the latest Iomega ZIP drive drivers for OS/2 from Iomega
 * 2) Copy it to an empty temporary directory
 * 3) Double click OS2V234.EXE (depends on version downloaded from the ftp site), or run from OS/2 command line window. This unzips the driver zip file, and a copy of pkunzip so the drivers can be unzipped.
 * 4) Read the readme that came with the drivers.
 * 5) Run extract.bat You must finish the file decompression by running the EXTRACT.BAT file. This will create two new directories labelled DISK1 and DISK2.
 * DISK1 - contains the Iomega Tools and Win-OS/2
 * DISK2 - contains the Drivers and Utilities OAD version 2.34.
 * 1) Copy each of the disk directories to a separate floppy. Open the disk1 folder in the PM, and insert an empty, formatted floppy in the floppy drive. Select all the objects in the disk1 folder, and drag them to the floppy icon. After the copy is completed, close the disk 1 folder, remove the floppy from the floppy drive, insert a second blank floppy, open the floppy icon, open the disk2 folder, select all objects in the folder, and drag them to the floppy icon.
 * 2) Decide which driver interface(filter) you need. The following is a breakdown of adapters and drives used with the Iomega ADD Filter and with Iomega OAD.

ADD FILTER* SUPPORTED IOMEGA HARDWARE:

ADAPTERS: DRIVES PC1600 16 bit SCSI adapter: Bernoulli 230 Zip zoom accelerator card: Multidisk 150 Jaz Jet, Zip 100 SCSI, Jaz 1GB


 * The Iomega ADD filter, allows you to use non-Iomega SCSI adapters compatible with OS/2 Adapter Device Drivers (ADD). Refer to your adapter documentation or manufacturer for information on OS/2 ADD compatibility.

OAD SUPPORTED IOMEGA HARDWARE: ADAPTERS: DRIVES: PC1616 16 bit SCSI adapter Bernoulli 230 PC1600 16 bit SCSI adapter** Multidisk 150 PC800 8 bit SCSI adapter Bernoulli 90 PC2 8 bit SCSI adapter Zip 100 SCSI PC4 8 bit SCSI adapter Zip 100 Parallel port PPA-I parallel port SCSI adapter Jaz 1GB PPA-3 parallel port SCSI adapter Zip zoom SCSI accelerator card**


 * The Zip zoom accelerator card and PC1600 may conflict with Adaptec 152x adapters or Adaptec 6x60 based SCSI adapters. If you have more than one of these adapters, refer to "Solving Problems" in the OADMAN.EXE or the ADDMAN.EXE electronic manuals before installing the adapter or running Automatic Setup. If you are installing the PC1600 or the Zip zoom accelerator card for the first time, Iomega recommends these adapters be supported with the Iomega ADD Filter.

Note the parallel port version requires OAD

Don't worry about correspondence between adapters and drive type, for instance, the Zip 100 Parallel port does not require the PC4 8 bit SCSI adapter.

8. Run setupref.exe from disk2 It will inform you of the options you need to make for selecting ADD or OAD filters, and how to load the distribution floppies onto your hard disc.

9. Run the executable that matches the driver type you will need. Internal help is available from within these programs. Before you run them, you should be aware of the settings of your parallel ports if you have changed them from the defaults.

10. Iomega ADD Filter and Iomega OAD Filter - Automatic Setup N.B., to make these instructions generic, where they refer to the OAD filter, I use OAD/ADD to indicate that the selected filter name should be used.

I. Insert the Iomega Tools for OS/2 install diskette into a floppy drive.

II. Run the OS/2 Device Driver Install program. Open your OS/2 System icon, open your System Setup folder, and double click on the Device Driver Install icon.

III. Check source and destination drives. Make sure the source drive is the floppy drive used in step I. The destination drive must be your OS/2 boot drive if you want OAD to load automatically when your system boots.

IV. Install the Open Architecture Drivers (OAD or ADD) Select Install and Iomega OS/2 OAD/ADD Driver, then click on OK. The OAD/ADD files are copied automatically to the selected destination drive. When file copying is complete, remove the Install diskette from your floppy drive.

V. Exit the OS/2 Device Driver Installation window. Select EXIT, YES, and OK to exit.

VI. Preform an OS/2 SHUTDOWN and reboot the system. NOTE: While the system is rebooting, the OAD/ADD driver will display a message indicating that configuration is not yet complete. Continue with step VII. to configure the software.

VII. Run GENOAD. (or GENADD) Open an OS/2 full-screen prompt and type:

CD OAD (change to the OAD directory) GENOAD (run GENOAD)

{if the ADD filter is appropriate for you: CD ADD (change to the ADD directory) GENADD (run GENADD)}

VIII. Press when you are ready to leave the Introduction screen. The Introduction screen explains how to use GENOAD/GENADD, including navigation information and how to make selections.

IX. Select "Scan Physical Connections" from the GENOAD/GENADD Main Menu and follow the screen instructions. Supported devices found on your system are displayed in the window as the scan progresses. Make sure all your Iomega devices are listed when the scan is finished. If No Devices are Found... Refer to Solving Problems in this guide or in the electronic manual.

X. Exit the hardware scan window. Press twice and select YES at each dialogue box to save the OAD/ADD changes, save OAD/ADD as CONFIG, and overwrite the existing OAD/ADD file.

XI. Exit GENOAD. Press ESC twice and select YES to exit.

XII. Perform an OS/2 SHUTDOWN and reboot the system.

This completes Automatic Setup. For additional information on Iomega OAD refer to the electronic manual OADMAN.EXE. For additional information on Iomega ADD refer to the electronic manual ADDMAN.EXE.

Your WARP system should boot up recognizing your ZIP drive at this point.

If using the parallel port there are options to choose optimization levels for the zip drive, and choose which parallel port driver is used, if there is a desire to override the automatic parallel port support mechanism...

Linux
As Linux gets more and more common here some BASIC rules for the installation, so that you can have a trip back in times ;-)

1. Have the IBM OS/2 Boot Manager installed. Using LILO is not advised, although you can also use LILO as boot manager.

2. If you possess the Gammatech Utilities make an backup of your partition table for an easier recovery if anything went wrong. Naturally this can also be done with the Graham Utilities, but as I don't have 'em I'm not familiarized with them.

3. Make the partitions for Linux with OS/2 fdisk but DON'T format them. Linux can - like OS/2 - boot from any logical partition. And - again like in OS/2 - the boot partition has the same limitations (e.g. if no support for LBA is in your Motherboards BIOS the partition on (E)IDE Drives has to be inside the magical 528MB range). Minimum is one partition to mount the root (/) and one smaller partition for the swap drive - its size depends on your installed memory and your needs, maximum size is 128 MB with kernel 2.0x, as a 'simple' rule, make the swap partition as large as your installed memory.

4. Add Linux to your Boot Manager menu.

5. Now you can install Linux itself (see your Linux Guide for doing this). Install the Linux boot manager LILO ONLY in the partition where you have mounted the Linux root (/) e.g. /dev/hdc5.

NEVER NEVER INSTALL LILO IN THE MBR if you want to avoid a lot of troubles. (I know what I'm talking of). Naturally this is not true if you decide to use LILO as boot manager.

6. If you should have the curious idea to change your partitions AFTER the installation of Linux (e.g. you want to make out of two small ones one big, or the other way round). You'll get CERTAINLY a KERNEL PANIC whenever you try to boot Linux: In this case you have to boot from the (hope you've done it before) generated Linux rescue disk(s) and then change your mounted drives (e.g. /dev/hdc5) in Linux, install Lilo new ... (see your Linux reference for how to do this).

7. Together with the ext2.ifs you can read-write access the Linux drives from OS/2. Unfortunately newer Linux releases have changed ext2 a little bit, so ext2.ifs fails, but you can create the ext2 Partition with ext2.ifs and install Linux afterwards without formatting the drive.

8. To read-access the OS/2 HPFS formatted drives compile the Linux kernel with the HPFS-MODULE option. There are also modules for read and write access of HPFS. Thanks to John Thompson by IBM they are available at Hobbes. Actually they are available for the kernel 2.0x, 2.1x. and 2.2x.

9.JFS is also available for Linux see: http://www-124.ibm.com/jfs/. When creating a JFS volume with Linux use the -O option to make it compatible with OS/2

Moving OS/2 to another Partition
By Daniela Engert

Rule of thumb: any drive letter found at a proper place in a valid WPS object is adjusted by the WPS if the object in question is targeted to another drive letter. Of course this doesn't include data stored in the OS/2 INIs which are *not* WPS objects (some software stores pointers to themselves there).

So, the basic operation of moving an existing desktop to another drive letter is *move* the "Desktop" tree from the source drives object to the target one. If the target drive letter doesn't yet exist, create it beforehand. Then reboot to a command line window only (no WPS started!) and issue "XCOPY source: target: /H /O /T /S /E /R /V". This moves the rest of your boot drive to the new target; don't forget to adjust CONFIG.SYS. If required run "SYSINSTX target:" to make the new target drive bootable, You may need to add the new target to your favourite boot manager as well.

If you need to transplant a desktop to another location, save away \OS2\OS2.INI, \OS2\OS2SYS.INI and the full \Desktop tree including *all* extended attributes. This needs to be done without PM active! Restore the mentioned items to the new target and you're done...

Using these operations I migrated several OS/2 2.1, Warp3 and Warp 4 installations to several new drive letters (D: -> E: -> F: -> ...), changed the underlying hardware and disk drives quite often, cloned existing desktops or full installations to new target drive letters (for testing purposes), and on and on...

No magic, just basic WPS features are involved.

Netscape Settings
Netscape Communicator 4.61 for OS/2 Release Notes

A number of additional browser configuration options are available in the OS/2 version of Netscape Communicator 4.61. These options can be enabled or disabled by editing the file PREFS.JS. This file is located in your NETSCAPE\USERS\NAME directory where NETSCAPE is the directory where you installed Netscape and NAME is the name of the user you created when you installed Netscape. Note these files might be in your 4.04 directory if you installed on a machine that has 4.04.

user_pref("os2.fonts.allow_arial", true|false);

By default, Netscape Communicator for OS/2 Warp only allows the Arial font to work on pages that use the Western Encoding. This is because web pages in other languages do not display properly with Arial. This preferences allows you to turn off Arial for ALL pages or to turn on Arial for ALL pages. Note: If you want the original behavior, you must REMOVE this preference. Neither true or false emulate the original behaviour.

user_pref("os2.replace_dots", true|false);

Sometimes, when files are downloaded, Netscape changes the name incorrectly. This happens when a filename has two extensions such as test.tar.gz. This preference prevents Netscape from changing the name of any filename it is going to download. Note: default=false

user_pref("os2.use_system_codepage", true|false);

For some national language functions within Netscape, the codepage of your operating system is used. If you set this value to false, Netscape will use your default encoding to be used. This allows more functions of a translated non-Western browser to work on a Western system configured for codepage 850. Note: default=true

user_pref("os2.use_oem_charset", true|false);

The User Defined Encoding defaults to 1004. This defaults the User Defined Encoding to your system codepage. Note: default=false

user_pref("os2.emulate.windows", true|false);

This preference causes your browser as a Windows browser. You can use this when a site will not let you use it. You can test this by typing javascript:alert(navigator.appVersion) in the URL bar. Note: default=false

user_pref("os2.drag_menu", true|false);

The toolbar menus for the OS/2 version were changed to be real menus, not simulated menus as in the Windows product. This preferences causes the simulated menus to be used by default. Note: default = false

user_pref("os2.url_completion", true|false);

This preference allows you to turn off URL completion in the URL bar. Note: default = true

user_pref("browser.bidi.bidi_enabled", true|false);

Although the OS/2 browser supports Arabic and Hebrew pages, by default, Hebrew and Arabic options are only available on Arabic and Hebrew systems or when you are viewing an Arabic or Hebrew page. This preference forces the browser to think it is on an Arabic or Hebrew system. Note: If you want the original behavior, you must REMOVE this preference.

user_pref("browser.download_unknown_as_binary", true|false);

By default, Netscape downloads unknown file types as text files. This preferences forces Netscape to download unknown types as binary. Note: default = false

user_pref("os2.mail_sound", "filename");

With the OS/2 version of the browser, you can specify a WAV or MIDI file to play when you receive mail. Change filename to the fully qualified name of the file you want to play.

user_pref("mailnews.start_page.enabled", true|false);

When Messenger is started, by default it loads a Netscape home page. This preference turns that off. Note: default = true

user_pref("mailnews.start_page.url", "name_of_page");

When Messenger is started, by default it loads a Netscape home page. This preference turns that off. This allows you to change the page that is loaded.

user_pref("browser.cache.memory_cache_size",4096);

Sets the Browser internal cache size to 4096 kByte. MacIntosh users ;-) have reported that this speeds up the Navigator.

How to use new Motherboards with more than 64MB RAM
Before using this advise try to get an updated bios for your motherboard or an newer OS/2 Kernel and test if this solves the problem. If not (and only then) follow these steps.

1. Get the patchldr.zip developed by Daniela Engert from hobbes, leo or somewhere else

2. Follow this description (from patchldr.zip)

From Warp 4 on, OS/2 uses the BIOS function Int15 [AX=E801] to get the size of installed memory. In the recent past some authority sentenced this function as 'not ACPI compliant' and made the BIOS manufacturers to remove this function. WinXX is not affected by that change because it uses BIOS function Int15 [EAX=0000E820] which was added later and which is considered 'ACPI compliant'.

You may run the DOS based utility MEMTEST from this package to determine if your BIOS exhibits the defect I described. Straight DOS is preferred, but it works in an OS/2 VDM sufficiently well. If BIOS function Int15 (E801) is reported as 'not supported', and you have more than 64 MeB of memory installed, the PatchLDR utility will solve the problem.

The utility patches OS2LDR so that the query for the size of installed memory no longer uses BIOS function Int15 [AX=E801] but Int15 [EAX=0000E820]. Due to space constraints I had to remove the memory detection routines for PS/2 machines. But, as these aren't affected by the recent BIOS changes, this is a non-issue.

This patch utility is supposed to work with all fixpacks of Warp 4, the later fixpacks of Warp 3 (including derivatives), and the current version of Warp Server for e-Business. It was able to patch all of my different Warp 3/4/SeB installations successfully. You may decide to run OS/2 with the patched OS2LDR even if you don't need it right now.

According to my own tests and a lot of user reports it solves the memory size defect found with all (?) of the Athlon boards and others as well. So I consider the patch as safe.

USAGE 1) move to the root of the boot partition. 2) enter the command 'ATTRIB -R -S -H OS2LDR'. 3) enter the command 'PatchLDR'.

If step 3 fails, an error message will be displayed. If it succeeds, the old OS2LDR is copied to OS2LDR.bak, and a new, patched OS2LDR is created.

4) enter the command 'ATTRIB +R +S +H OS2LDR'.

From the next reboot on, the new memory size detection code is in effect.

Please remember: after installing a fixpack the OS2LDR patch needs to be applied again because it will be replaced by a non-patched version from the fixpack. If the fixpack installer asks you if it should replace the patched version of OS2LDR with the one from the fixpack distribution, then reply 'YES'! Failing that may render OS/2 unbootable because OS2LDR and OS2KRNL need to match.

OS/2 Traps
TRAP 0000 - DIVIDE ERROR: A program attempted to divide a number by zero. Contact software support.

TRAP 0001 - DEBUG EXCEPTION: Contact software support.

TRAP 0002 - HARDWARE/MEMORY ERROR: Memory or hardware failure in the system. Contact hardware support.

TRAP 0003 - BREAKPOINT: This is a special instruction (INT 3) used in debugging" software, which was left in the code either accidentally or by design. Contact software support.

TRAP 0004 - OVERFLOW: An overflow occurred during an arithmetic operation. Contact software support.

TRAP 0005 - BOUND RANGE EXCEEDED: A Bound instruction exceeded the specified limits. Contact software support.

TRAP 0006 - INVALID OPCODE: The processor tried to execute an unreserved invalid opcode. Contact software support.

TRAP 0007 - COPROCESSOR NOT AVAILABLE: If coprocessor diagnostic tests run error-free, contact software support.

TRAP 0008 - DOUBLE FAULT: The processor detected an exception while processing another exception. It could be caused by either hardware or software. If TRAP 0002 also is being experienced, contact hardware support.

TRAP 0009 - COPROCESSOR OVERRUN: The middle portion of a COPROCESSOR operand is protected or not present. Contact software support.

TRAP 000A - INVALID TASK STATE SEGMENT: A task switch to an invalid task-switch segment was attempted. Contact software support.

TRAP 000B - SEGMENT NOT PRESENT: The referenced segment is not present. Contact software support.

TRAP 000C - STACK FAULT: The referenced page is not present in memory, or the procedure referencing the page does not have enough privilege to access the page. Contact software support.

TRAP 000D - GENERAL PROTECTION EXCEPTION: All protection violations that do not cause another exception cause a TRAP 000D. Contact software support.

TRAP 000E - PAGE FAULT: The referenced page is not present in memory, or the procedure referencing the page does not have enough privilege to access the page. Contact software support.

TRAP 000F - RESERVED BY INTEL.

TRAP 0010 - COPROCESSOR ERROR: The processor detected an error from the coprocessor. This could be caused by hardware or software.

OS/2 Optimisation
For those of you new to OS/2. Congratulations you are now about to experience slick, reliable computing, not to be found in most other operating systems.

This document is intended for both novice and experienced users. It is hoped that it will lead you to a better understanding of your system, and more enjoyable computing. It is not intended to be comprehensive, but rather as a starting point, and that you will find other information from various sources, some mentioned here.

The best way to optimise your system is by helping OS/2:
 * 1) Install as much memory as you can afford, OS/2 will use it if it is there, so you won't be wasting your money. Typically 32 Meg is a good starting point.
 * 2) Use only HPFS (High Performance File System) partitions
 * 3) Use OS/2 without DOS and Windows sessions (you also block those nasty little things called virus)
 * 4) Don't use VoiceType if you don't need it.
 * 5) Use small apps (like Papyrus) and not those RAM-Hogs like StarOffice
 * 6) Use native apps (not Java, Windows, Mirror ports like Word-perfect for OS/2)
 * 7) Delete the OpenDoc environment by using 'selective-uninstall', as OpenDoc is deplorably death.
 * 8) Use as few partitions as possible. OS/2 checks all partitions during boot-up, so having fewer partitions speeds boot-time.
 * 9) try and avoid program hopping, that is jumping from one application to the next, as this will avoid swapper activity (unless you have lots of RAM)

BTW. when you compare Windows and OS/2 on the same system, remember that Windows can only boot from the first partition, the one which is on most drives also the fastest! Using removable media together with OS/2 and newer Fixpaks slows OS/2 boot-up significantly (but the Drivers by Daniela Engert: DANIS506.ADD and DANIATAPI.FLT boost the speed for EIDE drives). As a trade off (compared to Windows, all versions) you get dynamically assigned drive letters, a feature that saves you from the drive-letter chaos in Windows whenever you change a partition, drive etc.

Partition Types
The partition type number (hex id) are as follows:
 * 00 Empty
 * 01 FAT12 (supported by OS/2)
 * 02 XENIX_1 root
 * 03 XENIX_2 usr
 * 04 FAT16 <32MB (supported by OS/2)
 * 05 EXTENDED, Supports at most 8 GB disks:
 * with type 05 DOS/Windows will not use the extended BIOS call, even if it is available. See type 0F below.
 * 06 FAT16 >32MB (supported by OS/2)
 * Partitions, or at least the FAT16 filesystems created on them, are at most 2 GB for DOS and Windows 95/98 (at most 65536 clusters, each at most 32 kB). Windows NT can create up to 4 GB FAT16 partitions (using 64 kB clusters), but these cause problems for DOS and Windows 95/98.
 * Note that VFAT is 16-bit FAT with long filenames; FAT32 is a different filesystem.
 * 07 IFS, e.g. HPFS, HPFS386 (supported by OS/2) or NTFS, or Advanced Unix, or QNX2.x pre-1988
 * IFS = Installable File System. OS/2 will only look at partitions with ID 7 for any installed IFS. That's why the EXT2.IFS packet includes a "Linux partition filter" device driver to fool OS/2 into thinking Linux partitions have ID 07.
 * 08 OS/2 (v1.0-1.3 only), or AIX boot partition, or split drive, or Commodore DOS, or DELL partition spanning multiple drives, or QNX 1.x and 2.x ("qny")
 * 09 AIX data partition, or Coherent filesystem, or QNX 1.x and 2.x ("qnz")
 * 0A BOOTMANAGER (supported by OS/2), or Coherent swap partition, or OPUS (Open Parallel Unisys Server).
 * 0B WIN95 OSR2 32-bit FAT Partitions up to 2047GB. Supported by DANIDASD.DMD
 * 0C WIN95 OSR2 32-bit FAT, LBA-mapped Extended-INT13 equivalent of 0B. Supported by DANIDASD.DMD
 * 0E WIN95: DOS 16-bit FAT, LBA-mapped
 * 0F WIN95: Extended partition, LBA-mapped, also used by PQMAGIC 4.0
 * Windows 95 uses 0E and 0F as the extended-INT13 equivalents of 06 and 05. This causes problems and possible data loss with LBA and INT13 extensions. (Especially when going back and forth between MS-DOS and Windows 95, strange things may happen with a type 0E or 0F partition.) OS/2 and even Windows NT does not recognize the four W95 types 0B, 0C, 0E, 0F, but there is a FAT32.IFS by Henk Kelder.
 * According to the uncountable requests for help in different OS/2 newsgroups the use of 0E and 0F is not recommended at all.
 * Supported by DANIDASD.DMD
 * ATTENTION: using PQMAGIC 4.0 also results in heavily errors.
 * 10 Hidden partition (bits OR'd with partition type)
 * 11 Hidden DOS 12-bit FAT
 * When it boots a DOS partition, OS/2 Boot Manager will hide all primary DOS partitions except the one that is booted, by changing its ID: 01,04,06 becomes 11,14,16. Also 07 becomes 17.
 * 12 COMPAQ config partition
 * To use a COMPAQ PC with OS/2 save the config partition on disks and then delete this partition (best is to delete all and re-partition the hard disk according to your needs).
 * ATTENTION: Seems not to work with all COMPAQ's, my now outdated CONTURA 386/25, and also the AERO 486/33 worked fine.
 * 14 Hidden DOS 16-bit FAT <32M
 * 16 Hidden DOS 16-bit FAT >=32M
 * 17 Hidden IFS (e.g., HPFS)
 * 18 AST Windows swapfile ('Zero Volt Suspend Partition' or 'SmartSleep Partition', 2MB+memory size).
 * 1b Hidden WIN95 OSR2 32-bit FAT
 * 1c Hidden WIN95 OSR2 32-bit FAT, LBA-mapped
 * 1e Hidden FAT95
 * 21 Reserved
 * 23 Reserved
 * 24 NEC DOS 3.x
 * 26 Reserved
 * 31 Reserved
 * 33 Reserved
 * 34 Reserved
 * 35 JFS (supported by OS/2 Server for e-business)
 * 36 Reserved
 * 38 THEOS ver 3.2 2gb partition
 * 39 THEOS ver 4 spanned partition
 * 3a THEOS ver 4 4gb partition
 * 3b THEOS ver 4 extended partition
 * 3c PartitionMagic recovery partition
 * 40 VENIX 80286
 * 41 LINUX/MINIX (sharing disk with DR DOS), or Personal RISC Boot, or PPC PReP (Power PC Reference Platform) Boot
 * 42 LINUX swap (sharing disk with DR DOS),or SFS (Secure Filesystem)
 * 43 LINUX native (sharing disk with DR DOS)
 * 4d QNX4.x
 * 4e QNX4.x 2nd part
 * 4f QNX4.x 3rd part, or Oberon partition
 * 50 OnTrack Disk Manager (older versions) RO
 * 51 OnTrack Disk Manager RW (DM6 Aux1), or NOVELL
 * 52 CP/M, or MICROPORT SysV/AT
 * 53 Disk Manager 6.0 Aux3
 * 54 Disk Manager 6.0 Dynamic Drive Overlay
 * 55 EZ-Drive
 * 56 Golden Bow VFeature Partitioned Volume.
 * 5c Priam EDisk
 * 61 SPEEDSTOR
 * 63 UNIX System V (SCO, ISC Unix, UnixWare, ...), Mach, GNU Hurd
 * 64 PC-ARMOUR protected partition, or NOVELL Netware 2.xx
 * 65 NOVELL Netware 3.xx or 4.xx
 * 67 NOVELL
 * 68 NOVELL
 * 69 NOVELL
 * 70 DiskSecure Multi-Boot
 * 71 Reserved
 * 73 Reserved
 * 74 Reserved
 * 75 IBM PC/IX
 * 76 Reserved
 * 80 MINIX until 1.4a
 * 81 LINUX/MINIX since 1.4b, or MITAC disk Manager
 * 82 LINUX SWAP or SOLARIS UFS, or PRIME
 * 83 LINUX or NT Stripe and Mirror Set
 * 84 OS/2 hidden C: drive, OS/2-renumbered type 04 partition. or Hibernation partition
 * 85 LINUX extended partition
 * 86 NTFS volume set
 * 87 NTFS volume set
 * 93 Amoeba
 * 94 Amoeba bad block table
 * 99 DCE376 logical drive
 * A0 IBM ThinkPad hibernation partition, or Phoenix NoteBIOS Power Management "Save-to-Disk" partition
 * A1 Reserved. Also used as "Save-to-Disk" on a NEC 6000H
 * A3 Reserved
 * A4 Reserved
 * A5 BSD/386, 386BSD, NetBSD, FreeBSD
 * A6 OpenBSD
 * A7 NEXTSTEP
 * AA Olivetti Fat 12 1.44Mb Service Partition
 * A9 NetBSD
 * B1 Reserved
 * B3 Reserved
 * B4 Reserved
 * B6 Reserved
 * B7 BSDI filesystem
 * B8 BSDI swap partition
 * C0 CTOS
 * C1 DRDOS/secured (FAT-12)
 * C4 DRDOS/secured (FAT-16, < 32M)
 * C6 DRDOS/secured (FAT-16, >= 32M), or Windows NT corrupted FAT16 volume/stripe set
 * C7 Windows NT corrupted NTFS volume/stripe set, or SYRINX boot
 * D8 CP/M-86
 * DB Digital Research CP/M, Concurrent CP/M, Concurrent DOS or CTOS (Convergent Technologies OS -Unisys)
 * E1 DOS access or SpeedStor 12-bit FAT extended partition
 * E3 DOS R/O or SpeedStor
 * E4 SpeedStor 16-bit FAT extended partition < 1024 cyl.
 * E5 Reserved
 * E6 Reserved
 * EB BeOS Filesystem
 * F1 SpeedStor
 * F2 DOS 3.3+ secondary partition
 * F3 Reserved
 * F4 SpeedStor large partition
 * F6 Reserved
 * FF BBT, Xenix Bad Block Table
 * FE PS2S PS/2 IML System Partition, or SpeedStor > 1024 cyl., or LANstep

ATTENTION: If you install different OS (e.g. Solaris and Linux, or OS/2 and NT) you can run into serious troubles whenever the id's aren't unique.

Together with a disk-tool like e.g. the FREE DFSee by Jan van Wijk, the fdisk out of LINUX, or the Norton Diskdoctor for Dos and naturally the Gammatech and the Graham utilities (both for OS/2) there are many useful options for recovering and not so useful for DESTROYING a partition table. So be careful whenever editing a partition table. It is wise to get accommodated with these tools JUST BEFORE an accident happens, cause when something went wrong you're to much excited.

Recover
In OS/2 Warp, IBM provides an archive feature which can be activated whenever you need it. It will save ON THE NEXT SYSTEM BOOT, a copy of all the necessary system files to restore to a previous configuration.

To recall a saved configuration, press "ALT-F1" when you see "OS/2" in the very upper left hand corner of your boot-screen screen. On fast computers it is not visible for long, so pay attention.

A blue screen will appear with a list of choices, and instructions, at the bottom of which will be listed the various archives available. Select the appropriate archive, and the system will be restored to this configuration.

For managing your archives there is the FREE tool warco13.zip, developed by Stefan Milcke (Stefan.Milcke@t-online.de)

Creating a System Configuration Archive
During the boot process you should see a small status window confirming the archive is being created.
 * 1) Click on an empty area of your desktop
 * 2) Click on "Properties"
 * 3) Click on "Archive"
 * 4) Click on "create archive on...."
 * 5) Edit the location if you desire
 * 6) Close the properties window
 * 7) Perform a normal shutdown

The system will create an archive on every boot, which will slow the boot process down, and create new archives. I normally only create an archive when I have made changes to my system and after the boot disable archive creation. Also the total number of archives is limited to 5, then OS2 will overwrite the oldest archive.

With this feature activated, you can simply press Alt+F1 at boot and be presented with a menu which will allow you to boot with an alternate (backup) config.sys file. See your user documentation for details.

WarpCenter Backup
(from: http://users.pandora.be/luc.vanbogaert/tips/system.html)

You can backup the contents and configuration of the Warp 4 WarpCenter, by keeping a backup of the following files in the C:\OS2\DLL directory:
 * SCENTER.CFG
 * DOCKn.CFG (where n is 0 to 15, for the 16 WarpCenter trays)

An easy way to make sure you always have a recent backup is to use the Warp 4 archive feature. Archive backs up all files that are listed in the C:\OS2\ARCHIVES\OS2.KEY file. So, all you have to do is add the above listed WarpCenter configuration files in this file, as: KEYFILE:OS2.INI KEYFILE:OS2SYS.INI KEYFILE:C:\CONFIG.SYS KEYFILE:C:\STARTUP.CMD KEYFILE:C:\AUTOEXEC.BAT KEYFILE:C:\OS2INIT.CMD KEYFILE:C:\OS2\DLL\SCENTER.CFG KEYFILE:C:\OS2\DLL\DOCK0.CFG KEYFILE:C:\OS2\DLL\DOCK1.CFG KEYFILE:C:\OS2\DLL\DOCK2.CFG ... Finally, make sure the Archive functionality is enabled (check the Archives tab in the Desktop's Settings notebook).

Archiving Your Network

Removing Autostarts
There is a clean way of removing the IBM Registration program from your system (unless you admire dancing elephants). This will totally uninstall the "art" directory and all components relating to registration. Some applications (like StarOffice, Smartsuite, AmiPro) install some 'reminders' or 'speeders' in the autostart folder remove or delete them, they are normally not needed.
 * 1) Open folder "OS/2 SYSTEM" on your desktop
 * 2) Open "DRIVES"
 * 3) Open "Drive C"
 * 4) Open "OS/2"
 * 5) Open "Install"
 * 6) Open "Installed Features"
 * 7) Open "Installed Object - Inventory"
 * 8) Click the checkbox next to "art"
 * 9) Click on "uninstall"
 * 10) Click "art" in the next box that opens
 * 11) Click on "uninstall"

Selective Boot
The ALTF1 boot process begins by displaying a selection screen which is constructed from three files to be found in x:\OS2\BOOT

ALTF1TOP.SCR RECOVERY CHOICES

Select the system configuration file to be used, or enter the option corresponding to the archive desired.

ESC - Continue the boot process using \CONFIG.SYS without changes F2 - Go to command line, (no files replaced, use original CONFIG.SYS) F3 - Reset primary video display to VGA and reboot F4 - Restart the system from the Maintenance Desktop (Selective Install) F5 - Enable full hardware detection F6 - Disable hardware detection

Choosing an archive from the list below replaces your current CONFIG.SYS, Desktop directory, and INI files with older versions. These older versions might be different from your current files. Your current files are saved in \OS2\ARCHIVES\CURRENT. ALTF1MID.SCR 1) Archive created 5-6-1999 7:09:58AM 0) Original archive from INSTALL created 5-5-1999 8:03:16AM ALTF1BOT.SCR

ALTF1BOT.SCR contains a blank line to overwrite any screen image occupying the last line of the screen

These files are text files, you can edit them, but remember that the text must fit within the original number of lines. Otherwise the image will be more than the 25 line screen size and cause scrolling

STEP 1

MAKE BACKUPS OF ALL FILES TO BE MODIFIED

According to IBM the following characters are reserved and cannot be used as selections in your menu: Warp3 C M V X 1 2 3 Warp4 C M V X 1 2 3 4 5 Decide what you need and modify ALTF1TOP.SCR (18 Lines, including 1 empty line at top) to suite your needs, as an example next line is line 1 ---vvvvvvvv---

ACME CORP SYSTEM RECOVERY CHOICES

Select one of the following

ESC - Continue the boot process using \CONFIG.SYS without changes F3 - Reset primary video display to VGA and reboot F5 - Enable full hardware detection F6 - Disable hardware detection D - Enable DOS/Windows P - Pure OS/2 (no DOS/Windows support) N - DISABLE Network

CAUTION choosing an archive from the list below reconfigures your entire system, think before you act.... or press ESC

Your current files are saved in \OS2\ARCHIVES\CURRENT.

line above is line 18 -^^^^^^^^-- STEP 2

When a selection is made ALTF1.CMD is called with the keystroke passed as a parameter. Edit this file to reflect your selection screen. Note x: refers to the boot drive

ALTF1.CMD @ECHO OFF REM REM Make sure at least one parameter was passed REM IF @%1==@ goto end REM rem F3 passed a "V" REM If a V or v is passed, call SETVGA REM IF V==%1 GOTO setvga IF v==%1 GOTO setvga REM rem F4 passed an "M" REM If a M or m is passed, call SETVGA REM IF M==%1 GOTO setvga IF m==%1 GOTO setvg a REM REM Check our modified selections REM

rem new lines added here vvvvvv

IF D==%1 GOTO setd IF d==%1 GOTO setd IF P==%1 GOTO setp IF p==%1 GOTO setp IF N==%1 GOTO setn IF n==%1 GOTO setn GOTO skip


 * setd

REM REM Set up DOS/WINDOZE REM copy x:\os2\boot\config.d x:\config.sys

GOTO end


 * setp

REM REM Set up pure OS/2 REM copy x:\os2\boot\config.p x:\config.sys

GOTO end


 * setn

REM REM Disable Network REM copy x:\os2\boot\config.n x:\config.sys

GOTO end


 * skip

rem original lines begin here vvvvvvvv

arcrecov %1

GOTO end


 * setvga

setvga


 * end

STEP 3

Create corresponding config(x).sys files in the x:\OS2\BOOT directory for the command file to be able to copy

StarOffice HTML Association
Delete the StarWriterHtmlFile Class.

You can do this either by using the FREE VClassed by Daniele Vistalli (dvistalli@tin.it), or by using this REXX script by Winifried Tilanus. /* DELCLASS.CMD This REXXprogram destroys classes */ Call RxFuncAdd 'SysLoadFuncs', 'RexxUtil', 'SysLoadFuncs' Call SysLoadFuncs class = "StarWriterHtmlFile"

rc = SysDeregisterObjectClass (class) if rc = 1 then do say "Class "class" destroyed OK" end else do say "Class "class" destroy failed" end

SWAPPER OPTIMISATION
1) swapper size

On system boot the swapper.dat file is initialised, so a contiguous block of hard drive space will be created, but only as large as you have specified. So if your size is small you will experience swapper fragmentation as it is used

Your swap file will grow (in 1MB increments), but it also shrinks when one of two conditions are met.

a) when the amount of free space in the swap file is greater than 1.5MB, the swap file will be compressed during system idle time. (It will not shrink if there is a constant "hit" on the drive by a program such as a swap file monitor.)

b) during the compression of new entries, free space is moved to the end of the swap file. When this free space at the end of the swap file exceeds 1MB, the swap file will be shrunk.

OS/2 tries to maintain the file size the same as specified in config.sys by moving free space to the end of file, and then re-sizing. So if you specify a small file size, this mechanism will consume valuable CPU time. The usual way to determine YOUR swapper size is to simply use your computer as normal and occasionally check the size of swapper.dat. Then set this value (plus a couple of meg) as your start-up size.

2) swapper location

a) Consider dedicating a separate partition for the swap file. This helps avoid fragmentation of the swap file, because other files will not be added or deleted from the dedicated partition.

b) If you have both FAT and HPFS partitions, put the swap file on the HPFS partition to take advantage of the better performance of HPFS, and less fragmentation

c) If you have a system with two hard disk controllers, put the swap file on a disk managed by the LEAST used controller.

d) Keep your swap file on the MOST used partition of the LEAST used hard drive.

<<=Warning=>> NEVER put your swap file on a networked drive.

SYNATTACK
Here is a tip from IBM's TCP/IP document site

For TCP/IP 4.0 - apply the latest MPTS/TCP/IP update. This will give you a new program -SYNDEF.EXE.

This works as follows: SYNDEF.EXE ON (enables SYN defences) SYNDEF.EXE OFF (disables SYN defences) SYNDEF.EXE -? (displays SYNDEF syntax)

For TCP/IP 4.x - The ability to protect against this type of attack is built in to TCP/IP 4.x. To enable this protection:

1. To GET the current status of the SYNATTACK parameter in the INETCFG.INI file, go to an OS/2 command line and type:

INETCFG -G SYNATTACK, then press Enter.

2. By default, SYNATTACK is set to 0, which means OFF.

3. To SET the SYNATTACK parameter in the INETCFG.INI file to an ON state, (1), type the following at an OS/2 command line:

INETCFG -S SYNATTACK 1

4. This new setting in TCP/IP 4.x will now prevent the SYNATTACK from occurring.

Windows 2000
Since Release Candidate 3 Windows 2000 destroys the OS/2 Boot Manager every time it is booted.

One solution could be to toggle with an disk editor (e.g. from the Gammatech Utilities) a byte in the first sector of the Boot Manager Partition OFFSET 0Eh (decimal 14), from 0x01 to 0x2d. This reserves an greater amount of reserved Sectors, so Windows 2000 changes only unassigned Sectors not needed by the Boot Manager. DFSee 3.32 can do this for your without the need to poke around with an disk editor.

Or call the Microsoft Support and ask for the Hotfix Q265003, it will be included in Service Pack 2 for Windows 2000.

Or use this tip from - Daniela Engert from VOICE 8/2000

"Maybe you are interested in patching FP13 FDISK so that it writes out a modified Boot Manager which will not be affected by Win2K":

For FP13 FDISK use this script file (the Boot Manager sector image is at file offset 13404h)

FILE FDISK.COM VER 13411 04 CHA 13411 00 VER 13412 01 CHA 13412 20 VER 13414 02 CHA 13414 00 VER 13416 02 CHA 13416 00 VER 1341A 0C CHA 1341A 00 VER 1343A 46415420202020 CHA 1343A 424F4F544D4752 and run "PATCH FDISK.PAT /A" from the x:\OS2 directory. Then run FDISK and recreate the Bootmanager. Other FDISK versions may have the sector image at another offset.
 * FDISK.PAT

ServicePak 4 adds those fixes:
 * 309344 File Appears to Be Deleted Although You Do Not Have Permissions on the OS/2 Warp4-Based Server
 * 323582 Net3101 Error on OS/2 Server Because of SessionSetup SMB

Windows NT 4.0
By using a filter driver the NTFS partition can be hidden by inserting BASEDEV=EXT2FLT.FLT E.g. if you have one disk, the OS/2 Boot Manager installed and NT is on the first partition the correct options are /A /W /M 1


 * TIP:Windows NT 4.0 can use HPFS partitions if you have the pinball.sys out of NT 3.51 and the utility hpfs_nt4.zip by Chris Behnken.
 * ATTENTION:pinball.sys can only operate with disks or partitions up to 4GByte.


 * TIP:There is also an NTFS.IFS by Daniel Steiner and a VFAT.IFS with NTFS read-support. But as some users reported problems be very careful when using it. The best would be to make a complete backup of your installation.

Windows XP
A workaround for XP clients suddenly being unable to delete files on OS/2 server shares after installing SP1.

Replace mrxsmb.sys in %systemroot%\system32\drivers with the one from the initial release. You will have to place it in %systemroot%\system32\dllcache as well to keep it from being overwritten by system restore. Roaming profiles still do not work.

On workstations with Microsoft Windows XP Service Pack 1 the following problems (see below) can occur in conjunction with file resources on OS/2 servers.

These problems are known to Microsoft and will be fixed with Windows XP Service Pack 2. In the meantime the necessary patches can be requested from Microsoft directly.


 * Problem:Files created on OS/2 servers cannot be deleted.
 * Solution:
 * 1) Install patch (MS Hotfix) Q325929
 * 2) This registry parameter needs to be set: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\lanmanworkstation\parameters\ "EnableDownLevelLogOff"=dword:00000001
 * 3) Install patch (MS Hotfix) Q813586

Computer Configuration\Administrative Templates\System\User Profiles\ "Do not check for user ownership of Roaming Profile folders"
 * Problem:Roaming Profiles stored on OS/2 servers can no longer be loaded successfully.
 * Solution:
 * 1) Activate this Group Policy: