OS/2 Professional

home *** CD-ROM | disk | FTP | other *** search

/ OS/2 Professional / OS2PRO194.ISO / os2 / info / faq / os2_20 / os2help / infoapar.fax < prev next >

Wrap

Text File | 1992-09-17 | 193.2 KB | 4,740 lines

/* ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ */ Known printers and correct device/driver to use under OS/2: MODEL: DEVICE (DRIVER) ---------------------- AST TurboLaser: AST TurboLaser (PSCRIPT.DRV) Agfa Matrix ChromaScript v51_8: Agfa Matrix ChromaScript v51_8 (PSCRIPT.DRV) Agfa/Compugraphic 9400PS V49_3: Agfa-Compugraphic 9400PS v49_3 (PSCRIPT.DRV) Agfa/Compugraphic 400PS: Agfa/Compugraphic 400PS (PSCRIPT.DRV) Apple LaserWriter II NT: Apple LaserWriter II NT (PSCRIPT.DRV) Apple LaserWriter II NTX: Apple LaserWriter II NTX (PSCRIPT.DRV) Apple LaserWriter Plus v42_2: Apple LaserWriter Plus v42_2 (PSCRIPT.DRV) Apple LaserWriter Plus: Apple LaserWriter Plus (PSCRIPT.DRV) Apple LaserWriter: Apple LaserWriter (PSCRIPT.DRV) Canon BubbleJet BJ10E: Proprinter X24E (IBM42XX.DRV) Canon BubbleJet BJC800: Epson LQ-2550 (EPSON.DRV) Colormate PS v51_9: Colormate PS v51_9 (PSCRIPT.DRV) Dataproducts LZR 1260 v47_0: Dataproducts LZR 1260 v47_0 (PSCRIPT.DRV) Dataproducts LZR-2665: Dataproducts LZR-2665 (PSCRIPT.DRV) Digital LN03R ScriptPrinter: Digital LN03R ScriptPrinter (PSCRIPT.DRV) Digital LPS PrintServer 40: Digital LPS PrintServer 40 (PSCRIPT.DRV) Epson 24 pins - 136 columns: 24-pin 136 Col (EPSON.DRV) Epson 24 pins - 80 columns: 24-pin 80 Col (EPSON.DRV) Epson 9 pins - 136 columns: 9-pin 136 Col (EPSON.DRV) Epson 9 pins - 80 columns: 9-pin 80 Col (EPSON.DRV) Epson DFX-5000 9 pins - 136 columns: DFX-5000 (EPSON.DRV) Epson DFX-8000 9 pin - 136 column: DFX-8000 (EPSON.DRV) Epson EPL-6000 Laser: EPL-6000 (EPSON.DRV) Epson EPL-7000: Epson EPL-7000 (LASERJET.DRV) Epson EPL-7500 v52_3: Epson EPL-7500 v52_3 (PSCRIPT.DRV) Epson EX-1000 Color 9 pins - 136 columns: EX-1000 (EPSON.DRV) Epson EX-800 Color 9 pins - 80 columns: EX-800 (EPSON.DRV) Epson FX-1050 9 pins - 136 columns: FX-1050 (EPSON.DRV) Epson FX-286e 9 pins - 136 columns: FX-286e (EPSON.DRV) Epson FX-850 9 pins - 80 columns: FX-850 (EPSON.DRV) Epson JX-80 Color 9 pins - 80 columns: JX-80 (EPSON.DRV) Epson LQ-1010 24 pin - 132 column: LQ-1010 (EPSON.DRV) Epson LQ-1050 (N9) 24 pins - 136 columns: LQ-1050 (N9) (EPSON.DRV) Epson LQ-1050 24 pins - 136 columns: LQ-1050 (EPSON.DRV) Epson LQ-1170 24 pins - 136 columns: LQ-1170 (EPSON.DRV) Epson LQ-1500: LQ-1050 (EPSON.DRV) Epson LQ-2500 Color 24 pins - 136 columns: LQ-2500 (EPSON.DRV) Epson LQ-2550 Color 24 pins - 136 columns: LQ-2550 (EPSON.DRV) Epson LQ-500 24 pins - 80 columns: LQ-500 (EPSON.DRV) Epson LQ-510 24 pins - 80 columns: LQ-510 (EPSON.DRV) Epson LQ-570 24 pins - 80 columns: LQ-570 (EPSON.DRV) Epson LQ-850 (N9) 24 pins - 80 columns: LQ-850 (N9) (EPSON.DRV) Epson LQ-850 24 pins - 80 columns: LQ-850 (EPSON.DRV) Epson LQ-860 Color 24 pins - 80 columns: LQ-860 (EPSON.DRV) Epson LQ-870 24 pins - 80 columns: LQ-870 (EPSON.DRV) Epson LQ-950 (N9) 24 pins - 110 columns: LQ-950 (N9) (EPSON.DRV) Epson LX-800 9 pins - 80 columns: LX-800 (EPSON.DRV) Epson LX-810 9 pins - 80 columns: LX-810 (EPSON.DRV) Generic PostScript Printer: Generic PostScript Printer (PSCRIPT.DRV) HP 7470A Plotter: HP7470A (PLOTTERS.DRV) HP 7475A Plotter: HP7475A (PLOTTERS.DRV) HP 7550A Plotter: HP7550A (PLOTTERS.DRV) HP 7580A Plotter: HP7580A (PLOTTERS.DRV) HP 7580B Plotter: HP7580B (PLOTTERS.DRV) HP 7585A Plotter: HP7585A (PLOTTERS.DRV) HP 7585B Plotter: HP7585B (PLOTTERS.DRV) HP 7586B Plotter: HP7586B (PLOTTERS.DRV) HP ColorPro: HP7440A (PLOTTERS.DRV) HP DeskJet 500: HP DeskJet 500 (EPSON.DRV) HP DeskJet 500C: HP DeskJet 500 (EPSON.DRV) HP DeskJet Plus: HP DeskJet 500 (EPSON.DRV) HP DeskJet : HP DeskJet 500 (EPSON.DRV) HP DraftMaster I: HP7595A (PLOTTERS.DRV) HP DraftMaster II: HP7596A (PLOTTERS.DRV) HP DraftPro: HP7570A (PLOTTERS.DRV) HP LaserJet 2000: HP LaserJet 2000 (LASERJET.DRV) HP LaserJet 500 Plus: HP LaserJet 500 Plus (LASERJET.DRV) HP LaserJet Classic: HP LaserJet Classic (LASERJET.DRV) HP LaserJet IID v52_2: HP LaserJet IID v52_2 (PSCRIPT.DRV) HP LaserJet IID: HP LaserJet IID (LASERJET.DRV) HP LaserJet III v52_2: HP LaserJet III v52_2 (PSCRIPT.DRV) HP LaserJet III: HP LaserJet III (LASERJET.DRV) HP LaserJet IIID v52_2: HP LaserJet IIID v52_2 (PSCRIPT.DRV) HP LaserJet IIID: HP LaserJet IIID (LASERJET.DRV) HP LaserJet IIIP PS v52_2: HP LaserJet IIIP PS v52_2 (PSCRIPT.DRV) HP LaserJet IIIP: HP LaserJet IIIP (LASERJET.DRV) HP LaserJet IIISi PS v52_3: HP LaserJet IIISi PS v52_3 (PSCRIPT.DRV) HP LaserJet IIISi: HP LaserJet IIISi (LASERJET.DRV) HP LaserJet IIP Plus: HP LaserJet IIP Plus (LASERJET.DRV) HP LaserJet IIP v52_2: HP LaserJet IIP v52_2 (PSCRIPT.DRV) HP LaserJet IIP: HP LaserJet IIP (LASERJET.DRV) HP LaserJet Plus: HP LaserJet Plus (LASERJET.DRV) HP LaserJet Series II: HP LaserJet Series II (LASERJET.DRV) IBM 2380 PPS II: IBM 2380 PPS II (IBM42XX.DRV) IBM 2381 PPS II: IBM 2381 PPS II (IBM42XX.DRV) IBM 2390 PPS II: IBM 2390 PPS II (IBM42XX.DRV) IBM 2391 PPS II: IBM 2391 PPS II (IBM42XX.DRV) IBM 3812 Page Printer:IBM 5152 Graphics Printer (IBM5152.DRV) -3812 must be in 5152 compatability mode -Available on CompuServe,IBM Bulletin Boards & OS2TOOLS IBM 3816 - 01D: IBM 3816 - 01D (IBM52XX.DRV) IBM 3816 - 01S: IBM 3816 - 01S (IBM52XX.DRV) IBM 3852 Jetprinter II: IBM 3852 Jetprinter II (IBM3852.DRV) -Available on CompuServe,IBM Bulletin Boards & OS2TOOLS IBM 4019 LaserPrinter E: IBM 4019 LaserPrinter E (IBM4019.DRV) IBM 4019 LaserPrinter: IBM 4019 LaserPrinter (IBM4019.DRV) IBM 4019 Laserprinter E: IBM 4019 Laserprinter E (LASERJET.DRV) IBM 4019 Laserprinter: IBM 4019 Laserprinter (LASERJET.DRV) IBM 4019 v52_1 (17 Fonts): IBM 4019 v52_1 (17 Fonts) (PSCRIPT.DRV) IBM 4019 v52_1 (39 Fonts): IBM 4019 v52_1 (39 Fonts) (PSCRIPT.DRV) IBM 4029 (17 Fonts 300 Dpi): IBM 4029 (17 Fonts 300 Dpi) (PSCRIPT.DRV) IBM 4019 v52_1 (39 Fonts): IBM 4019 v52_1 (39 Fonts) (PSCRIPT.DRV) IBM 4029 (17 Fonts 300 Dpi): IBM 4029 (17 Fonts 300 Dpi) (PSCRIPT.DRV) IBM 4029 (17 Fonts 600 Dpi): IBM 4029 (17 Fonts 600 Dpi) (PSCRIPT.DRV) IBM 4029 (39 Fonts 300 Dpi): IBM 4029 (39 Fonts 300 Dpi) (PSCRIPT.DRV) IBM 4029 (39 Fonts 600 Dpi): IBM 4029 (39 Fonts 600 DPI) (PSCRIPT.DRV) IBM 4029 LaserPrinter 10: IBM 4029 LaserPrinter 10 (IBM4019.DRV) IBM 4029 LaserPrinter 10L: IBM 4029 LaserPrinter 10L (IBM4019.DRV) IBM 4029 LaserPrinter 5E: IBM 4029 LaserPrinter 5E (IBM4019.DRV) IBM 4029 LaserPrinter 6: IBM 4029 LaserPrinter 6 (IBM4019.DRV) IBM 4029 LaserPrinter 10: IBM 4029 Laserprinter 10 (LASERJET.DRV) IBM 4029 LaserPrinter 10L: IBM 4029 Laserprinter 10L (LASERJET.DRV) IBM 4029 Laserprinter 5E: IBM 4029 Laserprinter 5E (LASERJET.DRV) IBM 4029 Laserprinter 6: IBM 4029 Laserprinter 6 (LASERJET.DRV) IBM 4072 ExecJet: IBM 5202 QuietWriter III (IBM52XX.DRV) *Lexmark beta driver expected in July 92* IBM 4201 Proprinter II: IBM 4201 Proprinter II (IBM42XX.DRV) IBM 4201 Proprinter III: IBM 4201 Proprinter III (IBM42XX.DRV) IBM 4201 Proprinter: IBM 4201 Proprinter (IBM42XX.DRV) IBM 4202 Proprinter II XL: IBM 4202 Proprinter II XL (IBM42XX.DRV) IBM 4202 Proprinter III XL: IBM 4202 Proporinter III XL (IBM42XX.DRV) IBM 4202 Proprinter XL: IBM 4202 Proprinter XL (IBM42XX.DRV) IBM 4207 Proprinter X24: IBM 4207 Proprinter X24 (IBM42XX.DRV) IBM 4207 Proprinter X24E: IBM 4207 Proprinter X24E (IBM42XX.DRV) IBM 4207 Proprinter XL24: IBM 4207 Proprinter XL24 (IBM42XX.DRV) IBM 4208 Proprinter XL24: IBM 4208 Proprinter XL24 (IBM42XX.DRV) IBM 4208 Proprinter XL24E: IBM 4208 Proprinter XL24E (IBM42XX.DRV) IBM 4216-031 v51_4 SheetFeed: IBM 4216-031 v51_4 SheetFeed (PSCRIPT.DRV) IBM 4224 - 01 & 02 & E3: IBM 4224 - 01 & 02 & E3 (IBM42XX.DRV) IBM 4224 - C2: IBM 4224 - C2 (IBM42XX.DRV) IBM 4226 Model 302: IBM 4226 Model 302 (IBM42XX.DRV) IBM 5152 Graphics Printer:IBM 5152 Graphics Printer(IBM5152.DRV) -Available on CompuServe,IBM Bulletin Boards & OS2TOOLS IBM 5182 Color Printer:IBM 5182 Color Printer (IBM5182.DRV) -Supports monochrome output only -Available on CompuServe,IBM Bulletin Boards & OS2TOOLS IBM 5201 Quietwriter (IBM52011.DRV) -Available on CompuServe,IBM Bulletin Boards & OS2TOOLS IBM 5201 Quietwriter II (IBM52012.DRV) IBM 5202 QuietWriter III: IBM 5202 QuietWriter III (IBM52XX.DRV) IBM 5204 QuickWriter: IBM 5204 QuickWriter (IBM52XX.DRV) IBM 5216 Wheelwriter I : IBM 5216 Wheelwriter I (IBM5216.DRV) -Available on CompuServe,IBM Bulletin Boards & OS2TOOLS IBM 5216 Wheelwriter II: IBM 5216 Wheelwriter II (IBM5216.DRV) -Available on CompuServe,IBM Bulletin Boards & OS2TOOLS IBM 6180 Plotter: IBM6180 (PLOTTERS.DRV) IBM 6182 Plotter: IBM6182 (PLOTTERS.DRV) IBM 6184 Plotter: IBM6184 (PLOTTERS.DRV) IBM 6186-1 Plotter: IBM6186-1 (PLOTTERS.DRV) IBM 6186-2 Plotter: IBM6186-2 (PLOTTERS.DRV) IBM 7371 Plotter: IBM7371 (PLOTTERS.DRV) IBM 7372 Plotter: IBM7372 (PLOTTERS.DRV) IBM 7374 Plotter: IBM7374 (PLOTTERS.DRV) IBM 7375-1 Plotter: IBM7375-1 (PLOTTERS.DRV) IBM 7375-2 Plotter: IBM7375-2 (PLOTTERS.DRV) IBM NULL Printer Driver (IBMNULL.DRV) IBM Personal Page Printer II-30: IBM Personal Page Printer II-30 (PSCRIPT.DRV) IBM Personal Page Printer II-31: IBM Personal Page Printer II-31 (PSCRIPT.DRV) IBM Personal Pageprinter: IBM Personal Pageprinter (PSCRIPT.DRV) Kyocera F-1000A/F-1000: Kyocera F-1000A/F-1000 (LASERJET.DRV) Kyocera F-1800A/F-1800: Kyocera F-1800A/F-1800 (LASERJET.DRV) Kyocera F-2000A/F-2200S: Kyocera F-2000A/F-2200S (LASERJET.DRV) Kyocera F-3000A/F-3300: Kyocera F-3000A/F-3300 (LASERJET.DRV) Kyocera F-5000A/F-5000: Kyocera F-5000A/F-5000 (LASERJET.DRV) Kyocera F-800A/F-800: Kyocera F-800A/F-800 (LASERJET.DRV) Kyocera F-820: Kyocera F-820 (LASERJET.DRV) Kyocera P-2000: Kyocera P-2000 (PSCRIPT.DRV) Kyocera Q-8010: Kyocera Q-8010 (PSCRIPT.DRV) Linotronic 100 v38_0: Linotronic 100 v38_0 (PSCRIPT.DRV) Linotronic 100 v42_5: Linotronic 100 v42_5 (PSCRIPT.DRV) Linotronic 200 v47_1: Linotronic 200 v47_1 (PSCRIPT.DRV) Linotronic 200 v49_3: Linotronic 200 v49_3 (PSCRIPT.DRV) Linotronic 300 v47_0: Linotronic 300 v47_0 (PSCRIPT.DRV) Linotronic 300 v47_1: Linotronic 300 v47_1 (PSCRIPT.DRV) Linotronic 300 v49_3: Linotronic 300 v49_3 (PSCRIPT.DRV) Linotronic 500 v49_3: Linotronic 500 v49_3 (PSCRIPT.DRV) PaintJet: Paintjet (SMGXPJET.DRV) PaintJet XL: Paintjet XL (SMGXPJET.DRV) NEC LC-890: NEC LC-890 (PSCRIPT.DRV) Olivetti LP 5000: Olivetti LP 5000 (PSCRIPT.DRV) Panasonic KX-P1123 in Epson LQ-850 mode: Panasonic KX-P1123 (EPSON.DRV) Panasonic KX-P1124 in Epson LQ-2500 mode: Panasonic KX-P1124 (EPSON.DRV) Panasonic KX-P1124i in Epson LQ-850 mode: Panasonic KX-P1124i (EPSON.DRV) Panasonic KX-P1180 in Epson FX-86e mode: Panasonic KX-P1180 (EPSON.DRV) Panasonic KX-P1191 in Epson FX-86e mode: Panasonic KX-P1191 (EPSON.DRV) Panasonic KX-P1624 in Epson LQ-2500 mode: Panasonic KX-P1624 (EPSON.DRV) Panasonic KX-P1654 in Epson LQ-1050 mode: Panasonic KX-P1654 (EPSON.DRV) Panasonic KX-P1695 in Epson FX-1050 mode: Panasonic KX-P2624 (EPSON.DRV) Panasonic KX-P2624 in Epson LQ-1050 mode: Panasonic KX-P2624 (EPSON.DRV) Panasonic KX-P4420: Panasonic KX-P4420 (LASERJET.DRV) Panasonic KX-P4450: Panasonic KX-P4450 (LASERJET.DRV) Panasonic KX-P4450i: Panasonic KX-P4450i (LASERJET.DRV) Panasonic KX-P4455 v51_4: Panasonic KX-P4455 v51_4 (PSCRIPT.DRV) Phaser Card v1_1: Phaser Card v1_1 (PSCRIPT.DRV) QMS ColorScript 100 Mod 10: QMS ColorScript 100 Mod 10 (PSCRIPT.DRV) QMS ColorScript 100 Mod 30: QMS ColorScript 100 Mod 30 (PSCRIPT.DRV) QMS ColorScript 100 Mod 30si: QMS ColorScript 100 Mod 30si (PSCRIPT.DRV) QMS ColorScript 100: QMS ColorScript 100 (PSCRIPT.DRV) QMS IS X320T: QMS IS X320T (PSCRIPT.DRV) QMS-PS 1500: QMS-PS 1500 (PSCRIPT.DRV) QMS-PS 2000: QMS-PS 2000 (PSCRIPT.DRV) QMS-PS 2200: QMS-PS 2200 (PSCRIPT.DRV) QMS-PS 2210: QMS-PS 2210 (PSCRIPT.DRV) QMS-PS 2220: QMS-PS 2220 (PSCRIPT.DRV) QMS-PS 410: QMS-PS 410 (PSCRIPT.DRV) QMS-PS 800 Plus: QMS-PS 800 Plus (PSCRIPT.DRV) QMS-PS 800: QMS-PS 800 (PSCRIPT.DRV) QMS-PS 810 TURBO: QMS-PS 810 TURBO (PSCRIPT.DRV) QMS-PS 810: QMS-PS 810 (PSCRIPT.DRV) QMS-PS 815 MR: QMS-PS 815 MR (PSCRIPT.DRV) QMS-PS 815: QMS-PS 815 (PSCRIPT.DRV) QMS-PS 820 Turbo: QMS-PS 820 Turbo (PSCRIPT.DRV) QMS-PS 820: QMS-PS 820 (PSCRIPT.DRV) QMS-PS 825 MR: QMS-PS 825 MR (PSCRIPT.DRV) QMS-PS 825: QMS-PS 825 (PSCRIPT.DRV) Qume ScripTEN: Qume ScripTEN (PSCRIPT.DRV) Seiko ColorPoint PS Model 04: Seiko ColorPoint PS Model 04 (PSCRIPT.DRV) Seiko Colorpoint PS Model 14: Seiko ColorPoint PS Model 14 (PSCRIPT.DRV) Seiko Personal ColorPoint PS: Seiko Personal ColorPoint PS (PSCRIPT.DRV) Silentwriter LC 890XL v50_5: Silentwriter LC 890XL v50_5 (PSCRIPT.DRV) Silentwriter2 290 v52_0: Silentwriter2 Model 90 v52_2 (PSCRIPT.DRV) Silentwriter2 Model 90 v52_2: Silentwriter2 Model 90 v52_2 (PSCRIPT.DRV) TI 2115 (13 fonts) v47_0: TI 2115 (13 fonts) v47_0 (PSCRIPT.DRV) TI OmniLaser 2108: TI OmniLaser 2108 (PSCRIPT.DRV) TI OmniLaser 2115: TI Omnilaser 2115 (PSCRIPT.DRV) TI microLaser PS17 v_52_1: TI microLaser PS17 v_52_1 (PSCRIPT.DRV) TI microLaser PS35 v_52_1: TI microLaser PS35 v_52_1 (PSCRIPT.DRV) Tektronix Phaser II PX v2_02: Tektronix Phaser II PX V2_02 (PSCRIPT.DRV) Tektronix Phaser II PXi v2010: Tektronix Phaser II PXi v2010 (PSCRIPT.DRV) Tektronix Phaser III PXi v2010: Tektronix Phaser III PXi v2010 (PSCRIPT.DRV) Varityper VT-600: Varityper VT-600 (PSCRIPT.DRV) Wang LCS15 FontPlus: Wang LCS15 FontPlus (PSCRIPT.DRV) Wang LCS15: Wang LCS15 (PSCRIPT.DRV) /* ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ */ PRINTING TIPS AND INFORMATION FOR OS/2 1.3 AND OS/2 2.0 . ************************************************************* GENERAL OS/2 PRINTING TIPS ************************************************************* . DON'T TRY INSTALLING OS/2 2.0 PAINTJET DRIVER ON A 1.3 SYSTEM .. The OS/2 2.0 PaintJet driver does not work on a 1.3 system. This driver (any any other driver) requiring the mirrors.dll will not work with 1.3. The mirrors.dll is a 32 bit dll. ---------------------------------------------------------------- DMA PARALLEL PORT ARBITRATION LEVEL .. When using OS/2 2.0, the DMA parallel prot arbitration level should not be disabled. It should be set to SHARED 7. When using OS/2 1.3 with CSD 5054 or greater applied, the DMA parallel port arbitration level should not be disabled. Any level prior to this, should have the arbitration level disabled on those systems with a DMA parallel port (PS/2 models 56, 57, 80-A21, 80-A31, 90, and 95). --------------------------------------------------------------- PARALLEL PORT PRINTING PROBLEMS .. If nothing prints on an AT (ISA) bus system, the parallel port may be configured incorrectly. This is especially true if the parallel port worked correctly under DOS. Up to 3 parallel ports can be installed on most systems as long as the port address and hardware interrupt levels are set properly. The proper combinations under OS/2 are address 3BC and IRQ7, 378 and IRQ7, and 278 and IRQ5. If these combinations are not used, printer error messages or very slow printing will occur. .. AT bus systems are incapable of sharing hardware interrupt levels. This means each adapter in your system must have a different hardware interrupt level assigned. Special code handles the conflict as described in the paragraph above. Many sound cards (Soundblaster) use the same hardware interrupt level as the first parallel port and the conflict must be resolved if you intend to print. Using IRQ10 with Soundblaster is recommended since it does not conflict with the parallel ports (IRQ7, IRQ5). IRQ2 cannot be used since it drives the slave 8259 Programmable Interrupt Controller. .. Problems have been found when using certain parallel port printer cables that do not meet the parallel port specifica- tions. Cables that are longer than six feet in length are suspect. Cables that do not contain all 25 wires will not work under OS/2. The six foot cable length problem is more evident on higher speed processor systems. .. Some older parallel port adapters fail to generate hardware interrupts. These adapters usually work correctly under DOS since DOS does not use hardware interrupts to print. OS/2, due to its multitasking capability, must use interrupts to transfer data out the parallel port. If your adapter fails to generate interrupts, it must be replaced in order to print under OS/2. If your buffer light illuminates on your printer or if your printer prints the first character and then an error message is displayed after approximately 45 seconds, you may be experiencing an interrupt problem. ------------------------------------------------------------- WHAT PRINTERS ARE SUPPORTED? See the file called PRDESC.LST on the first print driver diskette with the OS/2 2.0 package. It contains a compre- hensive list of all the printer models supported. ------------------------------------------------------------- PRINTER DRIVERS NO LONGER SHIPPED WITH OS/2 2.0 OS2TOOLS contains a package called OS2PDRVR. This package contains OS/2 printer drivers that were shipped with OS/2 1.3, but are no longer shipped with OS/2 2.0. It includes IBM3852, IBM5152, IBM5182, IBM52011, and IBM5216. The package states that in the future it will contain BETA and CSD versions also. The printer drivers can also be accessed in Compuserve (Library 17). ------------------------------------------------------------- REDIRECTING PRINTER PORT To print to a communications port, you must redirect the output: . 1. Display the pop-up menu for the appropriate printer object. 2. Select the arrow to the right of OPEN; then select SETTINGS. 3. Select OUTPUT. 4. Display the pop-up menu for the port you want to set up. 5. Select the arrow to the right of REDIRECTION. 6. Select the port you need. For example, you might select COM1 to send your output through a communications port. or 1. Select OS/2 SYSTEM; then select Command Prompts. 2. Select OS/2 Window or OS/2 Full Screen. SPOOL /D:LPT1 /O:COM1 PRINT MYFILE.TXT /D:LPT1 Note: You can redirect output to a COM port; however, you cannot redirect output from a COM port to a LPT port. The redirection option is only available when two or more printer objects are defined. ------------------------------------------------------------ IMPORTANT DOCUMENT ON OS2TOOLS CALLED OS2TNT ( OS/2 TIPS AND TECHNIQUES. THIS IS A LIVING DOCUMENT AND ALONG WITH OTHER INFORMATION, CONTAINS GOOD PRINTING TIPS. IT IS UPDATED AS NECESSARY. THE FOLLOWING IS FROM OS2TNT..... General Information ------------------- When installing auxiliary parallel port expansion cards, you need to ensure that LPT1 is configured to interrupt level 7 (IRQ7). Not doing so will cause printing under OS/2 to function erratically. Be aware that when using many other common adapters such as the SoundBlaster card, they may come from the factory configured on IRQ7. Also, many manufacturers recommend you configure their cards on IRQ7. Non-microchannel machines cannot share interrupts and each card must be on a separate IRQ to avoid conflicts. See the reference for your adapter cards to configure the IRQs. Additionally, LPT2 cards should be configured on IRQ5. -------------------------------------------------------------- .. QUESTIONS, COMMON PROBLEMS AND ANSWERS .. PROBLEM: Automatic emulation switching does not work RESOLUTION: None AES does not currently work under OS/2 2.0. Lexmark is working on this to be released soon. QUESTION: How does AES for OS/2 interact with 2.0 GA? ANSWER: The basic function of AES is to provide a convenient method for emulation mode switching on the IBM LaserPrinter products. By correlating LPT ports with emulation modes on the printer, a user can send their job to the correct port and set the mode switch properly, and thus not have to touch the printer to change emulation modes. During AES install, the option is given to the user if they want to install extra LPT ports (as the LPTX.SYS Device Driver). This driver is the same identical driver that is used by the Lexmark External Network Adapter, IBM 4033. It essentially allows for character monitors to be installed on LPT ports > 3. Then the character monitor does what it needs to, and re-directs that data to the physical port where the printer is connected. Or in the case of the IBM 4033, the data is re-directed (by the character monitor) to the Token Ring or Ethernet PS/2 card PROBLEM: Printing problems with parallel ports - nothing prints. RESOLUTION: Ensure that LPT1 is configured to use IRQ7 and LPT2 is configured as IRQ5. Check the printer cable to ensure that the cable runs all 25 lines, not all cables wire the necessary lines. If the problem persists and you are convinced it is not an interrupt problem, cable problem or just the wrong driver, the problem may be with your I/O card. Some older I/O cards do not work in OS/2. TIPS AND TECHNIQUES ------------------- If you send a print job to a printer that is powered off, you may experience a corrupted job when responding to the RETRY dialog after powering on the printer. You should cancel the job and resubmit it after turning on the printer. ------------------------------------------------------------- BETA VERSION OF IBM4072 EXECJET DRIVER FROM LEXMARK Customers who need an IBM4072 ExecJet driver can now get a beta version from Lexmark by calling Lexmark support at 1-606- 232-3000 or by logging on to the Lexmark Bulletin board at 1-606-232-5653. IBM users can obtain the driver by entering the following command at a VM prompt: EXEC TOOLS SENDTO LEXCJN1 LEXTOOLS DRIVERS GET OS24072 PACKAGE -------------------------------------------------------------- PARALLEL CARDS KNOWN NOT TO WORK: Boca Research: After Calling Boca Researches tecnical support line, they admitted that the parallel ports in the following cards will NOT work correctly for os/2. These cards will however be upgraded this summer (exact date unclear). IDE Controller cards I/O AT41 and I/O AT45cards. SIIG: SIIG multi-purpose serial/parallel/game card. -customer could not print with this card. Only printed when he replaced card. DIAMOND: - DIAMOND I/O DIO-100 Revision A 1985. Card did not work. Customer got printing to work only when the card was replaced. ---------------------------------------------------------- SOME OEM PARALLEL PORT CARDS THAT WORK CORRECTLY UNDER OS/2 .. These are cards that a) the manufacturer confirms that they work under interrupt driven printing for os/2 2.0. or b) Where the succesfull replacement for a card that did not work under os/2 2.0. BOCA RESEARCH: IO AT 44 - confirmed by manufacturer and customer IO AT 24- confirmed by manufacturer EVEREX: EVEREX Multi I/o card (model???) - confirmed by customer ---------------------------------------------------------- PRINT PROBLEMS WITH MULTIPLE PRINT OBJECT USING SAME PORT. Some os/2 applications have problems selecting a printer when there are multiple print objects defined for the same output port. Applications that select the print driver to use based on the internal printer name and not on the print queue will not be able to select the correct driver when multiple print objects are defined for the same output port ( since there may be 2 distinct printer drivers for the same printer name.) This problem may result in application printing errors. Applications that are known to have this problem are: - Corel Draw V2.0 for os/2 (contact corel for a fix). (printing and print driver selection problems when more that one print object uses the same output port as teh default printer). - Aldus pagemaker V3.01 for OS/2 (contact Aldus). (problems selecting printers when more than one printer object uses the same output port). --------------------------------------------------------- The two abios patch files new in OS/2 2.0 related to printing are: W05010.BIO and W05000.BIO ---------------------------------------------------------- /* ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ */ Common Problems from DOSAP group: (Updated 07/15/92 at 09:00) IPE at ##0160:fff6453f-000d. cs:ip here is 0150:4912. This is the BlastSFT problem. The bug is in file system code. There is a kernel fix for this. The APAR for this problem is PJ04081. A temporary workaround for this problem is to move the application and data files to an HPFS partition. This trap only occurs with FAT partitions. Stacker does not work with OS/2. Stacked partitions will not be accessable. If the customer wants to access data on a stacked partition, he needs to boot DOS and move it to a non stacked (FAT) partition. Stac Electronics has promised an OS/2 version of Stacker for the end of the year. For those customers desperate for disk compression under OS/2, have them contact Max Eidswick at (303) 484-2400. His company is developing a disk compression utililty for OS/2 and will send free beta code to anyone who wants it. The customer must understand that this product is in no way related to IBM or recommended by us. Many communication programs using modems and fax boards are not going to work under OS/2 2.0. Each VDM process can only simulate less than 1000 interrupts per second. This is due to the VDM only having one thread to operate on. While any DOS application is always going to operate on one thread, the OS/2 overhead processing for the VDM can be moved off the main thread, allowing more interrupts to be simulated. Please tell customers that we cannot handle serial communica- tion at more than 9600 baud. Also, encourage customers with fax and other communication boards to contact the board manufacturer to get interrupt information from them. Some vendors produce boards that use polling instead of interrupts that may work better with OS/2. MSCDEX.EXE. Microsoft CD-ROM support. If trying to run this in a VDM it will give "Incorrect DOS version". This must be run in a VMB. Info on setting up a VMB is in the online help. See VMDISK. After the session is booted, we need to add this into the version table. Enter "SETVER MSCDEX.EXE 4.00". Program will now run. EMS not showing up in VDM. This can be one of two problems. First, an adapter conflict. User should use reference disk to check out the memory map. EMS requires 64K of contiguous memory in the UMB. If there is not 64K contiguous, adapter ROM and/or RAM areas need to be moved. If it is not possible to free 64K contiguous memory, the MEM_INCLUDE_ REGIONS to overmap memory reserved for adapter cards. For instance, we see a lot of these problems with 1-2-3. As long as the program is local, a customer could overmap memory allocated to his TokenRing card. Customers can also use the EMS_PAGE_FRAME DOS setting to explicitly place the page frame at a fixed location. The default is AUTO. This should NOT be set to NONE if the customer wants to use EMS. It has been suggested in the past to set this to NONE. Bernie Thompson verifie that this does not give full EMS support (it is not intended to)-- so this should NOT be suggested. Secondly, this may be an actual bug. In some instances, even when there is 64K contiguous memory, EMS does not load. There is a new VEMM.SYS available. I believe this is up on bulletin boards and Compuserv. The APAR associated with this problem is PJ03666. Lotus Development corporation also has a fix available for 1-2-3 3.1. They can be reached at 1-800-223-1662. Customer receiving SYS1200: The DOS environment cannot be created. If seen when starting a DOS session, the customer probably did not install DOS support, or it was not installed correctly for some reason. Doing a selective reinstall and insuring that DOS support is chosen should fix this problem. If this error is seen on bootup, while the config.sys is being processed, check the PROTECTONLY statement in config.sys. This statement should read "PROTECTONLY=NO". If it is set to YES, OS/2 apps are given memory below 640K to operate in, thus leaving no room for DOS. A customer would want to have "PROTECTONLY=YES" only if he will not be running any DOS sessions. Customer receiving SYS0005 errors starting DOS sessions. This is APAR PJ04346. This is usually caused by cross-linked extended attributes. Have the customer boot from the installation diskette and Esc out at Disk 1. The CHKDSK program is on diskette 2. Have the customer switch diskettes. At the a: prompt have the customer type: CHKDSK c: /f (for FAT) CHKDSK c: /f:3 (for HPFS) (c: is assumed to be the startup drive. Adjust accordingly) WordPerfect 5.1: Reading files from FAT partitions sometimes may result in the BLASTSFT problem (IPE listed at the top of this info apar. cs:eip value will be 0150:00004912. We have a kernel fix for this. The same problem is often seen with Autocad 10. Another problem is with the document viewer. This presents the user with a graphical picture of the document (often refered to as WYSIWYG viewer). This is not working under 2.0, and we do not currently have a solution for this. Speaking of Autocad: Version 10, we have a fix; Version 11 uses VCPI (virtual control program interface) which we do not support. Version 12 should run OK. Microsoft C 7.0 is not working under 2.0. The APAR pertinent to this problem is: PJ04082. This is due to lack of full DPMI support. Various errors will be produced, most common of them being an error indicating that a floating point instruction was attempted and no numeric co-processor is present. Novell Netware: 1. Have the user try to load the novell drivers in a VMB and run IPX from there. Use the FSACCESS command to share network drives with other system sessions. For help on setting up a VMB, refer to online help: "Starting specific DOS version" in the master help index, and the VMDISK command in the command reference. 2. Netware Lite is not running under 2.0. This is a bug in Novell code. Contact Novell at 1-800-526-7937. Video problems swtiching from DOS full screen or WIN-OS/2 full screen to desktop and back: Tseng ET4000 has synch problems here if the batch number on the chipset is #TC6059AF or later. Installing the new VSVGA.SYS dated 04-08-92 or later should solve the problem. SYS3176 errors when trying to start DOS or WIN-OS/2 sessions. This problem, when occuring with Tseng ET3000 chipsets. The customer needs to set the DOS setting HW_ROM_TO_RAM ON for every DOS related object he wishes to invoke. need to set DOS_RM_SIZE to 624. If the customer does not have this chipset consider the following: This can be caused by setting the combination of DOS=HIGH,UMB. this error can sometimes be corrected by adjusting DOS settings (HW_ROM_TO_RAM and DOS_RM_SIZE), but is still persisting in many There has been a general APAR created for this: PJ04253, which is avaiting investigation. Problems with PC3270, if using TokenRing, can usually be resolv moving the device driver statements from the config.sys into th DOS_DEVICE area, loading them only for the that session. Addit a document is available in PCOMDOCS PACKAGE on MKTTOOLS or PCTO which helps customer's configure PC3270. We are seeing users w/ 3270 emulators (e.g. Attachmate Extra 3270) which are halting the system. We don't have a solution for this now. Also--a report of PC3270 and DOS Direct Connect (companion product) not working correctly (which is a regression from previous betas and .304e). There are PC3270 sessions hanging the system, which seem to be covered under any of the above. We are waiting for customer info. In summary, there are several problems here. SYS0005 errors running programs This error can be caused by cross-linked EA's and corrected by r CHKDSK with the /f parameter. However, we are seeing many of th where this is not the case and do not currently have a solution, Colorado Tape backup program not working The problem is believed to be in VFLPY.SYS. The APAR number for this problem is PJ03793. COM ports, fax cards, and modems malfunctioning Many customers are complaining about poor performance while usin communications programs in the background. This is a known prob and us due to the VDM process only having a single thread to ope on. When in the background, the thread cannot simulate the inte necessary to keep the connection up quick enough. We have people calling in who can't get their COM 3 and 4 ports on OEM equipment. This can sometimes be solved by adding paramt on the DEVICE=COM.SYS line in the config for the address and IRQ of the COM port. In many instances, this is not working, and we unsure why. We have a WIDE variety of modems, comm programs, and speeds whic are customers are reporting as not working, even in the foregrou This is a MAJOR problem, as almost all home users wish to have t The IBM 8543 internal fax modem card is not functioning correctly using the supplied DOS software. This card is often found in L40SX IBM laptops. The APAR number for this problem is PJ04526. Problems with apps alternating access between a: and b: drives. This has been seen in Borland Paradox 3.5 for DOS, and Norton Utilities 6.1. This problem is being worked. The APAR number associated with this problem is PJ04123. PCTools and Norton Utilities may experience video problems when switching back to thier full screen sessions. This is due to their use of proprietary fonts and screen colors. When OS/2 swtiches away from their full screen session, it saves font and color info, but cannot recognize these fonts & colors. When you return to the full screen there will be blinking characters and other video anamolies. To fix this problem, the user must go into the application and disable the useage of these internal fonts and colors. Refer them to the user's guide of their application. It should be noted that these problems occur under Desqview and other multitaskers as well. PCTools 7.1 install traps in a VDM. This is APAR PJ04165, which is currently being worked. This app needs to be installed under DOS until this APAR is resolved. If dualboot or multiboot is available, boot to DOS and install from there. Reboot to OS/2 and migrate the program to the OS/2 desktop. If bootable DOS is not available from the hard drive, a startup diskette must be created. Boot DOS from the diskette. We need to create a directory on the fixed disk to hold command.com, autoexec.bat and config.sys while we are installing PCTools from the a: drive. Enter the following from the DOS command line: c: md tempdos cd tempdos copy a: command.com copy a: config.sys copy a: autoexec.bat set path=c: tempdos;%PATH% The statements above will allow the PCTools installation to complete without interruption looking for command.com on the a: drive, and a config.sys & autoexec.bat to update at the end of the installation. Insert the PCTools installation diskette and proceed as above. Central Point PCTools has a few problems. PJ04165 addresses a VDM crash when installing the program. This only happens on hw with two floppy drives. VFLPY.SYS is the suspected cause. Work around: boot DOS to install, or disconnect a floppy and temporar ily reconfig machine to install with just one floppy. PJ04164 addresses the fake version problem. You need to fake DOS versio ro run PCTools7.1 If the user shells out to DOS and returns, the version number is lost and a crash results. This problem is generic, as it will happens with any application. Network requestor programs such as IPX (novell netware), banyan vines, etc. should be run in a VMB. Refer to online documentation on "Starting specific DOS version" in master help index and the VMDISK command in the command reference. Block device drivers are not allowed in a VDM. Any error message about a block device driver indicates that the customer is attempting to load one in a VDM. They must use a VMB. Quicken Checkfree is not working properly. The autodial function does not work until the dial window is closed. This is addressed under APAR PJ04585. On TSR's: TSR's, if written properly (that is, using no undocumented DOS features) will load in a VDM. A user can load a TSR from the command line, from the autoexec.bat (to load in every VDM) or from another batch file and enter the /k parameter in the parameters line in the object to load just for one DOS session. Unfortunately, many TSR's use undocumented DOS features. You can try to load these into a VMB, running either DOS from drive a: or from an image, using the VMBOOT command and the DOS_STARTUP_DRIVE DOS setting. Before reporting any TSR problems, have the customer try to load it in a VMB. DOSFindNext-> Trap 000E -> APAR PJ04265 already written. CheckFree 3.0 DOSAP-> Backup program fails in DOS window; run in DOS full screen mode only. WPS-> MMotion multimedia app. with supporting hardware hangs DOS sessions. This is an unsupported IBM product. Refer customer to Nancy Frank at Sparrow Hawk, Inc. (800-779-5166) DOSAP Instant Recall gives Trap E in DOS window...run in full screen mode only Logitech Handscanners -> DOSAP Grey Touch Set XMS_MEMORY to 0 in DOS settings and run alone. Fototouch (WINAP) will run OK under win/r (standard mode). DOSAP PCBoard and h/w gives Trap 000D. PCBoard has fix available. Call 801-261-1686. DOSAP Telemate BBS gives trap 000D ( 0160:fff6453f ). Try commenting out DELDIR statement from autoexec.bat. Also if using Fordos.com, remove it -- just reference command.com instead. /* ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ */ TRAP0002 ( 0002 ): (The following excerpt is from the PS/2 Trap or NMI Error Guidelines Record # H083121) Memory failures running under OS/2 could display a TRAP0002 or a TRAP000C error message. The OS/2 error message will inform the user that the operating system has detected a hardware memory error on the system board or on an option card, in many cases. The most common type of TRAP0002 error is caused by memory, but it may on some occasions be caused by a system board or a micro channel adapter failure. It may also be caused by other hardware error or software errors. A new Service Aid Diskette Utility ( SAD ) is now available which will provide additional help in determining which of four possible causes of a TRAP0002 error has occurred. The four causes of a TRAP0002 error are: 110 Error - System Board memory Parity Error 111 Error - Memory Expansion Adapter Parity Error 112 Error - Watchdog Timer Error (Could be Hardware or Software) 113 Error - DMA Arbitration Error(Could be Hardware or Software) Microsoft ( MS ) LAN MANAGER Version 2.2 is required in order to run under OS/2 2.0, per MS. If customer is running LAN MAN 2.0, a device driver error may be generated at boot time from the config.sys stating problems loading the NETBEUI.OS2 driver. The interim workaround for running a release below 2.2 would be to run from a VMB ( Virtual Machine Boot ). MS Lan Mgr 2.2 is not yet available as of 5/20/92. Customer should be directed to contact Microsoft for availability of LANMAN 2.2. keywords: MS Microsoft LAN MAN NETBEUI CONFIG.SYS Error Other workarounds reported to us are: Use a DOS lan requestor with a MS lan man server -- or -- Use IBM Lan Server 2.0 requestor code with a MS lan man server. Intermitten hangs with SEAGATE ST02 Controller. Investigation has shown that this card cannot be used with OS/2 2.0. Customer have been recommended to replace this card with a 16 bit controller card. Hangs and intermitten problem with CORE 1GB harddrive and IBM SCSI adapter. Problem is being investigated by IBM hardware support. Contact them. Hangs and traps on Mod 90 and 95 Memory SIMMS must match on these systems, this includes memory speed, size and manufacture. Also the Right memory card ( closest to the power supply ) must be completely empty or completely populated. Reported by customer who confirmed with Northgate: Northgate 386/33's that contain up to 8 meg on the motherboard and require a daughter card for 9-16 meg may have a defect in the daughter card that causes a trap 0002 in OS/2 2.0. The problem arises when more than 12 meg is on the system, and only occurs on a 32 bit operating system. OS/2 2.0 should run OK with 12 meg. The customer purchased his system in 1989. The motherboard was made by Motherboard Factory. Intermittent hangs and traps. Sometimes trap 000D , sometimes trap 000E . Although this could be a number of things, recommend the following: - Disable cache - Disable shadow RAM - If customer has AMI BIOS disable "hidden refresh" and "fast decode enable" - Change the wait states. Trap running DOS application where CS varies but IP is 000006C5. This can be corrected by setting MOUSE_EXCLUSIVE_ACCESS=ON for each DOS session. On Compaq Laptops,the PWRCON.EXE from the User Programs Diskette for OS/2 Version 1.x, is not supported under OS/2 2.0. PWRCON is a program to allow a user to control power conservation on a battery operated system. It can be run from Config.sys, Startup.cmd or manually started. This program is not supported currently under OS/2 2.0. If the disk is formatted HPFS, it can cause the following trap when the laptop automatic screen blank out occurs on a Compaq LTR Lite 25: Trap 000E CS:EIP 0160 : FFF65898. MODEL 80, SCSI DRIVE AND OEM MEMORY BOARD, XTEND MICRO PRODUCTS, HANGS OR STALLS SYSTEM FOR UP TO 20 MINUTES MODEL 8580-041 WITH SCSI ADAPTER AND XTEND OEM MEMORY CARD HANGS FOR AS MUCH AS 10-15 MINUTES WHEN "LAUNCHING" OR STARTING AN APPLICATION. CAN DOUBLE CLICK ON ICON FOR APP OR ON DRIVES C: AND SYSTEM STALLS. APPS INCLUDE DESCRIBE 3.0, DISPLAYWRITE COMPUTER FOR OS/2, SPELLING CHECKER FROM WORDPERFECT. THE DRIVE LIGHT STAYS ON, THE MOUSE ARROW CAN MOVE, BUT THE KEYBOARD IS DEAD. CTRL ESC DOES NOT WORK. WIN SYSTEM CLOCK GOES AWAY AND THERE IS NO BUSY CLOCK PROGRESSION INDICATOR TO DENOTE SYSTEM ACTIVITY. AFTER A SIGNIFICANT AMOUNT OF TIME, THE SYSTEM RETURNS TO NORMAL WIN SYSTEM CLOCK RETURNS AND IS UPDATED WITH CORRECT TIME. WHILE THE SYSTEM IS STALLED, IF KEYSTROKES OR MOUSE MOVEMENTS ARE INITIATED, THEY ARE STORED IN THE BUFFER AND PLAYED BACK WHEN THE SYSTEM RETURNS. REPLACING OEM MEMORY BOARD WITH IBM MEMORY BOARD RESOLVES PROBLEM. THIS PROBLEM IS BEING HANDLED IN APAR PJ04266 /* ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ */ INFO APAR TO DOCUMENT COMMON OS/2 PROBLEMS AND SOLUTIONS PROBLEM: DOS application generated print job spools but does not print. (Green arrow still points to document in job object found in the print object). RESOLUTION: The DOS application has not closed the printer data stream. If the DOS application is printing using BIOS interrupt 17h then use the PRINT_TIMEOUT DOS Setting to force the data stream closed. You may be able to determine if the application is using int 17h (as opposed to int 21h) by the destination name. LPTx in Win-OS/2 uses int 17h while LPTx.OS2 uses int 21h function calls. Parallelx in DOS uses int 17h. LPTx in DOS can be either one, older versions of applications use int 17h. The PRINT_TIMEOUT setting, by default, is turned ON and set to 15 seconds. User should wait 15 seconds, if the job doesn't complete spooling, then the DOS application is not using int 17h (See discussion below on lptdd.sys). PROBLEM: DOS application generated print job is split into several spool files. SOLUTION: If the DOS application opens and closes the printer data stream for every character, line, or page then there is nothing short of disabling the spooler for that printer to correct this problem. An alternative may be to upgrade the application. Contact the manufacturer. If the problem occurs with complex printouts, then you may need to increase the DOS Settings PRINT_TIMEOUT value. ╣ *PROBLEM* The DOS application generated print job will not begin printing until the application is terminated. *SOLUTION* The DOS application has opened the data stream and sent the print output but has not closed the the data stream. If the application is printing using int 21h, then use the DOS_DEVICE DOS Setting to load the c: os2 mdos lptdd.sys device driver to convert the int 21h calls into int 17h calls. The PRINT_TIMEOUT DOS Setting can be used to close the print job. ------------------------------------------------------------- *PROBLEM* My security device attached to the parallel port doesn't work. Any of my DOS applications that use the security device can only be started from one DOS session. An error message is displayed when trying to start additional copies of this application. *SOLUTION* USER can press the key sequence Ctrl-Alt-PrtSc simultaneously to have the security software release access to the parallel port software prior to starting second copy of the DOS application. ------------------------------------------------------------- *PROBLEM* After printing from one DOS application and then trying to print from anywhere else within OS/2, nothing prints. When I terminate the DOS application, other printing works fine. *SOLUTION* The particular DOS application you are initially printing from, is accessing the parallel port hardware directly. OS/2 prevents collisions from two or more applications trying to access the same parallel port hardware simultaneously by preventing the second access until the first DOS application terminates. This is true even if the second application is the OS/2 print object! ------------------------------------------------------------- *PROBLEM* Other parallel attached devices (not printers) such as tablet systems, LAN adapters, and parallel to SCSI devices do not work in a DOS session. *SOLUTION* There's a current restriction within DOS sessions where hardware interrupt IRQ7 is not reflected into the DOS session. OS/2 development is aware of this limitation and is working on a solution. These hardware attachments may attempt to use this feature of the parallel port and are prevented from doing so. ------------------------------------------------------------- *PROBLEM* I have a PS/2 system that supports a DMA parallel port. Can OS/ take advantage of this? *SOLUTION* The current systems with a DMA parallel port include PS/2 models 56, 57, 80-A21, 80-A31, 90 and 95. Customer with these systems should ensure that the built-in parallel port arbitration level is set to SHARED7 (DMA is enabled). OS/2 will automatically take advantage of this feature; no additional setup is required. OS/2 1.3 customers with CSD 5054 or greater can reenable this feature. Use the reference diskette shipped with this system to view the system configuration (setup). ------------------------------------------------------------- *PROBLEM* My printer does not have a supported OS/2 PM printer driver. *SOLUTION* If your printer driver is not among the 200 printers supported then determine if your printer supports a more common printer emulation mode. Install the printer driver that supports your printer in the emulation mode. ------------------------------------------------------------- *PROBLEM* My printer has a supported Win-OS/2 printer driver but not a PM printer driver. How should I configure my system? *SOLUTION* If you will be doing primarily Win-OS/2 printing then setup the proper Windows printer driver within the control panel. Setup the OS/2 print object with the IBMNULL printer driver. You should be able to print from Win-OS/2 with no problems. Contact your printer manufacturer to obtain an OS/2 printer driver or to determine what other printers your printer emulates. ------------------------------------------------------------ *PROBLEM* Printing from Win-OS/2 is very slow, everywhere else is okay. *SOLUTION* If printing from Win-OS/2 and Print Manager is specified for the printer, then you may need to set the Print Manager Options menu to a higher priority than what it is currently set to. ------------------------------------------------------------ *PROBLEM* My system has an AT bus (ISA) and my parallel printer prints slowly from anywhere under OS/2, DOS, or Win-OS/2 sessions. *SOLUTION* Your parallel port address and hardware interrupt levels are not set correctly. Valid parallel port combinations include 3BC/IRQ7, 378/IRQ7, and 278/IRQ5. Power off your system, remove the parallel port adapter and configure the adapter by adjusting the DIP switches and/or jumpers to set the parallel port to one of these industry standard combinations. Make sure that other adapter cards are not interrupting on the same interrupt levels. Sound, MIDI and serial cards can share these same hardware interrupt levels. ------------------------------------------------------------ *PROBLEM* Printing works just fine under the DOS operating system but after installing OS/2, printing does not work. *SOLUTION* If the print output can be seen in the print object (if spooler is enabled), then the problem is most likely either the cable or the hardware interrupt level. See the solution above for directions to configure your parallel port. Some signals used to transmit data under OS/2 are not used when printing under DOS, some cable manufacturers reduced the costs of their cables by not wiring these signals. You may need to purchase a new cable. Some older parallel port adapter cards do not interrupt properly, since DOS did not use this feature you may not have seen this problem. You may need to upgrade your parallel port adapter. --------------------------------------------------------------- *Problem* . Customer has Printer Speedup boards and or utilities that can be used under DOS but not OS/2 such as printer engines and Postscript speedup devices. . *Solution or Limitation* . These Speedup boards are not supported under 2.0. The only possibility of using them is if they are not for a specific printer port that is also a generic printer port under OS/2 for example LPT3 and a physical LPT3 device exists, the customer may be able to either use the device driver in a VDM or in a VM Boot session. This is the only possible support. -------------------------------------------------------------- Problem: When printing to a OS/2 1.3 Server from an OS/2 2.0 Requester with either a PM application or 3270 Print (Communications Manager), the print session will hang or an error will be received in the PM application that a DevEscape failed. . Resolution: The printer drivers on both the 2.0 requester and 1.3 (preferrably WR05050) server should be of the same type and of the same level. If in doubt, use the 2.0 printer drivers when configuring the systems. Also see APAR PJ03997 for resolutions. ------------------------------------------------------------ . *PROBLEM* Printing from applications that use INT 2F function 01H (print spooling feature of DOS) will not work. . *SOLUTION* INT 2F function 01h is not currently emulated in a VDM. Applications that use this interrupt will not print. These applications are ones that require that the PRINT.COM is loaded as a TSR, using the /d option. A DOS kernel fix exists that returns a value of 01h (not installable) if the application were to query to see if the DOS spooler (PRINT.COM) was loaded. Note that attempts to load PRINT.COM in a VDM session will currently fail. Emulating int 2F funct 01H is currently being considered for future releases. Currently there are no known major applications that use int 2F for printing. /* ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ */ COMMON VIDEO PROBLEMS IN OS/2 2.0 - INFO APAR 1) Video goes out of synch when switching from DOS full screen or WINOS/2 full screen to desktop. This is usually caused by Tseng ET4000 chips in the video controller (batch TC6059AF or higher only!). If the customer has these chips in his video board, send the fix for APAR PJ03677. 2) SYS3176 error when starting a DOS session. Try setting HW_ROM_TO_RAM to ON for each session that is having the problem. Also try changing DOS_RMSIZE to 624 instead of 640. If this does not work, the VSVGA.SYS fix from IBM might resolve the problem. 3) ATI 8514 Ultra or Graphics Ultra locks with white screen on bootup. The older ATI ROM chips return an incorrect monitor ID when queried by OS/2. Have customer call ATI at 416-756-0711 to obtain an update. Remember, these boards MUST be set up as an 8514 PRIMARY display and the statement DEVICE= OS2 MDOS VVGA.SYS MUST be changed to DEVICE= OS2 MDOS VSVGA.SYS 4) C0000005 error on bootup. If the customer has Western Digital chips (C30 or C31), with 1MB memory, send the fix for APAR PJ03721. If not, remove the SVGA info from the CONFIG.SYS file. Note that this will limit the user to VGA only. Change SET VIO_VGA=DEVICE(BVHVGA, BVHSVGA) DEVICE=C: OS2 MDOS VSVGA.SYS to SET VIO_VGA=DEVICE(BVHVGA) DEVICE=C: OS2 MDOS VVGA.SYS 5) Trident video problems: If the user is experiencing problems with super VGA on Trident based video boards, they will need to call Trident (not IBM) for the proper SVGA driver. If they have problems with the driver that Trident sends them, they need to call Trident, not IBM. IBM only supports VGA mode on Trident boards with 8900 or 9000 chipsets. The 8800 chipset is not currently supported nor do I believe that it will be. 6) Dell computer Video problems. Dell's 486/50 uses a Western Digital 90C30 chip. Our standard BVCHSVGA.DLL fix should help. Other models (325SX, 325, NL25, etc.) do NOT use this chip and this fix DOES NOT apply. Dell uses a customized Phoenix BIOS. Here are a few CMOS settings that have been known to help. Use CTRL-ALT-ENTER to access CMOS setup: FAST_VIDEO OFF if sync problems FAST_VIDEO_BIOS (shadowing) OFF if problems BIOS_CACHING OFFif problems COMPATIBILITY_SPEED ON for faster Mhz machines 7) Errors loading video drivers on bootup. The selective install utility sometimes will add the same device driver statement more than once to the CONFIG.SYS file. This will result in an error message every time the user boots up. The system will function properly and upon investigation you will find that driver file DOES exist in the proper directory. It is simply trying to load the driver twice during bootup, the second attempt will fail. Remove the duplicate DEVICE= statement from the CONFIG.SYS. /* ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ */ WINAP INFO APAR - GENERAL WINOS2 INFORMATION 1. Hit List (keyword HITLIST) Regularly updated 'Hit List' of questions commonly asked of OS/2 support, and the answers. Q. I've found a problem with the WIN-OS/2 printer driver that I'm using with my printer? How do I get an updated version of the driver? A. The WIN-OS/2 drivers were not written by IBM, but are licensed for inclusion in OS/2. If you need a driver update IBM might be able to obtain it for you, but you'll get it much quicker if you contact the supplier directly. Q. How do I run WIN-OS/2 in real mode? A. Type 'winos2 /r' from an OS/2 'DOS Full Screen' session, or put '/r' in the parameters held for an OS/2 shell object. Q. Why won't ScanMan and FotoTouch run under WIN-OS/2? A. They both make a 4B interrupt call to create a DOS thread. This isn't currently supported, but will be addressed in a future release. See APAR PJ04100 (status; closed). Logitech scanners will work from WIN-OS/2 in but in real mode only. Note that Ansel (Fototouch's predecessor) will work in real mode. Q. I get DOS Error 5 when I try to run some of my Windows applications under WIN-OS/2? What's the fix? A. Boot from OS/2 boot disk, insert disk 1 when prompted. When you get OS/2 Welcome screen press ESC. Insert disk 2 and type A:CHKDSK C: /F (FAT) or /F:3 (HPFS) where 'C:' is the drive OS/2 was installed to. Repeat CHKDSK until it runs without any errors. Q. I have the Canadian version of WordPerfect 5.1, how do I run FIXWP? FIXWP (see OS/2 readme) doesn't work for the Canadian version. Call WordPerfect and ask for interim release. Q. SHIFT-ESC doesn't seem to do anything under WIN-OS/2. This means certain programs (see Attachmate under Applications) can't be run. Is there a fix? A. A keyboard bypass option for SHIFT-ESC needs to be added to WIN-OS/2 and DOS settings for CUA (Common User Access) compatibility. See APAR PJ04880 (status; open). Q. I Get FATAL ERROR 0X0401 trying to start a Windows application in a WIN-OS/2 session. What's the fix? A. This problem is caused by one or more of the drivers or font files listed in the WIN-OS/2 SYSTEM.INI or WIN.INI file being absent or not loading correctly. This can happen if the application migration/installation was incomplete/incorrect. Check device statements, or re-install application from WIN-OS/2 Full Screen. This error has also occurred on systems running in XGA or 8514 video mode when an application tries to use large fonts. It might be necessary to modify the WIN-OS/2 SYSTEM.INI file as follows; fonts.fon= xgasys.fon, fixedfon.fon= xgafix.fon, oemfonts.fon=xgaoem.fon. Q. I have an 8514 display and am having trouble using DDE with WIN-OS/2. What's the fix? A. If you have an 8514 display use DOS Settings to set VIDEO_8514A_XGA_IOTRAP to Off and VIDEO_SWITCH_NOTIFICATION to On. Q. Data I put in the OS/2 clipboard doesn't show up in the WIN-OS/2 clipboard. What could be causing this? A. Because of the particular data format there may be a rendering problem that prevents the reception of the data from the WIN-OS/2 clipboard by the WIN-OS/2 application. A private data format used by one application could be unusable by another. WIN-OS/2 clipboard issues are covered in a similar document (or INFO APAR) to this one. Q. I'm using the EPSON.DRV WIN-OS/2 printer driver and I get duplicate form feeds, can I disable form feeds? A. The EPSON.DRV driver doesn't provide disable form feed or intelligent form feed options. If this causes you a problem you'll need to select another driver that works for your printer. APAR PJ03858. . /* ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ */ **************************************************************** FAX NUMBERS FOR OS/2 RELATED PRINT PROBLEMS. THESE FAXES PROVIDE SOLUTIONS FOR KNOWN PROBLEMS. **************************************************************** . . FAX # PROBLEMS ADDRESSED BY FAX --------- ------------------------- PR001 FAX - When trying to print to the LPT port in the system, OS/2 returns an error stating that the printer is off-line, off, or out of paper, or cannot write to LPTx. Also, the printing may have worked under DOS, but does not work under OS/2. . - Receive printer pop-up that the printer is off-line or it is not responding when starting a job. . - Erratic or slow printing *************************************************************** INSTALLATION PROBLEMS FOR OS/2 2.0 FOR IBM SYSTEMS AND PCM ====================== KNOWN INSTALL PROBLEMS ====================== ************************ MEMORY PROBLEMS ************************ Common Symptom: Trap 2, Trap 6 or other Trap at 60000x:9084. These problems are caused by: Mismatched memory simms (from different manufactures) - this is especially common if you recently added memory to your system, or if it was assembled from parts (not a recognized brand of clone). Mismatched memory simms (different classes) 1x9 simms cannot be mixed with 1x3 simms. Also, the 1x9 simms seem to be more reliable than the 1x3 simms. Slow memories on 486 machines (you may need 60 or 70ns memories). Cache problems. Solution: Replace memory and/or tune wait states, disable cache during install, turn turbo switch off. ****************** SCSI PROBLEMS ****************** These problems are caused by: incorrect BIOS need OS/2 compatible driver from manufacturer incorrect identification of adapter by OS/2 mismatched settings of SYNCH/ASYNCH mode for SCSI controller, hard drive, causes slow drives, misssing icons - see OS2TNT, V2TECH Solution: Update BIOS, get driver from manufacturer, change settings. Known problems: AMI SCSI - slow, noisy disk - BASEDEV workaround - see APAR II06081 FUTURE DOMAIN 16XX SCSI controller - hang on LOGO screen after reboot following good install - check for interrupt conflict - see APAR II06081 Always Technology SCSI - BIOS upgrade - see APAR # II06081 Bernoulli Boxes - UNSOLVED problem with IOMEGA ADAPTER - see APAR # II06081 Colorado Memories Tape Drive - fix available from Colorado - see APAR II06081 PROCOMM+ SCSI disk adapters (Microchannel) - UNSOLVED, talk to PROCOMM - see APAR # II06081 Early versions of IBM 16-bit SCSI adapters - update microcode - see APAR # II06081 dependencies - stick with IBM and Toshiba SCSI CD-ROM drives - others later - see readme Removable media support - Bernoulli (IOMEGA), and SyQuest - support is limited, treats them like big floppies - see readme All Adaptec adapters - SCSI hard disks must be configured as SCSI target ID 0 or 1 to be able to start up from that hard disk - see readme BIOS will not recognize - configure as non startup drive - see readme Adaptec AHA-174x adapter with IBM WDS-3180 80MB SCSI, IBM WDS-3160 160MB SCSI - Adapter will not recognize in 'STANDARD MODE' (AHA-154x emulation). Adapter should be configured in 'ENHANCED MODE' - see readme Future Domain TMC-850/860/875/885 w/BIOS revision level 7.0, and Future Domain TMC-1660/1670/1680 w/BIOS revision level 2.0 can cause "Disk Read Error" on installation disk for model 35 and 40 - need BIOS upgrade - see readme AMI "Fast Disk" and AMI "Fast Disk II" SCSI adapters are incorrectly recognized as Adaptec adapters - see readme for workaround Always IN2000 SCSI adapter - causes Internal Processing Error - need BIOS upgrade VCN1-02 - see APAR # II06081 Quantam Plus Hardcard - need EPROM upgrade - see APAR # II06081 SUMO SCSI adapters don't seem to work with OS/2 - talk to manufacturer ******************** FDISK PROBLEMS ******************** Some common problems: selections to dump or more disk. Insufficient disk space for swapper file growth on low memory systems - suggest install selections to dump or more disk. Incorrect setup information in CMOS memory for hard drive being used - see if it works under another operating system. Slow, noisy disk or FDISK errors (especially on RLL, MFM, or ESDI disks) - BASEDEV workaround - see APAR II06078 Nonstandard or out of date BIOS (especially with IDE drives) - disk inaccessible or FDISK errors. Look for Phoenix or AMI standard BIOS and check dates in MORETIP or info APAR #II06078 Incorrect identification of adapter by OS/2 Trying to install on a drive which was compressed using a stacker utility - suggest uncompressing the disk or reformatting. Trying to install over a Beta version of OS/2 2.0 (1.3 is OK) - reformat first. Trying to install HPFS with less than 6M of memory - dump HPFS or get more memory. Trying to install on less than 4M (user may think he has 4M, but some cache arrangements or ROM to RAM remapping can steal some) - try to disable these features in CMOS setup. Disk corruption/failure (it won't even support DOS) - try high and low level format or get new drive. Quantum IDE hard disks require a free ROM update from Quantum. Install hangs on Disk 1 - this may be caused by having disk caching enabled on the drive controller card - try disabling it - also try turning off the controller's asynchronous memory refresh capabilities if applicable. already reside on the hard disk. IBM OS/2 2.0 can only be installed from Drive A, like DOS (unless you swap drive cables/change CMOS setup to fool system) Automatic migration of your DOS CONFIG.SYS and AUTOEXEC.BAT files can cause problems and is not recommended - recover using original config.sys in OS2 SYSTEM. If you have Windows 3.1 installed on your system do not migrate your Windows desktop. If you are using the IBMINT13.I13 driver to access an MFM, RLL, or ESDI hard drive, and the hard drive has more than 1024 cylinders, be certain your hard disk adapter's sector translation mode is enabled. COUNTRY.SYS problems are usually a symptom of a disk which is not recognized by OS/2, and may be caused by the following: Conflict with another device attached to the same controller card. Try removing anthing like a tape backup, which may be the cause of the conflict. On a P70, you need ECA068, contact IBM CE. ****************** BIOS PROBLEMS ****************** Many of the problems above have old bios as their root cause, so there is a lot of overlap between this and other problems - see details on how to check dates in MORETIP or info APAR #II06078 Some common causes: - Wrong keyboard BIOS - Outdated video adapter BIOS In many cases these problems stem from old standard BIOS which is easily replaced, but in some cases, customer has old "custom" BIOS (manufacturer has included functionality specific to the motherboard on the BIOS). In this case there may be no upgrade path and the motherboard may need to be replaced. For more detailed information on BIOS, see INFO APAR II06082 ************************************ ADAPTER CONFLICT PROBLEMS ************************************ On ISA machines, interrupt conflicts and memory mapping conflicts can cause a variety of problems. For example, many SuperVGA adapters use large chunks of upper memory, and many hard disk adapters have on board ROMs which can be mapped into this area as well. Also, Soundblaster boards use INT 7, which conflicts with many printers. Adapters must cooperate in their use of memory and interrupts and must not share address space or interrupts. Callers should be encouraged to check interrupt level settings on their boards. Also try removing cards that are not needed during install. Sometimes you will get a Trap D at 160:FFFxxxxx. ******************************** VIDEO ADAPTER PROBLEMS ******************************** Install problems resulting from video adapter conflicts typically occur on disk 6 or later. This is when the graphical install icons come up, and it is the first place where more complex calls are made to the video BIOS. One notable exception is the Oak video card. Try another video card during install, or try the card in an 8 bit slot during install. Try some different adapter DIP switch settings listed in your adapter manual. Make sure video card is in VGA mode with auto-sense turned off. Some specific problems: If you have a super VGA adapter, install should always be done as VGA. If you have an ATI Ultra, Vantage, or other 8514/A hardware compatible ada ter, use 8514/A driver for install. C0000005 is displayed on the screen during install (e.g. Western digital PVGA1D) - need fixed version of BVHSVGA.DLL Hang on Disk1 right after LOGO screen caused by OAK video card BIOS problem. Workaround is to patch loader file - see Install Adapter APAR video card is in VGA mode with auto-sense turned off. White screen after installation with no system activity - Try setting the video card to 8 bits and moving the video card to an 8-bit slot, also disable the auto-switching capability of the card if possible. Out of Synch/Install problems - caused by problems addressing card in 16-bit mode, switch to 8 bit mode (using jumpers or dip switches on board) and put in 8 bit slot. Install Adapter APAR Some super VGA cards have ROMs with conflicting addresses for some hard disks. ************** OTHER PROBLEMS ************** Failures very early on install disk (especially Zeos notebooks) - try applying patch to sysinstx.com in Install Other APAR Dual Boot feature does not allow boot back to OS/2 from DOS - there may be a disk cacheing utility or a TSR which blocks this. /* ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ */ DOSAP INFOAPAR, QUESTIONS TO ASK ABOUT DOSAP PROBLEMS When DOS applications experience problems running under OS/2, our main goal is to determine whether the problem is with the operating system or not. Even though the error received is from OS/2, the error could be due to the application not following standards or it could be a usage problem (usually corrected by DOS settings). Steps to take to analyze a DOSAP problem: 1. Gather the information on the 857 form by entering 'FA 857' from the PMR. 2. We want to know first if the problem is with the DOS session or specific to certain applications. If the customer can open a DOS full screen prompt and get a prompt, there is no problem creating the DOS environment in OS/2. In addition, if he can open a DOS window and get a prompt, his problem is most likely not video related. 3. Once the prompt is received, ask the customer if he can access files from the prompt with 'dir', 'type', and similar DOS commands. If this is true, he probably doesn't have a disk or file system problem. 4. Now, let's see what applications are failing. If the customer is receiving an out of memory error of some sort, there are two prime candidates. If the error is from OS/2 and contains the text "heap space is full", the customer is out of swapper space. In general, this is something that should always be checked. It is very important that this information be included in the 783 form (swapper on: field, and "free" field for that partition). If the error is something generated by the application, expanded memory is usually the cause. Please see APAR II06047 about EMS problems. 5. If you are not familiar with the application, ask if the app requires any hardware other than the base system. If it requires a modem, get the COM port settings (COM port number, IRQ, etc.). You may want to use form insert 864 for this use. Record any hardware required in the PMR. 6. IS THE PROBLEM REPRODUCABLE? If it is not readily repro- duced, have the customer stop all other running applications and check whether it will fail WHEN RUNNING ALONE. 7. If the problem occurs when switching sessions, it's probably NOT due to DOS emulation. Please reconsider what other subsystem may be at fault. 8. If the machine is a clone, ask the customer if he has altered any DOS settings. If you bring up help for the DOS settings and scroll down to the bottom, you will find a hypertext link to "DOS and WIN-OS/2 Settings, Descriptions". Double-click on this to bring up categories for the different DOS settings. By choosing a category, all pertinent DOS settings are listed, and descriptions of them can be viewed. The following gives a list of general problems, and what DOS settings should be checked: Memory problems: EMS_MEMORY_LIMIT MEM_INCLUDE_REGIONS EMS_PAGE_FRAME XMS_MEMORY_LIMIT DPMI_MEMORY_LIMIT DOS_RM_SIZE Video problems: all VIDEO_* settings Communications problems: COM_HOLD DOS_BACKGROUND_EXECUTION IDLE_SECONDS IDLE_SENSITIVITY also check CONFIG.SYS parameters on DEVICE=COM.SYS line 9. If the problem "hangs the system" it is important to determine if the system is REALLY hung. Rule #1-- if the mouse moves, the system is not hung. Have the customer use repetitve Ctrl-Esc's to cancel the session. A pop-up should appear indicating that a particular program is not respond- ing. It can then be ended. Insure that "FI 778" is performed for a TRAP or IPE and ALL register information is entered. Just the location or type of trap provides no useful information in almost all cases. 10. Ask the customer if he has tried the application in a VMB (virtual machine boot). Refer the customer to the online help on "Starting specific DOS version" in the master help index and the VMDISK command in the command reference. If using VMDISK to create an image file, remind the customer that he must have a DEVICE=FSFILTER.SYS statement in his config.sys in the image. If OS/2 was installed on an HPFS partition, FSFILTER.SYS must be copied from the OS2 MDOS directory onto the diskette BEFORE the image is created. Specific DOS sessions are often needed to run network requestor programs such as Novell Netware and Banyan Vines. /* ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ */ INFO APAR WITH TIPS FOR USING COM PORTS ON AT BUS SYSTEMS . **************************************************************** THESE ARE INFORMATION TIPS FOR COM PORT USAGE ON AT BUS SYSTEMS **************************************************************** . Keywords: com comm communication communications async com1 com2 com3 com4 com1: com2: com3: com4: problem problems hang hangs port ports infoapar info apar os2 com comm LOCAL FIX: CONTENTS: Installation of COM Ports. Trouble Shooting Interrupts on AT bus machines Installation of COM PORTS ========================= The original ISA machine (the IBM PC-AT) allowed for the definition of up to four serial communications ports. However, there has never been any hardware architectural standard that defined the I/O port addresses or Interrupt Request (IRQ) lines associated with communication ports #3 or #4. Over the years a convention was established which places the port addresses for COM3 and COM4 at 03E8 and 02E8 respectively. This is a generally accepted convention and is not a standard. This is done by the filling in the optional parameters on the DEVICE statement for the communications device driver (COM.SYS). Using an editor, extend the DEVICE = statement as indicated below: DEVICE=X: OS2 COM.SYS (n,a,i) (n,a,i) where X = the drive where OS/2 is installed n = the Com port that you are attempting to access a = communications port I/O address (03E8, 02E8 for example) i = IRQ level For example, to specify that COM3 is at address 03E8 on IRQ5 and that COM4 is at address 02E8 on IRQ10 we would use the following statement (assuming that OS/2 is installed on the C: drive): DEVICE=C: OS2 COM.SYS (3,3E8,5) (4,2E8,10) Note that this syntax is actually quite general. If we wanted to set some non-standard parameters for COM1 and COM2 we could have done this as well and all within the same statement. The I/O address and IRQ level should be noted in the documentation that came with your adapter. Either or both might be fixed values or be settable to a range of values via jumpers or switches. In some cases you may find that the values are fixed or that the range of settings available to you is insufficient to avoid the sharing conflict. TROUBLE SHOOTING: ================ SYMPTOM: The COM port is not recognized or does not work at all ---------------------------------------------------------------- A. IF it is an AT, ISA, or EISA machine If trying to use COM 3 or COM 4: A.1. Parameters in DEVICE=C: OS2 COM.SYS in CONFIG.SYS are required A.2. IRQ for COM port in OS/2 must be different for each COM port. DOS does not handle multiple interrupts at the same time but OS/2 does. A.3. IRQ 5 is recommended for COM3. If IRQ 5 is taken, IRQ 9 or 10 is recommended. A.4. Reboot the system A.5. If error message during boot : COM3 not installed because of Interrupt is aleady in use. => Check if there is any IRQ conflict with other device driver or hardware. B. If system (AT bus or MCA) boots without error but any of the com port still not working at all Issue a Mode command to the problem com port => If it indicates com port not installed check IRQ conflicts (see A.5) => Check Mode command parameters to be correct (See MODE_CMD). SYMPTOM: Application appears to hang ------------------------------------- C. When the application is started: C.1. IF an OS/2 application => Ensure your COM port works in standalone DOS. => Using MODE command, turn off IDSR, ODSR, and OCTS (See MODE_CMD) => (See SUGGESTIONS) C.2. Using a DOS application => (Start from Letter A.1 Above and work down) => If still have problem, remove VCOM.SYS. D. After it has been running for some time: D.1 Using an OS/2 application and experiencing a lot of data loss => Lower the baud rate => (See SUGGESTIONS) D.2 Using a DOS application: D.2.1 A BBS communication package. => Set COM_HOLD DOS Setting to ON => If using a FOSSIL Driver, then If X00.SYS Rem VCOM.SYS in config.sys, else If another FOSSIL Driver. Rem VCOM.SYS won't work => If using less than 12MB of memory => See (SUGGESTIONS) D.2.2 A FAX application which uses a COM port. => Known limitation need to operate at < 9600 bps => Use OS/2 application for high speed fax. (Currently FAXPM and BitFax) D.2.3 An application which uses QBASIC or BASIC CTTY => Install COMDD.SYS in C: OS2 MDOS directory D.2.4 Some other ASYNC application. => Check with Chapter 5 of Readme. Example: -CrossTalk for Windows needs that BUFFER=OFF. -Mirror III is similar to CrossTalk. BUFFER can be controlled with MODE command. -LapLink PRO, IDSR, ODSR, and OCTS of all COM ports must be OFF. (See MODE_CMD) -LapLink III, remark out VCOM.SYS. D.2.5 In Auto Answer mode and a call comes in: => Known problem APAR PJ04200. => Remark out VCOM.SYS in Config.sys SYMPTOM: OS/2 does not detect FIFO ----------------------------------- E.1 COM.SYS detects FIFO and utilizes it, however VCOM.SYS only emulate as 16450 or 8250 chip and hides FIFO from DOS app. No performance problem is caused by this. E.2 If BUFFER = N/A (not available) is concerned, MODE is broken. SYMPTOM: The line is dropped randomly or fils to download file --------------------------------------------------------------- F.1 While switching sessions =>change PRIORITY_DISK_IO in config.sys from YES to NO, reboot. Go to F.2 below if problem continues F.2 Without switching sessions. => Increase idle sensitivity to 100 => If problem happenning during noticeable disk activity add additional memory to reduce swapping. => Try increasing DISKCACHE in config.sys (e.g. from 1024 to 2048) SYMPTOM: Slow through-put, poor performance -------------------------------------------- G.1 Using an OS/2 application => (See SUGGESTIONS) => Using MODE command, turn off IDSR, ODSR, and OCTS. (See MODE_CMD) G.2 Using a DOS application => Increase IDLE_SENSITIVITY to 100 => (See SUGGESTIONS) Note: Since interrupt must be simuated in VDM session, the throughput decreases. MODE_CMD: Use MODE from an OS/2 Command line or DOS command line and set IDSR, ODSR, and OCTS equal to OFF. eg: MODE COM3:9600,N,8,1,OCTS=OFF,ODSR=OFF,IDSR=OFF sets COM3 to 9600, no parity, 8 Data Bits, 1 Stop bit, OCTS, ODSR and IDSR to OFF. If OCTS and/or ODSR are set to ON, the com port will not transmit data unless CTS and/or DSR signal lines are enabled. If set to OFF, the com port will transmit regardless of the state of signal lines CTS and/or DSR. If IDSR is set to ON, the com port will discard the incoming data unless DSR signal line is enabled. If set to OFF, the port will receive data regarless of the state of DSR. If any problems transmitting or receiving, set OCTS=OFF, ODSR=OFF, IDSR=OFF to ensure that the hardware connected to the com port is not preventing the port from transmitting or receiving. SUGGESTIONS: => Increase IDLE_SENSITIVITY in DOS Settings => Adjust the disk cache in CONFIG.SYS => Change PRIORITY_DISK_IO from YES to NO in Config.sys => To reduce swapping add more memory /* ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ */ FDISK INSTALLATION PROBLEMS ************************************************* *** GENERAL INFO ON DRIVE PROBLEMS *** ************************************************* These problems can be caused by - incorrect setup information in CMOS memory for hard drive being used - disk corruption/failure - incorrect identification of adapter by OS/2 - trying to install on a drive which was compressed using a stacker utility - trying to install over a Beta version of OS/2 2.0 (1.3 is OK) controller/hard disk **************** Supported Drives **************** On (E)ISA bus machines, OS/2 specifically supports hard drive adapters which conform to the Western Digital chipset interface standard (i.e. nearly all MFM, RLL, IDE, and ESDI adapters) and Adaptec, Future Domain, and IBM SCSI adapters. In addition, "generic" INT13 support is provided for all other hard disk adapters. This "generic" support even embraces such devices as Iomega's Bernoulli and SyQuest's removeable media products. CD-ROM support is included as well. At present the OS/2 CD- ROM driver does not work with all brands, but the DOS device drivers, when suitably configured and installed, will still provide CD-ROM services to DOS/Windows programs. Printer and plotter support is discussed in Question 12. ---------------------------- Certain PC compatibles have difficulty accepting OS/2 2.0 (CSD level 02000 only; see Question 24), particularly AT bus systems with RLL, MFM, ESDI, or certain SCSI adapters (e.g. AMI SCSI adapters). The problem usually appears in the form of FDISK errors, extremely slow copying to the hard disk, or a whining/grating noise emanating from the hard disk. IBM suggests a simple workaround. First, DISKCOPY Diskette 1 of your OS/2 2.0 package. Set aside your original Diskette 1 and use the copy from now on as if it were the original. Using a text editor, modify the CONFIG.SYS file on Diskette 1 (the copy), replacing the line: 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. Follow instructions (insert Diskette 1 and press ENTER when prompted), then press ESC when prompted. At the OS/2 command line, type: RENAME C: OS2 IBM1S506.ADD IBM1S506.XXX COPY C: OS2 IBMINT13.I13 C: OS2 IBM1S506.ADD replacing C: with the appropriate drive if you are installing elsewhere. Remove Diskette 1, then press CTRL-ALT-DEL to reboot to finish installation. Miscellaneos installation tips ****************************** Be sure adequate free disk space is available before installing, including space for a swap file. Drives compressed using Stacker or similar utilities should be uncompressed before installing (unless access to these drives is not needed). OS/2 2.0 is not presently compatible with Stacker or similar utilities. However, an OS/2 2.0 version of Stacker is forthcoming. with other adapters. For example, many SuperVGA adapters use large chunks of upper memory, and many hard disk adapters have on board ROMs which can be mapped into this area as well. Adapters must cooperate in their use of memory and interrupts and must not share address space or interrupts. Check your product manuals for more help. Do not select HPFS when installing if your machine has 6 MB of RAM or less. Doing so will likely result in diminished performance. Change the IFS=...HPFS... line in your CONFIG.SYS to REM IFS=... if necessary. Automatic migration of your DOS CONFIG.SYS and AUTOEXEC.BAT files is not recommended. If you have Windows 3.1 installed on your system do not migrate your Windows desktop. Be sure your CMOS setup parameters are set correctly, especially those relating to floppy drives. All shadow RAM should be disabled for best performance. RAM should be given sufficient wait states and precharge cycles. The AT bus should run at 8 MHz. If you are using the IBMINT13.I13 driver to access an MFM, RLL, or ESDI hard drive, and the hard drive has more than 1024 cylinders, be certain your hard disk adapter's sector translation mode is enabled. Certain Quantum IDE hard disks require a free ROM update from the manufacturer to work with OS/2. When installing over a beta version of OS/2 (except OS/2 2.0 level 6.177H, the Limited Availability release) be sure to reformat. To install the OS/2 2.0 DOS/Windows upgrade DOS or OS/2 must already reside on the hard disk. If Diskette 1 is not write protected then the installation program will record a file indicating that upgrade terms have been satisfied and, in the future, will not require DOS or OS/2 on the hard disk to install. OS/2 uses the same diskette format as DOS, so use DISKCOPY to backup the installation diskettes and verify that none have been corrupted. **************************************** Miscellaneous Questions/Problems/Answers **************************************** Question: How do I access HPFS partitions on my hard drive without booting from the hard drive? I'm getting error messages now -- how do I "repair" my hard disk? With IBM OS/2 2.0, insert the Installation Diskette, Shutdown (if necessary), and reboot. When prompted insert Diskette 1 and press ENTER. When prompted, press ESC. You will be given an OS/2 command line prompt. From there you can make necessary changes to your hard disk -- an OS/2 character mode text editor is handy for such changes. (Make sure you backup CONFIG.SYS before making any changes so that you can easily revert to the old version should things go wrong.) FAT or HPFS partitions. After you reach the command line, insert Diskette 2. Do not log to another drive. Type CHKDSK X: /F to repair most kinds of damage to your hard disk, replacing X with the appropriate drive letter. OS/2 CHKDSK will also remark your hard disk as accessible, if possible, should OS/2 "lock it out" for some reason. The best way to avoid the need to perform CHKDSK is to always select Shutdown. Click on the Workplace Shell desktop background using mouse button two to bring up the appropriate menu. Also, avoid deleting OS/2- related files when using native DOS. Problem: My install hangs on Disk 1. Resolution: In many cases, PCM hardware has disk caching enabled on the drive controller card. The hang can often be fixed by disabling the on-board caching. Another suggestion is if the card has asynchronous memory refresh capabilities, turn it off. This too may fix the problem. Problem: Can't install OS/2 2.0 from Drive B. What's wrong? Resolution: IBM OS/2 2.0 can only be installed from Drive A, like DOS (unless your BIOS supports booting from Drive B), or across a network (contact IBM for more information on network installation procedures). If you have the wrong disk size go back to your dealer and obtain the correct media. Otherwise you could go inside your machine and swap floppy drive cable connectors, use your system's setup utility to set the new CMOS parameters, and then install OS/2 from the "new" Drive A. Sometimes the floppy drive cable connectors will not be the same. If so you can obtain an adapter plug. Question: How should I partition my hard disk for OS/2? Answer: OS/2 should ideally be in a partition by itself, unless you are considering a dual boot system which requires DOS to be loaded first. The partition should be approx 40-50 megabyts in size for OS/2 alone, assuming you wish a full default install and the swap drive on the same partition. The lower amount of memory you have, the larger swap file (and partition) you will need. You should have at least 2 partitions, one for OS/2 and the other for data. Question: Do I need to reformat to install OS/2 2.0? Answer: It's always a good idea. However, the only versions of OS/2 you MUST reformat over is over ANY OS/2 beta EXCEPT for L.A. (6.177H) If you formatted during an install and the install aborted, reformat. If you did a "dirty" (unformatted) install and it died, try again without formatting. If that too fails, you may want to back up any needed data files from the target drive and reformat. There should be no other reason to install 2.0 G.A. over itself. If you want to add features, use the OS/2 System object, System Setup and Selective Install. You can add virtually any feature this way. 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. COUNTRY.SYS not found 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. 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. See APAR II06081 for more info on SCSI compatibility. /* ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ */ FDISK INSTALLATION PROBLEMS ************************************************* *** GENERAL INFO ON DRIVE PROBLEMS *** ************************************************* These problems can be caused by - incorrect setup information in CMOS memory for hard drive being used - disk corruption/failure - incorrect identification of adapter by OS/2 - trying to install on a drive which was compressed using a stacker utility - trying to install over a Beta version of OS/2 2.0 (1.3 is OK) controller/hard disk **************** Supported Drives **************** On (E)ISA bus machines, OS/2 specifically supports hard drive adapters which conform to the Western Digital chipset interface standard (i.e. nearly all MFM, RLL, IDE, and ESDI adapters) and Adaptec, Future Domain, and IBM SCSI adapters. In addition, "generic" INT13 support is provided for all other hard disk adapters. This "generic" support even embraces such devices as Iomega's Bernoulli and SyQuest's removeable media products. CD-ROM support is included as well. At present the OS/2 CD- ROM driver does not work with all brands, but the DOS device drivers, when suitably configured and installed, will still provide CD-ROM services to DOS/Windows programs. Printer and plotter support is discussed in Question 12. ---------------------------- Certain PC compatibles have difficulty accepting OS/2 2.0 (CSD level 02000 only; see Question 24), particularly AT bus systems with RLL, MFM, ESDI, or certain SCSI adapters (e.g. AMI SCSI adapters). The problem usually appears in the form of FDISK errors, extremely slow copying to the hard disk, or a whining/grating noise emanating from the hard disk. IBM suggests a simple workaround. First, DISKCOPY Diskette 1 of your OS/2 2.0 package. Set aside your original Diskette 1 and use the copy from now on as if it were the original. Using a text editor, modify the CONFIG.SYS file on Diskette 1 (the copy), replacing the line: 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. Follow instructions (insert Diskette 1 and press ENTER when prompted), then press ESC when prompted. At the OS/2 command line, type: RENAME C: OS2 IBM1S506.ADD IBM1S506.XXX COPY C: OS2 IBMINT13.I13 C: OS2 IBM1S506.ADD replacing C: with the appropriate drive if you are installing elsewhere. Remove Diskette 1, then press CTRL-ALT-DEL to reboot to finish installation. Miscellaneos installation tips ****************************** Be sure adequate free disk space is available before installing, including space for a swap file. Drives compressed using Stacker or similar utilities should be uncompressed before installing (unless access to these drives is not needed). OS/2 2.0 is not presently compatible with Stacker or similar utilities. However, an OS/2 2.0 version of Stacker is forthcoming. with other adapters. For example, many SuperVGA adapters use large chunks of upper memory, and many hard disk adapters have on board ROMs which can be mapped into this area as well. Adapters must cooperate in their use of memory and interrupts and must not share address space or interrupts. Check your product manuals for more help. Do not select HPFS when installing if your machine has 6 MB of RAM or less. Doing so will likely result in diminished performance. Change the IFS=...HPFS... line in your CONFIG.SYS to REM IFS=... if necessary. Automatic migration of your DOS CONFIG.SYS and AUTOEXEC.BAT files is not recommended. If you have Windows 3.1 installed on your system do not migrate your Windows desktop. Be sure your CMOS setup parameters are set correctly, especially those relating to floppy drives. All shadow RAM should be disabled for best performance. RAM should be given sufficient wait states and precharge cycles. The AT bus should run at 8 MHz. If you are using the IBMINT13.I13 driver to access an MFM, RLL, or ESDI hard drive, and the hard drive has more than 1024 cylinders, be certain your hard disk adapter's sector translation mode is enabled. Certain Quantum IDE hard disks require a free ROM update from the manufacturer to work with OS/2. When installing over a beta version of OS/2 (except OS/2 2.0 level 6.177H, the Limited Availability release) be sure to reformat. To install the OS/2 2.0 DOS/Windows upgrade DOS or OS/2 must already reside on the hard disk. If Diskette 1 is not write protected then the installation program will record a file indicating that upgrade terms have been satisfied and, in the future, will not require DOS or OS/2 on the hard disk to install. OS/2 uses the same diskette format as DOS, so use DISKCOPY to backup the installation diskettes and verify that none have been corrupted. **************************************** Miscellaneous Questions/Problems/Answers **************************************** Question: How do I access HPFS partitions on my hard drive without booting from the hard drive? I'm getting error messages now -- how do I "repair" my hard disk? With IBM OS/2 2.0, insert the Installation Diskette, Shutdown (if necessary), and reboot. When prompted insert Diskette 1 and press ENTER. When prompted, press ESC. You will be given an OS/2 command line prompt. From there you can make necessary changes to your hard disk -- an OS/2 character mode text editor is handy for such changes. (Make sure you backup CONFIG.SYS before making any changes so that you can easily revert to the old version should things go wrong.) FAT or HPFS partitions. After you reach the command line, insert Diskette 2. Do not log to another drive. Type CHKDSK X: /F to repair most kinds of damage to your hard disk, replacing X with the appropriate drive letter. OS/2 CHKDSK will also remark your hard disk as accessible, if possible, should OS/2 "lock it out" for some reason. The best way to avoid the need to perform CHKDSK is to always select Shutdown. Click on the Workplace Shell desktop background using mouse button two to bring up the appropriate menu. Also, avoid deleting OS/2- related files when using native DOS. Problem: My install hangs on Disk 1. Resolution: In many cases, PCM hardware has disk caching enabled on the drive controller card. The hang can often be fixed by disabling the on-board caching. Another suggestion is if the card has asynchronous memory refresh capabilities, turn it off. This too may fix the problem. Problem: Can't install OS/2 2.0 from Drive B. What's wrong? Resolution: IBM OS/2 2.0 can only be installed from Drive A, like DOS (unless your BIOS supports booting from Drive B), or across a network (contact IBM for more information on network installation procedures). If you have the wrong disk size go back to your dealer and obtain the correct media. Otherwise you could go inside your machine and swap floppy drive cable connectors, use your system's setup utility to set the new CMOS parameters, and then install OS/2 from the "new" Drive A. Sometimes the floppy drive cable connectors will not be the same. If so you can obtain an adapter plug. Question: How should I partition my hard disk for OS/2? Answer: OS/2 should ideally be in a partition by itself, unless you are considering a dual boot system which requires DOS to be loaded first. The partition should be approx 40-50 megabyts in size for OS/2 alone, assuming you wish a full default install and the swap drive on the same partition. The lower amount of memory you have, the larger swap file (and partition) you will need. You should have at least 2 partitions, one for OS/2 and the other for data. Question: Do I need to reformat to install OS/2 2.0? Answer: It's always a good idea. However, the only versions of OS/2 you MUST reformat over is over ANY OS/2 beta EXCEPT for L.A. (6.177H) If you formatted during an install and the install aborted, reformat. If you did a "dirty" (unformatted) install and it died, try again without formatting. If that too fails, you may want to back up any needed data files from the target drive and reformat. There should be no other reason to install 2.0 G.A. over itself. If you want to add features, use the OS/2 System object, System Setup and Selective Install. You can add virtually any feature this way. 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. COUNTRY.SYS not found 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. 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. See APAR II06081 for more info on SCSI compatibility. /* ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ */ INFO APAR - MOUSE , INSTALLATION AND CONFIGURATION INFORMATION OS/2 2.0 Pointing Device Installation Document Version 1.1 ... ... INSTALL YOUR POINTING DEVICE ---------------------------- ... During installation the mouse device driver will attempt to detect your pointing device. If it does you will NOT receive a mouse selection panel during diskette 2. It is highly recommended that you do NOT go into the PM mouse panel to change things if you are not prompted to do so. We are finding out that many customers are messing things up by forcing a different device type then what was detected. A prime example of this is the Logitech series M mouse. This mouse is compatible with the MS serial mouse and will be detected. The mouse panel will read MS Serial Mouse. A lot of customers are then going into the PM panel and choosing Logitech Serial. This choice will add the PCLOGIC.SYS driver which does NOT work for the Logitech series M mouse. ... The bottom line is if you are not prompted for any mouse information leave well enough alone. ... ... ... Mouse PM install panel ---------------------- ... Logitech PS/2 Mouse - PS/2 (tm) Style Pointing Device ... Logitech Serial Mouse (Series M) - PS/2 (tm) Style Pointing Device ... Logitech Serial Mouse (Series C) - Logitech (TM) Serial Mouse ... Logitech Trackman serial mouse - Logitech (TM) Serial Mouse ... ... ... CONFIG.SYS STATEMENTS --------------------- ... For most of the common pointing devices that are out today the OS/2 2.0 CONFIG.SYS line for mouse support is simply. ... DEVICE=C: OS2 MOUSE.SYS ... There are some older Logitech Devices (i.e. Trackman) that are not detectable by MOUSE.SYS. These devices are still supported. ... The CONFIG.SYS lines for undetectable Logitech devices and PC Mouse System Mice are; ... DEVICE=C: OS2 PCLOGIC.SYS SERIAL=COM1 DEVICE=C: OS2 MOUSE.SYS TYPE=PCLOGIC$ ... ... If the device is plugged into COM2 then change the SERIAL= parameter to COM2. ... Note: On an AT bus system a serial mouse will only install on COM1 or COM2, and only if COM1 and COM2 are at the standard I/O addresses and IRQs, 3F8,IRQ4 for COM1 and 2F8,IRQ3 form COM2. ... The following pointing devices have been tested and verified to work. I have also included the CONFIG.SYS statements for each entry. ... ... DEVICE CONFIG.SYS Statements ------ --------------------- IBM PS/2 Mouse DEVICE=C: OS2 MOUSE.SYS ... MS PS/2 Mouse DEVICE=C: OS2 MOUSE.SYS ... MS Serial Mouse DEVICE=C: OS2 MOUSE.SYS ... Kensington Expert PS/2 Mouse DEVICE=C: OS2 MOUSE.SYS (NOTE: This is not the same as the Kensington serial mouse!!!) ... Logitech PS/2 Mouse DEVICE=C: OS2 MOUSE.SYS ... MS Bus Mouse DEVICE=C: OS2 MOUSE.SYS (NOTE: This mouse requires a special card that only works on an AT style bus.) ... MS Inport Mouse DEVICE=C: OS2 MOUSE.SYS (NOTE: This mouse requires a special card that only works on an AT style bus.) ... Logitech Serial Mouse DEVICE=C: OS2 MOUSE.SYS (Series M) ... Logitech Serial Mouse DEVICE=C: OS2 PCLOGIC.SYS SERIAL=COM2 (Series C) DEVICE=C: OS2 MOUSE.SYS TYPE=PCLOGIC$ ... Logitech Trackman DEVICE=C: OS2 PCLOGIC.SYS SERIAL=COM2 serial mouse DEVICE=C: OS2 MOUSE.SYS TYPE=PCLOGIC$ ... PC Mouse Systems DEVICE=C: OS2 PCLOGIC.SYS SERIAL=COM2 serial mouse DEVICE=C: OS2 MOUSE.SYS TYPE=PCLOGIC$ ... Visi-On serial mouse DEVICE=C: OS2 PCLOGIC.SYS SERIAL=COM2 DEVICE=C: OS2 MOUSE.SYS TYPE=PCLOGIC$ . .. NOTE: The mouse driver is smart enough to figure out if the mouse is in a mouse port or one of the COM ports. Be sure that the MOUSE.SYS statement appears before DEVICE=C: OS2 COM.SYS in your CONFIG.SYS file if the mouse is on a COM port. ... ... ... There are hundreds of pointing devices available today. Most of these are Microsoft compatable. If they are 100% MS compatable we support them with the following CONFIG.SYS statement DEVICE=C: OS2 MOUSE.SYS. ... We have found that some devices are not 100% compatible and therefore are not supported. ... The mouse device driver is layered allowing an OEM to easily add support for there pointing device. By writing a small mouse device dependent driver they can get there device to work with OS/2 2.0. Please contact the OEM manufacturer to find out if they provide a device driver for OS/2 2.0. ... An example of an OEM manufacturer that provides OS/2 support is HP. HP provides HILMOU.SYS and NOEXBIOS.SYS device drivers. Below is the instructions for adding support for your HIL mouse. ... HP Mouse ... - Directions for installing an HP mouse 1- Select any mouse during system installation 2- Copy HILMOU.SYS and NOEXBIOS.SYS to C: OS2 (these are supplied by 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 LINE SHOULD ALREADY BE IN CONFIG.SYS BUT WILL NEED TYPE=... ADDED ) ... ... Customer may also go to his dealer for the diskette which ships with the mouse. Customer may also see COMPUSERV GO HP /* ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ */ DOSAP INFOAPAR 2, DOSCOPY() SUBROUTINE ON OS/2 2.0 . I believe that the DosCopy() subroutine has a defect that prevents reliable date and time stamp setting of the target file when copying from a remote DOS LAN server to a local OS/2 2.0 filesystem. I was recently informed of a situation in which a file copy utility that I wrote (ccp - conditional copy) was incorrectly setting the date and time of target files. The ccp program uses the DosCopy() subroutine to perform any actual file copy operations. . For example, the bldtt.asm file had a source date and time of 6/28/91 and 12:55p. After the copy, its target date and time was 6/22/96 and 5:07p. In fact, about 400 files out of a total of 2000 files had incorrect date and time stamps after the copy. (The incorrect target date and time stamps are neither those of the source file nor those of the current time and date.) The results appear repeatable: the same files get the same bad timestamps each time. . The environment is as follows: 1) The ccp (conditonal copy) program, a 16-bit OS/2 application, is running on an OS/2 2.0 system. It uses the DosCopy() subroutine to perform the copy operation on each file that needs to be copied. 2) The source files exist on a DOS machine running LAN Server. The local OS/2 2.0 machine accesses the DOS machine's files via a remote drive that is set up by the NET USE command. 3) About 2000 files were copied. Of these, about 400 files had date and time stamps on the OS/2 2.0 system that did not match the date and time stamp of the source file on the DOS system. (No data was lost or corrupted, though). 4) The results are repeatable: Files that copy ok always copy ok. Files that get an incorrect target date and time always get the same incorrect date and time. The standard COPY command & DOS-only version of ccp did not fail 1) The built-in OS/2 COPY command correctly set the date and time stamps of the target files. 2) The DOS-only version of ccp also set the date and time stamps of the target files correctly. . Notes about the ccp program: (a) The OS/2-only version was developed on OS/2 1.3 using C2 1.1 and the OS/2 1.3 toolkit. Once it determines the exact source and target names of a file to copy,it calls the DosOpen subroutine to perform the actual copy. (b) The DOS-only version was developed using the C/2 1.1 on a DOS machine. It uses the open, close, read, and write subroutines to copy the file's data (it ignores EAs). It also uses the _dos_setftime and _dos_setfileattr subroutines to set a target file's date, time, and attributes to those of the source file. . DOSAP Volkswriter gives trap 000D. Need to upgrade to version 4 release 1.02. Call the vendor of the DOSAP for fix. . DOSAP WordPerfect 5.1 hangs. Set KBD_BUFFER_EXTEND to OFF in DOS SETTINGS. Set FILES = 40 in CONFIG.SYS. . Applications that use parallel ports for printing (ex: WordPerfect and Word Search) will give SYS1799 errors if apps are trying to access parallel ports simultaneously. You will need to terminate one of them since the parallel port can only be used by one DOSAP at a time. . SYS3176 errors (may be video board related). If setting HW_ROM_TO_RAM to ON and DOS_RMSIZE to 624 does not work, try setting DOS_HIGH and DOS_UMB to OFF both in CONFIG.SYS and DOS settings. . Castle Wolfenstein 3D by APOGEE... create a program object, specifiy paths, etc, then for sessions choose dos full screen, then for dos settings change VIDEO_RETRACE_EMULATION to OFF, IDLE_SENSITIVTY=100, and IDLE_SECONDS=60. A lot of APOGEE games may need these settings, not sure. . SYS2237 NPX errors reported with numerous DOSAPs APAR PJ04878 created for this. With MS CODEVIEW, a workaround exists: put SET NO87=YES in autoexec.bat for that dos session or os2 directory's autoexec.bat. . DOSAP ZSTEM 240 -> GETS PORT INITIALIZATION ERROR: Contact Mark at K.E.A. Systems at 604-431-0727 for an upgrade to their program for ethernet card connections. . OS/2 2.0 includes a TSR called FFIX.EXE that allows DOS function 5701 to work properly. The problem resides in the fact that OS/2 will not allow the change of date and time to any file that is o for read operations; the file must be opened for write operation This programs works for VDM sessions. . SYS3176 in VMB may be alleviated by removing IFS statement from the CONFIG.SYS file. . The Intel SatisFAXtion modem requires a DOS device driver called SATISFAX.SYS to be loaded before use with a DOS terminal program. You will also need the IOADDR parameter to be specified (get this from the SETUP program). Another driver will have to be loaded in order to use DOS Fax programs. See the "How to Use the Intel SatisFAXtion Board" manual for more information. Intel Customer Support # is 503-629-7000. This board is not supported by Intel or IBM in a networked environment. We do not support COM3 or COM4 under WinOS2, this is a MS Windows limitation. Intel does not currently have an OS2-specific driver for their modem. See the TNT for software install instructions... however, if the install fails please use real DOS 5.0 to install the program. . Q>THE CUSTOMER HAS INSTALLED 311 NETWORK. HE SAID THE NOVELL MANUAL ADDRESSES THE COMMAND SETTING NETWARE_RESOURCES AND LAST_DRIVE THAT SHOULD BE AVAILABLE IN THE DOS SETTING MENU. A>If the customer loads VSHELL.SYS in the os/2 config.sys, he will see two netware requester dos_settings --> NETWARE_RESOURCES and VIPX_ENABLED. If the VSHELL.SYS is not loaded, these choices will not appear in the MVDM DOS_ Settings. By the way, neither of these dos_settings will have a description attached to them -- that's one item they seem to have forgotten to add. . Colorado Tape Backup Units - Call Colorado for OS/2 2.0 compatible drivers. OS/2 version of backup program coming soon (Nov '92?). . Mountain Tape Backup Units - Call Mountain for OS/2 2.0 compatible backup package, available now. . LOCAL FIX: /* ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ */ INFORMATION REGARDING INTERRUPTS AND 2.0 OS/2 IN AT BUS SYSTEMS Information regarding interrupts and OS/2 2.0 in AT BUS systems --------------------------------------------------------------- ... Under OS/2 interrupts can not be shared. Results are unpredictable if interrupts are shared. Sharing interrupts is not a problem under DOS. It is possible for devices that are sharing interrupts to work perfectly under DOS and have problems under OS/2. ... On an ISA machine there are a total of 15 IRQ levels available. The standard settings, in order of priority, is as follows: ... ... IRQ# Device Associated ---- ----------------- 0 System Timer 1 Keyboard 2 Secondary Interrupt Controller (see note) 8 Realtime Clock 9 --- (see note) 10 --- free 11 --- free 12 --- free - reserved for aux dev 13 Math Coprocessor 14 Hard Disk 15 --- free 3 COM2 (Serial Communications Port #2) 4 COM1 (Serial Communications Port #1) 5 LPT2 (Parallel Printer Port #2 - add. 278) 6 Diskette 7 LPT1 (Parallel Printer Port #1 - add. 3BC and 378) ... ... (Note: On the IBM-AT (ISA bus) the IRQ9 pin is identical with the IRQ22 pin on the original IBM-PC. If you have an older, 8-bit adapter whose documentation states that it uses IRQ2 then be aware that this will actually be seen as IRQ9 when plugged into the 16-bit ISA bus.) ... ... If multiple hardware adapters of any kind (not just communications) are using the same IRQ level then the effect on your computer will be unpredictable. However, with single tasking systems like DOS, the two adapters which are sharing the interrupt may never cause any problems since they may never be in use at the same time. ... OS/2, however, presents a different set of problems. If we have two, three or four adapters, the probability is now high that they are used at the same time. If some of adapters had been set up using shared interrupts then the scene is set for mysterious things to occur in OS/2. ... OS/2 can, however, detect that an interrupt line is shared and will disallow the simultaneous use. Assume that COM1 and COM3 were sharing IRQ4 (a fairly common real situation). If we tried to use both COM ports at the same time OS/2 would refuse to allow the second one to start. A well written OS/2 communications program would see and report the error from OS/2 that the port could not be opened. A DOS application, however, will likely be unprepared to respond to this strange situation and it may simply hang there waiting forever for the port that will never open. ... The solution for all of this is to make sure that all of your hardware adapters have their own unique I/O addresses and IRQ assignments. Unfortunately, on an ISA machine, OS/2 has no way to query the computer to find out what these settings are. Therefore, after checking and setting the adapters according to the instruction manuals you must also tell OS/2 what you've done by placing explicit information into the CONFIG.SYS file. ... ... To summarize: ------------- ... *) Even though there is some flexibility for Printer & Comm. port assignment try to stick to the standard assignment as shown in IRQ table at the beginning of document. ... *) Available interrupts, in order of priority, are: IRQ10, IRQ11, IRQ12, IRQ15, IRQ3 (if not used for COM2), and IRQ5 (if not used for LPT2). ... *) Addresses and interrupts can be assigned in OS2 to comm ports as described in info apar II06069. Standard assigment is as follows: COM1 - 3F8 - IRQ 4 (default) COM2 - 2F8 - IRQ 3 (default) COM3 - 3E8 COM4 - 2E8 There is no OS/2 default setting for COM3 and COM4. It must be specified by the device=com.sys statement in config.sys. ... *) Printer port addresses and IRQ levels are hardcoded in OS/2 as follows: 3BC and 378 ==> IRQ7 (LPT1) 278 ==> IRQ5 (LPT2) Unlike the the comm ports, where the addresses and the interrupts can be modified by the device=com.sys in config.sys, the printer port addresses and IRQ shown above are fixed. OS2 assigns LPT1 to the highest printer port address being used. The printer address is specified in the printer adapter board. With OS/2 you can not use both addresses 3BC and 378 as printer port addresses. Both LPTs would be sharing IRQ7. Unlike DOS, OS/2 uses interrupts for printing. The interrupt is triggered by a signal line from the printer, ACK. If the IRQs are not configured correctly, or the printer cable is missing the ACK line the printer may work under DOS and have problems under OS/2. ... An example of address and interrupt assignment is follows: COM1 - 3F8,IRQ4 COM2 - 2F8,IRQ3 COM3 - 3E8,IRQ5 (IRQ5 not being used by lpt2) COM4 - 2E8,IRQ10 ... LPT1 - 378,IRQ7 ... *) If interrupt devices are occasionally losing data, try moving to a higher priority unused interrupt. /* ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ */ INSTALL INFORMATION APAR ON SCSI ************ SCSI SUPPORT ************ SCSI Hard drive driver support: SCSI Adapter Driver Adaptec AIC 6260 AHA152X.ADD Adaptec AHA 1510 AHA152X.ADD Adaptec AHA 1520/1522 AHA152X.ADD Adaptec AHA 1540/1542 AHA154X.ADD Adaptec AHA 1640/ AHA164X.ADD Adaptec AHA 1740/1742/1744 (Standard mode operation) AHA154X.ADD (Enhanced mode operation) AHA174X.ADD Future Domain TMC 850/860/875/885 FD8XX.ADD Future Domain TMC 1660/1670/1680 FD16-700.ADD Future Domain TMC 600/700 FD16-700.ADD Future Domain TMC 850IBM FD850IBM.ADD 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. 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. 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. Problems with Always IN2000 SCSI adapter Internal Processing Error. Symptoms of the problem are varied, but the most common is an FDISK error on the second diskette. Problem: 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. Always suggests installing the EPROMS and re-formatting the drive - seem to be some problems installing over DOS partitions. Always can be reached at 818-597-9595. 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. PROCOMM+ SCSI MCA adapters do not work Resolution: Contact PROCOMM for details on OS/2 support. 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. IBM 16-bit SCSI cards(early versions) 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. 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. Other SCSI hints ---------------- Some SCSI card have jumper pins which can be set to either Synchronous or Asynchronous mode. There have been noted problems such as no icons appearing or slow hard disk performance. This can be attributed to the SCSI card and hard disk not being set to the same asynch or synch settings. Either way, they must match. Be sure these are set properly. The early versions of the IBM 16-bit SCSI adapters may experience problems and report erroneously that the device is not functioning. This can be corrected by replacing the SCSI card with a card with updated microcode. /* ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ */ INFORMATION ON INSTALL PROBLEMS RELATED TO BIOS INFO APAR OS/2 INSTL - Information on Install BIOS Problems LOCAL FIX: Due to the wide variety and many sources for PC compatible equipment, many different combinations of hardware components and BIOS revisions exist. OS/2 is an advanced operating system that may require more up to date BIOS than DOS and Windows. Many install problems and other problems may be resolved by updating BIOS. You will need to determine your BIOS manufacturer, version, and date, and this should be checked with the manufacturer for compatibility with OS/2. If you need help determining your BIOS information, see "TIPS ON GETTING BIOS INFO" below. SOME BIOS COMPATIBILITY INFO ============================ The following table lists dates and revision levels required for OS/2 to work with listed components: Component Date ("mmddyy") Revision Level AMI BIOS -------- IDE hard drives 040990 SCSI 092588 or later (need OS/2 compatible and may need special installation procedure) Other drives 092588 or later MFM, RLL, ESDI, etc. Keyboard controller F only * * Revision level 0 or revision level 9 with non standard ID code format indicates motherboard OEM manufacturer - nonstandard BIOS. This may or may not work with OS/2, and it may have "custom" functionality for the specific motherboard which may preclude upgrading. The motherboard manufacturer should be contacted for further information. Phoenix Bios 051192 1.03 Always IN2000 SCSI VCN:1-02 for host adapter: 2.5-2.7 Quantam Plus Hardcard 2.6 PROCOMM+ SCSI MCA does not work - Contact PROCOMM for details on OS/2 support TIPS ON GETTING BIOS INFO ========================= AMI BIOS's of modern vintage provide a Screen ID Code, visible at the lower left of the screen during the initial RAM count, and which can be made to return by resetting with Ctrl-Alt-Del. The format of this ID code is: AMI BIOS and AMI BIOS Plus: aaaa-bbbb-mmddyy-Kc AMI Hi-Flex BIOS: ee-ffff-bbbbbb-gggggggg-mmddyy-hhhhhhhh-c If the screen ID code is in a form other than this, the BIOS is either very old or was produced by a company with a source code license. In the former case, contact us for update information. But in the latter case, only the motherboard manufacturer will be able to provide further information or updates. Everex 386 BIOS's are in this latter category. BIOS UPDATES ============ If a BIOS prior to the dates noted above requires replacement, note the following: 1. AMI BIOS and BIOS Plus series BIOS (16 character ID code) for CACHED motherboards are customized for individual mother- board designs, and can ONLY be obtained from the motherboard OEM, with only THREE common exceptions: a) BIOS's with "aaaa" = E307 can often be replaced with a standard type. b) BIOS's for Northgate or Motherboard Factory motherboards EXCEPT the Northgate Slimline can, be replaced by a standard type. c) BIOS's with "aaaa" = DAMI, DAMX, or EDAMI are usually for cached boards designed and/or built by AMI, and if so, can be updated. 2. The complete Screen ID Code is required to properly address whether a BIOS update for other motherboards can be provided, and in the case of the Hi-Flex BIOS, the complete SECOND and THIRD lines of the ID Code are also necessary. If not visable immediately on the screen, they may be viewed by pressing the <INS> key during boot-up. 3. For these AMI BIOS updates, Call Washburn & Co. to order new versions. OTHER COMPATIBILITY ISSUES ========================== 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 config- ured 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 occur- red" when you attempt to start the Installation diskette. Contact Future Domain for a free BIOS upgrade. Adapter: 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 comp- lete, 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. Adapter: 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 Adapter: PROCOMM+ SCSI MCA adapters do not work Resolution: Contact PROCOMM for details on OS/2 support. Adapter: 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 Other problems: Symptom: Slow hard drive speed 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. Some contact phone numbers: Always Technology 818-597-9595. Washburn & Co. 716-248-3627 (AMI Bios Upgrade) 800-836-8026 (AMI Bios Upgrade) Phoenix 1-405-321-8333 /* ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ */ INFORMATION ON INSTALL PROBLEMS RELATED TO VIDEO ADAPTERS OS/2 INFO APAR INSTL - info on video related install problems Installation of OS/2 should always be done with VGA, even if you have an SVGA card. IBM OS/2 support is limited to VGA and XGA, with the exception of Trident, Tseng, ATI, Headland, and Western Digital chipsets, for which OS/2 has designed "generic" support. listed in the readme file. The only SVGA support that is provided in the shrink wrapped version of OS/2 is the ability to switch away from a DOS or OS/2 fullscreen and have the current state of your video card saved.. and this is only after you have turned SVGA ON, and if you have one of the adapters listed in the readme..although everyone with a Tseng, Trident, ATI, Headland, or Western Digital chipset should try turning SVGA ON at least for a while to see if it fixes any unseemly video problems they might be having. IBM Tested Video Cards: o Orchid ProDesigner IIs by Orchid Technology (ISA and MCA versions) o Trident TVGA by Trident Microsystems, Inc. (8900b and c levels) o STB PowerGraph VGA by STB Systems, Inc. o Video Seven VRAM II, by Video Seven o Boca Super VGA by Boca Research Inc. o VGA Wonder XL Series by ATI Technologies, Inc. Video boards and the chipsets they use:(not official list) ============================================================ Chipset name Board name -------------------- --------------------------------- Chips & Technologies Cardinal, C&T MK82452 VGA chip Everex VGA chip Everex EV-673 Genoa GVGA chip Genoa 6400 Western Digital 9010 Paradise VGA Pro, VGA 1024, "PVGA" (512K) Western Digital 9030 MVGA 1024DX (1meg) 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 Trident 8900, Hi Res 512 (Zymos Poach 51) 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 Swan Palette Plus, 2TheMax VGA 4000, RAMDAC Diamond SpeedStar + HIcolor Video 7 VGA chip Video 7 VRAM, Video 7 Fastwrite, Video 7 VEGA Deluxe, Northgate Pro If you have an ATI Ultra, Vantage, or other 8514/A hardware compatible adapter, install OS/2 using the 8514/A driver. For the Graphics Ultra and Graphics Vantage change the line DEVICE=...VVGA.SYS to DEVICE=...VSVGA.SYS in CONFIG.SYS; Shutdown, reboot, and proceed with SVGA ON as described above. Problem: C0000005 is displayed on the screen during install Resolution: The problem occurs on Western Digital PVGA1D video cards, but may not be limited to them. It is resolved in a fixed version of BVHSVGA.DLL available from IBM. 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. Problem: My install hangs on Disk 1. Resolution: In many cases, PCM hardware has disk caching enabled on the drive controller card. The hang can often be fixed by disabling the on-board caching. Another suggestion is if the card has asynchronous memory refresh capabilities, turn it off. This too may fix the problem. Problem: Hang on Disk1 right after LOGO screen Resolution: Ask the customer if he has an OAK video card. An INT10 call is made to the BIOS which causes the problem on OAK cards. You will need to patch the OS2LDR file and make the following changes. Step 1. Make a backup copy of your Install Diskette 1. Use DOS DISKCOPY if necessary. *DO NOT* perform this modification on your original OS/2 2.0 Install Diskette 1. Step 2. Boot DOS, make sure you have DEBUG.COM on that diskette or on your hard drive where you can get to it. Change to the appropriate directory if necessary. Step 3. Insert your backup copy of Install Diskette 1. Type DEBUG A: OS2LDR<enter> at the DOS command prompt. Step 4. To unassemble OS2LDR, enter the following command: U 4F7C<enter> Step 5. Enter the following: 4F7C<enter> CD. will be displayed. You will enter 90<space> and 10. will be displayed. You will enter 90<enter> Step 6. To write changes to the file,enter the following command: W<enter> Step 7. To quit debug, enter the following command: Q<enter> Step 8. You should now see your DOS prompt. Restart the installation using your newly modified backup Install Diskette. Problem: Successful install, but the system hangs on the next reboot at the LOGO screen Resolution: Ask the customer if he has a FUTURE DOMAIN 16XX SCSI controller. The .ADD file uses interrupt driven I/O rather than polling which is used by DOS. An interrupt conflict likely exists. You should check all IRQ settings on all cards to find the conflict. 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. Problem: White screen after installation with no system activity Resolution: Try setting the video card to 8 bits and moving the video card to an 8-bit slot and disable the auto-switching capability of the card if possible. "Autoswitching" on non-IBM EGA adapters should be disabled (usually with a DIP switch or jumper setting). In rare cases it may be necessary to switch third party VGA/SuperVGA adapters into 8-bit mode. Limitation: The WPS will not operate with the Monochrome Display Adapter or the Hercules Monochrome Graphics Adapter. Usually the WPS will fail to work with monochrome EGA. However, some EGA adapters (e.g. Paradise Monochrome EGA Card, ATI EGA Wonder) will emulate all color EGA modes on TTL monochrome monitors and, thus, will work with the WPS. Limitation: Make sure adapters with on board ROMs are not conflicting with other adapters. For example, many SuperVGA adapters use large chunks of upper memory, and many hard disk adapters have on board ROMs which can be mapped into this area as well. 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. 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. 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 <enter> e. DEBUG A:OS2LDR <enter> f. U 4F7C <enter> g. E 4F7C <enter> h. CD.90 <enter> i. <SPACE> j. 10.90 <enter> k. W <enter> l. Q <enter> 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. Phoenix BIOS ============ Latest info from manufacturer (on 1-405-321 8333) is that new version 1.03 is out with bug fixes. The version should be dated 5/11/92 or higher. /* ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ */ MISCELLANEOUS INFO ON INSTALLATION NOT COVERED IN OTHER APARS SYS1200 error when attempting to Dual Boot to DOS with an error code indicating that the DOS environment cannot be created and you see an error code - EC=00BF. RESOLUTION: Ensure that you have not removed or remarked out any of the VIRTUAL DOS device drivers. If all else fails, rename your current CONFIG.SYS to CONFIG.XXX and copy your original CONFIG. SYS to the root directory. The original CONFIG.SYS can be found in the OS2 INSTALL directory. PROBLEM: Installation on ZEOS notebook fails RESOLUTION: Follow the following steps: The fix for this problem assumes that you have access to a working copy of OS/2 2.0. Ask your local IBM dealer if they can provide an OS/2 2.0 machine for you to use for a few minutes, or ask a friend/co-worker with 2.0 installed. Bring your Instal- lation diskette with you, along with a blank formatted high density 3.5 inch diskette. Step 1. Open the OS/2 System object on the OS/2 Desktop by double clicking with mouse button 1 (usually the left mouse button) Step 2. Open the Command Prompts folder (by double clicking on the folder object). Step 3. Double click on the OS/2 Window Object. Step 4. You should now be at an OS/2 Command Prompt. Step 5. Backup your Installation Diskette to the blank 3.5 inch high density diskette you brought with you. Enter the following command at the pronpt: DISKCOPY A: A:<enter> and follow the prompts. Step 6. With your backup diskette in the drive, enter the fol- lowing: PATCH SYSINSTX.COM<enter> Step 7. When asked for the offset address, enter: 96AF<enter> Step 8. On the line that is shown, enter 45 to replace 44 as the first byte in the line and then press <enter>. Step 9. When asked if you wish to apply patches, answer: Y <enter>. Step 10. At the OS/2 Command prompt again, enter: SYSINSTX A: Step 11. Install OS/2 on your ZEOS using the patched backup Installation Diskette. Step 12. The patch MUST be applied using OS/2. If it is not available, a diskette with the patch applied can be sent to you from IBM. LOCAL FIX: Blair Leavell PROBLEM: Fails to reboot after pressing enter. Install requests the user to press enter to reboot at the end of the full screen portion of install, or at the end in the case of a remote install. In some cases this will cause the system to hang. This is a problem in the file system shutdown. WORKAROUND: If the machine does not reboot, try Ctl-Alt-Del, and if this fails power off/on the machine. This should not cause the user any problems, but running a checkdisk after the install completes 'just in case' wouldn't be a bad idea. -Rick DeBay hang disk 6 disk 5 disk6 disk5 PROBLEM: Install hangs with no error during unpack. During install, unpack has been known to go into a tight loop. This has been recreated in Boca on OEM machines, and defect p024371 has been created. LOCAL FIX: This problem is intermittent, so a reinstall should not have the same problem. See Tips and Techniques for short cuts on continuing an installation. /* ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ */ INFORMATION APAR FOR OS/2 2.0 WORKPLACE SHELL. The following problems have workarounds detailed in this Info APAR for the Workplace Shell: NOTE: to find more details on a problem of interest to you in this file, enter: F keyword, where keyword is the first word for a problem listed in this index (the keyword for the blank desktop problem is "BlankDesktop", for example). Index to Workplace shell problems detailed in this Info APAR ============================================================ BlankDesktop - Some customers have experienced a blank desktop containing only a mobile mouse pointer. If this cannot be resolved permanently with Alt-F1 the workaround in this Info APAR may apply DrivesIcon - Some customers are experiencing problems with DRIVES icons opening and then closing immediately. LostIcon - Customer has lost an icon for a workplace shell folder, such as the OS2 System Folder icon has defaulted to yellow folder. SaveIcons - Customers are having problems associating an icon with an object . =========================================================== BlankDesktop ============= If a customer experiences a blank desktop containing only a mobile mouse pointer he/she may have INI file or CONFIG.SYS corruption. One possible cause for this blank desktop problem that we've found are extra SET USER_INI and SET SYSTEM_INI statements in the CONFIG.SYS. The following statements are as they should appear: SET USER_INI=C: OS2 OS2.INI SET SYSTEM_INI=C: OS2 OS2SYS.INI If the customer has any additional SET USER_INI or SET SYSTEM_INI statements in their CONFIG.SYS, they should be removed. Also, a MAKEINI or Alt-F1 may be required to return the desktop to normal. DrivesIcon ========== Some customers are experiencing problems with DRIVES icons opening and then closing immediately. This seems to be a disk problem which can be cleared up with a CHKDSK on the offending disk. To do so: 1) Boot with the OS/2 install diskette. 2) Follow prompts and enter install disk 1 when prompted. 3) Follow the prompts, ESC to exit when prompted. 4) With install disk 2 in the A Drive run: CHKDSK /F (FAT) or CHKDSK /F:3 (HPFS) If this does not work, have the customer erase the hidden file WP_ROOT._SF (Fat) or WP ROOT. SF (HPFS). Of course, the file will have to be unhidden first. LostIcon ======== Customer has lost an icon for a workplace shell folder, such as the OS2 System Folder icon has defaulted to yellow folder-to recover: 1) Must have access to another OS/2 2.0 machine. 2) Copy the Extended Attributes from this other machine's OS/2 System folder to diskette with EAUTIL as follows: FAT -EAUTIL C: OS!2_2.0_d OS!2_SYS easave /P /S or HPFS-EAUTIL "C: OS!2 2.0 Desktop OS!2 SYSTEM" easave /P /S where C: is the actual drive on which the operating system resides 3) Take the diskette to the machine with the missing icon and copy the extended attributes in easave to the os2 system folder with eautil: FAT -EAUTIL C: OS!2_2.0_d OS!2_SYS easave /O /J or HPFS-EAUTIL "C: OS!2 2.0 Desktop OS!2 SYSTEM" easave /O /J where it doesn't matter if the machines are mix and match Fat and HPFS, just use the right directory names for the file system you are copying to or from at the time. After a shutdown and reboot the correct icon should appear, and the customer will not have lost any customization. SaveIcons ============== For Customers having problems associating an icon with an object this method seems to work: 1) Open a settings notebook for the object. 2) Select the General Page and push the FIND pushbutton. 3) Select the LOCATE pushbutton 4) Select the PATH tab 5) In the Location field, enter the path in which the icon physically resides: C: MYICONS (or whatever) 6) Press the OK pushbutton 7) Change the Name field to the filename of your icon: MYICON.ICO (or whatever) 8) Make sure that ICON is hilighted in your Types box 9) Check "search just this folder" 10)Press the Find pushbutton 11)Your icon should now appear selected on the screen- Press OK That should do it! Your icon should now "stick". /* ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ */ INFO APAR - OS/2 2.0 PROBLEMS RUNNING ON GATEWAY PC Subject: OS/2 2.0 on Gateway 2000 machines - Here is an "official list" on what are known problems to look out for on Gateway 2000 machines. - Problem 1 - Country.Sys not found message on all Nomad "notebook" models. This is a problem with the BIOS on the Nomad machines according to Bill Williams. Nomad machines with Pheonix 1.02 BIOS will need to be upgraded. The Gateway 2000 Tech support group expects us to send the customer over to them on this problem. - Problem 2 - Gateway machines with a 486 can potential have DIVIDE UNDERFLOW errors. This problem is a bug on the 486 math coprocessor and will only be seen if the customer is running software that takes advantage of the coprocessor. The Rev E mother boards of 486 Gateway machines may exhibit this problem. If the customer is running into this problem we can send them to Gateway so they can upgrade to the Rev F version of the mother board. The Rev F board has a HW fix workaround for the coprocessor bug. - Problem 3 - Gateway machines that Trap 2 on boot or install This problem could be one of two things. The first is that the Read Ahead Cache on the mother board could be bad. Gateway has seen several cases of this. The workaround for this problem is to disable the external caching. This can be done by hitting Ctl-Alt-Esc during POST to activate CMOS Setup. The real solution however would be to get another board from Gateway or let them fix the one the customer has. The second thing that could cause the Trap 2 is bad memory. In this case the only thing that will consistently fix the problem is locating the memory sim that is bad and replacing it. Sometimes - just moving the sims around helps though. - For either of the versions of the Trap 2 problems it is also okay to refer them to Gateway. - Problem 4 - Machine hangs or screen goes blank when user goes into a DOS session on Gateway 386 machines. Here we have the TSENG video chip set problem. Most all of Gateway's 386 line has been shipped with the Diamond Speedstar video card that uses the TSENG chip set. Here Gateway asks that we work with the customer to try the VSVGA.SYS fix for the problem. They have the the fix module for this problem at Gateway and are helping customers that call there first without sending them to us. Bill Williams thinks that we can do the same here since it is not a problem specific to Gateway 2000 machines. /* ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ */ WINAP INFO APAR - CLIPBOARD, DDE, OLE PROBLEMS 5. Clipboard and DDE 5.1 Tell Me Q. Cut and paste operations seem very slow for WIN-OS/2 applications. How can I speed things up? A. If you are running your applications in WIN-OS/2 Full Screen mode you can disable the Public option for the WIN-OS/2 Clipboard. This will dramatically speed up cut and paste operations. Select Clipboard from WIN-OS/2 Accessories Folder in WIN-OS/2 Full Screen. Chose 'Options' drop-down menu and make sure 'Public' is not checked. You will need to repeat this each time a new clipboard is started. If your applications are running seamlessly (in windows on the OS/2 desktop) the only way to disable the 'Public' option is to edit the system.ini file in the 'C: OS2 MDOS WINOS2' directory (where 'C' is the drive that OS/2 was installed to). Remove 'CLIPWOS2' from the statements that begin with 'SAVDMApps=', 'MAVDMApps=' and 'WOS2VDMApps='. Note that the clipboard is always private when WIN-OS/2 is running in real mode. Note that mistakes in editing the system.ini may cause serious problems. Q. Data I put in the OS/2 clipboard doesn't show up in the WIN-OS/2 clipboard, why is this? A. If you are trying to paste an icon, the icon file may be too large, or the application might not understand the device-independent bit map (DIB) format of the file. Other data formats may also cause a rendering problem and not be transferred. Q. OLE (object linking and embedding) won't work from Amipro or Word under WIN-OS/2. What is the fix? A. Copy OLECLI.DLL, OLESRV.DLL and COMM.DLL from 'C:OS2 MDOS WINOS2 SYSTEM' to 'C:OS2 MDOS WINOS2' where 'C' is the drive OS/2 was installed on. Q. I can't get DDE (Dynamic Data Exchange) to work between OS/2 and WIN-OS/2 or between VDMs. Why is this? A. This will normally work. In the event of problems it is best first to contact the application supplier directly, as there are many application-specific issues relating to the successful use of DDE. If your computer is running in XGA (or 8514) video mode remember to set VIDEO_SWITCH NOTIFICATION to ON. /* ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ */ Migration and Installation 2.1 Tell Me Q. What does the OS/2 'migrate' utility do (select Setup - Migration Applications from the OS/2 System Folder or type 'migrate' at the command prompt)? A. The sole purpose of the migrate utility is to create program objects on the OS/2 desktop. It uses a migration database to determine what settings to apply to the object (an example of a setting for a Windows application would be DPMI memory limit). A migration database is shipped with OS/2. It is also possible to create a customized migration database. Q. How do I install WIN-OS/2 on my system? I already have Windows on my machine, how can I run a replica of my existing Windows environment under OS/2? A. One of the options as you install OS/2 is to install the WIN-OS/2 subsystem to allow you to run Windows applications from within OS/2. If you already have a Windows 3.0 desktop on your system you will be given the option to create a brand new WIN-OS/2 desktop, to create a WIN-OS/2 desktop based on the existing 3.0 desktop or to use (share) the original desktop . The second two options will not be allowed if your existing environment is 3.1. You can install or reinstall WIN-OS/2 at any time by selecting Setup then Selective Install from the OS/2 system folder. The most convenient way of accessing your old Windows applications is by creating objects (icons) on the OS/2 desktop. To automatically create Windows program objects on the OS/2 desktop, select Setup - Migrate Applications from the OS/2 System Folder. Simply double-click on the icon to start the application. The information needed by OS/2 to configure the Windows applications is contained in a migration database. The database contains information (including the location of system files, initialization files needed, DPMI settings) about many applications. It is possible to create a customized migration database. Q. My old Windows applications fail to run properly when I try to run them from OS/2. What am I doing wrong? A. This is how it works. If you migrated your old Windows 3.0 environment (environment, not applications) to WIN-OS/2 when you installed OS/2 and then you run WIN-OS/2 Full Screen (select OS/2 System Folder, Command Prompts) all your Windows applications will show up as icons in WIN-OS/2 and should run fine. These applications however will not be accessible from the OS/2 desktop. To make them accessible from the desktop, select Setup - Migrate Applications from the OS/2 System Folder. If you chose to create a default WIN-OS/2 environment when you installed WIN-OS/2 none of your old Windows applications will be visible on the OS/2 desktop although they will show up in WIN-OS/2 Full Screen. To make them accessible from both WIN-OS/2 Full Screen and from the desktop select Setup - Migrate Applications from the OS/2 System Folder. Migrate Applications does nothing more than create program objects on the OS/2 desktop. It uses a migration database to determine the WIN-OS/2 settings (for example the DPMI memory limit) for the program object. If you are having trouble with an application consider reinstalling it from WIN-OS/2 Full Screen Program Manager - File - Run. The installation program for the application will usually warn you that a copy of the application already exists. Simply opt to overwrite the existing copy of the application. The effect of doing this is to configure the application to run under WIN-OS/2. The alternative to re-installing the application is to determine what is wrong and fix it manually. For example, Lotus 123 can be fixed simply by copying the 123w.ini file from the old Windows directory to 'c: os2 mdos winos2' (replace 'c:' with the drive where OS/2 resides). Q. I have Windows 3.1 as well as OS/2 on my system. I migrated the mini-applications that come with Windows 3.1 to WIN-OS/2, but can't get them to run from WIN-OS/2. Why is this? A. The mini-applications that come with Windows 3.1 have header information that identifies them as being compatible with Windows Version 3.1+, and an error ('The WIN-OS/2* Session does not support this application') is displayed if an attempt is made to run them in a Windows 3.0 emulation environment such as the current version of WIN-OS/2 (you'll also get an error if you try and run them under the original Windows 3.0). /* ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ */ WINAP INFO APAR - PRINTING 6. Printing 6.1 Tell Me Q. Is the OS/2 printer driver that I installed on the desktop used when I print from a Windows application? What purpose does the WIN-OS/2 print manager serve? Should I disable it? A. To print from a Windows application, you must have installed the Windows printer driver appropriate to your printer (select 'Control Panel - Printers' from WIN-OS/2 Full Screen). If the port used has an active OS/2 printer object on it, then the output from the Windows printer driver will be passed through the OS/2 driver but will not usually be changed. Some OS/2 printer drivers may add a printer initialization sequence. If you are getting unexpected results when printing from WIN-OS/2, try changing the OS/2 printer driver to IBM NULL. This driver will not add any initialization sequence. The WIN-OS/2 print manager is only used if the active printer is set to a 'COMx' port, or if the OS/2 spooler is disabled. If port 'LPTx' or 'LPTxOS2' is selected and the OS/2 spooler is enabled the WIN-OS/2 spooler will be by-passed. Select 'Control Panel - Printer' from WIN-OS/2 Full Screen to disable the WIN-OS/2 spooler if desired. Q. I installed a new WIN-OS/2 printer driver and now whenever I print from a Windows application under OS/2 the ATM fonts print out very poorly - like 9 pin dot matrix. Why is this? A. In the first case, reinstalling ATM solves the problem. Unfortunately it's not possible to easily re-install just ATM from the OS/2 installation diskettes. Instead you would need to selectively re-install WIN-OS/2. Select Setup - Selective Install from OS/2 System folder. If you have a copy of ATM Version 2.02 (or Version 1.15) install this instead. Select Program Manager - File - Run from WIN- OS/2 Full Screen. Q. My WIN-OS/2 printer is configured to print to a COM port. Can I route my print jobs via the OS/2 spooler? A. Print jobs can't be routed via the OS/2 spooler if the WIN-OS/2 printer is assigned to a COM port. Q. I have configured my WIN-OS/2 printer to a COM port and the first page of the first print job that I submit after booting my system is not printed correctly. Why is this? A. This problem is being investigated. APAR PJ05025 (status; open). The workaround is to configure the printer to print to an LPT port, example LPT1.OS2. If it is necessary to print to a COM port and there is a spare LPT port , set the WIN-OS/2 printer to LPTx.OS2. At an OS/2 command prompt type 'spool /D:LPTx /O:COMx'. Then set an OS/2 printer object to COMx, making sure all the COM settings are correct. WIN-OS/2 print jobs will be routed to COMx. This approach has the added advantage that the OS/2 spooler may be used. The WIN-OS/2 Print Manager should be disabled. Type 'Help Spool' at an OS/2 Command Prompt for further information on reassigning ports. Q. We have an OS/2 Novell Network with remote printers. I have a network printer object on the OS/2 desktop that is not assigned to any port. I am able to print by dragging and dropping objects onto the printer icon but I can't print from WIN-OS/2. Why is this? A. The network printer object on the OS/2 desktop needs be assigned to a port (example LPT2) if you want to use the printer from WIN-OS/2. 'None' is not a valid port selection for a printer under WIN-OS/2. Q. Printing is very slow from my WIN-OS/2 applications. How can I speed things up? A. Many factors contribute to speed of printing. Try a different printer driver (there is for example an accelerator for the LexMark 4019 PPDS driver) and use fonts that are resident on your printer to keep the size of print files as small as possible. Q. The fonts I see on the screen do not exactly match the fonts being printed. Why is this? A. IBM ATM font metrics were specifically provided for OS/2 so that they could also be used in international settings. Some of the metrics for certain fonts, for example zaph-dingbats, do not always match the those of the postscript printer. To get round this problem either install a set of ATM fonts that match your printer fonts or turn off the 'Use Device Fonts' option in the ATM Control Panel in the WIN-OS/2 main folder. /* ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ */ WINAP INFO APAR - SEAMLESS, ATM, COMMUNICATIONS 3. Seamless WIN-OS/2 3.1 Tell Me Q. What is the difference between a seamless and a non-seamless application? Are there any problems running Windows applications seamlessly? A. First realize that the way an application is started (double-click on the application icon on the desktop...) is the same whether the application is set to run seamlessly or non-seamlessly. When a Windows application is started it is seamless if it starts as a window on the OS/2 desktop (imagine the Windows application starting up and 'punching a hole in the desktop' so that the application window can be displayed) . It is non-seamless if clicking on the application icon on the desktop first starts a WIN-OS/2 DOS session, and then starts the application from this new session. In this case the OS/2 desktop has been replaced with WIN-OS/2 Full Screen (imagine running Windows 3.0) and the application is running within a complete Windows environment. When the user closes the application, the Windows session is automatically terminated, and the OS/2 desktop is re-displayed. When applications are migrated to the desktop (Setup - Migrate Applications from the OS/2 System Folder) they are configured to run seamlessly. It is a simple matter to change them to run non-seamlessly (click on application icon with right mouse button, click on open, click on settings, click on session, click on WIN-OS/2 Full Screen). Running windows seamlessly is a complicated thing for OS/2 to do internally. The initial release of OS/2 2.0 has some glitches. The reported seamless problems are; - occasional unexpected loss of focus, for example when running Word for Windows seamlessly. Use the left mouse button to restore focus. APAR PJ03705 (status open). - no Windows applications are running at shutdown, but upon reboot show up cross-hatched (as if they were running when the machine was shut down). Correct by closing WIN-OS/2 session from window list. Press CTRL-ESC then use right mouse button to close. APAR PJ03705 (status; open). - OS/2 gets confused when more than one Windows application is running. Selecting an application from the window list (press CTRL-ESC) results in the wrong application being selected. Correct by changing session parameters for the applications. Do this by clicking on application icon with right mouse button, click on open arrow, select settings, select session, then click on 'Separate Session' check box. APAR PJ03705 (status; open). Q. My display is not VGA. Can I run my Windows applications in seamless windows? A. You will not be able to run seamless windows unless you are running OS/2 in VGA mode. 4. Adobe Type Manager (ATM) 4.1 Tell Me Q. How do I use the ATM (Adobe Type Manager) fonts shipped with OS/2? A. ATM Version 2.0 is shipped with OS/2, for use by Windows applications under OS/2. ATM is disabled by default. To enable you must select the ATM Control Panel from the WIN-OS/2 MAIN folder under WIN-OS/2 Full Screen. Choose option 'ATM ON', and click on 'Add' to install the 13 ATM Fonts shipped with WIN-OS/2 (they're on Driver Installation Diskette 5 so you'll need to have this ready). Note that extra ATM fonts may be purchased from Adobe. Q. I get a GP fault in ATM16.DLL whenever I try to load a WIN-OS/2 application. What's the fix? A. Install ATM Version 1.15 or 2.02 from WIN-OS/2 Full Screen. IBM can supply the 2.02 upgrade as a single file atmfix.exe. Q. I selected Printers from Control Panel in WIN-OS/2 Full Screen, then I selected Setup for my printer. What Cartridge option should I select? A. You must select None, unless your printer has a pluggable font cartridge installed. In this case select the cartridge that exactly matches the one installed in your printer. Q. The font metrics for the ATM fonts shipped with WIN-OS/2 are not the same as those sold by Adobe for Windows 3.0. Why is this? A. Different source metrics (.afm files) are used. The fonts shipped with WIN-OS/2 match a standard IBM format. You can install type 1 ATM fonts if necessary to assist in matching screen fonts with printer fonts. Contact Adobe for details of available fonts. 7. Communications 7.1 Tell Me Q. I selected Setup - Options from WIN-OS/2 MAIN in WIN-OS/2 Full Screen and get a list of options including No Network Installed. Which option should I select? A. Unless you are using a DOS-based LAN requestor (rather than an OS/2 based LAN requestor) you should select option No Network Installed. The only other valid option listed is IBM PC LAN Program. All the other options were included in error and should be ignored. These options can be got rid of (by editing the SETUP.INF file in OS2 MDOS WINOS2 SYSTEM directory). In most cases, users should not try to do this. Q. What do I need to do to get Rumba for Windows working under WIN-OS/2? A. Rumba may have problems when running in the background due to some INT 28 handling done in DOS emulation. Currently it is best to run in a VMBOOT session to avoid this problem. A fix is being worked on. Q. Are there any reasons why my old Windows communcications packages won't run under WIN-OS/2? A. All WIN-OS/2 applications run in OS/2 VDMs (virtual DOS machines). VDMs support a maximum of 1000 interrupts per second and this causes problems for many communications packages running at higher baud rates. If you are having problems, try reducing the baud rate if this option is available for your application. Q. Does WIN-OS/2 include named pipe support? What applications require this? A. A fix which includes a correct implementation of named pipes is available. APAR PJ03738. An integrated DOS kernel which includes this fix is expected to be available in the OS/2 service pack being prepared for release this fall. Some DOS and Windows applications use named pipes for access to Microsoft/Sybase SQL Servers. These applications also require that the file NETAPI.DLL for 'LAN Server' or 'LAN Manager' networks, or the equivalent for other networks, is accessible via the appropriate path statement. /* ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ */ USING ATI GRAPHICS VANTAGE VIDEO CARD W/ MOUSE PORT The ATI graphics vantage video card comes with a mouse port and an ATImouse. The mouse port will accept other mice as well. There tend to be problems using a mouse through this port due to interupt conflicts. But this can be resolved by setting the interupts for the mouse on the video board. Follow the steps below to do this... .. ... 1) On disk 1 of the utilities disks which come with the board there is a program called INSTALL ( on some it is VINSTALL ). This must be run from DOS ( booted DOS not a vdm dos session in OS/2 ). ... 2) Select "Set Power Up Configuration". This will list current selections for the board. ... 3) First thing to check is the Mouse Enable/Disable selection. Of course this must be set to enable. If it is not, then enable it. This may be your only problem. ... 4) Check port addresses. Primary should be:23C to 23F Secondary should be 238 to 23B you should not need to mess with these. ... 5) Set the interupt level. The available levels are 2-5, but 2-4 are already used by the system. 5 is a good choice as long as they are only using one printer. The interupt for lpt2 is 5 but as long as the only have one printer this will be no problem. If they want to use 2 printers, then advice them to get a converter to use the mouse in a serial port. ... ... NOTE: if during install they use another mouse beside the ATI, it may not work. advise them to use the ATI mouse during the install, and then switch back if they want to use the other. ... ... Any other questions call ATI customer service:416-756-0711. /* ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ */ CSET/2 AND WORKFRAM2/2 CHECKLIST C Set/2 and Workframe/2 Checklist ================================= .. .. INFORMATION TO GATHER --------------------- .. 1. a: Include syslevel CSD information for Base OS/2, Workframe/2, and for C-Set/2. .. 2. Is this A:a Workframe/2 problem, B: a compiler problem, or C: a debugger problem ? .. If you answered A to question 2, -------------------------------- .. 3. What is the date of the Workframe/2 EXE files? Are they pre-GA level? .. 4. What was the order of installation? Should be Workframe/2, Toolkit,and then C Set/2 (C Set/2 should always be last). .. 5. Was the update config.sys box checked? From the Workframe/2 icon pulldown have the customer click on settings. If update was checked the path and file name of program will read: d: IBMWF BIN WF.EXE. If the box was not checked it will read: d: IBMWF BIN WFENV.EXE .. 6. Ask for the EXACT error message that was received. .. 7. What type and make of display adapter is on the machine? .. EGA, CGA, VGA, SVGA, XGA, or BGA(8514) .. .. If you answered B to question 2, -------------------------------- .. 3: Is this A:a compile time problem, or B: an execution time problem? ____ .. if you answered A, .. 4: Is it a trap, or an internal compiler error? ____ If yes, please write in the message(s), including the message numbers (if any are displayed). .. Please pack (using PKZIP) a preprocessed file (produced with /P) which will reproduce this problem. Please include all the compile options used at the time of the failure. .. 5: If you answered No to question 4, Try compiling with /Sm turned on. If the failure persists, please follow the steps outlined above to provide C-Set/2 support with a test-case. Please include all compile options and message numbers. .. 6: If you answered B to question 3, Try the follwoing .. a) Compile with optimization off. If your program works at /O-, and fails at /O+, this is a compiler bug. Please follow the steps outlined above to provide C-Set/2 support with a test-case. .. b) Compile with /Kb, and remove all missing prototype warnings by supplying the missing prototypes. Investigate uninitialized variable warnings, and other warnings which may seem suspicious. .. c) Try expanding stack space with the linker /ST option, and the stack size parameter on your begin thread. The minimum sizes for stacks are as follows: For thread 1: 8K. Threads started with _beginthread: 12K. Add 4K if you call any PM functions. Add another 4K if you call any 16 bit functions. .. If none of these worked, please report the symptoms of the problem the best you can. .. If you answered B to Question 2 ------------------------------- .. 7: Is your debugging mode A: synchronous or B: asynchronous? ___ .. 8: Please describe the problem as best you are able, including the windows in which the problem manifiests itself in. .. If you answered A to Question 2 ------------------------------- .. 9: Please describe the problem as best you are able, including the windows in which the problem manifiests itself in. .. .. Any information relating to the problem, including this file can be sent to to CSET2@vnet.ibm.com on internet, or 70400,2356 on compuserve, or CSET2 at TOROLAB6 on VNET (internal IBM network). /* ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ */ COPYING LARGE FOLDERS TO DIFFERENT DRIVES AND GETTING GARBAGE IS Copying large folders from any type drive to any other type drive sometimes causes many subfolders to be created, each with the entire directory structure of what is being copied. In essence, this operation will fill a partition with garbage. Problem seems to be more easily recreatable when source and destination partitions have different file systems (i.e., copying from hpfs to fat). This problem occurs whether using context menu to copy or dragging and dropping. APAR PJ03685 addresses this problem. /* ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ */ HINTS FOR HANDLING WORKPLACE SHELL QUESTIONS/PROBLEMS. OS2INFO This Info APAR contains hints on doing problem determination for the Workplace Shell. The following areas are discussed: Extended Attributes (including sections on file systems, Dos utilities, Deinstalling OS/2, and CHKDSK), Shutdown, INI files, Nowhere directory, and the WP ROOT. SF file. EA's EA's play a major role in OS/2 2.0. The Workplace Shell uses ea's for everything. The WP Object is the object in workplace shell from which the other objects descend. EA's contain the information as to kind of object, where it is located, etc. Three types of objects: Persistent - These objects persist across boots 1. File system objects : Program references and folders are examples. The Desktop Directory contains the ea's for these objects. 2. Abstract objects : Printer, shredder, color palette are examples. The information for these objects are stored in the ini files. 3. Transients - These objects are gone upon reboot ( Find results or Task List) HPFS file systems have the ea attributes attached to each file. FAT file systems have all the ea's in the ea data. sf file. DOS Utilities Most DOS utilities are not concerned with preserving the pointers to the ea attributes that are contained in the FAT table. These utilities often do absolute sector reads and writes instead of manipulating the entire FAT entries. This is the reason people should not run disk defragmenters even from the DOS environment on a dual boot system. The pointers in the FAT cross-linked, etc.) result. Chkdsk /f cannot always clear these pointer from the FAT table entries. DOS utilities cannot harm a disk with an HPFS OS/2 partition since DOS cannot see the partition or manipulate the files. Deinstalling OS/2 The only way recommended for deinstalling OS/2 (for a successful reinstall of OS/2) is to format. HPFS Chkdsk should not be run on a live drive. (Swapper will always show allocation errors as it cannot be correct with the shrinking and growing. Swapper allocation errors should not be of concern.) Chkdsk /f may take several passes to clean up an HPFS drive as it cleans up primary structures and then secondary structures in several passes. Shutdown A poor shutdown can corrupt ini files because the workplace shell uses lazywrite threads and the information may be only half written out to the ini files. EA information may not be completely written either. INI's If you run makeini without erasing the ini file, you will be updating the ini. This is the best method to try for replacing objects that have been lost from the desktop. This procedure will not reinitialize your desktop to its default state. Placing your current ini files and config.sys in the install directory should restore your system to its current state when an ALT-F1 is performed. Nowhere The nowhere directory should have nothing in it. When an object doesn't know where to go, it goes there. It can get moved by moving it from the command prompt. WP ROOT. SF This file exists for each drive (including floppies and lan drives). A place was needed for ea's to be kept for drives objects since ea's can't be attached to the root directory. This file should be erased when drive objects are not working correctly, as when the icons are messed up, files are missing, or the drives icon opens and immediately closes. /* ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ */ MOUSE PROBLEMS AND RESOLUTIONS CHECKLIST Mouse Problems and Resolutions Checklist ======================================== ... For General Mouse driver information, type HELP MOUSE at an OS/2 prompt. Also see InfoApar II06079, Mouse, Installation and Configuration Information ... **Problem* No mouse pointer movement or no mouse pointer. An error is received upon boot up: SYS1201 VMOUSE.SYS not installed. *Explanation: This means that mouse.sys was installed, but could not find the mouse. If it can not find a connected mouse, then it will not install vmouse.sys. (It does not mean that vmouse.sys was not found as the error implies.) Either the install program could not correctly determine what type of mouse it was, or could not determine that a mouse was indeed present. *Resolution(s): This problem can be due to one of the following: ... 1- An unsupported type of mouse Check to see if there are any dip switches on the mouse. Some mice have settable switches that put it into MicroSoft Mouse emulation mode. ... Ask the customer what mouse driver was being used in DOS. If it is not the MOUSE.COM provided by DOS, then the mouse may be operating in a proprietary mode. ... 2- If the user had mouse support during the graphical install portion ofthe installation process, then he/she probably changed the mouse driver/port that OS/2 had already chosen. Have the user run the Selective Install program found in the OS/2 System/System Setup folder and choose a different driver. See InfoApar II06079 for correct driver. ... 3- An interrupt conflict Check the interrupts (use FI 863 as a guide). On an AT bus system, a serial mouse will only install on COM1 and COM2,and only if COM1 and COM2 are at the standard I/O addresses and IRQs: COM1= 3F8, IRQ4 and COM2= 2F8, IRQ3 See InfoAPAR II06091 for a detailed review of Interrupts and OS/2 2.0. ... 4- A bus mouse that is not being detected. See Apar PJ04855 and the following problem. ... ... **Problem* A bus mouse won't install. See Apar PJ04855. *Explanation: This may be due to one of the following: ... 1- Some bus mouse connections use IRQ0 which is the same as that used by the system timer. This is common when the mouse port is on the motherboard. -A serial mouse (or possibly a serial connection adapter, depending on hardware compatibility). ... 2-There is a problem with the autodetection systems and certain kinds of bus mice (e.g. PC Mouse Systems bus mouse). This results in the system not "seeing" the mouse at install and thus it will not work. -The driver, MSBUS01.SYS from version 1.3 works for many bus mice that are not fully 100% Microsoft compatible. Obtain 13MOUSE fix. Note: If this is a 3-button mouse, only 2 buttons will work. ... 3-Some machines do not use the 8042 keyboard/mouse chip to communicate with the mouse and keyboard ports and do not follow IBM spec for a PS/2 port. They are, therefore, not supported. (For example, Leading Technology uses a Samsung motherboard with a proprietary chip. The mouse plugged into the mouse port on a Leading Technology machine will not work.) -Use a serial mouse. ... ... ** Problem* A serial mouse won't work even though the IRQs check out. *Explanation: If the mouse is attached to COM3 or COM4, it will not work at this time. We only support attachment to COM1 and COM2. ... If the mouse is attached to COM1 or COM2, verify that the com port is at the standard I/O address and IRQ. ... Check for debug kernal vs. regular kernal in root directory. Debug kernal may have been installed by a CE and left on by mistake. It will monopolize com1 since it defaults to com1 for input and output, and will thus override mouse commands. ... *Additional problem determination: Issue a MODE COMx (where x is 1 or 2) from an OS/2 or DOS command prompt. This is a test of the COM ports: - If it reports that the port (the one the mouse is attached to) is NOT available, then MOUSE.SYS is LOADED. This means that the drivers are correct; don't change the CONFIG.SYS statements. ... - If it reports the baud rate and all the other COM port parameters, then MOUSE.SYS did not recognize the mouse and did NOT Load. See InfoApar II06079 for correct driver. ... ... **Problem* Logitech Mouse doesn't function under OS/2 when installed with the Logitech drivers. *Explanation: Most Logitech mice emulate Microsoft mice and use the PS/2 Pointing Device. *Resolution: The CONFIG.SYS should contain the following statement: DEVICE=C: OS2 MOUSE.SYS (do not specify TYPE=...) ... When a user selects a wrong mouse (Logitech serial, for example), then goes back via selective install and changes the selection (to PS/2 pointing device, for example), the statement: DEVICE=C: OS2 PCLOGIC.SYS is left in the CONFIG.SYS and the mouse will not work. The user must edit CONFIG.SYS and remove the offending statement by hand, leaving only the MOUSE.SYS and POINTDD.SYS statements in CONFIG.SYS. ... ... **Problem* After performing dual boot to DOS, mouse does not work. *Explanation: Mouse has a "memory" that remembers the mode it was in previously. *Resolution: Before performing the dual boot to OS/2, issue the command MOUSE PC. (If the mouse is in COM2, type MOUSE 2 PC. Sometimes, for Logitech mice, the command needed is LMOUSE PC or LMOUSE 2 PC). You can also perform a cold boot after issuing the BOOT /OS2 command. The third suggestion is to unplug the mouse and plug it back in after a few seconds, then boot to OS/2 to reset the mouse to MS mouse mode. ... ... ** Problem* MOUSE.SYS loads fine but VMOUSE.SYS does not load. *Resolution: If this is a dual boot machine, make sure the user is NOT loading the DOS MOUSE.SYS. ... ... **Problem* No mouse pointer in a VMB. *Resolution: Use the MOUSE.COM provided in OS2 MDOS subdirectory. ... ... **Problem* Can't use alternate pointing devices. *Resolution: 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. ... ... **Problem* The mouse gets out of sync on a 50 MHz Systems (AT bus). *Explanation: There have been some intermittent problems with AT-style bus machines with a mouse. The mouse can get out of synch. Input will function through the keyboard and the mouse, but it is recommended to shutdown the system and restart to "resynch" the mouse. ... ... **Problem* A 3-button mouse doesn't have three working buttons. *Explanation: The support is there for some of these mice at the device driver level but is not implememted at the WPS level. ... ... **Problem* The mouse pointer suddenly zips over to the side of the screen and hangs there, no longer responding to any mouse movements. In most cases, a cold boot has been the only remedy. See Apar PJ04330. *Explanation: This is caused by a hardware glitch and cannot be prevented from happening, but can be recovered from without a cold boot being required by using a special version of the mouse driver. *Resolution: Obtain WILDMOUS fix. ... ... ** Problem: The PS/2 Mouse on a PS/2 machine is responding too slow. *Resolution: Obtain FASTMOUS fix. ... ... Known MOUSE APARs: For open apars, if the customer has a similar problem add them to the IP page of the APAR. ... II06091 Infoapar - Interrupts and OS/2 V2.0 II06079 Infoapar - Mouse installation and configuration II06174 Infoapar - ATI Graphics Vantage Video Card with Mouse Port II06069 Infoapar - Com-port information ... PJ04534 Kensington Expert Mouse will not work with OS/2 V2.0 PJ04754 Mouse Systems PC BUS Mouse won't work with OS/2 V2.0 PJ04073 OS/2 supports only one Mouse. (APAR CLOSED as SUG). PJ04196 Selective install does not always remove DEVICE stmts PJ04415 Logitech 3 Button Mouse. 3rd button doesn't work. PJ04589 CHICONI Tracking Kybd with built in 3 button trackball PJ04545 Logitech trackman PJ04244 Logimenu.com will not work in OS/2 VDM PJ04330 Mouse hangs at right side of screen PJ04628 Mouse will not work with WIN-OS/2 PJ04810 Mouse systems optical mouse PJ04812 Chicony Trackball PJ04429 8516 Touch screen driver only operates with IBM mouse PJ04351 Cannot use 3-button mouse PJ04479 Special program for disabled users has sticky keys PJ04611 Semigraphics tablet will not work in OS/2 PJ04415 Logitech cordless serial 3-button mouse; 3rd button not operational in dos apps PJ04855 MS bus mouse will not work under OS/2 PJ04413 DOS mouse drivers that work in MS-DOS 5.0 don't work in VDM or VMB /* ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ */ INSTALLATION PROBLEMS ON IBM SYSTEMS AND OEM EQUIPMENT ************************************** MICROMASTER'S AOX BOARDS ************************************** Must be up to the latest "flash prom code" (control code) version. The latest is as follows: 32 bit boards Version 2.16 16 bit boards Version 1.24 There appears to be no problems with the 32 bit board but there are some reports of a "flaky mouse" with the 16 bit boards that as of yet has been unconfirmed by AOX. If customer does not know if he/she has a 16 or 32 bit board, have customer check serial number. All 16 bit boards begin with AA16..., else it is a 32 bit board. Make sure customer has MOD 80 ID set to no. Make sure customer has MMemory set to unmapped. to obtain the latest version control code, dial the AOX BBS at (617) 890-3393. The 16 bit code file is named 386MM and the 32 bit is MM32-BIT. ********************************************* INTEL SNAPIN BOARDS AND INBOARDS ********************************************* SNAPIN ------ There does not appear to be any problems with OS/2 2.0 and the Snapin board. Just make sure the osnapin.sys driver is at the latest version 1.1 (dated 10/30/91) and it is included in the config.sys file. There are two limitations: 1) The operating speed cannot be changed by the hot keys 2) Busmaster boards are not supported. INBOARD ------- The inboard is no longer supported by Intel, nor do they suggest utilizing the inboard with OS/2 2.0. They have successfully installed OS/2 on machines such as the MOD 50,50z, and 60, how- ever, it's reliability is unknown. It will not work with the Mod 25 and 30 machines. The driver that is needed in the config.sys file for the inboards is inbrdos2.sys (dated 2/17/88) Some of the older boards are not OS/2 compatible at all. To check compatibility, check the serial number on the board. If the last character is an "A", it is OS/2 compatible (although not necessarily 2.0 compatible.) ******************************** SYDOS REMOVABLE MEDIA ******************************** Sydos' driver in not currently compatible with OS/2 2.0. They However, they are looking into creating a driver in the near future. Once OS/2 is installed, IBMINT13.I13 can be used to to recognize the drive, but in order to use, it has to first be formatted with OS/2. This is *NOT* supported and it's relia- bility is unknown *************************************** ADAPTEC IDE CONTROLLERS *************************************** The following IDE controllers made by Adaptec are not not supported: ACB-2320 ACB-2322 ACB-2320A ACB-2322A ACB-2322B ACB-2322B-8 ACB-2620 Adaptec has no plans for writing OS/2 2.0 compatible drivers. /* ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ */ EGA PROBLEMS WITH OS/2 2.0 OS/2 supports pure EGA only (640x350x16 colors). Many OEM EGA adapters on the market have a number of EGA enhanced modes (AT&T = 640x400x16 colors, Paradise has an EGA 480 adapter). Our dri- rs do not support any of the enhanced modes. Please, chech your boards user manual for the hardware/software setting of adapters video mode. If you manage to install OS/2 but get blank areas on screen, a skewed screen or color blotches, this almost certainly indicates that your adapter is not running as pure EGA. In case that you have trouble installing OS2, please verify that no contention for the memory address range between the EGA and other adapters you may have exists.If you can't detect contention and the board is not an 8bit board, try putting it in 8 bit bus slot. When doing that, check manual for a dipswitch. Most EGA's are 8 bit only. If you had to install in 8 bit, you should still be able to put the board back into 16bit mode after the installation. Most boards have an auto-switching capability. This dip-switch should be disabled under OS/2 at all times. If you're installing on a laptop or a notebook computer, please consider calling the technical support representative of the manufacturer as laptops are usually not equipped norconfigured standard way. A hardware technician should be able to instruct about the adapter and BIOS configurations and different monitor setups. If your DOS application is attempting to set a video mode in DOS full screen and failing to do so, install all video related drivers/utilities from your native DOS CONFIG.SYS and AUTOEXEC.BAT. Repeat the statements in OS2 config.sys and AUTOEXEC.BAT files respectivelly. If you are experiencing video loss or crashes when attempting to run DOS MODE command or have problems using your DOS session, please call the video board manufacturer and find out whether your video BIOS needs an upgrade. /* ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ */ DIAMOND SPEEDSTAR AND DIAMOND STEALTH PROBLEMS IN OS/2 DIAMOND SPEEDSTAR: ET4000 BASED SVGA ADAPTER. If video synch problems exist in an OS/2 full screen session or desktop but go away temporarily after a DOS full screen session entered, make sure that you have executed SVGA ON from a DOS full screen session and performed a shutdown. Prior to executing this command, search for a file OS2 SVGDATA.PMI. If it exists delete it and regenerate it by executing SVGA ON from a DOS comm If your have a blurred strip across the desktop or experiencing other types of video synch problems, you may try to regenerate PMI configuration file by deleting the old PMI file and running TSR VMODE utility and selecting the highest resolution /refresh mode. in DOS full screen session. After the mode was successfull set, exit the utility and execute SVGA ON and reboot. SVGDATA.PM contains the register information for video modes supported by y adapter and is used by two drivers: BSVHSVGA in OS/2 full screen and by VSVGA.SYS in DOS full screen. Correct video driver statem in the CONFIG.SYS for SVGA support should be as follows: SET VIO_VGA=DEVICE(BVHVGA, BVHSVGA) DEVICE=x: OS2 MDOS VSVGA.SYS where x is your OS/2 system drive If video goes out of synch when switching from DOS or WIN-OS2 session to the desktop, check the ET4000 SVGA chipset on the adapter and record the batch number.If the batch is TC6059AF or higher, call the 800 support number and reactivate your call and request to be queued to OS2FIX queue. Ask for the fix for APAR PJ03677 to be mailed to you. The fix contains an updated VSVGA. SYS driver. If you have a blurred strip across the top of the desktop and have set the adapter for the highest vertical refresh rate, try regenerating the PMI file as explained above. It is important to run the VMODE utility and select the highest refresh rate mode prior to running SVGA ON. Recommended video BIOS revision for this adapter is 4.23.Contact Diamond about the BIOS upgrade. If you have intermittent video problems using DOS full screen session, set DOS settings for that icon as follows: HW_ROM_TO_RAM to ON, DOS_RMSIZE to 624. Settings screen can be reached by clicking with the right mouse button over the icon, selecting "Open settings" and going to the "Session" page in the notebook. DIAMOND STEALTH ADAPTER This adapter is currently not supported in high resolution mode. This however should not cause installation problems. After the installation is completed, edit the CONFIG.SYS and change the video related statements from SVGA to VGA. VGA video statements in CONFIG.SYS VGA should be as follows: SET VIO_VGA=DEVICE(BVHVGA) DEVICE=x: OS2 MDOS VVGA.SYS where x is your OS/2 system drive Please contact Diamond Systems regarding the PM driver availability. Recommended video BIOS revision is 2.32 for this adapter.Contact Diamond about the BIOS upgrade. /* ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ */ ------------------------------------------------------------------------------- Thank you for calling the OS/2 2.0 Support Line. Regarding the problem reported to the Support Line, we feel that this information may assist you in resoloving your problem. If you still require assistance, please call 1-800-237-5511, and reference your customer number and problem (PMR) number. Your Problem Record Number (PMR) should appear on the cover page of this faxed document.