Setup of Warp 4

Disclaimer
I have not used OS/2 since 2006. I put together this file in late 2007. My memory is not 100%. This includes many useful OS/2 utilities that were either hard to find or that have since been removed from IBM's FTP site. Most of these can still be found elsewhere on the net- maybe even all of them can. However I have tried to assemble them in one package for your convenience, as well as for myself next time I install Warp on a computer. I have totally forgotten what uzs551x2.exe is for, yet I had it in my utils pack back when I was still using Warp. There must have been a reason, I just don't remember it. Hopefully it's useful to you.

Useful Info for the relative novices
If a specific Warp version is not mentioned with any of the below files, they can be used on any version of Warp. Warp refers to versions 3.0, Connect 3.0, 4.0 and 4.5x of OS/2. Sometimes you will find versions referred to by their development/project names (Warp/Warp Connect/Merlin/Aurora), explained below. In all my files, I refer to versions by their numbers. Some websites and utilities refer to supported versions based on names.

Warp- original name given to OS/2 3.0 during development. Originally not with networking included, 1994

Warp Connect - OS/2 3.0 with networking capabilities, 1995

Warp 3.0 and Warp Connect were marketed as two versions. "Red Spine" and "Blue Spine" based on which color the box was. "Red Spine" did NOT include its own internal support for Windows 3.x code, if you wanted Windows support you needed Windows install disks. "Blue Spine" included internal support for Win 3.x code.

Merlin - name given to Warp 4.0 during development, marketed as Warp 4, included the networking and internal Win 3.x support same as Warp Connect 3.0 "Blue". Also included Java support and Voice Recognition software.

Aurora - name given to Warp Server 4.5 during development.

FYI, if you see a program or utility available in 2 versions, the one with PM (presentation manager) in its name or description will be the GUI version (ex: pkzip is command-line, pmzipper has a GUI)

Included Files
Warp_Install.txt - instructions (by me) for installing Warp, as well as necessary sequence of some other utils (ex: FixPak 35  or FixPak 5  or higher must be installed before GRADD video drivers). Sometimes you need to install "fix a" then "fix b" then "fix a" a second time. This is explained here. Also includes details on several useful batch files you should make to simplify your life. IBM's instructions for installing Warp 3/Warp 4 with newer drivers DO NOT WORK from CD, they only work from floppies!! My instructions work for both.


 * ip08196 - fixes for IBM Peer services for Warp Connect 3.0. See enclosed documentation, recommend using Disk Extract (included, below) to install.

MPTN - fixes for MPTS (Multi Protocol Transport Support) for Warp Connect 3. See enclosed documentation, recommend using Disk Extract (included, below) to install.


 * sfix144 - version 1.44 of IBM's SFix utility (fixpack installer)

TCPIP - Warp Connect 3 fixes for TCP/IP stack, mainly y2k compliance. NOT needed if you install IBM's v4.1 TCP/IP stack (not included in this archive). See enclosed documentation, recommend using Disk Extract (included, below) to install.


 * w3fp40 - Warp 3.0 FixPak 40.  See enclosed documentation, recommend using Disk Extract (included, below) to install.  FixPaks 41+ are by pay only and intended for Lan Server versions, not regular Warp 3.  THIS IS FOR WARP 3 and WARP CONNECT, NOT WARP 4 OR WARP 4.5x

Repeated for emphasis: ip08196, MPTN, TCPIP and w3fp40 are for Warp 3, NOT Warp 4 or Warp 4.5x!!!

Some of these are for English versions only, some are for any language... see each package's documentation for details.


 * 118os2jre.exe - v1.1.8 OS/2 JRE (Java Runtime Environment) (needed for install of 4.1 TCP/IP). Must install Netscape 2.02 or 4.61 (4.61 included, below) to install this.


 * ati-rage_sdd2se.exe - GRADD video drivers, despite the name this is a full pack with all drivers, not just ATI. This is the PAY VERSION, not the free version!!  Must install FixPak 5 (for Warp 4) or FixPak 35 (for Warp 3) or higher in order to use.


 * idedasd.exe - newer IDE drivers. I forget why it's here since I always used danis506 drivers, but there must be a reason...


 * uzs551x2.exe - unzip for OS/2, command-line version


 * Warpin-1-0-8.exe - WarpIn third-party program installer, v1.08- newer versions are available for Warp 4 and 4.5, this is the last version that worked reliably for me under Warp 3. Repeat for emphasis: this is the last one that worked FOR ME.  Maybe you can use a newer version, maybe you'll have to use an older one...


 * xwp-0-9-18-2.exe - XWorkplace v0.9.18.2 enchancements (mostly visual aka "eye candy") to the workplace shell, IMHO required for OS/2, installed by WarpIn (so install WarpIn, above, first), newer versions available for Warp 4 or higher - this is the newest one that worked well for me under Warp 3. Repeat for emphasis: this is the last one that worked FOR ME.  Maybe you can use a newer version, maybe you'll have to use an older one...


 * b120.zip - cmd files to trick Warp 3.0 Blue Spine into calling itself either Lan Server 4.0 (for installing FixPack 41+) or Warp 4.0 (for installing TCP/IP stack 4.1 and Java 1.3.1 EDIT THE CMD FILES (so you can read them) before running them and follow instructions!  Not following instructions is DANGEROUS and could totally hose your system!!  DO NOT USE WITH WARP 4.x!!!!


 * cfgmnt105.zip - ConfigMaint 1.05, CONFIG.SYS analyzer and optimizer. Designed for Warp 3.0, however it worked well for me under Warp 4.0, untested (by me) with Warp 4.5x versions.  Use on 4.x AT YOUR OWN RISK!!


 * danis506r1610.zip - third-party generic drivers that allow use of newer large hard drives (better than any that IBM ever released)


 * dskxtr13.zip - Disk Extract 1.3, used to apply FixPaks from HD instead of making numerous floppies


 * fi125us.zip - IBM's Feature Installer v1.25, used to install Java and 4.1 TCP/IP stack as well as many other IBM utilities


 * firewall_doc_v14.zip - documentation on Warp's internal firewall- setup and config instructions


 * isofs-v0_2_1.zip - makes ISO files (CD images) mountable in OS/2 without burning them to a CD first


 * jrstimdt.zip - date, day, time widget for XWorkplace... obviously requires XWorkplace to be installed


 * kon115.zip - freeware hex editor. A hex editor is always handy, but REQUIRED to install Odin on Warp 3.


 * lsw270.zip - lSwitcher, enhanced ALT-TAB switching between programs- works best with XWorkplace, but can be used standalone as well


 * nsc461.zip - Netscape Communicator 4.61, required for install of JRE 1.1.8 and TCP/IP 4.1 - outdated as a web browser, luckily newer Mozilla Firefox versions have been ported to OS/2


 * pci048vk.zip - utility for identifying PCI devices on your system- identifies by chipset and revision, not just vendor. Identifies over 12,000 devices.


 * pmzppr18.zip - Presentation Manager (PM) version of Zip - just a graphical version of Zip, much like WinZip is for Windows. Command-line version included (above) as uzs551x2.exe - command-line version MUST BE INSTALLED FIRST


 * ramfs118.zip - RAM disk utility, I put my TEMP directory on one


 * thewall098.zip - firewall setup and config utility, ONLY WORKS WITH THE 4.1 TCP/IP STACK!!


 * vrobj21.zip - honestly... I forget what this DLL does, but I got it for SOME reason... just add it to somewhere in your CONFIG.SYS's LIBPATH= statement. You may want to do a web search on it first, I'm sure it does something.  While I'm writing this, I have no internet access so I can't do that for you.


 * w4106.zip - updated Warp 4 (Not Warp 3 or Warp 4.5x) kernel, newer than the one in FixPak 15. If you don't know how to update your kernel, DO NOT mess with this.  Period.


 * xtrarexx044b.zip - XtraREXX, expands on REXX commands. Required for WarpIn or ZWorkplace (maybe both, fuzzy memory)


 * zampa10b.zip - graphical (PM REXX) firewall config utility

Links
useful internet links, I have not checked these since mid 2006.


 * http://hobbes.nmsu.edu/pub/os2/ - Hobbes, the SINGLE MOST IMPORTANT OS/2 file repository
 * ftp://ftp.netlabs.org/pub/ - OS/2 file repository IIRC
 * http://www.os2site.com/sw/index.html - OS/2 file repository
 * ftp://ftp.boulder.ibm.com/ps/products/os2/fixes/ - IBM removed all references to the FTP site from their website, but LAST TIME I CHECKED you could still access it directly. This may have changed.  In fact, it was scheduled to be removed in Dec 2006.
 * http://os2ports.com/downloads - OS/2-Unix ports repository

Warp_Install.txt
OS/2 must be installed on a partition contained within 1024 real tracks on a HD- regardless of LBA mode or not. This means you're limited to about 850 megs on a boot partition. I have mine set up on 500-800 meg partitions, and even the 500 meg ones aren't full.

You need the updated hard disk drivers in order to access disks over 540 megs in size. These dirvers are:
 * IBM1S506.ADD
 * IBM1FLPY.ADD
 * IBMIDECD.FLT
 * OS2CDROM.DMD
 * OS2DASD.DMD

Even better, get DANIS506.ADD and replace IBM1S506.ADD with it. This is a drop-in replacement by Daniela Engbert that adds extra functionality and better handling of bus mastering. These files should replace files of the same name on install disks 1 and 2 (4 are on disk 1, 1 on disk2)

do NOT follow IBM's instructions of adding the line copyfromfloppy=1 to your config.sys file!!!!

During install, IBM1S506.ADD is copied from CD to the HD as a read-only file, then it tries to copy the driver from floppy and the entire install fails due to this read-only attribute!!

Find drivers for your NIC. If you can't find OS/2-specific ones, that's OK- OS/2 will accept NDIS drivers as well. IBM's Device Driver Pak Online: http://www7.software.ibm.com/2bcprod.nsf Only worry about the NIC drivers, get everything else LATER. Trust me! :)

Warning: if you're not good with DOS-type commands now, you will be before you're done. add x:\diskimgs to your path (where x: is the letter of the CD-ROM drive)-or- copy xdfcopy.exe from there to somewhere in your system path. This program will work under DOS, OS/2 and Windows (I have used it myself under 95,98 and XP) switch to x:\diskimgs\os2\35 (cd command- you know this one, right?) you'll need three blank 1.44 floppies

type: xdfcopy disk0.dsk a:	-follow prompts to make disk0 type xdfcopy disk1_cd.dsk a:	-follow prompts for disk 1 type: xdfcopy disk2.dsk a:	- make disk 2 Update the drivers listed above on disks 1 & 2

Put disk0 and the CD in the computer you want to install OS/2 on. Follow prompts for disks1&2. Select Advanced Installation, and do NOT accept whatever drive it says it's going to install OS/2 onto. This will bring up the Fdisk screen. Delete all partitions on Fixed Disk 1 and install Boot Manager if you can- of course backup any files you need BEFORE deleting the partitions

Create other partitions as you like, however I recommend 2 boot partitions (1 for recovery when you screw up- if you're new to OS/2 rest assured you *will* screw up) and add both partitions to the Boot Manager Menu Note: OS/2 does not require you to ever make a primary partition- every one you make can be an extended partition if you like. You can use this to manipulate drive letters- for instance, you could have the slave drive on the secondary IDE channel be C: by making it a primary partition and all other drives have extended partitions.

Anyway, set up your two boot partitions, add them to the boot manager menu and set one of them as installable. This is the one that you'll be installing to right now (see how this works?) As you exit FDISK, it will give you a warning if you have no primary partitions- but this won't affect anything, so who cares- it's a useless warning. Since you changed drive letters, you'll have to reboot. Swap some more floppies, kick back, and pop another beer.

Disk0,disk1,disk2.. you're gonna get sick of this routine shortly. This time when you get to the point where OS/2 asks you what drive it's installing to, it should be the one you selected. Sicne it's just been FDISK-ed you'll have to format. Choose HPFS, if you choose FAT you're shooting yourself in the foot. About 90% of OS/2 software can't be run from a FAT partition, including Java and Odin (the Windows APIs). FAT will also suck of a shitload more resources- a 14 meg FAT disk cache performs less effectively than a 1.5 meg HPFS cache. At any rate, use HPFS for OS/2 whenever possible, and if you need to share with Windows running on the same machine, have Win make a different FAT32 of NTFS partition- OS/2 can read/write both of them, just can't create them. Sidenote: NTFS is MS's version of a fucked-over HPFS. While better than FAT, it's still not as good as the real HPFS. :)

After the format (which takes seconds) files are copied, OS/2 detects hardware (usually incorrectly) and tells you to pop out the disk and reboot.

Diverge from IBM's path again, due to the same problem above- the drivers on your HD are the old ones from 1996 that can't handle newer drive capacities. Put in disk0, disk1,disk2 as prompted- the first screen that comes up after everything is loaded says at the bottom "press F3 for comamnd prompt" Do it.

IBMIDECD.FLT and one of the .DMD files will be in the root of your install drive. The others will be located in \os2\boot

Replace them anywhere you find them with the updated ones off of the floppies. IBM1S506.ADD is read-only, so you'll have to attrib it to replace it- but attrib isn't in your path. It's found on the cd-rom at x:\os2image\debug <-- add to your path "path=%path%;x:\os2image\debug;"

attrib -r ibm1s506.add replace with updated drivers remove floppy reboot 

OS/2 will boot the install program, copy files, etc bring up a hardware choices menu. No matter WHAT it sees your video card as, manually override it to VGA- not VGA GRADD, regular VGA. Worry about getting it right later, I have NEVER seen it be able to get a readable display from any video card except for generic VGA setting! besides, the best video drivers require FixPak 5 or higher to be installed, so you may as well hold off until then. The same goes for sound card, etc- tell it you don't have one. The only driver you want to worry about is the NIC driver you got earlier. You did get it, right? I know how to update them later under 3.0, but never had to under 4.0- so you're on your own if you ignored me.  For the software choices, disable VoiceType (voice recognition software, if you really want you can add it later) and do NOT install openGL at this point, the file on the CD is corrupt. I have a good copy of it I'll get to you later.

Under the networking, do not click on "install" if there's a blue > or red mark next to any areas. Get enough data that they all turn green first.

Once you click on install, files are copied and pretty soon it reboots.

Guess what? Somewhere in that process it copied the HD drivers from the CD again. Put in Disk0 when it reboots and go thru most of this BS again to get the updated drivers from the floppies to your HD. However, this time around none of them should be read-only so it's a little easier. The other good news is this is the last time you'll have to do this.

After you update the drivers and reboot, the install program finishes. It may reboot a few times during this process as it adds varions networking components

Congrats, the base OS is installed, but looks like crap since you're in 16color 640x480 mode. We need to fix that.

From here on, I'm assuming that you've installed to C: If this is not the case, change what I tell you to your drive letter. Make a directory called Utils inside utils, make the following directories: belfry sfix sdd configmaint finstall Run "uzs551x2.exe" and place its files in belfry you realize I'm having you do this from the command-line, right?  cd\ e config.sys "e" is the OS/2 text editor, welcome to modifying your config.sys file starting at the top and working your way down, make the following changes: IFS=HPFS....etc,etc change the "2048" to "1536" remove "programs," from the AUTOSTART= line programs is bad, if it's in there OS/2 will restart any program that were running when it was shut down. This is bad- if the program caused the crash, you will reload that program and most likly crash again!! in PATH= add "c:\utils\belfry;" to the end in LIBPATH= make ".\;" the first entry, remove it from the middle DISKCACHE=D,LW change to DISKCACHE=64 This is the cache for FAT drives(but not FAT32!), you probably only have one- your CD. LW turns on "lazywrite" aka write cacheing, and you're probably not going to write to the CD. If it is a burner, it already has a decent-sized cache built in anyway. The "d" means "default size" which is 10% of system RAM- RESOURCE HOG!!!!  so we change it to 64k in size. Trust me. basedev=ibm1s506.add /v  <-- add the /v (verbose, give you nifty info as you boot) basedev=ibm2flpy.add  <-- delete this line. It's for microchannel systems only- unless you have an IBM PS/2 from around 1988 this driver is useless. However, the line ABOVE it, ibm1flpy.add is needed!

Save config.sys

reboot 

Open an OS/2 session, either window or full-screen, doesn't matter. type unzip and hit enter. if you get an unknown command message, you fucked up and the unzip.exe you put in belfry wasn't in the path for some reason. Fix it before continuing.

anyway, in configmaint unzip cfgmt105

in sfix execute sfix144.exe

in belfry unzip dskxtr13.zip

in belfry, type this:

copy con xtract.cmd dskxtrct /s:%1 /t:c:\temp ctrl-z Congrats, you've made your first comamnd file- which is, for all intents and purposes a batch file. Make another one:

copy con svc.cmd set sfcdromdir=c:\temp c:\utils\sfix\service.exe ctrl-z You may not need to hit enter after the ctrl-z's, it may auto-save the file for you already....

make a directory called "temp" in the root of the drive

Remember how I told you I was assuming drive C: and it was your job to change it? Hopefully you listened, or you get to edit those 2 comamnd files- use "e" for this.

In the \utils\sdd directory, run ati-rage-sdd2se.exe despite its name, it's not only for ATI chipsets. Your video card's chips are probably on its supported list, however you can't use it yet- requires FixPak 5 (if Warp 4), FixPak 35 (if Warp 3) or higher first... We're just getting ready. Someone screwed up and slipped this into a FTP site- it's a pay only program with accelerated drivers, but they named it like it's a free one.  I don't expect it will remain there long!

unzip fi125us.zip in \utils\finstall

make the directory c:\temp

Note: this says FixPak 14, that is for Warp 4. If you're using Warp 3, substitute FixPak 40 instead.

use the xtract.cmd file to extract fixpak 14 disk images. This is done by: xtract for instance, on my system the images are drive h:\fixpak\w4fp14 and named xr_w014.1dk thru xr_w014.kdk my command is: xtract h:\fixpak\w4fp14\xr_w014.?dk

This will extract the floppy images to your hard drive, every disk has 1 file the same on it, so dskxtrct will prompt you for what to do- hit "a" for overwrite 'a'll or, if you prefer you can make 20 floppies... no fucking chance of that here, buddy! type exit to close the OS/2 session and return to the PM

click on drive icon, go to c:\utils\belfry and click on svc.cmd

This runs the service program and you go... the only thing that requires input is it want an "archive" directory, make it something uinque. I usually use "c:\archive" this is where the original files are stored in case the fixpaks fucks your system, which it won't. FP 14 has been out for 7 years, if there were problems with it, they would have been found already.

As it runs, let it overwrite all files EXCEPT for the five newer HD drivers that you've copied three times already, and you probably have their names memorized. If you let it "service" them, you WILL fuck your system. For them, click on "cancel" which really means "don't cancel, just skip this one file."

After service is done, reboot.

Delete all files in the \temp directory

unzip nsc461.zip into the temp directory

run install to install netscape 4.61

Why install this ancient POS? Because IBM decided to use it, along with their "feature installer" to install Java as well as a few other things.

After installing Netscape, reboot.

run fisetup.exe in the \utils\finstall dir

let it restart your desktop

delete files in temp directory

in the temp directory, unzip javainuf118.zip -d -o -d and -o are REQUIRED in order to recreate the directory structure

run the install program, and watch Netscape and the Feature installer (finstall) do their work.

Netscape will want to set up a user account- just click on "next" repeatedly until the "finished" button appears, then click it. Select the Java options you want, the only real option is do you want to install the unicode ont or not? I'd recommend installing it. reboot

Before you think Java 1.1.8 is ancient, bear in mind that version numbers don't correspond to Windows versions. Current Jave version, from Sun who is the authority on Java, is 1.4.2. Going back there were 1.4.1, 1.3.0- and IBM's 1.1.8 is the same as Sun's 1.3.0 so it's only 2 versions back. Anyway, we'll install 1.4.2 Release 5 later- but some of the newer network config programs run on Java, and they don't like 1.4.2. This is where IBM was smart- they realize that in a networked environment not all computers will run the same OS, so the only way to do a remote config of a workstation is a Java program that can run on any of them- OS/2, Linux, Sun or Windows- it doesn't matter what the LAN admin uses, he/she can config the workstation remotely.

After the reboot, edit config.sys namely, three lines make sure that the \java11 directory comes before \javaos2 in all three- otherwise your system will try to use java 1.1.0 instaead of 1.1.8 and later things will fail.
 * path
 * libpath
 * classpath

Java overwrote a few of the system files and downgraded them. Install Fixpak 14 again now, the same way we did earlier.

Once change: when it lists things to service, click on "services" then "uncommitted products" and commit FP14. This deletes the archive made when FP14 was first installed, freeing disk space. Applying multiple fixpaks without committing is a very quick way to hose your system for other reasons as well. From now on, every time you run the service utility, commit products before servicing anything!

After FP14 is installed, reboot

in \utils\sdd\en, open readme.txt hopefully your video card's chipset is in there! after you read it and get confused, go back (via command-line) to \utils\sdd type SET LANG=en_US setup SDD c:\utils\sdd\ c: NOTE: the trailing backslash is required. You will get a SYS3176 error without it! This installs the Scitech Display Doctor drivers for your video. Do what it says, and reboot on the red toolbox at the warpcenter (top of screen), select "system" and set your video to a realistic resolution and number of colors. If your chipset isn't supported, replace "SDD" with "VGA" Reboot. Yay, OS/2 looks decent now!  Toolbox-system-change screen resolution/color depth

The fixes in the "Peer" directory will update the Peer-to-Peer networking to the most recent level. Use xtract to extract the images, much like done with FixPak 40

The files in MPTN will upgrade the MPTN and (base)TCP/IP services, do 8415,8423 then do the TCPIP fix (next)

TCPIP has TCPIP fixes/updates. You need to have MPTN at 8421 or higher first, so install 8423

Go back to MPTN and install 8425


 * Install Warpin

I have had luck with on Warp 3
 * Install XWorkplace (recommended) there are newer versions out there, HOWEVER the one I included is the last one

I also included a few other utils which come in handy, such as Kon (hex editor)

You will need a hex editor to get things like Odin working on Warp 3. For info on Odin, do a web search- I've had much success getting Win32 programs working on OS/2 thanks to it. You also will need the hex editor to get Firefox 1.0.7 or 1.5 working under Warp 3. For instructions for both, do a web search for "Warp 3 Odin"