OS/2 Warp Connect

This page Copyright (c) 2003,2004 P.R. Nienhuis, Amsterdam
Last updated 16 December 2005

(An old version of this document, pertaining to OS/2 Warp 3 NL on the original 4.1 GB hard disk, is here.)


Be warned: this page is still under construction!



    (Intermezzo: UpdCD)
   Step 1: Temporary boot partition
   Step 2: Finishing all HPFS and FAT partitions & Boot Manager
   Step 3: OS/2 maintenance partition
   Step 4: Warp Connect itself


Applying FixPaks

Gradd Video

Network components installation
    Updating the TCP/IP stack and utilities
    Optional: NFS

Other interesting software
    Basic OS/2 utilities
    OpenWatcom C++ & F77
    IBM Developer Driver kit Online
    X-Windows server PMX
    X-Windows suite XFree86


Why would one stick with such an old OS?

Well, consider:
Stability: I used OS/2 years ago for assembly programming for DOS programs; forgetting a POP instruction then would only lead to a crashed DOS window. Opening a new one and continuing programming would take just 5 seconds. Trying this under pure DOS and even Win95 DOS-boxes would sooner or later induce terrible lock-ups, implying power-offs, lengthy boot sequences and often time-devouring scandisk sessions.
Speed: My Libby takes 3-4 minutes to boot any Windows (no not a freshly installed Windows which is indeed quickly, but a "real world" one slowed down by indispensable virus scanners, silently introduced program stubs, etc. etc.). Booting OS/2 Warp Connect needs a mere 45 seconds for much the same functionality and better stability.
Fun: OS/2 is by no means easy to install (which must have been one of the reasons it never made it as the common operating system). However, for a hobbyist such a stumbling block is what it all makes worthwile, isn't it?
Price: Warp 3 and Warp Connect are regularly featured on E-Bay and here in the Netherlands on Marktplaats.nl for just 10-30 dollars or Euros. While support and development for Windows 95 (which came out later than Warp 3) has been completely dropped several years ago, Warp 3 can still be fully updated to current standards for the price of just download time (in case of cable or DSL no extra costs) or the price of a WUK (Warp Update Kit - glance the UpdCD links below). IBM may not support Warp anymore (for free, that is), but they haven't removed updates and fixpaks for Warp 3 - on their sites you can still find drivers and update kits even for OS/2 2.0 . Many updates and drivers for Warp 4 or ECS (OS/2's commercial successor) turn out to work under Warp 3, too.

Nevertheless, I think OS/2 critics are probably somewhat right: as far as user base is concerned, OS/2 may not be dead but has turned largely into a niche and/or hobbyist's OS; Warp 3 is probably quite dead. But then again, I know people who still run their old Atari ... and Warp Connect can still be used for almost all daily work save demanding stuff like video editing etc. In case you really want to try to run Warp 3 (Connect), and considering that IBM will drop OS/2 support soon and Warp 3 probably even sooner, it is wise to glance through this page and download all files you need a.s.a.p., before they disappear completely from the web.


OS/2 is clearly the most difficult OS to install on a Libretto, mostly because of the lack of an OS/2 floppy driver for the PCMCIA Flashbuster floppy. Therefore, at least a DOS boot floppy including some DOS file and disk utilities is needed.
Furthermore, some fiddling around with DOS DEBUG.EXE is needed - be very careful when you type in the DEBUG commands!

Probably OS/2 has to be installed as the first OS, as it is the most demanding as regards proper partition table setup. Both Windows and Linux can be installed easily in a later stage.

Some issues adressed in the sequence proposed below are:

OS/2 installation proceeds roughly as follows:


This comprises mainly downloading a number of needed utilities and updates, setting up various file trees (directory structures) and establishing a connection between the Libretto and another PC and/or back-up media.
My description assumes you just got a Libretto and its associated restore Windows CD-ROMs and -floppies. Be aware that you do need a DOS boot floppy to make the first partition, as there is no OS/2 driver for the PCMCIA-floppy drive.
Would you have another PC running OS/2, then you could temporarily transfer the Libby's hard disk to that desktop, partition it from there and copy the OS/2 installation files (possibly UpdCD burn directory, see below) to it.

Download BOOTOS2, DANIS506.ADD, DANIATAPI.FLT, GT2GBW3.ZIP and DSKXTRCT.EXE (all on Hobbes); LOADDSKF (DSKXTRCT *is* more efficient, but having LOADDSKF doesn't hurt); IDEDASD.EXE (look here and search for IDEDASD.EXE or Greater than 8.4 GB Hardfile support in de "OS/2 Component Updates" section); fixpak 40 for Warp 3 & Service tool v. 1.43 (look here); GRADD video drivers (latest version = a.097) (look here); and (in case of Warp Connect) the fixpaks for MPTS, TCP/IP, ASKPSP, IBM Peer and LAN Requester (also here, but just some levels higher in the ftp directory tree; have a look at Warpupdates to see which ones you need). It may be handy to download a PCMCIA package update too from here (choose your language, e.g. PCCARDEN.EXE for English). Expand all archives in separate subdirectories. For each fixpak, LOADDSKF all fixpak floppy images to floppy (or RAM disk) and from there into a proper directory structure per fixpak, or invoke DSKXTRCT to do that in one fell swoop.

  1. (If you only have Warp3 floppies: make an installation tree using LOADDSKF; read the README.CID file on the Warp boot floppies how to do this, it is much similar to the fixpak directory trees but you might include your Windows 3.1 floppies as well for installation of Win-OS/2.)
  2. (If the Libretto is your only PC, backup all the just made directory trees to CD-ROM, ZIP-drive or whatever.)

  3. Make a DOS (yes, DOS) boot floppy (format it with /S) and add CHKDSK, FDISK, DEBUG, FORMAT, DELTREE, MOVE, XCOPY and probably XCOPY32 (i.e., the Windows versions). Optionally include device drivers for a ZIP-drive, a PCMCIA CD-ROM drive, a network card or software to communicate/transfer files through a serial or parallel port with another PC.

(Intermezzo: UpdCD)
I've been playing around with Updcd recently, and I am quite impressed. It allows one to make a Warp install CD in which all updates and fixpaks have been integrated, much like the slipstreaming of MS-Windows servicepacks, but in this case much better:
Updcd's creator Zsolt Kádár also added tools for integration of non-standard-but-very-useful additions like Netscape 4.61, Feature Installer, Warpin, EMX, Freetype/2 ..... you-name-it.
And best of all, it works for Warp 3, too. Not without glitches, but they can easily be overcome. You do need another running OS/2 system (Warp 3 or 4), but if you have, you can skip all steps below referring to fixpaks and gt3gbw.zip. All such things are incorporated into the first installation.
You do not need to make a real CD, it is sufficient to build the installation tree (\os2image) up-to-date, and preferrably also all network installation stuff.
To get it installed on the Libretto, the updated \OS2IMAGE directory must be copied to the harddisk somewhere, in the second half of step 3, and the contents of the diskette images (in \DISKIMGS) too, save the .BIO files and SCSI drivers (mostly .ADD); adapt CONFIG.SYS to exclude the CONINST and I2OXPORT stuff and other unneeded things. Next start up from the maintenance partition and enter the commands shown below in step 4. A peculiarity is that you cannot get reboots the first time(s), just hit F3 and/or press OK, then Ctrl-Alt-Del.
Perhaps a CID-like installation may be better suited for the Librettos; in that case the directory \CID excluding its subdir IMG must be copied to harddisk, too. In this IMG directory (105 MB) the rest of the Warp Connect stuff is included, but it might not fit on your temporary partition.

Installation step 1: Temporary OS/2 boot partition

This step merely comprises setting up a hard disk partition from which OS/2 can boot.
The essential part of the trick is cooking up a proper OS/2 boot sector. This can be done by pasting the 19 bytes of partition layout info, starting at offset 0bh in the MS-DOS boot sector after formatting, into an OS/2 boot sector grabbed from an OS/2 boot floppy (e.g., the installation floppy) and writing that into the new OS/2 boot partition.
Below I have outlined how I partitioned my 15 own GB disk; of course you can put in your own additions / changes / amendments to fit your needs. It is just the procedure which matters.
Update 11/12/03: Verified & checked on new 60 GB hard disk.

Boot from the DOS floppy and using (MS-) FDISK, and wipe out *all* existing partitions (yep).

  1. Make a primary partition of -say- 100 MB; use DOS/Windows FDISK for this. Be sure to specify NO large disk support, otherwise you won't get FAT16 but rather FAT32 which OS/2 can't read yet! Leave the partition empty. It will undoubtedly be at the start of the hard disk, and it will be called C: (Fig. 1). Do not forget to set it as active (= default boot) partition!

  2. Figure 1

  3. Format the partition (FAT16, already selected with FDISK, see above) using DOS/Windows FORMAT.

  4. Use DOS/Windows DEBUG.exe to copy a boot sector of an OS/2 boot floppy (floppy #0) to this partition. Type: (Mind you, in the lines below, everything after <Enter> (which means: hit the Enter key) is a comment and must not be typed in) :
    CD C:\ <Enter>
    C: <Enter>
    Debug <Enter> Assuming DOS debug has been copied to the C:-partition
    L cs:100 $ 00 1 <Enter> where $ is the number of the OS/2 partition. 0=A, 1=B etc. As you copy from A, set $ to 0
    r cx <Enter>
    200 <Enter>
    n c:\os2boot.br <Enter>
    w <Enter>
    q <Enter>

  5. Using DOS/Windows DEBUG, merge the partitions boot sector (the partition lay-out, the BPB) with the OS/2 boot sector (boot code).
    CD C:\ <Enter>
    C: <Enter>
    Debug <Enter>
    L cs:100 # 00 1 <Enter> (load first (=boot) sector; # refers to the partition number, 0=A, 1=B, etc, so set # to 2)
    m cs:0110 L27 cs:0600 <Enter> (save the needed partition info / BPB (media/sectors/heads etc) in memory)
    n os2boot.br <Enter>(OS/2 boot sector file)
    r cx <Enter> (read only first 512 bytes of the file)
    200 <Enter> (Debug echoes a colon; 200 hex = 512 decimal)
    L <Enter> (Load the OS/2 boot sector which originated from the other computer)
    m cs:0600 L27 cs:0110 <Enter> (Fudge BPB/ sector/media/heads/absolute sector stuff of final partition in)
    w cs:100 # 00 1 <Enter> (write it back to disk - # is again partition number, probably 2)
    q <Enter>

  6. Copy some windows utilities to the hard disk, for instance in a directory WINUTIL, i.e. Xcopy.exe and xcopy32.exe.

  7. Copy all files from your 2 OS/2 Warp boot floppies (Boot disk & Install disk) to the partition, including *all* hidden and system ones:

    <partition_drive_letter>:\WINUTIL\XCOPY A:*.* <partition_drive_letter>: /s /c /h

    (the /s /h /c flags mean: all files in subdirs, continue in case of erors, and also copy hidden and system files.

  8. Now delete all *.ADD files and all *.FLT files except XDFLOPPY.FLT

  9. Rename the (probably hidden) file OS2KRNLI to OS2KRNL. That change makes that OS/2 doesn't ask for the next floppy ....

  10. Copy all files from the os2image\disk_1 directory on the OS/2 CD-ROM to the partition. That subdir contains more files than the install floppy! (a.o. FDISK.EXE).

  11. Copy the files in IDEDASD.EXE to the partition, simply allow to overwrite the existing (old) ones. Then copy DANIS506.ADD to the partition.

  12. Edit the CONFIG.SYS which was copied from install disk 1: remove all references to SCSI drivers and to IBM1FLPY.ADD, IBM2FLPY.ADD and XDFLOPPY.FLT. Edit the line containing BASEDEV=IBMS506.ADD to refer to DANIS506.ADD instead.
    You can also make the following CONFIG.SYS and put it on the partition:

    set os2_shell=cmd.exe
    ifs=hpfs.ifs /c:64
    set path=\;\os2;\os2\system;\os2\install
    set dpath=\;\os2;\os2\system;\os2\install
    set keys=on
    rem basedev=ibm1flpy.add
    rem basedev=xdfloppy.flt
    set os2_shell=cmd.exe

  13. Remove the DOS boot floppy and reboot.

Hopefully your OS/2 Warp system boots OK.
My screen was clobbered up after booting. Remedy: add a reference to a non-existing basedev in CONFIG.SYS; OS/2 will complain that it can't be found but your screen is OK.

Installation step 2: Finishing all HPFS and FAT partitions & boot manager

Next step is to set up the almost final partitioning as far as all HPFS and FAT (including FAT32) partitions is concerned.

Start up OS/2 FDISK and make the following primary partitions (see Fig. 2):

  1. A temporary partition (at the beginning of the empty space) just as a place holder, in its space plus the space occupied by the primary partition you are working from the future OS/2 HPFS partition will be located;

  2. A boot manager partition (just one cylinder, usually 7 MB on large HDs), at the start of empty space;

  3. A large (several GB) partition which is to be the future Windows FAT32 partition. Now you got 4 primary partitions. You cannot add any partition anymore.

  4. Figure 2

  5. To be able to add logical partitions (i.e., add one extended partition), now delete partition D: (Fig. 2). FDISK will report empty space between your temporary OS/2 FAT partition and Boot Manager partition (see Fig. 3). You now have 3 primary partitions, i.e. the temporary OS/2 FAT partition, OS/2 Boot Manager and the future FAT32 Windows partition. From now on you can only add logical partitions, viz.:

  6. A logical FAT16 partition of 200-300 MB, meant as a common FAT16 partition and (more importantly) as a future OS/2 maintenance boot partition;

  7. A small (say 20 MB) FAT partition to be changed into a Linux /boot partition later;

  8. Partitions for any other OS than Linux, OS/2 and Windows you plan to install. I don't treat other OS-es than these three; I assume here that other OS-es can boot just fine from a logical partition or can be booted from a DOS FAT16 partition with DOS-based boot loaders similarly to Linux (viz. using loadlin).
    I have put my Windows 98 here - just needed 650 MB for that.

  9. A Linux swap partition (say, 100-200 MB);

  10. One or more Linux partitions (/, or perhaps /, /usr, /home, etc.) where the bulk of Linux will be installed;

  11. A large FAT partition, to be turned into FAT32 later.

Figure 3

While you are at it, look out and be sure to avoid at least cylinders 1016-1026, better even 1013-1030, as these are the cylinders where the Libretto BIOS will dump the hibernation information. (Have a look at the Windows page to read the gory details). Make sure that no partition extends into, or starts in this area. You can temporarily place a logical FAT partition here, as a last step before closing down FDISK, you can either delete this partition, or you may choose to later change it (using Linux fdisk) into a partition type not recognized or used by any OS you will install on the Libretto (e.g., type a0 = IBM hibernation partition).

In addition, it may be wise to leave some 75-80 MB empty space at the end of the HD as maybe (who knows) some day Toshiba may decide to upgrade the Libretto BIOS and move the hibernation area to the end of the HD.

  1. Now that all partitions are made up (by OS/2 FDISK), they have to be turned into the proper types. OS/2 FDISK can only make FAT (or HPFS) types. In addition, this will also make the drive letter assignment look more like the final one.
    You need partition editing software or a DOS or OS/2 disk editor to do this. I used an old Norton Disk Doctor and/or Linux, but other candidates are Partition Magic, PartEdit (DOS version, look here), .....
    If you take Linux, you can do it along these lines: copy some preliminary Linux start-up files to a FAT partition and boot e.g., Linux Mandrake 9 (or any other distro which can initialize the PCMCIA slots). Look here for some more details. You don't have to install Linux - the "installation" only goes as far as the Linux disk partitioning section - just change the partitons made in steps 3, 6, 7 - 10 into type 0b, 83, ?? (I took 0b for FAT32), 82, 82 and 0b, respectively.
    Would you be unable or unwilling to run Linux or PartEd or so, then you can easily remove all logical partitions other than FAT16 or HPFS to get the proper drive letters. Later, when installing Linux, the Linux setup can easily re-create them.
    Be warned that Win9x may not recognize FAT32 logical partitions beyond the 1024th cylinder if the logical partition chain is no more in disk order; if so, the extended partition type must be changed to 0f rather than 05, rendering it inaccessible for Warp 3. You can circumvent this using the EXPARTW4 package (look on Hobbes) but the downside is that primary FAT32 partitions will be inaccessible (hidden) for OS/2 then.

  2. Now, add the following partitions to the Boot Manager menu:

    • The primary OS/2 FAT16 partition from which you have booted;
    • The anticipated Windows primary FAT32 partition;
      (It may be better to wait until Windows has been installed - BM needs the proper boot sector which will only be there after Windows has been installed.)

    • The anticipated OS/2 logical maintenance partition;

    • The anticipated Linux /boot partition;
      (Likewise, it may be better to wait until Linux has been installed.)

    • Any other boot partitions you may have reserved for other operating systems.
      (Likewise, defer this until these actually have been installed.)

Finally, close down FDISK and reboot from the primary OS/2 FAT partition.

Installation step 3: OS/2 maintenance partition

This next stage comprises installation of a very limited OS/2 into the maintenance partition, plus preparing for the installation proper of OS/2 on a primary HPFS partition.

  1. Format the (logical) OS/2 maintenance partition (FAT). Assign it a proper label. Copy ALL files from the primary OS/2 FAT partition (including the possibly hidden system files).

  2. Using the files in GT2GBW3.ZIP, update the boot sector of the OS/2 maintenance partition using
    SYSINSTX <driveletter:>
    (otherwise the Libretto just won't be able to boot from it, all you'll see then is a cursor in the upper left corner of the screen).

  3. Edit the copy of CONFIG.SYS on the maintenance partition and be sure to delete all references to any drive letter; only absolute paths starting at \ may be included.

Once you're done, reboot, now from the maintenance partition. If all is well, OS/2 should boot without any problems.
  1. Copy the OS/2 Warp installation tree from CD-ROM (or floppies, using LOADDSKF), the various fixpak trees and the downloaded and expanded utilities to this partition.
  2. Start up FDISK and delete the primary OS/2 FAT partition we started from in Step 2. Together with the empty space from the deletion of partition (A) in step 2, you now have contiguous space from the first cylinder til the Boot Managers partition. Assign all this space to a new partition (where OS/2 will be installed), set it Installable and add it to the Boot Manager's menu as your native OS/2 Warp partition.

  3. Reboot the maintenance partition.

Installation step 4: Warp Connect itself

If you copied the CONFIG.SYS file from the install floppy #1 to the maintenance partition, there is a chance that OS/2 wil boot up with the installation screen. If so, installation of Warp 3 is a piece of cake.
If not, enter the following commands:

cd <drive where OS/2 installation tree resides>
cd \SET PATH=x:\os2image\disk_1;x:\os2image\disk_2;%path%
SET SOURCEPATH=<X:\os2image >   <Enter>
SYSINST2   <Drive_letter:\directory_containing_OS/2_installation_tree > <Enter>
Where X: = drive letter of partition containing OS/2 installation tree. If SYSINST2.EXE can't be found, it is in \os2image\disk_2

(Hopefully) You will see that OS/2's setup screen will show. If not, some files from OS/2 install_disks 1 & 2 must be added (I'll have to find out which ones).
Follow the instructions; be sure to format the OS/2 Warp partition as HPFS and to specify VGA as the screen driver.

BEWARE! As soon as the first reboot occurs, first boot from the maintenance partition and run the files from the GT2GBW3 archive, to be sure that OS/2 can boot from the newly made partition. Probably OS/2 boot manager will be instructed to boot your new Warp partition immediately and you'll be stuck with a black screen with a blinking cursor. No problem, just press the three-finger salute CAD.)

After the first reboot, the Selective Install screen is shown. On the Main menu (= actually Hardware menu, although it doesn't explicitly say so), add PCMCIA support (any Toshiba or Matsushita will do), plain VGA, no Multimedia, maybe a simple text printer or no printer at all, and no (repeat: no) brand of sound card or the like. On the next screen (= actually Software menu, again not explicitly), install Multimedia Support and all other options you like.

From then on, installation proceeds easily.


Warp Connect and plain Warp 3 ran on my Libretto 110CT quite OK with:

Fixpak installation

An important thing to do as soon as possible after installation of Warp itself is to apply FP40 to the newly installed Warp. This procedure is easily done as follows:

  1. Make sure that the fixpak files are expanded (using LOADDSKF) and put in a directory tree on the maintenance partition;
  2. Make sure that the service diskettes (currently at level CS1.43) are expanded into the same directory;

  3. Setup a RESPONSE.FIL file (instructions for FSERVICE) as follows (where in this example the fixpak directory tree resides in E:\OS2FP40 - fill in *full* pathname incl. driveletter on your computer):

    :SOURCE E:\OS2FP40
    * End of sample SERVICE response file without backup.

  4. Type: FSERVICE /<params>

At first, Warp will seemingly do little or nothing, but after a while (up to 10 minutes or so) it will one by one update almost all system files. You MUST however KEEP the IDEDASD files (don't let them be overwritten!).

GRADD video driver

You will soon get bored by the 640x480 16 bit VGA screen mode. Currently the only alternative is to use the (non-accelerated) GRADD generic video driver. I also tried the SDD driver (versions 7.04 & trial 7.09) but both couldn't be instructed to display properly in 800x480 resolution.
I also downloaded a Neomagic driver => same problem.
Even the Scitech SNAP drivers (as late of v. 2.2.3) can't be instructed to show 800x480 resolution. Worse yet, after uninstalling SNAP and reinstalling GRADD97, I initially kept the newer SNAP versions of various video files and then GRADD couldn't show 800x480. I had to reinstall GRADD again, this time overwriting all video files left behind by SNAP, to get 800x480 back....

For GRADD, it is best to have the latest fixpak installed (FP40, the higher ones are for Warp Server not Warp 3) and your display resolution must still be plain VGA.
Unpack / unzip the GRADD files into a temporary directory and run the installer:


where GEN stands for "generic".

(You can also specify SETUP NM, but then you must in a later stage exchange the line "SET C1=NMGRADD" in Config.sys with "SET C1=GENGRADD" - no harm done.
I got two CONFIG.SYS versions in \OS2\BOOT which differ only in that NMGRADD or GENGRADD line and use the recovery choices screen to boot between an external 1024x768 panel -accelerated- and internal 800x480 -stand-alone, unaccelerated. I still have to find out which files must be copied in place to skip the System screen where the other resolution must be selected first. I'll keep you informed)

(Although Neomagic is listed as supported, I couldn't get it working properly with setup NM. In 800*480 resolution, the mouse pointer refused to go beyond pixel column 640 and the screen image would pan to the left and wrap around instead: look here and compare with the picture at the top of this page to see what I mean. Vertical panning worked perfectly. I suspect there are still standard resolutions (viz. 640*480) hard-coded in the accelerated driver. Admittedly, it *was* accelerated...)

Before rebooting, you must manually add the following PRIVATE.DIF file to your C:\OS2 directory:

OEMString = "DDC 2 TOS 20612"

Graphics Mode: 640 x 480 at 60Hz vertical refresh.

XResolution = 640
YResolution = 480
VerticalRefresh = 60
HorizontalRefresh = 0
VPolarityPositive = 0
HPolarityPositive = 0

Graphics Mode: 800 x 480 at 60Hz vertical refresh.

XResolution = 800
YResolution = 480
VerticalRefresh = 60
HorizontalRefresh = 0
VPolarityPositive = 1
HPolarityPositive = 1

Graphics Mode: 800 x 480 at 75Hz vertical refresh.

XResolution = 800
YResolution = 480
VerticalRefresh = 75
HorizontalRefresh = 0
VPolarityPositive = 0
HPolarityPositive = 0

Graphics Mode: 800 x 480 at 85Hz vertical refresh.

XResolution = 800
YResolution = 480
VerticalRefresh = 85
HorizontalRefresh = 0
VPolarityPositive = 0
HPolarityPositive = 0

Next, reboot, and in the OS/2 System \ System Setup folder doubleclick on "System", select "DDC 2 TOS 20612" monitor and on the next page select a suitable 800x480 resolution & color depth. You have to reboot to try and test it.


Next the network section of Warp Connect needs to be set up.

Put the NDIS (NDIS2) driver for your network LAN adapter (I assume a PCMCIA-, nowadays called PC-card adapter) in a temporary directory on your hard disk.
In case you got a PC-Card without OS/2 drivers, it is wise to search the Web using e.g. Google - look for e.g., "OS/+2 NDIS LAN adapter <brand name>". Especially a number of Russian and Hungarian sites contained usable drivers.
Would you have a RTL8139 based PC-Card LAN adapter wih a suitable OS/2 NDIS driver, please inform me as I have been desperately looking for it ;-)

On the Warp Connect CD you'll find files called PRODINST.CMD and INSTALL.CMD. The former allows separate installation of network components, the latter will install a complete network environment.

If you selected PRODINST.CMD, after installation of Peer and TCPIP you'll need to configure networking adapters. On the desktop or in the OS/2 System folder you'll find an MPTS icon. Click on it, click "Configure", and in the next screen select "Configure LAN adapter". In the following screen you must first select your LAN card ("Have disk").

Once the LAN adapter is selected, you must bind the required network protocols (e.g., NetBios, LAN requester, TCP/IP, etc.). When that is done, click "OK"; in the next screen (which you've seen before) you now need to select "Configure NetBios" in case you have bound that protocol to your network adapter, otherwise click "Done". NetBios merely comprises setup of network names and a unique name for your computer. MPTS will try to update your CONFIG.SYS - on my system it didn't work out OK, I had to manually fix up my CONFIG.SYS. Once MPTS is finished, it may be time for a reboot.

Beware that a number of card brands (e.g., Xircom) do not need socket services but instead use a so-called point-enabler. You might need to disable the card slot where your network card resides, e.g.


disables the upper slot (the second, #2). Mind you, it is a zero not an O in IG0!

Next step is -if needed- to setup TCP/IP. TCP/IP setup is found in the Network icon on the desktop.

Then it is time to reboot and check if the network can be reached: open an OS/2 command prompt and try to ping other computers on the network.

Updating the TCP/IP stack and utilities

Although OS/2's naming might deceive you, it is the TCP/IP stack which is updated by MPTS upgrades. The TCP/IP utilities are updated through TCP/IP fixpaks. You need to successively update MPTS by applying the following fixpaks, either through FSERVICE (from a maintenance partition) or through MPTS itself:


TCP/IP upgrades are available up till level UN2100 (16 bit); real 32 bit can only be achieved if you patch the relevant SYSLEVEL files to deceive FSERVICE into thinking you got Warp Server rather than Warp Connect. But you can also try to manually unpack the fixpak files and copy them over the respective files in the TCP/IP directory; I've already unpacked them but never tried - my network is running OK so why should I change it? Again, much information can be found on the Warpupdates site. Relevant fixpaks are (in order of application:)

UN0980     (to be applied before WR08621 above, and again after having applied WR08621!)

Once you've updated the TCP/IP stack and util, you might consider upgrading other Warp Connect components, too. These comprise IBM Peer, LAN Requester, AskPSP, ...

Optional: NFS

NFS is a very efficient protocol and very fast (even with 16-bit utils still twice as fast as NETBEUI between my Libretto and my desktop). Apart from a quite easy Linux - OS/2 + Windows file sharing, it also allows to avoid NetBIOS over TCP/IP (TCPBEUI) which may eliminate some risks of file sharing across the Internet - OTOH, NFS is not that safe either and you must be sure to run a firewall and to properly set up your NFS exports.
Regarding NFS on Warp Connect one has to resort to the UN57064 stuff from IBM (a very busy server, you might need to retry often) or from Hobbes. This NFS Kit can easily be installed on top of Warp Connect's network stuff, but beware: specify \TCPIP rather than the default \MPTN install directory, otherwise your NFS won't work! (at least, that's what IBM suggested in an old TCP/IP Newsletter. I did by accident install it in \MPTN and found that until now all stuff works as expected ...)   In addition, you'll need an updated NFSD.EXE and NFSCLIENT.EXE (grab one here or here (look for PN69745.zip - a free download if you use ZOC for Telnetting into the BBS).
Note: one can still download various 32-bit TCP/IP utilities for Warp Server etc. Although they can't be installed using the regular way (one or more of the syslevel files have to patched for that) one can unpack them and manually copy the utilities into place. Some day I'll try them out on my Virtual PC Warp Connect box.


This department comprises:

  Basic OS/2 utilities

To be able to do some useful things under OS/2 a lot easier, a number of free but IMO vital tools are needed. They can be found on Hobbes or Netlabs or the IBM download site(s). These are:


EMX is a Linux emulator for the OS/2 platform. It is needed for various useful programs. Look on Hobbes and download the latest version (currently as of September 2003 it was 0.9d or so). You can follow the instructions in the ZIP file for installation.


ODIN is an emulator (or better, an interpreter) which allows 32-bit Windows programs (Windows 95 and up, not Windows 3.1) to be run seamlessly under OS/2 Warp. Although Warp 3 is not supported, ODIN can be run on that platform; some fiddling around is needed.

Why run Windows programs? As the ODIN people say, "some good programs have been written for the Win32 platforms", and I do agree with them. Pity those programmers ignored OS/2.

Why not? Well, because this way, viruses for the Win32 platform now can also harm OS/2 Warp. As ODIN runs at Ring 0 (the most privileged level of the OS/2 kernel), harmful programs cannot effectively be shielded. You might need to install and run an OS/2 virus scanner and update it regularly.

Anyway, detailed instructions for installation of ODIN on Warp 3 are outlined here. Suffice it to say here that you might need to download quite a number of fixpak levels for Warp 4 (yes, four) before you get hold of the proper PMSHELL.EXE version for your language (the mentioned site features just UK-English and DE-German). FYI, on my US Warp Connect I run a Warp 4 FP12 PMSHELL.EXE.
The latest ODIN builds can be found here.

OpenOffice 1.1

OpenOffice is IMO a real good, quite complete office suite, and it's free. It is by no means easy to get it running on Warp 3, but I managed to do it the following way.

I could access my Windows FAT32 C:-drive from Warp 3 as drive E:. I booted Warp 3, fired up the Register Editor and exported all keys to a file. I then read that file into a text editor (e.g. Warp's EPM, Enhanced Editor) and threw away all keys which did not relate to OpenOffice. Many OpenOffice keys feature names containing "Star", "Staroffice", "Sun", etc. Next I did a search-and-replace action to replace all path names in the file from e.g., C:\<some_path> to E:\<some_path> (as OpenOffice seen from OS/2 resides on E:). Then in OS/2, I used the Win98 registry Editor (which runs fine on Warp 3 using ODIN) to import all the keys into the registry kept on the Warp drive (Warp's / ODIN's registry editor is just a piece of sh....). The next action comprised making a desktop shortcut to E:\Programs\OpenOffice.org1.1\programs\soffice.exe and associate .xls, .ppt and .doc files to OpenOffice.

Not all OpenOffice components run as desired (Help nor Spell Checker work, selecting languages doesn't work either) but most functionality is useable. Hopefully it gets better with newer releases of OpenOffice and ODIN.

In the meantime Innotek has published a beta port of OpenOffice 1.1 for OS/2. It needs two helper apps which are readily installed, but the OpenOffice setup itself does not work out OK.

OpenWatcom C++ & Fortran77

If you want to do some real developing for OS/2, you might need this compiler. It is a free download from the OpenWatcom site (currently version 1.2 stable). As valuable bonus this package features cross-compiling (you can develop e.g. Windows NT programs on an OS/2 platform) and OS/2 16 bit programs, which may look outdated until you realize that most OS/2 device drivers have 16 bit interfaces to the operating system. The only other available compiler which can do this trick is the old Microsoft one (see below). Go to the OpenWatcom ftp site and either download either open-watcom-os2-1.2.exe or a selection of the various zip files for version 11.c (which is advertised as an "upgrade" but really is an almost complete package); either way, take good care of the README.TXT.

For 11.0c you might need the IBM developers Toolkit in addition, but that one is not free. But wait- the IBM Toolkit 4.0 upgrade can (could?) be downloaded for free. You must first register as a guest user on the DevCon site. Then search for os2tk199.zip and download it. Simply expand the zip file into a proper directory somewhere and edit the various LIBPATH, INCLUDE, BOOKSHELF and HELP statements in CONFIG.SYS. This toolkit upgrade features almost all include files, libraries and utilities you need including the resource compiler, save for one vital file called bseerr.h.

However, a similar file is included in the OpenWatcom Fortran include files (it is called bseerr.fi) and you can have it translated to c by the f2c utility. Or you can do it yourself at the expense of some work. I used a text editor with a good search-and-replace followed by a spreadsheet program to translate the Fortran decimal constants into hex, but you might do it your way.

A while ago a clever programmer put together a zip file containing many needed include files (inc. bseerr.h) here, hopefully you can still find it (start from there looking for archive.zip).

More information on OpenWatcom is given on http://www.openwatcom.org.

In case you want to do some cross-compiling for Windows, you also need Microsoft's Platform SDK. For this you must surf to Microsoft's MSDN site and do a search for Platform SDK (you can order one on CD). Its location changes continuously, so once you get hold of a Platform SDK download make adequate backup copies.
The newest version of OpenWatcom (1.2 and up) for OS/2, which seems to have a preliminary but working toolkit included.

IBM DDK online

IBM's on-line Driver Developer Kit has recently been re-opened on a new location. For a while you could not register anymore (that has been re-enabled too), but someone on comp.os.os2.programmer.tools found out that you can access the library anyway using guest for both login name and password. If I were you I'd download really all files as the site still may close down in the near future.
Amongst others, on the DDK site you can find the old Microsoft C compiler and their MASM assembler, with can both be used for driver development.

Miscellaneous useful software

NPS WPS NPS-WPS (look for NPSWP182.ZIP) is a PM enhancer capable of autoraising windows (much like X-Windows) and it can provide a close button so that you do not have to double-click in the top left of each and every window anymore to close it. In addition, it has many more goodies.
Gibbon Double Click This one transforms a click on the middle mouse button into a double-click. The program used to be shareware but nowadays you can get a registration key for free by registering at http://www.gibbon.com/.
Star Office 5.1a (look on Hobbes) is the latest version for OS/2. It has quite good support for MS-Office file formats (at least MS-Office 97). Upon acquisition of Star Division, Sun has released a public key for previous version 5.1, reproduced here (type it literally, mind case):
Company: Sun Free Download version
Key: 680A-0JH7-M60MVR-CQPD-147K
(if it doesn't work, experiment with the O's (uppercase o) - some of them may be 0 (zero's) instead.
On Hobbes some patches and updates can be found.
EZ-Play is PC-Card management software from IBM. It does not support Cardbus cards (very well), and I could only get my CF-cards recognized. None of my PCMCIA CD-ROM players could be set to work with it.
Speaking of it, Veit Kannegieser has made a PC-Card Cardbus enabler and a patch for a faulty PCMCIA.SYS (look on Hobbes). Perhaps these allow for better recognition of PC-Card mass storage devices.
I had more luck with the DANIS506.ADD and DANIATAPI.FLT drivers - they allowed me to use my Freecom Traveller 1 CD-R/RW as a CD-rewriter. I tried to get my Cardbus Freecom Traveller II+ CD-R/RW/DVD and Argosy external 2,5" HD to work, too, but no luck. I begin to think that that may be related to the DANI drivers not being able to cope with the ISA bus on the one hand where the internal HD is connected to and the PCI-to_Cardbus on the other hand where PC-Card mass storage is to be connected to .... in addition Warp 3 doesn't have very good PCMCIA support.
BATTERY.ZIP (again, on Hobbes) is a good tiny battery status indicator for the desktop.
BLACKOUT.ZIP (here) is a screen blanker (OS/2 Warp APM as shipped cannot blank the screen by itself); I run it with a command line like "Blackout -t 0 -s 4 -l -m" from the Startup folder.
HYBERNATE (here) is a package which is NOT suitable to hibernate your OS/2 Warp! (it will fubar your entire MBR!) but, when used together with APM2V1.4 it is quite useful for powering the Libretto down after shutdown (another thing OS/2 Warp 3 cannot do). Hybernate setup asks you to swap the original W3 kernel for a W4 kernel from fixpak 12 and patch that a bit, together with a few other files (DOSCALL1.DLL, PMMERGE.DLL, VW32S.SYS, IBMKBD.SYS, RESOURCE.SYS) and add ISAPNP.SNP and PNP.SYS. Of course you need a W4 license.


X-server PMX

Maybe not so very useful, but I liked it much: On top of Warp Connects TCP/IP stack one can very well run IBM's X-Windows Kit for TCP/IP V. 2.0. That used to cost $ 140,-, but you can freely access download updates and CSDs which together constitute the complete package. FWIW, nowhere in the included docs did I see a provision that one is to be a licensee of the TCP/IP 2.0 Kit; in the latest package README.1ST file, a stanza says that the product's end-of-life has been reached (already in 1997) and that installation is all at your own risk.

There is a more recent and without doubt better and also free X version (XFree86 v. 4.3.0) but that is always full-screen; the PMX server allows "rootless" windows, even the Linux kdm login screen (after enabling XDMCP) is just a PM screen.

OK, the stuff is a bit outdated (it is for X11 Release 5 rather than contemporary X11R6 as featured on Linux); in addition it can't handle a scroll mouse wheel. Nevertheless, I get the impression that PMX is quite a bit faster than XFree86 and better integrated into the PM desktop.
To show what can still be done, here's a picture from my Libby running Linuxconfig on my desktop through X-Windows:



When e.g. the datafiles for an X-application are on my Lib, I mount the Lib's drive(s) through NFS on the desktop (if needed through X-Windows) and then run the CPU-hungry app on the desktop. Provided the graphics output speed of the app is not the issue, a significant speed improvement can be noted; as I do quite a bit of number-crunching with limited graphical manipulation, that provision is accounted for. Of course on the desktop PC itself things go much faster.

Download all the files in the UN59374, UN87312 and PMXFixup directories from ftp://service.boulder.ibm.com/ps/products/tcpip/fixes/v2.0os2 (keep these directories apart on your HD).
Expand all files using LOADDSKF or -preferrably- DSKXTRCT or unzip and start with installation in the order given above, using the TCPINST.EXE in each package. I read in an old IBM TCPIP Newsletter that installation should be in \TCPIP rather than the default \MPTN , but I've tried both and couldn't discern any difference. Reboot between installation of each package just to be sure.
A much easier alternative is to download the complete PMX.ZIP package from the OS2Ports.com site which is devoted to *NIX->OS/2 ports.
After installation and reboot you need to add/specify a few thingies in the TCP/IP Configuration (in OS/2 System folder):

In addition, do the following:
  • In your CONFIG.SYS, add a line:
  • Reboot
  • Make a desktop folder called e.g., PMX or X-Windows, add the following programs:
    • PMX.EXE in \<TCPIP or MPTN>\BIN. You might make a shortcut on the Launch Bar, too;
  • Fire up PMX, and when you see its window appearing, start the program XEV. It will open up an X-window and an OS/2 command window. If all went well, various instructions should be shown on the command window when you hover the mouse pointer over the X-window.
  • Try the other X-programs in the X-windows folder.
  • Then, you can choose to apply the updates in the PMXFixup package. I haven't yet done so, but maybe I'll try it some day. They seem to be needed only in case the installation of PMX hangs.

As an example, I'll outline how I get to run programs on e.g. a Linux PC to show up on your Libretto.

  • Make sure that telnet and telnetd have been installed on your Linux box and started by inetd or xinetd (using linuxconf). To test, type in a terminal:
        open <your_linux_box'_host_name>
    If you see a login prompt, telnet and telnetd are working OK. If not, you'll have to sort it out (this is an OS/2 page, remember? :-) )
  • Add your Libretto's host name and IP address to your /etc/hosts file (if that hadn't been done already);
  • On your Libretto, add the Linux hostname and IP address to the hosts file in either \TCPIP\ETC or \MPTN\ETC (or both);
  • Open an OS/2 command prompt and check that telnet and telnetd are working, using similar syntax as on the Linux box. If telnetd doesn't work, check the TCP/IP Configuration settings and try to launch it using "start inetd".
  • If all looks well, reopen the OS/2 command window. First check the DISPLAY setting:
        echo %DISPLAY%
    If you see an empty line, check your CONFIG.SYS setting for the DISPLAY variable. In that case, you can for the time being enter:
        set DISPLAY=<your_Libby's_host_name>:0
  • Type: xhosts
    If all is well, the host name of your Linux box should be mentioned. If not, just type
        xhost <your_linux_box'_host_name>
    and check again;
  • telnet into your Linux box and start an X-program (e.g., xcalc, xearth, kspread (K-Office's spreadsheet) or whatever. You may see a long list of complaints in the telnet terminal, but don't worry - usually after a while the Linux program's window shows up.
  • I tried XDMCP to login on my Linux desktop PC; the Linux login screen (kdm or xdm) was shown, but no window manager could be started. So XDMCP can as well be disabled I think.
  • Play around with it much more!

X-suite XFree86

XFree86, the native Unix/Linux X-server, has been ported to OS/2 by Holger Veit. I call it a "suite" because it includes a.o. a window manager (twm) and much more utilities than PMX or other commercial X-servers.
In contrast to PMX and e.g., Hoblink X, XFree86 demands exclusive access to the screen; consequently PM/WPS and PM-programs will be inaccessible once XFree86 has been started. IMHO this is quite a disadvantage, it effectively limits usability of your OS/2 box to a few ported X programs and/or turns it into an X-terminal, but it may be that many other users have other opinions.
Detailed instructions can be found on OS2Ports.com. Take notice that the latest version mentioned there is 3.3.6, although 4.3.0 is also on their XFree86 ftp-subdirectory. It may be that the 4.3.0 branch on Netlabs (I can't get the %22 from the URL, remove it yourself please) is somewhat more recent as regard fixes.

I found that only version 3.3.6 could be run on my Libretto. I can give you the XF86Config files for the internal LCD screen (with a virtual 800x600 resolution) and an external 15" 1024x768 TFT panel.
XFree 4.3.0 could only start the X-server itself in 640x480 and lower resolutions; twm did not start through. The system would hang when using the above XF86Config files (actually meant for v. 3.3.6, but on Linux XFree86 4.3.0 runs OK with 3.3.6 F86Config files).


Al Savage's Warp install notes . Very useful stuff, geared towards Warp 4 but equally well applicable to Warp 3. Admittedly a slow server.
Notebook/2 site Dr. Martinus' Notebook/2 Site. Outdated and disappeared. It contained a lot of useful info. It's supposed to be taken over by http://www.os2warp.be in spring 2004?/5?
os2warp.be, claims to become the hardware info site for OS/2
EDM, Electronic Developer Magazine for OS/2. Not updated, no more issues, but the on-line editions are still accessible.
OS/2 World.Com
OS/2 Site, an Australian site
OS/2 Voice, an electronic magazine
OS/2 E-Zine, another e-magazine (warning: Mozilla 1.4.1 and later crash on this site!)
Chuck McKinnis' NICPAK page, a collection of LAN card drivers, also PCMCIA ones
Link Everything On-line, a file repository
Warpguru's Home Page (Roman Stangl's site)
Gfd.Sys.Drv-GFD - a somewhat misty download site, but it contains a lot of rare stuff
OS/2 Files - another download site
OS/2 Super Site Just what its name says
Tucows OS/2 download site
SchnickSchnack a German download site containing rare stuff

Commercial software:
BMT Micro

And if that's not enough, here are 830 more, nicely sorted per subject....