OS/2 2.0 Tech Support Document

Patrick Steil - OS/2 Application Assistance Center

May 20, 1991 - Release 2

GO TEAM OS/2!!!!

Disclaimer: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

Also, this document could contain technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the document.

This document does NOT contain IBM officially tested and proven resolutions to problems. The items contained in this document are provided as a help to those having problems (primarily in getting OS/2 installed on incompatible hardware). The information that appears here has been gathered from many different sources within and outside of IBM.

NOTE: All additions from Release 1 are marked with a "|".

GENERAL INFO
Phone numbers: IBM NSC BBS               404-835-6600  8-N-1 IBM SERV(Hardware Maint)  800-426-7378 OS/2 BBS Info             800-547-1283 OS/2 Ordering Line        800-3IBM-OS2 OS/2 Defect Support       800-237-5511 IBM's National Info Serv  800-IBM-3333 PS HelpCenter             800-PS2-2227

Always Technology         818-597-9595 Gateway                   800-523-2000 HP Customer Service       800-752-0900 Trident BBS               415-691-1016  (PM SVGA drvs) Trident BBS               203-483-0348  (PM SVGA drvs) Trident Tech Support      415-691-9211 Washburn & Co.            716-248-3627  (AMI Bios Upgrade) 800-836-8026 (AMI Bios Upgrade)

New Packages for GA code: BVHSVGA   - For video cards with WD C30 & C31 chips IBM2FLPY  - This is a fix required for PMTAPE to run IBMS1506  - Replace ST506 driver for OS/2 GA code OS2KRNL   - Autocad, WORDPROOF, and SideKick Plus fix ONLY PMSPL     - Fixes printing to a non-OS/2 print server SOMFIX    - Better synergy for WorkPlace Shell Api's  VEMMGA     - Fix for using EMS with Lotus 123 2.3 and others VSVGA     - For TSENG cards with batch code of TC6059AF only RESTKN    - DOS device driver that will reset Token Ring cards Sources for more help/information: - CompuServe - IBM OS/2 Bulletin Board - IBM NSC Bulletin Board - Prodigy - OS/2 README FILE - OS/2 TNT DOCUMENT from IBM - HONE: - NATIVEINFO(not much info yet on GA yet I'm sure) - ASKQ - IBMPC FORUMS: OS2OEM  -  OS/2 2.0 INFO ABOUT RUNNING ON OEM HW   VGACLONE - INFO REGARDING OEM VIDEO CARDS OS2V2SDK - GENERAL OS2 INFO FROM DEVELOPERS OS2V2BUG - OS/2 2.0 BUG REPORTS OS2V2DEV - GENERAL OS2 INFO FROM DEVELOPERS OS2V2APP - PROBLEMS RUNNING APPS ON OS/2 2.0 OS2V2SHL - WORKPLACE SHELL INFO OS2DSETS - OS/2 2.0 DOS PROGRAM SETTINGS OS2WSETS - OS/2 2.0 WINDOWS PROGRAM SETTINGS

GENERAL INSTALLATION PROBLEMS
Installation bugs/fixes:

1. 5.25" diskette problem:

Symptom: Install program asks for disks 16, 17, and 18 during 3.5" diskette install.

Problem: The CMOS was not changed to view the A: disk as a 3.5" 1.44MB disk drive.

Resolution: Run the hardware SETUP program for the machine. If running AMI Bios, Press the DEL key at system bootup time. Press ENTER on the first selection "Standard System Setup". Press ENTER on the "warning screen". About half way down the screen is the A drive setting. Use PGUP or PGDN to select 1.44MB. Hit ESC. Choose "Write to CMOS and EXIT" with the cursor, press ENTER. Answer 'Y' to the question "Write to CMOS and EXIT?".

From here the machine should be setup correctly. The user can then proceed to place the OS/2 installation diskette in drive A and proceed with the install again.

2. AMI Bios version problem

Symptom: Various install problems. The suggestion to upgrade these items should always be made. Possible SYS2025, and SYS2027 at disk#1.

Problem: Machine must have BIOS dated 5/9/91 and keyboard controller chip version KF. The following information will be seen by the user at (cold)boot time: AMI BIOS and AMI BIOS Plus: aaaa-bbbb-mmddyy-Kc AMI Hi-Flex BIOS: ee-ffff-bbbbbb-gggggggg-mmddyy-hhhhhhhh-c If an IDE hard drive is in the system, "mmddyy" should be 040990 or later. For other drives including MFM, RLL, ESDI, or SCSI, "mmddyy" should be 092588 or later. Controller chip version can be located on the bottom of that same screen. Check the last digit in the long stream of digits (the "c" above). The last digit will probably be either be 8, B, D, or F. The required level should be F for OS/2 v2.0 or v1.3. Pressing the INS key during bootup should cause this info to stay on the screen.

Resolution:
 * 1. Call Washburn & Co. to order new versions.
 * 2. Bad diskette. Format new diskette and diskcopy failing diskette to this new diskette.
 * 3. Clean, swap or replace the diskette drive.
 * 4. Disable system memory cache during installation.

3. Phoenix Bios version problem

Symptom: Same as #2 above.

Problem: Not yet determined what the required level of BIOS is, but Version 1.02.05D seems to work good on a variety of machines.

Resolution:

Contact hardware vendor, or Phoenix for more info. If you do not have the above version, please call Phoenix and get to at least that level.

4. IBMS1506.ADD problem

Symptom: Not sure at this time.

Problem: Not sure at this time.

Resolution: Get new IBMS1506.SYS.

5. Memory problems on a Model 90/95

Symptom: Memory problems

Problem: Downlevel processor card/memory riser card.

Solution: If your processor card has part number 84F9356 then it should be replaced.(ECA-053) If your memory "riser" card is part number 84F8157, 84F9356, or N33F4905, then it should be replaced.(ECA-084)

6. Install hangs at "Loading please wait..." message.

Symptom: Install hangs at "Loading please wait..." message.

Problem: Possible BAD memory.

POSSIBLE Resolution: Get new SIMMS. Make sure that the new SIMMS are matched in speed and type.

7. At Disk#1 install reboots computer or internal processing error

Symptom: When diskette #1 of install process is inserted in drive the machine will reboot, or cause an internal processing error.

Problem: Bad memory.

Resolution: Replace memory with good memory.

8. FDISK errors, slow installation, grinding noise from HDD.

Symptom: FDISK unsuccessful error on Disk #1, VERRYYYY slow installation, or unusual noises coming from hard drive. May also experience an "Internal Processing Error" within the first two diskettes.

Problem: Incompatible hard disk driver. This problem appears on AT bus machines with RLL, MFM, and ESDI drives. If the hard drive has more than 1024 cylinders, be certain your hard disk adapter's sector translation mode is enabled.

Resolution: If you are unsuccessful in getting OS/2 installed because of the above problem, please follow these next steps on Diskette #1 of OS/2 install set. (You should make a backup DISKCOPY of your install diskette before modifying anything). Using a text editor, modify the CONFIG.SYS file on Diskette #1(the copy). Make the following modification to CONFIG.SYS: 1. Replace BASEDEV=IBM1S506.ADD with REM BASEDEV=IBM1S506.ADD. Boot the Installation Diskette, and proceed through the installation procedure through the first five diskettes, then reinsert the Installation Diskette as directed. Then after files have been copied from the Installation Diskette the system prompts you to remove the diskette and press ENTER to reboot. Do so, but immediately reinsert the Installation Diskette as soon as the SCREEN clears. Insert Diskette #1 and press ENTER when prompted. At the next screen, press ESC. At the OS/2 command line, type: RENAME x:\OS2\IBM1S506.ADD IBM1S506.XXX COPY x:\OS2\IBMINT13.I13 x:\OS2\IBM1S506.ADD replacing x: with the appropriate drive if you are installing elsewhere. Remove Diskette 1, then press CTRL-ALT-DEL to reboot to finish installation. Installation should flow smoothly from here on.

9. COUNTRY.SYS not found

Symptom: COUNTRY.SYS error message at bootup of first two diskettes or after first five diskettes, and reboot of machine by installation program.

Problem: Invalid device driver for hard disk being used. Seems to occur more often on non-IDE/SCSI drives. More prevalent on ESDI/MFM/RLL drives. Country.SYS error messages almost always point to OS/2 not being able to recognize the hard drive media.

Resolution: Follow instructions in #8 above.


 * 10. COUNTRY.SYS not found

Symptom: COUNTRY.SYS not found error message while installing.

Problem: Possible conflict with another device on the machine.

Resolution: Disconnect any tape backup, CD-ROM or other devices not needed for installation. Reconnect once installation is complete.


 * 11. COUNTRY.SYS not found on a P70

Symptom: COUNTRY.SYS not found error message while installing on a P70.

Resolution: Contact your IBM CE for ECA068. This is indicative of a problem recognizing the disk. ECA068 should remedy this.


 * 12. ERROR number 60002,9084

Symptom: Trap on installation with error message 60002,9084.

Problem: Possible bad memory.

Resolution: Try removing SIMMS one at a time(if possible) and try installation until it works. Otherwise have your hardware dealer/service personnel check and/or replace memory SIMMS.


 * 13. Installation locks up at start of graphical install

Symptom: After first set of diskettes is installed and installation program warm-boots the computer, the graphical install portion does not appear. Rather the machine hangs at this point.

Problem: Video card may be in set for non standard VGA mode, or autosense capability on the card not working correctly for OS/2.

Resolution: Make sure video card is in VGA mode with auto-sense turned off.


 * 14. Problem installing on a ZEOS notebook machine

Symptom: Installation fails on this machine. Can be attempted on other machines that also hang very early during install.

Problem: Unknown at this time.

Resolution: The customer must have access to (a running version of) OS/2. A patch must be applied and it MUST be applied using OS/2. The instructions for applying the patch follow:
 * 1) Make a backup copy of the INSTALL diskette
 * 2) With the diskette in drive  and from the A: prompt type: PATCH SYSINSTX.COM
 * 3) When asked for the offset address: 96AF
 * 4) On the line shown, enter 45 to replace 44 as the first byte in the line and
 * 5) When asked if you want to continue patching: N
 * 6) When asked to apply patches: Y
 * 7) At the  prompt type: SYSINSTX A:
 * 8) Install OS/2 using the new patch diskette.


 * 16. AOX Systems

Symptom: AOX system has problems installing or booting OS/2.

Problem: Outdated "flash-prom" code.

Resolution: Call AOX support and ask for the latest "flash-prom" code upgrade.


 * 17. Gateway 2000 machine locks up

Symptom: Machine locks up. No further details available at this time.

Problem: Micronics motherboard with revision level E or prior needs to be upgraded to level F.

Resolution: Call Gateway for upgrade. 800-523-2000.


 * 18. Receiving 111 Error message with MicroChannel machine

Symptom: Receive a 111 message at system bootup time on PS/2 machines.

Problem: Channel Check on the microchannel. A card installed in your system has detected some sort of memory problem. This does not necessarily point to actual RAM SIMM problems but can be generated by any card on the system.

Resolution: Have system checked out by IBM SERVICE. See phone number above for outside customers.


 * 19. Not enough RAM installed

Symptom: May vary.

Problem:

1. SYS0318:Message file cannot be found. (customer had 2 MB memory)

2. Sys????:The system cannot load the DLL, QCALLS... (customer had less than 4 MB memory)

Resolution:

Install at least 4MB RAM Silly! May need to disable system cache also? If 4MB is installed.

HARD DRIVE PROBLEMS
SCSI Hard drive driver support: Note: These drivers can be found on diskette #8 in a file called DASDDRVS. The above drivers can be unpacked with the following command: UNPACK A:\DASDDRVS \OS2 /N:xxxxxxxx.ADD Add the following statement in the CONFIG.SYS: BASEDEV=xxxxxxxx.ADD Once these steps are taken, reboot the machine to initiate the appropriate support.

Following are a number of notes about usage, and about potential compatibility problems with the microcode levels on various adapters and devices.

Adapter: All Adaptec adapters

Note: SCSI hard disks must be configured as SCSI target ID 0 or 1 to be able to start up from that hard disk.

Adapter: Adaptec AHA-154x

Drive: IBM 0661 - 320MB SCSI

Note: Adapter BIOS will not recognize the drive as Target 0 or 1 (Drives 80, 81). For OS/2 2.0, the drive can be used as a non-startup drive.

Adapter: Adaptec AHA-174x

Drive: IBM WDS-3180 - 80MB SCSI, IBM WDS-3160 - 160MB SCSI

Note: Adapter will not recognize these drives when configured in 'STANDARD MODE' (AHA-154x emulation). Instead, the AHA-174x adapter should be configured in 'ENHANCED MODE'. This mode is supported by the OS/2 2.0 drivers, and the problem does not occur when the adapter is operating in enhanced mode.

Adapter: Future Domain TMC-850/860/875/885 w/BIOS revision level 7.0. Future Domain TMC-1660/1670/1680 w/BIOS revision level 2.0.

System: IBM Models 35 and 40 when the Future Domain adapter is controlling the startup diskette.

Note: Will produce the message, "Disk read error has occurred" when you attempt to start the Installation diskette. Contact Future Domain for a free BIOS upgrade.

1. AMI SCSI Adapters

Symptom: AMI "Fast Disk" and AMI "Fast Disk II" SCSI adapters are incorrectly recognized as Adaptec adapters.

Problem: At the final restart after the installation is complete, delete from the CONFIG.SYS file, any line with "BASEDEV=AHA1xxx.ADD" (where "x" can be any character). Ensure the line, "BASEDEV=IBMINT13.I13," appears in the CONFIG.SYS file.

2. Problems with Always IN2000 SCSI adapter

Symptom: Problem:
 * Internal Processing Error.
 * Bios adapter with bad bios. Bios level of 3.06A
 * or 3.20 should be upgraded. The current BIOS level is
 * VCN:1-02 and works with OS/2 v2.0.

Resolution:

Upgrade to current BIOS level of VCN:1-02. Also, Always IN 2000 SCSI Host Adapters may require an EPROM upgrade from Always for $20 to operate with V2.0. The revision level should be 2.5-2.7 to work properly. The dividing line is not clear, and at least one customer was not helped by the EPROMS, though several others were. Always suggests installing the EPROMS and re-formatting the drive - seems to be some problems installing over DOS partitions. Always can be reached at 818-597-9595. The customer who was NOT fixed by the EPROMS was unwilling to re-format. Symptoms of the problem are varied, but the most common is an FDISK error on the second diskette.


 * 3. Bernoulli Boxes

Notes:

44 and 89MB drives will work if connected to any other SCSI card other than Bernoulli's own card. The drive will work as a large diskette and will be non-bootable.


 * 4. PROCOMM+ SCSI MCA adapters do not work

Resolution:

Contact PROCOMM for details on OS/2 support.


 * 5. Slow SCSI support or missing icons

Symptom:

Slow hard drive speeds and possibly no icons appearing. Other data corruption possible.

Problem:

Hard drive and adapter card settings not correctly matched.

Resolution:

Ensure that hard drive and card are matched in their settings of SYNCH and ASYNCH mode.


 * 6. IBM 16-bit SCSI cards(early versions)

Symptom:

Early versions of the IBM 16-bit SCSI adapters may experience problems and report erroneously that the device is not functioning.

Resolution:

Replace SCSI card with a card with updated microcode.


 * 7. Quantam Plus Hardcard

Symptom:

Numerous failures under 1.3 and 2.0.

Problem:

Microcode lower than 2.6 will cause numerous failures under 2.0. Also, drive cannot be second disk if installation will take place on the hard card drive.

Resolution:

Call Quantum about EPROM upgrades. Note: They will deny the problems being theirs!

VIDEO PROBLEMS
IBM Tested Video Cards:
 * Orchid ProDesigner IIs by Orchid Technology (ISA and MCA versions)
 * Trident TVGA by Trident Microsystems, Inc. (8900b and c levels)
 * STB PowerGraph VGA by STB Systems, Inc.
 * Video Seven VRAM II, by Video Seven
 * Boca Super VGA by Boca Research Inc.
 * VGA Wonder XL Series by ATI Technologies, Inc.

1. Western Digital PVGA1D video card

Symptom:

C00005 message on screen.

Problem:

Happens on above video card (video chips: Western Digital C30 & C31) with 1 MB installed.

Resolution:

Get the new BVHSVGA package.

Replace the existing BVHSVGA.DLL on the system -- in the \OS2 directory. Do this by booting from the OS/2 2.0 install diskette, insert disk #1, press ESC at the next prompt. At the A: prompt place the diskette with the replacement file into the drive and copy this .DLL into the \OS2 directory on the installed partition.

2. Out of Synch/Install problems

Symptom:

May vary

Problem:

Addressing of card in 16-bit mode.

Resolution:

Switch card to 8-bit mode if available. This will probably involve setting a jumper, or dip switch according to the documentation that comes with the card.

3. Video Cards using TSENG TC6059AF chip(ET4000/see below)

Symptom:

Problems going from DOS SVGA -> PM VGA Desktop

Problem:

Some hardware register not handled correctly by the GA version of the VSVGA.SYS driver.

Resolution:

Get new VSVGA.SYS.

4. Trap E switching a DOS fullscreen to a window

Symptom:

When I window a DOS fullscreen running in SVGA I often get a Trap E. Will be prevalent on overcommited (low-memory) systems. The PM driver you are using can also have an effect.

Solution:

Get the new VSVGA.SYS.

5. Trident 8900B Card

Symptom:

Screen "wavers".

Problem:

Hardware problem with these cards.

Resolution:

Call Trident. Phone number: ?

6. Trident 8900C Card

Symptom:

System hangs with blinking cursor in the upper right hand corner.

Problem:

PMI file usually not created properly.

Resolution:

See "HOW TO REGENERATE PMI FILES" below:

7. Trident 9000 Card

Symptom:

DOS/PM screen Synch problems possible. Running SVGA ON does not help.

Resolution:

Follow the "HOW TO REGENERATE PMI FILES" description below.

8. Video Corruption returning to WIN-OS2 session

Symptom:

Video becomes corrupted when returning to a previously opened Full screen WIN-OS2 session.

Problem:

WIN-OS2 session not aware that a video mode switch has taken place.

Resolution:

Set your VIDEO_SWITCH_NOTIFICATION in the DOS SETTINGS to ON.

9. Colors of Windows applications appear distorted

Symptom:

Windows applications running on the OS/2 Desktop appear different than in a WIN-OS2 fullscreen.

Problem:

The DOS/Windows application's colors have to be translated to use the OS/2 PM color palette. With the OS/2 VGA Desktop, there is a limitation of 16 colors. This colors simply cannot be translated correctly.

Resolution:

Run the application fullscreen, or obtain a PM driver that can support more than 16 colors.

10. Installation of OS/2 halts at Blue "IBM Logo" screen

Symptom:

OS/2 boots up to Blue IBM Logo screen and does not finish printing "INSERT DISK #1 message". Drive light continues to stay on indefinitely.

Problem:

Incompatible OAK Video card.

Resolution:

1. Temporarily use another VGA card to get OS/2 installed. Should be able to place card in after install completes.

2. NOT VERIFIED: This should only be tried by more experienced users.
 * a. Make backup copy of INSTALL disk.
 * b. Un Write-protect INSTALL disk.
 * c. Boot up DOS and put INSTALL disk in drive A.
 * d. COPY A:OS2LDR A:OS2LDR.OLD
 * e. DEBUG A:OS2LDR
 * f. U 4F7C
 * g. E 4F7C
 * h. CD.90
 * i. 
 * j. 10.90
 * k. W
 * l. Q
 * m. Use new install diskette to install OS/2.

Note: The install will no longer display text on the blue screen that comes up after install diskette is inserted. When the blue screen comes up, insert disk 1 and continue.

HOW TO REGENERATE PMI FILES:

Start up a DOS FULLSCREEN session and type "SVGA ON". This will create a file called SVGADATA.PMI. You can then exit the DOS FS, and shutdown OS/2. At boot time, this file is read(if present) by BVHSVGA.DLL. You need to verify that the following statements appear in the CONFIG.SYS: SET VIO_VGA=DEVICE(BVHVGA,BVHSVGA) DEVICE=D:\OS2\MDOS\VSVGA.SYS Note: A PMI file tells OS/2 (BVGSVGA.DLL specifically) the capabilities of your video card, resolutions supported, etc. this information enables OS/2 to perform successful mode switching between any HIGH RES DOS/Windows session and the OS/2 VGA session.

Video boards and the chipsets they use:(not official list)

Chipset name                Board name --  Chips & Technologies VGA chip - Cardinal, C&T MK82452 Everex VGA chip              - Everex EV-673 Genoa GVGA chip              - Genoa 6400 Western Digital 9010 (512K)  - Paradise VGA Pro, VGA 1024, "PVGA" Western Digital 9030 (1meg)  - MVGA 1024DX S3 (86C911)                  - STB Wind/X, Orchid Fahrenheit 1280, Diamond Stealth VRAM HIcolor Oak OTI-067                  - United Solutions, Inc. Image 1024 Oak OTI-037                  - VGA 800-160 (Taiwan made) RealTek                      - RealTek SVGA Trident 8800 chip            - ATI Prism Elite, Everev 678, Maxxon, Imtec, Logix Trident 8900 chip (Zymos Poach 51) - Trident 8900, Hi Res 512 Tseng ET3000 VGA chip        - Genoa 5400, STB VGA/EM, Orchid Designer, OTI SVGA (old), Optima 1024 Tseng ET4000 VGA chip        - Orchid Pro Designer II, Ultra SVGA, STB Powergraph, Diamond SpedStar, Boca Research Super VGA, Optima Mega SVGA, Diamond SpeedStar + Tseng ET4000 & Sierra RAMDAC - Swan Palette Plus, 2TheMax VGA 4000, Diamond SpeedStar + HIcolor Video 7 VGA chip             - Video 7 VRAM, Video 7 Fastwrite, Video 7 VEGA Deluxe, Northgate Pro

Some other suggestions for video problems:

In many cases, OS/2 requires a different dip switch setup for your adapter. Try some of the suggested variations in your adapter manual.

I'm getting some corruption returning to my WinOS2 fullscreen Set your VIDEO_SWITCH_NOTIFICATION in the DOS SETTINGS to ON.

MOUSE PROBLEMS
Mouse problems:

1. Mouse driver does not install correctly

Symptom: No mouse pointer movement(or no mouse pointer).

Problem: Either the install program could not correctly determine what type of mouse it was, or could not determine that a mouse was indeed present. If the user had mouse support during the graphical install portion of the installation process, then he probably changed the mouse driver/port that OS/2 had already chosen for his configuration.

Resolution: Have the user run the Selective Install program found in the OS/2 System/System Setup folder and choose a different driver. See below for further suggestions.

2. Mouse does not work after Dual boot

Symptom: After performing dual boot to DOS, mouse does not work.

Problem: Mouse has a "memory" that remembers the mode it was in previously.

Resolution: Before performing the dual boot, open a DOS window or fullscreen and type MOUSE PC. You can also perform a cold boot after issuing the BOOT /DOS command. The third suggestion is to unplug and plug it back in after a few seconds (this allows the mouse to be reset).


 * 3. HP Mouse installation

Resolution: 1) Select any mouse during installation 2)  Copy HILMOU.SYS and NOEXBIOS.SYS to C:\OS2\ (these     are supplied the manufacturer) 3) Modify CONFIG.SYS with the following in the order     shown:       DEVICE=C:\OS2\NOEXBIOS.SYS       DEVICE=C:\OS2\HILMOU.SYS       DEVICE=C:\OS2\MOUSE.SYS TYPE=HILMOU$       (THIS LAST LINE SHOULD ALREADY BE IN CONFIG.SYS BUT WILL NEED "TYPE=HILMOU$" ADDED)       HP Cust Service # is 1-800-752-0900  P#289547        Customer may also go to his dealer for the diskette which         ships with mouse. Customer may also see COMPUSERV GO HP.


 * 4. Logitech Mice

Symptom:

Logitech mouse does not function under OS/2.

Problem:

Mouse does not function when installed with the Logitech drivers.

Resolution:

Select PS/2 style pointing device during install. If already installed and mouse is not working correctly, perform a Selective Install(run INSTALL from the command line) and choose the above mentioned driver.


 * 5. Alternate pointing devices (two mice!)

Notes:

There is an undocumented function in the mouse device driver. If you have some alternate pointing device such as a tablet or touch screen you may use it in addition to the regular mouse pointing device. 1) Install the device driver for the device with the appropriate DEVICE= statement in CONFIG.SYS (this must be an OS/2 device driver.) 2) Add the following to the end of the DEVICE=C:\OS2\MOUSE.SYS line: STYPE=xxxxxx$ Where the xxxxx$ is the name of the device (from the device driver manual)

3) Upon reboot, both pointing devices will be active.

6. For General Mouse driver info:

Type HELP MOUSE at an OS/2 prompt to read about proper CONFIG.SYS parameters for the mouse drivers.

COM PORT PROBLEMS
1. OS/2 cannot see COM3 and COM4.

Symptom:

OS/2 does not recognize COM3 and COM4 installed on an (E)ISA machine.

Problem:

COM3 and COM4 are supported on PS/2s without any additional effort. On (E)ISA machines, some additions are required to CONFIG.SYS.

Resolution:

Using a text editor, include "(port number, base address, interrupt number)" parameters next to the COM.SYS and VCOM.SYS filenames. One example: DEVICE=C:\OS2\COM.SYS (3,3E8,5) (4,2E8,3) DEVICE=C:\OS2\MDOS\VCOM.SYS (3,3E8,5) (4,2E8,3) NOTE: These are NOT default parameters and must be configured according to the user's hardware reference material for the card where the COM ports reside.

Parameters for COM1 and COM2 need not be included (unless they are somehow nonstandard). OS/2 must end up with sequentially numbered COM ports. For example, if port two is not installed but port three or port four is installed start numbering using (2,...) in the DEVICE lines.

The port address cannot be shared. If a port address is shared by two or more COM port, it will create unpredictable outcome. Although we may put any preferred values to install COM 3 or/and 4, the ports or COM.SYS may not be able to perform as it should be if the values are different from the ones specified by the COM 3 and COM 4 adapter cards. For an example, a FAX/MODEM card which can be configured as COM 4, but the documentation indicates that the IRQ will be 3 when COM 4 is chosen. If COM.SYS is installed for COM 2 which uses IRQ 3, there will be a conflict in IRQ level. COM.SYS will make both COM 2 and COM 4 available, but both ports cannot be opened at the same time. If the user would like to use COM4, it is recommended to disable COM2 or to remove COM2 adapter card.

2. Problems performing high-speed communications

Symptom:

Using high speed modems (19200+ and maybe 9600), any interference with OS/2 while downloading/uploading data(moving the mouse, CTRL-ESC) will result in losing data or even losing the connection.

Problem:

Hardware on the motherboard controlling the COM Port loses interrupts when running under OS/2. DOS is able to run with the slower hardware successfully since it can dedicate ALL resources to dealing with the COM port.

Resolution:

Need to have a 16550 UART chip installed on motherboard or serial card. Contact your normal hardware support people to find out if you can have this done on your machine.


 * 3. More on problems with high-speed communications

Symptom:

Performing disk I/O can corrupt/interrupt high speed communications. The machine is configured using the IBMINT13.I13 driver for his drive.

Problem:

The IBMINT13.I13 driver is not a high performance driver since it is for general use by many different drives.

Resolution:

Contact supplier of hard drive to see if there is an OS/2 2.0 specific driver available for their drive.

PRINTING PROBLEMS
1. Cannot print on LPT1 or LPT2

Symptom:

No printing works.

Problem:

Another adapter is using IRQ7 or IRQ5. Cheap cable not using all 25 pins. Older parallel port card which does not support interrupt driven printing.

Resolution:

Make sure no other adapter card uses IRQ7 for LPT1 or IRQ5 for LPT2 (Soundblaster defaults to using IRQ7). Also make sure the printer cable being used has a full set of 25 pins. Some older cables do not use all the pins since in DOS they weren't all used. Under OS/2 all 25 lines can be used. Buy a cheap parallel port card that does support interrupt driven printing.


 * 2. HP Scanjet

Symptom:

Error message stating you cannot access the printer.

Problem:

Switches not set correctly on the card?.

Resolution:

Set EMS_FRAME_LOCATION in the DOS Settings to AUTO.

For AT bus machines:
 * Set card switches to 1010.

For MCA machines:
 * Run Reference disk and set card to ROM addresses C8000-CBFFF and I/O address to 268-26F.

CD-ROM DEVICES

 * 1. CD-ROM compatibility

Notes:

The only ones known to work at this time are IBM and Toshiba CD-ROM drives. If the CD-ROM device is SCSI with no other devices attached to the SCSI adapter or is non-SCSI try using a VMBOOT to get this working.

TAPE BACKUP UNITS
1. Mountain tape backup units

Symptom:

Above referenced tape backup units do not work reliably under OS/2.

Resolution:

Reference the customer back to 800-237-5511 and tell him to reference APAR #PJ03793.


 * 2. Memory Systems tape backup units

Resolution:

Colorado Memory Systems has a fix for their tape backup systems that allow customers to run the hardware from OS/2 DOS sessions. Customers should call Colorado Memory Systems directly.


 * 3. 160 Errors during install

Resolution:

Remove tape backup unit.

OTHER OEM DEVICES
For more info on the following hardware cards see the OS/2 README file found in the root directory of OS/2 after installation is complete.
 * ATI ETC
 * Cardinal FAX
 * Practical Peripherals
 * Smart Fax
 * Twincomm 24/96

MISCELLANEOUS PROBLEMS
1. Trying to run application(s) results in SYS0005, Access Denied

Symptom: SYS0005 msg returned by OS/2 when you attempt to execute a program.

Problem: OS/2 is unable to successfully access the file. File may be corrupted, or bad areas on the disk are causing problems for OS/2.

Resolution: Run CHKDSK on the drive. If this is the boot drive, you will need to boot from the installation disk, then disk #1. When you get to the next screen, hit ESC to return to the A: prompt. At that point, insert diskette #2 into the A: drive and type "CHKDSK x: /F" where "x" is the drive you are running the command against(the OS/2 boot drive).

2. SYS3176 when trying to open any DOS session

Symptom: Simply opening any DOS session results in this trap.

Problem: SVGA support having problems with TSENG chip video cards. Especially with the ET3000 chip based video cards.

Resolution: There are four things to try: 1. Set RMSIZE = 624 instead of 640.

2. In the DOS Settings set HW_ROM_TO_RAM to ON.

3. Disable SVGA support by changing the following lines: SET VIO_VGA=DEVICE(BVHVGA,BVHSVGA) DEVICE=D:\OS2\MDOS\VSVGA.SYS to SET VIO_VGA=DEVICE(BVHVGA) DEVICE=D:\OS2\MDOS\VVGA.SYS 4. The updated VSVGA.SYS driver may help also.

3. FatalExit code x0401 when trying to execute Win-OS2

Symptom: Above error message whenever WIN-OS2 is started. May flash by user without user being able to record error. You can have user start up a DOS Fullscreen and start WIN at the command line to verify that this is the problem.

Problem: Missing .DRV, or .DLL in the \OS2\MDOS\WINOS2 or \OS2\MDOS\WINOS2\SYSTEM directory. OS/2 probably did not install these correctly. (I got this err msg by erasing VGA.DRV in the SYSTEM directory)

Resolution: Have user redirect DIR listings of the two directories above by the command: DIR > LPT1 Once the user has this information he can go back and compare his WIN.INI and SYSTEM.INI to see what file(s) are missing. The INI files are located in the first directory noted above.

4. Swapper file not shrinking

Symptom: Swapper file does not dynamically deallocate itself as it should.

Resolution: Reference APAR PJ03686.

APPLICATION/SOFTWARE PROBLEMS
1. MicroSoft Word/PM

Symptom: Unknown.

Problem: Incompatible DLL causing problems on 2.0.

Resolution: All registered users may call MicroSoft for the updated DLL. Phone number for MicroSoft: ?


 * 2. Lotus 123 v3.x needs patch for OS/2

Symptom: Unknown at this time.

Problem: Does not function correctly on OS/2 1.x or 2.0.

Resolution: REQUEST 123PATCH FROM GBFORNEY AT WAYVMIC5 or call Lotus.

3. Lotus 123 v2.3 and other DOS apps having EMS memory problems

Symptom: DOS programs not seeing or even allowing OS/2 to allocate EMS memory.

Problem: Same as above.

Resolution: Get new VEMM.SYS. Simply replace this file in the \OS2 directory and shutdown/reboot OS/2.

4. PMTape not functioning on PS/2's

Symptom: Tape backup program PMTAPE not functioning correctly.

Problem: Bad IBM2FLPY.ADD driver.

Resolution: Get the interim IBM2FLPY.ADD fixed driver. Copy new file over existing one. Not yet ready for customer distribution.


 * 5. OLE Support for Windows apps not installed with OS/2 2.0

Symptom: Messages that indicate OLECLI.DLL, OLESVR.DLL, SHELL.DLL cannot be found running certain Windows apps under Win-OS2 which had been installed on the actual Windows 3.0 product.

Problem: The above mentioned DLL's are normally installed along with the application that uses them. The .DLL's are in the SYSTEM directory under the "WINDOWS" directory for the Windows 3.0 product.

Resolution: Reinstall the applications on WIN-OS2 or copy the DLL's over to the \OS2\MDOS\WINOS2\SYSTEM directory.


 * 6. CorelDraw gets GP Fault in GDI.EXE

Symptom: When starting the CorelDraw v2.0 application in a seamless window, we get the message: WALDO has caused an error in WIN-OS2*. GP Fault in Module: GDI.EXE at 0001:49AB Problem: Missing configuration parameters in WIN.INI.

Resolution: Place the following lines in the WIN.INI found in \OS2\MDOS\WINOS2: CorelDrawY DIR=C:\COREL


 * 7. Some Games have "flashing" problems in DOS FULLSCREEN

Symptom: High flashing rate on parts of the Fullscreen with some graphic intensive DOS games.

Problem: The method used by certain DOS applications to draw their graphics. Full details not known.

Resolution: Turn VIDEO_RETRACE_EMULATION to OFF in the DOS SETTINGS for that DOS application.
 * 8. Cannot get any expanded memory in the OS/2 Dos Environment

Symptom: The MEM command from a OS/2 DOS session reports no expanded memory.

Problem: Hardware base address conflicting with area needed for expanded memory. Seems that OS/2 may be requiring that the 64K region starting at C0000 be free in order for it to correctly configure expanded memory.

Resolution: Move the hardware base address for any card using the above address to another address. Consult your hardware references to figure this out, or run a hardware diagnostic program to give you the information needed.


 * 9. Dos programs causing Internal Processing Errors

Symptom: Dos programs that use FCB's may cause internal processing errors.

Problem: Dos programs that use FCB's. The programs known to be fixed are Autocad, WORDPROOF and SideKick Plus.

Resolution: Get OS2KRNL fix.

OTHER APPLICATION/SOFTWARE CONSIDERATIONS
For more info on the following applications see the OS/2 README file found in the root directory of OS/2 after installation is complete.
 * Ansel for Windows
 * Bound Checker (DOS)
 * Central Point Backup for Windows
 * Close-Up (Windows)
 * Desert Storm CD-ROM (Windows)
 * Distinct Back-Up (Windows)
 * DoDot 3.0 (Windows)
 * Fax Concentrator (DOS)
 * Magic-CV (DOS)
 * Mathematica 2.0 (Windows)
 * MusicPrinter Plus 4.0 (DOS)
 * OmniPage Professional 1.0 (Windows)
 * Oracle (DOS) (There is an OS/2 version of this program.)
 * Perceive for Windows
 * Realizer 1.0 (Windows)
 * Sherlock Holmes CD-ROM (DOS)
 * Smart Fax (DOS)
 * Soft-ICE (DOS)
 * Splash 1.01 (DOS)
 * Windows Multimedia Extension programs
 * Action! Sampler 1.0 (Windows)
 * Adobe Type Manager (Windows)
 * After Dark (Windows)
 * Aldus Pagemaker 4.0 (Windows)
 * Aldus Persuasion 2.0 (Windows)
 * Arts & Letters Graphics Editor 3.1 (Windows)
 * AutoCAD Version 10 (DOS)
 * AutoCAD (OS/2)
 * AutoManager 4.0 (DOS)
 * Borland C++ 2.0 (DOS)
 * Central Point Backup for DOS 7.1 (DOS)
 * Central Point PC Tools Deluxe 7.1 (Windows)
 * Commander Keen (DOS)
 * Control Room 1.0 (DOS)
 * CorelDRAW 2.0 (OS/2)
 * CorelDRAW 2.0 (Windows)
 * CorelDRAW 2.1 (Windows)
 * dBase IV 1.1 (DOS)
 * Designer (OS/2)
 * Drafix CAD Version 1.11 (Windows)
 * Drafix CAD Version 3.0 (Windows)
 * Dynacomm Asynchronous OS/2 (OS/2)
 * Enhanced Editor (OS/2)
 * F19 (DOS)
 * F-117A Stealth Fighter 2.0 (DOS)
 * Fastback Plus 2.1 and 3.04 (DOS)
 * FastLynx 1.1 (DOS)
 * FormBase 1.2 (Windows)
 * Form Publisher (Windows)
 * FotoMan (Windows)
 * Framework III 1.1 (DOS)
 * Harvard Graphics (Windows)
 * Harvard Draw (Windows)
 * hDC FileApps 1.0 (Windows)
 * HP New Wave 3.0 (Windows)
 * IBM 3363 Optical Disk Drive*
 * IBM PC/3270 V2.0* (DOS)
 * IBM PC/3270 V2.0* (Windows)
 * Intel SatisFAXtion
 * King's Quest (DOS)
 * LAN Support Program Device Drivers (DOS)
 * LANtastic 4.1 (DOS)
 * LapLink III 3.0 (DOS)
 * Linkway Mammals (DOS)
 * Linkway Presidents (DOS)
 * Lotus 123 for Windows 1.0 (Windows)
 * Lotus Freelance Graphics for OS/2 (OS/2)
 * Lotus Freelance Graphics for Windows (Windows)
 * Lotus Magellan 2.0 (DOS)
 * Lotus Notes (OS/2)
 * MagiCorp (Windows)
 * Mathcad 3.0 (Windows)
 * MicroProse Civilization (DOS)
 * Microsoft Bookshelf - CD-ROM Reference Library** (DOS/Multimedia)
 * Microsoft Chart 3.0** (DOS)
 * Microsoft Codeview** (DOS/OS/2)
 * Microsoft Codeview for Windows Version 3.0** (Windows)
 * Microsoft Excel for DOS 2.1** (DOS)
 * Microsoft Excel for OS/2 3.0** (OS/2)
 * Microsoft Excel for Windows 3.0** (Windows)
 * Microsoft Money 1.0** (Windows)
 * Microsoft QuickC** (Windows)
 * Microsoft Project for Windows 1.0** (Windows)
 * Microsoft Windows 3.0** (DOS)
 * More Windows (Windows)
 * National Geographics Mammals (DOS)
 * The Norton Backup 1.2 (DOS)
 * The Norton Desktop (Windows)
 * The Norton Utilities 5.0 (DOS)
 * PaintShow Plus 2.21 (DOS)
 * Paradox 3.5 (DOS)
 * Peachtree Complete III 5.0 (DOS)
 * Perform Pro 1.0 (Windows)
 * PFS: First Choice (DOS)
 * PFS: WindowWorks 1.75 (Windows)
 * Photostyler (Windows)
 * Publisher's PowerPak 2.1 (Windows)
 * Quattro Pro 3.0 (DOS)
 * Quicken (DOS)
 * Quicken for Windows (Windows)
 * Risk (DOS)
 * SantaFe Media Manager (DOS)
 * SideKick (OS/2)
 * Signmaster 5.11 (DOS)
 * Soft Term (OS/2)
 * SoundBlaster (DOS)
 * Space Quest IV (DOS)
 * SQLWindows 3.0 (Windows)
 * Turbo C++ 2.0 (DOS)
 * Turbo Debugger 2.01 (DOS)
 * Turbo Debugger for Windows (Windows)
 * Turbo Pascal 6.0 (DOS)
 * The Way You Work (DOS/Windows)
 * Windows Multimedia Extensions (Windows)
 * WINFAX PRO (Windows)
 * Wing Commander II (DOS)
 * WordPerfect for Windows (Windows)
 * WordPerfect Office 3.0 (DOS)
 * Xtree Pro Gold 2.0 (DOS)