OS/2 Networking Installation Tips and Traps
By: Walter Metcalf
Since writing the previous article, I ran into a challenging series of problems in trying to set up my LAN
again. In fact I can only recall one or two other instances in my career where I had a more serious series
These problems were different in that they did not involve loss of data. Since I'm a bit of a fanatic about
backing up, my data was actually quite safe. However, there were several times where I almost
despaired of ever having my main system (hardware and OS/2) working again!
As I was struggling with some of those problems, I realized that many of you may have encountered at least some
of these problems while installing your network, I decided it would be appropriate to take a bit of a break and
list a few of the problems I encountered, how I finally solved them, and in some cases what you can do to
avoid them. Being forewarned may also save you some grief later on.
As happens in many cases, my problems began because I was doing a number of things to my computer all
within a short period of time, along with a certain amount of inexperience about the possible consequences
of each. Here's what had transpired prior to "D-day":
If each of these changes to the system had been made one at a time, with enough time between them to evaluate
the behaviour of each on the system, and prepare for the next, some or all of the trauma could have been
avoided. Unfortunately, the only thing I had much control over was the timing of the processor upgrade, and
at that point there was no reason to suspect any problems. (The processor itself gave OS/2 absolutely no trouble:
it just ran much, much faster!) Nevertheless, spacing out changes or additions to your systems is always a
- Set up a working LAN using 1 Lan card
- "The Cable Guy" came to install Internet on Cable (aka cable modem).
- Since my cable company won't install on LAN's, I had to take down my new network.
- I tried to set up LAN using 2 LAN card's (original + the one connected to cable modem).
- This means two domains instead of one.
- Upgraded the processor.
- I can't be sure when, but somewhere, and it could have been during the processor upgrade, the
motherboard BIOS decided for no particular reason to reprogram the IRQ and address locations
of all the Plug 'n' Play expansion boards in my computer.
Unless otherwise noted, all content on this site is Copyright © 2004, VOICE
- Network Adapter and Protocol Services (NAPS) Failed.
- Specifically this occurred immediately after the first reboot of the installation and was
the first clue something was wrong. Fortunately the fix is fairly straightforward, if a
- Garbage, usually in the form of software on the hard drive, whose versions are incompatible
with what you are trying to install.
- One of the Peer Services fixpaks is dated July 1999, and when you recall that the
Warp CD was manufactured in 1996, it's easy to see how installing Networking from the
CD could result in trying to install a file over a newer version of itself, leading
- Reinstall OS/2 from scratch. (Of course you must back up at least your system partition, and
then reformat it first.)
- Lock-up on network card driver.
- In other words, your computer hangs while processing the NIC driver during boot-up. This was a
a tough problem to solve, because there are a number of possible causes.
- Possible Causes
- IRQ (or other resource) Conflict
This is the most common cause. In fact it was ONE cause in my case.
- Bad (LAN) card
- NetBios protocol conflict
I'm not sure about the precise nature of the conflict (and I don't want to risk taking
taking down my system again by further experimenting!) It seems to be due to the
presence of multiple NetBios protocol specifications, OR, a version conflict between
the driver version and the installed version of OS/2 Networking and Peer Services.
- IRQ Conflict
- Either use jumpers (or DIP switches) on the expansion cards or the computer's BIOS
to resolve the conflict by making sure that each device in the system has a different
IRQ. Software programs that can help in identifying resources used by devices include
ScanPCI and RMView, which is included in OS/2 as a utility command.
(RMView command line parameters /IRQ and /DA are especially useful.) ScanPCI is
freeware. (See below for additional information on setting the BIOS.)
- Bad Card
- The only sure test is to replace it with an identical card that's known to be good. If
new card works, discard the old card.
- NetBios protocol conflict
- The trick here is to install as little as possible at first, and then upgrade. Here's
what worked for me. Your mileage may vary.
- Make sure there are no IRQ or other resource conflicts and that your hardware is
- Install all the cards you will need in your final system into your computer. (You
might as well install and configure OS/2 for the hardware it will eventually have
- Install and configure OS/2 up to the Networking Page. (See Figure 1.)
Figure 1. (Click to expand.)
- Using Advanced Install, select Networking and Protocol Services. For each Lan card
in your computer add an adapter. For each adapter add the TCP/IP protocol. For
the first adapter only add the NETBIOS protocol as well.
Select TCP/IP services, and accept all the defaults. (You will come back later and
configure the TCP/IP).
Select User ID and Password and enter valid values.
- As far as I have been able to determine, that is the minimum you can configure for Peer
Services (aka File and Print Client) for the install to succeed. (Note: it should be
possible to use a different protocol from NETBIOS: I just have not tried it.)
Computer Reprograms Cards
Next week: Setting Up a LAN on Warp 4, Part 3
1 The MPTS install program actually generates a warning message in that instance. The main network install program is apparently less forgiving.