From: Edmund Reinhardt
If you are planning to run both Warp and Client Access, here is something you should be aware of.
It seemed so simple: install WARP and Client Access (V3R1) on my Thinkpad. But, when I did, I got a very strange result?the WIN-OS2 and DOS-OS2 interfaces ceased to work!
This is not the fault of WARP or Client Access?together they work perfectly! However, people who get WARP also get the BonusPak, which includes an Internet connect package. Installing the Internet connect package creates the problem. The TCP/IP for DOS component of the Internet connect package uses a Virtual Device Driver (VDD) that clashes with the Client Access VDD.
The problem is that they both use interrupt 60, and Client Access gets the interrupt first. If the interrupt isn't in-tended for Client Access, it simply throws it away?to the consternation of DOS.
There are fixes available. For V3R0M5, it is SF20242; for V3R1M0, it is SF22405. Hopefully, this will allow you to avoid feeling the pain (and confusion) that I have just experienced.