Black Box 4

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

/ Black Box 4 / BlackBox.cdr / os2 / v2tech.arj / V2TECH.DOC

Wrap

Text File | 1992-05-15 | 36.3 KB | 921 lines

OS/2 2.0 Tech Support Document Patrick Steil OS2AAC18 @ DALVM41B OS/2 Application Assistance Center May 13, 1991 - Version 1.06 ================================================================= =============GENERAL INFO======================================== ================================================================= Phone numbers: IBM NSC BBS 404-835-6600 8-N-1 OS/2 BBS Info 800-547-1283 OS/2 Ordering Line 800-3IBM-OS2 OS/2 Defect Support 800-237-5511 Washburn & Co. 716-248-3627 (AMI Bios Upgrade) 800-836-8026 Trident BBS 415-691-1016 (PM SVGA Seamless drvs) ================================================================= New Packages on OS2TOOLS for GA code: PMSPL.DLL IBM2FLPY.SYS IBMS1506.SYS VSVGA.SYS BVHVGA.SYS ================================================================= Where to search for problems/bugs/fixes: - OS/2 README FILE - OS/2 TNT DOCUMENT ON OS2TOOLS - HONE: - NATIVEINFO(not much info yet on GA yet I'm sure) - ASKQ - IBMPC FORUMS: OS2OEM - OS/2 2.0 INFO ABOUT RUNNING ON OEM HW VGACLONE - INFO REGARDING OEM VIDEO CARDS OS2V2SDK - GENERAL OS2 INFO FROM DEVELOPERS OS2V2BUG - OS/2 2.0 BUG REPORTS OS2V2DEV - GENERAL OS2 INFO FROM DEVELOPERS OS2V2APP - PROBLEMS RUNNING APPS ON OS/2 2.0 OS2V2SHL - WORKPLACE SHELL INFO OS2DSETS - OS/2 2.0 DOS PROGRAM SETTINGS OS2WSETS - OS/2 2.0 WINDOWS PROGRAM SETTINGS ================================================================= =============GENERAL INSTALLATION PROBLEMS======================= ================================================================= Installation bugs/fixes: 1. 5.25" diskette problem: Symptom: Install program asks for disks 16, 17, and 18 during 3.5" diskette install. Problem: The CMOS was not changed to view the A: disk as a 3.5" 1.44MB disk drive. Resolution: Run the hardware SETUP program for the machine. If running AMI Bios, Press the DEL key at system bootup time. Press ENTER on the first selection "Standard System Setup". Press ENTER on the "warning screen". About half way down the screen is the A drive setting. Use PGUP or PGDN to select 1.44MB. Hit ESC. Choose "Write to CMOS and EXIT" with the cursor, press ENTER. Answer 'Y' to the question "Write to CMOS and EXIT?". From here the machine should be setup correctly. The user can then proceed to place the OS/2 installation diskette in drive A and proceed with the install again. 2. AMI Bios version problem Symptom: Various install problems. The suggestion to upgrade these items should always be made. Problem: Machine must have BIOS dated 5/9/91 and keyboard controller chip version KF. To find out version numbers, have user check information on screen as the computer is booting up. The date will be somewhere on the screen or in the CMOS information. The keyboard controller chip version can be located on the bottom of that same screen. Check the last digit in the long stream of digits. The last digit will probably be either be 8, B, D, or F. The required level should be F for OS/2 v2.0 or v1.3. Pressing the INS key during bootup will cause this info to stay on the screen. Resolution: Call Washburn & Co. at 716-248-3627 to order new versions. 3. Phoenix Bios version problem Symptom: Same as #2 above. Problem: Not yet determined what the required level of BIOS is. Resolution: Have user contact hardware vendor, or Phoenix for more info. Makers of Phoenix phone number: ? 4. COUNTRY.SYS not found Symptom: COUNTRY.SYS error message at bootup of first two disketttes 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 prevelant on ESDI/MFM/RLL drives. Resolution: If OS/2 crashes during the first two diskettes, copy IBMINT13.I13 over IBM1S506.ADD on diskette #1. Reboot and try installation again. If it happens after the first five diskettes/reboot process, perform the same function copying the IBMINT13.I13 driver from diskette #1 to the drive where OS/2 is getting installed. If this does not help, the new IBM1FLPY.ADD from OS2TOOLS may help. Just replace the old version of this file with the new one. 5. IBMS1506.ADD problem Symptom: Not sure at this time. Problem: Not sure at this time. Resolution: New IBMS1506.SYS available on OS2TOOLS. 6. Memory problems on a Model 90/95 Symptom: Memory problems Problem: Downlevel processor card/memory riser card. Solution: If your processor card has part number 84F9356 then it should be replaced.(ECA-053) If your memory "riser" card is part number 84F8157, then it should be replaced.(ECA-084) 7. Install hangs at "Loading please wait..." message. Symptom: Install hangs at "Loading please wait..." message. Problem: Possible BAD memory. POSSIBLE Resolution: Get new SIMMS. Make sure that the new SIMMS are matched in speed and type. 8. At Disk#1 install reboots computer or internal processing error Symptom: When diskette #1 of install process is inserted in drive the machine will reboot, or cause an internal processing error. Problem: Bad memory. Resolution: Replace memory with good memory. 9. FDISK errors, slow installation, grinding noise from HDD. Symptom: FDISK unsuccesful error on Disk #1, VERRYYYY slow installation, or unusual noises coming from hard drive. Problem: Incompatible hard disk driver. Resolution: 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. Installation should flow smoothly from here on. ================================================================= =============HARD DRIVE PROBLEMS================================= ================================================================= 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. Adapter: Adaptec AHA-154x Drive: IBM 0661 - 320MB SCSI Note: Adapter BIOS will not recognize the drive as Target 0 or 1 (Drives 80, 81). For OS/2 2.0, the drive can be used as a non-startup drive. Adapter: Adaptec AHA-174x Drive: IBM WDS-3180 - 80MB SCSI, IBM WDS-3160 - 160MB SCSI Note: Adapter will not recognize these drives when configured in 'STANDARD MODE' (AHA-154x emulation). Instead, the AHA-174x adapter should be configured in 'ENHANCED MODE'. This mode is supported by the OS/2 2.0 drivers, and the problem does not occur when the adapter is operating in enhanced mode. Adapter: Future Domain TMC-850/860/875/885 w/BIOS revision level 7.0. Future Domain TMC-1660/1670/1680 w/BIOS revision level 2.0. System: IBM Models 35 and 40 when the Future Domain adapter is controlling the startup diskette. Note: Will produce the message, "Disk read error has occurred" when you attempt to start the Installation diskette. Contact Future Domain for a free BIOS upgrade. 1. AMI SCSI Adapters Symptom: AMI "Fast Disk" and AMI "Fast Disk II" SCSI adapters are incorrectly recognized as Adaptec adapters. Problem: At the final restart after the installation is complete, delete from the CONFIG.SYS file, any line with "BASEDEV=AHA1xxx.ADD" (where "x" can be any character). Ensure the line, "BASEDEV=IBMINT13.I13," appears in the CONFIG.SYS file. 2. Problems with Always IN2000 SCSI adapter Symptom: Unknown at this time. Resolution: Always IN 2000 SCSI Host Adapters may require an EPROM upgrade from Always for $20 to operate with V2.0. The dividing line is not clear, and at least one customer was not helped by the EPROMS, though several others were. Always suggests installing the EPROMS and re-formatting the drive - seems to be some problems installing over DOS partitions. Always can be reached at 1-818-597-9595. The customer who was fixed by the EPROMS was unwilling to re-format. Symptoms of the problem are varied, but the most common is an FDISK error on the second diskette. ================================================================= =============VIDEO PROBLEMS====================================== ================================================================= 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. 1. Western Digital PVGA1D video card Symptom: C00005 message on screen. Problem: Happens on above video card (video chips: Western Digital C30 & C31) with 1 MB installed. Resolution: Get the fixed BVHSVGA.DLL from OS2TOOLS or the below request: REQUEST BVHSVGA PACKAGE FROM BERNIET AT BCRVMPC1 Send this file to the user and have him replace the existing BVHSVGA.DLL on their system -- \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 instruct the user to copy this .DLL into the \OS2 directory on the installed partition. 2. Out of Synch/Install problems Symptom: May vary Problem: Addressing of card in 16-bit mode. Resolution: Switch card to 8-bit mode if available. This will probably involve setting a jumper, or dip switch according to the documentation that comes with the card. 3. Video Cards using TSENG TC6059AF chip(ET4000/see below) Symptom: Problems going from DOS SVGA -> PM VGA Desktop Problem: Some hardware register not handled correctly by the GA version of the VSVGA.SYS driver. Resolution: Get new VSVGA.SYS from OS2TOOLS. 4. Trap E switching a DOS fullscreen to a window Symptom: When I window a DOS fullscreen running in SVGA I often get a Trap E. Will be prevalent on overcommited (low-memory) systems. The PM driver you are using can also have an effect. Solution: Get the new VSVGA.SYS from OS2TOOLS. 5. Trident 8900B Card Symptom: Screen "wavers". Problem: Hardware problem with these cards. Resolution: Call Trident. Phone number: ? 6. Trident 8900C Card Symptom: System hangs with blinking cursor in the upper right hand corner. Problem: PMI file usually not created properly. Resolution: See "HOW TO REGENERATE PMI FILES" below: 7. Trident 9000 Card Symptom: DOS/PM screen synch problems possible. Running SVGA ON does not help. Resolution: Follow the "HOW TO REGENERATE PMI FILES" description below. 8. Video Corruption returning to WIN-OS2 session Symptom: Video becomes corrupted when returning to a previously opened Full screen WIN-OS2 session. Problem: WIN-OS2 session not aware that a video mode switch has taken place. Resolution: Set your VIDEO_SWITCH_NOTIFICATION in the DOS SETTINGS to ON. 9. Colors of Windows applications appear distorted Symptom: Windows applications running on the OS/2 desktop appear different than in a WIN-OS2 fullscreen. Problem: The DOS/Windows application's colors have to be translated to use the OS/2 PM color palette. With the OS/2 VGA desktop, there is a limitation of 16 colors. This colors simply cannot be translated correctly. Resolution: Run the application fullscreen, or obtain a PM driver that can support more than 16 colors. 10. Installation of OS/2 halts at Blue "IBM Logo" screen Symptom: OS/2 boots up to Blue IBM Logo screen and does not finish printing "INSERT DISK #1 message". Drive light continues to stay on indefinately. Problem: Incompatible OAK Video card. Resolution: 1. Temporarily use another VGA card to get OS/2 installed. (May work after successful installation). Otherwise wait for fix from IBM(watch IBM NSC BBS). 2. NOT VERIFIED: This should only be tried by more experienced users. a. Make backup copy of INSTALL disk. b. Un Write-protect INSTALL disk. c. Boot up DOS and put INSTALL disk in drive A. d. COPY A:OS2LDR A:OS2LDR.OLD e. DEBUG A:OS2LDR f. U 4F7C g. E 4F7C h. CD.90 i. <SPACE> j. 10.90 k. W l. Q m. Use new install diskette to install OS/2. Note: The install will no longer display text on the blue screen that comes up after install diskette is inserted. When the blue screen comes up, insert disk 1 and continue. HOW TO REGENERATE PMI FILES: Start up a DOS FULLSCREEN session and type "SVGA ON". This will create a file called SVGADATA.PMI. You can then exit the DOS FS, and shutdown OS/2. At boot time, this file is read(if present) by BVHSVGA.DLL. You need to verify that the following statements appear in the CONFIG.SYS: SET VIO_VGA=DEVICE(BVHVGA,BVHSVGA) DEVICE=D:\OS2\MDOS\VSVGA.SYS Note: A PMI file tells OS/2 (BVGSVGA.DLL specifically) the capablities of your video card, resolutions supported, etc. this information enables OS/2 to perform successful mode switching between any HIGH RES Dos/Windows session and the OS/2 VGA session. Video boards and the chipsets they use:(not official list) Chipset name Board name ---------------------------- -------------------------------------- Chips & Technologies VGA chip - Cardinal, C&T MK82452 Everex VGA chip - Everex EV-673 Genoa GVGA chip - Genoa 6400 Western Digital 9010 (512K) - Paradise VGA Pro, VGA 1024, "PVGA" Western Digital 9030 (1meg) - MVGA 1024DX S3 (86C911) - STB Wind/X, Orchid Farhrenhite 1280, Diamond Stealth VRAM HIcolor Oak OTI-067 - United Solutions, Inc. Image 1024 Oak OTI-037 - VGA 800-160 (Taiwan made) RealTek - RealTek SVGA Trident 8800 chip - ATI Prism Elite, Everev 678, Maxxon, Imtec, Logix Trident 8900 chip (Zymos Poach 51) - Trident 8900, Hi Res 512 Tseng ET3000 VGA chip - Genoa 5400, STB VGA/EM, Orchid Designer, OTI SVGA (old), Optima 1024 Tseng ET4000 VGA chip - Orchid Pro Designer II, Ultra SVGA, STB Powergraph, Diamond SpedStar, Boca Research Super VGA, Optima Mega SVGA, Diamond SpeedStar + Tseng ET4000 & Sierra RAMDAC - Swan Palette Plus, 2TheMax VGA 4000, Diamond SpeedStar + HIcolor Video 7 VGA chip - Video 7 VRAM, Video 7 Fastwrite, Video 7 VEGA Deluxe, Northgate Pro Some other suggestions for video problems: In many cases, OS/2 requires a different dip switch setup for your adapter. Try some of the suggested variations in your adapter manual. I'm getting some corruption returning to my WinOS2 fullscreen Set your VIDEO_SWITCH_NOTIFICATION in the DOS SETTINGS to ON. ================================================================= ==========MOUSE PROBLEMS========================================= ================================================================= Mouse problems: 1. Mouse driver does not install correctly Symptom: No mouse pointer movement(or no mouse pointer). Problem: Either the install program could not correctly determine what type of mouse it was, or could not determine that a mouse was indeed present. If the user had mouse support during the graphical install portion of the installation process, then he probably changed the mouse driver/port that OS/2 had already chosen for his configuration. Resolution: Have the user run the Selective Install program found in the OS/2 System/System Setup folder. 2. Mouse does not work after Dual boot Symptom: After performing dual boot to DOS, mouse does not work. Problem: Mouse has a "memory" that remembers the mode it was in previously. Resolution: Before performing the dual boot, open a DOS window or fullscreen and type MOUSE PC. You can also perform a cold boot after issuing the BOOT /DOS command. The third suggestion is to unplug and plug it back in after a few seconds (this allows the mouse to be reset). 3. For General Mouse driver info: Type HELP MOUSE at an OS/2 prompt to read about proper CONFIG.SYS parameters for the mouse drivers. ================================================================= ==========COM PORT PROBLEMS====================================== ================================================================= 1. OS/2 cannot see COM3 and COM4. Symptom: OS/2 does not recognize COM3 and COM4 installed on an (E)ISA machine. Problem: COM3 and COM4 are supported on PS/2s without any additional effort. On (E)ISA machines, some additions are required to CONFIG.SYS. Resolution: Using a text editor, include "(port number, base address, interrupt number)" parameters next to the COM.SYS and VCOM.SYS filenames. One example: DEVICE=C:\OS2\COM.SYS (3,3E8,5) (4,2E8,3) DEVICE=C:\OS2\MDOS\VCOM.SYS (3,3E8,5) (4,2E8,3) NOTE: These are NOT default parameters and must be configured according to the user's hardware reference material for the card where the COM ports reside. Parameters for COM1 and COM2 need not be included (unless they are somehow nonstandard). OS/2 must end up with sequentially numbered COM ports. For example, if port two is not installed but port three or port four is installed start numbering using (2,...) in the DEVICE lines. Note that AT bus COM ports cannot be used at the same time if they share interrupts because of bus design limitations (cf. Roger C. Alford, "Under the Hood: How Interrupts Work," Byte, February, 1992, pp. 249- 256). PolyCom, a replacement driver available from shareware/freeware sources (see Question 9), supports up to eight ports with the right hardware. 2. Problems performing high-speed communications Symptom: Using high speed modems (19200+ and maybe 9600), any interference with OS/2 while downloading/uploading data(moving the mouse, CTRL-ESC) will result in losing data or even losing the connection. Problem: Hardware on the motherboard controlling the COM Port loses interrupts when running under OS/2. DOS is able to run with the slower hardware successfully since it can dedicate ALL resources to dealing with the COM port. Resolution: Need to have a 16550 UART chip installed on motherboard or serial card. Contact your normal hardware support people to find out if you can have this done on your machine. ================================================================= ==========PRINTING PROBLEMS====================================== ================================================================= Printing problems: 1. Cannot print Symptom: No printing works. Problem: Another adapter using IRQ7 to print. Cheap cable not using all 25 pins. Older parallel port card which does not support interupt driven printing. Resolution: Make sure no other adapter card uses IRQ7 (soundblaster by default uses IRQ7). Also make sure the printer cable being used has a full set of 25 pins. Some older cables do not use all the pins since in DOS they weren't all used. Under OS/2 all 25 lines can be used. Buy a cheap parallel port card that does support interrupt driven printing. ================================================================= ==========OEM DEVICES============================================ ================================================================= 1. Colorado Mountain Systems and Mountain tape backup units Symptom: Above referenced tape backup units do not work reliably under OS/2. Resolution: Reference the customer back to 800-237-5511 and tell him to reference APAR #PJ03793. For more info on the following hardware cards see the OS/2 README file found in the root directory of OS/2 after installation is complete. o ATI ETC o Cardinal FAX o Practical Peripherals o Smart Fax o Twincomm 24/96 ================================================================= ==========MISCELLANEOUS PROBLEMS================================= ================================================================= Miscellaneous: 1. Trying to run application(s) results in SYS0005, Access Denied Symptom: SYS0005 msg returned by OS/2 when you attempt to execute a program. Problem: OS/2 is unable to successfully access the file. File may be corrupted, or bad areas on the disk are causing problems for OS/2. Resolution: Run CHKDSK on the drive. If this is the boot drive, you will need to boot from the installation disk, then disk #1. When you get to the next screen, hit ESC to return to the A: prompt. At that point, insert diskette #2 into the A: drive and type "CHKDSK x: /F" where "x" is the drive you are running the command against(the OS/2 boot drive). 2. SYS3176 when trying to open any DOS session Symptom: Simply opening any DOS session results in this trap. Problem: SVGA support is screwing things up. Seems to happen more readily with the ET3000 chip based video cards. Resolution: There are three things to try: 1. In the Dos Settings set HW_ROM_TO_RAM to ON. 2. Disable SVGA support by changing the following lines: SET VIO_VGA=DEVICE(BVHVGA,BVHSVGA) DEVICE=D:\OS2\MDOS\VSVGA.SYS to SET VIO_VGA=DEVICE(BVHVGA) DEVICE=D:\OS2\MDOS\VVGA.SYS 3. Set DOS_HIGH, DOS_UMB, AND ROM_TO_RAM to ON for every DOS session. 3. FatalExit code x0401 when trying to execute Win-OS2 Symptom: Above error message whenever WIN-OS2 is started. May flash by user without user being able to record error. You can have user start up a DOS Fullscreen and start WIN at the command line to verify that this is the problem. Problem: Missing .DRV, or .DLL in the \OS2\MDOS\WINOS2 or \OS2\MDOS\WINOS2\SYSTEM directory. OS/2 probably did not install these correctly. (I got this err msg by erasing VGA.DRV in the SYSTEM directory) Resolution: Have user redirect DIR listings of the two directories above by the command: DIR > LPT1 Once the user has this information he can go back and compare his WIN.INI and SYSTEM.INI to see what file(s) are missing. The INI files are located in the first directory noted above. 4. Swapper file not shrinking Symptom: Swapper file does not dynamically deallocate itself as it should. Resolution: Reference APAR PJ03686. ================================================================= ==========APPLICATION/SOFTWARE PROBLEMS========================== ================================================================= 1. MicroSoft Word/PM Symptom: Unknown. Problem: Incompatible DLL causing problems on 2.0. Resolution: All registered users may call MicroSoft for the updated DLL. Phone number for MicroSoft: ? 3. Lotus 123 v2.3 and other DOS apps having EMS memory problems Symptom: DOS programs not seeing or even allowing OS/2 to allocate EMS memory. Problem: Same as above. Resolution: Send user new VEMM.SYS. This new file can be found on OS2TOOLS. Simply replace this file in the \OS2 directory and shutdown/reboot OS/2. 4. PMTape not functioning on PS/2's Symptom: Tape backup program PMTAPE not functioning correctly. Problem: Bad IBM2FLPY.ADD driver. Resolution: Interim IBM2FLPY.ADD fixed driver on OS2TOOLS. Copy new file over existing one. Not yet ready for customer distribution. For more info on the following applications see the OS/2 README file found in the root directory of OS/2 after installation is complete. o Ansel for Windows o Bound Checker (DOS) o Central Point Backup for Windows o Close-Up (Windows) o Desert Storm CD-ROM (Windows) o Distinct Back-Up (Windows) o DoDot 3.0 (Windows) o Fax Concentrator (DOS) o Magic-CV (DOS) o Mathematica 2.0 (Windows) o MusicPrinter Plus 4.0 (DOS) o OmniPage Professional 1.0 (Windows) o Oracle (DOS) (There is an OS/2 version of this program.) o Perceive for Windows o Realizer 1.0 (Windows) o Sherlock Holmes CD-ROM (DOS) o Smart Fax (DOS) o Soft-ICE (DOS) o Splash 1.01 (DOS) o Windows Multimedia Extension programs o Action! Sampler 1.0 (Windows) o Adobe Type Manager (Windows) o After Dark (Windows) o Aldus Pagemaker 4.0 (Windows) o Aldus Persuasion 2.0 (Windows) o Arts & Letters Graphics Editor 3.1 (Windows) o AutoCAD Version 10 (DOS) o AutoCAD (OS/2) o AutoManager 4.0 (DOS) o Borland C++ 2.0 (DOS) o Central Point Backup for DOS 7.1 (DOS) o Central Point PC Tools Deluxe 7.1 (Windows) o Commander Keen (DOS) o Control Room 1.0 (DOS) o CorelDRAW 2.0 (OS/2) o CorelDRAW 2.0 (Windows) o CorelDRAW 2.1 (Windows) o dBase IV 1.1 (DOS) o Designer (OS/2) o Drafix CAD Version 1.11 (Windows) o Drafix CAD Version 3.0 (Windows) o Dynacomm Asynchronous OS/2 (OS/2) o Enhanced Editor (OS/2) o F19 (DOS) o F-117A Stealth Fighter 2.0 (DOS) o Fastback Plus 2.1 and 3.04 (DOS) o FastLynx 1.1 (DOS) o FormBase 1.2 (Windows) o Form Publisher (Windows) o FotoMan (Windows) o Framework III 1.1 (DOS) o Harvard Graphics (Windows) o Harvard Draw (Windows) o hDC FileApps 1.0 (Windows) o HP New Wave 3.0 (Windows) o IBM 3363 Optical Disk Drive* o IBM PC/3270 V2.0* (DOS) o IBM PC/3270 V2.0* (Windows) o Intel SatisFAXtion o King's Quest (DOS) o LAN Support Program Device Drivers (DOS) o LANtastic 4.1 (DOS) o LapLink III 3.0 (DOS) o Linkway Mammals (DOS) o Linkway Presidents (DOS) o Lotus 123 for Windows 1.0 (Windows) o Lotus Freelance Graphics for OS/2 (OS/2) o Lotus Freelance Graphics for Windows (Windows) o Lotus Magellan 2.0 (DOS) o Lotus Notes (OS/2) o MagiCorp (Windows) o Mathcad 3.0 (Windows) o MicroProse Civilization (DOS) o Microsoft Bookshelf - CD-ROM Reference Library** (DOS/Multimedia) o Microsoft Chart 3.0** (DOS) o Microsoft Codeview** (DOS/OS/2) o Microsoft Codeview for Windows Version 3.0** (Windows) o Microsoft Excel for DOS 2.1** (DOS) o Microsoft Excel for OS/2 3.0** (OS/2) o Microsoft Excel for Windows 3.0** (Windows) o Microsoft Money 1.0** (Windows) o Microsoft QuickC** (Windows) o Microsoft Project for Windows 1.0** (Windows) o Microsoft Windows 3.0** (DOS) o More Windows (Windows) o National Geographics Mammals (DOS) o The Norton Backup 1.2 (DOS) o The Norton Desktop (Windows) o The Norton Utilities 5.0 (DOS) o PaintShow Plus 2.21 (DOS) o Paradox 3.5 (DOS) o Peachtree Complete III 5.0 (DOS) o Perform Pro 1.0 (Windows) o PFS: First Choice (DOS) o PFS: WindowWorks 1.75 (Windows) o Photostyler (Windows) o Publisher's PowerPak 2.1 (Windows) o Quattro Pro 3.0 (DOS) o Quicken (DOS) o Quicken for Windows (Windows) o Risk (DOS) o SantaFe Media Manager (DOS) o SideKick (OS/2) o Signmaster 5.11 (DOS) o Soft Term (OS/2) o SoundBlaster (DOS) o Space Quest IV (DOS) o SQLWindows 3.0 (Windows) o Turbo C++ 2.0 (DOS) o Turbo Debugger 2.01 (DOS) o Turbo Debugger for Windows (Windows) o Turbo Pascal 6.0 (DOS) o The Way You Work (DOS/Windows) o Windows Multimedia Extensions (Windows) o WINFAX PRO (Windows) o Wing Commander II (DOS) o WordPerfect for Windows (Windows) o WordPerfect Office 3.0 (DOS) o Xtree Pro Gold 2.0 (DOS)