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
This is a second draft. Please send comments, updates, and suggestions to:
Frank McKenney (rrs0059@ibm.net) Be warned that flames will be automatically routed to an attack-trained copy of Warp's UltiMail/2 Lite; on detecting a flame it will promptly trigger a SYS3175 self-destruct sequence, taking the offending missive with it.HTML formatting of this document was performed by Jon Seymour.
Please report formatting or broken link problems to: jon@zeta.org.au.
Refer to this link for information about the location of the most recent version of this document.
The most recent ASCII version of these notes will usually be found in the Hobbes directory:
ftp://ftp.cdrom.com/os2/warp/info/(wrpin???.zip)