How to update Warp 4

For starters, make sure when you download this stuff that you use a Binary download. This is usually the default for most FTP clients, but not always. Second, each time you download another update, take my advice and put all its associated files in a separate directory on your hard disk. This will make installing everything easier later. And finally get familiar with Hobbes and with the IBM Boulder FTP site:
 * Hobbes:http://hobbes.nmsu.edu
 * IBM Boulder:ftp://service.boulder.ibm.com/ps/products/ and ftp://service.boulder.ibm.com/ps/products/os2/

Its worthwhile to have both Info-Zip's Unzip and DSKXTRCT (which allows you to extract IBM's .DSK files to your hard disk without needing a floppy). Grab them, extract them, and put the .EXE's somewhere in your path:
 * DSKXTRCT:
 * Unzip:

If you want to grab ZIP while you're at it, its always good to have too. Search the Hobbes archive for it.

For Warp 4, I'm assuming you're working with the original 1996 release, and the US English version. If you're on any other language, you'll have to substitute the appropriate fixpaks for your language.

There are many ways to install fixpaks, but an easy way is with sfix:

You can also use IBM's RSU-CSF facility if you wish. If you want to do this, grab the utility from: ftp://service.boulder.ibm.com/ps/products/os2/rsu/csf144.zip

(I'll get to how to use that utility later)

For Warp 4, you'll want to install the Device Driver 2 fixpak, and Fixpak 15 - the latest "free" fixpaks from IBM:
 * The *.?DK version of Fixpak 15: ftp://service.boulder.ibm.com/ps/products/os2/fixes/v4warp/english-us/xr_m015/
 * Or the ZIPped version of the fixpak: ftp://service.boulder.ibm.com/ps/products/os2/rsu/xr_m015


 * The *.?DK version of Device Driver 2 Fixpak: ftp://service.boulder.ibm.com/ps/products/os2/fixes/ddpak/xr_d002/
 * Or the ZIPped version of the DDK2 fixpak: ftp://service.boulder.ibm.com/ps/products/os2/rsu/xr_d002/

Which to grab? If you're using sfix, grab the disk image version (the *.?DK link). If you're using the IBM RSU-CSF facility, grab the ZIPped version. Place the groups of files each in their own directory (as I mentioned earlier) - for example: c:\fp15 c:\ddk2 c:\csf144 etc. You get the idea.

While you're at it, download (into its own directory) the TCP/IP fixpak at: ftp://service.boulder.ibm.com/ps/products/tcpip/fixes/v3.1os2andv4.0os2/universal/un_0980/

Also, grab the version of MPTS with the 32-bit TCP/IP stack (many of the newer apps out there need the 32 bit stack). The "installation" for the newer version of MPTS is at: ftp://service.boulder.ibm.com/ps/products/mpts/fixes/english-us/wr08610_conv/

And then the Fixpak to update MPTS (once you get the "newer" version installed) is at: ftp://service.boulder.ibm.com/ps/products/mpts/fixes/english-us/wr08621/

If you're going to use the peer-to-peer networking features, grab the peer networking update at: ftp://service.boulder.ibm.com/ps/products/lan/fixes/ibm.peer/english-us/ip08414/

On a Novell network? You'll want the most updated client at: ftp://service.boulder.ibm.com/ps/products/netware/Client_OS2_V212/

If you have an older display adapter, you may want to try the last "free" version of Scitech Display Doctor that doesn't require a Passport Advantage subscription: ftp://service.boulder.ibm.com/ps/products/os2/os2ddpak_cur/sddse704.exe


 * Note that before installing this, check its readme to see if your display adapter is on the list of supported adapters.

For anything that you need Feature Install for, you'll need Netscape 4.61:

Feature Install can be found at:

If you want the IBM Plug-in pack for Netscape 4.61 - this adds MPEG playback to OS/2's MMOS2, it also adds the ability to stream any file types that OS/2's MMOS2 understands from the internet: nspip30.exe

You'll probably also want DaniS506.ADD instead of IBM1S506.ADD: I also suggest every OS/2 installation have EMXRT installed. Many *nix ports use the EMX runtime library, so its good to have it installed:

Many new applications these days are using Warpin for their install, so its a good idea to have Warpin on your system: http://warpin.netlabs.org/?show=download

If you want FAT32 support, grab it from: ftp://ftp.netlabs.org/pub/fat32/

For FAT32 to work, you may need DaniDASD (this is needed for any non-LVM version of OS/2 which you want to work with FAT32): http://hobbes.nmsu.edu/download/pub/os2/system/drivers/storage/danidasd144.zip

(I haven't used VFAT-OS2 or RAMfs, so I can't comment on them)

For CD Writing with the "free" tools, you'll want DANIATAPI (if you're using an IDE writer):

And ASPIROUT: http://home.clara.net/orac/os2.htm

And finally, grab a memory checking utility such as countmem to tell you whether or not OS/2 is recognizing all your memory (sometimes OS/2 has trouble seeing memory over 64 Megs on *some* system BIOS'es):

And grab Patchldr just in case you do need to patch the loader so OS/2 will see all your memory (in cases where countmem only sees 64 Megs):

For more on CD burning, check the info at: http://www.os2world.com/cdwriting/

You'll also want to grab the latest version of Firefox and Thunderbird, or Mozilla suite, or SeaMonkey, or all of the above - so you'll have a modern web browser. You can find info on them at: http://os2news.warpstock.org/Warpzilla.html and http://www.mozilla.org/ports/os2/


 * Step 1:Okay, so you've decided what you want, downloaded it, now what? I'm assuming you've already got a base Warp 4 up and running.

Install the Device Driver fixpaks and Fixpak 15.
 * 1) install the sfix utility
 * 2) use the sfix utility to install FP15
 * 3) Reboot
 * 4) Use sfix to install the Device Driver 2 fixpak
 * 5) Reboot
 * 6) Unzip the countmem.zip and run countmem.exe in a command prompt. If all your memory is recognized then no need to patch your loader. If it only sees 64 MB, then jump to Step 1.7
 * 7) Unzip patchldr.zip, and follow the directions in its documentation file for patching your boot loader so all your memory will (hopefully) be recognized. Reboot and run countmem again and see if OS/2 now sees all your installed memory.


 * Step 2:If you plan to try and use the Scitech Display Doctor display driver, then install it now (read its docs on how to install it - it requires a recent OS/2 fixpak - that's why it has to wait until after FP15 is installs). Reboot, set your resolution under the System properties, and reboot again to get your desired screen resolution.


 * Step 3:if you installed MPTS and TCP/IP when you installed OS/2, then install the TCP/IP fixpak using either sfix or the RSU - CSF utility (to use the CSF facility, you'll first need to use DSKXTRCT to extract the files to your hard disk, then see below for directions). Reboot


 * Step 4:Use DSKXTRCT to extract the wr08610 files to a directory on your hard disk, change to that directory and run: MPTS.EXE

This will install the newer MPTS utility, along with an early version of the 32-bit TCP/IP stack. Then reboot


 * Step 5:Use sfix (or RSU-CSF facility) to update MPTS with wr08621. Reboot


 * Step 6:Use sfix to install the Peer fixpak (if you're using Peer). Reboot


 * Step 7:Now you can start installing other stuff such as Netscape Communicator and Feature Install (for regular browsing, I suggest the latest version of FireFox or Seamonkey, although the feature install plug-in won't work with these newer browsers), Firefox or Seamonkey, the EMX Runtime, Danis drivers, ASPIRout, Warpin, FAT32, etc. All of this stuff has documentation that explains how to install it - read it!

1. Unzip the CSF utility to its own directory: c:\csf144
 * How to install Fixpaks using the CSF-RSU utility instead of SFIX:

2. Extract the desired fixpak into its own directory using either UNZIP or DSKXTRCT:

For example: c:\fp15 Change into your CSF directory, and type the command (from a command prompt): os2serv c:\csf144\csf c:\fp15 Then highlite your fixpaks and use the "Install" option. Also, make sure the "replace newer" files is selected, that way it'll replace any files with the ones in the fixpak.

You can install *any* fixpak this way with IBM's RSU version of the CSF utility - just replace the C:\FP15 directory with the directory that your desired fixpak is.

Final Words
Okay, that covers the majority of the updates that I normally recommend for a freshly installed Warp 4 machine. Of course another option is to use many of these components to create an updated Warp 4 CD using UpdCD, which once created you can just boot from and do an install - the result being at the latest fixpak levels. But, if you don't have a rebuilt CD, all the above information should get you on the right track.