Warp Installation Notes v1.1.2

By Frank McKenney

About The Warp Installation Notes

Caveat: the material included has been compiled from verbal comments, e-mail messages posted in public locations (e.g. the Internet NewsGroups), the occasional manual, and my own interpretations of all of the above. I do not have access to all (or even most) of the equipment and software described (I had to sell my favorite 486DX 33&1/3 with 6.7 Mb RAM, two 4300 Baud serial ports, an ESDI adapter using IRQ1, and a 108 Mb RLL+ drive), so I am unable to personally verify all of its content. While I have tried to avoid excessive jargon whereever possible, describing an OS/2 installation is a technical topic and requires a certain number of technical terms. I also make the occasional typographic eror...

...and the occasional TELEPHONE NUMBER ERROR: Hints v1.1.2 is being sent out specifically because the telephone number I supplied for the Aztech BBS in Area code (501) is NOT repeat NOT the Aztech BBS, but a (now harassed) Southwestern Bell customer in Arkansas who has been receiving odd calls that abruptly hang up. PLEASE DO NOT USE THIS NUMBER. If I obtain a correct number I will include it in v1.2.

In all cases, you should use your own best judgement as to which of the following material applies to your situation. Corrections, more detailed explanations, and additional material will be welcomed. If, for example, you see a BBS telephone number mentioned but know of an FTP site for the same information, please let me know. We're all in this together.

Note re changes: I started marking the 1.1 changes with a vertical bar at the left margin. This would have added a nice touch, but it turned out to be impractical. When I finally realized that I'd need to mark more than 75% of the document, I went back and removed them. Maybe the changes for v1.2 won't be as extensive (;-).

Note re v1.11 release: Short form: oops! Long form: I posted Hints v1.1 without realizing that I had not completed revision on a section about pausing CONFIG.SYS processing so that device driver messages could be seen. As it turns out, the technique I had used under 2.1 and 2.11 for doing this turned out (a) to be narrower in scope that I had realized, and (b) to work differently under Warp. I have removed the text, but the need for such a facility is still there. Suggestions for a workable technique would be welcomed.

One of the changes I hope to make for v1.2 is to break out a separate section for new drivers. As many of you have noted, there are a large number of problems related to drivers, and it might be easier to simply include a section devoted to driver-related problems.

Let me mention that my purpose in putting this document together was to get users operational under Warp as soon, and as easily, as possible. Consequently, I'm not concerned with making sure I have the description and location of the absolutely latest and greatest driver for the IBM XVXGA adapter. I'm perfectly willing to leave that task to others.

What I do want is to be able to provide driver information for driver-related problems that might prevent an installation or cause serious performance problems under Warp. I'll settle for any driver that will let the user successfully install and run without significant errors and with reasonable performance.

Changes, additions, and comments should be directed to rrs0059@ibm.net or mailed to:

                             Frank McKenney
                           McKenney Associates
                          3464 Northview Place
                        Richmond, Virginia  23225
                             (804) 320-4887

General Hints, Suggestions, and Warnings

I have several pieces of "non-standard" (e.g. not officially supported) hardware in my system. As a result, I had always needed to do some tweaking after an OS/2 installation before everything was running smoothly (and the Warp betas were just as bad). I did not look forward to installing Warp GA; in fact, I set aside a whole day to do it.

I was <almost> (but not quite!) disappointed when OS/2 Warp GA installed from its CD with no problems. Instead, I spent the rest of the time playing with the IBM Internet Connection software, IBM Works, and the other BonusPak applications. Result? The installation <did> wind up taking all day (;-).

However, certain configurations do run into problems installing Warp GA. I have listed a number of known problems and workarounds in the following pages to help those of you already stuck, and to forewarn those of you who might need new drivers prior to starting up. I'm hoping that this will result in more people wasting(;-) their time <running> OS/2 Warp and fewer people wasting their time pounding on walls or flaming on the Usenet newsgroups because of snags in installing Warp (;-).

Read the Documentation

Before starting your installation, read the documentation. I know, you've all heard it before. It's a pain, it takes time, and the computer and OS/2 Warp are just <sitting> there when they could be multitasking their little hearts out. I'm still going to recommend it, especially for those of you who are installing OS/2 for the first time. Specifically, you should make sure you cover: Before starting your installation, read the documentation. This includes:

The new "User's Guide to OS/2 Warp", and in particular,

  Chapter  1 - Before You Begin
  Chapter  2 - Using Easy Installation
  Chapter 14 - Solving Installation Problems
  Chapter 15 - Solving System Problems
  Chapter 16 - Video Procedures
  Chapter 17 - Using Advanced Installation
  Chapter 18 - Setting Up a Hard Disk
  Chapter 19 - Special Hardware Considerations
  The README file      (root drive of the OS/2 Warp V3 CD)
                       (Diskette ?? for the Diskette version)
  The README.INS file  (Warp Installation Diskette)
  The README.CID file  (Warp Installation Diskette)

Manufacturers' README files for any device drivers <not> included with the OS/2 Warp GA package.

(other suggestions will be welcomed).

Hardware-Specific Information

If you have owned a computer for any length of time, you're probably aware that it has internal quirks that tend to show up an the most inconvenient times. You install your new SuperFast! display adapter, it doesn't work, and you suddenly discover the world of "IRQs" and "I/O Addresses" that had remained hidden under your computer's covers for <years>... (and you wish it would go back again (;-)).

A complete description of each part of your computer is a useful thing to have around. It helps in insurance claims, and it can help you see possible sources of conflict if your machine sudddenly freezes up during Warp installation. Such a list would include descriptions of the System Board (processor, chipset, RAM, BIOS type and date), disk drives (manufacturer, model, size, interface), monitor (manufacturer, model, suported frequencies and resolutions), and adapters (manufacturer, model, IRQs used, I/O addresses used).

An organized person has this list in a word-procesing document, keeps it up to date, and periodically prints out a copy and files it. This is not the only approach; for example, many of us compile this list by waiting until we have a problem, then opening up the computer, pulling each adapter, and then searching desperately for the manual to tell us whether the IRQ is set by jumper J12-A or J16-A.

Just keep in mind that if you do run into a problem, this information will be requested by IBM OS/2 Support, and will be appreciated by anyone else you ask for assistance. Warnings

• 1. Before performing ANY OS/2 maintenance, including the installation of OS/2 Warp GA, be sure to have a CURRENT backup of ALL of your programs and data.

• 2. Before performing ANY OS/2 maintenance, including the installation of OS/2 Warp GA, be sure to have a CURRENT backup of ALL of your programs and data. This is not a typo; it is a redundant copy of my text for backup purposes (;-).

• 3. Have a set of <tested> OS/2 bootable diskettes ready with the usual system utilities (FDISK, FORMAT, TEDIT, etc.). Be aware that a set of (e.g.) 2.11 bootable diskettes created with BOOTOS2 will not be able to run some of the system utilities <from> an installed copy of Warp due to version level differences.

Beta Testers

Remember that warning when you received your Beta code that you would have to re-format your Beta partition before installing Warp GA? Yes, it's a pain to do. Yes, it would be nice if IBM would dedicate the resources to testing all possible combinations of Beta1, Beta2, Gamma, and Gamma+ systems with GA installed over them, but lazy as I am, I'd rather see the time spent on improving the base operating system.

It's not that GA-over-Beta is guaranteed to fail. It's that mixing various levels of similar-but-not-identical code creates an incredibly large set of possible combinations of software, and the problems that result are likely to (a) be subtle, (b) remain hidden for some time after Warp GA is installed, (c) be difficult to pin down, and (d) be highly individualized (one of a kind).

Imagine the long-term results of (say) an OS/2 INI file mangled by the Warp Beta code being passed on to Warp GA. Result: much time could be spent, both by IBM and you, in tracking down a problem that could have been avoided by a clean install. There are already enough possibilities for conflicts, don't add new ones.

Have Someone To Talk To

Finally, if you're only moderately technical but know someone who is familiar with OS/2, it doesn't hurt to let them know that you're about to start an installation and <might> be calling on them for help if you encounter problems.

And even if you <are> intimate with all the idiosyncracies of OS/2 Warp, it still doesn't hurt to have someone else to share your problems with - or to whom you can announce that you did the whole thing in 45 minutes flat (;-).

The Notes...

         o Unable to find CD-ROM during install
         o Various odd symptoms with PTI IDE drive
         o Install from CD-ROM locks up
         o No sound from PAS-16
         o Unable to create OS/2 bootable partition
         o Hard Drives using OnTrack Disk Manager
         o Mouse pointer displaced - Dell
         o OS/2 hangs after installation
         o System stops booting because of problem with COUNTRY.SYS
         o Problems recognising various CD-ROM drives
         o Message - HDD Controller Failure *
         o Installation of Warp fails with SYS3175 typically around diskette 1 *
         o #9GXEPRO - problems with display esp. with Windows sessions *
         o Canon Bubblejet - unable to find printer drivers *
         o Boot message - "line ?? is unrecognizable" following MM uninstall *
         o Trap 0003 trying to use certain types of CD-ROM *
         o Warp Installation from CD fails - no matching driver found *
         o Problems using MS Windows communications programs *
         o Printer does not print *
         o Floppy drive does not recognize when a diskette is replaced *
         o Performance - Warp boot seems to take longer than expected *
         o NCR SCSI adapter not recognised *
         o MIRO 20SD - S3 864 - unable to use higher screen resolutions *
         o Various OS/2 Error Messages *