FixPak, What's a FixPak?- by Thomas Chamberlain

Imagine this: you've just bought your nice, new, shiny copy of OS/2 Warp and are ready to get to some 32 bit, Multitasking, Multi-Threaded, Crash proof action. After jumping over the hurdle of the 20 disk install you have but a short reboot to go and you're on your way. Now, the reboot has taken place, you jump into OS/2, BUT WAIT! Where's your CD drive? After a few attempts at fixing the problem it becomes fairly obvious OS/2 isn't going to see your CD drive no matter how many ways you try to tell it to. Even worse, other strange problems start to reveal themselves. So, what do you do now? You get a FixPak!

What's a FixPak?

A FixPak (formally known as a ServicePak for all you long time OS/2 users) is a program that IBM releases to bring your system up to date with current releases and fix bugs in OS/2 (IBM calls them APAR's which stands for "Authorized Program Analysis Report" but that's just because IBM likes using long technical terms). IBM releases FixPaks about every month internally but very few officially make their way to the outside world. Although many of them get leaked to the Internet it's usually not a good idea to use these.

How Do These APAR Things Work?

How do FixPaks come about? Well, you (and usually many other users like you) report your problems to IBM Central who then reports them to the programmers who then create a FixPak (actually this process is far more complex which is the cause of many APAR's getting lost in the mix).

Your bug must meet one of five requirements before being considered an APAR. It must:

  1. Cause data corruption.
  2. Cause a regression of supported function, major application, or device driver compatibility.
  3. Cause a frequent system hang (such as Trap Errors).
  4. Cause a serious visual problem.
  5. Cause a significant portion of hardware or software not to function.
If your bug "passes" all those tests it becomes eligible for a "Fix in Current" solution (A.K.A. a FixPak). If not, it's sent to another group who will hopefully provide a fix in the next released version of OS/2.

How Do I Get a FixPak?

FixPaks are fairly easy to obtain for just about anyone. For those of you who are on-line here are a few places to pick up the latest FixPaks:

America Online users should go to the OS/2 Forum (Keyword: OS2) where the FixPaks can be found under the Patches/Fixes section of the File directories.

CompuServe users need to go to the OS/2 Support Forum (Go OS2SUPP) where the FixPaks reside in the IBM Files directory.

Prodigy users are off to the OS/2 Club (Jump: OS/2) where the FixPaks are a bit hidden. You have to "browse Files from IBM," then go to IBM Files, then the FixPaks are in the Fixes section.

For those of you on the Internet, OS/2 FixPaks can be found on the hobbes FTP site. Get there by FTPing to hobbes.nmsu.edu and switching to the /os2/patches directory (you'll have to go to the /os2/ibm/cset++ directory for Loaddskf.exe file--more on that and the other files later). Alternatively, you can FTP directly to IBM's site at service.boulder.ibm.com and look in the /ps/products/os2/fixes/v3.0warp/ directory.

If you have a modem but don't have access to any of the above on-line services you can call the OS/2 Shareware BBS at (703) 385-4325 or IBM's BBS in your local area. When you log on go to the File Directories by pushing "F" at the main menu. Then Locate a file with the "L" command. When asked for a string to search for, enter "FixPak".

Finally, If you don't have access to any of these sources you can try IBM Technical Support. They've been known to send FixPaks to needy people in the past.

What Files Do I Download?

These are the files you'll need to download to make the FixPaks work for Warp:

What Do I Do Once I Get the Files?

Each of the above files requires a floppy disk (with the exception of Loaddskf.exe) so before you go anywhere you'll need 9 blank disks. Once you've got them, insert your first disk, go to an OS/2 Command line, change to the directory containing the above files, and type: "LOADDSKF CSFBOOT.1DK A:/F". Then do the same for the second disk (Replacing "CSFBOOT.1DK" with "CSFBOOT.2DK" of course). This will create two boot disks. After that do the same thing with all of the XR_W0xx files ("LOADDSKF XR_W0xx.1DK", etc.). Loaddskf.exe will load the .xDK files onto disks and uncompress them. One last warning, label the disks!

Applying the FixPak!

Now comes the moment of Truth. There are two ways to apply a FixPak to a System. The first (and the one I find to be the easiest) is to insert the first boot disk (CSFBOOT.1DK) and type "A:\SERVICE" at a command prompt. From then on you'll be prompted what to do. It is important to remember the "Fix Disks" are the XR_W0xx.xDK disks and that the "Boot Disks" are the CSFBOOT.xDK disks. You'll be prompted for them by both names during the process for some reason.

The second way is also fairly simple--just insert Boot Disk 1 into your A: drive and reboot. From then on you will be prompted by the program. And that is all there is to applying a FixPak. Luckily IBM has made this process quite a bit easier since the first FixPak released (FixPak #5).

What If It Doesn't Work?

IBM is good about applying the most recent FixPaks to their most recent releases to OS/2 Warp. So in some cases your nice, new, shiny copy of OS/2 Warp might already be fixed. If so you'll get a message saying something to the effect of, "No Files to Service." If so, don't worry, it means you're already taken care of. You should still look for future FixPak releases but for now your up to date.

Why Won't Galactic Civilizations Work?

This brings us to the recent release of FixPak #16--a FixPak that has already become infamous for its problem causing abilities. FixPak #16 made many programs (Galactic Civilizations, IBM Works, etc.) unusable and hence was recalled by IBM. IBM has released a replacement for FixPak #16 (FixPak #17) that supposedly fixes the problems caused by the original. Look for it in the places mentioned earlier in this article.

But I Already Installed FixPak #16!!!

Lucky for you (and me too since I also installed FixPak #16) there is a "Back out" procedure for FixPaks. IBM includes a whole list of ways to back out of the FixPak depending on what your individual problem is. The important thing to remember is to have your original installation disks handy. Many of the processes require that the OS/2 Installation disks be used. Look for complete instructions in the FixPak documentation files.

Anything Else?

Just a warning: there are two philosophies towards FixPaks. One says, "If it ain't broke don't fix it!" I don't subscribe to this school of thought for one simple reason: how do you know it ain't broke? In these days of ultra advanced Computer Operating Systems something could be silently destroying your computer and you wouldn't have the slightest idea it was happening until it was too late or you just might not be getting the performance you could be. My theory is, "FixPak's have an uninstall option so what do you have to lose?"

As for you, it's up to you to decide which philosophy you follow. It is generally a good idea to wait a couple of days after a release is out, watch the newsgroups, and if problems are reported with a new FixPak, by all means stay away from it (unfortunately my impatience will always make me one of the problem reporters rather than one of the silent listeners). A FixPak is like any upgrade in the end, you have to use your own discretion when deciding when to use it and when not to and no one (including me) can tell you how to handle that.

And if you ever need a guide, my e-mail box is always open.

update 1/27/96: I thought I'd add this little update to inform you that the replacement for the now infamous FixPak #16 has just been released as of today. After a two week delay (IBM's original claims was that the fix for FixPak #16 would be out within a couple days of the original being pulled), FixPak #17 has hit the FTP sites and on-line services everywhere. Although it's too early to detect any problems with this newest addition to the FixPak family those who have already installed it say it appears to have none of the problems that plagued FixPak #16. Also, you may be interested to know that this FixPak has a "fix" for the Single Input Queue that has irritated many users of Warp.
Thomas Chamberlain is a 17 year old Student who has been using OS/2 for a little over a year now. He's a member of Team OS/2 and can usually be found conferencing with his fellow OS/2 users in the America On-Line OS/2 Forum.

Send a letter to the editor.

Our Sponsors: [BMT Micro] [Indelible Blue] [Mt. Baker Software] [Whitestone]

Contents | Previous Article | Next Article

This page is maintained by Falcon Networking. We welcome your suggestions.

Copyright © 1996 - Falcon Networking