OS/2 Shareware BBS: 14 Text

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

/ OS/2 Shareware BBS: 14 Text / 14-Text.zip / insin2.zip / 21INSTAL.INF

(.txt)

Wrap

OS/2 Help File | 1994-05-27 | 512KB | 19,912 lines

ΓòÉΓòÉΓòÉ 1. Introduction ΓòÉΓòÉΓòÉ Introduction Information current as of 5/27/94. The entries in this file are a compendium of installation difficulty reports and their solutions from IBM's Technical Support staff. These reports are specific to OS/2 2.1 and OS/2 For Windows 2.1. Many of these problems have been solved with the release of IBM's OS/2 2.11 refresh. In addition to the common/known problem entries, the last six entries in this file are: OS/2 2.1 README file OS/2 2.1 Special Edition for Windows README OS/2 2.1 Special Edition for Windows Installation README Personal OS/2 Beta 1 General README Personal OS/2 Beta 1 Installation README OS/2 2.11 manufacturing refresh README OS/2 2.11 ServicePak (XR06200) Installation README OS/2 for Windows ServicePak (XR06300) README updates OS/2 2.11 Documentation Updates They contain additional information about entries in this file. ΓòÉΓòÉΓòÉ 2. Problem reports, fixes, and work-arounds ΓòÉΓòÉΓòÉ Problem reports, fixes, and work-arounds Rather than reading the entire file, it is recommended that you use the Search capability of OS/2's on-line books on specific keywords, such as "COUNTRY.SYS" or "BIOS Upgrade" or "APAR". There are some known duplications of information in the file, but hopefully any errors or contradictions have been removed. ΓòÉΓòÉΓòÉ 2.1. Installation of OS/2 2.1 hangs after the first reboot, (DISK #5) ΓòÉΓòÉΓòÉ Installation of OS/2 2.1 hangs after the first reboot, (DISK #5) SUMMARY OF RESOLUTION: Workaround is to reinstall OS/2 2.1 using a Response file. DETAILS OF RESOLUTION: WARNING: All installation selections must be made in the Response file BEFORE the installation begins. 1. Copying the Response file to Diskette #1. a.To copy the response file onto a diskette, you must make some modifications to Diskette #1. These modifications make room on the diskette for the response file. b.Make a copy of Diskette #1. You will modify the copy.(Ex. DISKCOPY A: B:) c.Make extra room on the copy of Diskette #1 by deleting files that will not be needed in a response file installation: 1) Delete the MOUSE.SYS file from the copy of Diskette #1. 2) Delete the SYSINST2.EXE file from the copy of Diskette #1. 3) Delete the BUNDLE file from the copy of Diskette #1. 4) If you are installing OS/2 2.1 on a Micro Channel(*) computer, delete the following file from your copy of Diskette #1: DEL IBM1*.ADD 5) If you are installing OS/2 2.1 on a non-Micro Channel computer, delete the following files from your copy of Diskette #1: DEL IBM2*.ADD DEL *02.SYS d.Edit the CONFIG.SYS file that exists on the copy of Diskette #1. 1) Change the SET OS2_SHELL statement from: SET OS2_SHELL=SYSINST2.EXE to: SET OS2_SHELL=RSPINST.EXE A:\OS2SE21.RSP 2) Delete the following statement: DEVICE=\MOUSE.SYS 3) If you are installing OS/2 2.1 on a Micro Channel computer, delete the following statements from the CONFIG.SYS file on your copy of Diskette #1: BASEDEV=IBM1FLPY.ADD BASEDEV=IBM1S506.ADD 4) If you are installing OS/2 2.1 on a non-Micro Channel computer, delete the following statements from the CONFIG.SYS file on your copy of Diskette #1: BASEDEV=IBM2FLPY.ADD BASEDEV=IBM2ADSK.ADD BASEDEV=IBM2SCSI.ADD e.Unpack the SAMPLE.RSP from disk#13, This file is in directory REQUIRED. UNPACK A:REQUIRED /N:SAMPLE.RSP) to the copy of diskette #1. f.Use an editor (such as the System Editor) to modify and save the file. The file contains comments that explain each of the installation options.(Default setting has worked fine in all cases) g.Copy the modified response file to the copy you made of Diskette #1. Use the name OS2SE21.RSP when you copy the file: EX. COPY SAMPLE.RSP A:OS2SE21.RSP h.Copy the RSPINST.EXE file (located in DISK#7 under directory REQUIRED UNPACK A:REQUIRED /N:RSPINST.EXE) to the copy of Diskette #1. 2. Begin the installation of the workstation by inserting the Installation Diskette and restarting the system. 3. When prompted for Diskette #1, insert the modified copy of Diskette #1, and press Enter. 4. From this point, the installation program will prompt only for the insertion of diskettes. No other installation screens will appear. 5. When prompted to insert Diskette #1 again, insert the original copy of Diskette #1. NOTE This procedure can be used to install the same set of options on multiple workstations. Using a response file, you can make sure that a group of workstations is set up with the same set of options and HARDWARE. ΓòÉΓòÉΓòÉ 2.2. Cannot install OS/2 2.1 on an EISA system with an Adaptec 1742A. ΓòÉΓòÉΓòÉ Cannot install OS/2 2.1 on an EISA system with an Adaptec 1742A. SUMMARY OF RESOLUTION: Run the Setup Configuration Program provided with the Adaptec card Setup diskette and setup the card to the configuration described below. DETAILS OF RESOLUTION: Set up the Adaptec Card in the following configuration using the Setup Diskette that came with the controller. 1. Enhanced Mode to OFF 2. Standard Mode to ON 3. Hex Address to C800 4. I/O Port to 230H 5. DMA Channel to 5 6. Parity Check to OFF 7. Synchronous Negotiation to ON 8. Enabled Disconnect to YES 9. IRQ to 11 (default is 2) ΓòÉΓòÉΓòÉ 2.3. Problem w/XGA$DMQS during install ΓòÉΓòÉΓòÉ Problem w/XGA$DMQS during install Before installation of the OS/2 2.1 Upgrade, the line SET DMQSPATH=D:\XGA$DMQS was added to the CONFIG.SYS and the XGA$DMQS directory had been copied from C: to D:. When the Installation migrated the existing CONFIG.SYS the above line was deleted from the CONFIG.SYS and all the DMQS files were copied to the same partition as the base system. SUMMARY OF RESOLUTION: Add the line back to the new CONFIG.SYS and XCOPY the XGA$DMQS directory to D: DETAILS OF RESOLUTION: 1. Change the CONFIG.SYS a. Start an editor session. b. Open the OS/2 CONFIG.SYS. c. Add a line and type in SET DMQSPATH=D:\XGA$DMQS. d. Save the changes and exit the editor. 2. XCOPY the XGA$DMQS directory from C: to D:. a.Start an OS/2 session. b.Type XCOPY C:\XGA$DMQS D:\XGA$DMQS /S (then press enter) 3. Execute a proper shutdown and reboot the system. ΓòÉΓòÉΓòÉ 2.4. Problems installing OS/2 2.1 on system with a HYPERACE 486 upgrade. ΓòÉΓòÉΓòÉ Problems installing OS/2 2.1 on system with a HYPERACE 486 upgrade. DESCRIPTION OF SYMPTOMS: When the installation process prompts for Diskette 1 after pressing ENTER the diskette drive spins, trying to read the diskette, gives up and then displays the message Disk read error - please insert System disk. SUMMARY OF RESOLUTION: Disable the CACHE switches on the board itself. DETAILS OF RESOLUTION: 1. There are dip swithces on the Hyperace card that need to be disabled. a.Switch 1 is the main cache b.Switch 2 is the HIMEM cache c.Switch 4 is the BIOS cache 2. The main cache switch may be the only one needed to install but if the problem continues turn all the above off. 3. Consult the documentation that came with the card on the procedure for doing this. 4. After a successful installation the CACHES can be enabled by resetting the switches. ΓòÉΓòÉΓòÉ 2.5. TRAP 0002 on Model 8590 OR 8595 ΓòÉΓòÉΓòÉ TRAP 0002 on Model 8590 OR 8595 DESCRIPTION OF SYMPTOMS: Trap 0002 during installation of OS/2 2.X on a MODEL 8590, OR 8595. SUMMARY OF RESOLUTION: 1. Make sure SIMMS are not mismatched. 2. Check part numbers on the Microprocessor and Memory riser and check below to see if a new Engineering chages are needed. DETAILS OF RESOLUTION: 1. Ensure that the machines have matched pairs of single inline memory modules (SIMMS); they must be matched in size and speed. 2. If the computer is a 33 MHz system and the Microprocessor card part number is 84F9356, contact local IBM representative and request ECA053. 3. On the MODEL 90 if the Memory riser card is part number N33F4905 or 84F9356, contact local IBM representative and request ECA084. ΓòÉΓòÉΓòÉ 2.6. Horizontal Black bands across the screen after DISK 5 reboot ΓòÉΓòÉΓòÉ Horizontal Black bands across the screen after DISK 5 reboot Horizontal Black bands across the screen after DISK 5 reboot with the GATEWAY 2000 486/66 local bus and ATI Graphics Ultra Pro DESCRIPTION OF SYMPTOMS: During install on a Gateway 2000 486 66 with local bus and ATI Graphics Ultra Pro the system gets as far as the screen that shows the colorful OS/2 fullscreen symbol. The display then shows 5 or 6 horizontal bands of video separated by black bands. The bands scroll horizontally across the screen. SUMMARY OF RESOLUTION: Run the Setup program for the ATI card and set up the monitor as an IBM default. DETAILS OF RESOLUTION: 1. Boot DOS. 2. Change directories to MACH32 3. Type INSTALL then press enter. 4. At the Main Selection screen select SET POWER UP CONFIGURATION. 5. At the next screen select MONITOR TYPE. 6. The next screen should have the 1572 Monitor with 72hz refresh rate highlighted, press enter to select it. 7. Select IBM default as the new Monitor. 8. After successful installation repeat steps to reselect the 1572 Monitor. ΓòÉΓòÉΓòÉ 2.7. Disk Read error occurred when booting the Installation Diskette ΓòÉΓòÉΓòÉ Disk Read error occurred when booting the Installation Diskette DESCRIPTION OF SYMPTOMS: 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. Will produce the message, "Disk read error has occurred" when attempting to start the Installation diskette. SUMMARY OF RESOLUTION: Contact Future Domain for a BIOS upgrade ΓòÉΓòÉΓòÉ 2.8. SYS02025 AND SYS02027 on non-IBM Machines with AMI BIOS on Diskette #1. ΓòÉΓòÉΓòÉ SYS02025 AND SYS02027 on non-IBM Machines with AMI BIOS on Diskette #1. DESCRIPTION OF SYMPTOMS: During installation of OS/2 2.0 on OEM (Other Equipment Manufacturers) machines with AMI BIOS, the system will display two SYS error messages 02025 and 02027 after inserting Disk 1. SUMMARY OF RESOLUTION: 1. Make sure disk 1 is not bad. 2. Check the AMI BIOS date and Keyboard Controller Chip version. The date should be 5/9/91 and Controller Chip version should be F. 3. Ensure that there is not a hardware problem with the Floppy Controller or Floppy Drive. DETAILS OF RESOLUTION: 1. Try booting with the Disks on another machine that is already running OS/2 2.0. 2. Machine must have BIOS dated 5/9/91 and keyboard controller chip version KF. The following information will be seen by the user at (cold)boot time: AMI BIOS and AMI BIOS Plus: aaaa-bbbb-mmddyy-Kc AMI Hi-Flex BIOS: ee-ffff-bbbbbb-gggggggg-mmddyy-hhhhhhhh-c If an IDE hard drive is in the system, "mmddyy" should be 040990 or later. For other drives including MFM, RLL, ESDI, or SCSI, "mmddyy" should be 092588 or later. Controller chip version can be located on the bottom of that same screen. Check the last digit in the long stream of digits (the "c" above). The last digit will probably be either be 8, B, D, or F. The required level should be F for OS/2 v2.0 or v1.3. Pressing the INS key during bootup should cause thisinfo to stay on the screen. If they are not up to date Call Washburn & Co. to order a new version. 3. If the above two steps do not solve the problem have some hardware diagnostics performed on the Floppy Controller and Floppy Drive. ΓòÉΓòÉΓòÉ 2.9. COUNTRY.SYS error message on Boot-Up. ΓòÉΓòÉΓòÉ COUNTRY.SYS error message on Boot-Up. AMI Fast Disk and Fast Disk II SCSI adapters are recognized as ADAPTEC Adapters, gives COUNTRY.SYS error message on Boot-Up. DESCRIPTION OF SYMPTOMS: Country.sys cannot be found error message on boot up, using an AMI Fast Disk or Fast Disk II SCSI Adapters. SUMMARY OF RESOLUTION: 1. 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). 2. Ensure the line, "BASEDEV=IBMINT13.I13," appears in the CONFIG.SYS file. DETAILS OF RESOLUTION: 1. Boot DOS or from a DOS Bootable Diskette with a text editor on it. 2. Start the Editor and edit the OS/2 CONFIG.SYS. 3. Delete any line that references an Adaptec Driver. ie. any line with a reference to AHA1xxx.ADD (where xxx can be any character) 4. Ensure that the line BASEDEV=IBMINT13.I13 is present. If not add the line. 5. Save any changes and exit the editor. 6. Remove any disks from drive A, and Boot OS/2. ΓòÉΓòÉΓòÉ 2.10. Installation hangs on Disk #1. ΓòÉΓòÉΓòÉ Installation hangs on Disk #1. DESCRIPTION OF SYMPTOMS: Installation hangs on disk 1 of the installation process with the loading please wait message showing. SUMMARY OF RESOLUTION: Turn off disk caching, asynchronous memory refresh capabilities, turbo and shadowing, during the installation. These can be turned back on after a successful install. DETAILS OF RESOLUTION: The disk caching,async memory refreshes, and shadowing are enabled and disabled in the CMOS setup of the BIOS. The turbo is sometimes put on a switch on the casing of the computer or can also be set from the CMOS. Enter the setup utility and make the appropriate changes; consult the documentation that came with the computer on how to enter and change the setup. ΓòÉΓòÉΓòÉ 2.11. Hang on Disk #1 of Installation: Will not draw the OS/2 LOGO screen ΓòÉΓòÉΓòÉ Hang on Disk #1 of Installation: Will not draw the OS/2 LOGO screen DESCRIPTION OF SYMPTOMS: On systems that have video cards with a Western Digital Chipset, the installation will hang on disk 1 before the OS/2 logos are displayed. SUMMARY OF RESOLUTION: Video card may be set for a non-standard VGA mode, or autosense capability on the card is turned on. DETAILS OF RESOLUTION: 1. Make sure video card is in VGA mode with auto-sense turned off. 2. Try setting the video card to 8 bits and moving the video card to an 8-bit slot . ΓòÉΓòÉΓòÉ 2.12. Hang on Disk #1 while installing on a system with a QUANTUM HARD CARD ΓòÉΓòÉΓòÉ Hang on Disk #1 while installing on a system with a QUANTUM HARD CARD DESCRIPTION OF SYMPTOMS: While installing OS/2 2.1 on a system with a Quantum Hard Card the installation process will hang on Disk #1. SUMMARY OF RESOLUTION: 1. Modify the CONFIG.SYS on Diskette #1 of the OS/2 installation diskettes and add the default settings for the Quantum hard card to the BASEDEV=IBM1S506.ADD line. 2. The line should read as follows after editing. BASEDEV=IBM1S506.ADD /A:1 /IRQ:11 DETAILS OF RESOLUTION: 1. Make a Backup copy of Diskette #1 and use the copy for the following steps. 2. Boot the system with DOS or a DOS bootable diskette. 3. Insert the copy of Diskette #1 in Drive A: 4. Edit the CONFIG.SYS on the copy of Diskette #1. 5. Locate the BASEDEV=IBM1S506.ADD line. 6. Add /A:1 /IRQ:11 to the end of the line. 7. The edited line should now look like BASEDEV=IBM1S506.ADD /A:1 /IRQ:11 8. Save the changes and remove the diskette from Drive A: 9. Begin installation of OS/2 2.1 using the copy of Diskette #1 when asked to insert Diskette #1. ΓòÉΓòÉΓòÉ 2.13. Slow SCSI support or missing Icons on boot-up ΓòÉΓòÉΓòÉ Slow SCSI support or missing Icons on boot-up DESCRIPTION OF SYMPTOMS: Slow SCSI support and bad or missing icons after installation of OS/2 2.0. Also other data corruption may occur. SUMMARY OF RESOLUTION: Ensure that hard drive and card are matched in their settings of SYNCH and ASYNCH mode. DETAILS OF RESOLUTION: Consult the documentation for the Hard drive and controller card to make sure that the controller and drive and either both set for asynch mode or synch mode. ΓòÉΓòÉΓòÉ 2.14. Installation Diskette or DISK 1 hangs during install on a PS/2 MOD 80 ΓòÉΓòÉΓòÉ Installation Diskette or DISK 1 hangs during install on a PS/2 MOD 80 DESCRIPTION OF SYMPTOMS: OS/2 V2.1 hangs on Disk #1 or Installation Disk on MOD 8580. SUMMARY OF RESOLUTION: Copy the packed file BUNDLE on Disk 1 to another location on the diskette. DETAILS OF RESOLUTION: 1. If you have two diskette drives a. Insert a DOS bootable diskette in drive A and start the computer (if the computer is already running, you can restart it by pressing Ctrl+Alt+Del). b. Place a blank diskette in drive B. This diskette will become the replacement OS/2 diskette #1. c. At the DOS A> prompt, type: FORMAT B: /v (then press enter) e. When asked for a volume label type: DISK 1 (then press enter) f. When asked if you want to format another, type: N (then press enter) g. Remove the replacement OS/2 diskette #1 from drive B h. Insert the original OS/2 diskette #1 into drive B i. At the DOS A> prompt, type: XCOPY B: A: /p J. At the first (Y/N)? prompt, remove the DOS diskette from drive A and place the replacement OS/2 diskette #1 in drive A K. At the B:BUNDLE(Y/N)? prompt, type: N (then press enter) L. For all other (Y/N)? prompts, type: Y (then press enter) M. When the DOS A> prompt appears, type COPY B:BUNDLE A: (then press enter) 2. If you have one diskette drive a. Insert a DOS bootable diskette in the diskette drive and start the computer (if the computer is already running, you can restart it by pressing Ctrl+Alt+Del). b. At the DOS A> prompt, type: FORMAT B: /v (then press enter) c. When prompted, place a blank diskette in the diskette drive. This diskette will become the replacement OS/2 diskette #1. d. When asked for a volume label type: DISK 1 (then press enter) e. When asked if you want to format another, type: N (then press enter) f. When prompted to insert diskette for drive A, remove the replacement OS/2 diskette #1 from the diskette drive and place the DOS diskette in the diskette drive g. At the DOS A> prompt, type: DISKCOPY A: B: (then press enter) When prompted to insert SOURCE diskette in drive A:, place the original OS/2 diskette #1 in the diskette drive When prompted to insert TARGET diskette in drive B:, place a blank diskette in the diskette drive. This diskette will become the temporary copy of diskette #1 h. When asked if you want to copy another diskette, type N (then press enter) i. When prompted to insert disk with command.com in drive A, place the DOS diskette in the diskette drive. k. At the DOS A> prompt, type: ERASE B:BUNDLE (then press enter) When prompted to insert diskette for drive B:, place the temporary copy of diskette #1 in the diskette drive. When prompted to insert diskette for drive A:, place the DOS diskette in the diskette drive. l. At the DOS A> prompt, type: XCOPY B: A: (then press enter) When prompted to insert diskette for drive B:, place the temporary copy of diskette #1 in the diskette drive When prompted to insert diskette for drive A:, place the replacement OS/2 diskette #1 in the diskette drive m. When prompted to insert disk with command.com in drive A, place the DOS diskette in the diskette drive. n. When the DOS A> prompt appears, type XCOPY B:BUNDLE A: When prompted to insert diskette for drive B:, place the original OS/2 diskette #1 in the diskette drive When prompted to insert diskette for drive A:, place the replacement OS/2 diskette #1 in the diskette drive ΓòÉΓòÉΓòÉ 2.15. DISK READ ERROR MESSAGE ON DISK 1 ΓòÉΓòÉΓòÉ DISK READ ERROR MESSAGE ON DISK 1 During Installation of OS/2 2.1, the floppy drive will begin to rapidly seek back and forth then give a DISK READ ERROR MESSAGE ON DISK 1 DESCRIPTION OF SYMPTOMS: 1. At disk1 after the logo shows up, the floppy drive starts seeking rapidly back and forth, the screen clears and "A disk read error has occured. Restart the system." message appears. 2. This is known to happen on systems with AOX, HYPER ACE, and XTEND processor upgrade cards. SUMMARY OF RESOLUTION: 1. The cause of this error is a file on disk 1 called BUNDLE, size 344132. 2. Moving the position where this file resides on the disk 1 is known to fix the problem. DETAILS OF RESOLUTION: 1. Insert a DOS bootable diskette in the diskette drive and start the computer (if the computer is already running, you can restart it by pressing Ctrl+Alt+Del). 2. At the DOS A> prompt, type: FORMAT B: /v (then press enter) 3. When prompted, place a blank diskette in the diskette drive. This diskette will become the replacement OS/2 diskette #1. 4. When asked for a volume label type: DISK 1 (then press enter) 5. When asked if you want to format another, type: N (then press enter) 6. When prompted to insert diskette for drive A, remove the replacement OS/2 diskette #1 from the diskette drive and place the DOS diskette in the diskette drive 7. At the DOS A> prompt, type: DISKCOPY A: B: (then press enter) When prompted to insert SOURCE diskette in drive A:, place the original OS/2 diskette #1 in the diskette drive When prompted to insert TARGET diskette in drive B:, place a blank diskette in the diskette drive. This diskette will become the temporary copy of diskette #1 8. When asked if you want to copy another diskette, type N (then press enter) 9. When prompted to insert disk with command.com in drive A, place the DOS diskette in the diskette drive. 10. At the DOS A> prompt, type: ERASE B:BUNDLE (then press enter) When prompted to insert diskette for drive B:, place the temporary copy of diskette #1 in the diskette drive. When prompted to insert diskette for drive A:, place the DOS diskette in the diskette drive. 11. At the DOS A> prompt, type: XCOPY B: A: (then press enter) When prompted to insert diskette for drive B:, place the temporary copy of diskette #1 in the diskette drive When prompted to insert diskette for drive A:, place the replacement OS/2 diskette #1 in the diskette drive 12. When prompted to insert disk with command.com in drive A, place the DOS diskette in the diskette drive. 13. When the DOS A> prompt appears, type XCOPY B:BUNDLE A: When prompted to insert diskette for drive B:, place the original OS/2 diskette #1 in the diskette drive When prompted to insert diskette for drive A:, place the replacement OS/2 diskette #1 in the diskette drive ΓòÉΓòÉΓòÉ 2.16. Install hangs with an Internal Processing Error ΓòÉΓòÉΓòÉ Install hangs with an Internal Processing Error IPE AT 0F00:7275 ON DISK 1 OF OS/2 2.1 INSTALL, OR IPE AT 0F00:76A1 ON DISK 1 OF OS/2 2.0 INSTALL ON ROM LOADABLE MACHINES DESCRIPTION OF SYMPTOMS: 1. When trying to install OS/2 2.0 GA the installation program hangs on Install Disk 1 with an Internal Processing Error at ## 0F00 : 76A1 60000, 6000 Internal Revision 6.307 2. When trying to install OS/2 2.1 GA the installation program hangs on Install Disk 1 with an (Only in thinkpad 700C installing from cdrom attached to Docking Station.) Internal Processing Error at ## 0F00 : 7275 60000, 6000 Internal Revision 6.427 This error could be the same for machines that are currently running a. OS/2 2.0's preload code b. OS/2 2.0's 10/92 Service Pak I c. OS/2 2.1 but are missing the necessary ABIOS files; NOTE Also that it is NOT recommended to install OS/2 2.1 on top of an beta version of OS/2 2.1. 3. Occurs on a ROM loadable machine such as an IBM Model 9556 or 9557. SUMMARY OF RESOLUTION: Copy the .BIO file from the Reference Disk onto copies of the Installation Disk and Disk 1 then update the ABIOS.SYS files on these disks and use the copies for the install. This is known as the ABIOS workaround. DETAILS OF RESOLUTION: 1. Using DISKCOPY command make backup diskettes for OS/2 2.0 Installation Disk and Disk 1. It is very important that these backups are used for rest of the procedure. 2. Locate a file xxxx.BIO on the reference disk of your PS/2 or PS/VALUEPOINT. (If you don't have the reference disk then follow instructions that came with the machine to create one). 3. Copy this xxxx.BIO to INSTALL and DISK_1 diskettes. 4. Using a plain text editor, edit the file ABIOS.SYS on the INSTALL diskette and add a line, stating the name of the xxxx.BIO as in step 3, to the FIRST LINE of the file. Make sure that you you use the same format as used for other lines in this file. 5. Copy this modified ABIOS.SYS to the DISK_1. 6. Using these two modified disks the installation will continue beyond Disk 1. 7. This procedure is the same for OS/2 2.0 and OS/2 2.1. ΓòÉΓòÉΓòÉ 2.17. TRAP D on Disk #1 during Installation of OS/2 2.1 on a COMPAQ 386/33 DESKPRO ΓòÉΓòÉΓòÉ TRAP D on Disk #1 during Installation of OS/2 2.1 on a COMPAQ 386/33 DESKPRO DESCRIPTION OF SYMPTOMS: Trap 000D on Disk 1 during install of OS/2 2.1 on a Compaq 386/33I Deskpro. CS:EIP=0538:00003823. SUMMARY OF RESOLUTION: 1. Make a copy of Disk #1 2. Using this copy and an editor, edit the CONFIG.SYS file on the copy of Disk #1 as follows: REM OUT: BASEDEV=IBM2M57.ADD BASEDEV=IBM2SCSI.ADD 3. Use the edited copy of Disk #1 to install. ΓòÉΓòÉΓòÉ 2.18. After Install, Blank Desktop and No System Activity ΓòÉΓòÉΓòÉ After Install, Blank Desktop and No System Activity DESCRIPTION OF SYMPTOMS: After Installation and reboot the user gets a blank desktop with no system activity SUMMARY OF RESOLUTIONS: 1. If Using an ATI Ultra, or Ultra Graphics. a. Ensure the ATI board is setup as an 8514 PRIMARY display. b. Check the CONFIG.SYS for DEVICE=C:\OS2\MDOS\VSVGA.SYS c. Contact ATI for updated ROM chip. 2. Run chkdsk 3. Check CONFIG.SYS for duplicate SET USER_INI, and SET SYSTEM_INI statements. 4. Set video card to 8 bits and move it to an 8 bit slot. 5. If the above is not applicable or does not work, remake the desktop. DETAILS OF RESOLUTION: 1. The ATI 8514 Ultra, or Ultra Graphics. a. These boards MUST be set up as an 8514 PRIMARY display b. The correct DEVICE statement in the CONFIG.SYS should read DEVICE=X:\OS2\MDOS\VSVGA.SYS It will sometimes install as VVGA.SYS This must be changed. c. The older ATI ROM chips return the incorrect monitor ID when queried by OS/2. 2. Run Chkdsk a. Insert the Installation disk in drive A. b. Turn on the computer; if already on execute a proper shutdown and when prompted press Ctrl+Alt+Del. c. When prompted insert disk 1 and press enter. d. When the welcome to OS/2 screen is displayed hit the esc key to cancel and an A: prompt will appear. e. Insert disk2 and type chkdsk c: /f and press enter. f. If errors are displayed rerun the command until no errors are found. g. Run this command on all drive letters that exist. 3. Check the OS/2 CONFIG.SYS for duplicate INI statements. a. Boot from DOS or a DOS BOOTABLE DISKETTE. b. Open an editor session. c. Open the CONFIG.SYS. d. Locate the SET USER_INI, and SET SYSTEM_INI statements. e. Scroll through the CONFIG.SYS and make sure they are not repeated. If they are delete the second occurrence. f. Save any changes and exit the editor. 4. Set the Video card to 8 bit mode and place in an 8 bit slot. Consult the documentation that came with the card on the procedure to do this. 5. Remake the desktop. a. Restart the computer using the OS/2 Installation Diskette, then when prompted insert Diskette 1. b. When the Welcome To OS/2 screen appears press the Esc key to cancel the installation. c. At the A:> prompt type C: then press enter. d. Type CD \OS2 the press enter. e. Type ERASE OS2.INI then press enter. f. Type MAKEINI OS2.INI INI.RC then press enter. g. Type ERASE OS2SYS.INI then press enter. h. Type MAKEINI OS2SYS.INI INISYS.RC then press enter. i. Delete the hidden file WP ROOT. SF in the startable partition. 1) For FAT file systems i. Type ATTRIB -S -H WP?ROOT.?SF then press enter ii. Type DEL WP?ROOT.?SF then press enter 2) For HPFS file systems i. Type ATTRIB -S -H "WP ROOT. SF" press enter ii. Type DEL "WP ROOT. SF" then press enter j. Delete the desktop 1) For FAT CD to OS!2_2.0_D and delete this directory and all subdirectories under it. 2) For HPFS CD to "OS!2 2.0 DESKTOP" and delete this directory and all subdirectories under it. NOTE: If MAKEINI has been run before, or ALT-F1 was used, other desktops may have been created. Delete ALL desktops. (e.g. OS!2_21.0_D is another desktop.) ΓòÉΓòÉΓòÉ 2.19. Installing OS/2 2.1 on a machine with an AOX/KINGSTON upgrade ΓòÉΓòÉΓòÉ Installing OS/2 2.1 on a machine with an AOX/KINGSTON upgrade DESCRIPTION OF SYMPTOMS: Cannot install OS/2 2.1 on a machine with a 286 CPU upgraded to a 386SX with an AOX upgrade. SUMMARY OF RESOLUTION: Boot real DOS and run AOX232.EXE that can be obtained from AOX'S BBS or Technical Support group. DETAILS OF RESOLUTION: 1. Download AOX232.EXE from AOX'S BBS (617) 890-3393 or call the AOX Technical Support group(800-232-1269) and request it. 2. Boot the machine from DOS or a DOS bootable diskette. 3. Insert the disk with AOX232.EXE in drive A: 4. This needs to be run every time before installation of OS/2 2.1 5. Remove the disk from drive A and insert the OS/2 2.1 Installation diskette in drive A and press Ctrl + Alt + Del to reboot the system and restart the installation. ΓòÉΓòÉΓòÉ 2.20. TRAP 2 OR TRAP 6 at 60000X:9084 during install ΓòÉΓòÉΓòÉ TRAP 2 OR TRAP 6 at 60000X:9084 during install DESCRIPTION OF SYMPTOMS: Trap 2, Trap 6 or other Trap at 60000x:9084. SUMMARY OF RESOLUTION: 1) Disable cache during (Esp. Phoenix BIOS) 2) Turn turbo switch off. 3) Always IN2000 SCSI 4) Disable Shadows 5) Mismatch Memory 6) Old 8590 and 8595with N33f4905 or 84f9356 needs ECA084 or ECA053. DETAILS OF RESOLUTION: 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). 1. Make sure that all the simms in the machine are the same speed, type, and manufacturer. 2. Run memory checking diagnostics on the simms to ensure they are not bad. ΓòÉΓòÉΓòÉ 2.21. System asks for DISK 16 but there are only 15 disks plus the printer driver disks ΓòÉΓòÉΓòÉ System asks for DISK 16 but there are only 15 disks plus the printer driver disks DESCRIPTION OF SYMPTOMS: The installation of OS/2 2.0 goes fine up to disk 15 but then the system prompts for disk 16, the problem is there are only disks 0-15 for installation and the printer driver diskettes. SUMMARY OF RESOLUTION: This problem usually occurs on systems which have had the A: and B: drives switched because OS/2 has to install from drive A: but drive A: was a 5.25 inch drive and the install disks are 3.5 inch. The drive cables must be physically switched and the CMOS setup has to be updated as to the new configuration. DETAILS OF RESOLUTION: Go inside the machine and swap floppy drive cable connectors, use the 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 an adapter plug can be obtained. ΓòÉΓòÉΓòÉ 2.22. TRAP 8 on installation DISK # 1 on MYLEX systems ΓòÉΓòÉΓòÉ TRAP 8 on installation DISK # 1 on MYLEX systems DESCRIPTION OF SYMPTOMS: Trap 8 on Disk 1 of installation on MYLEX systems. CS:EIP 0160 : FFF63898 IPE at ##0160:FFF6345F - 0008:A53F SUMMARY OF RESOLUTION: This is a known problem with MYLEX systems which they are aware of. For a fix contact MYLEX systems. ΓòÉΓòÉΓòÉ 2.23. SYS 0045 during install. ΓòÉΓòÉΓòÉ SYS 0045 during install. Getting a SYS0045 Cannot find sector requested on D drive on disk1 of installation. If you run an OS2 CHKDSK on the drive it returns SYS1336 & SYS1374 File Allocation Table is bad on drive D. Use pc tools or norton disk editor to edit the boot record. There was a line in the boot record which said OEMID was pcformat, since it had been formatted with pctools. He changed that to IBM 5.0, and that solved the problem. Do not have to reformat. ΓòÉΓòÉΓòÉ 2.24. COUNTRY.SYS not found ΓòÉΓòÉΓòÉ COUNTRY.SYS not found COUNTRY.SYS error message at bootup of first two diskettes or after first five diskettes, and reboot of machine by installation program. 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. ΓòÉΓòÉΓòÉ 2.25. Installing on TI Notebooks (TI4000/30, /40/& 50's.) ΓòÉΓòÉΓòÉ Installing on TI Notebooks (TI4000/30, /40/& 50's.) The install work around for the TI notbook/Laptops is as follows. Goto CMOS Advanced settings. 1. Power Savings=Off 2. Time Out Interval=On 3. HDmotor Timeout=On 4. LCD Power=Low 5. Advanced OS Power=Off 6. External cache=Off 7. Turbo=Off. Note all settings can be set back to normal after the install has completed. The Power savings switch in the TI4000/33 is not compatible with OS2 2.1 power management software, and should not be used. ΓòÉΓòÉΓòÉ 2.26. SYS 2025 & 2027 on the installation ΓòÉΓòÉΓòÉ SYS 2025 & 2027 on the installation Getting sys02025 and sys02027 on the install diskette. Check if customer swapped their floppy drives without updating their cmos. Setting the cmos correctly allowed them to install without getting the sys02025 and sys02027. This is different from 2.0 where it allowed you to install and then asked for a nonexistent diskette 16 at the end. ΓòÉΓòÉΓòÉ 2.27. SYS 2025 & 2027 on the installation with PHOENIX BIOS ΓòÉΓòÉΓòÉ SYS 2025 & 2027 on the installation with PHOENIX BIOS If you get a cust. with a 2025 & 2027 with the phoenix bios 1.03 m series,the cust. needs to do the following: 1) Make a copy of the installation disk 2) Rename the os2boot to os2bllt on the new install disk 3) Delete the os2ldr from the new instl disk 4) Delete the os2ldr.msg from the new installation disk 5) Copy the os2boot from the orignal installation disk to the copy the cust. made. 6) Copy the os2ldr from the orginal installation to the install disk the cust. made. 7) Copy the os2ldr.msg from the orginal installation disk to the install disk the cust. made. 8) Then reboot the system using the installation disk the cust. made. ΓòÉΓòÉΓòÉ 2.28. AST machine, COUNTRY.SYS not Found ΓòÉΓòÉΓòÉ AST machine, COUNTRY.SYS not Found AST machine and has added 3rd party memory to it he may encounter an error on install of 2.1, country.sys not found. The explanation from AST is that the new 486 Notebook is designed for 3.3V memory modules and currently the 3rd party memory modules are 5.5V. ΓòÉΓòÉΓòÉ 2.29. Installation failure on 700C ΓòÉΓòÉΓòÉ Installation failure on 700C Receiving a sys0005 on the install disk after disk5 and would reference the WPHELP.HLP file. Can not get past install disk. Copy the ABIOS.SYS from the Thinkpad Reference onto the install and disk1. ΓòÉΓòÉΓòÉ 2.30. Hangs and SYS 3175's during selective installs. ΓòÉΓòÉΓòÉ Hangs and SYS 3175's during selective installs. There is a potential workaround to the problem of hangs and SYS 3175's during selective installs. The workaround is to rename the \os2\drivers\fd16-700.exe to \os2\drivers\fd16-700.bak. ΓòÉΓòÉΓòÉ 2.31. How to add dual-boot AFTER OS/2 installation ΓòÉΓòÉΓòÉ How to add dual-boot AFTER OS/2 installation Did not select dual boot option when installing OS/2, and now want to add it. Can I do so without having to install DOS and then reinstall all of OS/2? *** This answer applies to OS/2 versions 1.3 and 2.X *** You do not need to reinstall OS/2 in order to get the dual boot feature. If you are using OS/2 2.0, get from OS2EWS the DBPREP package. This package is: A utility to allow DOS 4.0, DOS 5.0, and DR DOS to be installed as a dualboot function on top of OS/2 2.0, and recover to OS/2 in case something goes wrong during the DOS install. ΓòÉΓòÉΓòÉ 2.32. Problem installing on some PS/2 Model 80 ESDI systems ΓòÉΓòÉΓòÉ Problem installing on some PS/2 Model 80 ESDI systems There is a problem installing OS2 2.1 on some PS2 8580, ESDI units. These units will install and run with OS2 2.0 but with 2.1 you cannot get past disk 1 of install set Make a DISKCOPY of install disk 1. Delete the BUNDLE file from copy of disk 1. Format a new disk and label it "DISK 1". XCOPY the files from disk 1 copy to new disk. Copy the BUNDLE file from real disk 1 to new disk. Use the new disk for installation in place of disk 1. To speed things up, you can XCOPY files to a hard disk. ΓòÉΓòÉΓòÉ 2.33. BIOS was not compatible error message during install ΓòÉΓòÉΓòÉ BIOS was not compatible error message during install Installing OS/2 2.1 on a 486 machine. Error msg that states that "the BIOS was not compatible". If the manufacturer of the opti-chip is Award, they will passed you to company called Pinnacle Sales. This company sells an upgrade chip that is compatible with OS/2. It costs $59.00. Pinnacle Sales:(408)453-7500. ΓòÉΓòÉΓòÉ 2.34. Selective Install fails ΓòÉΓòÉΓòÉ Selective Install fails There is a new fix available out on the IBM NSC BBS. It is call OS2CCP and might be a solution for anyone having problems with Selective Install. Here is the description: Starting in late June, OS/2 2.1 began shipping a reduced diskette package to take advantage of better diskette compression techniques. These diskettes are salmon in color (the original package contained blue diskettes.) Because the layout of the diskettes is different for the two packages, the enclosed CMD files will need to be run to allow selective installs to work correctly if the installation package is different from the package that is currently available to you. This diskette contains files which are to be used to alter the user's system to accommodate the other OS/2 package. This procedure is to be used only in those situations in which a user has a mismatch. If you are not sure if you have a mismatch, run the CHECK.CMD file to determine which version and type of package is installed. See the README file for more details. ΓòÉΓòÉΓòÉ 2.35. Installation failures on Gateway machines ΓòÉΓòÉΓòÉ Installation failures on Gateway machines Gateway has released ADVOSOF.exe for OS2 installations. This file Disables all the power saver features and disables all caches and turns the turbo mode off. Gateway has this file on their BBS in the OS2/NoMAD drivers file area. Gateway's tech support recommends this file for both OS2 and Windows NT install Preperation. ΓòÉΓòÉΓòÉ 2.36. Enabling CACHE after having to disable CACHE for installation ΓòÉΓòÉΓòÉ Enabling CACHE after having to disable CACHE for installation OS/2 trapping when you renable the shadow ram, cache and turbo after installing. Accel, the manufacturer of the motherboard and found out that if you go into the cmos advanced system settings and the A20 Gate Handler is disabled it will cause os/2 2.1 to trap when turning the shadow ram, cache and turbo back on. When the customer set the A20 Gate Handler to enabled os/2 no longer trapped. ΓòÉΓòÉΓòÉ 2.37. Installing OS/2 with 4M RAM and UNPACK2.EXE and using CDROM during install. ΓòÉΓòÉΓòÉ Installing OS/2 with 4M RAM and UNPACK2.EXE and using CDROM during install. Editing the config.sys on disk #1 (create partition before the procedure) change " memman=swap " and add " swappath=c:\ 64 1024 " and rem all unwanted basedev. Boot up from disk and go through install. After booting on os/2 edit the config.sys and rem statement that was added on the disk #1 in config.sys "memman and swappath " as well as any incorrect one. NOTE: For disk install adding swap might not be necessary. ΓòÉΓòÉΓòÉ 2.38. Installing on a DPT SCSI Controller, TRAP 0008 ΓòÉΓòÉΓòÉ Installing on a DPT SCSI Controller, TRAP 0008 DPT SCSI controller and were getting a trap 0008 on diskette #1. Set the interrupt from 15 level to 15 edge upgrade the eprom to 5C ΓòÉΓòÉΓòÉ 2.39. SYSTEM CANNOT FIND THE FILE KBD01.SYS ΓòÉΓòÉΓòÉ SYSTEM CANNOT FIND THE FILE KBD01.SYS "SYSTEM CANNOT FIND THE FILE KBD01.SYS" ERROR MESSAGE ON BOOT UP AFTER A SUCCESSFUL INSTALL On a system with a Micropolis SCSI 1 gig harddrive the user is getting "system cannot find the file KBD01.SYS this driver program or data file is not located in the default path or the path specified for it not in the config.sys file. Install this file in the correct directory or the appropriate config.sys file statement." Upon checking the CONFIG.SYS the correct statements are there and the file is located in the correct place on the harddrive. Workaround: Disable the "Read ahead cache" on the Micropolis Drive. There is a utility on the Micropolis BBS called UTIL.EXE which will allow the user to disable the "Read ahead cache" on the Micropolis 1 GB Drive Model 2112. ΓòÉΓòÉΓòÉ 2.40. Greater then 16 MB in MOD 80 will not install 2.1 ΓòÉΓòÉΓòÉ Greater then 16 MB in MOD 80 will not install 2.1 Fix: The trick is to get the correct RAM init code installed on the hard drive using the Reference Diskette. This requires a modified FDDF.ADF file and EMO option diskette level 1.3. You can also remove the EMO card for the installation if you have 4 meg on the planer. ΓòÉΓòÉΓòÉ 2.41. Installing OS/2 2.x on top of Lan Server 3.0 with HPFS386 ΓòÉΓòÉΓòÉ Installing OS/2 2.x on top of Lan Server 3.0 with HPFS386 1. Use the BACKACC command to back up all access control profiles on the drive containing OS/2 (e.g. BACKACC C:\ /S) 2. Use the NET command to delete all access control profiles for the drivce containing OS/2 3. Reboot from the ServicePak diskettes and install the service pack 4. On restart after installing the ServicePak, restart the server and use RESTACC to restore the access control profiles saved above (e.g. RESTACC C:\ /s) 5. At this point access control profiles should be reset as they were before. If the Service program still fails to find the SYSLEVEL files on reboot, I would suggest making sure that all directories have the ARCHIVE attribute bit removed before continuing. This can be done using the ATTRIB command. ΓòÉΓòÉΓòÉ 2.42. Hang with White screen after installation with no system activity: ΓòÉΓòÉΓòÉ Hang with White screen after installation with no system activity: * There is a fix available on Compuserve and the IBM NSC BBS for the following problems in a file called 21WPSF.ZIP. 1. White desktop after installing OS/2 2.1 over another version of OS/2. 2. "shutdown complete" message is displayed underneath the "shutting down please wait" message. 3. Mass duplication of template objects after creating a shadow. If you have the white desktop with the environment noted above it is recommended to get the 21WPSF.ZIP fix from Compuserve or the BBS. If however you do not have access to a modem the following workarounds have had a high success rate. 1) Do CHKDSK x: /f (for FAT ) CHKDSK x: /f:3 (for HPFS) on OS/2 Partition from OS/2 Installation diskettes. See Page 137 in the "Installation Guide for instructions on how to run CHKDSK. 2) Check the OS/2 CONFIG.SYS file on the root directory for the following 2 statements. If you have more than one set of these two statements, REM out the first set in the config.sys file. SET USER_INI=C:\OS2\xxxxx.INI SET SYSTEM_INI=C:\OS2\xxxxxx.INI If you do have two sets, EDIT the CONFIG.SYS with any EDITOR by either copying the file to a diskette and editing on another machine or boot up with a DOS diskette and Run EDIT or EDLIN to "REM" out the duplicate set of SETUSER and SETSYSTEM lines. (e.g. REM USER_INI=C:\OS2\xxxxx.INI) ΓòÉΓòÉΓòÉ 2.43. Black Desktop ΓòÉΓòÉΓòÉ Black Desktop 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. Contact the manufacturer or hardware technical literature for instructions if necessary. ΓòÉΓòÉΓòÉ 2.44. If ATI 8514 Ultra or Graphics Ultra locks with white screen on bootup. ΓòÉΓòÉΓòÉ If 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. Call ATI at 416-882-2626 to obtain an update. Remember, these boards MUST be set up as an 8514 PRIMARY display and the statement DEVICE=C:\OS2\MDOS\VVGA.SYS MUST be changed to DEVICE=\OS2\MDOS\VSVGA.SYS ΓòÉΓòÉΓòÉ 2.45. TRAP 0002 on IBM 8590, 8595 ΓòÉΓòÉΓòÉ TRAP 0002 on IBM 8590, 8595 If you are experiencing problems with a Model 90 or 95, ensure the system is at the latest engineering change (EC) level. Call 1-800-IBM-SERV if the following conditions are met. If the Model 90 or 95 is a 33 MHz system and you are having intermittent difficulty identifying memory parity errors such as TRAP 0002, forcing you to restart the system, then ECA053 might apply. If the microprocessor card has part number 84F9356, contact IBM representative to assist you with a replacement. If the Model 90 is experiencing intermittent memory errors, ECA084 might apply if the part number of memory riser card is N33F4905 or 84F9356. Contact 1-800-IBM-SERV. For both the Model 90 and 95, you must ensure that the single inline memory modules match in pairs. This means that each pair of single inline memory modules, as described in system technical reference manual, must be matched in memory size and speed. Mixing these modules can cause some computers to report memory errors. ΓòÉΓòÉΓòÉ 2.46. SYS02025 and SYS02027 on OEM with PHOENIX bios 1.03 on OS/2 2.1 Install Diskette. ΓòÉΓòÉΓòÉ SYS02025 and SYS02027 on OEM with PHOENIX bios 1.03 on OS/2 2.1 Install Diskette. Work around: 1) Make backup copy of OS/2 2.1 Install diskette. 2) Del OS2LDR /* from backup diskette */ Del OS2BOOT /* from backup diskette */ 3) Copy OS2LDR /* from original to backup */ Copy OS2BOOT /* from original to backup */ The SYS02025 and SYS02027 errors have also been found when the user swaps the floppy drive cables without updating CMOS. Updating CMOS corrects the problem (3.5 and 5.25 cable swap). Note that there is a tool available on the IBM NSC BBS and Compuserve that allows you to install OS/2 2.X from the B drive, when the B drive is 3.5 and and A drive is 5.25 and the diskettes are 3.5. This utility is called INST21L (if you have blue labels on your disks) or INST21M (if you have salmon label on your disks). ΓòÉΓòÉΓòÉ 2.47. SYS1201 boot error during (or after) installation of OS/2 2.1 ΓòÉΓòÉΓòÉ SYS1201 boot error during (or after) installation of OS/2 2.1 This will offer suggestions for resolving SYS1201 errors during boot of OS/2 2.1. The information provided is for the general availability release of OS/2 2.1. PROBLEM: SYS1201 - VMOUSE NOT INSTALLED... There appears to be a problem with the OS/2 2.1 installation program if there is any MOUSE.* on the drive where OS/2 2.1 is being installed. The symptom of this problem is the SYS1201 - VMOUSE NOT INSTALLED error. While this is not the ONLY reason for this error, the following steps should offer most users relief of this problem. 1) Review the CONFIG.SYS file for OS/2 2.1 and verify that the DEVICE= statement points to MOUSE.SYS in the x:\OS2 directory (where x: is the installed drive and is usually 'c:'). There has been one user who has reported that MOUSE.COM was loaded in the CONFIG.SYS file instead of MOUSE.SYS. This event HAS NEVER been duplicated in the IBM labs. There should be no reference to MOUSE.COM in the CONFIG.SYS file for OS/2 2.1. 2) Copy the MOUSE.SYS file from Program Diskette 1 (which is the second disk in the install series) to the x:\OS2 directory (where x: is the installed drive and is usually 'c:'). Shutdown OS/2 2.1 and reboot the computer. 3) If the problem persists after following the preceding instructions, you can "HOT PLUG" (unplug, wait and then plug in) the mouse. If this fixes the problem and you previously used the mouse under OS/2 2.0, you can try using the MOUSE.SYS from OS/2 2.0. This is also located on Program Diskette 1 of the install series of OS/2 2.0. PROBLEM: SYS1201 - COM.SYS NOT INSTALLED... or IRQ NOT AVAILABLE. 1) If you only have one (1) serial port AND you have a MOUSE plugged into the port, you will get this error. Edit the CONFIG.SYS file and place a remark (REM) statement before the "DEVICE=...\COM.SYS" and "DEVICE=...\VCOM.SYS" lines. 2) If you have a PS/2 or equivalent Microchannel Architecture (MCA) computer, you should not pass ANY parameters to the COM.SYS device driver. Only ISA and non-ABIOS computers require parameters for serial ports greater than COM2:. 3) If you have an Industry Standard Architecture (ISA or AT) computer, you will have to provide the CORRECT Input/Output (I/O) address and Interrupt Request Level (IRQ) for serial ports greater than COM2:. The parameters must match the PHYSICAL settings of the serial adapter(s). You will have to reference the documentation which should have come with the serial adapter to determine how to PHYSICAL change (or "jumper") the adapter. If you have an internal modem and have two external serial ports, we recommend that you try to set the modem to I/O address "3e8" and IRQ 5. (NOTE: You can only use IRQ 5 if you have only one (1) parallel port (LPT1:). The format of the parameter line is: DEVICE=...\COM.SYS (p,addr, irq) For example, if you have PHYSICALLY configured your internal modem to I/O address 3e8 (or COM3:) and have set the PHYSICAL IRQ to level five (5), you would set the following parameters: DEVICE=x:\OS2\COM.SYS (3,3e8,5) 4) If you provide an invalid address or IRQ, you will get messages that indicate that the "COMx" port was not installed or that the IRQ is not available. You will have to verify that the serial adapter (i.e. internal modem) is configured correctly. ΓòÉΓòÉΓòÉ 2.48. ISA bus workaround for installation problems on AT (ISA) BUS machines ΓòÉΓòÉΓòÉ ISA bus workaround for installation problems on AT (ISA) BUS machines CONFIGURATION: AT-bus (ISA) machine non-SCSI disk controller (RLL, MFM, ESDI) sometimes occurs on IDE controllers. SYMPTOMS: Very slow install Very noisy hard disk during install FDISK errors Very slow operation There is a driver, IBM1S506.ADD that is available on the IBM NSC BBS as well as various other non-IBM OS/2 BBS's around the country. This driver fixes the symptoms described above. If you are unable to obtain the driver, the workaround described below will alternatively allow you to install and use OS/2 2.X, however, it is recommended that you obtain the driver. WORKAROUND BEFORE INSTALLATION: ------------------------------ Step 1: Use DOS to edit the CONFIG.SYS on Diskette 1 in the 2.X package. NOTE: Diskette 1 is the first diskette AFTER the Install diskette. Change the line - BASEDEV=IBM1S506.ADD to REM BASEDEV=IBM1S506.ADD Alternate to Step 1 Above: -------------------------- If you don't have access to DOS OR do not have a DOS editor to edit the CONFIG.SYS, as an alternate to editing the CONFIG.SYS file on Diskette 1, you may follow these steps: a) Insert the Installation Diskette into drive A b) Turn on the computer. If the computer is already on, press and hold Ctrl+Alt and press Del to restart the system. c) When you are prompted to do so, remove the Installation Diskette and insert Diskette 1. d) Press Enter. e) When the Welcome screen is displayed, press Esc to display the OS/2 command prompt. f) With Diskette 1 in the drive, rename the IBM1S506.ADD to IBM1S506.OLD by typing the following at the prompt: RENAME IBM1S506.ADD IBM1S506.OLD g) Continue with Step 2. Step 2: Insert the Installation Diskette into drive A. Step 3: Turn on the computer. If the computer is already on, press and hold Ctrl+Alt, and press Del to restart the system. Proceed with Diskette 1 through 5. Step 4: After Diskette 1 through 5 are processed, you will be asked to reinsert the Installation diskette. DO SO. After copying some files from the Installation diskette, you will be asked to remove the Installation diskette and press Enter to reboot. DO NOT DO THIS. LEAVE THE INSTALLATION DISKETTE IN THE DRIVE. NOTE: In OS/2 2.1 the installation is slightly different, it will ask for the installation diskette then diskette #1 at this point you will see the message take out the diskette and reboot. DO NOT DO THAT..INSTEAD PUT THE INSTALLATION DISKETTE BACK IN THE A: DRIVE. Step 5:Press and hold Ctrl+Alt and press Del to restart the system. Step 6:Your computer should now be rebooting off the Installation Diskette. Step 7:When you are prompted to do so, remove the Installation Diskette and insert Diskette 1. Step 8:Press Enter. Step 9:When the Welcome screen is displayed, press Esc to display the OS/2 command prompt. Step 10:You are now at a command line. If you are NOT attempting to install HPFS, continue on to the next step, otherwise execute the following steps to load the HPFS driver. Insert Diskette #2 in the drive, and enter the following command: chkdsk c: (If your operating system will reside on a drive other than C, use the appropriate drive letter instead.) Step 11: Enter the following commands: RENAME C:\OS2\IBM1S506.ADD IBM1S506.XXX COPY C:\OS2\IBMINT13.I13 C:\OS2\IBM1S506.ADD (If your operating system will reside on a drive other than C, us the appropriate drive letter instead.) Step 12: Remove the diskette from the drive. Press ALT-CTRL-DEL to reboot the system, and install should pick up where it left off. WORKAROUND AFTER INSTALLATION Open the system folder on the desktop, then open Command Prompts Folder Open OS/2 Window, at the prompt go the OS2 subdirectory on the drive that OS2 was installed on, and type: RENAME IBM1S506.ADD IBM1S506.XXX COPY IBMINT13.I13 IBM1S506.ADD Close all open folders and proceed with a proper shutdown. When the machine is rebooted the change will take effect. ΓòÉΓòÉΓòÉ 2.49. IBM Premier ABIOS Systems Installation ΓòÉΓòÉΓòÉ IBM Premier ABIOS Systems Installation At the time of the original release of OS/2 2.0, the installation code could not recognize new hardware with RAM loadable ABIOS. The architecture in the installation process has been changed to recognize this RAM loadable ABIOS and has been incorporated into the latest release. There is a workaround for the original GA release. Make a copy of the Installation Disk and Disk One of OS/2 2.0. Substitute the ABIOS.SYS from the Premier hardware reference disk to both the OS/2 2.0 Installation and Disk One. Copy the SF838XX.BIO file from the hardware reference disk (should be about 40K) to both OS/2 2.0 Installation Disk and Disk One. If there isn't enough space on the diskettes, get rid of the other .BIO files that exist on the Installation and Disk One. Then you are ready to begin installation of GA OS/2 2.0 on your Premier machine. Once OS/2 2.0 is loaded, you can apply the OS/2 Service Pack 2 (xr06100) available on Compuserve, the IBM NSC BBS or call 1-800-3IBM-OS2. If the problem is with an IBM ThinkPad computer, there is another item that deals with this special case of ABIOS.SYS problems. ΓòÉΓòÉΓòÉ 2.50. Information on INSTALL BIOS PROBLEMS ΓòÉΓòÉΓòÉ 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 an updated BIOS. Many install problems and other I/O related problems may be resolved by updating the 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. ΓòÉΓòÉΓòÉ 2.51. SOME BIOS COMPATIBILITY INFO ΓòÉΓòÉΓòÉ 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 MC Enabler SCSI Host Apdater 2.0 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 UPGRADES ============== 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 upgrade 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. ΓòÉΓòÉΓòÉ 2.52. All Adaptec adapters - SCSI settings ΓòÉΓòÉΓòÉ All Adaptec adapters - SCSI settings Note: SCSI hard disks must be configured as SCSI target ID 0 or 1 to be able to start up from that hard disk. ΓòÉΓòÉΓòÉ 2.53. Adaptec AHA-154x ΓòÉΓòÉΓòÉ 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. ΓòÉΓòÉΓòÉ 2.54. Adaptec AHA-174x ΓòÉΓòÉΓòÉ 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. ΓòÉΓòÉΓòÉ 2.55. Future Domain adapter BIOS revision level requirements ΓòÉΓòÉΓòÉ Future Domain adapter BIOS revision level requirements 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. ΓòÉΓòÉΓòÉ 2.56. AMI SCSI Adapters ΓòÉΓòÉΓòÉ 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. ΓòÉΓòÉΓòÉ 2.57. Bernoulli Boxes ΓòÉΓòÉΓòÉ 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 Iomega has drivers for the Bernoulli Boxes. ΓòÉΓòÉΓòÉ 2.58. MC Enabler SCSI Host adapter ΓòÉΓòÉΓòÉ MC Enabler SCSI Host adapter Resolution: Requires ROM Revisions 2.00. or higher. ΓòÉΓòÉΓòÉ 2.59. IBM 16-bit SCSI cards (early versions) ΓòÉΓòÉΓòÉ 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 ΓòÉΓòÉΓòÉ 2.60. Slow hard drive speed and possibly no icons appearing. ΓòÉΓòÉΓòÉ Slow hard drive speed and possibly no icons appearing. 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. ΓòÉΓòÉΓòÉ 2.61. Installing OS/2 2.X on a PC using the Always IN-2000 SCSI Host adapter? ΓòÉΓòÉΓòÉ Installing OS/2 2.X on a PC using the Always IN-2000 SCSI Host adapter? Contact Always Technology to obtain BIOS upgrade VCN:1-02 for the controller. ΓòÉΓòÉΓòÉ 2.62. Known problems involving an AOX add-in processor card in a Micro Channel PS/2? ΓòÉΓòÉΓòÉ Known problems involving an AOX add-in processor card in a Micro Channel PS/2? If you encounter problems installing or booting OS/2 with this configuration, contact AOX for the latest "flash PROM" code update. ΓòÉΓòÉΓòÉ 2.63. Installing OS/2 2.0 on a L40, and getting CRC errors and the installation locks up. ΓòÉΓòÉΓòÉ Installing OS/2 2.0 on a L40, and getting CRC errors and the installation locks up. Tried several sets of diskettes with the same results. Some early L40s had inadequate shielding around the diskette drive that shows up when installing OS/2. The power supply, which is beside the drive emits more electromagnetic interference when multiple devices are running concurrently, such as when OS/2 is multitasking (while installing diskette 3, for example). If you have verified that the diskettes themselves are not defective, replace the diskette drive. ΓòÉΓòÉΓòÉ 2.64. Installing OS/2 2.0 on a P70, and getting CRC errors and the installation locks up. ΓòÉΓòÉΓòÉ Installing OS/2 2.0 on a P70, and getting CRC errors and the installation locks up. Tried several sets of diskettes with the same results. Some early P70s had an engineering defect that only shows up with multitasking operating systems (including OS/2 and AIX). There is an Engineering Change Announcement (ECA) that fixes this problem. Take your system in to your dealer and have them service the system under warranty. ECA068 will extend the warranty indefinitely for this particular problem, without charge. ΓòÉΓòÉΓòÉ 2.65. Getting a C000005 error during installation and can't continue. ΓòÉΓòÉΓòÉ Getting a C000005 error during installation and can't continue. The problem results from a conflict with some SVGA cards. There is a replacement BVHSVGA.DLL file available on the IBM NSC BBS) that allows installation. ΓòÉΓòÉΓòÉ 2.66. System is hanging during installation (or bootup). ΓòÉΓòÉΓòÉ System is hanging during installation (or bootup). If you have a SVGA card that uses the Western Digital PVGA1D chipset, there is a replacement BVHSVGA.DLL file available on the IBM NSC BBS that corrects this problem. ΓòÉΓòÉΓòÉ 2.67. Known INSTALL problems with AMI BIOS ΓòÉΓòÉΓòÉ Known INSTALL problems with AMI BIOS Symptom: Various install problems. The suggestion to upgrade these items should always be made. Possible SYS2025, and SYS2027 at disk#1. Problem: Machine must have BIOS dated 5/9/91 and keyboard controller chip version KF. The following information will be seen by the user at (cold)boot time: AMI BIOS and AMI BIOS Plus: aaaa-bbbb-mmddyy-Kc AMI Hi-Flex BIOS: ee-ffff-bbbbbb-gggggggg-mmddyy-hhhhhhhh-c If an IDE hard drive is in the system, "mmddyy" should be 040990 or later. For other drives including MFM, RLL, ESDI, or SCSI, "mmddyy" should be 092588 or later. Controller chip version can be located on the bottom of that same screen. Check the last digit in the long stream of digits (the "c" above). The last digit will probably be either be 8, B, D, or F. The required level should be F for OS/2 v2.0 or v1.3. Pressing the INS key during bootup should cause this info to stay on the screen. Resolution: 1. Call Washburn & Co. to order new versions. 2. Bad diskette. Format new diskette and diskcopy failing diskette to this new diskette. 3. Clean, swap or replace the diskette drive. 4. Disable system memory cache during installation. Washburn & Co. 716-248-3627 (AMI Bios Upgrade) 800-836-8026 (AMI Bios Upgrade) ΓòÉΓòÉΓòÉ 2.68. Installing with ATI VIDEO ADAPTERS ΓòÉΓòÉΓòÉ Installing with ATI VIDEO ADAPTERS ATI Wonder SVGA The ATI Wonder Super VGA board is supported in VGA mode only with the video drivers supplied with OS/2. However, ATI does have drivers for 800x600 and 1024x768 resolutions in 16 colors. As of this writing, there are no drivers for 256 colors. You c an call ATI at 416-756-0711 to get information on obtaining these drivers. If you have any problems with ATI drivers, you will need to speak to ATI, IBM will not be able to help you. ATI Vantage and Graphics Ultra These boards are almost identical, the major difference being that the Vantage uses DRAM and the Graphics Ultra uses the faster VRAM. The Graphics Ultra is probably the best choice for using the higher resolution modes under OS/2. It will provide 10 24 x 768 resolution with 256 colors for both OS/2 and full screen Windows applications using the drivers supplied with OS/2. ATI also has drivers for these boards which will provide 640x480, 800x600, and 1024x768 resolutions in 16 or 256 colors. You MUST have 1MB of memory on your video board to get 256 colors. Before installing OS/2, use the setup program (provided by ATI) to setup your video board. During installation, OS/2 should recognize the board as an 8514 and list that as your primary display. If not, the board is not set up properly. DO NOT attempt to use these boards as your secondary display, it MUST be the primary display. After the installation, you will need to modify a line in your CONFIG.SYS as follows: Change DEVICE=C:\OS2\MDOS\VVGA.SYS to DEVICE=C:\OS2\MDOS\VSVGA.SYS The IBM 8514 board uses VVGA.SYS, the ATI 8514 boards require VSVGA.SYS. As of this time, seamless Windows are not supported in the high resolution mode. You will be limited to using Windows as a full screen application only. If you must have seamless Windows, you MUST select medium resolution when installing OS/2 video dri vers. Medium resolution is VGA (640 x 480) so you will lose the advantage of having an 8514 compatible board. This will be added later this year as an enhancement to the OS/2 graphics engine. The only serious problems we have encountered with these boards is with switching from DOS and Windows full screen applications to the desktop or vice versa. You may occasionally have a DOS or Windows session lock up or appear to hang after the switc h. This can be resolved by turning VIDEO_SWITCH_NOTIFICATION to ON for each and every object on your desktop that launches a full screen session. If the problem persists, turn VIDEO_8514A_XGA_IOTRAP to ON also. These switches can be found in the DOS Settings in the "Open - Settings" notebook. If you do not have the VIDEO_8514A_XGA_IOTRAP setting listed, you do not have the proper drivers installed for 8514 operation. I would also recommend that you set these switches for each of the objects in your command prompts folder that launch a full screen session. ATI 8514 Ultra This board provides the same functionality as the Graphics Ultra, but requires a separate VGA or SVGA adapter in your system. All of the information listed above for the Graphics Ultra applies to this board as well. One additional problem has been encountered with this board though, you may get a blank white screen when booting (usually seen during the reboot required by the install process) and the system will hang. This is caused by an incorrect monitor ID being returned to OS/2 when it queries the device to see what kind of monitor is attached. ATI has corrected this problem with their latest 8514 Ultra ROM chip. You can call ATI at 416-756-0711 to obtain an update. General Considerations The 8514 compatible boards (Vantage, Graphics Ultra, and 8514 Ultra) are NOT Super VGA boards. You should NOT execute SVGA ON from the DOS command prompt as you would for other high resolution boards. This WILL cause problems with your video! You can c heck the C:\OS2 directory for the file SVGADATA.PMI to determine if the SVGA program has been executed. If this file exists, delete it, shutdown, and reboot your system. You may have heard that you need to put your board in an 8 bit slot in order to work properly, this is not true for ATI boards. You should have no problem using your board in 16 bit mode. ΓòÉΓòÉΓòÉ 2.69. CDROM install with Sony 31A ΓòÉΓòÉΓòÉ CDROM install with Sony 31A The Sony 31A device driver is available on the IBM NSC BBS The file name is SONY31A.ZIP. ΓòÉΓòÉΓòÉ 2.70. Non Supported CDROM Information ΓòÉΓòÉΓòÉ Non Supported CDROM Information When installing OS/2 2.1 from a nonsupported CDROM, the following procedure might work, but cannot be supported by the Support Center. If you have a nonsupported CDROM, the following instructions might allow the CDROM to operate under OS/2. If unsuccessful please contact the manufacturer or supplier of the CDROM. 1. Make the diskettes images from the CD ROM(DOS must be present) Go to the images subdirectory when booted in real DOS and use LOADDSKF to make the diskette images (LOADDSKF filename A:) 2. Disconnect the CD ROM 3. Install OS/2 v2.0 or v2.1 from diskette. 4. Copy devices drivers(ext. .ADD)to \OS2 directory (CD ROM/Sound card). 5. Copy the device drivers for the Controller/Adapter. 6. Connect the CD ROM and plug in Sound Card and Controller/Adapter. 7. Do a Selective install of for CDROM (modifies the CONFIG.SYS) Statements in CONFIG.SYS that should appear: EX: DEVICE=x:\OS2\OS2CDROM.DMD /Q IFS=x:\OS2\CDFS.IFS /Q BASEDEV=<device_driver_name> Where x: is the drive where OS/2 resides ** All device drivers MUST be compatible with OS/2 ** Most vendors will provide the technical support or literature to install on OS/2 if it is not in the supported list. IBM will not supply other suppliers device drivers to ensure that the latest updated drivers are received directly from the source. Please do not request non-IBM drivers from the IBM Support Centers. If you are unsuccessful installing OS/2 2.1 from CDROM on a non-supported CDROM please either contact your manufacturer, make the diskettes from the images on another PC or exchange your CDROM package for the diskette package. ΓòÉΓòÉΓòÉ 2.71. Installation of Super VGA display drivers. ΓòÉΓòÉΓòÉ Installation of Super VGA display drivers. Display drivers that typically come from the display card manufacturers are replacements to the DISPLAY.DLL file in the OS2\DLL directory of the partition where you installed (For example, C:\OS2\DLL). To install a replacement display driver, following these steps: 1. From an DOS Full Screen, under OS/2 2.0, run the SVGA utility by typing: SVGA ON (See the OS/2 2.0 readme file for more information on SVGA). 2. Shutdown and reboot from either a DOS diskette (if you have FAT) or from the OS/2 installation diskettes. If you choose to boot from the Installation Diskettes, follow these steps, otherwise skip down to step 3. a.Insert the Installation Diskette into drive A. b.Turn on the computer. If the computer is already on, press and hold Ctrl + Alt and press Del to restart the system. c.When you are prompted to do so, remove the Installation Diskette and insert diskette 1. d.Press enter. e.When the Welcome screen is displayed, press Esc to display the command prompt. 3. Switch to the drive that you installed OS/2 on (i.e., C:)/ 4. Switch to the \OS2\DLL directory (by typing cd \os2\dll), and execute the following step to backup the existing display driver: rename display.dll display.old 5. Copy the new display driver provided by the board manufacturer (filename may vary), into the \OS2\DLL directory with the filename of DISPLAY.DLL. For example, if the filename of the display driver you have is DISP.DRV and is in the \TEMP directory, you would execute the following statement from the OS2\DLL directory: copy \TEMP\DISP.DRV DISPLAY.DLL This will copy DISP.DRV from the \TEMP directory and rename it to DISPLAY.DLL in the OS2\DLL directory since that is where you were when you issued the copy command. ΓòÉΓòÉΓòÉ 2.72. Diamond Speedstar Adapter ΓòÉΓòÉΓòÉ Diamond Speedstar Adapter Recommended video BIOS revision for this adapter is 4.23. Contact Diamond about the BIOS upgrade. ΓòÉΓòÉΓòÉ 2.73. Diamond Stealth adapter ΓòÉΓòÉΓòÉ 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 (refer to the General considerations section for the outline of the VGA support). Recommended video BIOS revision is 2.32 forthis adapter. Contact Diamond about the BIOS upgrade. ΓòÉΓòÉΓòÉ 2.74. Diamond Speedstar 24X Card Configuration ΓòÉΓòÉΓòÉ Diamond Speedstar 24X Card Configuration The following information is necessary for the proper configuration of the Diamond Speedstar 24X card and the CTX 5648NI monitor. They are incorrectly identified by the OS/2 installation process as an IBM 8514A adapter and a SONY 1302 monitor. One of the following changes must be made to the CONFIG.SYS: SET VIO VGA=DEVICE(BVHVGA,BVHSVGA) DEVICE=C:\OS2\MDOS\VSVGA (Super VGA set) (assuming you have the IBM corrective service update of the file "BVHSVGA.DLL" copied into the C:\OS2\DLL directory) -OR- SET VIO VGA=DEVICE(BVHVGA) DEVICE=C:\OS2\MDOS\VVGA.SYS ( Standard VGA set) (OS/2 2.0 will use standard VGA 640x480x16 mode for DOS, WIN/OS2, and OS/2 screens no matter which set you choose.) Once you make one of the above corrections, there will still be a problem with the WIN/OS2 screen being out of synchronization, off center, and reduced in size. This problem can be corrected by running 24XMODE from a DOS session. Choose "Custom" under monitor selection and use the highest acceptable non-interlaced rate (60-70hz) for 640, 800, and 1024 resolutions; then save the configuration. Add the line "24XMODE MONITOR" to the OS/2 AUTOEXEC.BAT. You must choose "Shutdown" from the workplace Shell to save/reboot so that the changes may take affect. This assumes that the Speedstar 24X utility " 24XMODE.COM" is loaded in the root directory of the boot drive. ΓòÉΓòÉΓòÉ 2.75. Country.Sys not found message on all Gateway Nomad "notebook" models. ΓòÉΓòÉΓòÉ Country.Sys not found message on all Gateway 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. ΓòÉΓòÉΓòÉ 2.76. Gateway machines with a 486 can potential have DIVIDE UNDERFLOW errors. ΓòÉΓòÉΓòÉ 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. ΓòÉΓòÉΓòÉ 2.77. Gateway machines that Trap 2 on boot or install ΓòÉΓòÉΓòÉ 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 canbe 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. ΓòÉΓòÉΓòÉ 2.78. Common Symptom: Trap 2, Trap 6 or other Trap at 60000x:9084. ΓòÉΓòÉΓòÉ Common Symptom: Trap 2, Trap 6 or other Trap at 60000x:9084. These problems are caused by: Mismatched memory simms (from different manufacturers) - 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). ΓòÉΓòÉΓòÉ 2.79. Cache problems. ΓòÉΓòÉΓòÉ Cache problems. Solution: Replace memory and/or tune wait states, disable cache during install, turn turbo switch off. ΓòÉΓòÉΓòÉ 2.80. SCSI install problems ΓòÉΓòÉΓòÉ SCSI install problems Problem: FDISK error, hang during install, hang on disk1 or 2. Solutions: Incorrect BIOS date 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 ΓòÉΓòÉΓòÉ 2.81. AMI SCSI - slow, noisy disk during install ΓòÉΓòÉΓòÉ AMI SCSI - slow, noisy disk during install BASEDEV workaround - see APAR II06081 ΓòÉΓòÉΓòÉ 2.82. hang on LOGO screen after reboot following good install ΓòÉΓòÉΓòÉ hang on LOGO screen after reboot following good install FUTURE DOMAIN 16XX SCSI controller - hang on LOGO screen after reboot following good install check for interrupt conflict - see APAR II06081 ΓòÉΓòÉΓòÉ 2.83. Always Technology SCSI ΓòÉΓòÉΓòÉ Always Technology SCSI BIOS upgrade - see APAR # II06081 ΓòÉΓòÉΓòÉ 2.84. Colorado Memories Tape Drive attached during install. ΓòÉΓòÉΓòÉ Colorado Memories Tape Drive attached during install. disconnect tape drive during install. fix available from Colorado - ΓòÉΓòÉΓòÉ 2.85. PROCOMM+ SCSI disk adapters (Microchannel) ΓòÉΓòÉΓòÉ PROCOMM+ SCSI disk adapters (Microchannel) Unsupport SCSI, refer to manufacturer. ΓòÉΓòÉΓòÉ 2.86. Early versions of IBM 16-bit SCSI adapters ΓòÉΓòÉΓòÉ Early versions of IBM 16-bit SCSI adapters Update microcode ΓòÉΓòÉΓòÉ 2.87. Unable to install to removable media support - Bernoulli (IOMEGA), and SyQuest ΓòÉΓòÉΓòÉ Unable to install to removable media support - Bernoulli (IOMEGA), and SyQuest Support is limited, treats them like big floppies - see readme ΓòÉΓòÉΓòÉ 2.88. All Adaptec adapters ΓòÉΓòÉΓòÉ 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 ΓòÉΓòÉΓòÉ 2.89. Adaptec AHA-174x w/IBM SCSI drives will not recognize in 'STANDARD MODE' ΓòÉΓòÉΓòÉ Adaptec AHA-174x w/IBM SCSI drives will not recognize in 'STANDARD MODE' 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 ΓòÉΓòÉΓòÉ 2.90. Future Domain can cause "Disk Read Error" on installation disk for PS/2 35 and 40 ΓòÉΓòÉΓòÉ Future Domain can cause "Disk Read Error" on installation disk for PS/2 35 and 40 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 ΓòÉΓòÉΓòÉ 2.91. AMI "Fast Disk" SCSI adapters are incorrectly recognized as Adaptec adapters ΓòÉΓòÉΓòÉ AMI "Fast Disk" SCSI adapters are incorrectly recognized as Adaptec adapters See readme for workaround ΓòÉΓòÉΓòÉ 2.92. Always IN2000 SCSI adapter - causes Internal Processing Error ΓòÉΓòÉΓòÉ Always IN2000 SCSI adapter - causes Internal Processing Error Need BIOS upgrade VCN1-02 - see APAR # II06081 ΓòÉΓòÉΓòÉ 2.93. Quantam Plus Hardcard Attached ΓòÉΓòÉΓòÉ Quantam Plus Hardcard Attached Need EPROM upgrade - see APAR II06081 ΓòÉΓòÉΓòÉ 2.94. SUMO SCSI adapters don't seem to work with OS/2 ΓòÉΓòÉΓòÉ SUMO SCSI adapters don't seem to work with OS/2 Talk to manufacturer ΓòÉΓòÉΓòÉ 2.95. FDISK problems during INSTALL ΓòÉΓòÉΓòÉ FDISK problems during INSTALL Some common problems: 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. ΓòÉΓòÉΓòÉ 2.96. Trying to install over a Beta version of OS/2 2.0 (1.3 is OK) fails ΓòÉΓòÉΓòÉ Trying to install over a Beta version of OS/2 2.0 (1.3 is OK) fails Reformat first. ΓòÉΓòÉΓòÉ 2.97. Trying to install HPFS with less than 6M of memory ΓòÉΓòÉΓòÉ Trying to install HPFS with less than 6M of memory Must have 6MB ΓòÉΓòÉΓòÉ 2.98. Trying to install on 4MB ΓòÉΓòÉΓòÉ Trying to install on 4MB User may think he has 4MB, but some cache arrangements or ROM to RAM remapping can steal some - try to disable these features in CMOS setup. ΓòÉΓòÉΓòÉ 2.99. Install hangs on Disk 1 ΓòÉΓòÉΓòÉ 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. ΓòÉΓòÉΓòÉ 2.100. 1024 Limit Problem during install ΓòÉΓòÉΓòÉ 1024 Limit Problem during install 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. ΓòÉΓòÉΓòÉ 2.101. COUNTRY.SYS problems ΓòÉΓòÉΓòÉ 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. ΓòÉΓòÉΓòÉ 2.102. BIOS PROBLEMS ΓòÉΓòÉΓòÉ 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. ΓòÉΓòÉΓòÉ 2.103. Adapter Conflict Problems ΓòÉΓòÉΓòÉ Adapter Conflict Problems 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. ΓòÉΓòÉΓòÉ 2.104. Video Adapter Problems ΓòÉΓòÉΓòÉ 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. ΓòÉΓòÉΓòÉ 2.105. If you have a super VGA adapter, install should always be done as VGA. ΓòÉΓòÉΓòÉ 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 adapter, use 8514/A driver for install. ΓòÉΓòÉΓòÉ 2.106. C0000005 is displayed on the screen during install ΓòÉΓòÉΓòÉ C0000005 is displayed on the screen during install (Western digital PVGA1D) - need fixed version of BVHSVGA.DLL ΓòÉΓòÉΓòÉ 2.107. Hang on Disk1 right after LOGO screen caused by OAK video card BIOS problem. ΓòÉΓòÉΓòÉ Hang on Disk1 right after LOGO screen caused by OAK video card BIOS problem. Workaround is to patch loader file - see Install Adapter APAR ΓòÉΓòÉΓòÉ 2.108. Hang on disk 6 during install ΓòÉΓòÉΓòÉ Hang on disk 6 during install Video card is in VGA mode with auto-sense turned off. ΓòÉΓòÉΓòÉ 2.109. White screen after installation with no system activity ΓòÉΓòÉΓòÉ 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. ΓòÉΓòÉΓòÉ 2.110. Out of Synch/Install problems ΓòÉΓòÉΓòÉ 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. ΓòÉΓòÉΓòÉ 2.111. IRQ conflicts ΓòÉΓòÉΓòÉ IRQ conflicts Some super VGA cards have ROMs with conflicting addresses for some hard disks. ΓòÉΓòÉΓòÉ 2.112. Failures very early on install disk (especially Zeos notebooks) ΓòÉΓòÉΓòÉ Failures very early on install disk (especially Zeos notebooks) Try applying patch to sysinstx.com in Install Other APAR ΓòÉΓòÉΓòÉ 2.113. Dual Boot feature does not allow boot back to OS/2 from DOS ΓòÉΓòÉΓòÉ Dual Boot feature does not allow boot back to OS/2 from DOS There may be a disk caching utility or a TSR which blocks this. ΓòÉΓòÉΓòÉ 2.114. DOS environment cannot be created error message ΓòÉΓòÉΓòÉ DOS environment cannot be created error message 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. 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. ΓòÉΓòÉΓòÉ 2.115. Installation on ZEOS notebook fails ΓòÉΓòÉΓòÉ Installation on ZEOS notebook fails 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 Installation 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. ΓòÉΓòÉΓòÉ 2.116. Fails to reboot after pressing enter. ΓòÉΓòÉΓòÉ 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. ΓòÉΓòÉΓòÉ 2.117. IBM ISA CDROM INSTALLATION FOR OS/2 2.1 ΓòÉΓòÉΓòÉ IBM ISA CDROM INSTALLATION FOR OS/2 2.1 To properly install this drive you will need the following: 1.The switch settings on the interface card. Refer to your cd-rom manual. 2.The Diskette with the ISACDOS2.ADD driver. 3.The OS/2 diskettes or the CDROM install package. FOR INSTALLATION OF OS/2 2.1 1.Make a diskcopy of OS/2 DISK1. 2.Edit the CONFIG.SYS and add the device driver line. BASEDEV=ISACDOS2.ADD /M:xxx Where xxx is the hex address set on the switches. 3.Start the installation. AFTER OS/2 IS INSTALLED 1.Open the OS/2 SYSTEM ICON. 2.Open COMMAND PROMPTS. 3.Open OS/2 WINDOW. 4.Type E CONFIG.SYS. 5.Add the line BASEDEV=ISACDOS2.ADD /M:xxx Where xxx is the hex address set on the switches. 6.Save and exit. 7.Type exit 8.Close COMMAND PROMPTS. 9.Select SYSTEM SETUP. 10.Select SELECTIVE INSTALL. 11.Put a check mark in the CDROM BOX. 12.Click on OK. 13.This will bring up a list of CDROMS. Select OTHER. 14.Follow the online instructions for the driver installation. 15.SHUT DOWN and REBOOT. Check the DRIVES ICON for the presence of your CDROM. ΓòÉΓòÉΓòÉ 2.118. Setting up the ATI MACH32 chipset to emulate the IBM 8514 ΓòÉΓòÉΓòÉ Setting up the ATI MACH32 chipset to emulate the IBM 8514 Setting up the ATI MACH32 chipset to emulate the IBM 8514, using the IBM 8514 Device drivers. Video Cards with the MACH32 Chipset ATI VGA Wonder GT ATI Graphics Ultra Plus ATI Graphics Ultra Pro ATI Ultra Professional Summary for setting up the adapters 1. Setup the ATI Mach32 Card to emulate the 8514 video adapter Select the monitor type as Custom and set the resolutions as follows a. 640x480 - Setup b. 800x600 - NON-SUPORTED (This is not supported!!!) c. 1024x768 - Setup d. 1280x1024 - NON-SUPORTED (This is not supported!!!) 2. Setup the Memory Aperture. a. ISA bus systems 1. Disable, if the system has more than 12MB of RAM 2. Enable, set to 96MB, the apature should show as 100MB b. EISA bus systems 1. Enable, set to 96MB, the apature should show as 100MB 3. Setup the VGA MEMORY a. 1MB of Video RAM on the video card Set VGA MEMORY to SHARED b. 2MB of Video RAM on the vidoe card Set VGA MEMORY to 512K or 1MB 4. Test video card 5. Check system information, for 1MB or 2MB of VRAM 6. Installation of OS/2 Install as a VGA system, then Selective install 8514. * Note: DO NOT run SVGA ON, it does not apply to this adapter!!! If the SVGADATA.PMI file exists delete it!!!! * Note: Monitor must be capable of the higher refresh rates. Check monitor specifications, to be sure DETAIL for setting up the adapters 1. Setup the ATI Mach32 Card to emulate the 8514 video adapter a. Boot off of a DOS diskette, with no memory management programs c. Place the ATI installation diskette in the computer d. Change to the Drive Type A: then press Enter (where 'A' is the drive the disk is in) e. Type INSTALL then press Enter f. Select POWER UP CONFIGURATION g. Select MONITOR TYPE h. Select CUSTOM * Take note of the Warning 1) Select 640X480 a. IBM Default / 60 Hz (whichever is present) 2) Select 800x600 a. Select "NON-SUPPORTED" 3) Select 1024x768 a. Select Highest refresh rate the monitor can handle * For refresh rates, check the monitor specifications b. If, there are no monitor specifications. 1) A good starting point is 72Hz 2) Select the desired refreash reate (72Hz) 3) Adjust the screen via the instructions on the screen * If you can not see the screen press ESC. to return, and select different refreash rate. * The possible refresh rates are 72Hz, 70Hz, 60Hz NonInterlaced, 87.5Hz Interlaced) 4) Continue until the screen is, as desired 4) Select 1280x1024 a. Select "NON-SUPPORTED" i. Press ESC, Hit "Y" to save changes j. Press F10 to save the Changes. 2. Setup the Memory Aperture. a. ISA bus systems 1. Disable, if the system has more than 12MB of RAM 2. Enable, set to 96MB, the apature should show as 100MB b. EISA bus systems 1. Enable, set to 96MB, the apature should show as 100MB 3. Setup the VGA MEMORY a. If 1MB of Video RAM on the video card Set VGA MEMORY to SHARED b. If 2MB of Video RAM on the vidoe card Set VGA MEMORY to 512KB or 1MB 4. Save Settings a. Return to the POWER UP CONFIGURATION menu b. Press F10, monitor will flicker while programming the EPROM. c. Shutdown system then turn system off. Restart system. 5. ESC until the main menu, Select UTILITIES a. Select system information 1) Check for 1MB of video memory, or 2MB (which ever the board has). 2) Press ESC b. Select TEST 1) Select RUN ALL TESTS 2) Select JUST ONCE, for number of times to run tests 6. Shutdown system then turn system off. Restart system. 7. Installation of OS/2 Install as a VGA system, then Selective Install 8514 * Note: DO NOT run SVGA ON, it does not apply to this adapter!!! If the SVGADATA.PMI file exists delete it!!!! 8. If the system is setup improperly. Or is not in the 8514 mode a. Do a selective installation of VGA support, then b. Do a selective installation of 8514 if the higher resolution is desired, and supported (at least 1MB of VRAM and a monitor which will support the higher resolution). * Note: Monitor must be capable of the higher refresh rates. Check monitor specifications, to be sure ΓòÉΓòÉΓòÉ 2.119. Setting up adapters with the MACH8 chipset to emulate the 8514 ΓòÉΓòÉΓòÉ Setting up adapters with the MACH8 chipset to emulate the 8514 Setting up adapters with the MACH8 chipset to emulate the 8514, using the IBM 8514 drivers Video Cards with the MACH8 Chipset ATI Ultra ATI Graphics Vantage ATI 8514 Ultra Summary for setting up the Adapter 1. Setup the ATI Mach8 Card to emulate the 8514 video adapter Select the monitor type as Custom and set the resolutions as follows a. 640x480 - Setup b. 800x600 - NON-SUPORTED (This is not supported!!!) c. 1024x768 - Setup d. 1280x1024 - NON-SUPORTED (This is not supported!!!) 2. Test video card 3. Check system information, for 1MB of VRAM 4. Installation of OS/2 Install as a VGA system, then Selective install 8514. * Note: DO NOT run SVGA ON, it does not apply to this adapter!!! If the SVGADATA.PMI file exists delete it!!!! * Note: Monitor must be capable of the higher refresh rates. Check monitor specifications, to be sure Details for setting up the Adapter 1. Setup the ATI Mach8 Card to emulate the 8514 video adapter a. Boot off of a DOS diskette, with no memory management programs c. Place the ATI installation diskette in the computer d. Change to the Drive Type A: then press Enter (where 'A' is the drive the disk is in) e. Type INSTALL then press Enter f. Select POWER UP CONFIGURATION g. Select MONITOR TYPE h. Select CUSTOM * Take note of the Warning 1) Select 640X480 a. IBM Default / 60 Hz (whichever is present) 2) Select 800x600 a. Select "NON-SUPPORTED" 3) Select 1024x768 a. Select Highest refresh rate the monitor can handle * For refresh rates, check the monitor specifications b. If, there are no monitor specifications. 1) A good starting point is 72Hz 2) Select the desired refresh rate (72Hz) 3) Adjust the screen via the instructions on the screen * If you can not see the screen press ESC. to return, and select different refreash rate. * The possible refresh rates are 72Hz, 70Hz, 60Hz NonInterlaced, 87.5Hz Interlaced) 4) Continue until the screen is, as desired 4) Select 1280x1024 a. Select "NON-SUPPORTED" i. Press ESC, Hit "Y" to save changes j. Press F10 to save the changes, monitor will flicker while programming the EPROM. k. Shutdown system then turn system off. Restart system. 2. ESC until the main menu, Select UTILITIES a. Select system information 1) Check for 1MB or 1.5MB of video memory. 2) Press ESC b. Select TEST 1) Select RUN ALL TESTS 2) Select JUST ONCE, for number of times to run tests 3. Shutdown system then turn system off. Restart system. 4. Installation of OS/2 Install as a VGA system, then Selective Install 8514 * Note: DO NOT run SVGA ON, it does not apply to this adapter!!! If the SVGADATA.PMI file exists delete it!!!! 8. If the system is setup improperly. Or is not in the 8514 mode a. Do a selective installation of VGA support, then b. Do a selective installation of 8514 if the higher resolution is desired, and supported (at least 1MB of VRAM and a monitor which will support the higher resolution). * Note: Monitor must be capable of the higher refresh rates. Check monitor specifications, to be sure ΓòÉΓòÉΓòÉ 2.120. Information on MITSUMI CD-ROM Device Drivers for OS/2. ΓòÉΓòÉΓòÉ Information on MITSUMI CD-ROM Device Drivers for OS/2. The Mitsumi model CD-ROM players are not supported for use with OS/2. However, you can obtain device drivers that may allow the device to work. If you need such drivers, contact the IBM NSC BBS. This driver is available free of charge. The name of the file is MITFX.ZIP. This driver works only for the Mitsumi models FX001, FX001D, and LU005 CD-ROM players. If you do not have one of these models, you may need to contact the other references listed below. Installation instructions are outlined in the README file supplied in the ZIP package. Systems Integration Technologies 1280 South Powerline Road Suite 171 Pompano Beach, FL 33069 Tel: (305) 968-4605 (305) 972-7038 Computer Discount Warehouse C/O Neil no address available Tel: (800) 800-4239 ext. 265 Both of these supply the necessary drivers for a minimal price. Other sources may have the drivers as well, but no information is available at this time. Until these drivers are acquired, the CD-ROM cannot be used with OS/2. ΓòÉΓòÉΓòÉ 2.121. Installing support for Multimedia CD-ROM packages ΓòÉΓòÉΓòÉ Installing support for Multimedia CD-ROM packages Installing support for Multimedia CD-ROM packages (Media Vision Pro Audio Spectrum, Creative Labs Sound Blaster) These multimedia packages are unsupported through the IBM OS/2 Technical Support Center, but we have had some success with installing support for the Sound Blaster and Pro Audio Spectrum SCSI interfaces. Before proceeding with this setup, you need to obtain the OS/2 Device Drivers from the respective manufacturers. Windows and DOS drivers are not compatible with OS/2. The OS/2 drivers can be obtained from these areas: Creative Labs -- BBS (405) 742-6660 (2400 baud, 8 bits, no parity, 1 stop bit) Files can be found in the OS/2 Audio and CD-ROM Drivers section. They are: for single-speed CD-ROMs, you need CLIOS2CD.ZIP for double-speed CD-ROMs, you need SBCD2.ZIP also, Presentation Manager programs are in SBMMPM2.ZIP For help un-zipping these files, you can look in the New Users directory online. Media Vision -- BBS (510) 770-0968 (2400 baud, 8 bits, no parity, 1 stop bit) (510) 770-1661 (2400 baud, 8 bits, no parity, 1 stop bit) (510) 770-0527 (9600 baud, 8 bits, no parity, 1 stop bit) The file you need is called TMV1SCSI.ZIP. It contains the driver file and also a mixer program and readme file for more information. It can be found in the OS/2 section online. * * * * * Two methods are available. If you have installed OS/2 on your system and wish to add CD-ROM support with one of these packages, skip to step 2. If you want to install from the CD-ROM, use both of these proceedures. 1. Installing from the CD-ROM Make a backup copy of diskette 1 of the OS/2 2.1 installation package. We recommend using the DISKCOPY command, as this will make an exact duplicate of the disk. If you must use the COPY command, make sure that you copy every file and change the volume label of the destination disk to "DISK 1" (do not include the quotes in the volume name). Next, some files will need to be deleted from the backup copy you just created. Good targets for deletion would be the Adaptec and Future Domain SCSI drivers following: AHA152X.ADD AHA164X.ADD FD16-700.ADD FD7000EX.ADD AHA154X.ADD AHA174X.ADD FD8XX.ADD Then copy the manufacturer-supplied driver onto your copy of diskette 1. Next, edit the config.sys on diskette using any plain text editor toinclude the following statements: Lowercase will represent lines that already exist; CAPS represent lines you need to insert. This is to insure proper placement and installation. set cdrominst=1 ifs=cdfs.ifs /q BASEDEV=TMV1SCSI.ADD *** or substitute your driver filename *** Then, delete or REM any BASEDEV statements referring to the filenames which were deleted in the preceeding step (the Adaptec and Future Domain device drivers). REM-ing these statements is recommended for easier recognition of the changes made. From there, you may attempt the installation. If successful, you can go on to step 2. If not, you will need to create the installation disks from the CD "disk images" and install from the floppies. The proceedure for this is explained in your OS/2 Version 2.1 package. 2. Installing CD-ROM support after OS/2 2.1 is installed. Once OS/2 2.1 is installed, you need to make some changes to the CONFIG.SYS located in the root directory of the OS/2 partition in order to make your CD-ROM accessible. For demonstartion purposes, X: will represent the OS/2 partition. First, copy the following files to X:\OS2. These files are located in the following places according to the OS/2 package you own: CD-ROM Installation package ................... Diskette 1 3.5 Diskettes, Blue Label on disk ............. Diskette 10 (packed) 3.5 Diskettes, Salmon Label on disk ........... Diskette 12 (packed) 5.25 Diskettes, Blue Label on disk ............ Diskette 16 (packed) 5.25 Diskettes, Salmon Label on disk .......... Diskette 9 (packed) The files are named OS2CDROM.DMD and CDFS.IFS. If the files are on a "packed" disk, the syntax for unpacking the files is as follows: UNPACK A:\CDROMREQ /N:OS2CDROM.DMD UNPACK A:\CDROMREQ /N:CDFS.IFS Once these are copied, copy the manufacturer-supplied device driver to the X:\OS2 directory as well. From there, you need to edit the config.sys using a plain text editor. For example, to use the OS/2 system editor, open an OS/2 Window and type from the X:\ prompt: E CONFIG.SYS Once the editor is displayed, make the following changes. Lowercase will represent lines that already exist; CAPS represent lines you need to insert. This is to insure proper placement and installation. basedev=ibm1s506.add basedev=os2dasd.dmd DEVICE=X:\OS2\OS2CDROM.DMD /Q IFS=X:\OS2\CDFS.IFS /Q set bookshelf=x:\os2\book . . . further down . . . codepage=437,850 devinfo=kbd,us,x:\os2\keyboard.dcp BASEDEV=TMV1SCSI.ADD *** or your device driver filename *** devinfo=scr,vga,x:\os2\viotbl.dcp . . . Once these changes are complete, save the file and exit the editor. Then perform a shutdown and restart your computer to install the support. Once again, this support is not guaranteed to work in any case, since the drivers are made by other manufacturers. IBM does not supply these drivers at this time, but may in the future. For further assistance, you can contact the manufacturer of your device at the above listed phone numbers. ΓòÉΓòÉΓòÉ 2.122. Microsoft MS-DOS 6.2 upgrade and OS/2 . . . ΓòÉΓòÉΓòÉ Microsoft MS-DOS 6.2 upgrade and OS/2 . . . Before starting the upgrade, please refer to the Getting Started book with MS-DOS 6.2. Installing the upgrade on an OS/2 DUAL BOOT system: The MS-DOS 6.2 upgrade must be installed while DOS is the current operating system. If you are running OS/2 as the current operating system, the steps below should be taken: (1.) Boot to DOS by opening an OS/2 Window and typing: BOOT /DOS (2.) Once the boot procedure is complete, place the MS-DOS 6.2 upgrade diskette in the appropriate drive and type: A:SETUP (if the diskette is in the A: drive) or B:SETUP (if the diskette is in the B: drive) (3.) After a proper upgrade has been completed, please review the CONFIG.SYS and AUTOEXEC.BAT files for the proper OS/2 statements. If they are not there, please refer to the Installation Guide and place the statements as necessary. (4.) After these statements have been verified, dual boot should function as before. To return to OS/2, type: C:\OS2\BOOT /OS2 ΓòÉΓòÉΓòÉ 2.123. Installing MS-DOS 6.2 Upgrade on an OS/2 BOOT MANAGER system: ΓòÉΓòÉΓòÉ Installing MS-DOS 6.2 Upgrade on an OS/2 BOOT MANAGER system: The MS-DOS 6.2 upgrade must be installed while DOS is the current operating system. If you are running OS/2 as the current operating system, the steps below should be taken: (1.) Complete a proper shutdown of OS/2 by placing the mouse cursor on the desktop and pressing your right mouse button. When the "pop-up" menu has appeared, choose Shutdown from the menu. Follow the instructions until the system has told you it is safe to turn of the system or reboot. Rather than turn the machine off, execute a warm boot by pressing CTRL - ALT - DEL. (2.) When the Boot Manager menu appears, choose to boot to the DOS partition. (3.) Once the boot procedure is complete, place the MS-DOS 6.2 upgrade diskette in the appropriate drive and type: A:SETUP (if the diskette is in the A: drive) or B:SETUP (if the diskette is in the B: drive) (4.) Once the upgrade has completed, use the DOS FDISK program to set the Boot Manager partition as ACTIVE, or refer to page 132 of the OS/2 2.1 Installation Guide on "making boot manager startable." If any problems occur while trying to upgrade to MS-DOS 6.2, please refer to Microsoft Technical Support. ΓòÉΓòÉΓòÉ 2.124. How to set up OS/2 for Windows for HPFS only? ΓòÉΓòÉΓòÉ How to set up OS/2 for Windows for HPFS only? Details of Question: User has OS/2 For Windows and would like to set up the system for HPFS only. Answer Summary: The issue is that in order to enable Windows application support under OS/2 for Windows, real Microsoft Windows 3.1 must be installed. Windows 3.1 will not install under OS/2, only DOS. Since DOS cannot see or access HPFS drives, the problem is how to get Windows 3.1 on an HPFS drive. The user can install DOS and Windows, back up the Windows code to diskettes, install OS/2 for Windows, then restore the Windows code from diskettes, then use selective install from OS/2 to add the Windows application support. NOTE: IBM cannot authorize you to make a backup copy of non-IBM supplied code. If you wish to use this method, you are responsible for ensuring you have the right to make a backup copy of Windows 3.1. If you are unsure, please consult your license agreement for the product or contact the vendor. Detailed Answer: 1. Make sure your system has DOS and Windows 3.1 on it. 2. Back up to diskette the subdirectory(ies) that contain the Windows code only. There is no need to back up the DOS code, since you will not need it in this all-HPFS configuration. PLEASE REFER TO THE NOTE ABOVE. 3. Install OS/2 for Windows, choosing to reformat the partition with HPFS. 4. Create the appropriate directory on the target drive, and restore the Windows 3.1 code from diskettes. 5. Open the OS/2 System folder, then the System Setup folder, and start Selective Install. 6. Follow the steps to install Windows application support. ΓòÉΓòÉΓòÉ 2.125. After installing OS/2 for Windows, the mouse does not work at all. ΓòÉΓòÉΓòÉ After installing OS/2 for Windows, the mouse does not work at all. Details of Question: User installed OS/2 for Windows. After rebooting the system, the mouse does not work. When booting to DOS, the mouse works fine. Answer Summary: Sometimes if there is a DOS-based mouse device driver installed, the OS/2 mouse device driver does not get copied over. The solution is to unpack and copy over the OS/2 mouse device driver. Detailed Answer: The OS/2 mouse device driver can be found on diskette 1 of the installation package. 1. Copy the file MOUSE.SYS from the installation diskette 1 to the \OS2 directory on the boot drive. 2. The line containing MOUSE.SYS should be in the OS/2 CONFIG.SYS file. In any case, you will need to reboot the system for the device driver change to take effect. If it is not, use selective install to reinstall the mouse device driver support. a. Open the OS/2 System folder, then the System Setup folder, then open the Selective Install item. b. The first screen will indicate mouse support. Select the one appropriate for the user's hardware and select the OK pushbutton, then select the Install pushbutton and let the mouse device support reinstall itself. c. You must reboot the system for this change to take effect. ΓòÉΓòÉΓòÉ 2.126. Windows 3.1 on CD-ROM ΓòÉΓòÉΓòÉ Windows 3.1 on CD-ROM I have Windows 3.1. It was installed from a CD-ROM. When I install OS/2 for Windows, it tries to find disk #7 on the CD. It is not there. How can I fix this? User installed Windows from a CD-ROM. During the installation of OS/2 for Windows, OS/2 asks for the Windows diskettes, but is treating the images on the CD as 5.25 inch images, where there are 7 diskettes. There is no 7th image on the CD. The user will either have to obtain a diskette #7, or fake out the installation program. Detailed Answer: There are 3 possibilities to fixing this situation: 1. Obtain a Windows 5.25 inch diskette #7. 2. Install Windows 3.1 from a floppy disk. Then use the floppies during OS/2 for WIndows installation. 3. Create a "fake" diskette #7. This can be done by: a. Format a blank 5.25 inch diskette. b. Use the LABEL program to label it DISK7, according to the Microsoft Windows diskette labels. c. Copy the files from diskette 6 from the CD to this diskette and use it when the installation program asks for diskette #7. ΓòÉΓòÉΓòÉ 2.127. Installing with Paradise EGA 480 ΓòÉΓòÉΓòÉ Installing with Paradise EGA 480 This board is capable of higher, non-EGA resolution modes. Our drivers do not support these modes. In order to install properly with this adapter, set all dip switches to OFF, with the exception of switches number 2 and 3. The two switches that are causing the problems are switch #5 (auto switch capability) and switch #6( monitor sense switch). ΓòÉΓòÉΓòÉ 2.128. Paradise VGA+, VGA Pro and VGA 1024 ΓòÉΓòÉΓòÉ Paradise VGA+, VGA Pro and VGA 1024 These boards have problems installing OS/2. These are all 8/16 bit boards, with an autosense switch used for detection of the bus width. OS/2 will successfully install only if this capability is disabled. Set the dip switch to OFF or insert the board into an 8 bit slot. After you have successfully installed OS/2, you may put the board back into 16 bit bus mode. ΓòÉΓòÉΓòÉ 2.129. Paradise VGA Accelerator ΓòÉΓòÉΓòÉ Paradise VGA Accelerator This board is based on the WD90C30 and WD90C31 chipsets with 1MB of video RAM and will have problems installing OS/2. After the first five diskettes, error message C000005 appears during the reboot. An official fix for BVHSVGA.DLL driver is available which will fix the problem. Call the 800 tech support line and request to be mailed a fix for APAR PJ03721. The fix is shipped with instructions on how to install the upgraded driver. There are a number of other video and motherboard manufacturers that are using Western Digital/Paradise chipsets. 8/16 bit chipsets are PVGA1A and PVGA1B, aka WD90C00. For boards built with these chipsets, apply the autosense OFF fix for the successful i nstallation. Boards using WD90c30 and c31 experiencing the C000005 error should apply PJ03721 fix. If you have installed successfully but experience video corruption problems when switching back into a previously opened WIN-OS2 session, set DOS parameter VIDEO_SWITCH_NOTIFICATION to ON in the DOS settings for the WIN-OS2 session in question. You can reach the settings screen by clicking with the right mouse button over the session icon and opening Settings notebook, Session page. If there are synch problems on the desktop with higher resolution adapters, check if the SVGA support has been successful ly installed and activated. OS/2 installation detects if the video adapter has higher-resolution capabilities and if so, specifies SVGA basic video support in the CONFIG.SYS. This support is currently limited to DOS session and VIO subsystem only. In order to activate the support, SVGA ON command must be issued from a DOS full screen session and the system should be shutdown after that. This will create a configuration file called SVGADATA.PMI in the OS2 directory. If you are not interested in the SVGA su pport, you may correct your CONFIG.SYS to indicate VGA support only. CONFIG.SYS statements for SVGA support are: SET VIO_VGA=DEVICE(BVHVGA, BVHSVGA) DEVICE=x:\OS2\MDOS\VSVGA.SYS (where x is your OS/2 system drive letter.) VGA support CONFIG.SYS statements are: SET VIO_VGA=DEVICE(BVHVGA) DEVICE=x:\OS2\MDOS\VVGA.SYS (where x is your OS/2 system drive letter.) If after the PMI file is generated, some of the high resolution modes in your DOS have video problems, you may consider regenerating the PMI file. First remove the \OS2\SVGADATA.PMI file. Locate a DOS mode changing utility that was shipped with the adapt er and run it in OS/2 DOS full screen session. Select the desired video mode and exit the utility. Run SVGA ON immediately after and reboot. This should ensure that timing information in the PMI file is correct for your adapter. ΓòÉΓòÉΓòÉ 2.130. Using a RESPONSE FILE to install OS/2 2.1 ΓòÉΓòÉΓòÉ Using a RESPONSE FILE to install OS/2 2.1 Using a RESPONSE FILE to install OS/2 OS/2 2.1, 3.5 blue diskettes/CD too complicated, too manual WARNING: Make ALL install selections in response file BEFORE the installation. ********************************************************************* COPYING THE RESPONSE FILE TO DISK #1 ____________________________________ The following is a list of the steps you would perform to modify a response file and then place that response file on a copy of disk #1. This procedure requires UNPACK-ing compressed files. To do this, copy UNPACK.EXE from Diskette #2 of the OS/2 package to your hard drive. Any reference to UNPACK should be performed from the hard drive. To copy the response file onto a diskette, you must make some modifications to disk #1. These modifications make room on the diskette for the response file. 1.) Make a copy of disk #1. You will modify the copy only. DISKCOPY A: A: (to use the same drive as source and destination) DISKCOPY A: B: (to use different drives as source and destination) 2.) Make extra room on the copy of disk #1 by deleting files that will not be needed in a response file installation. a.) Delete the MOUSE.SYS file from the copy of disk #1 b.) Delete the BUNDLE file from the copy of disk #1 NOTE: This step is not necessary for CD-ROM installations. c.) Delete the SYSINST2.EXE file from the copy of disk #1 d.) If you are installing OS/2 2.1 on a Micro Channel(*) computer, delete the following file from your copy of disk #1: DEL IBM1*.ADD e.) If you are installing OS/2 2.1 on a non-Micro Channel computer, delete the following files from your copy of disk #1: DEL IBM2*.ADD f.) Edit the CONFIG.SYS that exists on the copy of diskette #1. 1.) Change the SET OS2_SHELL statement from: SET OS2_SHELL=SYSINST2.EXE to: SET OS2_SHELL=RSPINST.EXE A:\OS2SE20.RSP 2.) Delete the following statement: DEVICE=\MOUSE.SYS 3.) If you are installing OS/2 2.1 on a Micro Channel computer, delete the following statements in the CONFIG.SYS file on the copy of disk #1. BASEDEV=IBM1FLPY.ADD BASEDEV=IBM1ADSK.ADD BASEDEV=IBM1SCSI.ADD 3.) Make a copy of the SAMPLE.RSP file, located in a compressed file named REQUIRED on disk #13 that has to be unpacked and then copied to the copy of disk #1: UNPACK A:\REQUIRED C:\ /N:SAMPLE.RSP This will place the file in the root directory of the C: drive. 4.) Use an editor (such as the system editor) to modify and save the file. The file contains comments that explain each of the installation options. 5.) Copy the modified response file to the copy you made of disk #1. Use the name OS2SE20.RSP when you copy the file: example: COPY C:\SAMPLE.RSP A:\OS2SE20.RSP 6.) Copy the RSPINST.EXE File, located in a compressed file named REQUIRED on disk #7 that has to be unpacked and then copied to your copy of disk #1: UNPACK A:\REQUIRED C:\ /N:RSPINST.EXE This will place the file in the root directory of your C: drive. 7.) Begin the installation of the workstation by inserting the installation diskette and restarting the system. 8.) When prompted for disk #1, insert the modified copy of disk #1 and press enter. From this point, the installation program will ask only for the insertion of diskettes. No other installation actions will be necessary. NOTE: When prompted to insert disk #1 again, insert the original disk #1 into drive a: Response files can be used to install the same set of options on multiple workstations. Ensure that the workstations are set up with the same set of options and hardware. ************************************************************************* ΓòÉΓòÉΓòÉ 2.131. Installation hangs on or after either the Blue Disk #17 or Salmon Disk #13 ΓòÉΓòÉΓòÉ Installation hangs on or after either the Blue Disk #17 or Salmon Disk #13 Sometimes near the end of the installation, the system will hang and all system activity will freeze. If this happens, all hope is not lost! A workaround is available to get the system up and running. At this point, enough of the system has been loaded to get up to the desktop. The only things missing are the VIDEO statements in the CONFIG.SYS file on your hard drive. To create these statements . . . NOTE: If you installed your system from a CDROM, you will need to look at step #5 before beginning. (1) Place the Installation Diskette in the A: drive and reboot the system. If the keyboard is locked up, you may need to hard boot the system (turn it off, and then back on). (2) When prompted to insert Diskette 1, do so and press ENTER. This should display the "logo screen" and begin loading the system. (3) When the "welcome screen" is displayed, you will have the option of pressing either ENTER to continue, or ESC to cancel the install. YOU MUST PRESS ESC TO PERFORM THE WORKAROUND!!! (4) When the A:\> prompt is displayed, take the following steps: (a) Change to the drive on which OS/2 resides (C:, D:, etc...) (b) Change Directory to the \OS2 directory on your hard drive. EXAMPLE: CD \OS2 (c) Type: DIR *.* > SVGADATA.PMI (d) Type: SETVGA <d>: Where <d> is the Drive on which OS/2 resides. (5) Once SETVGA.CMD starts, it will ask you for Display Driver Disk 1. If you installed from CDROM, you must create this diskette. This can be done by typing from the prompt: <cd>:\DISKIMGS\LOADDSKF <cd>:\DISKIMGS\OS2\<size>\DISP1.DSK A: Where <cd> is the letter of your CDROM drive and <size> is the size of your diskette (35 for 3.5" disks, 525 for 5.25" disks). Once this process has completed, you can reboot the system to get to the desktop. Once there, go to an OS/2 Window and type DSPINSTL to install your video adapter and correct resolution for your video. Then, shutdown and reboot again, and do a Selective Install for your printer and WIN-OS2 support. If this is unsuccessful, you can also try a few other things . . . (1) Check in the \OS2\DLL subdirectory for the following files and status: a. IBMVGA32.DLL 42378 4-22-93 3:54P b. IBMDEV32.DLL 85326 4-22-93 4:08P c. BVHVGA.DLL 40892 4-25-93 4:04P d. DISPLAY.DLL 77120 4-29-93 9:24P If these files are not on your hard drive, you can get them by unpacking them from Display Driver Diskette #1 by placing the disk in your A: drive and typing: (from the c:\> prompt) \OS2\UNPACK A:\VGA The next step depends on which installation method you are using. If you have the 3.5 disks, you need either diskette #2 if the labels are blue, or diskette #3 if the labels are salmon. If you have 5.25 disks, you need diskette #4. If you have the CD, these files will be in a directory rather than on a physical disk. Once you have the proper disk, type the following: (Example: from the c:\> prompt) \OS2\UNPACK A:\BUNDLE /N:DISPLAY.DLL This will place these files on your hard drive in the \OS2\DLL subdirectory. Once those files are there, use a plain-text editor to check the CONFIG.SYS file on your hard drive for the following statements: DEVINFO=SCR,VGA,x:\OS2\VIOTBL.DCP SET VIDEO_DEVICES=VIO_VGA SET VIO_VGA=DEVICE(BVHVGA) DEVICE=x:\OS2\MDOS\VVGA.SYS Where x: is the partition on which OS/2 resides. ΓòÉΓòÉΓòÉ 2.132. Installing with the Sony 31A CDROM ΓòÉΓòÉΓòÉ Installing with the Sony 31A CDROM This CDROM is a non-supported, non-SCSI CDROM. If you follow the steps listed in this document, you should be able to use the Sony 31A both to install OS/2 and as a CDROM device from the OS/2 desktop. NOTE: Before starting the steps listed below, you need to get the correct device driver for your CDROM from the IBM NSC BBS. The driver file is called SONY31A.ZIP. You will need a copy of PKUNZIP to un-zip the driver package. For installing support for the CDROM as an installation drive for OS/2, follow Parts A and B. For just adding support after OS/2 installation is complete, skip Part A and go immediately to Part B. ***** PART A ***** (1.) Make a DISKCOPY of the OS/2 Diskette #1. You will modify the copy and use it for the installation of OS/2. (2.) Use a plain-text editor to modify the CONFIG.SYS on your copy of Diskette #1. Look for a statement that reads: BASEDEV=AHA152X.ADD Directly ABOVE that statement, include your Sony 31A device driver as a BASEDEV: BASEDEV=SONYB31A.ADD (3.) Copy the driver onto your copy of Diskette #1. (4.) Use the copy of diskette #1 to install OS/2, and begin the install as normal. (5.) Once installed, the CDROM will not show up in your Drives Icon View, and cannot be accessed via command prompt. To fix this, please follow the steps outlined in Part B. NOTE: If you performed the steps above and the installation continued to fail, you will have to install using the floppy diskettes. You can use the CD through DOS to create the installation diskettes. ***** PART B ***** (1.) Boot up under OS/2. Once there, use an OS/2 Window (command prompt) to edit the CONFIG.SYS on your hard drive. Type: E CONFIG.SYS (2.) Once in the editor, look for a statement that reads: DEVINFO=KBD,US,X:\OS2\KEYBOARD.DCP (Where X: is the partition letter of your OS/2 system.) (3.) Directly below that statement, add the following line to the CONFIG.SYS on your hard disk: BASEDEV=SONYB31A.ADD (4.) Once these changes have been made, save the file and exit the editor. If it asks you to select a file type, choose "Plain Text" as the file type. (5.) Now all that remains is physically putting the drivers on your hard drive. The required files are OS2CDROM.DMD, CDFS.IFS, and SONYB31A.ADD. These all must be copied into the \OS2 directory on your hard drive. The first two files can be obtained by performing a Selective Install of your CD-ROM. a. Double-click the OS/2 System folder. b. Double-click the System Setup folder. c. Double-click the Selective Install object. d. On the system configuration screen, place a check mark in the box beside CD-ROM Device Support, and then click the OK button. e. Scroll to the bottom of the Select CD-ROM Device(s) listing and choose "Other", and then click the OK button. f. Once you return to the system configuration screen, click the OK button. g. The next screen is to install additional features. Since they do not relate to the CD-ROM install, click the Install button to proceed. h. Follow the instructions given, and this will add the other necessary files to the hard drive. Be SURE you have copied the SONYB31A.ADD file into the \OS2 directory on your hard drive. (6.) Perform a proper SHUTDOWN of your desktop and reboot. When the desktop comes up, use the Drives Icon View (OS/2 System folder) to check your CDROM. ΓòÉΓòÉΓòÉ 2.133. Unsupported Adaptec IDE controllers ΓòÉΓòÉΓòÉ Unsupported Adaptec IDE controllers ACB-2320 ACB-2322 ACB-2320A ACB-2322A ACB-2322B ACB-2322B-8 ACB-2620 ΓòÉΓòÉΓòÉ 2.134. Can not install with AOX Micromaster 486/33 ΓòÉΓòÉΓòÉ Can not install with AOX Micromaster 486/33 Disable the board and then install, the boards works fine once OS/2 is installed. ΓòÉΓòÉΓòÉ 2.135. Installing 2.1 over another version of OS/2 and various devices to not work after install. ΓòÉΓòÉΓòÉ Installing 2.1 over another version of OS/2 and various devices to not work after install. 2.1 REM's out line in config.sys it does not understand. Usually unremm'ing the lines works unless the existing driver does not work with OS/2 2.1. Recommend contacting manufacturer of the program or device for an updated driver. ΓòÉΓòÉΓòÉ 2.136. OSO001.MSG message not found while on disk1 during initial install ΓòÉΓòÉΓòÉ OSO001.MSG message not found while on disk1 during initial install Kernal can not find CDROM drive 1. Check CDROM drive for CDROM present 2. Unrecognized CDROM, SUPPORTED DRIVERS? 3. Unrecognized SCSI adapter (TRANTOR, Ultrastor) ΓòÉΓòÉΓòÉ 2.137. OS/2 2.1 and do NOT install WIN-OS/2 or DOS Support and system does not boot after install ΓòÉΓòÉΓòÉ OS/2 2.1 and do NOT install WIN-OS/2 or DOS Support and system does not boot after install REM out DEVICE=X:\OS2\MDOS\VVGA.SYS ΓòÉΓòÉΓòÉ 2.138. Failure on install diskette, disk1, disk2 ΓòÉΓòÉΓòÉ Failure on install diskette, disk1, disk2 1. Ensure floppy drive is jumered for AT mode 2. Make sure the BIOS hasn't been modified by the motherboard manufacturer and had change line support enabled. PJ05147 corrects this problem. 3. Disable CACHE ΓòÉΓòÉΓòÉ 2.139. Failure after DISKETTE 5 ΓòÉΓòÉΓòÉ Failure after DISKETTE 5 Video mode may have been incorrectly identified. Disk type may have been incorrectly identified. ΓòÉΓòÉΓòÉ 2.140. Failure after DISKETTE 6 ΓòÉΓòÉΓòÉ Failure after DISKETTE 6 ON some OEM machines unpack will go into a tight loop and hang install. Usually restarting installation fixes problem. ΓòÉΓòÉΓòÉ 2.141. Hang on Disk #17 or after workaround ΓòÉΓòÉΓòÉ Hang on Disk #17 or after workaround 1. Reboot with install disk, disk1 and then ESC to A prompt 2. Type X: were x=drive installed 3. Type CD\OS2 4. Type DIR *.* >SVGADATA.PMI 5. Type SETVGA (it will ask for display disk1, if installing from CDROM make the disk image using LOADDSKF as documented) 6. Reboot 7. After desktop, go to OS/2 window and type DSPINSTL for correct resolution 8. Reboot 9. Do a selective install for printer and WIN-OS2 support ΓòÉΓòÉΓòÉ 3. Informational APARs ΓòÉΓòÉΓòÉ Informational APARs ΓòÉΓòÉΓòÉ 3.1. APAR II06078 ΓòÉΓòÉΓòÉ APAR II06078 FDISK INSTALLATION PROBLEMS Model 90 with 2.88 drive needs at least 1.3.02 release for 1.3. Customer can install a 1.44 drive or use 1.3.03 to install on a 2.88 drive because of hardware upgrades. The symptom is Can not find country.sys error *** 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. ΓòÉΓòÉΓòÉ 3.2. APAR II06081 ΓòÉΓòÉΓòÉ APAR II06081 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. ΓòÉΓòÉΓòÉ 3.3. APAR PJ03721 ΓòÉΓòÉΓòÉ APAR PJ03721 OEM MACHINES WITH WESTERN DIGITAL SUPER VGA VIDEO THAT HAVE 1 MG VIDEO MEMORY CRASH AFTER FIRST BOOT THEN THE C0000005 MSG OCCURS AN INSTALLATION PROBLEM OCCURS ON OEM MACHINES WITH THE WESTERN DIGITAL SUPER VGA VIDEO CHIP, WHICH HAVE 1 MG. OF VIDEO MEMORY. * THE SYSTEM IS DETECTING THAT THE VIDEO ADAPTER FALSELY HAS 2 MG. OF VIDEO MEMORY INSTEAD OF 1 MG. OF ACTUAL MEMORY. THIS CAUSES THE SYSTEM TO CRASH. AFTER THAT A MESSAGE NUMBER APPEARS ON THE SCREEN: C0000005 * THE BVHSVGA.DLL NEEDS TO BE REPLACED WITH THE CORRECTED FILE BY WAY OF THIS APAR. * IN THE MEANWHILE, ALL REFERENCES TO SVGA MENTIONED IN THE CONFIG.SYS NEED TO BE REMMED-OUT UNTIL THE CORRECTION IS MADE IN ORDER TO BYPASS THIS INSTALLATION ERROR, AND USE THE VGA INSTALLATION FILES INSTEAD. PROBLEM SUMMARY: An installation problem occurs on OEM machines with the Western Digital super VGA video chip, which has 1MB of video memory. This occurs when the base 512K VRAM is upgraded with an additional 512K for 1MB total. If the extra 512K is removed, the system boots normally. PROBLEM CONCLUSION: The problem has been fixed and system now detects 1mb on adapter. New BVHSVGA.DLL is also available. ΓòÉΓòÉΓòÉ 4. README files ΓòÉΓòÉΓòÉ README files ΓòÉΓòÉΓòÉ 4.1. OS/2 2.1 README file ΓòÉΓòÉΓòÉ OS/2 2.1 README file OS/2 2.1 - README _________________ Welcome to OS/2* 2.1. This readme contains helpful hints found in our testing as well as updated information that did not make our printed publications. It is divided into the following categories: o General System Considerations o WIN-OS/2 Application Compatibility o DOS Application Compatibility o OS/2 Application Compatibility o DOS and WIN-OS/2 Multimedia Application Compatibility o Network o Advanced Power Management o Display adapters o Audio Adapters o Printers o Scanners o Mahjongg Game o Trademarks and Service Marks A separate Readme file for MMPM/2 is contained in the MMPM/2 program. GENERAL SYSTEM CONSIDERATIONS o OS/2 2.1 uses a system proportional font that is designed to meet the International Standards Organization (ISO) 9241 standard and the German DIN 66234 standard on suitable hardware. ISO compliant fonts cause some text strings to be clipped. If you do not want to use ISO compliant fonts, modify the OS2.INI file to install fonts that are not ISO compliant. Font changes made in the OS2.INI file are global across all applications. If you have REXX installed, you can type the following information into a CMD file and use it to change the font. /* */ call RxFuncAdd "SysIni", "RexxUtil", "SysIni" AppName = "PM_SystemFonts" KeyName = "DefaultFont" FontName = "10.System Proportional Non-ISO" call SysIni "USER", AppName, KeyName, FontName||"0"x exit After the file has been run, shutdown and restart the system. o If you experience video corruption: - Display the pop-up menu for the desktop; then select Refresh to redraw the desktop. - If the screen goes blank, press Alt+Esc to switch between the applications to force repainting of the screen. o DOS Images on the hard disk (VMBs) need to use the FSFILTER and FSACCESS drivers provided with this version of OS/2. FSFILTER and FSACESS drivers are located in the \OS2\MDOS directory. o The Check disk option for a CD-ROM object will not display information about the CD-ROM. To obtain information about the CD-ROM: 1. Point to the CD-ROM drive object. 2. Click mouse button 2. 3. Select the arrow to the right of Open. 4. Select Details view. o During a system shutdown, there might be times when the "Shutdown is completed" message is not displayed. If this happens, wait until all disk activity is complete, then power off the system. o If you are installing OS/2 2.1 over a system that has OS/2 2.0 installed, the desktop directory name will be "OS!2_2.0_D" and the title of the desktop will be "OS/2 2.0 Desktop". On a system that has OS/2 2.1 installed, the desktop directory name will be "Desktop". o If you have a preinstalled system, and you change your country or keyboard configuration using the Configure Preinstalled System program, located in the Configuration Tools folder, the changes only occur for OS/2 sessions. To configure the country and keyboard for WIN-OS/2 sessions, use the International icon from the WIN-OS/2 Control Panel. o After installing OS/2 2.1 on your system, use the Migrate Applications program to migrate your programs instead of the Selective Install program. The Migrate Applications program is located in the System Setup folder. WIN-OS/2 APPLICATION COMPATIBILITY o The performance of Windows programs that use floating point operations can be improved by changing the WIN-OS/2* setting, WIN_RUN_MODE, to Enhanced Compatibility. o Windows scanning programs should be run in a WIN-OS/2 full-screen session to avoid video corruption. o To ensure the integrity of 16-color bit maps on SVGA, XGA, and 8514 systems, run Microsoft Paint Brush in a WIN-OS/2 full-screen session. o Some messages encountered in a WIN-OS/2 window session request that you select either Ignore or Close, however the only options are Ignore and OK. Select OK instead of Close. o If you are using a WIN-OS/2 window session, an OS/2 Presentation Manager session, and a DOS full-screen session, Alt+Esc might not sequence through all of the windows correctly. Alt+Esc might switch to the WIN-OS/2 session every other time or the DOS full-screen session might never be displayed. To avoid this problem, press Ctrl+Esc or press mouse buttons 1 and 2 at the same time to display the Window List then select the desired session. o If you are in a full-screen WIN-OS/2 session and you encounter a problem where transparent desktop icons appear over open windows, minimize or maximize the window to force repainting. o The Copy Disk option for the WIN-OS/2 File Manager does not prompt for a target diskette. Use the DISKCOPY command in either a DOS or OS/2 command prompt session instead. o During installation of the Windows 3.1 SDK, a message is displayed stating that the installation program cannot find KRNL286.EXE or KRNL386.EXE. Ignore the message and continue installation. The SDK will function normally. o If you are using the Winsleuth Gold hardware diagnostics program: - Do not run Chip test (RAM test program). Chip test attempts to lock hardware interrupts. OS/2 2.1 does not allow programs to lock hardware interrupts. - When the video mode hardware test switches from character to graphics mode, a "suspended" message might appear. If the message appears, Select Full-screen from the Sessions System menu. Testing will resume. APPLICATION NOTES: Access Dr. Watson** Hollywood** WinRoach** ------------------------------------------ Run in a WIN-OS/2 full-screen session. AmiPro** 2.0 and 3.0 -------------------- Equation symbols might be incorrect after certain printer drivers are installed for: ATM fonts --------- WIN-OS/2 ships with ATM fonts Version 2.5. If you were using a previous version of ATM fonts with your Windows programs, you can upgrade to the new ATM fonts provided by WIN-OS/2. See the "OS/2 2.1 Using the Operating System" book for instructions. Borland Turbo and Pascal debugger ---------------------------------- Run in a full-screen session. CorelDRAW 2.0 ------------- Install from a DOS or OS/2 session. CorelDRAW 2.5 ------------- At the end of CorelDRAW 2.5 installation, you might experience problems, after selecting one of the View readme options. The View readme options are "Yes" and "No". If you select Yes, CorelDRAW will not run. Icons will be generated. You must restart your system and recreate each icon, using the Migrate Applications program. If you select No, CorelDRAW will not run. A folder will be appear without icons. You must restart your system and create each icon, using the Migrate Applications program. For information on the Migrate Applications program, refer to the OS/2 2.1 Using the Operating System book. Facelift** Fonts ---------------- Modify the SYSTEM.INI file after the fonts are installed: 1. Edit the SYSTEM.INI file in the \OS2\WINOS2 directory. 2. Change the sdisplay.drv= line to sdisplay.org=. 3. Copy the display.drv= line to the next line in the file. Add an "s" to the beginning of the new (copied) line. 4. Save and exit the file. 5. Restart WIN-OS/2. FoxPro** 2.5 ------------ Install using a WIN-OS/2 Enhanced-compatibility mode session, but run in a WIN-OS/2 standard-mode session FrameMaker** ------------ Use a mouse to select table cells. Microsoft Windows Printing System --------------------------------- The OS/2 spooler must be disabled. If you are using a parallel printer, direct the output of the printer to LPT1 instead of LPT1.OS2. Norton Desktop 2.0 ------------------ Run in a WIN-OS/2 full-screen standard-mode session. Paint Brush** ------------- To ensure the integrity of 16-color bit maps on SVGA, XGA, and 8514 systems, run Paint Brush in a WIN-OS/2 full-screen session. If you are using the Paint Brush program in a WIN-OS/2 window session, the mouse pointer/hourglass will not disappear when the Zoom In option is selected from the View menu. In a full-screen WIN-OS/2 session, the mouse pointer/hourglass will disappear and only the Zoom In box will remain on the screen. If you are using Paint Brush to paint single pixels in zoom-in mode, the pixel will look unpainted where the mouse pointer covers the pixel being painted. Zoom out and in again to see the entire pixel painted correctly. Powerpoint** 3.0 ---------------- If you are displaying the DROPBXV.PPT and GRIDWRVK.PPT demo slides in 640x480x256, you might see small horizontal line corruption. If you are using a WIN-OS/2 window, you might get incorrect background color when viewing a thumbnail of a template. This will not affect the running of the application. Video for Windows ----------------- Run is a full-screen session. If you configure video animation to run full-screen in Video playback, Deselect Skip video frames if behind, to eliminate any corruption of the video during play. WindowWorks** ------------- Install in a WIN-OS/2 full-screen session. Lotus Improv 2.0 for Windows ---------------------------- Must be installed with WIN-OS/2 running in enhance mode, to install and configure correctly. DOS APPLICATION COMPATIBILITY o Use OS/2 system utilities. DOS system utilities might not recognize the extended attributes associated with a file. o OS/2 provides integral disk caching and memory optimization functions. Use of the equivalent functions that are provided with MS-DOS 6.0 is not necessary and may produce errors. APPLICATION NOTES: DOS Games --------- For performance reasons, play in a DOS full-screen session. Change the DOS setting, VIDEO_8514A_XGA_IOTRAP to OFF. Fotoman** --------- If you have problems running Fotoman, set the DOS COM_DIRECT_ACCESS setting ON. Freelance Graphics** -------------------- If you are using Freelance in a WIN-OS/2 window, you might get incorrect background color when viewing a thumbnail of a template. This will not affect the running of the application. Wayne Gretsky's Hockey Game --------------------------- Not supported. Wing Commander** II ------------------- Set HW_TIMER to OFF. Terminator game --------------- Must use a joystick. Microsoft MSCDEX ---------------- Change the DOS INT_DURING_IO setting to ON. Intel** SatisFAXtion** ---------------------- Must be run in a specific DOS session, unless you do the following before you install the program: 1. Make a copy of your AUTOEXEC.BAT file and name it AUTOEXEC.FAX. 2. Install the program. 3. Rename the AUTOEXEC.BAT file FAX.BAT. 4. Rename the AUTOEXEC.FAX file AUTOEXEC.BAT. 5. Make a program object for the SatisFAXtion program. 6. Change the value of the DOS_AUTOEXEC setting for the object to FAX.BAT. 7. Save and exit the Settings notebook. Microsoft** C/C++ 7.0 Linker -------------------------- If you are using Microsoft C/C++ 7.0 Linker, set the DPMI_DOS_API DOS setting to ENABLED. OS/2 APPLICATION COMPATIBILITY o Closing OS/2 applications that use the hardware palette (typically picture viewers or sample graphic applications) occasionally causes a repaint problem on the desktop. If the windows do not repaint correctly, a refresh will restore the desktop, but any windows that are opened or moved will still have the problem. Restarting the system is the only way to completely correct this problem. o If you are using Lotus 123G for OS/2 or Lotus Freelance Graphics for OS/2, you need to run the following utility prior to using these products with OS/2 2.1. 1. Change to the appropriate Lotus directory that contains the application. For example, type CD \123G 2. Backup the LD2CORE.DLL file. For example, type COPY LD2CORE.DLL LD2CORE.BAK 3. Run the update program. Type, LD2FIX The Lotus program is now updated. You need to shutdown and restart your system for these changes to take effect. APPLICATION NOTES: Communication Manager/2 ----------------------- When used with Host Graphics support (HGINST) you might experience shutdown problems. Ensure that the following GDDM fixes have been applied to the host system: UN36882 - MVS UN38883 - VM/SP UN38884 - VM/XA SP UN38885 - DOS/VSE Netview DM/2 (NVDM/2) --------------------- If you are using the CID method of installation, you will need an updated version of the LAPSCID.DLL file. This file is available as LAPDLL.ZIP on the CompuServe OS2SUPPORT forum, Lib #17 and the OS2BBS on TALKLINK. IBM LAN Server 2.0 and 3.0 Remote Installation Program Load (RIPL) ---------------------------------------------- An updated version is needed to run with OS/2 2.1. The diskette image is available as 2IRIPL.ZIP on the CompuServe OS2SUPPORT forum, Lib #17 and the OS2BBS on TALKLINK. WordPerfect** 5.0 for OS/2 -------------------------- If you are using SVGA hardware, you must run this application in VGA mode. DOS AND WIN-OS/2 MULTIMEDIA APPLICATION COMPATIBILITY o The following WIN-OS/2 and DOS Settings should be used for Multimedia applications: DOS/WIN INT_DURING_IO ON DOS/WIN HW_TIMER ON WIN VIDEO_SWITCH_NOTIFICATION ON WIN VIDEO_8514A_XGA_IOTRAP OFF DOS/WIN VIDEO_RETRACE_EMULATION OFF APPLICATIONS NOTES: Action!** 2.0 ------------- Run in a WIN-OS/2 full-screen session. Add the following line to the AUTOEXEC.BAT file: SET TEMP=C:\ Animation Works** 1.0 --------------------- Run in 640x480 resolution. IconAuthor** 4.0 ---------------- If you are running the demo for this program, you must exit and reenter the WIN-OS/2 session before running the actual application. Linkway** Live 1.0 (Tool Series) -------------------------------- Use the following DOS setting to make the demo run properly: DOS_RMSIZE=576 MIDI ---- Make sure that the MIDI mapper (in the Control Panel) is properly set to the sound adapter. Nautilus** 1.6 and 1.76 ----------------------- Run in a WIN-OS/2 full-screen session. NETWORK o The Workplace Shell login is not compatible with NetWare** 4.0 Directory Services and should be disabled unless you are using the NetWare 4.0 Bindery Compatibility mode. To disable the login: 1. Edit the CONFIG.SYS file. 2. Remove the CONNECTIONS option from SET AUTOSTART. 3. Save and exit the CONFIG.SYS file. 4. Restart the system to activate the changes. o If you are using the NetWare Requester version 2.01, (ships with NetWare 4.0) but have no NetWare 4.0 servers, you can increase the speed of the login process by turning the Directory Services off. To turn the services off: 1. Edit NET.CFG file in the root directory of the boot drive. 2. Add Directory Services Off to the file. 3. Save and exit the file. o Novell** NetWare Requester 2.0 and 2.01 programs NMPIPE.SYS, NPSERVER.SYS, and NPDAEMON.EXE require the following information to be added to the OS2VER file. To add this information to the file: 1. At an OS/2 command prompt, type: ATTRIB -h -r -s OS2VER 2. Edit the OS2VER file in the root directory of the boot drive. 3. Type the following information in the file: 20=NMPIPE.SYS 20=NPSERVER.SYS 20=NPDAEMON.EXE 4. Save and exit the file. 5. Type ATTRIB +h +r +s OS2VER o If you are using FFST/2 (for example, if you enable the FFST/2 feature when installing Communications Manager/2 or Data Base Manager/2), REM out the "RUN=...\EPW.EXE" statement in your CONFIG.SYS file. To utilize FFST/2 technology, add a "DETACH EPW.EXE" as the first statement in your STARTUP.CMD file. ADVANCED POWER MANAGEMENT The OS/2 2.1 APM support relies on the power status information returned from the BIOS on your laptop. You might notice incorrect battery life or status within the power icon on your laptop. If this occurs, rely on the LEDs on your laptop for accurate power status information. o Turning the APM setting to OFF also turns off the BIOS power management. If you want to turn off the APM but not the BIOS power management, place REM before the APM device driver statement in your CONFIG.SYS file, then restart your system to invoke the change. REM DEVICE=C:\OS2\APM.SYS DISPLAY ADAPTERS (IMAGE, SVGA, XGA, 8514) o The OS/2 operating system will experience video problems similar to those observed in a DOS environment. These problems are due to the failure of a BIOS video mode set. An example of this problem is the video image on an ALR** Modular PS with a Flexview** 2x SVGA display fails to occupy the entire screen in 1024 x 768 mode. o If you are using an LCD display and have difficulty locating the mouse pointer on the screen, you can increase the size of the pointer if you are using 640x480 resolution. To change the size of the pointer (if you have REXX installed): 1. Use an editor to create a file called LARGE.CMD. 2. Add the following information to the file. /* LARGE.CMD Set VGA pointers to large */ /* (c) Copyright IBM Corp. 1992, All rights reserved */ call RxFuncAdd "SysIni", "RexxUtil", "SysIni" call SysIni "USER", "PM_IBMVGA", "CURSOR_SIZE", "1", say Result exit 3. Save and exit the file. 4. At an OS/2 command prompt, type "LARGE" and press Enter. This program will increase the size of the cursor. To force a standard size pointer, replace the "1" in the program with a "2". To let the system select the size of the pointer, replace the "1" in the program with a "0". o Users of the NCR** Safari notebook, SSL/25, should modify the following information in the CONFIG.SYS file on their startup drive to allow video register shadowing to be processed correctly in OS/2 2.1: DEVICE=C:\OS2\MDOS\VVGA.SYS to DEVICE=C:\OS2\MDOS\VSVGA.SYS o Systems with Image Adapters running in dual-display modes will lose DOS window support after a DOS full-screen or OS/2 full-screen session has been invoked. The system must be restarted to reinstate the DOS window environment. The problem can be avoided by turning off the dual display mode under the Image Adapter setup. SVGA CONSIDERATIONS o The Western Digital** 90C31 SVGA chipset will have video problems when Windows 2.x applications are run. o If you are using a ZEOS** system with Speedstar** VGA, you must run the VMODE utility supplied with the system to configure the display during the display driver installation. o Zenith Data Systems** with Headland HT208 do not support high resolution modes even though you can successfully set these modes and install high resolution drivers. If a high resolution mode is used, a white half-screen will be displayed. To correct this problem, use DSPINSTL to install VGA. o If you have a Sigma Legend** display adapter you might experience minor video corruption on the desktop when you switch between the desktop and DOS if they are running in different modes. This can be corrected by using a DOS utility to set the DOS session to the same mode as the desktop. XGA CONSIDERATIONS o If an XGA-2 adapter is installed, and you have modified the default display type in the System Settings notebook (page 2), after you restart the system it will display the Workplace Shell* in one resolution and WIN-OS/2 in a different resolution. To change the resolution for the Workplace Shell: 1. Open OS/2 System. 2. Open System Setup. 3. Open System. 4. Select a 640x480xn resolution. 5. Shutdown and restart the system. 6. Repeat steps 1 through 3. 7. Select the desired resolution. 8. Shutdown and restart the system. The Workplace Shell and WIN-OS/2 will now display in the same resolution. o If you are using a dual display system with XGA as the primary display and VGA as the secondary display, you might see some minor corruption when the XGA display is set to a resolution with 65536 colors. This corruption will be on the display that does not have focus and will not interfere with the operation of the system. o On dual display configurations with XGA-2 as the primary display and VGA as the secondary display, the DOS full-screen session might be corrupted if a Windows** application is started in a window session. To recover from this situation, shutdown and restart the system. o If you are using Dual Boot with an XGA-2 adapter, you must modify the CONFIG.DOS file: 1. Edit the \OS2\SYSTEM\CONFIG.DOS file. 2. Locate the line DEVICE=C:\DOS\EMM386.EXE RAM 2048 X=nnnn-nnnn 3. Change nnnn-nnnn to C000-CFFF. 4. Save and exit the file. o On IBM P75 systems, there might be some corruption on the screen whenever several icons are selected and moved together. This corruption can be eliminated by clicking mouse button 2 to bring up the pop-up menu; then selecting Sort. o An IBM P75 system with an external monitor attached might only have the 640x480x16 resolution selection on the the System Settings Screen page. If the external monitor is capable of displaying higher resolutions, use the P75 reference diskette to disable the built-in plasma display. o If you are using an XGA system, the hash lines around the icons of open applications might change color unexpectedly. This does not interfere with the operation of the system. o If you are using an XGA system, extra lines might appear on the face of the OS/2 System Clock between the quarter (:15) and half (:30) hour. These lines do not interfere with the operation of the clock. 8514 CONSIDERATIONS o If you are using the 1MB version of an ATI** Graphics Ultra** Pro adapter, the VGA memory must be set to SHARED to work properly with the OS/2 8514 display driver. This might cause some DOS applications running in the background to corrupt the desktop. To correct this problem, you must upgrade to the 2MB version of the Graphics Ultra Pro and set the VGA memory to 256K or greater. NOTE: In the "OS/2 Installation Guide", it states that the ATI Graphics Ultra Pro must be configured to IBM DEFAULT for the 640x480 display type. This setting might be referred to as 60Hz rather than IBM DEFAULT. o If you are using a system with an 8514 adapter with Windows applications running in a WIN-OS/2 window session in separate VDMs, video corruption might occur in bitmaps when clipping between applications. o After you start a WIN-OS/2 window session, 256 color bitmaps might become discolored due to the sharing of the 256 color palette. This should not affect the running of the applications. o Selecting windows in Mathematica might not bring focus to the proper window. AUDIO ADAPTERS Audio support in WIN-OS/2 and DOS sessions is dependent on installed drivers. You should install the audio adapter driver that came with your audio adapter. When installing audio support for WIN-OS/2, be sure to install both DOS and Windows device drivers. Configure both drivers to use the same interrupt level and DMA channel. o The following drivers are available with the Audio Capture and Playback Adapter* (ACPA): - ACPADD.SYS - ACPADD2.SYS - ACPAK12.SYS - ACPA.DRV The latest updates are available on the IBM Bulletin Board Service. o MMPM/2 installs ACPA support for OS/2 only, not WIN-OS/2 or DOS. There are two ways to get DOS ACPA support in DOS sessions: 1. Edit the CONFIG.SYS file. 2. Add DEVICE=C:\ACPAK12.SYS 3. Save and exit the CONFIG.SYS file. 4. Copy the ACPAK12.SYS file to the C:\ directory. 5. Restart the system to activate the changes. Or 1. Point to the DOS full-screen or window object. 2. Click mouse button 2. 3. Select the arrow to the right of Open. 4. Select Settings. 5. Select the Session tab. 6. Select DOS Settings. 7. Select DOS_DEVICE. 8. Type C:\ACPAK12.SYS in the Value field. 9. Select Save. 10. Double-click on the title-bar icon to close the notebook. 11. Copy the ACPAK12.SYS file to the C:\ directory. To install WIN-OS/2 ACPA support: 1. Access the Control Panel in WIN-OS/2 Main. 2. Select Drivers. 3. Select Add. 4. Select Unlisted or Updated Drivers. 5. Select OK. 6. Insert the diskette containing the ACPA driver into drive A. 7. Type A: 8. Select OK. 9. When the next menu level appears, select the M-Audio sound driver. o MMPM/2 installs Sound Blaster** support for OS/2 only, not WIN-OS/2 or DOS. o To add WIN-OS/2 Sound Blaster support: 1. Install the DOS device driver following the instructions that came with the adapter. Use an OS/2 DOS session for the install. 2. Install the Windows driver. NOTE: Be sure to use the same I/O address, interrupt, and DMA settings used during install of the DOS drivers. PRINTERS o If you are using the HP** LaserJet** printer driver, some complex images might not print correctly when LaserJet performance options are enabled. If you experience incorrect output or degraded printer performance, return the performance options to the disabled state. To change the performance options: 1. Point to the printer object. 2. Click mouse button 2. 3. Select the arrow to the right of Open. 4. Select Settings. 5. Select the Printer Drivers tab. 6. Select Job properties. 7. Change the performance options to their default settings. 8. Double-click on the title-bar icon to close the notebook. o If you experience problems while printing bitmaps from an application while using the PostScript printer driver, Select the Printer-specific format option on the Queue options page in the Settings notebook of your printer object. o The OS/2 printer drivers on the OS/2 2.1 printer driver diskettes are stored in a packed format that is not compatible with OS/2 1.3 or 2.0. To install one of the OS/2 2.1 printer drivers on a system with OS/2 1.3 or 2.0 installed, you must first unpack the driver on a system that has OS/2 2.1 installed. You do not have to complete these steps to install a printer driver on a system that already has OS/2 2.1 installed. NOTE: Do not install the new 32-bit PostScript driver (PSCRIPT.DR_) that came with OS/2 2.1 on a system with OS/2 1.3 or 2.0 installed. It is not compatible with these versions of OS/2. While testing is continuing, current compatibility information about tested systems is available through your dealer, Marketing Representative, CompuServe, IBM National Support Center Bulletin Board System (NSC BBS), and IBMLink. To unpack a printer driver for use on a OS/2 1.3 or OS/2 2.0 system, complete the following steps on your system that has OS/2 2.1 installed. 1. Open an OS/2 command prompt. 2. Type: MD X:\DRIVER Where X is a drive on your system. 3. Insert into drive A the OS/2 2.1 printer driver diskette that contains the printer driver you want to install. The printer driver names end in a "_". Printer Driver: Diskette # Packed Name: IBM Null 1 IBMNULL.DR_ HP LaserJet 1 LASERJET.DR_ HP DeskJet 1 HPDJPM.DR_ IBM 52XX 1 IBM52XX.DR_ Epson 1 EPSON.DR_ Plotter Driver 1 PLOTTERS.DR_ IBM 4019 2 IBM4019.DR_ IBM 42XX 2 IBM42XX.DR_ IBM 5201-2 2 IBM52012.DR_ PaintJet 3 SMGXPJET.DR_ 4. Type: UNPACK A:\Packed name X:\DRIVER Where X is a drive on your system. For example if you want to install the Epson printer driver, type : UNPACK A:\EPSON.DR_ X:\DRIVER The printer driver files are now unpacked in the X:\DRIVER directory. 5. Copy the driver files to a diskette and install them onto your OS/2 1.3 or 2.0 system. SCANNERS If you have a Logitech hand scanner on an AT bus computer, run the scanner at the 100, 200, or 300 DPI setting. MAHJONGG GAME OS/2 2.1 includes a new tile-matching game called Mahjongg Solitaire. To install Mahjongg Solitaire from diskettes: 1. Insert Diskette 11 into drive A. 2. Open an OS/2 command prompt. 3. Type: UNPACK A:MAHJONGG drive: where drive is the drive letter of the partition OS/2 2.1 is installed on. 4. Press Enter. 5. Type: MAHINST and press Enter. Then, follow the instructions on the screen. To install Mahjongg Solitaire from CD: 1. Insert the CD into the CD drive. 2. Open an OS/2 command prompt. 3. Type: UNPACK cddrive:\OS2SE21\DISK_11\MAHJONGG drive: where cddrive is the drive letter of the CDROM and drive is the drive letter of the partition OS/2 2.1 is installed on. 4. Press Enter. 5. Type: MAHINST and press Enter. Then, follow the instructions on the screen. TRADEMARKS AND SERVICE MARKS ____________________________ The following terms, denoted by an asterisk (*) in this README, are trademarks or registered trademarks of the IBM Corporation in the United States or other countries: Audio Capture and Playback Adapter ------------------------------------------ IBM ------------------------------------------ Linkway ------------------------------------------ Micro Channel ------------------------------------------ Multimedia Presentation Manager/2 ------------------------------------------ OS/2 ------------------------------------------ WIN-OS/2 ------------------------------------------ Workplace Shell ------------------------------------------ XGA ------------------------------------------ The following terms, denoted by a double asterisk (**) in this README, are trademarks of other companies as follows: Trademark: Owner: -------------------------------------------------------------- Action! Expertelligence -------------------------------------------------------------- ALR Advanced Logic Research, Inc. -------------------------------------------------------------- Animation Works Gold Disk Inc. -------------------------------------------------------------- APM Astek International Ltd. -------------------------------------------------------------- ATI ATI Technologies, Inc. -------------------------------------------------------------- CompuServe CompuServe Inc. -------------------------------------------------------------- Describe Lenname Advanced Products -------------------------------------------------------------- Facelift Bitstream Inc. -------------------------------------------------------------- Flexview Nutmeg Systems -------------------------------------------------------------- Fotoman Logitech International -------------------------------------------------------------- FoxPro Fox Holdings, Inc. -------------------------------------------------------------- FrameMaker Frame Technologies Inc. -------------------------------------------------------------- Hollywood Claris Corporation -------------------------------------------------------------- HP Hewlett-Packard Company -------------------------------------------------------------- HP LaserJet Hewlett Packard -------------------------------------------------------------- Intel Intel Corporation -------------------------------------------------------------- Legend Sigma Designs Inc. -------------------------------------------------------------- Logitech Logitech, Inc. -------------------------------------------------------------- Freelance Graphics Lotus Development Corporation -------------------------------------------------------------- IconAuthor Aimtech Corporation -------------------------------------------------------------- Legend Sigma Designs, Inc. -------------------------------------------------------------- Logitech Logitech, Inc. -------------------------------------------------------------- Microsoft Microsoft Corporation -------------------------------------------------------------- Nautilus Softshell Systems -------------------------------------------------------------- NCR NCR Corporation -------------------------------------------------------------- NET NCR Corporation -------------------------------------------------------------- NetWare Novell, Inc. -------------------------------------------------------------- Novell Novell, Inc. -------------------------------------------------------------- Paint Brush Microsoft Corporation -------------------------------------------------------------- Panasonic Matsushita Electric Industrial Co., Ltd. -------------------------------------------------------------- PostScript Adobe Systems Inc. -------------------------------------------------------------- Powerpoint Microsoft Corporation -------------------------------------------------------------- Sound Blaster Creative Labs, Inc. -------------------------------------------------------------- SpeedStar Diamond Computer Systems, Inc. -------------------------------------------------------------- Ultra ATI Technologies, Inc. -------------------------------------------------------------- Western Digital Western Digital Corporation -------------------------------------------------------------- Windows Microsoft Corporation -------------------------------------------------------------- WindowWorks Spinnaker Software Corporation -------------------------------------------------------------- WordPerfect WordPerfect Corporation -------------------------------------------------------------- Zenith Data Systems Zenith Electronics Corporation -------------------------------------------------------------- ZEOS ZEOS International Ltd. -------------------------------------------------------------- IBM DISCLAIMS ALL WARRANTIES, WHETHER EXPRESSED OR IMPLIED, INCLUDING WITHOUT LIMITATION, WARRANTIES OF FITNESS AND MERCHANTABILITY WITH RESPECT TO THE INFORMATION IN THIS DOCUMENT. BY FURNISHING THIS DOCUMENT, IBM GRANTS NO LICENSES TO ANY RELATED PATENTS OR COPYRIGHTS. Copyright IBM Corporation, 1993, all rights reserved. ΓòÉΓòÉΓòÉ 4.2. OS/2 For Windows 2.1 README file ΓòÉΓòÉΓòÉ OS/2 For Windows 2.1 README file OS/2 2.1 Special Edition for Use with Windows Version 3.1 - README __________________________________________________________________ Thank you for purchasing a copy of OS/2* 2.1 Special Edition. This product is designed for licensed users of Microsoft** Windows** Version 3.1 product. After the installation of this product, your system will allow you to run DOS, Windows, and OS/2 applications. Throughout the documentation provided with this product, all references to WIN-OS/2* apply to running your Windows Version 3.1 programs under the special edition. This README contains helpful hints found in our testing as well as updated information that did not make our printed publications. You can use the Find option in the Edit menu to help you locate information in this README. It is divided into the following categories: o General System Considerations o International Standards Organization (ISO) Fonts o CD-ROM o Dual Boot and Boot Manager o WIN-OS/2 Application Compatibility o DOS Application Compatibility o OS/2 Application Compatibility o DOS and WIN-OS/2 Multimedia Application Compatibility o Network o Advanced Power Management o Display adapters o Audio Adapters o Printers o Scanners o Mahjongg Game o Trademarks and Service Marks A separate README file for MMPM/2 is contained in the MMPM/2 program. GENERAL SYSTEM CONSIDERATIONS o If you experience video corruption: - Display the pop-up menu for the desktop; then select Refresh to redraw the desktop. - If the screen goes blank, press Alt+Esc to switch between the applications to force repainting of the screen. o DOS Images on the hard disk (VMBs) need to use the FSFILTER and FSACCESS drivers provided with this version of OS/2. FSFILTER and FSACESS drivers are located in the \OS2\MDOS directory. o During a system shutdown, there might be times when the "Shutdown is completed" message is not displayed. If this happens, wait until all disk activity is complete, then power off the system. o If you are installing OS/2 2.1 Special Edition over a system that has OS/2 2.0 installed, the desktop directory name will be "OS!2_2.0_D" and the title of the desktop will be "OS/2 2.0 Desktop". On a system that has OS/2 2.1 installed, the desktop directory name will be "Desktop". o After installing OS/2 2.1 Special Edition on your system, use the Migrate Applications program to migrate your programs instead of the Selective Install program. The Migrate Applications program is located in the System Setup folder. o It is recommended that you do not turn "ON" both the OS/2 and the Windows screen savers at the same time. INTERNATIONAL STANDARDS ORGANIZATION (ISO) FONTS o OS/2 2.1 Special Edition uses a system proportional font that is designed to meet the International Standards Organization (ISO) 9241 standard and the German DIN 66234 standard when using ISO compliant hardware. ISO compliant fonts cause some text strings to be clipped. If you do not want to use ISO compliant fonts, modify the OS2.INI file to install fonts that are not ISO compliant. Font changes made in the OS2.INI file are global across all applications. If you have REXX installed, you can type the following information into a CMD file and use it to change the font. /* */ call RxFuncAdd "SysIni", "RexxUtil", "SysIni" AppName = "PM_SystemFonts" KeyName = "DefaultFont" FontName = "10.System Proportional Non-ISO" call SysIni "USER", AppName, KeyName, FontName||"0"x exit After the file has been run, shutdown and restart the system. CD-ROM o The Check disk option for a CD-ROM object will not display information about the CD-ROM. To obtain information about the CD-ROM: 1. Point to the CD-ROM drive object. 2. Click mouse button 2. 3. Select the arrow to the right of Open. 4. Select Details view. DUAL BOOT AND BOOT MANAGER o If you use the Dual Boot or Boot Manager feature to switch to DOS, be aware of the following restrictions on installing and running programs under DOS: - If you install a Windows application that updates the AUTOEXEC.BAT or the CONFIG.SYS file, you must migrate the application after you switch back to the OS/2 operating system, and update the OS/2 versions of AUTOEXEC.BAT and CONFIG.SYS. - Do not run the Windows Setup program. We recommend that you do not change your video configuration for Windows. WIN-OS/2 APPLICATION COMPATIBILITY o The performance of Windows programs that use floating point operations can be improved by changing the WIN-OS/2* setting, WIN_RUN_MODE, to Enhanced Compatibility. For more information about WIN-OS/2 settings, refer to the Master Help Index. o Windows scanning programs should be run in a WIN-OS/2 full-screen session to avoid video corruption. o To ensure the integrity of 16-color bit maps on SVGA, XGA, and 8514 systems, run Microsoft Paint Brush** in a WIN-OS/2 full-screen session. o Some messages encountered in a WIN-OS/2 window session request that you select either Ignore or Close, however the only options are Ignore and OK. Select OK instead of Close. o If you are using a WIN-OS/2 window or full-screen session, an OS/2 Presentation Manager session, and a DOS full-screen session, Alt+Esc might not sequence through all of the windows correctly. Alt+Esc might switch to the WIN-OS/2 session every other time or the DOS full-screen session might never be displayed. To avoid this problem, press Ctrl+Esc or press mouse buttons 1 and 2 at the same time to display the Window List then select the desired session. o If you are in a full-screen WIN-OS/2 session and you encounter a problem where transparent desktop icons appear over open windows, minimize or maximize the window to force repainting. o If you are using the Winsleuth Gold hardware diagnostics program: - Do not run Chip test (RAM test program). Chip test attempts to lock hardware interrupts. OS/2 2.1 Special Edition does not allow programs to lock hardware interrupts. - When the video mode hardware test switches from character to graphics mode, a "suspended" message might appear. If the message appears, Select Full-screen from the Sessions System menu. Testing will resume. WIN-OS/2 APPLICATION NOTES: Access Dr. Watson** Hollywood** WinRoach** ------------------------------------------ Run in a WIN-OS/2 full-screen session. AmiPro** 2.0 and 3.0 -------------------- Equation symbols might be incorrect after certain printer drivers are installed. The following printer drivers might cause a problem: - Canon** BubbleJet - HP DeskJet** - HP LaserJet II - HP LaserJet III - HP Plotter Borland Turbo and Pascal debugger ---------------------------------- Run in a full-screen session. CorelDRAW 2.0 ------------- Install from a DOS or OS/2 session. Facelift** Fonts ---------------- Modify the SYSTEM.INI file after the fonts are installed: 1. Edit the SYSTEM.INI file in the directory where your Windows files reside. 2. Change the sdisplay.drv= line to sdisplay.org=. 3. Copy the display.drv= line to the next line in the file. Add an "s" to the beginning of the new (copied) line. 4. Change the fdisplay.drv= line to fdisplay.org=. 5. Copy the display.drv= line to the next line in the file. Add an "f" to the beginning of the new (copied) line. 6. Save and exit the file. 7. Restart WIN-OS/2. FormBase** 1.1 -------------- When you install Formbase, do not select to modify the CONFIG.SYS file. Modifying the CONFIG.SYS file damages the integrity of the file and your system. FoxPro** 2.5 ------------ Install using a WIN-OS/2 Enhanced-compatibility mode session, but run in a WIN-OS/2 standard-mode session FrameMaker** ------------ Use a mouse to select table cells. Lotus Freelance Graphics** -------------------------- Run the Tutorial in a WIN-OS/2 full-screen session. If you are using Freelance in a WIN-OS/2 window, you might get incorrect background color when viewing a thumbnail of a template. This will not affect the running of the application. Lotus** Improv 2.0 for Windows ---------------------------- Must be installed with WIN-OS/2 running in enhance mode, to install and configure correctly. Microsoft Windows Printing System --------------------------------- The OS/2 spooler must be disabled. If you are using a parallel printer, direct the output of the printer to LPT1 instead of LPT1.OS2. Norton Desktop 2.0 ------------------ Run in a WIN-OS/2 full-screen standard-mode session. Powerpoint** 3.0 ---------------- If you are displaying the DROPBXV.PPT and GRIDWRVK.PPT demo slides in 640x480x256, you might see small horizontal line corruption. If you are using a WIN-OS/2 window, you might get incorrect background color when viewing a thumbnail of a template. This will not affect the running of the application. Video for Windows ----------------- Run in a full-screen session. If you configure video animation to run full-screen in Video playback, Deselect Skip video frames if behind, to eliminate any corruption of the video during play. WindowWorks** ------------- Install in a WIN-OS/2 full-screen session. WinTach** --------- Run this application in a WIN-OS/2 full screen session. DOS APPLICATION COMPATIBILITY o Use OS/2 system utilities. DOS system utilities might not recognize the extended attributes associated with a file. o OS/2 provides integral disk caching and memory optimization functions. Use of the equivalent functions that are provided with MS-DOS 6.0 is not necessary and may produce errors. o To display the DOS bar in a DOS full-screen or window session, add $i to the PROMPT statement in the AUTOEXEC.BAT file. For example, type: PROMPT $i$p$g Save the modified AUTOEXEC.BAT file. To restart your system, press and hold Ctrl + Alt keys; then press Del. o If your application uses its own DOS Protect Mode Interface (DPMI), set the DPMI_DOS_API DOS setting to ENABLED. Example applications include: - Microsoft C/C++ 7.0 Linker - Borland** C - C++** - Turbo** C - Paradox** DOS APPLICATION NOTES: DOS Games --------- For performance reasons, play in a DOS full-screen session. Change the DOS setting, VIDEO_8514A_XGA_IOTRAP to OFF. For more information about DOS settings, refer to the Master Help Index. Fotoman** --------- If you have problems running Fotoman, set the DOS COM_DIRECT_ACCESS setting ON. Wayne Gretzky's Hockey Game --------------------------- Not supported. Wing Commander** II ------------------- Set HW_TIMER to OFF. Terminator game --------------- Must use a joystick. Microsoft MSCDEX ---------------- Change the DOS INT_DURING_IO setting to ON. Intel** SatisFAXtion** ---------------------- Must be run in a specific DOS session, unless you do the following before you install the program: 1. Make a copy of your AUTOEXEC.BAT file and name it AUTOEXEC.FAX. 2. Install the program. 3. Rename the AUTOEXEC.BAT file FAX.BAT. 4. Rename the AUTOEXEC.FAX file AUTOEXEC.BAT. 5. Make a program object for the SatisFAXtion program. 6. Change the value of the DOS_AUTOEXEC setting for the object to FAX.BAT. 7. Save and exit the Settings notebook. OS/2 APPLICATION COMPATIBILITY o Closing OS/2 applications that use the hardware palette (typically picture viewers or sample graphic applications) occasionally causes a repaint problem on the desktop. If the windows do not repaint correctly, a refresh will restore the desktop, but any windows that are opened or moved will still have the problem. Restarting the system is the only way to completely correct this problem. o If you are using Lotus 123G for OS/2 or Lotus Freelance Graphics for OS/2, you might experience problems using large bit maps. To correct this problem, you need to run the following utility prior to using these products with OS/2 2.1 Special Edition. 1. Change to the appropriate Lotus directory that contains the application. For example, type: CD \123G 2. Backup the LD2CORE.DLL file. For example, type: COPY LD2CORE.DLL LD2CORE.BAK 3. Run the update program. Type: LD2FIX The Lotus program is now updated. You need to shutdown and restart your system for these changes to take effect. o Do not run an OS/2 screen saver and a Windows screen saver, or multiple Windows screen savers at the same time. OS/2 APPLICATION NOTES: Communication Manager/2 ----------------------- When used with Host Graphics support (HGINST) you might experience shutdown problems. Ensure that the following Graphical Data Display Manager (GDDM) fixes have been applied to the host system: UN36882 - MVS UN38883 - VM/SP UN38884 - VM/XA SP UN38885 - DOS/VSE CorelDRAW 2.5 ------------- At the end of CorelDRAW 2.5 installation, you might experience problems, after selecting one of the View README options. The View README options are "Yes" and "No". If you select Yes, CorelDRAW will not run. Icons will be generated. You must restart your system and recreate each icon, using the Migrate Applications program. If you select No, CorelDRAW will not run. A folder will appear without icons. You must restart your system and create each icon, using the Migrate Applications program. For information on the Migrate Applications program, refer to the "OS/2 2.1 Using the Operating System" book. Netview DM/2 (NVDM/2) --------------------- If you are using the CID method of installation, you will need an updated version of the LAPSCID.DLL file. This file is available as LAPDLL.ZIP on the CompuServe OS2SUPPORT forum, Lib #17 and the OS2BBS on TALKLINK. WordPerfect** 5.2 ----------------- If this application is installed on your system and you reinstall OS/2, do the following: 1. Change to the appropriate WordPerfect directory that contains the application. 2. Type: INSTALL /WPS The WordPerfect application is now updated. You need to shutdown and restart your system for these changes to take effect. IBM LAN Server 3.0 Remote Installation Program Load (RIPL) ---------------------------------------------- An updated version from version 3.0 is needed to run with OS/2 2.1 Special Edition. Use diskette image that is available as 21SERIPL.ZIP on the CompuServe OS2SUPPORT forum, Lib #17 and the OS2BBS on TALKLINK to run RIPL with OS/2 2.1 Special Edition. DOS AND WIN-OS/2 MULTIMEDIA APPLICATION COMPATIBILITY o The following WIN-OS/2 and DOS Settings should be used for Multimedia applications: DOS/WIN INT_DURING_IO ON DOS/WIN HW_TIMER ON WIN VIDEO_SWITCH_NOTIFICATION ON WIN VIDEO_8514A_XGA_IOTRAP OFF DOS/WIN VIDEO_RETRACE_EMULATION OFF APPLICATIONS NOTES: Action!** 2.0 ------------- Run in a WIN-OS/2 full-screen session. Add the following line to the AUTOEXEC.BAT file: SET TEMP=C:\ Animation Works** 1.0 --------------------- Run in 640x480 resolution. IconAuthor** 4.0 ---------------- If you are running the demo for this program, you must exit and reenter the WIN-OS/2 session before running the actual application. Linkway** Live 1.0 (Tool Series) -------------------------------- Use the following DOS setting to make the demo run properly: DOS_RMSIZE=576 MIDI ---- Make sure that the MIDI mapper (in the Control Panel) is properly set to the sound adapter. Nautilus** 1.6 and 1.76 ----------------------- Run in a WIN-OS/2 full-screen session. NETWORK o The Workplace Shell login is not compatible with Novell** NetWare** 4.0 Directory Services and should be disabled unless you are using the NetWare 4.0 Bindery Compatibility mode. To disable the login: 1. Edit the CONFIG.SYS file. 2. Remove the CONNECTIONS option from SET AUTOSTART. 3. Save and exit the CONFIG.SYS file. 4. Restart the system to activate the changes. o If you are using the NetWare Requester version 2.01, (ships with NetWare 4.0) but have no NetWare 4.0 servers, you can increase the speed of the login process by turning the Directory Services off. To turn the services off: 1. Edit NET.CFG file in the root directory of the boot drive. 2. Add Directory Services Off to the file. 3. Save and exit the file. o Novell** NetWare Requester 2.0 and 2.01 programs NMPIPE.SYS, NPSERVER.SYS, and NPDAEMON.EXE require the following information to be added to the OS2VER file. To add this information to the file: 1. At an OS/2 command prompt, type: ATTRIB -h -r -s OS2VER 2. Edit the OS2VER file in the root directory of the boot drive. 3. Type the following information in the file: 20=NMPIPE.SYS 20=NPSERVER.SYS 20=NPDAEMON.EXE 4. Save and exit the file. 5. Type ATTRIB +h +r +s OS2VER o If you are using FFST/2 (for example, if you enable the FFST/2 feature when installing Communications Manager/2 or Data Base Manager/2), REM out the "RUN=...\EPW.EXE" statement in your CONFIG.SYS file. To utilize FFST/2 technology, add a "DETACH EPW.EXE" as the first statement in your STARTUP.CMD file. NOVELL DOS REQUESTER There are three ways to use Novell** DOS Requester with OS/2. o VM Boot from Drive A If you install OS/2 Special Edition on drive C and you have installed it over a Novell DOS Requester, you can use the requester after OS/2 is installed by creating a VM Boot Diskette and selecting the "Boot from Drive A" object on your desktop. To do this: 1. Create a DOS Bootable Diskette with a version of DOS later than 3.20. 2. Make the following changes to the CONFIG.SYS file: DEVICE=A:\FSFILTER.SYS A:\HIMEM.SYS A:\EMM386.SYS FILES=60 BUFFERS=30 SHELL=A:\COMMAND.COM /E:2000 /P LASTDRIVE=last physical drive on your system 3. Copy the files from the OS/2 directory to the DOS directory. 4. Insert the DOS Diskette into Drive A. 5. Select DOS from Drive A to start your Novell DOS Requester. o Boot Manager from Drive C If OS/2 Special Edition is installed on a logical drive, (for example, D:) then DOS, Windows Version 3.1, and Novell DOS Requester will start from drive C. To do this: 1. Copy D:\OS2\MDOS\FSFILTER.SYS to C: 2. Make the following changes to the CONFIG.SYS file: DEVICE=C:\FSFILTER.SYS DEVICE=D:\OS2\MDOS\HIMEM.SYS DEVICE=D:\OS2\MDOS\EMM386.SYS FILES=60 BUFFERS=30 SHELL=C:\COMMAND.COM /E:2000 /P LASTDRIVE=last physical drive on your system 3. Make the following changes to the AUTOEXEC.BAT file: @ECHO OFF PROMPT $P$G PATH C:\WIN31;C:\DOS;C:\NETWARE C:\NETWARE\LSL.COM C:\NETWARE\TOKEN.COM C:\NETWARE\IPXODI.COM C:\NETWARE\NETX.EXE 4. Restart your system with OS/2. 5. Select OS/2 System. 6. Select the Command Prompts folder. 7. Make a copy of the DOS From Drive A object that is in the Command Prompts folder. For information about copying an object, refer to the "OS/2 2.1 Using the Operating System" book. 8. Point to the DOS From Drive A object (the copy). 9. Click mouse button 2. 10. Select the arrow to the right of Open. 11. Select Settings. 12. Select the Session tab. 13. Select DOS Settings. 14. Select DOS_STARTUP_DRIVE. 15. Type C: in the Value field. 16. Select Save. 17. Double-click on the title-bar icon to close the notebook. 18. Select DOS From Drive C to start Boot Manager. o Dual Boot If you install OS/2 Special Edition on drive C and you have Novell DOS Requester on your workstation, you can use the requester after OS/2 is installed by using its dual boot feature. Select the Dual Boot object in the Command Prompts folder to start DOS from drive C. DOS has full network support. UPGRADING TO NETWARE REQUESTER FOR OS/2 Install NetWare** Requester for OS/2 2.1 following the manufacturer's directions. This product provides network support for DOS, OS/2, and Windows Version 3.1. To make the Windows program aware of the network: 1. Select the Windows Setup object located in the Main folder. 2. Select Options. 3. Select Change System Settings. 4. Select Novell NetWare (DOS Version 3.21 and higher). 5. Insert the Windows diskette number 2 when prompted. 6. Select Restart Windows. A network object appears in the Windows Control Panel. 7. Select the Network object. ADVANCED POWER MANAGEMENT The OS/2 2.1 code in OS/2 2.1 Special Edition APM support relies on the power status information returned from the BIOS on your laptop. You might notice incorrect battery life or status within the power icon on your laptop. If this occurs, rely on the LEDs on your laptop for accurate power status information. o Turning the APM setting to OFF also turns off the BIOS power management. If you want to turn off the APM but not the BIOS power management, place REM before the APM device driver statement in your CONFIG.SYS file, then restart your system to invoke the change. REM DEVICE=C:\OS2\APM.SYS DISPLAY ADAPTERS (IMAGE, SVGA, XGA, 8514) o The OS/2 operating system will experience video problems similar to those observed in a DOS environment. These problems are due to the failure of a BIOS video mode set. An example of this problem is the video image on an ALR** Modular PS with a Flexview** 2x SVGA display fails to occupy the entire screen in 1024 x 768 mode. o If you are using an LCD display and have difficulty locating the mouse pointer on the screen, you can increase the size of the pointer if you are using 640x480 resolution. To change the size of the pointer (if you have REXX installed): 1. Use an editor to create a file called LARGE.CMD. 2. Add the following information to the file. /* LARGE.CMD Set VGA pointers to large */ /* (c) Copyright IBM Corp. 1992, All rights reserved */ call RxFuncAdd "SysIni", "RexxUtil", "SysIni" call SysIni "USER", "PM_IBMVGA", "CURSOR_SIZE", "1", say Result exit 3. Save and exit the file. 4. At an OS/2 command prompt, type "LARGE" and press Enter. This program will increase the size of the cursor. To force a standard size pointer, replace the "1" in the program with a "2". To let the system select the size of the pointer, replace the "1" in the program with a "0". o Users of the NCR** Safari notebook, SSL/25, should modify the following information in the CONFIG.SYS file on their startup drive to allow video register shadowing to be processed correctly in OS/2 2.1 Special Edition. DEVICE=C:\OS2\MDOS\VVGA.SYS to DEVICE=C:\OS2\MDOS\VSVGA.SYS o Systems with Image Adapters running in dual-display modes will lose DOS window support after a DOS full-screen or OS/2 full-screen session has been invoked. The system must be restarted to reinstate the DOS window environment. The problem can be avoided by turning off the dual display mode under the Image Adapter setup. SVGA CONSIDERATIONS o The Western Digital** 90C31 SVGA chipset will have video problems when Windows 2.x applications are run. o If you are using a ZEOS** system with Speedstar** VGA, you must run the VMODE utility supplied with the system to configure the display during the display driver installation. o Zenith Data Systems** with Headland HT208 do not support high resolution modes even though you can successfully set these modes and install high resolution drivers. If a high resolution mode is used, a white half-screen will be displayed. To correct this problem, use Selective Install to install VGA. o If you have a Sigma Legend** display adapter you might experience minor video corruption on the desktop when you switch between the desktop and DOS if they are running in different modes. This can be corrected by using the DOS utility that is packaged with this display adapter to set the DOS session to the same mode as the desktop. XGA CONSIDERATIONS o If an XGA-2 adapter is installed, and you have modified the default display type in the System Settings notebook (page 2), after you restart the system it will display the Workplace Shell* in one resolution and WIN-OS/2 in a different resolution. To change the resolution for the Workplace Shell: 1. Open OS/2 System. 2. Open System Setup. 3. Open System. 4. Select a 640x480xn resolution. 5. Shutdown and restart the system. 6. Repeat steps 1 through 3. 7. Select the desired resolution. 8. Shutdown and restart the system. The Workplace Shell and WIN-OS/2 will now display in the same resolution. o If you are using a dual display system with XGA as the primary display and VGA as the secondary display, you might see some minor corruption when the XGA display is set to a resolution with 65536 colors. This corruption will be on the display that does not have focus and will not interfere with the operation of the system. o On dual display configurations with XGA-2 as the primary display and VGA as the secondary display, the DOS full-screen session might be corrupted if a Windows** application is started in a window session. To recover from this situation, shutdown and restart the system. o On IBM P75 systems, there might be some corruption on the screen whenever several icons are selected and moved together. This corruption can be eliminated by clicking mouse button 2 to bring up the pop-up menu; then selecting Sort. o An IBM P75 system with an external monitor attached might only have the 640x480x16 resolution selection on the the System Settings Screen page. If the external monitor is capable of displaying higher resolutions, use the P75 reference diskette to disable the built-in plasma display. o If you are using an XGA system, the hash lines around the icons of open applications might change color unexpectedly. This does not interfere with the operation of the system. o If you are using an XGA system, extra lines might appear on the face of the OS/2 System Clock between the quarter (:15) and half (:30) hour. These lines do not interfere with the operation of the clock. 8514 CONSIDERATIONS o If you are using the 1MB version of an ATI** Graphics Ultra** Pro adapter, the VGA memory must be set to SHARED to work properly with the OS/2 8514 display driver. This might cause some DOS applications running in the background to corrupt the desktop. To correct this problem, you must upgrade to the 2MB version of the Graphics Ultra Pro and set the VGA memory to 256K or greater. NOTE: In the "OS/2 Installation Guide", it states that the ATI Graphics Ultra Pro must be configured to IBM DEFAULT for the 640x480 display type. This setting might be referred to as 60Hz rather than IBM DEFAULT. o If you are using a system with an 8514 adapter with Windows applications running in a WIN-OS/2 window session in separate VDMs, video corruption might occur in bitmaps when clipping between applications. o After you start a WIN-OS/2 window session, 256 color bitmaps might become discolored due to the sharing of the 256 color palette. This should not affect the running of the applications. o Selecting windows in Mathematica might not bring focus to the proper window. AUDIO ADAPTERS Audio support in WIN-OS/2 and DOS sessions is dependent on installed drivers. You should install the audio adapter driver that came with your audio adapter. When installing audio support for WIN-OS/2, be sure to install both DOS and Windows device drivers. Configure both drivers to use the same interrupt level and DMA channel. o The following drivers are available with the Audio Capture and Playback Adapter* (ACPA): - ACPADD.SYS - ACPADD2.SYS - ACPAK12.SYS - ACPA.DRV The latest updates are available on the IBM Bulletin Board Service. o MMPM/2 installs ACPA support for OS/2 only, not WIN-OS/2 or DOS. There are two ways to get DOS ACPA support in DOS sessions: 1. Edit the CONFIG.SYS file. 2. Add DEVICE=C:\ACPAK12.SYS 3. Save and exit the CONFIG.SYS file. 4. Copy the ACPAK12.SYS file to the C:\ directory. 5. Restart the system to activate the changes. Or 1. Point to the DOS full-screen or window object. 2. Click mouse button 2. 3. Select the arrow to the right of Open. 4. Select Settings. 5. Select the Session tab. 6. Select DOS Settings. 7. Select DOS_DEVICE. 8. Type C:\ACPAK12.SYS in the Value field. 9. Select Save. 10. Double-click on the title-bar icon to close the notebook. 11. Copy the ACPAK12.SYS file to the C:\ directory. To install WIN-OS/2 ACPA support: 1. Access the Control Panel in WIN-OS/2 Main. 2. Select Drivers. 3. Select Add. 4. Select Unlisted or Updated Drivers. 5. Select OK. 6. Insert the diskette containing the ACPA driver into drive A. 7. Type A: 8. Select OK. 9. When the next menu level appears, select the M-Audio sound driver. o MMPM/2 installs Sound Blaster** support for OS/2 only, not WIN-OS/2 or DOS. o To add WIN-OS/2 Sound Blaster support: 1. Install the DOS device driver following the instructions that came with the adapter. Use an OS/2 DOS session for the install. 2. Install the Windows driver. NOTE: Be sure to use the same I/O address, interrupt, and DMA settings used during installation of the DOS drivers. PRINTERS o If you are using the HP** LaserJet** printer driver, some complex images might not print correctly when LaserJet performance options are enabled. If you experience incorrect output or degraded printer performance, return the performance options to the disabled state. To change the performance options: 1. Point to the printer object. 2. Click mouse button 2. 3. Select the arrow to the right of Open. 4. Select Settings. 5. Select the Printer driver tab. 6. Select Job properties. 7. Change the performance options to their default settings. 8. Double-click on the title-bar icon to close the notebook. o If you experience problems while printing bitmaps from an application while using the PostScript printer driver, Select the Printer-specific format option on the Queue options page in the Settings notebook of your printer object. o The OS/2 printer drivers on the OS/2 2.1 printer driver diskettes are stored in a packed format that is not compatible with OS/2 1.3 or 2.0. To install one of the OS/2 2.1 printer drivers on a system with OS/2 1.3 or 2.0 installed, you must first unpack the driver on a system that has OS/2 2.1 installed. You do not have to complete these steps to install a printer driver on a system that already has OS/2 2.1 installed. NOTE: Do not install the new 32-bit PostScript driver (PSCRIPT.DR_) that came with OS/2 2.1 on a system with OS/2 1.3 or 2.0 installed. It is not compatible with these versions of OS/2. While testing is continuing, current compatibility information about tested systems is available through your dealer, Marketing Representative, CompuServe, IBM National Support Center Bulletin Board System (NSC BBS), and IBMLink. To unpack a printer driver for use on a OS/2 1.3 or OS/2 2.0 system, complete the following steps on your system that has OS/2 2.1 installed. 1. Open an OS/2 command prompt. 2. Type: MD X:\DRIVER Where X is a drive on your system. 3. Insert into drive A the OS/2 2.1 printer driver diskette that contains the printer driver you want to install. The printer driver names end in a "_". Printer Driver: Diskette # Packed Name: IBM Null 1 IBMNULL.DR_ HP LaserJet 1 LASERJET.DR_ HP DeskJet 1 HPDJPM.DR_ IBM 52XX 1 IBM52XX.DR_ Epson 1 EPSON.DR_ Plotter Driver 1 PLOTTERS.DR_ IBM 4019 2 IBM4019.DR_ IBM 42XX 2 IBM42XX.DR_ IBM 5201-2 2 IBM52012.DR_ PaintJet 2 SMGXPJET.DR_ 4. Type: UNPACK A:\Packed name X:\DRIVER Where X is a drive on your system. For example if you want to install the Epson printer driver, type : UNPACK A:\EPSON.DR_ X:\DRIVER The printer driver files are now unpacked in the X:\DRIVER directory. 5. Copy the driver files to a diskette and install them onto your OS/2 1.3 or 2.0 system. SCANNERS If you have a Logitech hand scanner on an AT bus computer, run the scanner at the 100, 200, or 300 DPI setting. MAHJONGG GAME OS/2 2.1 code in OS/2 2.1 Special Edition includes a new tile-matching game called Mahjongg Solitaire. To install Mahjongg Solitaire from diskettes: 1. Insert Diskette 10 into drive A. 2. Open an OS/2 command prompt. 3. Type: UNPACK A:MAHJONGG drive: where drive is the drive letter of the partition OS/2 2.1 is installed on. 4. Press Enter. 5. Type: MAHINST and press Enter. Then, follow the instructions on the screen. To install Mahjongg Solitaire from CD: 1. Insert the CD into the CD drive. 2. Open an OS/2 command prompt. 3. Type: UNPACK cddrive:\OS2SE21\DISK_10\MAHJONGG drive: where cddrive is the drive letter of the CDROM and drive is the drive letter of the partition OS/2 2.1 is installed on. 4. Press Enter. 5. Type: MAHINST and press Enter. Then, follow the instructions on the screen. TRADEMARKS AND SERVICE MARKS ____________________________ The following terms, denoted by an asterisk (*) in this README, are trademarks or registered trademarks of the IBM Corporation in the United States or other countries: Audio Capture and Playback Adapter ------------------------------------------ IBM ------------------------------------------ Linkway ------------------------------------------ Micro Channel ------------------------------------------ Multimedia Presentation Manager/2 ------------------------------------------ OS/2 ------------------------------------------ WIN-OS/2 ------------------------------------------ Workplace Shell ------------------------------------------ XGA ------------------------------------------ The following terms, denoted by a double asterisk (**) in this README, are trademarks of other companies as follows: Trademark: Owner: -------------------------------------------------------------- Action! Expertelligence -------------------------------------------------------------- ALR Advanced Logic Research, Inc. -------------------------------------------------------------- Animation Works Gold Disk Inc. -------------------------------------------------------------- APM Astek International Ltd. -------------------------------------------------------------- ATI ATI Technologies, Inc. -------------------------------------------------------------- Borland Borland International, Inc. -------------------------------------------------------------- Canon Canon Kabushiki Kaisha -------------------------------------------------------------- CompuServe CompuServe Inc. -------------------------------------------------------------- C++ AT&T, Inc. -------------------------------------------------------------- Describe Lenname Advanced Products -------------------------------------------------------------- DeskJet Hewlett-Packard Company -------------------------------------------------------------- Facelift Bitstream Inc. -------------------------------------------------------------- Flexview Nutmeg Systems -------------------------------------------------------------- FormBase Xerox Corporation -------------------------------------------------------------- Fotoman Logitech International -------------------------------------------------------------- FoxPro Fox Holdings, Inc. -------------------------------------------------------------- FrameMaker Frame Technologies Inc. -------------------------------------------------------------- Freelance Graphics Lotus Development Corporation -------------------------------------------------------------- Hollywood Claris Corporation -------------------------------------------------------------- HP Hewlett-Packard Company -------------------------------------------------------------- HP LaserJet Hewlett Packard -------------------------------------------------------------- IconAuthor Aimtech Corporation -------------------------------------------------------------- Intel Intel Corporation -------------------------------------------------------------- Legend Sigma Designs Inc. -------------------------------------------------------------- Logitech Logitech, Inc. -------------------------------------------------------------- Lotus Lotus Development Corporation -------------------------------------------------------------- Microsoft Microsoft Corporation -------------------------------------------------------------- Nautilus Softshell Systems -------------------------------------------------------------- NCR NCR Corporation -------------------------------------------------------------- NET NCR Corporation -------------------------------------------------------------- NetWare Novell, Inc. -------------------------------------------------------------- Novell Novell, Inc. -------------------------------------------------------------- Paint Brush Microsoft Corporation -------------------------------------------------------------- Panasonic Matsushita Electric Industrial Co., Ltd. -------------------------------------------------------------- Paradox Borland International, Inc. -------------------------------------------------------------- PostScript Adobe Systems Inc. -------------------------------------------------------------- Powerpoint Microsoft Corporation -------------------------------------------------------------- Sound Blaster Creative Labs, Inc. -------------------------------------------------------------- SpeedStar Diamond Computer Systems, Inc. -------------------------------------------------------------- Turbo C Borland International, Inc. -------------------------------------------------------------- Ultra ATI Technologies, Inc. -------------------------------------------------------------- Western Digital Western Digital Corporation -------------------------------------------------------------- Windows Microsoft Corporation -------------------------------------------------------------- WindowWorks Spinnaker Software Corporation -------------------------------------------------------------- WinTach Texas Instrument -------------------------------------------------------------- WordPerfect WordPerfect Corporation -------------------------------------------------------------- Zenith Data Systems Zenith Electronics Corporation -------------------------------------------------------------- ZEOS ZEOS International Ltd. -------------------------------------------------------------- IBM DISCLAIMS ALL WARRANTIES, WHETHER EXPRESSED OR IMPLIED, INCLUDING WITHOUT LIMITATION, WARRANTIES OF FITNESS AND MERCHANTABILITY WITH RESPECT TO THE INFORMATION IN THIS DOCUMENT. BY FURNISHING THIS DOCUMENT, IBM GRANTS NO LICENSES TO ANY RELATED PATENTS OR COPYRIGHTS. Copyright IBM Corporation, 1993, all rights reserved. ΓòÉΓòÉΓòÉ 4.3. OS/2 For Windows 2.1 INSTALLATION README file ΓòÉΓòÉΓòÉ OS/2 For Windows 2.1 INSTALLATION README file OS/2 2.1 Special Edition for Use with Windows Version 3.1 - INSTALLATION README _______________________________________________________________________________ Thank you for purchasing a copy of OS/2* 2.1 Special Edition. This product is designed for licensed users of Microsoft** Windows** Version 3.1 product. After the installation of this product, your system will allow you to run DOS, Windows, and OS/2 applications. Throughout the documentation provided with this product, all references to WIN-OS/2* apply to running your Windows Version 3.1 programs under the special edition. This document provides you with information you need before you install OS/2* 2.1 Special Edition. It contains helpful hints found in our testing as well as updates and corrections to the "OS/2 2.1 Installation Guide". Use the information in conjunction with the "OS/2 2.1 Installation Guide", the "OS/2 2.1 Using the Operating System" manual, and the "OS/2 2.1 Special Edition for Use with Windows Version 3.1 Installation Guide". Do NOT install this product over OS/2 2.1. Installation of OS/2 2.1 Special Edition over OS/2 2.1 is not supported. Do NOT install OS/2 2.1 over this product. Installing OS/2 2.1 over OS/2 2.1 Special Edition is not supported. If you install OS/2 2.1 over OS/2 2.1 Special Edition, you might lose the ability to use the Dual Boot or Boot Manager feature to start Windows Version 3.1. You will need to re-install Windows Version 3.1, and you might need to re-install some of your Windows programs. The "OS/2 2.1 Special Edition for Use with Windows Version 3.1 Installation Guide" INCORRECTLY states that you cannot install OS/2 2.1 Special Edition over previous versions of OS/2. You CAN install this product over previous versions of OS/2. However, if you install this product over previous versions of OS/2 you must have Windows 3.1 installed on your system to run Windows applications. If you are installing OS/2 2.1 Special Edition over a product release such as OS/2 1.3, OS/2 2.0, OS/2 2.0 with the Service Pak, DOS, or DOS and Windows**, it is recommended that you do not reformat the OS/2 partition. Do not install this product over Windows** for Work Groups. Installing this product over Windows for Work Groups is not supported. To install OS/2 2.1 Special Edition, the original device drivers, fonts, and specific language information shipped with Windows 3.1 are required. You will use these files to update your Windows 3.1 configuration to match your OS/2 configuration. Listed below is information to assist you. o Some computer manufacturers ship Windows 3.1 diskettes with the computer. Use those diskettes when requested during the installation process. o Some computer manufacturers preinstall the Windows 3.1 diskette images on the hard disk and provide authorization to use a utility to create the Windows 3.1 diskettes. If you are authorized to do so, and you have not done so, create the Windows 3.1 diskettes and use those diskettes when requested during the installation process. o Some computer manufacturers ship the Windows 3.1 device drivers on a directory on the hard disk. The installation process will install the device drivers, fonts, and language specific information from that directory and you will not be prompted for diskettes. o If you have an Ultimedia preinstalled system, or you installed Windows Version 3.1 from your Ultimedia System CD-ROM, do the following when prompted for the Windows Version 3.1 diskettes: 1. Insert the Ultimedia System CD-ROM into the drive. 2. Change to the directory containing Windows 3.1 on your CD-ROM. For example, type: D:\WINSETUP 3. Continue with the installation process. o If Windows 3.1 was installed from 3.5-inch diskettes, you must have the 3.5-inch Windows 3.1 diskettes. If Windows 3.1 was installed from 5.25-inch diskettes, you must have the 5.25-inch Windows 3.1 diskettes. o If you have updated the device drivers, fonts, or specific language information from those shipped on the Windows 3.1 diskettes, or from those on your preinstalled system, you might be overwriting these files. If you are installing OS/2 2.1 Special Edition over an existing OS/2 2.0 system in which you have application programs on the desktop, you should not elect to migrate these applications during your installation. Your current application set will continue to be available to you after installation. If you have a version of the OS/2 2.1 Special Edition beta installed, you need to reformat the OS/2 partition. Installing OS/2 2.1 Special Edition over a previous beta version is not supported. Do not use any OS/2 system files (such as OS2.INI or OS2SYS.INI) from a previous beta version. ****************IMPORTANT!***************** If you have a DOS or Windows Compression product installed before installing OS/2 2.1 Special Edition, check the documentation that came with your disk compression program to make sure it is compatible with the OS/2 operating system. If the disk compression program is incompatible with the OS/2 operating system, you will not be able to use the compressed drive while running OS/2 2.1 Special Edition, or the installation of OS/2 2.1 Special Edition might fail. If you have a DOS system with compression activated, do one of the following: 1. Decompress the disk where DOS and/or Windows Version 3.1 is installed. 2. Select a different partition to install OS/2 2.1 Special Edition. 3. Format the disk partition and reinstall DOS and Windows without compression. If you are installing OS/2 2.1 Special Edition on a non-Micro Channel (MCA) system, change the settings in your CMOS to the following: o Turbo/System Speed should be OFF/Slow o Caching (External) should be OFF o ROM Shadowing (System and Video) should be OFF These settings affect the way that OS/2 2.1 Special Edition installs. Failure to change these settings might result in OS/2 2.1 Special Edition not installing at all; installing and then booting to a Trap 2; or what seems to be a good install and later having unexplainable random Traps (from a few days to a few months later). To improve system performance after you have installed this version of the OS/2 operating system, all of the above settings can be changed back without causing damage to OS/2 2.1 Special Edition. ******************************************* DOS 3.1 AND 3.2 USERS _____________________ DOS Versions 3.1 and 3.2 will create only one partition with a maximum size of 32MB. If both DOS and Windows Version 3.1 are already in the partition, OS/2 2.1 Special Edition might not fit in the same partition. To solve this problem, allow OS/2 2.1 Special Edition to create additional partitions at installation time. A minimum of 20MB is required for the installation of OS/2 2.1 Special Edition. NOTE: When you start from DOS, the partitions created with OS/2 2.1 Special Edition cannot be accessed. DOS 3.3 USERS _____________ DOS Version 3.3 allows multiple partitions no larger than 32MB. Although OS/2 2.1 Special Edition allows partitions larger than 32MB, in order for DOS to access the contents of the partition, do not create a larger partition. This allows DOS to access the contents of the partition. Also, for optimum performance, put DOS Version 3.3 and Windows Version 3.1 in one partition and OS/2 2.1 Special Edition in another partition. SCSI-BASED CD-ROM SUPPORT _________________________ The majority of SCSI-based CD-ROM drives and adapters are supported by OS/2 2.1 Special Edition. ("SCSI-based" refers to the small computer system interface (SCSI), a standard input/output interface used by personal computers.) A complete list of the CD-ROM drives and SCSI adapters tested on OS/2 2.1 Special Edition can be found in the "Hardware Support" chapter of the "OS/2 2.1 Using the Operating System" manual. (Note that Panasonic** MC521 support is not shipped with OS/2 2.1 Special Edition. Please contact Panasonic to receive this support.) OBTAINING ADDITIONAL CD-ROM SUPPORT If, after reviewing the list in "OS/2 2.1 Using the Operating System", you find that your CD-ROM drive or SCSI adapter is not supported within OS/2 2.1 Special Edition, you can contact the manufacturer and obtain an OS/2 Adapter Device Driver (.ADD) file. After you receive the .ADD file, follow the instructions in the "Before You Begin" section of the "OS/2 2.1 Installation Guide" to add this file to Diskette 1. As an alternative, you can create installation diskettes from the diskette images that are on the OS/2 2.1 Special Edition CD, if you have DOS support for your CD-ROM drive. If support for your CD-ROM was not properly installed during initial installation of OS/2 2.1 Special Edition, then you will need to use the Selective Install program located in the System Setup folder to reinstall the CD-ROM support appropriate for your CD-ROM. CREATING DISKETTES FROM THE OS/2 2.1 SPECIAL EDITION CD You use the LOADDSKF utility program to create the diskettes. (LOADDSKF.EXE is in the \DISKIMGS directory of the CD. LOADDSKF can be run from either the DOS or OS/2 operating system.) In the following sections, you will see lists of the product diskettes for OS/2 2.1 Special Edition and the actual diskette names as they exist on the CD. For each diskette image file, use LOADDSKF to expand the image to its own diskette. (Note that you must use formatted diskettes for this procedure.) For example: cddrive:\DISKIMGS\LOADDSKF cddrive:\DISKIMGS\OS2\size\disk_name b: where: cddrive is the drive letter of the CD-ROM size is 35 for 3.5-inch diskettes or 525 for 5.25-inch diskettes disk_name is the diskette image file name (for example, DISK0.DSK, PMDD1.DSK.) b is the drive letter of your diskette drive (A: or B:) After you create all the diskettes (16 for 3.5-inch diskettes or 19 for 5.25-inch diskettes), insert the DISK0 diskette in drive A:, restart your system, and follow the instructions to install OS/2 2.1 Special Edition. List of 3.5-Inch Diskette Images DISKIMGS\OS2\35\DISK0.DSK -- INSTALLATION Diskette DISKIMGS\OS2\35\DISK1.DSK -- Diskette 1 of 11 DISKIMGS\OS2\35\DISK2.DSK -- Diskette 2 of 11 DISKIMGS\OS2\35\DISK3.DSK -- Diskette 3 of 11 DISKIMGS\OS2\35\DISK4.DSK -- Diskette 4 of 11 DISKIMGS\OS2\35\DISK5.DSK -- Diskette 5 of 11 DISKIMGS\OS2\35\DISK6.DSK -- Diskette 6 of 11 DISKIMGS\OS2\35\DISK7.DSK -- Diskette 7 of 11 DISKIMGS\OS2\35\DISK8.DSK -- Diskette 8 of 11 DISKIMGS\OS2\35\DISK9.DSK -- Diskette 9 of 11 DISKIMGS\OS2\35\DISK10.DSK -- Diskette 10 of 11 DISKIMGS\OS2\35\DISK11.DSK -- Diskette 11 of 11 DISKIMGS\OS2\35\PMDD1.DSK -- Printer Drivers Diskette 1 of 2 DISKIMGS\OS2\35\PMDD2.DSK -- Printer Drivers Diskette 2 of 2 DISKIMGS\OS2\35\DISP1.DSK -- Display Drivers Diskette 1 of 2 DISKIMGS\OS2\35\DISP2.DSK -- Display Drivers Diskette 2 of 2 List of 5.25-Inch Diskette Images DISKIMGS\OS2\525\DISK0.DSK - INSTALLATION Diskette DISKIMGS\OS2\525\DISK1.DSK - Diskette 1 of 13 DISKIMGS\OS2\525\DISK2.DSK - Diskette 2 of 13 DISKIMGS\OS2\525\DISK3.DSK - Diskette 3 of 13 DISKIMGS\OS2\525\DISK4.DSK - Diskette 4 of 13 DISKIMGS\OS2\525\DISK5.DSK - Diskette 5 of 13 DISKIMGS\OS2\525\DISK6.DSK - Diskette 6 of 13 DISKIMGS\OS2\525\DISK7.DSK - Diskette 7 of 13 DISKIMGS\OS2\525\DISK8.DSK - Diskette 8 of 13 DISKIMGS\OS2\525\DISK9.DSK - Diskette 9 of 13 DISKIMGS\OS2\525\DISK10.DSK - Diskette 10 of 13 DISKIMGS\OS2\525\DISK11.DSK - Diskette 11 of 13 DISKIMGS\OS2\525\DISK12.DSK - Diskette 12 of 13 DISKIMGS\OS2\525\DISK13.DSK - Diskette 13 of 13 DISKIMGS\OS2\525\PMDD1.DSK - Printer Drivers Diskette 1 of 2 DISKIMGS\OS2\525\PMDD2.DSK - Printer Drivers Diskette 2 of 2 DISKIMGS\OS2\525\DISP1.DSK - Display Drivers Diskette 1 of 2 DISKIMGS\OS2\525\DISP2.DSK - Display Drivers Diskette 2 of 2 If you want to create diskettes for the Multimedia support that is part of OS/2 2.1 Special Edition, note that the images are located in the \DISKIMGS\MMPM2 directory. Use LOADDSKF to expand each image to its own diskette. For example: cddrive:\DISKIMGS\LOADDSKF cddrive:\DISKIMGS\MMPM2\size\disk_name b: where: cddrive is the drive letter of the CD-ROM size is 35 for 3.5-inch diskettes or 525 for 5.25-inch diskettes disk_name is the diskette image file name (for example, DISK1.DSK) b is the drive letter of your diskette drive (A: or B:) NOTE: Use previously formatted diskettes for the target (b:). List of 3.5-Inch Multimedia Diskette Images DISKIMGS\MMPM2\35\DISK1.DSK - Diskette 1 of 2 DISKIMGS\MMPM2\35\DISK2.DSK - Diskette 2 of 2 List of 5.25-Inch Multimedia Diskette Images DISKIMGS\MMPM2\525\DISK1.DSK - Diskette 1 of 3 DISKIMGS\MMPM2\525\DISK2.DSK - Diskette 2 of 3 DISKIMGS\MMPM2\525\DISK3.DSK- Diskette 3 of 3 When you do a selective install to update your system from VGA to SVGA, your system attempts to write to the CD-ROM. Therefore, you must create the diskette images for the display drivers before performing the selective install. HARDWARE CONSIDERATIONS _______________________ If you have a Quantum hard card, you must make a modification to the BASEDEV=IBM1S506.ADD line in the CONFIG.SYS file of Diskette 1 before you install OS/2 2.1 Special Edition. The BASEDEV statement should be modified as follows: BASEDEV=IBM1S506.ADD /A:1 /IRQ:11 (These are the default settings for the Quantum hard card.) If you have added a device driver statement to the CONFIG.SYS file on diskette 1 and later migrate your old CONFIG.SYS file, make sure there are not two copies of this statement in your file. If you have two copies of this statement in your file, REM one statement out. If you have a Logitech** TrackMan**, select one of the two Logitech mouse choices during installation. INSTALLING OS/2 2.1 SPECIAL EDITION FROM A CD ON AN IBM THINKPAD ATTACHED TO A DOCKING STATION ________________________________________________ If you are installing OS/2 2.1 Special Edition on an IBM* ThinkPad* 700, 700C, 720, or 720C attached to a 3550 Docking Station, you need to replace the ABIOS files on the OS/2 Installation Diskette with files from the Reference Diskette. Do the following: 1. Detach the ThinkPad from the Docking Station. 2. Create a Reference Diskette (if you have not already done so) by following the documentation that came with the ThinkPad. 3. Make a copy of the OS/2 Installation Diskette. 4. Insert the original OS/2 Installation Diskette into drive A. 5. Turn on the computer. If it is already on, press Ctrl+Alt+Del. 6. When you are prompted to do so, remove the Installation Diskette, insert Diskette 1, and press Enter. 7. When the Welcome screen is displayed, press Esc to display the command prompt. 8. Insert the copy of the Installation Diskette into drive A. 9. Type: DEL *.BIO and press Enter. 10. Remove the copy of the Installation Diskette, and insert the Reference Diskette you created in step 2 into drive A. 11. If your computer has more than one diskette drive, insert the copy of the Installation Diskette into drive B. Otherwise, in the next two steps, you will be prompted to insert diskettes into both drive A and drive B. When you are asked to insert a diskette into drive A, insert the Reference Diskette. When you are asked to insert a diskette into drive B, insert the copy of the Installation Diskette. 12. Type: COPY A:\*.BIO B:\ and press Enter. 13. Type: COPY A:\ABIOS.SYS B:\ and press Enter. 14. Power off the ThinkPad and return it to the Docking Station. 15. Restart the installation procedure by inserting the copy of the Installation Diskette into drive A. INSTALLING OS/2 2.1 SPECIAL EDITION USING RIPL ______________________________________________ When installing OS/2 2.1 Special Edition using the IBM LAN Server 3.0 Remote Installation Program Load (RIPL), the OS/2 2.1 Special Edition version of RIPLINST.EXE is dependent upon the OS/2 2.1 Special Edition version of UNPACK.EXE. Therefore, if you are using the OS/2 2.1 Special Edition version of RIPLINST.EXE on a client machine with OS/2 version 2.0 or lower, then you must copy the UNPACK.EXE file to the client machine. To do this, do the following: 1. Insert OS/2 2.1 Special Edition Diskette 2 into drive A 2. At an OS/2 command prompt type: copy a:\unpack.exe \os2\unpack.exe After copying the file to the client machine, you can now execute the OS/2 2.1 Special Edition version of the RIPLINST.EXE program. o When installing IC06163 to a LAN Server supporting Remote IPL (RIPL), you must first obtain a special utility package from the IBM Service and Support Center. To obtain this tool, you must request the LAN SERVER RIPL package for IC06163. VIDEO CONSIDERATIONS ____________________ The following information pertains to video support for OS/2 2.1 Special Edition. INSTALLING SUPER VGA (SVGA) SUPPORT After the VGA installation is complete, follow the procedure "Changing Your Setup or Adding Features" in Appendix A of the "OS/2 2.1 Installation Guide". INSTALLING S3 SUPER VGA (SVGA) SUPPORT For more information on how to install S3** SVGA support, refer to the S3 README. CID INSTALL UPDATE FOR S3 256 COLOR DISPLAY DRIVERS If you want to install the S3 256 color display driver using CID installation, add the following statements to your LCU command file. The following information provides a guide to help you update your LCU command file. /*****************************************************/ /* PRODUCT DATA SECTION */ /*****************************************************/ . . . x.s3video256 = 15 x.15.name='S3 Video 256 color' x.15.statevar = 'CAS_' || x.15.name x.15.instprog = 'x:\img\s3_256\S3INST.CMD', ' x:\img\s3_256 ' || bootdrive x.15.rspdir = '' x.15.default = '' ======================================================= S3INST.cmd needs to be modified before it can by used. Use a text editor to REM out the PAUSE statement. ======================================================= /*---------------------------------------------------*/ /* NUMBER OF PROGRAMS SET UP IN THE */ /* PRODUCT DATA SECTION */ /*---------------------------------------------------*/ NUM_INSTALL_PROGS = 15 /*****************************************************/ /* INSTALL SECTION */ /*****************************************************/ . . . when OVERALL_STATE = 2 then do if RunInstall(x.s3video256) == BAD_RC then exit Call CheckBoot end . . . end exit INSTALLATION ON SPECIFIC VIDEO ADAPTERS In the "OS/2 2.1 Installation Guide", instructions are given for configuring the ATI** Graphics Ultra Pro. These instructions state that the monitor type for 640 x 480 must be configured to IBM DEFAULT. Note that this setting might be referred to as 60Hz rather than IBM DEFAULT. The Radius XGA display adapter is supported on PS/2* Models 35 and 40 and PS/ValuePoint* 486 systems. If you are using the display adapter on a PS/ValuePoint system, the VPXGA.EXE utility is required. For a copy of this utility program, check your Radius installation diskette or contact Radius. The OS/2 2.1 Special Edition operating system cannot restore the state of a Sigma Legend** display adapter after you switch sessions or video modes. Also, the Sigma Legend video adapter might cause the system to stop when using 1024 x 768 x 256 color mode. Use only 640 x 480 or 800 x 600 mode with this adapter. CORRECTION TO INSTALLATION GUIDE APPENDIX B ___________________________________________ Appendix B of the "OS/2 2.1 Installation Guide" presents information on how to respond to messages that begin with "TRAP". The information in the appendix pertains only to TRAP0002 messages. EXTENDED SERVICES (ES) 1.0 __________________________ o If you installed OS/2 2.1 Special Edition on a system that already had Extended Services installed, you need to replace the existing ESSTART.CMD file with the ESSTART.BAK file that was installed by OS/2 2.1 Special Edition. (The ESSTART.BAK file is located in the OS2\INSTALL subdirectory.) First rename ESSTART.CMD to ESSTART.OLD. Then rename ESSTART.BAK to ESSTART.CMD. o If you are installing Extended Services over OS/2 2.1 Special Edition for the first time (that is, there is no Extended Services on the workstation), or if you are installing Extended Services from diskettes, rename the existing ESSTART.CMD file from the Extended Services Diskette 1. Then, copy the file ESSTART.BAK from the \OS\INSTALL directory to Extended Services Diskette 1. Finally, rename the ESSTART.BAK file ESSTART.CMD, and begin the installation of Extended Services. NOTICES AND TRADEMARKS __________ If you want to run Windows programs on the OS/2 desktop, with OS/2 2.1 Special Edition, you agree that you are a current licensee of Microsoft Windows Version 3.1 software. You also agree to abide by all the conditions of the Microsoft Windows Version 3.1 license agreement. In order for OS/2 2.1 Special Edition to work properly, you need to have the original copies of Windows Version 3.1 files on your system. During installation you will be prompted for your original Windows diskettes. This process replaces any modified code from your original copy of Windows, leaving you with one and only one copy of Windows on your system. If you have changed any of your Windows file names or have made any additional unauthorized copies, you must dispose of them accordingly, leaving you one copy of Windows on your hard file. Your Windows system configuration will be updated to match your selected OS/2 2.1 system configuration. As a result of this update, your existing Windows device drivers might be overwritten. Also, if you install any other manufacturer's enhanced device drivers on your system, they might be overwritten. Be sure to verify with the license agreement that came with the other manufacturer's device driver that it can be used with OS/2 Special Edition. The following terms, denoted by an asterisk (*) in this README, are trademarks or registered trademarks of the IBM Corporation in the United States or other countries: IBM ----------------------------------------------- OS/2 ----------------------------------------------- PS/2 ----------------------------------------------- PS/ValuePoint ----------------------------------------------- ThinkPad ----------------------------------------------- XGA ----------------------------------------------- The following terms, denoted by a double asterisk (**) in this README, are trademarks of other companies as follows: Trademark: Owner: -------------------------------------------------------------- Adaptec Adaptec, Inc. -------------------------------------------------------------- ATI ATI Technologies, Inc. -------------------------------------------------------------- Legend Sigma Designs Inc. -------------------------------------------------------------- Logitech Logitech, Inc. -------------------------------------------------------------- Panasonic Matsushita Electric Industrial Co., Ltd. -------------------------------------------------------------- S3 S3 Incorporated -------------------------------------------------------------- TrackMan Logitech, Inc. -------------------------------------------------------------- Windows Microsoft Corporation -------------------------------------------------------------- IBM DISCLAIMS ALL WARRANTIES, WHETHER EXPRESSED OR IMPLIED, INCLUDING WITHOUT LIMITATION, WARRANTIES OF FITNESS AND MERCHANTABILITY WITH RESPECT TO THE INFORMATION IN THIS DOCUMENT. BY FURNISHING THIS DOCUMENT, IBM GRANTS NO LICENSES TO ANY RELATED PATENTS OR COPYRIGHTS. Copyright IBM Corporation, 1993, all rights reserved. ΓòÉΓòÉΓòÉ 4.4. Personal OS/2 Beta README Part 1 ΓòÉΓòÉΓòÉ Personal OS/2 Beta README Part 1 OS/2 Performance Beta Version 2.99 Special Edition for Windows Readme _______________________________________________________________ This product is designed for licensed users of the Microsoft** Windows** Version 3.1 product. After the installation of this product, you will be able to run DOS, Windows, and OS/2 applications on the same desktop. This README contains helpful hints found during our testing. It is divided into the following categories: o General System Considerations o Visual Enhancements o Diskette Formatting Problems on ISA/EISA Systems o ATM Demand Load Setting o WIN-OS/2 Window Session Fast Load Setting o VDM Priority Setting o International Standards Organization (ISO) Fonts o CD-ROM o Dual Boot and Boot Manager o Windows Application Compatibility o DOS Application Compatibility o OS/2 Application Compatibility o DOS and WIN-OS/2 Multimedia Application Compatibility o Network o Display adapters o Audio Adapters o Printers o Scanners o Advanced Power Management (APM) o Programming Tools o Serviceability and Diagnostic OS2KRNL. o Trademarks and Service Marks NOTE: This hardcopy of the README file contains the latest information. Use this document instead of the one provided on the OS/2 CD-ROM or the OS/2 Diskette Images. Throughout the documentation provided with this product, all references to WIN-OS/2* apply to running your Windows Version 3.1 programs under the OS/2 Performance Beta version. A separate README file with additional information for MMPM/2 is contained with the MMPM/2 program. GENERAL SYSTEM CONSIDERATIONS o Your system files might be read-only. As a result, the system will not update the .INI or .SYS files. To resolve this problem, change to the directory where your system files are located. (C:\OS2 is the default.) Type the following at an OS/2 command prompt: ATTRIB -r *.ini press Enter and then type: ATTRIB -r *.sys and press Enter. Shut down your system. When you restart your system, your system files will be updated. Note: If you want to selectively install the Serviceability and Diagnostic Aids, you must be sure to perform the steps above. o Before you can run Selective Install from the OS/2 CD-ROM, you must place the OS/2 CD in the CD-ROM drive attached to your system. o Do not run the Windows Setup program, and do not change your video configuration for Windows. o If you experience video corruption (for example, stacked or missing icons): - Display the desktop pop-up menu (click mouse button 2 on the OS/2 desktop background). - Select Refresh to redraw the desktop. - If the screen goes blank, press Alt+Esc (to switch between the applications) to force repainting of the screen. o If you have set a password using LOCKUP from the desktop pop up menu and you have forgotten the password, 1. Add the following statement to the LOCK.RC file located in the \OS2 directory. "PM_Lockup" "LockupOptions" "" This must be placed right above the END statement. 2. Insert the Installation Diskette into drive A and restart your system. 3. When prompted remove the Installation Diskette and insert Diskette 1 into drive A. 4. Press Esc to display the OS/2 command prompt and type: MAKEINI LOCK.RC and press Enter. 5. When MAKEINI is complete, remove Diskette 1 from drive A and restart your system. o DOS Images on the hard disk (VMBs) need to use the FSFILTER and FSACCESS drivers provided with this version of OS/2. FSFILTER and FSACCESS drivers are located in the \OS2\MDOS directory. o If you are running CHKDSK without the /F parameter from the command line on an HPFS partition that also contains your SWAPPER.DAT file, you might receive a SYS0552 error message. This message can be ignored. If you are using CHKDSK from the pop-up menu of a drive icon, you might receive a WARNING message stating "The disk is in use or locked by another process." If this occurs, CHKDSK will not display its diagram how the disk is being used. o If you use the Dual Boot feature and you have an SVGA system set to 1024x768 resolution, the fonts will be too large for the display when you switch to DOS. To correct this problem do the following to the WIN.INI file located in the OS2\MDOS\WINOS2 directory. Change the high-resolution font statement courF.fon, serifF.fon, smallF.fon, sserifF.fon, and symbolF.fon to low-resolution fonts. Note: When you switch back to OS/2 from DOS, you need to return the resolution statement back to the original high-resolution fonts. Therefore, you must change the font statement to courE.fon, serifE.fon, smallE.fon, sserifE.fon, and symbolE.fon, respectively. | o When you use the Windows Version 3.1 Control Panel under OS/2, the changes to the 386 Enhanced mode settings are ignored and you might receive an error message. Disregard the error message. o The Recorder application located in the Accessories Program Group of your Windows product will not run with OS/2 Performance Beta Version 2.99. Running this application can lead to undesirable and unpredictable results. o If WIN-OS2 window fails to come up on an IBM Thinkpad, make sure that your CONFIG.SYS file contains the following statment: DOS=LOW,NOUMB and the WINOS2 settings has DOS set to LOW and UMB set to OFF. VISUAL ENHANCEMENTS ------------------- This version of OS/2 includes visual enhancements and functions: o A new color palette has been added and includes over 100 colors. This color palette replaces the color palette that exists in previous versions of OS/2. o Fifteen new schemes with bit map support and Icon Text Background color support has been added. The original schemes can be re-created by creating another scheme palette with the Scheme Palette Template located in the Templates folder. Note: If you use the Clovers scheme your icon text and Active Title Bar will be unreadable. To fix the problem, you can change the icon text background to non-transparent and the Active Title Bar text to white. o IMPORTANT: If you did not reformat the OS/2 partition, you must recreate the color and scheme palettes to view the changes made to these objects. To add the new color palette and scheme palette to the desktop, follow the instructions provided in the OS/2 User's Guide to run MAKEINI on the OS2.INI and OS2SYS.INI files, and then use the following REXX file to create the new objects. Creating a new Scheme Palette /* Delete the old Scheme Palette */ call RxFuncAdd 'SysLoadFuncs', 'RexxUtil', 'SysLoadFuncs' call SysLoadFuncs SchemeObjectId = "<WP_SCHPAL>" SchemeObjectLocation = "<WP_CONFIG>" call SysSetObjectData SchemeObjectId,"NODELETE=NO" call SysDestroyObject SchemeObjectId /* Create new Scheme Palette object */ rc = SysCreateObject('WPSchemePalette',, 'Scheme Palette',, SchemeObjectLocation,, 'NODELETE=YES;AUTOSETUP=YES;OBJECTID='SchemeObjectId,, 'update'); Creating a new Color Palette /* Delete the old Color Palette */ call RxFuncAdd 'SysLoadFuncs', 'RexxUtil', 'SysLoadFuncs' call SysLoadFuncs ColorObjectId = "<WP_CLRPAL>" ColorObjectLocation = "<WP_CONFIG>" call SysSetObjectData ColorObjectId,"NODELETE=NO" call SysDestroyObject ColorObjectId /* Create new Color Palette object */ rc = SysCreateObject('WPColorPalette',, 'Color Palette',, ColorObjectLocation,, 'NODELETE=YES;OBJECTID='ColorObjectId,, 'update'); o The scheme palette allows you to edit, manipulate, and drag bit maps as well as colors and fonts to the desktop. To edit or preview a bit map: 1. Open "OS/2 System". 2. Open "System Setup". 3. Open the "Scheme Palette". 4. Select a scheme or double-click on its icon or press the Edit Scheme push button. 5. Click mouse button 2 on the folder icon located near the lower left corner of the window. 6. Select "Folder Background" from the pop up menu. 7. Select the color or bit map you want to use. Some of the new schemes added to OS/2 contain new wallpaper bit maps as well. o The scheme palette supports a background color for the icon text. This feature enables you to change the background color beneath the text, making it easier to see the text when a bit map is displayed as a folder background. To edit the icon text background color: 1. Open "OS/2 System". 2. Open "System Setup". 3. Open the "Scheme Palette". 4. Select a scheme or double-click on its icon or press the Edit Scheme push button. 5. Using mouse button 2, click on "Icon Text" in the preview area 6. Click on the "Edit Color..." push button. 7. Select the color you want for to be displayed behind the icon text. 8. You can change the icon text background to transparent by selecting the "Transparent color" checkbox when "Icon Text Background" is displayed in the "Window Area" listbox. There are some examples of schemes with transparent icon text background and some examples with a color that is associated with the icon text background. o There are six new tiled bit maps contained in the \os2\bitmap subdirectory. These can be used for setting the lockup bit map or setting the background bit map for schemes or folders. o The Workplace Shell can now participate in Display Device Driver Palette Management. This can be important if you are using a high-resolution bit map for your desktop background or the background for any folder. To enable palette management for the Workplace Shell, add the following statement to the CONFIG.SYS file: SET WORKPLACEPALETTEAWARE=YES Then restart your system. When it restarts, the Workplace Shell can respond to palette management requests like any other palette-aware program. If the focus folder has a 16-color or 256-color background bit map, its colors are loaded into the hardware palette, and displayed with the correct colors. All other visible windows (including other folders containing bit maps) are displayed with colors which closely match their colors. When you switch focus to another window, the hardware palette can be reloaded if that window is part of a palette-aware application or it is a folder that contains a bit map. When you switch focus to a window for a non-palette-aware application, or to a folder which does not contain a bit map, the hardware palette is not changed. o You have to run with Workplace Shell Palette Management set to "OFF" if you are using any programs that are not palette-aware programs but depend on the default palette being loaded. o The Settings Notebook pages for Folder or Desktop Background and Desktop Lockup Background have been combined into a single screen. This is the same screen used to edit the Folder Background. This screen now contains a a preview area, which enables you to view your folder background or lockup screen bit maps. You can open a folder containing bit map files and drag a bit map file to the preview area to set the background bit map for a folder or lockup screen. You can also open the Color Palette and drag a color to the preview area to set the background color for a folder or for lockup screen. There is a new entry in the list of background bit maps: *OS2LOGO. This entry represents a drawn OS/2 logo. This is the bit map that was formerly selected as the lockup bit map if you selected (none). You can now use this bit map for your desktop background, as well as the lockup bit map. NOTE: This bit map is drawn each time the folder is opened, or the system is locked up. It is recommended that you use the *OS2LOGO for a Lockup background or Desktop background because it takes some time for the system to redraw the bit map each time you open a folder. o The Full screen and Partial screen radio buttons and the Auto-dim checkbox have been moved from the Desktop Settings Notebook Lockup page 2 to Lockup page 1. o The bit maps used for drawing a folder's background are scaled or tiled separately for each open view of a folder. The bit maps should be displayed properly no matter how many views are concurrently open, even if the views have vastly different shapes. DISKETTE FORMATTING PROBLEMS ON ISA/EISA SYSTEMS ------------------------------------------------ Symptoms: (one or more of the following) - Abnormally slow diskette formatting - FORMAT gives "Track 0 bad" error - 1.44MB/2.88MB diskette formatted to 720KB - FORMAT program will not accept /F:1.44MB parameter The latest diskette drives can detect the position of the hole on right edge of a diskette to determine the capacity of a diskette (720KB, 1.44MB, 2.88MB) that is to be formatted. Use the following information to stop diskette drives from detecting the diskette capacity if the drive does not use its capacity detection in a standard way. AFTER you install OS/2 modify the CONFIG.SYS as follows: (One 1.44MB drive installed) BASEDEV=IBM1FLPY.ADD /A:0 /U:0 /!MS (Two 1.44MB drives installed) BASEDEV=IBM1FLPY.ADD /A:0 /U;0 /!MS /U:1 /!MS ATM DEMAND LOAD SETTING The Adobe Type Manager (ATM) automatically starts when a WIN-OS/2 session is started. If you do not use the ATM after it is started, memory is wasted and start-up time is increased. A WIN-OS/2 setting has been created so you can stop the ATM from being started automatically. The default setting is "OFF" or disable start up. If you try to change the setting while the WIN-OS/2 session is running, ATM is not automatically started. You must shut down and restart the WIN-OS/2 session before the changed setting becomes active. WIN-OS/2 WINDOW SESSION FAST LOAD SETTING To improve the start-up time for a Windows application in a WIN-OS/2 window session, follow these steps: 1. Open OS/2 System. 2. Open System Setup. 3. Open Win-OS/2 Setup. 4. Click on the Win-OS/2 Settings push button. 5. Change the Fast Load setting to "ON". The steps above start an application which has no other function but to initiate a common WIN-OS/2 session. The Fast Load setting is checked during OS/2 startup to determine if the application should be started. This application is not displayed in the OS/2 Window List. To stop the application from starting a WIN-OS/2 window session set the Fast Load setting to "OFF". In this version of OS/2, when the Fast Load setting is set to "ON", you can stop the application by exiting the Program Manager, shutting down your system and when prompted, closing the Win-OS/2 session. VDM PRIORITY SETTING The task priority of a VDM is constant. A setting was created to allow you to increase the priority of separate VDM's. The new setting, VDM_PRIORITY ranges from 0 to 31, in increments of 1, with a default setting of 0. Modifications to the setting while the VDM is running does not dynamically modify the priority. INTERNATIONAL STANDARDS ORGANIZATION (ISO) FONTS o OS/2 Performance Beta Version 2.99 uses a system proportional font that is designed to meet the International Standards Organization (ISO) 9241 standard and the German DIN 66234 standard when using certain ISO compliant hardware. | ISO fonts cause some text strings to be clipped. If you do not want to use ISO compliant fonts, modify the OS2.INI file to install fonts that are not ISO compliant. Font changes made in the OS2.INI file are global across all applications. If you have REXX installed, you can type the following information into a CMD file and use it to change the font. /* */ call RxFuncAdd "SysIni", "RexxUtil", "SysIni" AppName = "PM_SystemFonts" KeyName = "DefaultFont" FontName = "10.System Proportional Non-ISO" call SysIni "USER", AppName, KeyName, FontName||"0"x exit After the file has been run, shutdown and restart the system. CD-ROM o The Check disk option for a CD-ROM object will not display information about the CD-ROM. To obtain information about the CD-ROM: 1. Point to the CD-ROM drive object. 2. Click mouse button 2. 3. Select the arrow to the right of Open. 4. Select Details view. DUAL BOOT AND BOOT MANAGER o If you use the Dual Boot or Boot Manager feature to switch to DOS, and you install a Windows application that updates the AUTOEXEC.BAT or the CONFIG.SYS file, you must migrate the application after you switch back to the OS/2 operating system. You must also update the OS/2 versions of AUTOEXEC.BAT and CONFIG.SYS to have statements similar to those in the Windows** version of these files. NOTE: Users of DOS 5.0 and 6.3 must add the following line to the AUTOEXEC.BAT file to display the DOSSHELL. SET COMSPEC=C:\DOS\COMMAND.COM This statement must be placed just above the C:\DOS\DOSHELL statement. o Added support for Boot Manager exists on a disk other than Disk 1. To delete and re-install the Boot Manager, exit FDISK after you delete the Boot Manager and re-start FDISK to install Boot Manager again. (This is true even if you are going to place it in the same partition.) You will have to re-enter the partition names. WINDOWS APPLICATION COMPATIBILITY --------------------------------- o The original WIN-OS/2* color scheme was added to the list of available color schemes in the WIN-OS/2 color panel. If you change color schemes and would like to return to the original color scheme, select WIN-OS/2 Original. o Windows scanning programs should be run in a WIN-OS/2 full-screen session to avoid video corruption. o To ensure the integrity of 16-color bit maps on SVGA, XGA, and 8514 systems, run Microsoft Paint Brush** in a WIN-OS/2 full-screen session. o Some messages encountered in a WIN-OS/2 window session request that you select either Ignore or Close, however the only options are Ignore and OK. Select OK instead of Close. o If you are using a WIN-OS/2 window or full-screen session, an OS/2 Presentation Manager session, and a DOS full-screen session, Alt+Esc might not sequence through all of the windows correctly. Alt+Esc might switch to the WIN-OS/2 session every other time or the DOS full-screen session might never be displayed. To avoid this problem, press Ctrl+Esc or press mouse buttons 1 and 2 at the same time to display the Window List then select the desired session. o If you are in a full-screen WIN-OS/2 session and you encounter a problem where transparent desktop icons appear over open windows, minimize or maximize the window to force repainting. o During installation of the Windows 3.1 SDK, a message is displayed stating that the installation program cannot find KRNL286.EXE or KRNL386.EXE. Ignore the message and continue installation. The SDK will function normally. | o If you installed touch-screen support, before you can use Windows, | you must copy TOUCH.DRV from the \SYSTEM directory of the drive | where you have OS/2 installed to the \SYSTEM subdirectory within the | directory where you have Windows installed. o If you are using the Winsleuth Gold hardware diagnostics program: - Do not run Chip test (RAM test program). Chip test attempts to lock hardware interrupts. OS/2 Performance Beta does not allow programs to lock hardware interrupts. - When the video mode hardware test switches from character to graphics mode, a "suspended" message might appear. If the message appears, Select Full-screen from the Sessions System menu. Testing will resume. Windows Application Notes: Access Dr. Watson** Hollywood** WinRoach** ------------------------------------------ Run in a WIN-OS/2 full-screen session. AmiPro** 2.0 and 3.0 -------------------- Equation symbols might be incorrect after the following printer drivers are installed. - Canon** BubbleJet - HP DeskJet** - HP LaserJet II - HP LaserJet III - HP Plotter ATM fonts --------- WIN-OS/2 includes ATM fonts Version 2.5. If you were using a previous version of ATM fonts with your Windows programs, you can upgrade to the new ATM fonts provided by WIN-OS/2. See Chapter 19, "Adobe Type Manager for WIN-OS/2", in the "OS/2 2.1 Using the Operating System" book for instructions. You must set the WIN_ATM WIN-OS/2 setting to "ON" to enable ATM font support. Borland Turbo and Pascal debugger ---------------------------------- Run in a full-screen session. CorelDRAW 2.0 ------------- Install from a DOS or OS/2 session. Facelift** Fonts ---------------- Modify the SYSTEM.INI file after the fonts are installed: 1. Edit the SYSTEM.INI file in the directory where your Windows files reside. 2. Change the SDISPLAY.DRV= line to SDISPLAY.ORG=. 3. Copy the DISPLAY.DRV= line to the next line in the file. Add an "S" to the beginning of the new (copied) line. 4. Change the FDISPLAY.DRV= line to FDISPLAY.ORG=. 5. Copy the DISPLAY.DRV= line to the next line in the file. Add an "F" to the beginning of the new (copied) line. 6. Save and exit the file. 7. Restart WIN-OS/2. FormBase** 1.1 -------------- When you install FormBase, do not choose to modify the CONFIG.SYS file. Modifying the CONFIG.SYS file damages the integrity of the file and your system. FoxPro** 2.5 ------------ Install using a WIN-OS/2 Enhanced-compatibility mode session, but run in a WIN-OS/2 standard-mode session FrameMaker** ------------ Use a mouse to select table cells. Lotus Freelance Graphics** -------------------------- Run the Tutorial in a WIN-OS/2 full-screen session. If you are using Freelance in a WIN-OS/2 window, you might get incorrect background color when viewing a thumbnail of a template. This will not affect the running of the application. Lotus Freelance Graphics** 2.0 ------------------------------ If you are running Lotus Freelance Graphics 2.0 on any machine with an Intel** 386 16Mhz processor it is recommended that you use a Math Coprocessor. Lotus** Improv 2.0 for Windows ---------------------------- Must be installed with WIN-OS/2 running in enhanced mode. Mathematica** 2.2 ----------------- Must be run in a WIN-OS/2 window session. Microsoft Windows Printing System --------------------------------- The OS/2 spooler must be disabled. If you are using a parallel printer, direct the output of the printer to LPT1 instead of LPT1.OS2. Norton Desktop 2.0 ------------------ Run in a WIN-OS/2 full-screen standard-mode session. Powerpoint** 3.0 ---------------- If you are displaying the DROPBXV.PPT and GRIDWRVK.PPT demo slides in 640x480x256, you might see small horizontal line corruption. If you are using a WIN-OS/2 window, you might get incorrect background color when viewing a thumbnail of a template. This will not affect the running of the application. Video for Windows ----------------- Run in a full-screen session. If you configure video animation to run full-screen in Video playback, Deselect Skip video frames if behind, to eliminate any corruption of the video during play. Windows** Version 3.1 with Pen Extensions ----------------------------------------- Not supported. WindowWorks** ------------- Install in a WIN-OS/2 full-screen session. WinTach** --------- Run this application in a WIN-OS/2 full-screen session. DOS APPLICATION COMPATIBILITY ----------------------------- o Use OS/2 system utilities. DOS system utilities might not recognize the extended attributes associated with a file. o OS/2 provides integral disk caching and memory optimization functions. Use of the equivalent functions that are provided with MS-DOS 6.0 is not necessary and may produce errors. o To display the DOS bar in a DOS full-screen or window session, add $i to the PROMPT statement in the AUTOEXEC.BAT file. For example, type: PROMPT $i$p$g Save the modified AUTOEXEC.BAT file. Shut down your system, then restart your system. (Press and hold the Ctrl+Alt+Del keys to restart your system.) o If your application uses its own DOS Protect Mode Interface (DPMI), set the DPMI_DOS_API DOS setting to ENABLED. Example applications include: - Microsoft C/C++ 7.0 Linker - Borland** C - C++** - Turbo C** - Paradox** NOTE: If you are using Microsoft C/C++ 7.0 Linker, configure the program object's DOS_SETTINGs with DPMI_DOS_API=ENABLED. Also, modify the AUTOEXEC.BAT being used for the session so that the Microsoft \C700\BIN directory is searched first. For example: PATH X:\C700\BIN;\C:\OS2;C:\OS2\MDOS;C:\OS2\MDOS\WINOS2;C:\; o It is not necessary to run SHARE.EXE in a DOS session. OS/2's DOS emulation provides SHARE.EXE compatible to that which comes with DOS versions 5.x and 6.x. DOS Application Notes: DOS Games --------- For performance reasons, play in a DOS full-screen session. Change the DOS setting, VIDEO_8514A_XGA_IOTRAP to OFF. For more information about DOS settings, refer to the Master Help Index. Fotoman** --------- If you have problems running Fotoman, set the DOS COM_DIRECT_ACCESS setting ON. Paradox V4.0 ------------- If you have problems running Paradox V4.0 change the DOS setting DPMI_DOS_API = ENABLE. Wayne Gretzky's Hockey Game --------------------------- Not supported. Wing Commander** II ------------------- Set HW_TIMER to OFF. WordPerfect V6.0 ----------------- If you have problems running WordPerfect V6.0 change the DOS setting DOS_FILES = >99. Terminator game --------------- Must use a joystick. Maxis Sim City 2000 for DOS --------------------------- Under the Program tab for the program object, set the Optional Parameters to NO_MEM_CHK. Under the Session Tab, select the DOS_SETTINGS button and set DPMI_MEMORY_LIMIT to 8. Microsoft MSCDEX ---------------- Change the DOS INT_DURING_IO setting to ON. Intel** SatisFAXtion** ---------------------- Must be run in a specific DOS session, unless you do the following before you install the program: 1. Make a copy of your AUTOEXEC.BAT file and name it AUTOEXEC.FAX. 2. Install the program. 3. Rename the AUTOEXEC.BAT file FAX.BAT. 4. Rename the AUTOEXEC.FAX file AUTOEXEC.BAT. 5. Make a program object for the SatisFAXtion program. 6. Change the value of the DOS_AUTOEXEC setting for the object to FAX.BAT. 7. Save and exit the Settings notebook. OS/2 APPLICATION COMPATIBILITY ------------------------------ Do not run an OS/2 screen saver and a Windows screen saver or multiple Windows screen savers at the same time. OS/2 Application Notes: Communication Manager/2 ----------------------- When used with Host Graphics support (HGINST) you might experience shutdown problems. Ensure that the following Graphical Data Display Manager (GDDM) fixes have been applied to the host system: UN36882 - MVS UN38883 - VM/SP UN38884 - VM/XA SP UN38885 - DOS/VSE Netview DM/2 (NVDM/2) --------------------- If you are using the CID method of installation, you will need an updated version of the LAPSCID.DLL file. This file is available as LAPDLL.ZIP on the CompuServe OS2SUPPORT forum, Lib #17 and the OS2BBS on TALKLINK. Pen for OS/2 ------------ If this version of OS/2 is installed over a system with Pen for OS/2 and the CONFIG.SYS is migrated, the pen device might not work after you restart your system. To correct this, you must edit the CONFIG.SYS file. DEVICE=(path)\EMI.SYS DEVICE=(path)\XXX.SYS (where xxx is the name of the pen device) DEVICE=(path)\EIQO2.SYS The above three lines should be in the order shown and must be in the CONFIG.SYS between the following 2 lines: DEVICE=(path)\POINTDD.SYS DEVICE=(path)\MOUSE.SYS If you receive the following message when installing or reinstalling Pen for OS/2: SYS1059: The system cannot execute the specified program., you must apply a fix to the pen installation program. 1.) Do a selective installation of OS/2 to install the PATCH utilities a.) Select "OS/2 system". b.) Select "System Setup". c.) Select "Selective Install" d.) Select the "OK" push button on the "System Configuration" screen. e.) Select Seviceability and Diagnostics Aids f.) Select the Install push button on the "OS/2 Setup and Installation" screen and follow the instructions. 2.) To fix the Pen for OS/2 installation program folow these steps: a.) If you are reinstalling Pen for OS/2: 1. Copy the PEN.DAT file located in the \DISK12 directory on the OS/2 CD-ROM, to the drive and directory where you have Pen for OS/2 installed. 2. Change to the drive and directory where you have Pen for OS/2 installed and at an OS/2 command prompt, type: PATCH PEN.DAT / A and press Enter. b.) If you are installing Pen for OS/2 for the first time: 1. Copy the PEN.DAT file located in the \DISK12 directory on the OS/2 CD-ROM, to the PEN for OS/2 Diskette 1. 2. Insert the Pen for OS/2 Diskette 1 into drive A. 3. From an OS/2 command prompt, switch to drive A, and type: PATCH PEN.DAT /A and press Enter. c.) A message is displayed confirming that the fix has been applied. 3.) Install Pen for OS/2 RUMBA/400 for OS/2 ------------------ If you use RUMBA/400 for OS/2, you might have a more recent version of the MIRRORS.DLL file, located in the \OS2\DLL directory. The file currently shipped with OS/2 2.11 is from Micrografx ToolKit Ver. 3.01, ship level A51 dated 11/16/93. Before you begin installing this version of the operating system, you must back up your current MIRRORS.DLL file. After you install this version of the operating system, you can replace the OS/2 2.11 level of MIRRORS.DLL with the backed up copy you previously created. WordPerfect** 5.2 ----------------- If this application is installed on your system and you reinstall OS/2, do the following: 1. Change to the directory that contains WordPerfect. 2. Type: INSTALL /WPS The WordPerfect application is now updated. You need to shut down and restart your system for these changes to take effect. IBM LAN Server 3.0 Remote Installation Program Load (RIPL) ---------------------------------------------- An updated version from version 3.0 is needed to run with OS/2 Performance Beta. Use the diskette image that is available as 21SERIPL.ZIP on the CompuServe OS2SUPPORT forum, Lib #17 or on the OS2BBS on TALKLINK to run RIPL with this version of OS/2. IBM LAN Server DLR 2.0, 3.0 --------------------------- When running WIN-OS/2 in a VMboot environment, with DOS and IBM LAN Server DOS LAN Requester 2.0 or 3.0, the logoff option causes the WIN-OS/2 session to freeze. This problem occurs when network logon is performed prior to entering WIN-OS/2. To resolve the problem: - Do not use the network logoff in WIN-OS/2 when running LAN Server DOS LAN Requester 2.0 or 3.0. DOS AND WIN-OS/2 MULTIMEDIA APPLICATION COMPATIBILITY ----------------------------------------------------- o The following WIN-OS/2 and DOS Settings should be used for Multimedia applications: DOS/WIN INT_DURING_IO ON DOS/WIN HW_TIMER ON WIN VIDEO_SWITCH_NOTIFICATION ON WIN VIDEO_8514A_XGA_IOTRAP OFF DOS/WIN VIDEO_RETRACE_EMULATION OFF DOS DPMI_MEMORY_LIMIT 8 Applications Notes: Action!** 2.0 ------------- Run in a WIN-OS/2 full-screen session. Change the following line in the AUTOEXEC.BAT file to: SET TEMP=C:\ Animation Works** 1.0 --------------------- Run in 1024x768 resolution. IconAuthor** 4.0 ---------------- If you are running the demo for this program, you must exit and reenter the WIN-OS/2 session before running the actual application. Linkway** Live 1.0 (Tool Series) -------------------------------- Use the following DOS setting to make the demo run properly: DOS_RMSIZE=576 MIDI ---- Make sure that the MIDI mapper and channels (in the Control Panel) is properly set to the sound adapter. Nautilus** 1.6 and 1.76 ----------------------- Run in a WIN-OS/2 full-screen session. NETWORK o The Workplace Shell login is not compatible with Novell** NetWare** 4.0 Directory Services and should be disabled unless you are using the NetWare 4.0 Bindery Compatibility mode. To disable the login: 1. Edit the CONFIG.SYS file. 2. Remove the CONNECTIONS option from SET AUTOSTART. 3. Save and exit the CONFIG.SYS file. 4. Restart the system to activate the changes. o You might experience problems with WIN-OS/2 if you are using Novell Netware Requester 2.0 on this version of OS/2. To correct the problems, upgrade to Novell Netware Requester for OS/2 Version 2.1. o If you are using the NetWare Requester version 2.01, (ships with NetWare 4.0) but have no NetWare 4.0 servers, you can increase the speed of the login process by turning the Directory Services off. To turn the services off: 1. Edit NET.CFG file in the root directory of the boot drive. 2. Add Directory Services Off to the file. 3. Save and exit the file. o Novell NetWare Requester 2.0 and 2.01 programs NMPIPE.SYS, NPSERVER.SYS, and NPDAEMON.EXE require the following information to be added to the OS2VER file. To add this information to the file: 1. At an OS/2 command prompt, type: ATTRIB -h -r -s OS2VER 2. Edit the OS2VER file in the root directory of the boot drive. 3. Type the following information in the file: 20=NMPIPE.SYS 20=NPSERVER.SYS 20=NPDAEMON.EXE 4. Save and exit the file. 5. Type ATTRIB +h +r +s OS2VER o If you are using FFST/2 (for example, if you enable the FFST/2 feature when installing Communications Manager/2 or Data Base Manager/2), REM out the "RUN=...\EPW.EXE" statement in your CONFIG.SYS file. To utilize FFST/2 technology, add a "DETACH EPW.EXE" as the first statement in your STARTUP.CMD file. o NetWare Client for OS/2 uses a default frame type of 802.2 on Ethernet networks. This is a change from the previous default frame type of 802.3. Some routers do not support Ethernet 802.2 frame types. If you are having difficulty connecting to your server, add 802.2 Ethernet frame support at the server, and ensure your router has the latest revision of software. o When using NetWare Client version 2.1 for OS/2, load NETX.EXE into both global and private DOS sessions. The NetWare Client installation program can modify AUTOEXEC.BAT and any other DOS_AUTOEXEC files you specify. You must also change the DOS_LASTDRIVE setting for each DOS session to the last local drive on your system. o The Virtual Loadable Module (VLM) version of the NetWare DOS Client kit can be run in a DOS 5.X or 6.X VMB session under OS/2 in either global or private mode. Use DOSVIPX to allow sharing of the network adapter. This allows limited access to NetWare 4.0x Directory Services in a DOS VMB session. o The Novell file system fails to recognize LPT4 through LPT9 print devices and creates a disk full file instead. Copy or pipe to \DEV\LPTx might function as a workaround or drag and drop using the Workplace Shell. o Pressing Ctrl-C in a NetWare program, running in a DOS session might cause a SYS3175 error and the session to fail. The application will end properly. If you still require a session, start a new one. o Using a wildcard with the ATTRIB command can produce erratic results. Use NDIR or FLAG instead. o WIN-OS/2 File Manager and some other programs might show inaccurate drive information when running in a private NetWare session. Drives that are mapped in global or OS/2 sessions might appear as local drives. You can remap these drives to other volumes or directories without affecting the global session mappings. NOVELL DOS REQUESTER There are three ways to use Novell DOS Requester with OS/2. o VM Boot from Drive A If you install OS/2 Performance Beta on drive C and you have installed it over a Novell DOS Requester, you can use the requester after OS/2 is installed by creating a VM Boot Diskette and selecting the "Boot from Drive A" object on your desktop. To do this: 1. Create a DOS Bootable Diskette with a version of DOS later than 3.20. 2. Make the following changes to the CONFIG.SYS file: DEVICE=A:\FSFILTER.SYS A:\HIMEM.SYS A:\EMM386.SYS FILES=60 BUFFERS=30 SHELL=A:\COMMAND.COM /E:2000 /P LASTDRIVE=last physical drive on your system 3. Copy the files from the OS/2 directory to the DOS directory. 4. Insert the DOS Diskette into Drive A. 5. Select DOS from Drive A to start your Novell DOS Requester. o Boot Manager from Drive C If OS/2 Performannce Beta is installed on a logical drive, (for example, drive D), then DOS, Windows Version 3.1, and Novell DOS Requester will start from drive C. Follow these steps: 1. Copy D:\OS2\MDOS\FSFILTER.SYS to C. 2. Make the following changes to the CONFIG.SYS file: DEVICE=C:\FSFILTER.SYS DEVICE=D:\OS2\MDOS\HIMEM.SYS DEVICE=D:\OS2\MDOS\EMM386.SYS FILES=60 BUFFERS=30 SHELL=C:\COMMAND.COM /E:2000 /P LASTDRIVE=last physical drive on your system 3. Make the following changes to the AUTOEXEC.BAT file: @ECHO OFF PROMPT $P$G PATH C:\WIN31;C:\DOS;C:\NETWARE C:\NETWARE\LSL.COM C:\NETWARE\TOKEN.COM C:\NETWARE\IPXODI.COM C:\NETWARE\NETX.EXE 4. Restart your system with OS/2. 5. Select OS/2 System. 6. Select the Command Prompts folder. 7. Make a copy of the DOS from Drive A object that is located in the Command Prompts folder. For information about copying an object, refer to the "OS/2 2.1 Using the Operating System" book. 8. Point to the copy of the DOS From Drive A object. 9. Click mouse button 2. 10. Select the arrow to the right of Open. 11. Select Settings. 12. Select the Session tab. 13. Select DOS Settings. 14. Select DOS_STARTUP_DRIVE. 15. Type C: in the Value field. 16. Select Save. 17. Double-click on the title-bar icon to close the notebook. 18. Select DOS from Drive C to start Boot Manager. o Dual Boot If you install this version of OS/2 on drive C and you have Novell DOS Requester on your workstation, you can use the Dual Boot feature of OS/2 to switch to DOS and run the requester. Select the Dual Boot object in the Command Prompts folder to start DOS from drive C. DOS has full network support. Novell DOS Requester must be run in either a DOS or WIN-OS/2 session. The LAN adapter cannot be shared with any other application such as Communications Manager that attempts to utilize the LAN adapter. Using the NetWare Requester for the OS/2 operating system might remove some of the limitations of this configuration. UPGRADING TO NETWARE REQUESTER FOR OS/2 Install NetWare Requester for OS/2 2.1 following the manufacturer's directions. This product provides network support for DOS, OS/2, and Windows Version 3.1. To make the Windows program aware of the network: 1. Select the Windows Setup object located in the Main folder. 2. Select Options. 3. Select Change System Settings. 4. Select Novell NetWare (DOS Version 3.21 and higher). 5. Insert the Windows diskette number 2 when prompted. 6. Select Restart Windows. A network object appears in the Windows Control Panel. 7. Select the Network object. DISPLAY ADAPTERS (IMAGE, SVGA, XGA, 8514) o The OS/2 operating system will experience video problems similar to those observed in a DOS environment. These problems are due to the failure of a BIOS video mode set. An example of this problem is the video image on an ALR** Modular PS with a Flexview** 2x SVGA display fails to occupy the entire screen in 1024 x 768 mode. o If you are using an LCD display and have difficulty locating the mouse pointer on the screen, you can increase the size of the pointer if you are using 640x480 resolution. To change the size of the pointer (if you have REXX installed): 1. Use an editor to create a file called LARGE.CMD. 2. Add the following information to the file. /* LARGE.CMD Set VGA pointers to large */ /* (c) Copyright IBM Corp. 1992, All rights reserved */ call RxFuncAdd "SysIni", "RexxUtil", "SysIni" call SysIni "USER", "PM_IBMVGA", "CURSOR_SIZE", "1" say Result exit 3. Save and exit the file. 4. At an OS/2 command prompt, type "LARGE" and press Enter. This program will increase the size of the cursor. To force a standard size pointer, replace the "1" in the program with a "2". To let the system select the size of the pointer, replace the "1" in the program with a "0". o Users of the NCR** Safari notebook, SSL/25, should modify the following information in the CONFIG.SYS file on their startup drive to allow video register shadowing to be processed correctly in OS/2 Performance Beta. DEVICE=C:\OS2\MDOS\VVGA.SYS to DEVICE=C:\OS2\MDOS\VSVGA.SYS o Systems with Image Adapters running in dual-display modes will lose DOS window support after a DOS full-screen or OS/2 full-screen session has been invoked. The system must be restarted to reinstate the DOS window environment. The problem can be avoided by turning off the dual display mode under the Image Adapter setup. S3 FUNCTIONAL RESTRICTIONS -------------------------- o After Dark** for Windows images that move from left to right do not perform properly at 640x480x16M resolution. o To avoid a General Protection fault while loading Ventura Publisher** for Windows, be sure it is in one of the 256-color resolutions. o To avoid a trap in Lotus** 1-2-3** for OS/2, do not attempt to run the program at 16.7 million colors. o WordPerfect** 5.1 and 5.2 for Windows produce a General Protection fault when the "Print Preview" option is selected while you are using 800x600x64K or 600x480x16 million color mode. o The software motion video feature will take advantage of a 1MB aperture on video adapters and systems where it is available to improve the performance of video playback in 64K-color modes. For those systems with nonstandard locations, the actual physical address of the aperture must be provided in the following CONFIG.SYS statement: SET VIDEO_APERTURE=xxxh where "xxx" is a hexadecimal value in units of 1MB, representing the actual physical address to map to the aperture. For example, the IBM PS/ValuePoint systems must have the statement: SET VIDEO_APERTURE=400h to use a physical address at 1GB. NOTE: If you are using the 256-color mode and your desktop appears to be darker than other color modes, you must edit the SVGADATA.PMI file located in the \OS2 directory. Change the following statement from: HI-COLOR DAC by .... to: HI-COLOR DAC by unknown To make the changes effective, you must restart your system. ATTENTION IBM VALUEPOINT USERS: ------------------------------- You might encounter a blank screen while switching from one window to another when using any one of the following: PS/ValuePoint Display Models: 6314 6317 6319 PS/ValuePoint Computer Models: 6382 6384 6387 To correct or avoid this problem, you MUST do the following: 1. Make sure that the flash EEPROM level of your system is 61 or later. To check the EEPROM level: a. Begin the Configuration Utility program by turning the system off and then on again. b. During the memory count, press F1. (The memory count appears in the upper left corner of the screen as numbers followed by KB.) c. When the Configuration Utility screen appears, look for the Flash EEPROM Revision Level. d. The fifth and sixth characters in the Flash EEPROM Revision Level represent the actual revision level. e. If the revision level is less than 61, you must install the ValuePoint Flash BIOS update. To get the required ValuePoint Flash BIOS update do the following: f. Access the IBM PC Company Bulletin Board System (1-919-517-0001), then download the VP2FL61A.DSK file, which is the Flash BIOS Update Level 61. If you do not have access to a modem, you can call the IBM Help Center (1-800-772-2227) and request this update on diskette. 2. You must install both the flash update (if the revision level is less than 61) and the S3 Video Driver Update Package. SVGA CONSIDERATIONS o The Western Digital** 90C31 SVGA chipset will have video problems when Windows 3.1 applications are run. o If you are using a ZEOS** system with Speedstar** VGA, you must run the VMODE utility supplied with the system to configure the display during the display driver installation. o Zenith Data Systems** with Headland HT208 and Hewlett Packard** systems with HT209, do not support high resolution modes even though you can successfully set these modes and install high resolution drivers. If a high resolution mode is used, a white half-screen will be displayed. To correct this problem, use Selective Install to install VGA. o If you have a Sigma Legend** display adapter you might experience minor video corruption on the desktop when you switch between the desktop and DOS if they are running in different modes. This can be corrected by using the DOS utility that is packaged with this display adapter to set the DOS session to the same mode as the desktop. XGA CONSIDERATIONS o If you are using a dual display system with XGA as the primary display and VGA as the secondary display, you might see some minor corruption when the XGA display is set to a resolution with 65536 colors. This corruption will be on the display that does not have focus and will not interfere with the operation of the system. o On dual display configurations with XGA-2 as the primary display and VGA as the secondary display, the DOS full-screen session might be corrupted if a Windows** application is started in a window session. To recover from this situation, shutdown and restart the system. o If you are using Dual Boot with an XGA-2 adapter, you must modify the CONFIG.DOS file: 1. Edit the \OS2\SYSTEM\CONFIG.DOS file. 2. Locate the line DEVICE=C:\DOS\EMM386.EXE RAM 2048 X=nnnn-nnnn 3. Change nnnn-nnnn to C000-CFFF. 4. Save and exit the file. o On IBM P75 systems, there might be some corruption on the screen whenever several icons are selected and moved together. This corruption can be eliminated by clicking mouse button 2 to bring up the pop-up menu; then selecting Sort. o An IBM P75 system with an external monitor attached might only have the 640x480x16 resolution selection on the the System Settings Screen page. If the external monitor is capable of displaying higher resolutions, use the P75 reference diskette to disable the built-in plasma display. o If you are using an XGA system, the hash lines around the icons of open applications might change color unexpectedly. This does not interfere with the operation of the system. o If you are using an XGA system, extra lines might appear on the face of the OS/2 System Clock between the quarter (:15) and half (:30) hour. These lines do not interfere with the operation of the clock. o If you run VGA DOS graphics applications on the OS/2 desktop and your system does not have VGA support, your desktop might be corrupted. 8514 CONSIDERATIONS o If you are using the 1MB version of an ATI** Graphics Ultra** Pro adapter, the VGA memory must be set to SHARED to work properly with the OS/2 8514 display driver. This might cause some DOS applications running in the background to corrupt the desktop. To correct this problem, you must upgrade to the 2MB version of the Graphics Ultra Pro and set the VGA memory to 256K or greater. NOTE: In the "OS/2 Installation Guide", it states that the ATI Graphics Ultra Pro must be configured to IBM DEFAULT for the 640x480 display type. This setting might be referred to as 60Hz rather than IBM DEFAULT. o If you are using a system with an 8514 adapter with Windows applications running in a WIN-OS/2 window session in separate VDMs, video corruption might occur in bitmaps when you cut and paste between applications. o After you start a WIN-OS/2 window session, 256 color bitmaps might become discolored due to the sharing of the 256 color palette. This should not affect the running of the applications. o Selecting windows in Mathematica might not bring focus to the proper window. ΓòÉΓòÉΓòÉ 4.5. Personal OS/2 Beta README Part 2 ΓòÉΓòÉΓòÉ Personal OS/2 Beta README Part 2 AUDIO ADAPTERS Audio support in WIN-OS/2 and DOS sessions is dependent on installed drivers. You should install the audio adapter driver that came with your audio adapter. When installing audio support for WIN-OS/2, be sure to install both DOS and Windows device drivers. Configure both drivers to use the same interrupt level and DMA channel. For additional audio information, refer to the README file located in the \MMOS2 directory. o MMPM/2 installs Sound Blaster** support for OS/2 only, not WIN-OS/2 or DOS. o The following drivers are available with the Audio Capture and Playback Adapter* (ACPA): - ACPADD.SYS - ACPADD2.SYS - ACPAK12.SYS - ACPA.DRV The latest updates are available on the IBM Bulletin Board Service. o MMPM/2 installs ACPA support for OS/2 only, not WIN-OS/2 or DOS. There are two ways to get DOS ACPA support in DOS sessions: 1. Edit the CONFIG.SYS file. 2. Add DEVICE=C:\ACPAK12.SYS 3. Save and exit the CONFIG.SYS file. 4. Copy the ACPAK12.SYS file to the C:\ directory. 5. Restart the system to activate the changes. Or 1. Point to the DOS full-screen or window object. 2. Click mouse button 2. 3. Select the arrow to the right of Open. 4. Select Settings. 5. Select the Session tab. 6. Select DOS Settings. 7. Select DOS_DEVICE. 8. Type C:\ACPAK12.SYS in the Value field. 9. Select Save. 10. Double-click on the title-bar icon to close the notebook. 11. Copy the ACPAK12.SYS file to the C:\ directory. To install WIN-OS/2 ACPA support: 1. Access the Control Panel in WIN-OS/2 Main. 2. Select Drivers. 3. Select Add. 4. Select Unlisted or Updated Drivers. 5. Select OK. 6. Insert the diskette containing the ACPA driver into drive A. 7. Type A: 8. Select OK. 9. When the Add Unlisted or Updated Driver screen is displayed, select the M-Audio sound driver. 10. Select OK. 11. When the IBM ACPA Driver Setup screen is displayed, select Proper Input Source. DEFAULT IS MIC NORMAL Select OK. 12. Select Restart Now. 13. Open WIN-OS/2 session. 14. Select the Control Panel in WIN-OS/2 Main. 15. Select MIDI Mapper. 16. Select the down arrow for Name. 17. Select Extended MIDI for ACPA. 18. Select Edit. 19. Select Yes. 20. Select port name for all 16 SRC channels to be IBM M-Audio MIDI SYNTH. 21. Select OK. 22. Select Yes. 23. Select Close. 24. Close the WIN-OS/2 session. o To add WIN-OS/2 Sound Blaster support: 1. Install the DOS device driver following the instructions that came with the adapter. Use an OS/2 DOS session for the install. 2. Install the Windows driver. 3. When prompted, type: \OS2\MDOS\WINOS2 and press Enter. Your SYSTEM.INI file will be updated. NOTE: Be sure to use the same I/O address, interrupt, and DMA settings used during installation of the DOS drivers. PRINTERS o If you are using the HP** LaserJet** printer driver, some complex images might not print correctly when LaserJet performance options are enabled. If you experience incorrect output or degraded printer performance, return the performance options to the disabled state. To change the performance options: 1. Point to the printer object. 2. Click mouse button 2. 3. Select the arrow to the right of Open. 4. Select Settings. 5. Select the Printer driver tab. 6. Select Job properties. 7. Change the performance options to their default settings. 8. Double-click on the title-bar icon to close the notebook. o If you experience problems while printing bitmaps from an application while using the PostScript printer driver, Select the Printer-specific format option on the Queue options page in the Settings notebook of your printer object. SCANNERS If you have a Logitech hand scanner on an AT bus computer, run the scanner at the 100, 200, or 300 DPI setting. ADVANCED POWER MANAGEMENT SUPPORT FOR PORTABLE COMPUTERS o This version of OS/2 includes APM support that was not available for the original OS/2 2.1 release. Laptop computers with 32-bit protect-mode APM are now supported. Refer to README.INS for additional information on APM support. Laptop computers with the following are compatible with OS/2 for Windows Advanced Power Management: o 16-bit protect-mode APM in the BIOS o 32-bit protect-mode APM Laptop computers that have no APM support in BIOS or have only real-mode APM support are not compatible with OS/2 for Windows Advanced Power Management. The DOS utility program APMHERE, which is available on the IBM BBS, can quickly determine whether your computer has Advanced Power Management support in conformance with the APM 1.0 Specification (dated 1/91). Systems with BIOS dates before January 1991 will not have the protect-mode APM support in their BIOS. LAPTOP COMPUTERS WITH APM SUPPORT ---------------------------------- The table that follows lists the laptop computers that have Advanced Power Management support. (This list represents only systems tested as of January 27, 1994.) MANUFACTURER MODEL COMMENTS ---------------------------------------------------- Acer AcerNote 730 BIOS information displayed on start up: PhoenixBIOS(TM) A486 Version 1.03 R1.0 Acer AcerNote 750 AST Research PowerExec 4/25SL Perform the Inc. Color Plus following 486SL/25 Active steps: Matrix Color 1. Press FN F1 keys to get BIO access 2. Select Power Management. 3. Click on Power Management Section 4. Follow the Characterize the Battery instructions COMPAQ 4/25 COMPAQ CONTURA 4/25 Monochrome, VGA COMPAQ CONTURA 4/25C 486SL/25 Active Matrix COMPAQ CONTURA 4/25cx See NOTE 1. COMPUDYNE 4SL/25 BIOS information SubNOTEBOOK displayed on start up: PhoenixBIOS(TM) LAP486SL Version 1.03 PhoenixMISER(TM) 486L v2.0 80486SL BIOS Version 1.11 5/28/93 Gateway 2000 ColorBook 486SX/25 486SX/25 Dual Scan Color Gateway 2000 ColorBook See NOTE 1. 486DX/33 Requires 486DX/33 Dual corrected BIOS Scan Color from System Soft, Inc.; see NOTE 2. Gateway 2000 HandBook See NOTE 1. 486DX2/40 Requires 486DX2/40 corrected BIOS Monochrome from System Soft, Inc.; see NOTE 2. IBM P/S NOTE 425, For OS/2 for Windows, 425c use F1 to display the configuration panel and set RESUME ON ALARM to OFF when running the Alarm mini-application. IBM ThinkPad 700, Version 1.2 or higher 700C, 720, 720C, of the reference and diagnostic diskettes are required. IBM ThinkPad 750 See NOTE 4. NCR Corp. NCR 3150 BIOS information 486SX/25 Active displayed Matrix Color on start up: PhoenixBIOS(TM) A486 Version 1.03 (C)1989-1993 Phoenix Technologies Ltd. All Rights Reserved. Reference ID 15 NCR Corp. SAFARI Battery Life, Power Source, and Battery State information is incorrect. NEC Technologies UltraLite Versa Inc. Sharp 6800 Battery Life, Power Source, and Battery State information might be incorrect. Texas Instruments TravelMate 4000, 486DX2, 50MHz Toshiba T1950, T1950CS, T1950CT 486DX2/40 Mono, Dual Scan Color, Active Matrix Color Toshiba T3400, T3400CT 486SX/33 Monochrome, Active Matrix Color Toshiba T4700CS 486DX2/50 Dual Scan Color Toshiba T4700CT 486DX2/50 Active Matrix Color Toshiba T6600C, T6600C/CD, T6600C/CDV 486DX2/66 Active Matrix Color Twinhead Corp. SubNote 486DX/33 Does not have 486DX/33 the CPU clock Monochrome slowdown feature. See NOTE 3. Zenith MastersPort 386SLe Zenith ZNOTE 325L NOTE 1: To run OS/2 for Windows in these models, change the statement "BASEDEV=IBM1S506.ADD" in CONFIG.SYS to the following: BASEDEV=IBMINT13.I13 NOTE 2: For these models, the following BIOS information is displayed on start up: Systems Soft Bios for 80486/82C463 v1.01 (2069-09) Contact Systems Soft, Inc. (508-651-0088) for a corrected version of BIOS. NOTE 3: The OS/2 APM calls into the BIOS APM once per second to check if it is OK to do a suspend. The following BIOS do not return OK to suspend on OS/2 APM calls if the video display is active or changes during the CMOS suspend timeout: o PhoenixBIOS Version 1.03 o Phoenix NoteBIOS 486/OPTi463 Version 1.03 o PhoenixMISER V2.0 NOTE 4: Reinstall the ThinkPad video drivers after you finish installing OS/2 for Windows. PORTABLE COMPUTERS WITHOUT APM SUPPORT ------------------------------------ The table that follows lists the laptop computers that do not have APM support in their BIOS; however, they can be configured to run OS/2 for Windows if APM is not installed. (This list represents only systems tested as of January 27, 1994.) If you have installed OS/2 APM, ensure that it is removed properly by doing the following: o Remove the following two APM device statements from CONFIG.SYS: DEVICE=C:\OS2\APM.SYS DEVICE=C:\OS2\MDOS\VAPM.SYS o Delete the APM.SYS and VAPM.SYS files from the corresponding hard disk subdirectories. This gains about 1 second during startup and frees up hard disk space. MANUFACTURER MODEL COMMENTS ----------------------------------------------------- COMPAQ LTE-386s/25 See NOTE 1. COMPAQ LTE LITE 25/c See NOTE 1. 386SL COMPAQ LTE LITE 4/25e, See NOTE 1. 4/25c, 486SL/25 Active Matrix COMPUDYNE 3SXL/25 SLIMNOTE BIOS information displayed on start up: PhoenixBIOS(TM for VLSI Laptop 80386 BIOS Version 1.01 R2-1 06/09/92 IBM L40SX Discontinued product. See NOTE 2. IBM P/S NOTE, Model For OS/2 for Windows, 2141 use F1 to get the configuration panel and set RESUME ON RING and RESUME ON ALARM to OFF. IBM PS/2 N51 Install using 386SX/SLC UINSTALL. 8551-025 Librex T386SX If screen is black after resume, toggle the F1 key (Suspend key) to refresh screen. Northgate ZX Portable BIOS information 486SX/25 displayed on start up: Phoenix A486 version 1.01 See NOTE 3. Texas Instruments TravelMate 4000 See NOTE 3. WinDX2, 486DX/25 MHz Texas Instruments TravelMate 4000 See NOTE 3. WinSX Texas Instruments TravelMate 4000e See NOTE 3. SX25 Passive Matrix Color Texas Instruments TravelMate 4000e See NOTE 3. WinDX2/50 Active Color Texas Instruments TravelMate 4000 See NOTE 3. WinDX2/50 486DX2/50 Monochrome Toshiba T1800 386SX/20 See NOTE 4. Monochrome Toshiba T1850, T1850C See NOTE 4. 386SX/25 Monochrome, Dual Scan Color Toshiba T1900, T1900C See NOTE 4. 486SX/20 Monochrome, Dual Scan color Toshiba T2200SX 386SX/20 See NOTE 4. Monochrome Toshiba T3100SX 386SX/16 See NOTE 4. Mono Plasma Toshiba T3300SL 386SL/20 See NOTE 5. Monochrome Toshiba T4400SX, See NOTE 4. T4400SXP, T4400SXC 486SX/25 Mono, Plasma, AMC Toshiba T4400C 486DX/33 See NOTE 4. Active Matrix Color Toshiba T4500, T4500C See NOTE 4. 486SX/20 Monochrome, Active Matrix Color Toshiba T4600, T4600C See NOTE 5. 486SL/33 Monochrome, Active Matrix Color NOTE 1: To run OS/2 for Windows in these models, change the statement "BASEDEV=IBM1S506.ADD" in CONFIG.SYS to the following: BASEDEV=IBMINT13.I13 NOTE 2: For OS/2 for Windows APM, access the IBM BBS and download the following three files: o TGSFX.COM (located in file area 4) o RFL40SXA.TG0 (located in file area 27) o L40PWR.ZIP (located in file area 37) Run TGSFX.COM to install the TELEGET.EXE program. Then do the following: 1. Create a new L40SX reference diskette by using TELEGET.EXE to unpack RFL40SXA.TG0 onto a 1.44MB formatted diskette. 2. Use PKUNZIP to unzip the L40PWR.ZIP to obtain new IDLE.EXE and PWRMGMT.SYS files. 3. Replace the IDLE.EXE and PWRMGMT.SYS files on the newly created L40SX reference diskette with the new IDLE.EXE and PWRMGMT.SYS files obtained from the previous step. 4. Restart L40SX with the resulting reference diskette in A drive and configure it with APM. 5. Verify the APM configuration by selecting VIEW CONFIGURATION from the installation menu. 6. Exit the configuration. 7. Power off the computer and restart OS/2. NOTE 3: Contact the manufacturer for newer versions of their BIOS that have APM support. NOTE 4: These models require the Toshiba APM driver (OS2RES.EXE) available from the Toshiba BBS (714-837-4408). This Toshiba driver will provide partial power management capabilities under OS/2 for Windows. NOTE 5: While running OS/2, you can use the special power-saving keys but the additional capability of OS/2 protect-mode APM is not supported. PROGRAMMING TOOLS ----------------- Enhancements have been made to two of the tools that come with the OS/2 operating system. These enhancements are not described in the OS/2 documentation. This section describes these enhancements. LINK386 Three additional options are available in LINK386. o /EXEPACK:{1|2}ΓêÖ EXEPACK causes pages of code and data in the file to be compressed. The OS/2 loader will automatically decompress these pages when the program is executed. The /EXEPACK:1 option causes LINK386 to use the compression algorithm that is compatible with OS/2 2.0, 2.1, and 2.11. The /EXEPACK:2 option causes LINK386 to use a compression algorithm that is incompatible with OS/2 2.0, 2.1 and 2.11. o /NOOUTPUTONERRORΓêÖ This option will prevent LINK386 from creating the executable file if an error is encountered. o /NOSECTORALIGNCODEΓêÖ LINK386 normally aligns pages of code on sector (512 byte) boundaries. This reduces the time to load the pages when the application is executed. The /NOSECTORALIGNCODE option is provided to turn off this feature. Pages of code would then be aligned based on the value used in the /ALIGN option. RC - THE RESOURCE COMPILER Two additional options are available in RC, the Resource Compiler. o -x{1|2}ΓêÖ This option causes resources to be compressed. These resources will be automatically decompressed when the resource is accessed. The -x1 option causes RC to use the compression algorithm that is compatible with OS/2 2.0, 2.1, and 2.11. The -x2 option causes RC to use a compression algorithm that is incompatible with OS/2 2.0, 2.1 and 2.11. The -x2 option will produce smaller executable files that can access resources faster. WARNING: The compression algorithm in the LINK386 and RC tools in this beta is much more effective than previous versions but is incompatible with tools from prior versions of the Developer's Toolkit for OS/2, specifically MSGBIND. Do not use the new compression algorithm if you intend to use MSGBIND. PATHS The new programming tools are placed in the \OS2 directory. If your PATH is set to use the versions of LINK386 and RC that come in the Developer's Toolkit for OS/2, you will either need to copy the new programs to your existing tools directory, or change your PATH statement to include the \OS2 directory before your existing tools directory. KERNEL DEBUG FILES ------------------ The kernel debug diskettes included with the Developer's Toolkit for OS/2 2.1 will not work with this beta. The kernel debug files for this beta are located on the CD-ROM. Please refer to the Kernel Debugger Installation README file in the OS2TK21\DEBUG subdirectory on the CD for more information. Usually, the kernel debug files are available only in the Developer's Toolkit for OS/2. For this beta release, they are available in the base operating system. The final versions of these files will be available only in the Developer's Toolkit for OS/2. Serviceability and Diagnostic OS2KRNL ------------------------------------- This release of OS/2 provides two versions of the OS2KRNL file. They are the default install OS2KRNL and the Serviceability and Diagnostic OS2KRNL. The Serviceability and Diagnostic OS2KRNL provides support for standalone dump, trace functions, SMP/2, DosPTrace API, DosDebug API and application debuggers. The default OS2KRNL does not support these functions. To install the support for the Serviceability and Diagnostic OS2KRNL you must use Selective Install and select "Serviceability and Diagnostic Aids". Before you can run Selective Install from the OS/2 CD-ROM, you must place the OS/2 CD in the CD-ROM drive attached to your system. If after installation you want to switch OS2KRNL, at an OS/2 Command Line, type: SWAPKRNL and press Enter. Then follow the instructions on the screen. To activate the new kernel you must shutdown and reboot your system. NOTE: If you have a system with a CD-ROM drive attached, have installed the Service and Diagnostic OS2KRNL and attempt to switch to the Default OS2KRNL you might receive and error message. If you receive the error message, select "Return Error to Program", and then press Enter. The process will continue successfully. Before you can run Selective Install from the OS/2 CD-ROM, you must place the OS/2 CD in the CD-ROM drive attached to your system. TRADEMARKS AND SERVICE MARKS ____________________________ The following terms, denoted by an asterisk (*) in this README, are trademarks or registered trademarks of the IBM Corporation in the United States or other countries: Audio Capture and Playback Adapter ------------------------------------------ IBM ------------------------------------------ IBM PS/ValuePoint ------------------------------------------ Linkway ------------------------------------------ Micro Channel ------------------------------------------ Multimedia Presentation Manager/2 ------------------------------------------ OS/2 ------------------------------------------ WIN-OS/2 ------------------------------------------ Workplace Shell ------------------------------------------ XGA ------------------------------------------ The following terms, denoted by a double asterisk (**) in this README, are trademarks of other companies as follows: Trademark: Owner: -------------------------------------------------------------- Action! Expertelligence -------------------------------------------------------------- After Dark Berkely Systems, Inc. -------------------------------------------------------------- ALR Advanced Logic Research, Inc. -------------------------------------------------------------- Animation Works Gold Disk Inc. -------------------------------------------------------------- APM Astek International Ltd. -------------------------------------------------------------- ATI ATI Technologies, Inc. -------------------------------------------------------------- Borland Borland International, Inc. -------------------------------------------------------------- Canon Canon Kabushiki Kaisha -------------------------------------------------------------- CompuServe CompuServe Inc. -------------------------------------------------------------- C++ AT&T, Inc. -------------------------------------------------------------- Describe Lenname Advanced Products -------------------------------------------------------------- DeskJet Hewlett-Packard Company -------------------------------------------------------------- Facelift Bitstream Inc. -------------------------------------------------------------- Flexview Nutmeg Systems -------------------------------------------------------------- FormBase Xerox Corporation -------------------------------------------------------------- Fotoman Logitech International -------------------------------------------------------------- FoxPro Fox Holdings, Inc. -------------------------------------------------------------- FrameMaker Frame Technologies Inc. -------------------------------------------------------------- Freelance Graphics Lotus Development Corporation -------------------------------------------------------------- Hollywood Claris Corporation -------------------------------------------------------------- HP Hewlett-Packard Company -------------------------------------------------------------- HP LaserJet Hewlett-Packard Company -------------------------------------------------------------- IconAuthor Aimtech Corporation -------------------------------------------------------------- Intel Intel Corporation -------------------------------------------------------------- Legend Sigma Designs Inc. -------------------------------------------------------------- Logitech Logitech, Inc. -------------------------------------------------------------- Lotus Lotus Development Corporation -------------------------------------------------------------- Mathematica Wolfram Research, Inc. -------------------------------------------------------------- Microsoft Microsoft Corporation -------------------------------------------------------------- Nautilus Softshell Systems -------------------------------------------------------------- NCR NCR Corporation -------------------------------------------------------------- NET NCR Corporation -------------------------------------------------------------- NetWare Novell, Inc. -------------------------------------------------------------- Novell Novell, Inc. -------------------------------------------------------------- Paint Brush Microsoft Corporation -------------------------------------------------------------- Panasonic Matsushita Electric Industrial Co., Ltd. -------------------------------------------------------------- Paradox Borland International, Inc. -------------------------------------------------------------- PostScript Adobe Systems Inc. -------------------------------------------------------------- Powerpoint Microsoft Corporation -------------------------------------------------------------- Sound Blaster Creative Labs, Inc. -------------------------------------------------------------- SpeedStar Diamond Computer Systems, Inc. -------------------------------------------------------------- Turbo C Borland International, Inc. -------------------------------------------------------------- Ultra ATI Technologies, Inc. -------------------------------------------------------------- Ventura Publisher Ventura Software, Inc. -------------------------------------------------------------- Western Digital Western Digital Corporation -------------------------------------------------------------- Windows Microsoft Corporation -------------------------------------------------------------- WindowWorks Spinnaker Software Corporation -------------------------------------------------------------- WinTach Texas Instrument -------------------------------------------------------------- WordPerfect WordPerfect Corporation -------------------------------------------------------------- Zenith Data Systems Zenith Electronics Corporation -------------------------------------------------------------- ZEOS ZEOS International Ltd. -------------------------------------------------------------- IBM DISCLAIMS ALL WARRANTIES, WHETHER EXPRESSED OR IMPLIED, INCLUDING WITHOUT LIMITATION, WARRANTIES OF FITNESS AND MERCHANTABILITY WITH RESPECT TO THE INFORMATION IN THIS DOCUMENT. BY FURNISHING THIS DOCUMENT, IBM GRANTS NO LICENSES TO ANY RELATED PATENTS OR COPYRIGHTS. Copyright IBM Corporation, 1993, all rights reserved. ΓòÉΓòÉΓòÉ 4.6. Personal OS/2 Beta Installation README ΓòÉΓòÉΓòÉ Personal OS/2 Beta Installation README OS/2 Performance Beta Version 2.99 Special Edition for Windows Installation Readme -------------------------------------------------------- Welcome to OS/2* Performance Beta Version 2.99. This document provides you with information you need after you install this version of OS/2. This product is designed for licensed users of Microsoft** Windows** Version 3.1 product. After the installation of this product, your system will allow you to run DOS, Windows, and OS/2 applications on the same desktop. Throughout the documentation provided with this product, all references to WIN-OS/2* apply to running your Windows Version 3.1 programs under this version of OS/2. This README contains helpful hints found during our testing. It is divided into the following categories: o Creating Diskettes from the OS/2 CD-ROM o Ultimedia o Printer Considerations o Extended Services (ES) 1.0 Considerations o Hardware Considerations o Video Considerations o Restoring High-Resolution and Color After Installing OS/2 Performance Beta o DPMS-Supported Displays o Installation of Specific Video Adapters o S3 Video Accelerator Driver for OS/2 o Attention ValuePoint Users o S3 Installation o CD-ROM Support o Special Installation Procedures - Migrating CONFIG.SYS - RIPL Considerations - Installing with Adaptec 152X - Installing with SEMAINT - LAN CID Utility NOTE: This hardcopy of the README file contains the latest information. Use this document instead of the one provided on the OS/2 CD-ROM or the OS/2 Diskette Images. CREATING DISKETTES FROM THE OS/2 CD-ROM --------------------------------------- Use the LOADDSKF utility program to create the diskettes. (LOADDSKF.EXE is in the DISKS or DISKIMGS directory of the CD. LOADDSKF can be run from either the DOS or OS/2 operating system.) In the following section, you will see the lists of the diskettes for this version of OS/2 and the actual diskette names as they exist on the CD. For each diskette image file, use LOADDSKF to expand the image to its own diskette. (Note that you must use formatted diskettes for this procedure.) For example: cddrive:\DISKIMGS\LOADDSKF cddrive:\DISKIMGS\OS2\size\disk_name d: where: cddrive is the drive letter of the CD-ROM size is 35 for 3.5-inch 1.44MB diskettes or 525 for 5.25-inch 1.2MB diskettes disk_name is the diskette image file name (for example, DISK1.DSK, PMDD1.DSK.) d is the drive letter of your diskette drive (A: or B:) List of 3.5-Inch Diskette Images -------------------------------- | DISKIMGS\OS2\35\DISK0.DSK -- INSTALLATION Diskette (For Diskette or | CD-ROM Installation) | DISKIMGS\OS2\35\DISK1.DSK -- DISKETTE INSTALLATION Diskette 1 | DISKIMGS\OS2\35\DISK1_CD.DSK - CD-ROM INSTALLATION Diskette 1 | DISKIMGS\OS2\35\DISK2.DSK -- Diskette 2 of 12 DISKIMGS\OS2\35\DISK3.DSK -- Diskette 3 of 12 DISKIMGS\OS2\35\DISK4.DSK -- Diskette 4 of 12 DISKIMGS\OS2\35\DISK5.DSK -- Diskette 5 of 12 DISKIMGS\OS2\35\DISK6.DSK -- Diskette 6 of 12 DISKIMGS\OS2\35\DISK7.DSK -- Diskette 7 of 12 DISKIMGS\OS2\35\DISK8.DSK -- Diskette 8 of 12 DISKIMGS\OS2\35\DISK9.DSK -- Diskette 9 of 12 DISKIMGS\OS2\35\DISK10.DSK -- Diskette 10 of 12 DISKIMGS\OS2\35\DISK11.DSK -- Diskette 11 of 12 DISKIMGS\OS2\35\DISK12.DSK -- Diskette 12 of 12 DISKIMGS\OS2\35\PMDD1.DSK -- Printer Drivers Diskette 1 of 3 DISKIMGS\OS2\35\PMDD2.DSK -- Printer Drivers Diskette 2 of 3 DISKIMGS\OS2\35\PMDD3.DSK -- Printer Drivers Diskette 3 of 3 DISKIMGS\OS2\35\DISP1.DSK -- Display Drivers Diskette 1 of 3 DISKIMGS\OS2\35\DISP2.DSK -- Display Drivers Diskette 2 of 3 DISKIMGS\OS2\35\DISP3.DSK -- Display Drivers Diskette 3 of 3 List of 3.5-Inch Multimedia Diskette Images ------------------------------------------- DISKIMGS\MMPM2\35\DISK1.DSK - Diskette 1 of 2 DISKIMGS\MMPM2\35\DISK2.DSK - Diskette 2 of 2 ULTIMEDIA --------- o If you have an Ultimedia preinstalled system, or you installed Windows Version 3.1 from your Ultimedia System CD-ROM, do the following when prompted for the Windows Version 3.1 diskettes: 1. Insert the Ultimedia System CD-ROM into the drive. 2. Change to the directory containing Windows 3.1 on your CD-ROM. For example, type: D:\WINSETUP 3. Continue with the installation process. PRINTER CONSIDERATIONS ---------------------- o If you need to add a Windows printer driver after installing this version of OS/2, you must install the printer driver from the Windows Control Panel. Then, use the OS/2 Printer object to install the corresponding OS/2 printer driver. o The OS/2 printer drivers in this version of the OS/2 printer driver diskettes are stored in a packed format that is not compatible with OS/2 1.3 or 2.0. To install one of the new OS/2 printer drivers on a system with OS/2 1.3 or 2.0 installed, you must first unpack the driver on a system that has this version of OS/2 installed. You do not have to complete these steps to install a printer driver on a system that already has this version of OS/2 installed. NOTE: Do not install the new 32-bit PostScript driver (PSCRIPT.DR_) that came with this version of OS/2 on a system with OS/2 1.3 or 2.0 installed. It is not compatible with these versions of OS/2. Current compatibility information for this driver is available through your dealer, Marketing Representative, CompuServe, IBM National Support Center Bulletin Board System (NSC BBS), and IBMLink. To unpack a printer driver for use on a OS/2 1.3 or OS/2 2.0 system, complete the following steps on your system that has this version of OS/2 installed. 1. Open an OS/2 command prompt. 2. Type: MD X:\DRIVER Where X is a drive on your system. 3. Insert into drive A the OS/2 Performance Beta printer driver diskette that contains the printer driver you want to install. The printer driver names end in an underscore symbol ( _ ). Printer Driver: Diskette # Packed Name: ------------------------------------------ Epson 1 EPSON.DR_ HP DeskJet 1 HPDJPM.DR_ HP LaserJet III 1 LASERJET.DR_ IBM 4019 2 IBM4019.DR_ IBM 42XX 2 IBM42XX.DR_ IBM 5201-2 2 IBM52012.DR_ IBM 52XX 1 IBM52XX.DR_ IBM Null 1 IBMNULL.DR_ IBM PCL3 2 IBMPCL3.DR_ IBM PCL5 3 IBMPCL5.DR_ PaintJet 2 SMGXPJET.DR_ Plotter Driver 1 PLOTTERS.DR_ PostScript 1 PSCRIPT.DR_ Note: In order to get the proper printer driver directory structure on systems with OS/2 1.3, IBMPCL3, IBMPCL5, HPDeskJet and PaintJet must be installed using the Printer Install option in the Print Manager. Do not use the Control Panel to install these printer drivers. 4. Type: UNPACK A:\Packed name X:\DRIVER Where X is a drive on your system. For example if you want to install the Epson printer driver, type : UNPACK A:\EPSON.DR_ X:\DRIVER The printer driver files are now unpacked in the X:\DRIVER directory. 5. Copy the driver files to a diskette and install them onto your OS/2 1.3 or 2.0 system. EXTENDED SERVICES (ES) 1.0 CONSIDERATIONS ----------------------------------------- o If you installed OS/2 Performance Beta on a system that already had Extended Services installed, replace the existing ESSTART.CMD file with the ESSTART.BAK file that was installed by OS/2 Performance Beta. (The ESSTART.BAK file is located in the OS2\INSTALL subdirectory.) o If you are installing Extended Services over OS/2 Performance Beta for the first time (that is, there is no Extended Services on the workstation), or if you are installing Extended Services from diskettes, rename the existing ESSTART.CMD file from the Extended Services Diskette 1. Then, copy the file ESSTART.BAK from the \OS2\INSTALL directory to Extended Services Diskette 1. Finally, rename the ESSTART.BAK file ESSTART.CMD on ES Diskette 1, and begin the installation of Extended Services. HARDWARE CONSIDERATIONS ----------------------- o If you are using a ThinkPad 750C Series, after installing this version of the Performance Beta, you might find that your DOS full-screen session is corrupted. To fix this problem you must reinstall the video driver from the ThinkPad video features diskette. o After installation, you might have a video problem with the ThinkPad 750C. To fix this problem, do the following: 1. Start your system using the Installation disk 2. Run SETVGA X: where: X=your OS/2 boot drive 3. Restart your system, and then reinstall the ThinkPad 750c video drivers. o If you are using an IOMEGA PC Powered Pro 90, you must call the IOMEGA service number and request OAD Driver Version 2.3. o If you have an IBM PS/2 Model L40 SX and you want to install this version of OS/2, you must obtain the new IBM1FLPY.ADD device driver file from COMPUSERV or OS2BBS. (Internal IBM users can also obtain this file from the OS2BETA Tools Disk.) Copy IBM1FLPY.ADD to Diskette 1 of the OS/2 diskettes that came with this version of OS/2, and then proceed to install OS/2. VIDEO CONSIDERATIONS -------------------- The following information pertains to video support for this version of OS/2. Note: If you want to change your video mode you must use the Selective Install program located in the System Setup folder. Do not use DSPINSTL.EXE to change your video support. After using Selective Install for VGA, you must delete the SVGADATA.PMI file located in the OS2 directory before you shut down your system. RESTORING HIGH-RESOLUTION AND COLOR AFTER INSTALLING OS/2 PERFORMANCE BETA ____________________________________________ Install your video display driver using the installation procedures provided in the README file that comes with the video display driver. Refer to the notes following the table for exceptions and workarounds that apply to the display drivers listed below. NOTE: If you install display drivers other than those that came with this version of OS/2 or previous versions of OS/2, files such as BVHVGA.DLL, BVHSVGA.DLL, VGA.SYS, and VSVGA.SYS might be replaced. Replacing those files removes any updates applied to the files when you installed the OS/2 Performance Beta Version 2.99. ________________________________________________________________ IBM-TESTED DISPLAY DRIVERS ________________________________________________________________ Chip Use README Set/Board/System provided Driver Name README Date Tested on with driver ________________________________________________________________ ATI** Mach32 1-24-94 ATI Graphic Ultra Pro Y Cirrus** 542x 1-17-94 Diamond Speedstar Pro Y Compaq** QVision** 3-21-94 Compaq QVision Adapter Y IBM Image Adapter 2.00 6-4-93 Image Adapter/A Y 6-4-93 Image Adapter/I Y IBM Thinkpad 750 7-12-93 IBM ThinkPad 750 Y Matrox** MGA 2-22-94 Matrox MGA (ULT/2/M/H) Y (tested on MCA** hardware only) S3** 801/805/928 9-12-93 Actix GE32 Plus (801) (a) 5-23-93 NumberNine GXE (928) (a) STB** S3 (16-bit) 9-12-93 STB PowerGraph (805) Y S3** 911/924 10-4-93 Orchid FahrenHeit 1280 Y Tseng** ET4000 3-23-94 Hercules Dynamite Y Version 1.02 VLPRO V.800 Trident** 8900C 6-10-93 Trident 8900C Y(b) (16-bit) Weitek** P9000 2-17-94 Diamond Viper Y(c) NOTES: a. You can reinstall the S3 16-bit display driver for the 801, 805, and 928 chip sets. There are several versions of OS/2 drivers (available on electronic services and from other vendors) supporting the 90C801, 90C805, and 90C928 chip sets from the S3 Corporation. IBM provides service for the S3 32-bit display driver and recommends that you install the new version of this driver included in this version of OS/2. This 32-bit display driver better utilizes the S3 chip sets. Note: IBM recommends that you DO NOT reinstall the S3-supplied 16-bit driver, the STB-supplied S3 driver, or the IBM-supplied S3-16M driver. For information about installing S3 video display drivers see the "S3 Installation" section in this file. b. You can reinstall the Trident-supplied 16-bit display driver, but the OS/2 Performance Beta Version 2.99 SVGA 32-bit display driver better utilizes the Trident 8900C cards. IBM provides service for the OS/2 Performance Beta SVGA 32-bit display driver and recommends that you install the new version of this driver. Note: IBM recommends that you DO NOT reinstall the Trident driver supplied on numerous bulletin boards, because it removes fixes from the Base Video Handler and Virtual Device Driver for the OS/2 SVGA driver. To install the OS/2 Performance Beta SVGA 32-bit display driver, follow these steps: 1. Open the OS/2 System folder. 2. Open System Setup folder. 3. Open Selective Install. 4. When you see the Install screen, select Primary Display in the Display section. 5. Select Install. 6. When you see the Primary Display Adapter Type window, select Trident 8900C. 7. Follow the instructions for the Monitor Configuration/Selection Utility. For more information on when to use this utility to set the refresh rate, see the "OS/2 2.1 Installation Guide", Appendix A. c. After you install the OS/2 Performance Beta, install the Weitek display driver by following the instructions provided in the Weitek README file. IBM testing indicates that the Weitek display driver runs successfully on several computers but encounters "snow" with some configurations. DPMS-SUPPORTED DISPLAYS The XGA DMQS (\xga$dmqs\*.dqs) files in this version of the operating system do not have DPMS (Display Power Management Signaling) enabled for the DPMS supported displays. You must use the DPMS OVERRIDE parameter provided with the Power Management Utility that is located in System Setup. INSTALLATION OF SPECIFIC VIDEO ADAPTERS o ATI Graphics Pro Display Adapter In the "OS/2 2.1 Installation Guide", instructions are given for configuring the ATI** Graphics Ultra Pro. These instructions state that the display type for 640 x 480 must be configured to IBM DEFAULT. Note that this setting might be referred to as 60Hz rather than IBM DEFAULT. o Radius XGA Display Adapter The Radius XGA display adapter is supported on PS/2* Models 35 and 40 and PS/ValuePoint* 486 systems. If you are using this display adapter on a PS/ValuePoint system, the VPXGA.EXE utility is required. For a copy of this utility program, check your Radius installation diskette or contact Radius. o Sigma Legend Display Adapter The OS/2 Performance Beta cannot restore the state of a Sigma Legend** display adapter after you switch sessions or video modes. Also, the Sigma Legend video adapter might cause the system to stop when using 1024 x 768 x 256 color mode. Use only 640 x 480 or 800 x 600 mode with this adapter. S3 VIDEO ACCELERATOR DRIVER FOR OS/2 ------------------------------------ The S3 video accelerator driver supports the 86C801/86C805 and 86C928 chip sets from the S3** Corporation. These chip sets are found on many leading video display adapters, including Actix**, Artist Graphics**, Diamond Stealth**, Focus**, Metheus**, MiroMAGIC, Nth Graphics**, Number Nine**, Orchid**, PCG**, Vermont**, Video 7**, Volante** and on the system boards of leading hardware systems, such as those from the IBM* Corporation and the Dell** Computer Corporation. SUPPORTED FEATURES ------------------ This S3 video accelerator driver provides support for accelerated video graphics and advanced color resolutions when used with the minimum required video memory. It conforms to the current OS/2 32-bit flat memory model and is designed to function as a 32-bit Presentation Manager* display driver under the current OS/2 32-bit graphics engine. This video accelerator driver supports these resolutions and colors depths: Number of Video Memory Resolutions Colors Required 640x480 256 1MB 800x600 256 1MB 1024x768 256 1MB 1280x1024 256 2MB 640x480 65,536 1MB 800x600 65,536 1MB 1024x768 65,536 2MB 640x480 16,777,216 1MB This S3 video accelerator driver supports the following number of columns and rows in an OS/2 full-screen session: Columns Rows 132 25 132 43 COMPATIBILITY ------------- IBM has tested many display adapters containing the S3 chips sets. Those that have tested successfully are listed in this README file. However, certain display adapters in combination with certain chip sets might not be supported. IBM is continuing to test; therefore, support for additional combinations is expected to be added over time. NOTE: If you are using the 256 color mode, and your desktop appears to be darker than other color modes, you must edit the SVGADATA.PMI file located in the \OS2 directory. Change the following statement from: HI-COLOR DAC by .... to: HI-COLOR DAC by unknown To make the changes effective, shut down OS/2 and then restart your system. Supported S3 Adapters/Systems Chip sets ------------------------------------------------------ Actix GraphicsENGINE 32 801 Actix GraphicsENGINE 32 LB 805 Actix GraphicsENGINE ULTRA 928 Artist Graphics** Winsprint 928 Diamond Stealth 24** 801 Diamond Stealth 24 LB** 805 Diamond Stealth Pro** 928 Diamond Stealth Pro LB** 928 Focus 2 The Max Truespeed 801 Metheus (Brooktree DAC) 928 Metheus (AT&T** DAC) 928 MiroMAGIC S4 LB 928 National Design Volante** Warp 10 LB 805 Nth Graphics** S3 Advantage 801 Nth Graphics S3 Advantage LB 805 Number Nine** #9** GXE (Brooktree DAC) 928 Number Nine #9 GXE (AT&T DAC) 928 Orchid Fahrenheit** 1280 Plus 801 Orchid Fahrenheit LB 805 PCG** Photon Torpedo 801 PCG Photon Torpedo LB 805 Vermont** 801 ISA 801 Video 7 Win.Pro** 801 IBM PS/ValuePoint* 805 Dell 805 | ATTENTION IBM VALUEPOINT USERS: | ------------------------------- | | You might encounter a blank screen while switching from one window to | another when using any one of the following: | | PS/ValuePoint Display Models: 6314 6317 6319 | PS/ValuePoint Computer Models: 6382 6384 6387 | | To correct or avoid this problem, you MUST do the following: | | 1. Make sure that the flash EEPROM level of your system is 61 or later. | | To check the EEPROM level: | | a. Begin the Configuration Utility program by turning the system | off and then on again. | b. During the memory count, press F1. (The memory count appears in | the upper left corner of the screen as numbers followed by KB.) | c. When the Configuration Utility screen appears, look for the | Flash EEPROM Revision Level. | d. The fifth and sixth characters in the Flash EEPROM Revision | Level represent the actual revision level. | e. If the revision level is less than 61, you must install the | ValuePoint Flash BIOS update. | | To get the required ValuePoint Flash BIOS update do the following: | | f. Access the IBM PC Company Bulletin Board System | (1-919-517-0001), then download the VP2FL61A.DSK file, which is | the Flash BIOS Update Level 61. | | If you do not have access to a modem, you can call the IBM Help | Center (1-800-772-2227) and request this update on diskette. | | 2. You must install both the flash update (if the revision level is | less than 61) and the S3 Video Driver Update Package. S3 INSTALLATION --------------- Use the following instructions to install S3 video support. S3 INSTALLATION FROM DISKETTE ----------------------------- To install the S3 32-bit display driver from diskette, follow these steps: 1. Open the "OS/2 System" folder. 2. Open "System Setup". 3. Open "Selective Install". 4. When you see the Installation screen, select "Primary Display". 5. Select "Install". 6. When you see the Primary Display Adapter Type window, select "32 bit S3 Display Drivers". 7. Follow the instructions for the Monitor Configuration/Selection Utility. For more information on when to use this utility to set the refresh rate, see the OS/2 2.1 Installation Guide, Appendix A. S3 INSTALLATION FROM CD-ROM ---------------------------- To install the S3 32-bit display driver from CD-ROM, follow these steps: 1. Open the "OS/2 System" folder. 2. Open "System Setup". 3. Open "Selective Install". 4. When you see the Installation screen, select "Primary Display". 5. Select "Install". 6. Choose the defaults for monitor setting. 7. When the "Directory Screen" is displayed, select "Change". 8. When the directory list is displayed, select the "OS2SE21" directory. 9. Select " Set". 10. Press Esc to return to the "Directory Screen". 11. Select "Install". CD-ROM SUPPORT _________________ The majority of SCSI-based CD-ROM drives and adapters are supported by this version of OS/2. ("SCSI-based" refers to the small computer system interface (SCSI), a standard input/output interface used by personal computers.) A complete list of the CD-ROM drives and SCSI adapters tested on the OS/2 Performance Beta can be found in the "Hardware Support" chapter of the "OS/2 2.1 Using the Operating System" manual. Make sure you follow your hardware manufacturer recommendation for CD-ROM setup. Additional support includes: New Non-SCSI Drives Supported in OS/2 Performance Beta Version 2.99 ------------------------------------------------------------------- Vendor CD-ROM Drive Model --------------------------------- Creative Labs OmniCD IBM ISA CD-ROM Mitsumi CRMC-LU005 Mitsumi CRMC-FX001 Mitsumi CRMC-FX001D Panasonic CR-521 Panasonic CR-522 Panasonic CR-523 Panasonic CR-562 Panasonic CR-563 Philips LMS CM205 Philips LMS CM205MS Philips LMS CM206 Philips LMS CM225 Philips LMS CM225MS Philips LMS CM226 Sony CDU-31A Sony CDU-33A Sony CDU-531 Sony CDU-535 Sony CDU-6201 Sony CDU-6205 Sony CDU-7201 Sony CDU-7205 Sony CDU-7305 New SCSI Drives Certified for OS/2 Performance Beta Version 2.99 ---------------------------------------------------------------- Chinon 431 Chinon 435 Chinon 535 IBM Enhanced CD-ROM II NEC MultiSpin 3Xe NEC MultiSpin 3Xi NEC MultiSpin 3Xp Philips LMS CM215 Texel DM-3028 Texel DM-5028 SUPPORTED AUDIO CARD/CD-ROM PORT COMBINATIONS --------------------------------------------- The following table lists the Media Vision and Creative Labs audio cards with CD-ROM ports that are supported in this version of OS/2. Audio cards with CD-ROM ports from other manufacturers should also work if they provide a compatible CD-ROM interface chip. Media Vision ------------ ProAudio Spectrum 16 with Trantor SCSI port (TMV1SCSI.ADD) * Trantor SCSI support is available from Trantor BBS-510-656-5159. ProAudio Spectrum 16 with Sony 31A/Sony33A CD-ROM port (Sony31A.ADD) ProAudio Spectrum 16 with Philips LMS CM205 CD-ROM port (LMS205.ADD) ProAudio Spectrum 16 with Philips LMS CM206 CD-ROM port (LMS206.ADD) Jazz 16 with Future Domain FD9C50 SCSI port (FD8XX.ADD) Jazz 16 with Panasonic 563 CD-ROM port (SBCD2.ADD) Jazz 16 with Philips CM206 CD-ROM port (LMS206.ADD) Creative Labs ------------- Sound Blaster Pro with Panasonic CD-ROM port (SBCD2.ADD) Sound Blaster 16 with Panasonic CD-ROM port (SBCD2.ADD) Sound Blaster 16 SCSI-2 with Adaptec SCSI port (AHA152X.ADD) Sound Blaster 16 MultiCD with Mitsumi, (MITFX001.ADD, Sony and, SONY31A.ADD, Panasonic CD-ROM ports SBCD2.ADD) Mitsumi Device Driver Parameters -------------------------------- The parameters for the following CD-ROM adapter device drivers are described in this section: MITFX001.ADD This device driver supports the following CD-ROM drives: Mitsumi CRMC-FX001D Mitsumi CRMC-FX001 Mitsumi CRMC-LU005S Mitsumi CRMC-LU002S BSR 6800 Tandy CDR-1000 This section lists the parameters that are supported for the Mitsumi CD-ROM device driver. The parameters can be changed by modifying the BASEDEV=MITFX001.ADD line in CONFIG.SYS. It is recommended to change the transfer mode from it default, software polling transfer, to software interrupt transfer. This will help lower the CPU utilization of CD-ROM applications, enabling better performance for other tasks while the CD-ROM drive is being accessed. See the /I parameter below. For the MITFX001.ADD device driver, the syntax for the line in CONFIG.SYS is as follows: BASEDEV=MITFX001.ADD ╤ì/P:nnnΓêÖ ╤ìI:nnΓêÖ ╤ì/VΓêÖ ╤ì/P:nnnΓêÖ Specifies the base I/O port address of the interface card. This must be the same number as specified by the DIP switch on the interface card. ╤ì/I:nnΓêÖ Specifies the interrupt request (IRQ) channel number. This must match the value specified on the jumper setting on the interface card. If this parameter is not specified, the device driver will use software polling transfer. ╤ì/VΓêÖ The device driver will display the device driver revision level and CD-ROM product information at boot time. Mitsumi CD-ROM Device Driver Parameter Examples ----------------------------------------------- o Mitsumi CD-ROM drive attached to Mitsumi host adapter: If the Mitsumi host adapter is set to a base I/O port address of 320, the line in CONFIG.SYS should be: BASEDEV=MITFX001.ADD /P:320 o Mitsumi CD-ROM drive attached to Creative Labs Sound Blaster 16 MultiCD If the Mitsumi CD-ROM port on the Sound Blaster 16 MultiCD is set to I/O port address of 340, the line in CONFIG.SYS should be: BASEDEV=MITFX001.ADD /P:340 o To enable interrupt transfer mode, which improves performance, the /I parameter must be specified. For example to enable interrupt transfer mode for IRQ channel 10 at I/O port address of 320h, the line in CONFIG.SYS should appear as follows: BASEDEV=MITFX001.ADD /P:320 /I:10 Known Problems -------------- The Diamond Viper video card and the Mitsumi host adapter conflict at port address 300h, which is the default port address of the Mitsumi card. The result is a corrupted display screen. The user should change the port address on the Mitsumi card from 300h to another address, such as 310h, and add the /P parm to the BASEDEV=MITFX001.ADD statement in CONFIG.SYS. Sony 31A Device Driver Parameters --------------------------------- The parameters for the following CD-ROM adapter device driver are described in this section: SONY31A.ADD This device driver supports the following CD-ROM drives: Sony CDU-31A,CDU-7305 Sony CDU-33A,CDU-7405 This section lists the parameters that are supported for the Sony CD-ROM device driver. The parameters can be changed by modifying the BASEDEV=SONY31A.ADD line in the CONFIG.SYS. It is recommended to change the transfer mode from its default, software polling transfer, to software interrupt transfer. This change will help lower the CPU utilization of CD-ROM applications, enabling better performance for other tasks while the CD-ROM drive is being accessed. See the /I parameter below. For the SONY31A.ADD device driver, the syntax for the line in CONFIG.SYS is as follows: BASEDEV=SONY31A.ADD ╤ì/A:dΓêÖ ╤ì/AT:ddΓêÖ ╤ì/P:nnnΓêÖ ╤ìI:nnΓêÖ ╤ì/VΓêÖ ╤ì/A:dΓêÖ Identifies a specific adapter, d. The adapter is specified as a single digit value which is zero based. (for example, the first adapter is specified as /A:0). ╤ì/AT:ddΓêÖ Sets the adapter type connected to the CD-ROM drive. Supported values are: 00 = Sony CDB-334 (default) 05 = - Echo Speech (with ESC614 chip) - Orchid SoundWave 32 - Orchid GameWave 32 - Cardinal DSP16 08 = Media Vision ProAudio Spectrum-16 ╤ì/P:nnnnΓêÖ Specifies the base I/O port address of the interface card. The port address is specified as a four digit hex value. Leading zeros should be specified. The value must be the same number as the port address selected by the jumper on the host interface card. If this parameter is not specified, the default port address for the host adapter is used. For the Sony CDB-334 host interface card, the default is 0340. For the Media Vision ProAudio Spectrum-16 card the default is 1F88. See the section below titled "Sony CDB-334 Host Adapter Jumper Settings". ╤ì/I:nnΓêÖ Specifies the interrupt request (IRQ) channel number. This must match the value specified on the jumper setting on the interface card. If this parameter is not specified, the device driver will use software polling transfer. See the section below titled "Sony CDB-334 Host Adapter Jumper Settings". This parameter switch is not supported if the CD-ROM drive is attached to the Media Vision ProAudio spectrum. Note: Some Sony CDB-334 host adapter cards did not ship with the plastic jumper switch to select the IRQ channel on the IRQ jumper block. You must obtain and install the plastic jumper switch to enable the IRQ channel. ╤ì/VΓêÖ The device driver will display the device driver revision level and CD-ROM product information at startup time. Sony CDU-31A Device Driver Parameter Examples --------------------------------------------- o Sony CDU-31A or CDU-33A CD-ROM drive attached to Sony CDB-334 host adapter: The Sony CDB-334 host adapter supports base I/O port addresses of 320h, 330h, 340h or 360h. If the CDB-334 host adapter is set to any port address other than the default of 340h, the CONFIG.SYS statement needs to be modified. For example, if the Sony CDB-334 host adapter is set to a base I/O port address of 360, the line in CONFIG.SYS should be: BASEDEV=SONY31A.ADD /A:0 /P:0360 (Note: The Sony Desktop Library model number CDU-31A-LL/N includes the Sony CDB-334 adapter) o Sony CDU-31A or CDU-33A CD-ROM drive attached to Sony CDB-334 host adapter. If the Sony CDU-31A is attached to the Sony CDB-334 host adapter at base I/O port address of 360h, and the driver is operating in interrupt mode at IRQ channel 5, the line in your CONFIG.SYS should be: BASEDEV=SONY31A.ADD /A:0 /P:0360 /I:5 o Sony CDU-31A or CDU-33A CD-ROM drive attached to Media Vision ProAudio Spectrum-16 (PAS-16) host adapter: The line in CONFIG.SYS should appear as follows: BASEDEV=SONY31A.ADD /A:0 /AT:08 (Note: The default port address for the CDU-31A when attached to the PAS-16 card is 1F88. The Sony Desktop Library model numbers CDU-31A-LL/L and CDU-7305 include the PAS-16 adapter). o Sony CDU-31A or CDU-33A CD-ROM drive attached to the Creative Labs Sound Blaster Pro, Sound Blaster 16, or Sound Blaster 16 MultiCD host adapter: The port address specified on the BASEDEV statement in CONFIG.SYS should be 10h above the base I/O port address specified on the adapter card. For example, if the Sound Blaster card is set for a base I/O port address of 220h, the line in CONFIG.SYS should be: BASEDEV=SONY31A.ADD /A:0 /P:0230 o Sony CDU-31A or CDU-33A CD-ROM drive attached to the Echo Speech, Orchid SoundWave 32, Orchid GameWave 32, or Cardinal DSP16 host adapter: The line in CONFIG.SYS should appear as follows: BASEDEV=SONY31A.ADD /A:0 /AT:05 Sony 535 Device Driver Parameters --------------------------------- The parameters for the following CD-ROM adapter device drivers are described in this section: SONY535.ADD This device driver supports the following CD-ROM drives: Sony 531 series (CDU-531,6201,6205) Sony 535 series (CDU-535,6205,7205) This section lists the parameters which are supported for the Sony CD-ROM device driver. The parameters can be changed by modifying the BASEDEV=SONY535.ADD line in CONFIG.SYS. It is recommended to change the transfer mode from it default, software polling transfer, to software interrupt transfer. This will help lower the CPU utilization of CD-ROM applications, enabling better performance for other tasks while the CD-ROM drive is being accessed. See the /I parameter below. For the SONY535.ADD device driver, the syntax for the line in CONFIG.SYS is as follows: BASEDEV=SONY535.ADD ╤ì/P:nnnΓêÖ ╤ìI:nnΓêÖ ╤ì/U:d,d...ΓêÖ ╤ì/VΓêÖ ╤ì/P:nnnΓêÖ Specifies the base I/O port address of the interface card. The value must be the same number as the port address selected by the jumper on the host interface card. ╤ì/I:nnΓêÖ Specifies the interrupt request (IRQ) channel number. This must match the value specified on the jumper setting on the interface card. If this parameter is not specified, the device driver will use software polling transfer. Note: Some Sony host adapter cards did not ship with the plastic jumper switch to select the IRQ channel on the IRQ jumper block. You must obtain and install the plastic jumper switch to enable the IRQ channel. ╤ì/U:d,d...ΓêÖ Specifies the drive unit number which the Sony CD-ROM drive is set to. The value of d must be set to 0,1,2 or 3. If more than one Sony CD-ROM drive is attached to the adapter, this parameter must be specified. If only one CD-ROM drive is attached to the adapter, and this parameter is not specified, then the default unit id used by the driver is 0. ╤ì/VΓêÖ The device driver will display the device driver revision level and CD-ROM product information at boot time. Sony CDU-535 Device Driver Parameter Examples --------------------------------------------- o Sony CD-ROM drive attached to Sony CDB-240 series host adapter: For example, if the Sony host adapter is set to a base I/O port address of 360, the line in CONFIG.SYS should be: BASEDEV=SONY535.ADD /P:360 o Sony CD-ROM drive attached to Sony CDB-240 series host adapter. If the Sony CD-ROM drive is attached to the Sony host adapter at base I/O port address of 360h, and the driver is operating in interrupt mode at IRQ channel 5, the line in your CONFIG.SYS should be: BASEDEV=SONY535.ADD /P:360 /I:5 o Multiple Sony CD-ROM drives daisy chained to Sony CDB-240 series host adapter For example, if two Sony CD-ROM drives are daisy chained from the Sony host adapter with the first drive set to drive unit 0 and the second set to drive unit 1, the line in CONFIG.SYS should appear as follows: BASEDEV=SONY535.ADD /P:340 /U:0,1 SBCD2.ADD Device Driver Parameters ---------------------------------- The parameters for the following CD-ROM adapter device drivers are described in this section: SBCD2.ADD This device driver supports the following CD-ROM drives: Creative Labs OmniCD IBM ISA CD-ROM Panasonic 521,522,523,562,563 This section lists the parameters which are supported for the SBCD2.ADD device driver. The parameters can be changed by modifying the BASEDEV=SBCD2.ADD line in CONFIG.SYS. For the SBCD2.ADD device driver, the syntax for the line in CONFIG.SYS is as follows: BASEDEV=SBCD2.ADD ╤ì/P:nnnΓêÖ ╤ìT:nΓêÖ ╤ì/NSΓêÖ ╤ì/VΓêÖ ╤ì/P:nnnΓêÖ Specifies the base I/O port address of the interface card. The value must be the same number as the port address selected by the jumper on the host interface card. ╤ì/T:nnΓêÖ Sets the adapter type connected to the CD-ROM drive. Supported value is: 2 = Creative Labs CD-ROM interface card (not Sound Blaster) ╤ì/NSΓêÖ Disable drive select scan. Driver will not scan for more than one CD-ROM drive. SBCD2.ADD Parameter Examples ---------------------------- o Panasonic, Creative Labs OmniCD or IBM ISA CD-ROM drive attached to standard Panasonic or IBM ISA CD-ROM host adapter: The standard Panasonic or IBM ISA host adapter supports base I/O port addresses of 300h, 310h, 320h or 330h. For example, if the adapter is set to a base I/O port address of 300, the line in CONFIG.SYS should be: BASEDEV=SBCD2.ADD /P:300 o Panasonic, Creative Labs OmniCD or IBM ISA CD-ROM drive attached to Creative Labs Sound Blaster Pro, Sound Blaster 16, or Sound Blaster 16 MultiCD. For example, if the Sound Blaster card is set for a base I/O address of 220h, the line in CONFIG.SYS should be: BASEDEV=SBCD2.ADD /P:220 o Creative Labs OmniCD attached to standard Creative Labs CD-ROM host adapter (not Sound Blaster) : The standard Creative Labs host adapter supports base I/O port addresses of 250h or 260h. For example, if the adapter is set to a base I/O port address of 250, the line in CONFIG.SYS should be: BASEDEV=SBCD2.ADD /P:250 /T:2 o Panasonic, Creative Labs OmniCD or IBM ISA CD-ROM drive attached to Media Vision Jazz 16 sound card. For example, if the Media Vision card is set for a base I/O address of 300h, the line in CONFIG.SYS should be: BASEDEV=SBCD2.ADD /P:300 /NS o Panasonic, Creative Labs OmniCD or IBM ISA CD-ROM drive attached to Reveal audio card. For example, if the Reveal audio card is set for a base I/O address of 630h, the line in CONFIG.SYS should be: BASEDEV=SBCD2.ADD /P:630 Philips LMS 205 Device Driver Parameters ---------------------------------------- The parameters for the following CD-ROM adapter device drivers are described in this section: LMS205.ADD This device driver supports the following CD-ROM drives: Philips LMS CM205,CM225 NOTE: If you have installed this version of OS/2 and find that your CD-ROM drive does not function, you might have an LMS 205MS device driver. | To resolve this problem, you must copy the LMS206.ADD file from | Diskette 1 to the \OS2 directory and add the following line to your CONFIG.SYS file: BASEDEV=LMS206.ADD This section lists the parameters that are supported for the Philips LMS 205 CD-ROM device driver. The parameters can be changed by modifying the BASEDEV=LMS205.ADD line in the CONFIG.SYS. For the LMS205.ADD device driver, the syntax for the line in CONFIG.SYS is as follows: BASEDEV=LMS205.ADD ╤ì/P:nnnΓêÖ ╤ì/u:XΓêÖ ╤ì/m:YΓêÖ ╤ì/VΓêÖ ╤ì/P:nnnΓêÖ Specifies the base I/O port address of the interface card. The value must be the same number as the port address selected by the jumper on the host interface card. ╤ì/u:XΓêÖ Identifies a specific unit, X. Valid values for X are 0, 1, 2, 3. The default is zero. LMS205 locates all CM250 and CM260 host adapters and assigns unit numbers based on the order in which each was found. This parameter tells LMS205 which BASEDEV=LMS205.ADD line it is currently processing. ╤ì/m:YΓêÖ Indicates the number of 2500 byte CD frame buffers that should be allocated by the LMS205.ADD driver. Valid values for Y are 8,..., 26. The default is 16. Any value below the minimum (8) will be assigned the minimum (8). ╤ì/VΓêÖ The device driver will display the device driver revision level and CD-ROM product information at startup time. For example, IBM OS/2 LMS205.ADD 1.00 02-NOV-93 Philips LMS Unit 0: CM205 CDROM drive, FR4, CM260 HA Port: 0340 IRQ: 05 Philips LMS 206 Device Driver Parameters ---------------------------------------- The parameters for the following CD-ROM adapter device drivers are described in this section: LMS206.ADD This device driver supports the following CD-ROM drives: Philips LMS CM205MS,CM225MS (multisession photo CD version of CM205) Philips LMS CM206,CM226 NOTE: If you have installed this version of OS/2 and find that any of the above Philips CD-ROM drives do not function, you must copy | the LMS206.ADD file from Diskette 1 to the \OS2 directory and add the following line to your CONFIG.SYS file: BASEDEV=LMS206.ADD This section lists the parameters that are supported for the Philips LMS CD-ROM device driver. The parameters can be changed by modifying the BASEDEV=LMS206.ADD line in the CONFIG.SYS. For the LMS206.ADD device driver, the syntax for the line in CONFIG.SYS is as follows: BASEDEV=LMS206.ADD ╤ì/P:nnnΓêÖ ╤ì/u:XΓêÖ ╤ì/m:YΓêÖ ╤ì/VΓêÖ ╤ì/P:nnnΓêÖ Specifies the base I/O port address of the interface card. The value must be the same number as the port address selected by the jumper on the host interface card. ╤ì/u:XΓêÖ Identifies a specific unit, X. Valid values for X are 0, 1, 2, 3. The default is zero. LMS206 locates all CM250 and CM260 host adapters and assigns unit numbers based on the order in which each was found. This parameter tells LMS206 which BASEDEV=LMS206.ADD line it is currently processing. ╤ì/m:YΓêÖ Indicates the number of 2500 byte CD frame buffers that should be allocated by the LMS206.ADD driver. Valid values for Y are 8,..., 26. The default is 16. Any value below the minimum (8) will be assigned the minimum (8). ╤ì/VΓêÖ The device driver will display the device driver revision level and CD-ROM product information at startup time. For example, IBM OS/2 LMS206.ADD 1.00 02-NOV-93 Philips LMS Unit 0: CM206 CDROM drive, FR4, CM260 HA Port: 0340 IRQ: 05 SPECIAL INSTALLATION PROCEDURES -------------------------------- Migrating CONFIG.SYS -------------------- If you migrate CONFIG.SYS statements that contain multiple CALL= statements, check the CONFIG.SYS file to be sure that the CALL= statements are not concatenated. If the statements are concatenated, edit the CONFIG.SYS file so that the CALL= statements are on separate lines. RIPL Considerations ------------------- RIPL users must contact their service representative to obtain the RIPL function supported by this version of OS/2. Installing with Adaptec 152X ---------------------------- If you have an ADAPTEC 152X adapter with a Toshiba 3401 or Texel CD-ROM device, you must modify the CONFIG.SYS file located on Diskette 1 of the OS/2 Installation diskettes before you can install this version of OS/2 from CD-ROM. 1. Edit the CONFIG.SYS file located on Diskette 1. 2. Change the following line to: BASEDEV=AHA152X.ADD /!SN 3. Save the file and proceed with the OS/2 installation. When the installation is complete, check the OS/2 CONFIG.SYS file to ensure there is only one BASEDEV statement for AHA152X.ADD. If you have two BASEDEV statements for AHA152X you must remove the statement that does not contain the /!SN parameter. Installing with SEMAINT ----------------------- If you use SEMAINT to create maintenance systems to apply the Performance Beta, statements are added to the CONFIG.SYS file created by SEMAINT. These statements enable swapping to the target drive and directory of the maintenance system. This path is determined by the /T: parameter that SEMAINT uses when it is started. Swapping is enabled only on systems with 10 megabytes of RAM or less. The initial swap file size will be set to 1024KB or 1 megabyte and can grow depending on the amount of virtual memory needed during installation of the Performance Beta. This requires you to have at least 5 megabytes of free disk space prior to creating the maintenance system created by SEMAINT. If you have a maintenance system installed with this OS/2 version of SEMAINT, you must re-install using SEMAINT from this version of the Performance Beta. | LAN CID UTILITY | --------------- | If you want to use the LAN CID Utility, you must type: | | ;\OS2\DLL | | at the end of the LIBPATH statement in your CONFIG.SYS file located on | the SEDISK2. IBM DISCLAIMS ALL WARRANTIES, WHETHER EXPRESSED OR IMPLIED, INCLUDING WITHOUT LIMITATION, WARRANTIES OF FITNESS AND MERCHANTABILITY WITH RESPECT TO THE INFORMATION IN THIS DOCUMENT. BY FURNISHING THIS DOCUMENT, IBM GRANTS NO LICENSES TO ANY RELATED PATENTS OR COPYRIGHTS. (C) Copyright IBM Corporation 1993, 1994. All rights reserved. ΓòÉΓòÉΓòÉ 4.7. OS/2 2.11 README file ΓòÉΓòÉΓòÉ OS/2 2.11 README file Welcome to OS/2* 2.11. This README provides helpful hints found during testing as well as updated information that was not available at the time the publications were printed. It is divided into the following categories: o General System Considerations o WIN-OS/2 Application Compatibility o DOS Application Compatibility o OS/2 Application Compatibility o DOS and WIN-OS/2 Multimedia Application Compatibility o Network o Display Adapters o Audio Adapters o Printers o Scanners o Advanced Power Management Support for Portable Computers o Mahjongg Game o Trademarks A separate README file for MMPM/2 is contained in the MMPM/2 program. ΓòÉΓòÉΓòÉ 4.7.1. GENERAL SYSTEM CONSIDERATIONS ΓòÉΓòÉΓòÉ GENERAL SYSTEM CONSIDERATIONS o Your system .INI files might be read-only. As a result, the system will not update the .INI files. When this happens, the position of the icons will not be saved. To resolve this problem go to the directory where your system .INI files are located C:\OS2 (default). Then, type the following: ATTRIB -r *.ini Shut down your system and when it starts, your system .INI files are updated. o OS/2 2.1 uses a system proportional font that is designed to meet the International Standards Organization (ISO) 9241 standard and the German DIN 66234 standard on suitable hardware. ISO compliant fonts cause some text strings to be clipped. If you do not want to use ISO compliant fonts, modify the OS2.INI file to install fonts that are not ISO compliant. Font changes made in the OS2.INI file are global across all applications. If you have REXX installed, you can type the following information into a CMD file and use it to change the font. /* */ call RxFuncAdd "SysIni", "RexxUtil", "SysIni" AppName = "PM_SystemFonts" KeyName = "DefaultFont" FontName = "10.System Proportional Non-ISO" call SysIni "USER", AppName, KeyName, FontName||"0"x exit After the file has been run, shut down and restart the system. o If you experience video corruption: - Display the pop-up menu for the desktop; then select Refresh to redraw the desktop. - If the screen goes blank, press Alt+Esc to switch between the applications to force repainting of the screen. o DOS images on the hard disk (VMBs) need to use the FSFILTER and FSACCESS drivers provided with this version of OS/2. FSFILTER and FSACCESS drivers are located in the \OS2\MDOS directory. o The Check disk option for a CD-ROM object will not display information about the CD-ROM. To obtain information about the CD-ROM: 1. Point to the CD-ROM drive object. 2. Click mouse button 2. 3. Select the arrow to the right of Open. 4. Select Details view. o During a system shutdown, there might be times when the "Shutdown is completed" message is not displayed. If this happens, wait 30 seconds until all disk activity is completed, and then restart the system. o If you are installing OS/2 2.11 over a system that has OS/2 2.0 installed, the desktop directory name will be "OS!2_2.0_D" and the title of the desktop will be "OS/2 2.0 Desktop". On a system that has OS/2 2.11 installed, the desktop directory name will be "Desktop". o If you have a preinstalled system, and you change your country or keyboard configuration using the Configure Preinstalled System program, located in the Configuration Tools folder, the changes occur only for OS/2 sessions. To configure the country and keyboard for WIN-OS/2* sessions, use the International icon from the WIN-OS/2 Control Panel. o After installing OS/2 2.11 on your system, use the Migrate Applications program instead of the Selective Install program to migrate your programs. The Migrate Applications program is located in the System Setup folder. o If you are running CHKDSK from the command line without the /F parameter on an HPFS partition which also contains your SWAPPER.DAT file, you may receive a SYS0552 error message. This message can be ignored. If you are using CHKDSK from the popup menu of a drive icon, you may receive a WARNING message stating "The disk is in use or locked by another process." If this occurs, CHKDSK will not let you display the graphical representation of disk usage. o Added support for Boot Manager exists on a disk other than Disk 1. The ability to delete and re-install the Boot Manager requires that you exit FDISK after you delete the Boot Manager and re-start FDISK to install Boot Manager again. This is true even if you are going to place it in the same partition. This means you would have to re-enter the partition names. o The kernel debug diskettes shipped with the Developer's Toolkit for OS/2 version 2.1 will not work with OS/2 version 2.11. (The kernel debug files for OS/2 version 2.11 are located on the OS/2 version 2.11 CD-ROM. Please reference the Kernel Debugger Installation README file in the OS2TK21\DEBUG sub-directory on the CD for more information.) If you do not have access to this CD-ROM, you can retrieve the kernel debug files for OS/2 version 2.11 electronically through the IBM Personal Computer Company Bulletin Board System (PCC BBS) sponsored by the IBM Personal Systems Help Center in Raleigh, North Carolina. The PCC BBS is available 24 hours a day on a toll-call basis with no access charge to the bulletin board. To access the PCC BBS call 1-919-517-0001. Requirements for the asynchronous electronic connection to the PCC BBS are: * A modem that support 1200 to 14400 baud * Communication software that supports 8 bit file transfers * A switched telephone line. The modem should be set to: - eight data bits - one stop bit - no parity - standard transmission speed from 1200 to 14400 baud. Refer to the bulletin titled "OS/2 2.11 Kernel Debug Files" in file area 11 (OS/2 Programming) on the PCC BBS for downloading instructions once you are connected. The kernel debug files will also be available on the Developer Connection for OS/2 Volume 3 CD-ROM. ΓòÉΓòÉΓòÉ 4.7.2. WIN-OS/2 APPLICATION COMPATIBILITY ΓòÉΓòÉΓòÉ WIN-OS/2 APPLICATION COMPATIBILITY o The original WIN-OS/2 color scheme was added to the list of available color schemes in the WIN-OS/2 color panel. If you change color schemes and would like to return to the original color scheme, select WIN-OS/2 Original. o The performance of Windows** programs that use floating point operations can be improved by changing the WIN-OS/2 setting WIN_RUN_MODE to Enhanced Compatibility. o Windows scanning programs should be run in a WIN-OS/2 full-screen session to avoid video corruption. o To ensure the integrity of 16-color bit maps on SVGA, XGA*, and 8514 systems, run Microsoft** Paint Brush in a WIN-OS/2 full-screen session. o Some messages encountered in a WIN-OS/2 window session request that you select either Ignore or Close; when, the only options are Ignore and OK. Select OK instead of Close. o If you are using a WIN-OS/2 window session, an OS/2 Presentation Manager** session, and a DOS full-screen session, Alt+Esc might not sequence through all of the windows correctly. Alt+Esc might switch to the WIN-OS/2 session every other time, or the DOS full-screen session might never be displayed. To avoid this problem, press Ctrl+Esc or press mouse buttons 1 and 2 at the same time to display the Window List. Then select the desired session. o If you are in a full-screen WIN-OS/2 session and transparent desktop icons appear over open windows, minimize or maximize the window to force repainting. o During installation of the Windows 3.1 SDK, a message is displayed stating that the installation program cannot find KRNL286.EXE or KRNL386.EXE. Ignore the message and continue installation. The SDK will function normally. o If you are using the Winsleuth Gold hardware diagnostics program: - Do not run Chip test (a RAM test program). Chip test attempts to lock hardware interrupts. OS/2 2.1 does not allow programs to lock hardware interrupts. - When the video mode hardware test switches from character to graphics mode, a "suspended" message might appear. If the message appears, select Full-screen from the Sessions System menu. Testing will resume. ΓòÉΓòÉΓòÉ 4.7.3. APPLICATION NOTES: ΓòÉΓòÉΓòÉ APPLICATION NOTES: Access Dr. Watson** Hollywood** WinRoach** ------------------------------------------ Run in a WIN-OS/2 full-screen session. AmiPro** 2.0 and 3.0 -------------------- Equation symbols might be incorrect after certain printer drivers are installed. ATM fonts --------- WIN-OS/2 includes ATM fonts Version 2.5. If you were using a previous version of ATM fonts with your Windows programs, you can upgrade to the new ATM fonts provided by WIN-OS/2. See the "OS/2 2.1 Using the Operating System" book for instructions. Borland Turbo and Pascal debugger ---------------------------------- Run in a full-screen session. CorelDRAW** 2.0 ------------- Install from a DOS or OS/2 session. Facelift** Fonts ---------------- Modify the SYSTEM.INI file after the fonts are installed: 1. Edit the SYSTEM.INI file in the \OS2\WINOS2 directory. 2. Change the SDISPLAY.DRV= line to SDISPLAY.ORG=. 3. Copy the DISPLAY.DRV= line to the next line in the file. Add an "S" to the beginning of the new (copied) line. 4. Save and exit the file. 5. Restart WIN-OS/2. FoxPro** 2.5 ------------ Install using a WIN-OS/2 Enhanced-compatibility mode session, but run in a WIN-OS/2 standard-mode session. FrameMaker** ------------ Use a mouse to select table cells. Lotus Improv 2.0 for Windows ---------------------------- Must be installed with WIN-OS/2 running in enhanced mode. Mathematica** 2.2 ----------------- Must run seamlessly in a WIN-OS/2 window. Microsoft Windows Printing System --------------------------------- The OS/2 spooler must be disabled. If you are using a parallel printer, direct the output of the printer to LPT1 instead of LPT1.OS2. Norton Desktop** 2.0 ------------------ Run in a WIN-OS/2 full-screen standard-mode session. Paint Brush ------------- To ensure the integrity of 16-color bit maps on SVGA, XGA, and 8514 systems, run Paint Brush in a WIN-OS/2 full-screen session. If you are using the Paint Brush program in a WIN-OS/2 window session, the mouse pointer/hourglass will not disappear when the Zoom In option is selected from the View menu. In a full-screen WIN-OS/2 session, the mouse pointer/hourglass will disappear and only the Zoom In box will remain on the screen. If you are using Paint Brush to paint single pixels in zoom-in mode, the pixel being painted will look unpainted where the mouse pointer covers it. Zoom out and in again to see the entire pixel painted correctly. Powerpoint** 3.0 ---------------- If you are displaying the DROPBXV.PPT and GRIDWRVK.PPT demo slides in 640x480x256 resolution, you might see small horizontal line corruption. If you are using a WIN-OS/2 window, you might get incorrect background color when viewing a thumbnail of a template. This will not affect the running of the application. Video for Windows ----------------- Run in a full-screen session. If you configure video animation to run full-screen in Video playback, deselect Skip video frames if behind, to eliminate any corruption of the video during play. WindowWorks** ------------- Install in a WIN-OS/2 full-screen session. ΓòÉΓòÉΓòÉ 4.7.4. DOS APPLICATION COMPATIBILITY ΓòÉΓòÉΓòÉ DOS APPLICATION COMPATIBILITY o Use OS/2 system utilities. DOS system utilities might not recognize the extended attributes associated with a file. o OS/2 provides integral disk caching and memory optimization functions. Use of the equivalent functions that are provided with MS-DOS** 6.0 is not necessary and might produce errors. o It is not necessary to run SHARE.EXE in a DOS session. OS/2's DOS emulation provides SHARE.EXE compatible to that which comes with DOS versions 5.x and 6.x. ΓòÉΓòÉΓòÉ 4.7.5. APPLICATION NOTES: ΓòÉΓòÉΓòÉ APPLICATION NOTES: DOS Games --------- For performance reasons, play in a DOS full-screen session. Change the DOS setting VIDEO_8514A_XGA_IOTRAP to OFF. Fotoman** --------- If you have problems running Fotoman, set the DOS COM_DIRECT_ACCESS setting ON. Freelance Graphics** -------------------- If you are using Freelance in a WIN-OS/2 window, you might get incorrect background color when viewing a thumbnail of a template. This will not affect the running of the application. Harvard Graphics** 3.0 -------------------- If you have problems running Harvard Graphics 3.0 change the DOS setting VIDEO_8514A_XGA_IOTRAP to OFF. Maxis Sim City 2000 for DOS --------------------------- Under the Program tab for the program object, set the Optional Parameters to NO_MEM_CHK. Under the Session Tab, select the DOS_SETTINGS button and set DPMI_MEMORY_LIMIT to 8. Microsoft MSCDEX ---------------- Microsoft MSCDEX.EXE will only run in an OS/2 virtual machine boot (VMB) session. If you are using an OS/2 supported CD-ROM drive (your CD-ROM drive has an OS/2 specific driver) you should be able to run your CD-ROM based DOS program in a virtual DOS machine (VDM) session without MSCDEX.EXE running, since VCDROM.SYS emulates MSCDEX function in a VDM. To run DOS multimedia applications, change the DOS_SETTING, INT_DURING_IO to ON, for the program object. Intel** SatisFAXtion** ---------------------- Must be run in a specific DOS session, unless you do the following before you install the program: 1. Make a copy of your AUTOEXEC.BAT file and name it AUTOEXEC.FAX. 2. Install the program. 3. Rename the AUTOEXEC.BAT file FAX.BAT. 4. Rename the AUTOEXEC.FAX file AUTOEXEC.BAT. 5. Make a program object for the SatisFAXtion program. 6. Change the value of the DOS_AUTOEXEC setting for the object to FAX.BAT. 7. Save and exit the Settings notebook. Microsoft C/C++ 7.0 Linker -------------------------- If you are using Microsoft C/C++ 7.0, configure the program object's DOS_SETTINGs with DPMI_DOS_API=ENABLED. Also, modify the AUTOEXEC.BAT being used for the session so that the Microsoft \C700\BIN directory is searched first. For example: PATH X:\C700\BIN;C:\OS2;C:\OS2\MDOS;C:\OS2\MDOS\WINOS2;C:\; Paradox V4.0 ------------- If you have problems running Paradox V4.0 change the DOS setting DPMI_DOS_API = ENABLE. Wayne Gretsky's Hockey Game --------------------------- Not supported. Wing Commander** II ------------------- Set HW_TIMER to OFF. WordPerfect V6.0 ----------------- If you have problems running WordPerfect V6.0 change the DOS setting DOS_FILES = >99. Terminator Game --------------- Must use a joystick. ΓòÉΓòÉΓòÉ 4.7.6. OS/2 APPLICATION COMPATIBILITY ΓòÉΓòÉΓòÉ OS/2 APPLICATION COMPATIBILITY o Closing OS/2 applications that use the hardware palette (typically picture viewers or sample graphic applications) occasionally causes a repaint problem on the desktop. If the windows do not repaint correctly, a refresh will restore the desktop, but any windows that are opened or moved will still have the problem. Restarting the system is the only way to completely correct this problem. o If you are using Lotus 123G for OS/2 or Lotus Freelance Graphics for OS/2, you need to run the following utility prior to using these products with OS/2 2.1. 1. Change to the Lotus directory that contains the application. For example, type: CD \123G 2. Back up the LD2CORE.DLL file. For example, type: COPY LD2CORE.DLL LD2CORE.BAK 3. Run the update program. Type: LD2FIX The Lotus program is now updated. You need to shut down and restart your system for these changes to take effect. ΓòÉΓòÉΓòÉ 4.7.7. APPLICATION NOTES: ΓòÉΓòÉΓòÉ APPLICATION NOTES: Communications Manager/2 ------------------------ When used with Host Graphics support (HGINST) you might experience shutdown problems. Ensure that the following GDDM fixes have been applied to the host system: UN36882 - MVS UN38883 - VM/SP UN38884 - VM/XA SP UN38885 - DOS/VSE CorelDRAW 2.5 ------------- At the end of CorelDRAW 2.5 installation, you might experience problems if you select one of the View README options. The View README options are "Yes" and "No". If you select Yes, CorelDRAW will not run. Icons will be generated. You must restart your system and recreate each icon, using the Migrate Applications program. If you select No, CorelDRAW will not run. A folder will appear without icons. You must restart your system and create each icon, using the Migrate Applications program. For information on the Migrate Applications program, refer to the OS/2 2.1 Using the Operating System book. NetView DM/2 (NVDM/2) --------------------- o If you are using the CID method of installation, you will need an updated version of the LAPSCID.DLL file. This file is available as LAPDLL.ZIP on the CompuServe OS2SUPPORT forum, Lib #17 and the OS2BBS on TALKLINK. o Response install running under NetView to a SVGA or dual display system, with the primary as 8514, must have 10MB or more on the target system. Actual requirements depend on the applications running while using the response install. IBM LAN Server 2.0 and 3.0 Remote Installation Program Load (RIPL) ---------------------------------------------- An updated version is needed to run with OS/2 2.1. The diskette image is available as 2IRIPL.ZIP on the CompuServe OS2SUPPORT forum, Lib #17 and the OS2BBS on TALKLINK. IBM LAN Server DLR 2.0, 3.0 --------------------------- When running WIN-OS2 in a VMboot environment, with DOS and IBM LAN Server DOS LAN Requester 2.0 or 3.0, the logoff option causes the WIN-OS2 session to freeze. This problem occurs when network logon is performed prior to entering WIN-OS2. To resolve the problem, do the following: - Do not use the network logoff in WIN-OS2 when running LAN Server DOS LAN Requester 2.0 or 3.0. RUMBA/400 for OS/2 ------------------ If you use RUMBA/400 for OS/2, you might have a more recent version of the MIRRORS.DLL file, located in the \OS2\DLL directory. The file currently shipped with OS/2 2.11 is from Micrografix ToolKit Ver. 3.01, ship level A51 dated 11/16/93. Before you begin installing this version of the operating system, you must backup your current MIRRORS.DLL file. After you install this version of the operating system, you can replace the OS/2 2.11 level of MIRRORS.DLL with the backed up copy you previously created. ΓòÉΓòÉΓòÉ 4.7.8. DOS AND WIN-OS/2 MULTIMEDIA APPLICATION COMPATIBILITY ΓòÉΓòÉΓòÉ DOS AND WIN-OS/2 MULTIMEDIA APPLICATION COMPATIBILITY o The following WIN-OS/2 and DOS Settings should be used for Multimedia applications: DOS/WIN INT_DURING_IO ON DOS/WIN HW_TIMER ON WIN VIDEO_SWITCH_NOTIFICATION ON WIN VIDEO_8514A_XGA_IOTRAP OFF DOS/WIN VIDEO_RETRACE_EMULATION OFF DOS DPMI_MEMORY_LIMIT 8 ΓòÉΓòÉΓòÉ 4.7.9. APPLICATIONS NOTES: ΓòÉΓòÉΓòÉ APPLICATIONS NOTES: Action!** 2.0 ------------- Run in a WIN-OS/2 full-screen session. Change the following line in the AUTOEXEC.BAT file: SET TEMP=C:\ Animation Works** 1.0 --------------------- Run in 1024x768 resolution. IconAuthor** 4.0 ---------------- If you are running the demo for this program, you must exit and reenter the WIN-OS/2 session before running the actual application. LinkWay* Live 1.0 (Tool Series) -------------------------------- Use the following DOS setting to make the demo run properly: DOS_RMSIZE=576 MIDI ---- Make sure that the MIDI mapper (in the Control Panel) and channels are properly set to the sound adapter. Nautilus** 1.6 and 1.76 ----------------------- Run in a WIN-OS/2 full-screen session. ΓòÉΓòÉΓòÉ 4.7.10. NETWORK ΓòÉΓòÉΓòÉ NETWORK o Some systems could experience problems using Win-OS/2 with version 2.0 of the Novell Netware Requester on this version of the operating system. To correct the problems, it is necessary to upgrade to Novell Netware Requester for OS/2 Version 2.11. o The Workplace Shell login is not compatible with NetWare** 4.0 Directory Services and should be disabled unless you are using the NetWare 4.0 Bindery Compatibility mode. To disable the login: 1. Edit the CONFIG.SYS file. 2. Remove the CONNECTIONS option from SET AUTOSTART. 3. Save and exit the CONFIG.SYS file. 4. Restart the system to activate the changes. o If you are using the NetWare Requester version 2.01 (which ships with NetWare 4.0) but have no NetWare 4.0 servers, you can increase the speed of the login process by turning the Directory Services off. To turn the services off: 1. Edit NET.CFG file in the root directory of the boot drive. 2. Add "Directory Services Off" to the file. 3. Save and exit the file. o Novell** NetWare Requester 2.0 and 2.01 programs NMPIPE.SYS, NPSERVER.SYS, and NPDAEMON.EXE require that information be added to the OS2VER file. To add this information to the file: 1. At an OS/2 command prompt, type: ATTRIB -h -r -s OS2VER 2. Edit the OS2VER file in the root directory of the boot drive. 3. Type the following information in the file: 20=NMPIPE.SYS 20=NPSERVER.SYS 20=NPDAEMON.EXE 4. Save and exit the file. 5. Type ATTRIB +h +r +s OS2VER o If you are using FFST/2 (for example, if you enable the FFST/2 feature when installing Communications Manager/2 or Data Base Manager/2), REM out the "RUN=...\EPW.EXE" statement in your CONFIG.SYS file. To utilize FFST/2 technology, add a "DETACH EPW.EXE" as the first statement in your STARTUP.CMD file. o NetWare Client for OS/2 uses a default frame type of 802.2 on Ethernet networks. This is a change from the previous default frame type of 802.3. Some routers do not support Ethernet 802.2 frame types. If you are having difficulty connecting to your server, add 802.2 Ethernet frame support at the server, and ensure your router has the latest revision of software. o When using NetWare Client version 2.10 for OS/2, it is important to load NETX.EXE into both global and private DOS sessions. The NetWare Client installation program can modify AUTOEXEC.BAT and any other DOS_AUTOEXEC files you specify. You must also change the DOS_LASTDRIVE setting for each DOS session to the last local drive on your system. o The Virtual Loadable Module (VLM) version of the NetWare DOS Client kit can be run in a DOS 5 or 6 VMB session under OS/2 in either global or private mode. Use DOSVIPX to allow sharing of the network adapter. This allows limited access to NetWare 4.0x Directory Services in a DOS VMB session. o The Novell file system fails to recognize LPT4 through LPT9 print devices and creates a disk full file instead. Copy or pipe to \DEV\LPTx might function as a workaround or drag and drop using the Workplace Shell. o Pressing Ctrl-C in a NetWare utililty, running in a DOS session, might cause a SYS3175 error and the session to fail. The application will abort properly. If you still require a session start a new one. o Using a wildcard with the ATTRIB command can produce erratic results. Use NDIR or FLAG instead. o WIN-OS/2 File Manager and some other programs might show inaccurate drive information when running in a private NetWare session. Drives that are mapped in global or OS/2 sessions might appear as local drives. You can remap these drives to other volumes or directories without affecting the global session mappings. ΓòÉΓòÉΓòÉ 4.7.11. DISPLAY ADAPTERS (IMAGE, SVGA, XGA, 8514) ΓòÉΓòÉΓòÉ DISPLAY ADAPTERS (IMAGE, SVGA, XGA, 8514) o The OS/2 operating system will experience video problems similar to those observed in a DOS environment. These problems are due to the failure of a BIOS video mode set. An example of this problem is the video image on an ALR** Modular PS with a FlexView** 2x SVGA display failing to occupy the entire screen in 1024 x 768 mode. o If you are using an LCD display and have difficulty locating the mouse pointer on the screen, you can increase the size of the pointer if you are using 640x480 resolution. To change the size of the pointer (if you have REXX installed): 1. Use an editor to create a file called LARGE.CMD. 2. Add the following information to the file. /* LARGE.CMD Set VGA pointers to large */ /* (c) Copyright IBM Corp. 1992, All rights reserved */ call RxFuncAdd "SysIni", "RexxUtil", "SysIni" call SysIni "USER", "PM_IBMVGA", "CURSOR_SIZE", "1", say Result exit 3. Save and exit the file. 4. At an OS/2 command prompt, type "LARGE" and press Enter. This program will increase the size of the cursor. To force a standard size pointer, replace the "1" in the program with a "2". To let the system select the size of the pointer, replace the "1" in the program with a "0". o Users of the NCR** Safari notebook, SSL/25, should modify the following information in the CONFIG.SYS file on their startup drive to allow video register shadowing to be processed correctly in OS/2 2.1. Change: DEVICE=C:\OS2\MDOS\VVGA.SYS to DEVICE=C:\OS2\MDOS\VSVGA.SYS o Systems with Image Adapters running in dual-display modes will lose DOS window support after a DOS full-screen or OS/2 full-screen session has been invoked. The system must be restarted to reinstate the DOS window environment. The problem can be avoided by turning off the dual display mode under the Image Adapter setup. S3 FUNCTIONAL RESTRICTIONS --------------------------- o After Dark** for Windows** images that move from left to right do not perform properly at 640x480x16M resolution. o To avoid a General Protection fault while loading Ventura Publisher** for Windows be sure it is in one of the 256 color resolutions. o To avoid a trap in Lotus** 1-2-3** for OS/2 do not attempt to run the program at 16.7 million colors. o WordPerfect** 5.1 and 5.2 for Windows produce a general protection fault when the "Print Preview" option is selected while using 800x600x64K or 600x480x16 million color mode. o Users of the software motion video feature of MMPM/2 should expect satisfactory results in 256-color modes. However, in 64K-color modes, users of the feature will experience unusual MMPMCS results. The software motion video feature is not supported in 16 million color modes. In addition, the software motion video feature will take advantage of a 1MB aperture on video adapters and systems where it is available to improve the performance of video playback in 64K-color modes. For those systems with nonstandard locations, the actual physical address of the aperture must be provided in the following CONFIG.SYS statement: SET VIDEO_APERTURE=xxxh where "xxx" is a hexadecimal value in units of 1MB, representing the actual physical address to map to the aperture. For example, the IBM PS/ValuePoint Systems must have the statement: SET VIDEO_APERTURE=400h to use a physical address at 1GB. o If you are using the 256 color mode, and your desktop appears to be darker than other color modes, you must edit the SVGADATA.PMI file located in the \OS2 directory. Change the following statement from: HI-COLOR DAC by .... to: HI-COLOR DAC by unknown To make the changes effective you must reboot your system. NEW SETVGA PROCEDURE -------------------- Use the following procedure instead of the SETVGA command to return to VGA mode. NOTE: If your display is out of sync, start OS/2 using the OS/2 Installation Diskette, insert Diskette 1 when prompted, then press Esc to access a command prompt. Follow the instructions below to reset your display mode. o If you installed OS/2 from diskettes: 1. Be sure RSPDSPI.EXE is in the \OS2\INSTALL directory. If it is, go to step 2. If it is not, insert Installation Diskette 8 and unpack RSPDSPI.EXE with the following command: C:\OS2\UNPACK A:\INSTAID C: /N:RSPDSPI.EXE where: A: is the drive containing Installation Diskette 8 C: is the drive where OS/2 is installed 2. Type C:; then press Enter 3. Type CD C:\OS2\INSTALL; then press Enter 4. Type RSPDSPI /PK:VGA /SK:NONE /S:A:\ /T:C:; then press Enter /T:C: where C: is the drive where OS/2 is installed /S:A: where A: is the diskette drive you use to install OS/2 o If you installed OS/2 from CD-ROM or a LAN: 1. Be sure RSPDSPI.EXE is in the \OS2\INSTALL directory. If it is, go to step 2. If it is not, unpack RSPDSPI.EXE with the following command: C:\OS2\UNPACK E:\DISK_8\INSTAID C: /N:RSPDSPI.EXE where: C: is the drive where OS/2 2.1 is installed E: is the CD-ROM or LAN drive 2. Type C:; then press Enter 3. Type CD C:\OS2\INSTALL; then press Enter 4. Type RSPDSPI /PK:VGA /SK:NONE /S:E:\OS2SE21\ /T:C:; then press Enter /T:C: where C: is the drive where OS/2 2.1 is installed /S:E: where E: is the CD-ROM or LAN drive SVGA CONSIDERATIONS o The Western Digital** 90C31 SVGA chip set will have video problems when Windows 2.x applications are run. o If you are using a ZEOS** system with Speedstar** VGA, you must run the VMODE utility supplied with the system to configure the display during the display driver installation. o Zenith Data Systems** with the Headland Technology chip set HT208 do not support high resolution modes even though you can successfully set these modes and install high resolution drivers. If a high resolution mode is used, a white half-screen will be displayed. To correct this problem, use DSPINSTL to install VGA. o If you have a Sigma Legend** display adapter you might experience minor video corruption on the desktop when you switch between the desktop and DOS if they are running in different modes. This can be corrected by using a DOS utility to set the DOS session to the same mode as the desktop. XGA CONSIDERATIONS o If an XGA-2 adapter is installed, and you have modified the default display type in the System Settings notebook (page 2), after you restart the system it will display the Workplace Shell* in one resolution and WIN-OS/2 in a different resolution. To change the resolution for the Workplace Shell: 1. Open OS/2 System. 2. Open System Setup. 3. Open System. 4. Select a 640x480xn resolution. 5. Shut down and restart the system. 6. Repeat steps 1 through 3. 7. Select the desired resolution. 8. Shut down and restart the system. The Workplace Shell and WIN-OS/2 will now be displayed in the same resolution. o If you are using a dual-display system with XGA as the primary display and VGA as the secondary display, you might see some minor corruption when the XGA display is set to a resolution with 65536 colors. This corruption will be on the display that does not have focus and will not interfere with the operation of the system. o On dual-display configurations with XGA-2 as the primary display and VGA as the secondary display, the DOS full-screen session might be corrupted if a Windows application is started in a window session. To recover from this situation, shutdown and restart the system. o If you are using Dual Boot with an XGA-2 adapter, you must modify the CONFIG.DOS file: 1. Edit the \OS2\SYSTEM\CONFIG.DOS file. 2. Locate the line DEVICE=C:\DOS\EMM386.EXE RAM 2048 X=nnnn-nnnn 3. Change nnnn-nnnn to C000-CFFF. 4. Save and exit the file. o On IBM P75 systems, there might be some corruption on the screen whenever several icons are selected and moved together. This corruption can be eliminated by clicking mouse button 2 to bring up the pop-up menu and then selecting Sort. o An IBM P75 system with an external monitor attached might have only the 640x480x16 resolution selection on the the System Settings Screen page. If the external monitor is capable of displaying higher resolutions, use the P75 reference diskette to disable the built-in plasma display. o If you are using an XGA system, the hash lines around the icons of open applications might change color unexpectedly. This does not interfere with the operation of the system. o If you are using an XGA system, extra lines might appear on the face of the OS/2 System Clock between the quarter (:15) and half (:30) hour. These lines do not interfere with the operation of the clock. 8514 CONSIDERATIONS o If you are using the 1MB version of an ATI** Graphics Ultra** Pro adapter, the VGA memory must be set to SHARED to work properly with the OS/2 8514 display driver. This might cause some DOS applications running in the background to corrupt the desktop. To correct this problem, you must upgrade to the 2MB version of the Graphics Ultra Pro and set the VGA memory to 256K or greater. NOTE: In the "OS/2 Installation Guide", it states that the ATI Graphics Ultra Pro must be configured to IBM DEFAULT for the 640x480 display type. This setting might be referred to as 60Hz rather than IBM DEFAULT. o If you are using a system with an 8514 adapter with Windows applications running in separate WIN-OS/2 window sessions, video corruption might occur in bit maps when clipping between applications. o After you start a WIN-OS/2 window session, 256-color bit maps might become discolored due to the sharing of the 256-color palette. This should not affect the running of the applications. o Selecting windows in Mathematica might not bring focus to the proper window. ΓòÉΓòÉΓòÉ 4.7.12. AUDIO ADAPTERS ΓòÉΓòÉΓòÉ AUDIO ADAPTERS o Audio support in WIN-OS/2 and DOS sessions is dependent on installed drivers. You should install the audio adapter driver that came with your audio adapter. When installing audio support for WIN-OS/2, be sure to install both DOS and Windows device drivers. Configure both drivers to use the same interrupt level and DMA channel. o The following drivers are available with the Audio Capture and Playback Adapter (ACPA): - ACPADD.SYS - ACPADD2.SYS - ACPAK12.SYS - ACPA.DRV The latest updates are available on the IBM Bulletin Board Service. o MMPM/2 installs ACPA support for OS/2 only, not WIN-OS/2 or DOS. There are two ways to get DOS ACPA support in DOS sessions: 1. Edit the CONFIG.SYS file. 2. Add DEVICE=C:\ACPAK12.SYS 3. Save and exit the CONFIG.SYS file. 4. Copy the ACPAK12.SYS file to the C:\ directory. 5. Restart the system to activate the changes. Or 1. Point to the DOS full-screen or window object. 2. Click mouse button 2. 3. Select the arrow to the right of Open. 4. Select Settings. 5. Select the Session tab. 6. Select DOS Settings. 7. Select DOS_DEVICE. 8. Type C:\ACPAK12.SYS in the Value field. 9. Select Save. 10. Double-click on the title-bar icon to close the notebook. 11. Copy the ACPAK12.SYS file to the C:\ directory. To install WIN-OS/2 ACPA support: 1. Access the Control Panel in WIN-OS/2 Main. 2. Select Drivers. 3. Select Add. 4. Select Unlisted or Updated Drivers. 5. Select OK. 6. Insert the diskette containing the ACPA driver into drive A. 7. Type A: 8. Select OK. 9. When the Add Unlisted or Updated Driver screen is displayed, select the M-Audio sound driver. 10. Select OK. 11. When the IBM ACPA Driver Setup screen is displayed, select Proper Input Source. DEFAULT IS MIC NORMAL Select OK. 12. Select Restart Now. 13. Open WIN-OS/2 session. 14. Select the Control Panel in WIN-OS/2 Main. 15. Select MIDI Mapper. 16. Select the down arrow for Name. 17. Select Extended MIDI for ACPA. 18. Select Edit. 19. Select Yes. 20. Select port name for all 16 SRC channels to be IBM M-Audio MIDI SYNTH. 21. Select OK. 22. Select Yes. 23. Select Close. 24. Close the WIN-OS/2 session. o MMPM/2 installs Sound Blaster** support for OS/2 only, not WIN-OS/2 or DOS. o To add WIN-OS/2 Sound Blaster support: 1. Install the DOS device driver following the instructions that came with the adapter. Use a DOS session for the installation. 2. Install the Windows driver. NOTE: Be sure to use the same I/O address, interrupt, and DMA settings used during install of the DOS drivers. ΓòÉΓòÉΓòÉ 4.7.13. PRINTERS ΓòÉΓòÉΓòÉ PRINTERS o If you are using the HP** LaserJet** printer driver, some complex images might not print correctly when LaserJet performance options are enabled. If you experience incorrect output or degraded printer performance, return the performance options to the disabled state. To change the performance options: 1. Point to the printer object. 2. Click mouse button 2. 3. Select the arrow to the right of Open. 4. Select Settings. 5. Select the Printer Drivers tab. 6. Select Job properties. 7. Change the performance options to their default settings. 8. Double-click on the title-bar icon to close the notebook. o If you experience problems while printing bit maps from an application while using the PostScript printer driver, select the printer-specific format option on the Queue options page in the Settings notebook of your printer object. o The OS/2 printer drivers on the OS/2 2.11 printer driver diskettes are stored in a packed format that is not compatible with OS/2 1.3 or 2.0. To install one of the OS/2 2.11 printer drivers on a system with OS/2 1.3 or 2.0 installed, you must first unpack the driver on a system that has OS/2 2.11 installed. You do not have to complete these steps to install a printer driver on a system that already has OS/2 2.11 installed. NOTE: Do not install the new 32-bit PostScript driver (PSCRIPT.DR_) that came with OS/2 2.11 on a system with OS/2 1.3 or 2.0 installed. It is not compatible with these versions of OS/2. While testing is continuing, current compatibility information about tested systems is available through your dealer, Marketing Representative, CompuServe, IBM National Support Center Bulletin Board System (NSC BBS), and IBMLink*. To unpack a printer driver for use on a OS/2 1.3 or OS/2 2.0 system, complete the following steps on your system that has OS/2 2.11 installed. 1. Open an OS/2 command prompt. 2. Type: MD X:\DRIVER where X is a drive on your system. 3. Insert into drive A the OS/2 2.11 printer driver diskette that contains the printer driver you want to install. The printer driver names end in a "_". Printer Driver: Diskette # Packed Name: IBM Null 1 IBMNULL.DR_ HP LaserJet 1 LASERJET.DR_ HP DeskJet** 1 HPDJPM.DR_ IBM 52XX 1 IBM52XX.DR_ Epson 1 EPSON.DR_ Plotter Driver 1 PLOTTERS.DR_ IBM 4019 2 IBM4019.DR_ IBM 4076 2 IBMPCL3.DR_ IBM 42XX 2 IBM42XX.DR_ IBM 5201-2 2 IBM52012.DR_ PaintJet** 2 SMGXPJET.DR_ IBM 4039 3 IBMPCL5.DR_ NOTE: In order to get the proper printer driver directory structure on systems with OS/2 1.3, IBMPCL3, IBMPCL5, HPDeskJet and PaintJet must be installed using the Printer Install option in the Print Manager. Do not use the Control Panel to install these printer drivers. 4. Type: UNPACK A:\Packed name X:\DRIVER where X is a drive on your system. For example, if you want to install the Epson printer driver, type : UNPACK A:\EPSON.DR_ X:\DRIVER The printer driver files are now unpacked in the X:\DRIVER directory. 5. Copy the driver files to a diskette and install them on your OS/2 1.3 or 2.0 system. ΓòÉΓòÉΓòÉ 4.7.14. SCANNERS ΓòÉΓòÉΓòÉ SCANNERS If you have a Logitech hand scanner on an AT bus computer, run the scanner at the 100, 200, or 300 DPI setting. ΓòÉΓòÉΓòÉ 4.7.15. ADVANCED POWER MANAGEMENT SUPPORT FOR PORTABLE COMPUTERS ΓòÉΓòÉΓòÉ ADVANCED POWER MANAGEMENT SUPPORT FOR PORTABLE COMPUTERS o This version of OS/2 includes additional APM support that was not available for the original OS/2 2.1 release. Portables with 32 bit protect mode APM are now supported. Portable computers with the following are compatible with OS/2 2.11 Advanced Power Management: o 16-bit protect-mode APM in the BIOS o 32-bit protect-mode APM Portable computers that have no APM support in BIOS or have only real-mode APM are not supported by OS/2 2.11 Advanced Power Management. The DOS utility program APMHERE, which is available on the IBM BBS, can quickly determine whether your machine has Advanced Power Management support in con- formance to the APM 1.0 Specification (dated 1/91). Systems with BIOS dates prior to January 1991 will not have the protect-mode APM support in their BIOS. PORTABLE COMPUTERS WITH APM SUPPORT -------------------------------------- The table that follows lists the portable computers that have Advanced Power Management support. (This list represents only systems tested as of January 27, 1994.) MANUFACTURER MODEL COMMENTS ---------------------------------------------------- Acer AcerNote 730 BIOS informa- tion displayed on start up: PhoenixBIOS(TM) A486 Version 1.03 R1.0 Acer AcerNote 750 AST Research PowerExec 4/25SL Inc. MANUFACTURER MODEL COMMENTS ----------------------------------------------------- AST Research PowerExec 4/25SL Perform the Inc. Color Plus following 486SL/25 Active steps: Matrix Color 1. Press FN F1 keys to get BIO access 2. Select Power Man- agement 3. Click on Power Man- agement Section 4. Follow the Charac- terize the Battery instructions COMPAQ 4/25 COMPAQ CONTURA 4/25 Monochrome, VGA COMPAQ CONTURA 4/25C 486SL/25 Active Matrix COMPAQ CONTURA 4/25cx See NOTE 1. COMPUDYNE 4SL/25 BIOS informa- SubNOTEBOOK tion displayed on start up: PhoenixBIOS(TM) LAP486SL Version 1.03 PhoenixMISER(TM) 486L v2.0 80486SL BIOS Version 1.11 5/28/93 Gateway 2000 ColorBook 486SX/25 486SX/25 Dual Scan Color Gateway 2000 ColorBook See NOTE 1. 486DX/33 Requires cor- 486DX/33 Dual rected BIOS Scan Color from System Soft, Inc.; see NOTE 2. Gateway 2000 HandBook See NOTE 1. 486DX2/40 Requires cor- 486DX2/40 rected BIOS Monochrome from System Soft, Inc.; see NOTE 2. IBM P/S NOTE 425, For OS/2 2.11, 425c use F1 to display the configuration panel and set RESUME ON ALARM to OFF when running the Alarm applet. IBM ThinkPad 700, Version 1.2 or higher 700C, 720, 720C of the reference and diagnostic diskettes are required. IBM ThinkPad 750, NOTE 4. NCR Corp. NCR 3150 BIOS informa- 486SX/25 Active tion displayed Matrix Color on start up: PhoenixBIOS(TM) A486 Version 1.03 (C)1989-1993 Phoenix Technologies Ltd. All Rights Reserved. Reference ID 15 NCR Corp. SAFARI Battery Life, Power Source, * and Battery State informa- tion is incor- rect. NEC Technologies UltraLite Versa Inc. Sharp 6800 Battery Life, Power Source, and Battery State informa- tion might be incorrect. Texas Instru- TravelMate 4000, ments 486DX2, 50MHz Toshiba T1950, T1950CS, T1950CT 486DX2/40 Mono, Dual Scan Color, Active Matrix Color Toshiba T3400, T3400CT 486SX/33 Monochrome, Active Matrix Color Toshiba T4700CS 486DX2/50 Dual Scan Color Toshiba T4700CT 486DX2/50 Active Matrix Color Toshiba T6600C, T6600C/CD, T6600C/CDV 486DX2/66 Active Matrix Color Twinhead Corp. SubNote 486DX/33 Does not have 486DX/33 the CPU clock Monochrome slowdown feature. See NOTE 3. Zenith MastersPort 386SLe Zenith ZNOTE 325L NOTE 1: To run OS/2 2.11 in these models, change the statement "BASEDEV=IBM1S506.ADD" in CONFIG.SYS to the following: BASEDEV=IBMINT13.I13 NOTE 2: For these models, the following BIOS information is displayed on start up: Systems Soft Bios for 80486/82C463 v1.01 (2069-09) Contact Systems Soft, Inc. (508-651-0088) for a corrected version of BIOS. NOTE 3: The OS/2 APM calls into the BIOS APM once per second to check if it is OK to do a suspend. The following BIOS do not return OK to suspend on OS/2 APM calls if the video display is active or changes during the CMOS suspend timeout: o PhoenixBIOS Version 1.03 o Phoenix NoteBIOS 486/OPTi463 Version 1.03 o PhoenixMISER V2.0 NOTE 4: Reinstall the ThinkPad video drivers after you finish installing OS/2 2.11. PORTABLE COMPUTERS WITHOUT APM SUPPORT --------------------------------------- The table that follows lists the portable computers that do not have APM support in their BIOS; however, they can be configured to run OS/2 2.11 if APM is not installed. (This list represents only systems tested as of January 27, 1994.) If you have installed OS/2 APM, ensure that it is removed properly by doing the following: o Remove the following two APM device statements from CONFIG.SYS: DEVICE=C:\OS2\APM.SYS DEVICE=C:\OS2\MDOS\VAPM.SYS o Delete the APM.SYS and VAPM.SYS files from the corre- sponding hard disk subdirectories. This gains about 1 second in startup and frees up hard disk space. MANUFACTURER MODEL COMMENTS ----------------------------------------------------- COMPAQ LTE-386s/25 See NOTE 1. COMPAQ LTE LITE 25/c See NOTE 1. 386SL COMPAQ LTE LITE 4/25e, See NOTE 1. 4/25c, 486SL/25 Active Matrix COMPUDYNE 3SXL/25 SLIMNOTE BIOS informa- tion displayed on start up: PhoenixBIOS(TM for VLSI Laptop 80386 BIOS Version 1.01 R2-1 06/09/92 IBM L40SX Discontinued product. See NOTE 2. IBM P/S NOTE, Model For OS/2 2.11, 2141 use F1 to get the configura- tion panel and set RESUME ON RING and RESUME ON ALARM to OFF. IBM PS/2 N51 Install using 386SX/SLC UINSTALL. 8551-025 Librex T386SX If screen is black after resume, toggle the F1 key (Suspend key) to to refresh screen. Northgate ZX Portable BIOS informa- 486SX/25 tion displayed on start up: Phoenix A486 version 1.01 See NOTE 3. Texas Instru- TravelMate 4000 See NOTE 3. ments WinDX2, 486DX/25 MHz Texas Instru- TravelMate 4000 See NOTE 3. ments WinSX Texas Instru- TravelMate 4000e See NOTE 3. ments SX25 Passive Matrix Color Texas Instru- TravelMate 4000e See NOTE 3. ments WinDX2/50 Active Color Texas Instru- TravelMate 4000 See NOTE 3. ments WinDX2/50 486DX2/50 Monochrome Toshiba T1800 386SX/20 See NOTE 4. Monochrome Toshiba T1850, T1850C See NOTE 4. 386SX/25 Monochrome, Dual Scan Color Toshiba T1900, T1900C See NOTE 4. 486SX/20 Monochrome, Dual Scan color Toshiba T2200SX 386SX/20 See NOTE 4. Monochrome Toshiba T3100SX 386SX/16 See NOTE 4. Mono Plasma Toshiba T3300SL 386SL/20 See NOTE 5. Monochrome Toshiba T4400SX, See NOTE 4. T4400SXP, T4400SXC 486SX/25 Mono, Plasma, AMC Toshiba T4400C 486DX/33 See NOTE 4. Active Matrix Color Toshiba T4500, T4500C See NOTE 4. 486SX/20 Monochrome, Active Matrix Color Toshiba T4600, T4600C See NOTE 5. 486SL/33 Monochrome, Active Matrix Color NOTE 1: To run OS/2 2.11 in these models, change the statement "BASEDEV=IBM1S506.ADD" in CONFIG.SYS to the following: BASEDEV=IBMINT13.I13 NOTE 2: For OS/2 2.11 APM, access the IBM BBS and down- load the following 3 files: o TGSFX.COM (located in file area 4) o RFL40SXA.TG0 (located in file area 27) o L40PWR.ZIP (located in file area 37) Execute TGSFX.COM to install the TELEGET.EXE program. Then do the following: 1. Create a new L40SX reference diskette by using TELEGET.EXE to unpack RFL40SXA.TG0 onto a 1.44MB formatted diskette. 2. Use PKUNZIP to unzip the L40PWR.ZIP to obtain new IDLE.EXE and PWRMGMT.SYS files. 3. Replace the IDLE.EXE and PWRMGMT.SYS files on the newly created L40SX reference diskette with the new IDLE.EXE and PWRMGMT.SYS files obtained from the previous step. 4. Restart L40SX with the resulting reference diskette in A drive and configure with APM. 5. Verify the APM configuration by selecting VIEW CONFIGURATION from the installation menu. 6. Exit the configuration. 7. Power off the computer and restart OS/2. NOTE 3: Contact the manufacturer for newer versions of their BIOS that have APM support. NOTE 4: These models require the Toshiba APM driver (OS2RES.EXE) available from the Toshiba BBS (714-837-4408). This Toshiba driver will provide partial power management capabilities under OS/2 2.11. NOTE 5: While running OS/2, you can use the special power-saving keys but the additional capability of OS/2 protect-mode APM is not supported. ΓòÉΓòÉΓòÉ 4.7.16. MAHJONGG GAME ΓòÉΓòÉΓòÉ MAHJONGG GAME NOTE: The following information does NOT apply to the ServicePak version of the operating system. OS/2 2.1 includes a new tile-matching game called Mahjongg Solitaire. To install Mahjongg Solitaire from diskettes: 1. Insert Diskette 10 into drive A. 2. Open an OS/2 command prompt. 3. Type: UNPACK A:MAHJONGG drive: where drive is the drive letter of the partition OS/2 2.1 is installed on. 4. Press Enter. 5. Type: MAHINST and press Enter. Then, follow the instructions on the screen. To install Mahjongg Solitaire from CD: 1. Insert the CD into the CD drive. 2. Open an OS/2 command prompt. 3. Type: UNPACK cd\drive:\OS2SE21\DISK_11\MAHJONGG drive: where cddrive is the drive letter of the CDROM and drive is the drive letter of the partition OS/2 2.1 is installed on. 4. Press Enter. 5. Type: MAHINST and press Enter. Then, follow the instructions on the screen. ΓòÉΓòÉΓòÉ 4.7.17. Trademarks ΓòÉΓòÉΓòÉ Trademarks TRADEMARKS __________ The following terms, denoted by an asterisk (*) in this README, are trademarks or registered trademarks of the IBM Corporation in the United States or other countries: Audio Capture and Playback Adapter ------------------------------------------ IBM ------------------------------------------ IBMLINK ------------------------------------------ LinkWay ------------------------------------------ Micro Channel ------------------------------------------ Multimedia Presentation Manager/2 ------------------------------------------ NetView ------------------------------------------ OS/2 ------------------------------------------ Presentation Manager ------------------------------------------ WIN-OS/2 ------------------------------------------ Workplace Shell ------------------------------------------ XGA ------------------------------------------ The following terms, denoted by a double asterisk (**) in this README, are trademarks of other companies as follows: Trademark: Owner: -------------------------------------------------------------- Action! Expertelligence -------------------------------------------------------------- ALR Advanced Logic Research, Inc. -------------------------------------------------------------- AMI Pro Lotus Development Corp. -------------------------------------------------------------- Animation Works Gold Disk Inc. -------------------------------------------------------------- APM Astek International Ltd. -------------------------------------------------------------- ATI ATI Technologies, Inc. -------------------------------------------------------------- CompuServe CompuServe Incorporated -------------------------------------------------------------- CorelDraw Corel Systems Corporation -------------------------------------------------------------- DeScribe DeScribe Inc. -------------------------------------------------------------- DeskJet Hewlett-Packard Company -------------------------------------------------------------- Dr. Watson Empirical Tools and Technology -------------------------------------------------------------- Epson Seiko Epson Kabushiki Kaisha -------------------------------------------------------------- Facelift Bitstream Inc. -------------------------------------------------------------- FlexView Advanced Logic Research, Inc. -------------------------------------------------------------- FotoMan Logitech International -------------------------------------------------------------- FoxPro Fox Software, Inc. -------------------------------------------------------------- FrameMaker Frame Technology, Inc. -------------------------------------------------------------- Freelance Graphics Lotus Development Corporation -------------------------------------------------------------- Hollywood Claris Corporation -------------------------------------------------------------- HP Hewlett-Packard Company -------------------------------------------------------------- IconAuthor Aimtech Corporation -------------------------------------------------------------- Intel Intel Corporation -------------------------------------------------------------- LaserJet Hewlett Packard -------------------------------------------------------------- Legend Sigma Designs Inc. -------------------------------------------------------------- Logitech Logitech, Inc. -------------------------------------------------------------- Mathematica Wolfram Research, Inc. -------------------------------------------------------------- Microsoft Microsoft Corporation -------------------------------------------------------------- MS-DOS Microsoft Corporation -------------------------------------------------------------- Nautilus Softshell Systems -------------------------------------------------------------- NCR NCR Corporation -------------------------------------------------------------- NET NCR Corporation -------------------------------------------------------------- NetWare Novell, Inc. -------------------------------------------------------------- Norton Desktop Symantec Corp. -------------------------------------------------------------- Novell Novell, Inc. -------------------------------------------------------------- Paint Brush Microsoft Corporation -------------------------------------------------------------- PaintJet Hewlett-Packard Company -------------------------------------------------------------- Panasonic Matsushita Electric Industrial Co., Ltd. -------------------------------------------------------------- PostScript Adobe Systems Inc. -------------------------------------------------------------- PowerPoint Microsoft Corporation -------------------------------------------------------------- SatisFAXtion Intel Corporation -------------------------------------------------------------- Sound Blaster Creative Labs, Inc. -------------------------------------------------------------- SpeedStar Diamond Computer Systems, Inc. -------------------------------------------------------------- ULTRA ATI Technologies Inc. -------------------------------------------------------------- Western Digital Western Digital Corporation -------------------------------------------------------------- Windows Microsoft Corporation -------------------------------------------------------------- WindowWorks Spinnaker Software Corporation -------------------------------------------------------------- Wing Commander Origins Systems, Inc. -------------------------------------------------------------- WordPerfect WordPerfect Corporation -------------------------------------------------------------- Zenith Data Systems Zenith Electronics Corporation -------------------------------------------------------------- ZEOS ZEOS International Ltd. -------------------------------------------------------------- IBM DISCLAIMS ALL WARRANTIES, WHETHER EXPRESSED OR IMPLIED, INCLUDING WITHOUT LIMITATION, WARRANTIES OF FITNESS AND MERCHANTABILITY WITH RESPECT TO THE INFORMATION IN THIS DOCUMENT. BY FURNISHING THIS DOCUMENT, IBM GRANTS NO LICENSES TO ANY RELATED PATENTS OR COPYRIGHTS. (c) Copyright IBM Corporation, 1992, 1994, all rights reserved. ΓòÉΓòÉΓòÉ 4.8. OS/2 2.11 ServicePak (XR06200) README file ΓòÉΓòÉΓòÉ OS/2 2.11 ServicePad (XR06200) README file Installing OS/2 2.11 ServicePak Files are in the \OS2SP subdirectory Welcome to OS/2* 2.11. This document provides you with information you need before you install this version of the ServicePak. It contains helpful hints found in our testing as well as updates and corrections to the "OS/2 2.1 Installation Guide". Use this information in conjunction with the "OS/2 2.1 Installation Guide", and the "OS/2 2.1 Using the Operating System" manual. You also can use the new "Updates to: Installation Guide and Using the Operating System" booklet, provided with this version of OS/2. o This version of the ServicePak contains the following deliverables: - Service to the OS/2 2.1 operating system. These diskettes are used to service the OS/2 base operating system files, including the installed printer drivers. - Updated Display Driver diskettes. These diskettes are provided as replacements for the original OS/2 2.1 Display Driver diskettes. You might be prompted to insert these diskettes during installation. - Updated Printer Driver diskettes. These diskettes are provided only as replacements for the original OS/2 2.1 Printer Driver diskettes. You will NOT be prompted for these diskettes during installation. - Updated MMPM/2 installation diskettes. These diskettes are to be used to install service for this version of MMPM/2. o You will notice that the color scheme has changed for this version of OS/2. o After you install this version of OS/2, and you want to return to the desktop layout of your previous version of OS/2 you must press Alt-F1 prior to and up until the OS/2 logo screen is displayed. This will restore your CONFIG.SYS and your OS/2 system .INI files from the \OS2\INSTALL directory. o After you install this version of OS/2, and you want to return to the default desktop, you must do the following: 1. Restart your system using the OS/2 Installation Diskette, then insert Diskette 1. 2. Press Esc to display the OS/2 command prompt; then change to the \OS2 directory, on your hard drive. 3. Delete the current .INI files, and type: DEL OS2.INI (and press Enter) DEL OS2SYS.INI (and press Enter) 4. Re-create both files using the MAKEINI command. Type: MAKEINI OS2.INI INI.RC (and press Enter) MAKEINI OS2SYS.INI INISYS.RC (and press Enter) 5. Change to the \DESKTOP directory. 6. Delete all subfolders (subdirectories). 7.Change to the root directory. 8. Delete the hidden file WP?ROOT.?SF in the startable partition. Type: \OS2\ATTRIB -h -s -r WP?ROOT.?SF (and press Enter). Type: DEL WP?ROOT.?SF (and press Enter). 9. Press Ctrl+Alt+Del. The desktop is reinstalled to the default desktop. 10. Shut down the system using the Shut down choice on the desktop pop-up menu. o To install this version of the ServicePak, you must have 1MB available on your hard disk with 100KB free required on drive C. The size of the operating system increases after you apply service and varies based on your specific system configuration. This size increase will not exceed 1MB. o The WINOS2.ICO file has been updated for this version of OS/2. If you have customized this file, be sure to rename your file before you install OS/2. After you install, delete the new WINOS2.ICO file, then rename your backed up copy back to WINOS2.ICO. o If you are installing on a computer with 6 meg of memory or less, you must add the following lines to your CONFIG.SYS file located on Disk 2 of this version of the ServicePak. MEMMAN=SWAP, PROTECT SWAPPATH=C:\OS2\SYSTEM 2048 2048 where C:\OS2\SYSTEM refers to the drive and path where you have available SWAP space. If the CONFIG.SYS file located on Disk 2 is READONLY, you can turn off the READONLY attributes by typing the following: ATTRIB -r CONFIG.SYS Shut down your system and when it starts, your CONFIG.SYS files are updated. o If you receive a return code 15 while installing this version of the ServicePak, one or more of your system .INI files are locked. Your system .INI files might be READONLY. As a result, the system will not update the .INI files. When this happens, the position of the icons will not be saved. To resolve this problem go to the directory where your system .INI files are located C:\OS2 (default). Then, type the following: ATTRIB -r *.ini Shut down your system and when it starts, your system .INI files are updated. o Feedback from OS/2 testing and Customer Service indicates that, on some platforms, hardware performance related features might cause a failure in the OS/2 Installation program. The most common symptom of this problem is a Trap 002, which occurs while transferring files to the hard disk. If you are unsuccessful at installing OS/2 on your computer, you should consider the following procedure. Some hardware platforms provide settings to enable/disable performance related features. On systems that support this function, change the settings in your CMOS to the following: o Turbo/System Speed should be OFF/Slow o Caching (External) should be OFF o ROM Shadowing (System and Video) should be OFF To improve system performance after you have installed OS/2, all of the above settings can be changed back without causing damage to OS/2. o If you have a version of the OS/2 2.11 beta installed, you need to reformat the OS/2 partition. Installing OS/2 2.11 over a previous beta version is not supported. Do not use any OS/2 system files (such as OS2.INI or OS2SYS.INI) from a previous beta version. o If you are installing this version of the ServicePak and you receive the message: "The response file C:\CSF_SEL.000 is invalid." (where C:\ is representative of the drive where the file is located.) this indicates that there is a problem with the installation of the ServicePak. You must delete this file before you can continue installing the ServicePak. o If you are installing this version of the ServicePak, and currently have a PCMCIA communication device (modem or fax/modem), you must check your CONFIG.SYS file to ensure proper placement of the following device statement: DEVICE=C:\OS2\PCMCIA.SYS This statement must be located after the COM.SYS device statement, or your communications device might not function. o If you are using an IOMEGA PC Powered Pro 90, you must call the IOMEGA service number and request OAD Driver Version 2.3. o If you are installing from CD-ROM or diskette, you must install this on a partition that has OS/2 2.1 currently installed. o If you are installing this version of the ServicePak from CD-ROM and you receive the message: "The response file A:\RESPONSE.FIL was not found." this indicates that you cannot access your CD-ROM drive. Check the CD-ROM drive to ensure it is inserted correctly, or that it is ready and you are using a valid CD-ROM configuration. o Multimedia (MMPM/2) support can be installed directly from the CD-ROM. Change to the \MMPM2 subdirectory and perform a normal Multimedia install using MINSTALL. You can also create Multimedia diskette images for installation as described in this readme. o If you are using Selective Install to add support to your system after installing this version of the ServicePak: 1. Open the OS/2 System folder. 2. Open the System Setup folder. 3. Open the Selective Install object. 4. Select the items you want to install. 5. Select OK and choose drive A as the source drive. 6. When prompted to insert the OS/2 diskettes, insert the OS/2 2.1 Installation diskettes. (Service might need to be reapplied to ensure your system is at the proper level.) 7. When prompted to insert device driver diskettes, insert the device driver diskettes provided with the CSD. 8. Shutdown and reboot the computer to activate the changes. o If you have a DOS system with compression activated, do one of the following: 1. Decompress the disk 2. Select a different partition 3. Format the disk o Based on information provided by OS/2 testing and customer service, some computers using features related to hardware performance might fail during the OS/2 Installation program. The most common symptom of this problem is a Trap 002, which occurs while transferring files to the hard disk. PREINSTALLED SYSTEM CONSIDERATIONS ---------------------------------- o Before you install this version of the ServicePak, you must follow the steps below to backup files that will be overwritten during installation. 1. Open an OS/2 command prompt. 2. Change to the PRELOAD directory, Type: C: then press Enter, type, CD \OS2\INSTALL\PRELOAD then press Enter. 3. To make backup copies, type: COPY OS2LDR.MSG OS2LDR.BAK then press Enter, type, COPY README README.BAK then press Enter, type, COPY SAMPLE.RSP SAMPLE.BAK then press Enter. 4. Now install the ServicePak. o After you install the ServicePak or any time you reapply the ServicePak, to ensure you have the correct files on your preinstalled computer follow these steps: 1. Open an OS/2 command prompt. 2. Remove the following files by typing: DEL C:\OS2\INSTALL\DSPDRVS\*.DSP 3. Insert Display Driver Diskette 1 in drive A 4. Type: XCOPY A:*.* C:\OS2\INSTALL\DSPDRVS\*.* 5. Repeat steps 2 and 3 for Display Driver Diskette 2 and 3. 6. Insert Printer Driver Diskette 1 in drive A 7. Type: XCOPY A:*.* C:\OS2\INSTALL\PRTDRVS\PMDD_1\*.* 8. Insert Printer Driver Diskette 2 in drive A 9. Type: XCOPY A:*.* C:\OS2\INSTALL\PRTDRVS\PMDD_2\*.* 10. Insert Printer Driver Diskette 3 in drive A 11. Type: XCOPY A:*.* C:\OS2\INSTALL\PRTDRVS\PMDD_3\*.* This enables you to update your display and printers as needed. 12. Change to the PRELOAD directory, Type: C: then press Enter, and type, CD \OS2\INSTALL\PRELOAD then press Enter. 13. To restore your backed up copies, type: COPY OS2LDR.BAK OS2LDR.MSG then press Enter, type, COPY README.BAK README then press Enter, type, COPY SAMPLE.BAK SAMPLE.RSP then press Enter. This enables you to retain the correct version of these files needed for Create Utility diskettes and Selective Uninstall. If you created your utility diskettes after installing this version of the ServicePak and you did not backup and restore OS2LDR.MSG file, the following message will be displayed: Insert the Operating System/2 diskette 1 into Drive A: you must insert Utility diskette 2 into drive A, and then press Enter to continue. o After you install this version of OS/2 on a system originally installed with the Blue diskettes, you must copy UNPACK.EXE to UNPACK2.EXE located in the \OS2 directory. This enables you to successfully perform a Selective Install. If you originally installed with the Salmon diskettes, you DO NOT need to perform the previous instructions. CREATING DISKETTES FROM THE OS/2 CD You use the LOADDSKF utility program to create the diskettes. (LOADDSKF.EXE is in the \DISKIMGS directory of the CD. LOADDSKF can be run from either the DOS or OS/2 operating system.) In the following sections, you will see lists of the product diskettes for OS/2 2.11 and the actual diskette names as they exist on the CD. For each diskette image file, use LOADDSKF to expand the image to its own diskette. (Note that you must use formatted diskettes for this procedure.) For example: cddrive:\DISKIMGS\LOADDSKF cddrive:\DISKIMGS\OS2\size\disk_name d: where: cddrive is the drive letter of the CD-ROM size is 35 for 3.5-inch diskettes or 525 for 5.25-inch diskettes disk_name is the diskette image file name (for example, DISK1.DSK, PMDD1.DSK.) d is the drive letter of your diskette drive (A: or B:) List of 3.5-Inch Diskette Images DISKIMGS\OS2\35\DISK1.DSK -- INSTALLATION Diskette DISKIMGS\OS2\35\DISK2.DSK -- DISKETTE INSTALLATION diskette 2 DISKIMGS\OS2\35\DISK2_CD.DSK - CD-ROM INSTALLATION Diskette 2 DISKIMGS\OS2\35\DISK3.DSK -- Diskette 3 of 13 DISKIMGS\OS2\35\DISK4.DSK -- Diskette 4 of 13 DISKIMGS\OS2\35\DISK5.DSK -- Diskette 5 of 13 DISKIMGS\OS2\35\DISK6.DSK -- Diskette 6 of 13 DISKIMGS\OS2\35\DISK7.DSK -- Diskette 7 of 13 DISKIMGS\OS2\35\DISK8.DSK -- Diskette 8 of 13 DISKIMGS\OS2\35\DISK9.DSK -- Diskette 9 of 13 DISKIMGS\OS2\35\DISK10.DSK -- Diskette 10 of 13 DISKIMGS\OS2\35\DISK11.DSK -- Diskette 11 of 13 DISKIMGS\OS2\35\DISK12.DSK -- Diskette 12 of 13 DISKIMGS\OS2\35\DISK13.DSK -- Diskette 13 of 13 DISKIMGS\OS2\35\PMDD1.DSK -- Printer Drivers Diskette 1 of 3 DISKIMGS\OS2\35\PMDD2.DSK -- Printer Drivers Diskette 2 of 3 DISKIMGS\OS2\35\PMDD3.DSK -- Printer Drivers Diskette 3 of 3 DISKIMGS\OS2\35\DISP1.DSK -- Display Drivers Diskette 1 of 3 DISKIMGS\OS2\35\DISP2.DSK -- Display Drivers Diskette 2 of 3 DISKIMGS\OS2\35\DISP3.DSK -- Display Drivers Diskette 3 of 3 List of 5.25-Inch Diskette Images DISKIMGS\OS2\525\DISK1.DSK -- INSTALLATION Diskette DISKIMGS\OS2\525\DISK2.DSK -- DISKETTE INSTALLATION diskette 2 DISKIMGS\OS2\525\DISK2_CD.DSK - CD-ROM INSTALLATION Diskette 2 DISKIMGS\OS2\525\DISK2.DSK - Diskette 2 of 16 DISKIMGS\OS2\525\DISK3.DSK - Diskette 3 of 16 DISKIMGS\OS2\525\DISK4.DSK - Diskette 4 of 16 DISKIMGS\OS2\525\DISK5.DSK - Diskette 5 of 16 DISKIMGS\OS2\525\DISK6.DSK - Diskette 6 of 16 DISKIMGS\OS2\525\DISK7.DSK - Diskette 7 of 16 DISKIMGS\OS2\525\DISK8.DSK - Diskette 8 of 16 DISKIMGS\OS2\525\DISK9.DSK - Diskette 9 of 16 DISKIMGS\OS2\525\DISK10.DSK - Diskette 10 of 16 DISKIMGS\OS2\525\DISK11.DSK - Diskette 11 of 16 DISKIMGS\OS2\525\DISK12.DSK - Diskette 12 of 16 DISKIMGS\OS2\525\DISK13.DSK - Diskette 13 of 16 DISKIMGS\OS2\525\DISK14.DSK - Diskette 14 of 16 DISKIMGS\OS2\525\DISK15.DSK - Diskette 15 of 16 DISKIMGS\OS2\525\DISK16.DSK - Diskette 16 of 16 DISKIMGS\OS2\525\PMDD1.DSK - Printer Drivers Diskette 1 of 4 DISKIMGS\OS2\525\PMDD2.DSK - Printer Drivers Diskette 2 of 4 DISKIMGS\OS2\525\PMDD3.DSK - Printer Drivers Diskette 3 of 4 DISKIMGS\OS2\525\PMDD4.DSK - Printer Drivers Diskette 4 of 4 DISKIMGS\OS2\525\DISP1.DSK - Display Drivers Diskette 1 of 3 DISKIMGS\OS2\525\DISP2.DSK - Display Drivers Diskette 2 of 3 DISKIMGS\OS2\525\DISP3.DSK - Display Drivers Diskette 3 of 3 If you want to create diskettes for the Multimedia support that is part of OS/2 2.11, note that the images are located in the \DISKIMGS\MMPM2 directory. Use LOADDSKF to expand each image to its own diskette. For example: cddrive:\DISKIMGS\LOADDSKF cddrive:\DISKIMGS\MMPM2\size\disk_name d: where: cddrive is the drive letter of the CD-ROM size is 35 for 3.5-inch diskettes or 525 for 5.25-inch diskettes disk_name is the diskette image file name (for example, DISK1.DSK) d is the drive letter of your diskette drive (A: or B:) NOTE: Use previously formatted diskettes for the target (b:). List of 3.5-Inch Multimedia Diskette Images DISKIMGS\MMPM2\35\DISK1.DSK - Diskette 1 of 2 DISKIMGS\MMPM2\35\DISK2.DSK - Diskette 2 of 2 List of 5.25-Inch Multimedia Diskette Images DISKIMGS\MMPM2\525\DISK1.DSK - Diskette 1 of 3 DISKIMGS\MMPM2\525\DISK2.DSK - Diskette 2 of 3 DISKIMGS\MMPM2\525\DISK3.DSK- Diskette 3 of 3 CREATING INSTALLATION DISKETTES FOR THE CD-ROM INSTALL ------------------------------------------------------ To create the two installation diskettes for the CD-ROM install from an OS/2 command prompt, follow the instructions above to create the INSTALLATION Diskette (DISK1.DSK) and CD-ROM Diskette 2 (DISK2_CD.DSK). To proceed with the CD-ROM install: Shutdown OS/2, and then insert INSTALLATION diskette 1 in drive A and press Ctrl-Alt-Del. IMPORTANT CD-ROM INSTALLATION INFORMATION ------------------------------------------ Important information for users of Mitsumi, Panasonic (Creative Labs Omni CD, IBM ISA or Panasonic), or Sony 31a CDROM drives. BEFORE ATTEMPTING TO INSTALL THIS SERVICE PACK YOU MUST MODIFY the CONFIG.SYS on Diskette 2. To enable this service pack to be installed from your CD drive, you MUST edit the config.sys on diskette 2 and modify the BASEDEV= statement for your drive to include the CORRECT /P:??? parameter. To determine the correct value for ??? in the /P:??? parameter, edit the config.sys on your working system, locate the driver statement (one of the following) for your CD drive, and copy the /P:??? parameters from this statement to the same statement in config.sys on diskette 2. (for Panasonic, Creative, or IBM ISA) BASEDEV=SBCD2.ADD (for Mitsumi) BASEDEV=MITFX001.ADD (for Sony 31a) BASEDEV=SONY31.ADD If you have one of these statements in your existing OS/2 CONFIG.SYS, you can skip the rest of these instructions. If you do NOT have your CD drive currently working under OS/2 with one of these driver statements, but DID have the CD working under DOS, edit the DOS CONFIG.SYS, locate the DEVICE= statement for your CD Drive, and copy THAT /P: value to the appropriate statement above. IMPORTANT NOTE: If you do NOT have the CD working under OS/2 currently, and install this service from the CD, the driver WILL NOT be copied onto your system for you, but you CAN copy the driver manually, and ADD the support AFTER the service is applied by following the steps below. Place the service pack diskette 2 into the A: drive, open and OS/2 or DOS command session and type the following commands: (drive: below is the drive letter for your current OS/2 boot drive).. COPY A:\OS2CDROM.DMD drive:\os2 COPY A:\CDFS.IFS drive:\os2 COPY A:\xxx.ADD drive:\os2 (where xxx is the appropriate name from the list of drivers above) Edit the existing CONFIG.SYS on your OS/2 boot drive and place the following three lines AT THE END of the file: DEVICE=drive:\os2\OS2CDROM.DMD /Q IFS=drive:\os2\CDFS.IFS /Q BASEDEV=xxx.ADD /P:??? where this line matches the line you modified to allow service to be installed from the CDROM drive. CID and NVDM/2 NOTES -------------------- o For LCU and NVDM/2 users, you must unpack SEMAINT.EXE from the CID tree where your current CSD version of OS/2 2.11 resides, to the CID Code Server, directory ?:\EXE\OS2V21. o When invoking SEMAINT.EXE supplied with XR06200 or XR06300 the following rules apply to your installation procedures: (1) FSERVICE.EXE is bounded to the CSD for the product you are installing. Therefore, you must make sure your installation procedures access the corresponding version of FSERVICE in the appropriate CSD Install tree. (2) When invoking FSERVICE.EXE for XR06200 or XR06300, you must specify the new "/CID" parameter. This new parameter only applies to installations that have had SEMAINT installed. This new parameter is not needed when the client system is booted by diskette. (3) Installation of the XR06200 or XR06300 requires the specification of the "/S2:<CSDpath>" during the invocation of SEMAINT.EXE. (4) Installation of any CSD in your procedures FOLLOWING the installation of XR06200 or XR06300 requires that the "/S2:<CSDpath>" parameter be specified during the invocation of SEMAINT.EXE. (5) Installation of any CSD in your procedures PRIOR to the installation of XR06200 or XR06300 requires that the "/S2:<CSDpath>" parameter be omitted during the invocation of SEMAINT.EXE. o If you use SEMAINT to create maintenance systems to apply the ServicePak, statements are added to the CONFIG.SYS file created by SEMAINT. These statements enable swapping to the target drive and directory of the maintenance system. This path is determined by the /T: parameter that SEMAINT uses when it is started. Swapping is enabled only on systems with 10 megabytes of RAM or less. The initial swap file size will be set to 1024KB or 1 meagabyte and can grow depending on the amount of virtual memory needed during installation of the ServicePak. This requires you to have at least 5 megabytes of free disk space prior to creating the maintenance system created by SEMAINT. LCU and NVDM/2 EXAMPLES ----------------------- Example of the LCU command file for the /cid option x.os2v21csd = 1 x.1.name='OS/2 2.1 Service Pack' x.1.statevar = 'CAS_' || x.1.name x.1.instprog = 'x:\img\csd\os2v21\fservice.exe ', '/t:' || bootdrive || '\service ', '/cid ', '/s:x:\img\csd\os2v21 ', '/l1:x:\log\csd\os2v211\' || client || '.log ', '/r:' x.1.rspdir = 'x:\rsp\csd\os2v21' x.1.default = 'response.fil' Example of the LCU command file for the /s2: option x.semaint2 = 1 x.1.name='OS/2 2.x Maintenance - with /S2:' x.1.statevar = '' x.1.instprog = exepath || '\semaint ', '/s:' || os2img || ' ', '/s2:' || os2v21csdimg || ' ', '/t:' || bootdrive || '\service ', '/b:' || bootdrive || ' ', '/l1:' || os2log || '\' || client || '.log' x.1.rspdir = '' x.1.default = '' ============================================================================== Example of the Net View DM/2 profiles for the /cid option TargetDir = C:\SERVICE Section Install Begin Program = SA:\IMG\CSD\OS2V21\FSERVICE.EXE Parms = /CID /S:$(SourceDir) /T:$(TargetDir) /L1:$(LogFile1) /R:$(ResponseFile) SourceDir = SA:\IMG\CSD\OS2V21 ResponseFile = SA:\RSP\CSD\OS2V21\RESPONSE.FIL LogFile1 = SA:\LOG\CSD\OS2V21\$(WorkStatName).LOG End Example of the Net View DM/2 profiles for the /s2: option TargetDir = C:\SERVICE Section Install Begin Program = SA:\EXE\OS2V21\SEMAINT.EXE Parms = /B:C: /S:$(SourceDir) /S2:SA:\IMG\CSD\OS2V21 /T:$(TargetDir) /L1:$(LogFile1) SourceDir = SA:\IMG\OS2V21 LogFile1 = SA:\LOG\OS2V21\$(WorkStatName).LOG End *************************************************************************** New drives supported in OS/2 2.1 ServicePak ------------------------------------------------ Vendor CD-ROM Drive Model --------------------------------- Creative Labs OmniCD Chinon 431 Chinon 435 Chinon 535 IBM ISA CD-ROM Mitsumi CRMC-LU005 Mitsumi CRMC-FX001 Mitsumi CRMC-FX001D Panasonic CR-521 Panasonic CR-522 Panasonic CR-523 Panasonic CR-562 Panasonic CR-563 Sony CDU-31A Sony CDU-7305 New SCSI drives certified to work in OS/2 2.1 or OS/2 2.1 ServicePak ------------------------------------------------------------------------- IBM Enhanced CD-ROM II NEC MultiSpin 3Xe NEC MultiSpin 3Xi NEC MultiSpin 3Xp Philips LMS CM215 Texel DM-3028 Texel DM-5028 SCSI-BASED CD-ROM SUPPORT _________________________ The majority of SCSI-based CD-ROM drives and adapters are supported by OS/2 2.1. ("SCSI-based" refers to the small computer system interface (SCSI), a standard input/output interface used by personal computers.) A complete list of the CD-ROM drives and SCSI adapters tested on OS/2 2.1 can be found in the "Hardware Support" chapter of the "OS/2 2.1 Using the Operating System" manual. OBTAINING ADDITIONAL CD-ROM SUPPORT If, after reviewing the list in "OS/2 2.1 Using the Operating System", you find that your CD-ROM drive or SCSI adapter is not supported within the OS/2 product, you can contact the manufacturer and obtain an OS/2 Adapter Device Driver (.ADD) file. After you receive the .ADD file, follow the instructions in the "Before You Begin" section of the "OS/2 2.1 Installation Guide" to add this file to Diskette 1. As an alternative, you can create installation diskettes from the diskette images that are on the OS/2 CD, if you have DOS support for your CD-ROM drive. If support for your CD-ROM was not properly installed during initial installation of OS/2 2.1, then you will need to use the Selective Install program located in the System Setup folder to reinstall the CD-ROM support appropriate for your CD-ROM. HARDWARE CONSIDERATIONS _______________________ If you have a Quantum hard card, you must make a modification to the BASEDEV=IBM1S506.ADD line in the CONFIG.SYS file of Diskette 1 before you install OS/2 2.1. The BASEDEV statement should be modified as follows: BASEDEV=IBM1S506.ADD /A:1 /IRQ:11 (These are the default settings for the Quantum hard card.) If you have added a device driver statement to the CONFIG.SYS file on diskette 1 and later migrate your old CONFIG.SYS file, make sure there are not two copies of this statement in your file. If you have two copies of this statement in your file, REM one statement out. If you have a Logitech** TrackMan**, select one of the two Logitech mouse choices during installation. If you are using a ThinkPad 750c, after installing this version of the ServicePak, you might find that your DOS full screen session is corrupted. To fix this problem you must reinstall the video driver from the ThinkPad audio features diskette. If you are installing OS/2 2.11 on a micro-channel system with an IDE disk controller on the planner with an microchannel SCSI adapter installed as an option, refer to the OS/2 2.11 Update booklet information about installing OS/2 2.1 on a ThinkPad with a Docking Station. INSTALLING OS/2 2.1 USING RIPL ______________________________ When installing OS/2 2.1 using the IBM LAN Server 2.0 and 3.0 Remote Installation Program Load (RIPL), the 2.1 version of RIPLINST.EXE is dependent upon the 2.1 version of UNPACK.EXE. Therefore, if you are using the 2.1 version of RIPLINST.EXE on a client machine with OS/2 version 2.0 or lower, then you must copy the UNPACK.EXE file to the client machine. To do this, do the following: 1. Insert OS/2 2.1 Diskette 2 into drive A 2. At an OS/2 command prompt type: copy a:\unpack.exe \os2\unpack.exe After copying the file to the client machine, you can now execute the 2.1 version of the RIPLINST.EXE program. EXTENDED SERVICES (ES) 1.0 __________________________ o If you installed OS/2 2.11 on a system that already had Extended Services installed, replace the existing ESSTART.CMD file with the ESSTART.BAK file that was installed by OS/2 2.11. (The ESSTART.BAK file is located in the OS2\INSTALL subdirectory.) o If you are installing Extended Services over OS/2 2.11 for the first time (that is, there is no Extended Services on the workstation), or if you are installing Extended Services from diskettes, rename the existing ESSTART.CMD file from the Extended Services Diskette 1. Then, copy the file ESSTART.BAK from the \OS\INSTALL directory to Extended Services Diskette 1. Finally, rename the ESSTART.BAK file ESSTART.CMD, and begin the installation of Extended Services. VIDEO CONSIDERATIONS ____________________ The XGA DMQS (\xga$dmqs\*.dqs) files in this version of the operating system do not have DPMS (Display Power Management Signaling) enabled for the DPMS supported monitors. You must use the Power Management Utility. The following information pertains to video support for OS/2 2.11. INSTALLING SUPER VGA (SVGA) SUPPORT o After the VGA installation is complete, follow the procedure "Installing Support for Super VGA (SVGA)" in Appendix A of the "OS/2 2.1 Installation Guide". o Installing this version of the ServicePak does not fully service base video on SVGA systems. To complete updates to base video, you must open a DOS Full Screen session and type the following: SVGA ON This creates a new SVGADATA.PMI file in the C:\OS2 directory. To make the changes effective, you must shutdown and reboot your computer. INSTALLATION ON SPECIFIC VIDEO ADAPTERS In the "OS/2 2.1 Installation Guide", instructions are given for configuring the ATI** Graphics Ultra Pro. These instructions state that the monitor type for 640 x 480 must be configured to IBM DEFAULT. Note that this setting might be referred to as 60Hz rather than IBM DEFAULT. The Radius XGA display adapter is supported on PS/2* Models 35 and 40 and PS/ValuePoint* 486 systems. If you are using the display adapter on a PS/ValuePoint system, the VPXGA.EXE utility is required. For a copy of this utility program, check your Radius installation diskette or contact Radius. The OS/2 2.11 operating system cannot restore the state of a Sigma Legend** display adapter after you switch sessions or video modes. Also, the Sigma Legend video adapter might cause the system to stop when using 1024 x 768 x 256 color mode. Use only 640 x 480 or 800 x 600 mode with this adapter. S3 VIDEO ACCELERATOR DRIVER FOR OS/2 2.11 ---------------------------------------- This video accelerator driver supports the 86C801/86C805 and 86C928 chip sets from the S3** Corporation. These chip sets are found on many leading video display adapters, including Actix**, Artist Graphics**, Diamond Stealth**, Focus**, Metheus**, MiroMAGIC, Nth Graphics**, Number Nine**, Orchid**, PCG**, Vermont**, Video 7**, Volante** and on the system boards of leading hardware systems, such as those from the IBM* Corporation and the Dell** Computer Corporation. SUPPORTED FEATURES ------------------ This S3 video accelerator driver provides seamless support for accelerated video graphics and advanced color resolutions when used with the minimum required video memory. It conforms to the OS/2 2.11 32-bit flat memory model and is designed to function as a 32-bit Presentation Manager* display driver under the OS/2 2.11 32-bit graphics engine. This video accelerator driver supports these resolutions and colors depths: Number of Video Memory Resolutions Colors Required 640x480 256 1MB 800x600 256 1MB 1024x768 256 1MB 1280x1024 256 2MB 640x480 65,536 1MB 800x600 65,536 1MB 1024x768 65,536 2MB 640x480 16,777,216 1MB This S3 video accelerator driver supports the following number of columns and rows in an OS/2 full-screen session: Columns Rows 132 25 132 43 INSTALLATION FROM DISKETTE __________________________ This video accelerator driver is compatible with OS/2 2.1. Do not install it on previous versions of OS/2. Use the SVGA install instruction to install S3 video device drivers. Refer to Appendix A in the "OS/2 2.1 Installation Guide." COMPATIBILITY --------------------------------------- IBM has tested many display adapters containing the S3 chips sets. Those that have tested successfully are listed in this README file. However, certain display adapters in combination with certain chip sets might not be supported. IBM is continuing to test; therefore, support for additional combinations is expected to be added over time. NOTE: If you are using the 256 color mode, and your desktop appears to be darker than other color modes, you must edit the SVGADATA.PMI file located in the \OS2 directory. Change the following statement from: HI-COLOR DAC by .... to: HI-COLOR DAC by unknown To make the changes effective you must reboot your system. S3 Adapters/Systems Chipsets ----------------------------------------------- Actix GraphicsENGINE 32 801 Actix GraphicsENGINE 32 LB 805 Actix GraphicsENGINE ULTRA 928 Artist Graphics** Winsprint 928 Diamond Stealth 24** 801 Diamond Stealth 24 LB** 805 Diamond Stealth Pro** 928 Diamond Stealth Pro LB** 928 Focus 2 The Max Truespeed 801 Metheus (Brooktree DAC) 928 Metheus (AT&T** DAC) 928 MiroMAGIC S4 LB 928 National Design Volante** Warp 10 LB 805 Nth Graphics** S3 Advantage 801 Nth Graphics S3 Advantage LB 805 Number Nine** #9** GXE (Brooktree DAC) 928 Number Nine #9 GXE (AT&T DAC) 928 Orchid Fahrenheit** 1280 Plus 801 Orchid Fahrenheit LB 805 PCG** Photon Torpedo 801 PCG Photon Torpedo LB 805 Vermont** 801 ISA 801 Video 7 Win.Pro** 801 IBM PS/ValuePoint* 805 Dell 805 INSTALLATION IN A CID ENVIRONMENT ---------------------------------- NOTE: OS/2 2.11 must have been successfully installed on the client using the CID Method. To install the S3 video accelerator driver using CID, use the following information to modify your LCU command file. NOTE: The following information is meant as a guide, your LCU command file might be different. /*****************************************************/ /* LCU PRODUCT DATA SECTION */ /*****************************************************/ . . . x.s3dspinstl = 16 x.16.name='S3 CID Dspinstl' x.16.statevar = 'CAS_' || x.16.name x.16.instprog = bootdrive || '\os2\install\DSPINSTL.EXE', ' /pk:SVGA', ' /sk:NONE', ' /s:x:\img\os2v21, ' /t:' || bootdrive, ' /mc:8' x.16.rspdir = '' x.16.default = '' /*---------------------------------------------------*/ /* NUMBER OF PROGRAMS SET UP IN THE */ /* PRODUCT DATA SECTION */ /*---------------------------------------------------*/ NUM_INSTALL_PROGS = 16 /*****************************************************/ /* INSTALLATION SECTION */ /*****************************************************/ . . . when OVERALL_STATE = 3 then do if RunInstall(x.s3dspinstl) == BAD_RC then exit Call CheckBoot end . . . end exit /*****************************************************/ END OF LCU INFORMATION TO BE ADDED /*****************************************************/ Following is an explanation of the line that is executed in the LCU command file: C:\OS2\INSTALL\DSPINSTL /PK:SVGA /SK:NONE /S:X:\ /T:C: /MC:8 /PK:SVGA where SVGA is the primary adapter key /SK:NONE where NONE is the secondary adapter key /S:X:\ where X:\ is the redirected source path /T:C: where C: is the drive where OS/2 2.11 is installed /MC:8 is the manufacturing code that distinguishes S3. NOTE: After the S3 video accelerator driver has been successfully installed on the client machine using the CID method and the client machine is restarted, the default resolution will be 640x480x256. Trademarks ---------- The following terms, denoted by an asterisk (*) in this file, are trademarks or registered trademarks of IBM Corporation in the United States and/or other countries: IBM Presentation Manager OS/2 PS/ValuePoint The following terms, denoted by an asterisk (**) in this file, are trademarks or registered trademarks of other companies as follows: Trademark Owner ------------------------------------------------------- Actix Actix Systems Corporation After Dark Berkely Systems, Inc. Artist Graphics Artist Graphics AT&T American Telephone & Telegraph Company Dell Dell Computer Corporation Diamond Stealth Diamond Computer Systems, Inc. Diamond Stealth 24 Diamond Computer Systems, Inc. Diamond Stealth 24 LB Diamond Computer Systems, Inc. Diamond Stealth Pro Diamond Computer Systems, Inc. Diamond Stealth Pro LB Diamond Computer Systems, Inc. Fahrenheit Orchid Technology, Inc. Focus Information Builders, Inc Lotus Lotus Development Corporation Metheus Metheus Corporation Nth Graphics Nth Graphics Number Nine Number Nine Computer Corporation Orchid Orchid Technology, Inc. PCG Personal Computer Graphics Corporation S3 S3 Incorporated Ventura Publisher Ventura Software, Inc. Vermont Vermont Microsystems Video 7 Video Seven, Inc. Video 7 Win.Pro Video Seven, Inc. Volante National Design INc. Windows MicroSoft Corporation WordPerfect WordPerfect Corporation 1-2-3 Lotus Development Corporation #9 Number Nine Computer Corporation IBM DISCLAIMS ALL WARRANTIES, WHETHER EXPRESSED OR IMPLIED, INCLUDING WITHOUT LIMITATION, WARRANTIES OF FITNESS AND MERCHANTABILITY WITH RESPECT TO THE INFORMATION IN THIS DOCUMENT. BY FURNISHING THIS DOCUMENT, IBM GRANTS NO LICENSES TO ANY RELATED PATENTS OR COPYRIGHTS. THIS DRIVER IS COPYRIGHTED BY INTERNATIONAL BUSINESS MACHINES CORPORATION. ALL APPROPRIATE RESTRICTIONS APPLY. --------------------------------------------------------------------------- TRADEMARKS __________ The following terms, denoted by an asterisk (*) in this README, are trademarks or registered trademarks of the IBM Corporation in the United States or other countries: IBM ----------------------------------------------- OS/2 ----------------------------------------------- PS/2 ----------------------------------------------- PS/ValuePoint ----------------------------------------------- ThinkPad ----------------------------------------------- XGA ----------------------------------------------- The following terms, denoted by a double asterisk (**) in this README, are trademarks of other companies as follows: Trademark: Owner: -------------------------------------------------------------- Adaptec Adaptec, Inc. -------------------------------------------------------------- ATI ATI Technologies, Inc. -------------------------------------------------------------- Legend Sigma Designs Inc. -------------------------------------------------------------- Logitech Logitech, Inc. -------------------------------------------------------------- Panasonic Matsushita Electric Industrial Co., Ltd. -------------------------------------------------------------- TrackMan Logitech, Inc. -------------------------------------------------------------- Windows Microsoft Corporation -------------------------------------------------------------- IBM DISCLAIMS ALL WARRANTIES, WHETHER EXPRESSED OR IMPLIED, INCLUDING WITHOUT LIMITATION, WARRANTIES OF FITNESS AND MERCHANTABILITY WITH RESPECT TO THE INFORMATION IN THIS DOCUMENT. BY FURNISHING THIS DOCUMENT, IBM GRANTS NO LICENSES TO ANY RELATED PATENTS OR COPYRIGHTS. Copyright IBM Corporation, 1993, all rights reserved. ΓòÉΓòÉΓòÉ 4.9. OS/2 2.1 for Windows Service Pak XR06300 ΓòÉΓòÉΓòÉ OS/2 2.1 for Windows Service Pak XR06300 We have tried to listen and respond to the feedback from the internal and external forums and BBS's about the problems encountered with the ship level version of OS/2 2.1 ServicePak. In addition to the problems that were fixed by the OS/2 2.1 ServicePak, we have fixed the following pervasive problems that were found after the OS/2 2.1 ServicePak was installed. High Resolution Video Problems (PJ13483, defect 81739) - The OS/2 2.1 for Windows ServicePak sets your video display back to VGA. Please see the section in the README.INS titled, "RESTORING HIGH RESOLUTION AND COLOR AFTER INSTALLING OS/2 2.1 FOR WINDOWS SERVICEPAK" for information on getting your display back to high resolution. This was provided as the 211DDU package on the OS2CSD conferencing disk for the OS/2 2.1 ServicePak. Because of the wide variety of platforms and environments, we would appreciate feedback on how this works for you. Swapper not shrinking (PJ12410, defect 80314)- This is a problem with the swapper file not shrinking as quickly as it used to (it does shrink, just verrrrry slowly). We have fixed this problem in the OS/2 2.1 for Windows ServicePak. CD-ROM Support using AHA152X.ADD not working as designed (PJ12402, defect 80099) - With a Toshiba CD-ROM drive, this device driver has problems unless synchronous notification is turned off (/!SN added to device statement). This problem has been fixed in the OS/2 2.1 for Windows ServicePak. Blue vs. Pink Diskettes; UNPACK/UNPACK2 problems (defect 79460) - OS/2 2.1 for Windows was built and shipped using UNPACK2 exclusively. This problem does not exist for the OS/2 2.1 for Windows ServicePak. MS Word for Windows 6.0 (PJ12465, defect 80608) - A change made to support >8.3 file names in real-mode caused a new regression to occur in VDM applications (specifically MS Word for Windows 6.0, but others could be affected). The symptom is that the session appears to be hung with no response from the mouse or keyboard. This problem has been fixed in the OS/2 2.1 for Windows ServicePak. FORBROWS problem (PJ13370, defect 81504) - The FORBROWS application was experiencing a SYS3175 followed by a hang (its icon is still hashed and Ctrl-Alt Esc does not work) after the application exits. This problem has been fixed in the OS/2 2.1 for Windows ServicePak. Stacked icons (PJ13646, defect 78372) - This problem occurs when you migrate applications or when you open a network folder. Many, if not all of your application icons are stacked one on top of the other. A workaround was provided which indicated that you needed to do an ARRANGE or REFRESH of the folder and the icons would be correctly positioned. This problem has been fixed in the OS/2 2.1 for Windows ServicePak and the workaround is no longer necessary. Double Desktops (PJ12398, defect 78888) - This problem was caused by setting the the Desktop settings, Window, Object open behavior to Create new window. This resulted in an additional desktop folder appearing on your desktop. A workaround was provided that consisted of changing SET RESTARTOBJECTS=STARTUPFOLDERONLY or NO which was unacceptable to many users. This problem has been fixed in the OS/2 2.1 for Windows ServicePak and this workaround is no longer necessary. Cross hatched icons after the process has ended (PJ11814, defect 81479) - Another instance of this problem has been fixed in the OS/2 2.1 for Windows ServicePak. S3 and Valuepoints are blowing up VP monitors (APAR PJ12267, defect 79495) - This problem is fixed in the OS/2 2.1 for Windows ServicePak. Personal AS/2 does not work (PJ13647, defect 79080)- This problem resulted in a black screen with PAS/2 after the OS/2 2.1 ServicePak was installed. This problem has been fixed in the OS/2 2.1 for Windows ServicePak. APM Suspend function not working on ThinkPad 750C (PJ12413, defect 80196) - A fix that was made to the APM.SYS to support the Toshiba caused the suspend function on ThinkPad 750C and other laptops to no longer work. This problem has been fixed in the OS/2 2.1 for Windows ServicePak. CONFIG.SYS is READ-ONLY on diskette version of CSD (PJ12527, defect 80766) - The CONFIG.SYS file was erroneously set to READ-ONLY on the diskette version of the CSD. This has been fixed in the OS/2 2.1 for Windows ServicePak. RECOVER command executed against the whole partition destroys it (PJ13645, defect 81565) - RECOVER command works fine for individual files; however, if executed against the whole partition, it destroys the partition. RECOVER is changed to warn you that all data on the hard disk will be lost and ask you to confirm that you really want it to proceed if it is executed against the whole partition. TRACE facility (PJ08731, defect 69815)- The TRACE facility, which is used by the service organization for debugging purposes (part of the DUMP process), has been fixed in the OS/2 2.1 for Windows ServicePak. ΓòÉΓòÉΓòÉ 4.10. Summary of APARs fixed in Service Pak XR06200 Part 1 ΓòÉΓòÉΓòÉ Summary of APARs fixed in Service Pak XR06200 Part 1 SUMMARY OF APARs OS/2 STANDARD EDITION 2.1 SERVICE PAK XR06200 February 1994 ********************************************************************* * * * The following list provides a brief abstract of each APAR fixed * * in OS/2 2.1 XR06200 ServicePak. Every effort has been made to * * include all APARs fixed in OS/2 2.1 on this list, how ever some * * APAR numbers could be omitted from this list but are fixed in * * this ServicePak. If you have a concern with an APAR number not * * on the list, please contact IBM OS/2 Support for verification. * * * * Note: Some APAR numbers listed below are duplicated of other * * APAR numbers. Where this is the case, the duplicated APAR * * number is listed for information only. * * * ********************************************************************* JR06387 :WINSENDMSGWITHMM _ INSERTITIEMANDMIT _ ENDDOESNOT FORCE MENU ITEM TO THE VERY END OF THE MENU JR06444: MLE COULD NOT SCROLL TO THE LEFT WHEN THEY INPUT THE 1ST LINE JR06654: 12 BYTE CORRUPTION IN HPFS EXE'S/DLL'S JR06944: INCORRECT INTERNAL FILE IDENTIFIER NEED SYS#### AND HELP JR06958: LOADING 223RD FONT SET, IPE OR NOT ENOUGH MEMORY ERROR JR07070: TRAP 000D IN DOSEXECPGM FROM SESSION MANAGER WHEN APP STARTED FROM SHELL JR07106: MOUSE DISAPPEARS WHEN PROGRAM USE ON MLE JR07108: OS/2 UNABLE TO HANDLE "OPLOCK" FEATURE PROPERLY JR07163: SYS1943 WHEN PRINTING TO A PSCRIPT QUEUE THAT HAS A PRINTER DEFINITION ASSOCIATED WITH MORE THAN 6 DRIVERS PJ02409: PLACING 1 BITMAP IN 2 THREADS PRODUCES WRONG ERROR MESSAGE PJ03753: FROM NETWORK FOLDER, ALIAS'S FOR LOGON FUNCTION CAUSES USES TO BE MADE TO ALL ALIAS'S WHICH DO NOT DISCONNECT PJ04121: IF PRINTER ICON IS SET TO TWO LINES THE ICON TEXT UNDER 'SET DEFAULT' IS INCORRECT PJ04625: DOS BATCH FILE STATEMENT "IF EXIST C:\TEST\NUL" ALWAYS RETURNS TRUE PJ04767: HIDDEN ATTRIBUTE IS LOST WHEN A FILE IS COPIED USING DRAG-AND-DROP PJ04796: INCOMPLETE PRINT JOBS USING THE DATABASE APPLET IN THE PRODUCTIVITY FOLDER PJ05036: PRINTING AAAAA.MET TO HP PAINTJET RETURNS ERROR PJ05253: TRAP 000D WHEN RETURNING FROM DOSQPROCSTATUS PJ05352: TRAPDUMP DOES NOT WORK PROPERLY WITH 6091 DISPLAY PJ05700: OBJECT CREATED USING WINCREATEOBJECT AND NOMOVE=YES AND THEN UPDATED WITH NOMOVE=NO CANNOT THEN BE UPDATED WITH NOMOVE=YES PJ05949: WM_CHAR MESSAGES CHANGED IN 2.0 FOR SHIFT + F1, F9, AND ENTER PJ06190: BAD BOUNDING BOX IN OS/2 V2 WITH USE OF POSTSCRIPT PRINTER DRIVER PJ06241: SCREEN BLANKS IN WORDPERFECT WHEN SWITCHING TO AND FROM FULL SCREEN PJ06745: PULSE REDUCING IT'S PRIORITY TO IDLE IN THREAD 1, RECEIVES SIGTERM WHEN USER TRIES TO CLOSE IT AND NEVER PROCESSES THE MESSAGE PJ06839: COPY DOES NOT COPY EVERY FILE FROM A REDIRECTED DRIVE IF THE LAN DISCONNECTS AND RECONNECTS PJ06852: SYSTEM TRACE MINOR CODE FOR DEVHELP ISN'T IMPLEMENTED CORRECTLY PJ06871: CANNOT USE DITHERED COLORS FOR CONTAINERS - CONTAINER DOESN'T USE RGB PJ07034: PROGRAM THAT USES VIOREGISTER TO HOOK VIO API'S AN KBDREGISTER FOR KBD API'S GOES OUT OF SYNC WHEN SWITCHING TO FULLSCREEN PJ07070: OS/2 2.0 SHOULD NOT BE TRYING TO RESTART PROGRAMS THAT WERE STARTED FROM A NON-LOCAL DRIVE PJ07122: THE POST INVOCATION TRACE POINT FOR 32-BIT PMGPI ISN'T IMPLEMENTED PJ07139: THE POST AND PRE TRACE POINT FOR 32-BIT PMGRE AREN'T IMPLEMENTED PJ07167: BACKUP.EXE UNECESSARILY RESTRICTS CMD.EXE AND COMMAND.COM FROM BEING BACKED UP PJ07204: WINSHUTDOWNSYSTEM FUNCTION BLOCKS WM_QUIT MSG AFTER ABANDON SYSTEM SHUTDOWN PJ07234: CONTAINER IS NOT REPAINTING PROPERLY TO THE NEW SIZE WHEN IT IS IN THE DETAIL VIEW PJ07273: REPLACE IS NOT ALLOWED FOR COPY OR MOVE OF FOLDER PJ07274: NO ERROR MESSAGE IS DISPLAYED BY THE SHELL WHEN A COPY OR MOVE FAILS PJ07323: MINIMIZED WINDOW VIEWER (MWV) SORT MENU MISLEADING. UNAVAILABLE FUN- CTIONS APPEAR TO BE ENABLED - THEY SHOULD BE GREYED OUT PJ07357: OS/2 LOGO SCREEN SCRAMBLED UPON BOOTUP ON OEM SYSTEMS WITH THE M3125 VIDEO BOARDS PJ07589: PMWIN HANGING SYSTEM DUE TO THREAD BEING KILLED WHILE OWNING SEMA- PHORE(FSRHEAP) PJ07729: CHKDSK GIVES ERRONEOUS DATA AND CHKDSK /F CORRUPTS HARD DISK ON DR_DOS 6.0 PJ07780: KBDFLUSHBUFFER FAILING WITH RETURN CODE OF 500 (X'1F4') PJ07783: REXX APPLICATION FAILS ACCESSING INTERNAL CD-ROM, TRAP 000D PJ07815: OS/2 PERMANENT RESTRICTION NOT DOCUMENTED IN USER DOCS REGARDING DATA LENGTH LIMITATION OF 65535 BYTES WHEN PASTING INTO WINDOW PJ07850: COMBO LIST DROP BOX MALFUNCTION USING NUMERIC KEYPAD AS INPUT PJ07862: GPIBITBLT PROBLEMS PRINTING TO PRINTER - EPSON 9 PIN PRINTER DRIVER MAGITRONIX 486/33DX 16 M AMI BIOS 240 MEG IDE DRIVE PJ07875: TRACE FAILS IF MINOR CODE IS GREATER THAN 32769 DEC ( HEX 80) PJ07917: INCORRECT WINDOW TITLE WHEN _WPREGISTERVIEW IS USED PJ07941: USING CODEPAGE=863,850 GETTING MIX ACCENTUATED UPPER CHARACTERS WHEN MODIFYING THE TITLE OF AN OS/2 ICONS PJ07949: NETWORK SERVER MODE ENABLED DOES NOT WORK PJ07988: DRAG TO FOLDER CAUSES WRONG FILE TO BE REPLACED PJ07994: _WPSETICONDATA DOES NOT WORK WITH 16 BIT RESOURCE DLLS PJ07997: ERROR MSG BOX LOST FOCUS WHEN OPEN RESTRICTIVE DIRECTORY PJ08000: DEFAULT 'OPEN' ACTION CANNOT BE CHANGED FOR PROGRAMS OR BATCH COMMAND FILES PJ08004: SYS3175 ACCESS VIOLATION IN PMCTLS.DLL WHEN USING EPM OR OTHER APPS WHICH USE THE FILE SAVE DIALOG PJ08006: DRIVES CONTAINER SLOW TO POPULATE WITH LARGE NUMBERS OF SUBDIRECTORIES PJ08016: OBJECTVISION DOES NOT PRINT SPECIAL FONTS PJ08087: PSCRIPT.DRV IS NOT PRINTING ALL COLORS SPECIFIED BY GDDM PJ08089: LOADING DOS HIGH IN VDM CAUSES MS OVERLAY LINKER TO FAIL WITH "PACK- ED FILE IS CORRUPT" MESSAGE PJ08100: PROBLEM WITH MLE WITH A STYLE OF WS VISIBLE | MLS WORDWRAP | MLS BORDER INITIALIZED WITH A STRING OF TEXT THAT HAS NO NEWLINE PJ08109: LESS SHARED MEMORY WHEN SWAPPER.DAT PUT IN DISK PARTITION HAVING BIG FREE SPACE. ALSO HANGS BOOT WHEN NOSWAP SET PJ08117: ON XGA SYSTEM, WHEN 2 DIALOG BOXES ARE DISPLAYED SINGLE CHAR.TXT STRINGS AND LONG LINES DISAPPEAR PJ08126: CANNOT SET VIDEO_MODE_RESTRICTION=MONO WITH SYSCREATEOBJECT USING REXX PROGRAM PJ08129: COLOR BITMAPS NOT DISPLAYED WHEN USING 8514/A DEVICE DRIVER PJ08136: CODEVIEW NOT ACCEPTING KEYSTROKES BUT MOUSE WORKS PJ08148: VIOCREATELOGFONT GIVES BLANK CHARACTERS ON VGA ON SERVICE PACK PJ08154: MIGRATE UTILITY PROBLEM: ADD-PROGRAMS LIST DOESN'T CONTAIN ALL EXECUTABLE PROGRAMS ON THE DRIVE SPECIFIED PJ08161: TRAP 000D IN BLANKSBEFOREDOT CALLED BY DOS_OPENCREATE PJ08182: DOSCREATESEM RETURNS HANDLE=0 IF DBCS CHARACTER IN NAME PJ08198: WINDOW GETTING FOCUS BEFORE AUTOLOCKUP GETS FOCUS IN SUBSEQUENT MANUAL LOCKUPS WHEN OTHER WINDOW HAS THE FOCUS BEFORE LOCKUP PJ08204: DDE BETWEEN 123G AND WORD FOR WINDOWS FAILS WHEN "DEVICE INDEPENDENT BITMAP/PASTE LINK" IS SELECTED IN WORD PJ08216: BACKUP IN A VMB FROM A NETWORK DRIVE USING DOS LAN REQ 2.0 NOT WORKING ONLY ONE FILE BACKED UP, OTHERS IGNORED PJ08218: FTADMIN LOSES 4G DRIVE AND ITS MIRROR PJ08221: APPLCATION PROGRAM HANG UP IF THE PROGRAM USES 2 OR MORE MLE'S AT THE SAME TIME PJ08230: CANNOT 'COPY ALL' INTO THE CLIPBOARD FROM A DOS FULL SCREEN SESSION PJ08239: WINSETPRESPARAM DOESN'T CHANGE FONTS ON A NOTEBOOK PAGE AND STATUS LINE PJ08245: DIR AFTER DISKCOPY SHOWS INCORRECT FREE SIZE FOR DRIVE B: PJ08253: READ/2 ENTERING NOTE GIVES SYS3175 OR HANGS ON PMMLE.DLL PJ08264: WINSETOBJECTDATA DOES NOT RETURN THE VALUE SET BY THE _WPSETUP METHOD PJ08276: HPFS SUPERBLOCK/SPAREBLOCK CORRUPTION DISCOVERED ON BOOT UP PJ08277: DEFAULT COLORS FOR MLE, HARD TO READ USING TSENG/TRIDENT WITH 256 COLOR DRIVERS PJ08281: EPM DOESN'T DISPLAY SPECIAL CHARACTERS WHEN USING THE ALT+<KEY> ON A 122 FRENCH KEYBOARD PJ08289: TASK DOES NOT APPEAR IN TASKLIST WHEN FCF_TASKLIST IS SET. PROGRAM DOES NOT MINIMIZE TO DESKTOP PJ08290: START CMD ADDS A PRECEDING SPACE TO SINGULAR ARGUMENTS PASSED TO A REXX PROGRAM PJ08295: INCORRECT MESSAGE DELETING FONT FROM FONT PALETTE 8590-ALF XGA OS/2 2.0 SERVICE PAK ES 1.0 LS 2.0 PJ08303: PSCRIPT.DRV OUPUT DOESN'T CONFORM TO ADOBE STRUCTURE STANDARDS PJ08320: IBM2SCSI.ADD DOES NOT RECOGNIZE DEVICE TYPES > 7F PJ08326: SYSLEVEL HANGS WHEN USING PCSUPPORT FOR OS2 PJ08336: WINSETPRESPARAM NOT WORKING FOR MLE BORDER COLOR PJ08350: METAFILES TRAP OS/2 PICTURE VIEWER AT 5B:1AD32FBF PJ08363: HYPERGRAPHIC LINK DOES NOT WORK WITH 'FIT' ATTRIBUTE PJ08377: PERFORMANCE ISSUE, 8514A & SVGA MACHINES SCALE FAST, XGA SLOW PJ08384: TRAP AT NP_SEM_SIG+2 DURING NAMED PIPE WRITE PJ08392: LOADING DEVICE DRIVER CAUSES TRAP 000E ON A 486 SYSTEM WHEN CODE SEGMENT EXCEEDS 800HEX, BUT LOADS FINE ON A 386 MACHINE PJ08394: PM DOESN'T RESTORE WINDOWS TO THEIR ORIGINAL POSITION PJ08406: HELP FILE SCREEN REPAINT PROBLEM WITH FILE HYPERLINKED AND CTRLID 'BACKWARD FORWARD' USED PJ08409: VALUE LIMITS ARE EXCEEDED USING POSTSCRIPT DRIVERS AND TOOLKIT FOR OS2 2.0 AND 2.1 PJ08412: LOST SYSTEM SEMAPHORE NAME PJ08419: GPISETLINEWIDTH INCORRECT. PARAMETER 1 AND 2 BOTH IS SAME SIZE PJ08422: TRAP 000E CAUSED BY AN OS2KRNL DATA STRUCTURE NOT BEING INITIALIZED THUS CAUSING INTERMITTENT FAILURES UNDER HEAVY LOAD CONDITIONS PJ08423: MLE REPAINTS INCORRECTLY AFTER INSERTING <CR> PJ08424: PM TERMINAL(SOFTERM) DOES NOT APPEAR TO POSITION THE CURSOR CORRECT- LY WHEN CONNECTED VIA A VT100 (VT102) EMULATION PJ08427: HIGH STRESS COPIES IN HPFS CAUSES MULTI-SECTOR MISCOMPARES PJ08430: PM TERMINAL (SOFTERM) INCORRECTLY UPDATES THE SCREEN POSITION WHEN USING VT100 EMULATION AND SPLITTING LINES IN DEC EDITOR PJ08434: LOCKUP PASSWORD DISPLAYS IN COMMAND PROMPT SESSION PJ08436: 16MB MACHINE WITH NOSWAP SHOWS 7MB FREE, BUT RUNS OUT OF MEMORY PJ08457: COMBO BOX DISPLAY DRAWN INCORRECTLY WHEN USING 7.COURIER FONT PJ08459: OCCASIONAL NEGATIVE VALUES FOR THD.TMFAULT PJ08463: DOSSUBSETMEM GROW FUNCTION FAILS WHEN PRIOR ALLOCATIONS = MAXIMUM AMOUNT OF MEMORY IN POOL PJ08466: LONG PATH NAMES CAUSE WORKPLACE SHELL TO ABEND PJ08470: KLONDIKE SCORES UP TO +32767 THEN FLIPS TO -32767 AND COUNTS NEGAT- IVELY UP TO ZERO. SCORE IS A SHORT AND SHOULD BE LONG PJ08472: METAFILE PRINTED ON EPSON PRINTER MISSING DETAILS PJ08476: SYS3175 IN DOSISIGDISPATCH WHEN DOSCWAIT IS INVOKED PJ08483: COLOR SCHEME PALETTE DOES NOT HANDLE MENU BACKGROUND COLOR CORRECTLY PJ08484: NMAKE'S EXTMAKE FAILS WITH DEPENDENT PATHS PJ08490: SYS3175 ON DOSEXITLIST PROCESSING BETA/BORG, 2.0, SERVICE PACK, AND 2.1 SYSTEMS PJ08496: DIRTY SHUTDOWN ON HPFS386 VOLUME CORRUPTS DISPLAY ON BOOT IN XGA MODE ON 8515 WITH XGA-2 CARD PJ08507: ONLY SHADOWS FOUND WHEN DOING A FIND PJ08512: MVGA DRV V2.0 UNDER SP USING GPICREATEBITMAP ACC VIO PMGRE.DLL PJ08513: FONT ATTRIBUTE PROBLEMS UNDER CUSTOMIZATION PJ08516: DYNAMIC SORT CAPABILITY OF OBJECTS WITHIN FOLDERS LOST UNDER USER CUSTOMIZATION PJ08517: TRAPS OCCURRING IN PMWIN.DLL WHILE RUNNING IPMD PJ08527: ENTRIES ARE BEING LEFT IN THE SFT AFTER A PROCESS HAS ENDED AFTER A WHILE, NO MORE FILES CAN BE OPENED PJ08528: HELP FILES NOT FOUND IF INVALID NETWORK DRIVE IN HELP= PATH PJ08534: ISSUING WINSETHOOK WITH HK_MSGFILTER ALWAYS RECEIVES MSGF_DIALOGBOX MESSAGE PJ08556: TRAP 000E USING BACK/FORWARD FROM SEARCH RESULTS LIST PJ08557: PICVIEW BEEPS WHEN VIEWING A NETWORK DIRECTORY PREVENTING USER ACCESS TO FILE LISTS WHEN USING FILE-OPEN PJ08562: WHEN DISPLAYING FOUND TEXT IN PMSEEK, IF THE FIRST OUTPUT TEXT EXCEEDS THE MAX LINE LENGTH, THE REMAINING OUTPUT IS CORRUPTED PJ08585: ON HPFS, CREATE FILE W/NAME STARTING WITH THE DOT (.), THEN DO AN ATTRIB ON THIS, WHICH RETURNS SYS0002 CAN'T FIND FILE PJ08586: _WPSCANSETUPSTRING DOESN'T PARSE (CARET) CORRECTLY PJ08599: OS/2 WINDOW WHEN STARTED MINIMIZED IGNORES THE WINDOW SETTINGS HIDDEN/MINIMIZED WINDOW VIEWER/DESKTOP PJ08601: EXTENDED KBD NOT SUPPORTED IN CP 852,850 PJ08602: DISKCOMP DOES NOT FIND DIFFERENCES IN 2 DIFFERENT DISKS AT SECTOR 65659 PJ08606: MASS DUPLICATION OF TEMPLATE OBJECTS PJ08616: PMGPI TAKES COORDINATES IN LONG FORMAT BUT SHOULD BE SHORT PJ08622: CONTEXT MENU IN WINDOW LIST IS NOT RECOGNIZING THE INABILITY TO CLOSE COMM MANAGER'S 3270 PRINT CONTROL PJ08628: HELP OPTION DISPLAYS EVEN AFTER DISABLED. CLOSE AND DELETE OPTIONS APPEAR ON THE OBJECT SETTINGS EVEN WHEN DISABLED PJ08632: DOSQUERYFSINFO RETURNS 0 WITH UNFORMATTED DRIVE PJ08649: PRFREMOVEPROGRAM() DOES NOT DELETE LAST ICON PJ08658: UNDOCUMENTED RESTRICTION IN CONFIG.SYS PJ08659: FLOATING POINT EMULATOR FAILS TO HANDLE FBCD INSTRUCTION IN LOTUS 123G PJ08679: KEYBOARD CONTROLLER NOT WORKING ACCORDING TO SPEC. AND HANGS OS/2 2.0 ON PCM ATTEMPTING TO CHANGE THE KEYBOARD NUM LOCK LIGHT PJ08680: SYS 1477 IN PM APPLICATION USING WINSENDMSG(). SWAPPER.DAT GROWS WITHOUT BOUNDS PJ08682: HPFS HOTFIX STOPS SERVER PROCESSING WITH POPUP PJ08693: RUNNING FDISK FROM THE COMMAND LINE RETURNS A ZERO WHEN THE COMMAND IS SUCCESSFUL OR UNSUCCESSFUL PJ08694: CONTENTS OF A DRIVES FOLDER CANNOT BE SORTED IN TREE VIEW. PJ08700: HOLDING CONTROL KEY, DRAGDROP A FOLDER FROM CD ROM TO HARD DRIVE GIVES AN ERROR IF THERE IS NOT ENOUGH SPACE ON THE HARD DRIVE PJ08702: CANNOT RECOVER FROM PRINTER POP-UP ERROR USING LATEST EXOS2.DLL, BVHXGA.DLL, AND IBMXGA32.DLL PJ08713: IBM42XX DRIVER FORM FEEDS AFTER 16,000+ LINES PJ08727: OVERLAYED MESSAGE BOXES WHEN SHUTTING DOWN IN 2.1 PJ08728: TRAP 000D CS:EIP 08F0:00001406 CSLIM 0000299F REV. 6.514 IN COM.SYS WHEN PROTECTONLY=YES OR NO DOS (VDM) SUPPORT LOADED PJ08730: OS/2 V2.1 WOULD NOT INSTALL ON PS/2 8580-071 PJ08733: DOSSETPATHINFO RETURNS RC = 87 WITH HPFS DIRECTORY NAME PJ08734: AMIPRO 2.0 RECEIVING GP FAULT/3.0 RECEIVING PAGE FAULT PJ08735: IPFC :LP. TAG DOES SET LEFT MARGIN CORRECTLY PJ08736: HPIIISI AND HPIIIP LOOSES PRINTER SETTINGS PJ08738: DUAL DISPLAY - WINOS2 APPS GETTING SCRAMBLED PJ08739: ANSI ESC SEQUENCE NOT WORKING IF DOS_HIGH ON IN ANSI.SYS PJ08743: NET RUN COMMAND FAILS WITH NET3502 ERROR MESSAGE PJ08744: COMBO BOX BEHAVIOR CHANGES UPON USING WINSETPRESPARAM TO CHANGE THE FONTS BACK TO DEFAULT PJ08745: TRAP WHEN WIN-OS/2 FULL-SCREEN SESSION BROUGHT INTO FOREGROUND ON AMBRA SYSTEMS CONFIGURED IN SVGA MODE PJ08750: SYS3175 - TRAP IN PMWIN.DLL AT 1A23A8F1 WHEN CUSTOMER CREATED FORM OVERLAY BY USING OVERLAY GENERATOR, PJ08751: SEAMLESS WINOS2 APPLICATIONS RESTORE TO AN INACCESSIBLE TRANSPARENT STATE ON THE WORKPLACE SHELL PJ08752: TRAP IN HELPMGR.DLL WINCREATEHELPINSTANCE D1E7:0000011F PJ08763: ANY PROGRAM ICON LOSES CUSTOM ICON' AFTER UPDATING SETTINGS IN OS/2 2.1 PJ08764: FOREGROUND FAMILY TRAPS WHILE LOADING TOP SGCB FULL-POINTER PJ08766: KEYBOARD DOESN'T TRAP WHEN CONTAINER CONTROL IS DISABLED PJ08775: DLGEDIT.EXE RETURNS OUT OF MEMORY ERROR WITH LARGE INCLUDE FILES PJ08777: IF AN EXTRA PARAMETER IS ADDED IN THE DOS_VERSION SETTINGS A TRAP 000E OCCURS PJ08779: QUICK INVOICE CAUSES OVERFLOW. WORKED IN 2.0 PJ08783: XGA-2: SCREEN OUT OF SYNC WHEN ALT_ESC FROM WINOS/2 TOO EARLY PJ08784: SOFTWARE CAROUSEL RUNNING ON A 486/SX RETURNS A SYS2237 ERROR WHEN RUNNING UNDER OS/2 V 2.0, SERVICEPAK AND 2.1 PJ08791: MORE THAN 32K CHARACTERS IN MLE HANGS THE SYSTEM PJ08805: MACHINE WITH 17MB RAM DOES NOT INSTALL OS/2 PJ08806: HAVING A FOLDER WITH 'WORK AREA' ON AND IN DETAILS VIEW TAKES A LONG TIME TO CLOSE PJ08807: ADVANCED POWER MANAGEMENT DOES NOT WORK ON LAPTOPS THAT SUPPORT 32 BITS APM INTERFACE, BUT NOT THE 16 BITS INTERFACE PJ08808: GRAY SCREEN & HOURGLASS ON FIRST BOOT PJ08809: GARBAGE SHOWN IN POWER ICON OF SOME LAPTOPS PJ08816: PROGRAM OBJECT'S PARAMETER PROMPT MESSAGE CHANGES IF LOGGED ON TO A LAN PJ08819: CUSTOM OS2/1.3 DOES NOT WORK WITH OS2/2.0+ SAVING META FILES PJ08822: TRAP 000D IN HELPMGR WHEN USING A 16-BIT DLL FOR IPF COMMUNICATIONS OBJECT PJ08829: REGRESSION - ICONS REMAIN HATCHED AFTER APPLICATIONS ARE CLOSED (IF REGRESSIONS APPEAR AFTER APPLYING FIX, REMAKE INI FILES) PJ08832: RESTORE USING /S COMBINED WITH /A /B /E OR /L RETURNS ALL FILES, NOT JUST THOSE MATCHING TIME OR DATE CRITERIA PJ08835: MAKEINI FAILS WITH AN RC FILE GREATER THAN 500KB PJ08837: LOTUS 2.4 FILE RESERVATIONS NOT WORKING UNDER OS/2 V 2.1 & SERVICE PACK # 1. INT 21 FUNCTION 440A FAILING DOSAPAPAR PJ08840: DIALOG EDITOR "ARRANGE - ORDER GROUPS" - CANNOT MOVE ITEM TO END OF LIST PJ08843: UPON BOOTUP SOME FOLDERS ARE HASHED AS IF OPEN AND THEY APPEAR IN THE WINDOW LIST, BUT THEY DO NOT SHOW UP ON THE DESKTOP OR THE MINIMIZED WINDOW VIEWER PJ08851: A FOCUS CHANGE OF OVERLAPPING WINDOWS IN VISUAL BASIC CAUSES AN INCOMPLETE REPAINT OF THE WINDOW CONTENTS PJ08854: BUTTON MAPPINGS INCORRECT FOR 3-BUTTON MICE WHEN USED AS LEFT HANDED MOUSE PJ08861: SYS3175 PRINTING FROM TIME AND PLACE TO A PSCRIPT PRINTER IN OS/2 2.1 PJ08864: HELP FROM MINIMIZED VIEW OF WINOS2 DOES NOT WORK PJ08865: OS/2 2.1 FORMAT TAKES 3XS AS LONG TO FORMAT THE OPTICAL DRIVE PJ08870: OS/2 2.1 OS2 API GPIBITBLT LEAVING GARBAGE ON THE SCREEN DESCRIBE V4.0 HAS THIS PROBLEM AND REPORTED THE PROBLEM PJ08875: 5.25" DRIVE A WITH 3.5"(B:) OS/2 DISKETTES WILL NOT INSTALL PJ08877: IBM4207 X24E(IBM42XX.DRV) USES CODE PAGE 850 TO PRINT INSTEAD OF 437 PJ08878: SYS0039 LOOP WHEN EXECUTED DOS APPLICATION FROM DRIVE A: OR B: FROM WITHIN WINOS2 PROGRAM MANAGER PJ08879: AUTO-LOCKUP AND SHFT-F8 ON THE DESKTOP CAUSE UNEXPECTED LOCKUPS PJ08880: USING GPI MARKER IN XOR MODE DRAWS THE '+' INCORRECTLY AND SQUARE LEAVES MARKS BEHIND ON ALL SVGA CHIP SETS PJ08883: ON L40 WITH AN EXTERNAL MONITOR, THE FULLSCREEN DOS SESSION IS SHIFTED UP ABOUT THREE OR FOUR LINES PJ08885: MOVING AN OBJECT INSERTED WITH WPCNRINSERTOBJECT CAUSES ONE OF THE WPS THREADS TO GO INTO AN INFINITE LOOP PJ08888: 8K MEMORY LEAK IN PMGRE ON CLOSEDC AND RESTOREDC IN SERVICEPAK PJ08891: ICON EDITOR LOCKS UNTIL CTRL-ESC KEYS ARE PRESSED PJ08893: FONT SELECTION DOES NOT GET APPLIED PJ08895: WINOS2 PRINTER DRIVERS ARE NOT MIGRATED WHEN UPGRADING TO OS/2 2.1 PJ08899: XGA-2 FONTS ARE INCORRECT IN OS/2 2.1 PJ08900: MULTIPLE INSTANCES OF WORD FOR WINDOWS INCORRECTLY STARTED PJ08902: LAN MESSAGE HANGS SYSTEM IN OS/2 2.1 PJ08904: WINSHELD CAUSED A GP FAULT IN MODULE USER.EXE AT 000A:2D2A PJ08909: MOUSE FAILS ON RESUME FROM POWER DOWN ON IBM THINKPAD 700C PJ08910: ABSOLUTE DEVICES WON'T UPDATE IDC QUERY FUNCTION -SPECIAL NEEDS SUPPORT BROKEN IN TERMS OF POINTING (8516 TOUCH SCR OR PENPM) PJ08912: SEAMLESS APPLICATIONS LEAVE INVISIBLE WINDOW IF MINIMIZED TO DESKTOP PJ08914: SYSTEM PROPORTIONAL FONT SET DOES NOT REMAIN IN NORMAL STYLE, ALWAYS RETURNS TO BOLD STYLE PJ08915: ERRONEOUS ERROR MESSAGE ISSUED BY WORKPLACE SHELL IF ICON TEXT EXCEEDS ALLOWABLE LIMIT PJ08916: MOUSE LOST ON REBOOT AFTER INSTALL OF 2.1, DUE TO INSTALL OF OTHER SYSTEM MOUSE DRIVER INTO C:\OS2 PJ08917: CLASSES ARE HARD-CODED TO PRINT OBJECT NAMES PJ08919: CROSS-HASHES ARE NOT MAINTAINING COLOR PJ08922: TRAP 000E AT 0148 : 00007D13 -- SYSSERVVDM + 0X4B DUE TO RETURN CODE FROM SYSSERVWAITQ NOT BEING CHECKED IN SYSSERVVDM PJ08923: WORDPERFECT 5.0 GIVES "INSUFFICIENT MEMORY FOR WP FILE HANDLE" MSG WHEN STARTING APP IN OS/2 2.1 GA PJ08938: RELAY GOLD FOR WINDOWS VERSION 5.0C GP FAULT ON STARTUP PJ08940: WINOS2 SEAMLESS POP-UP DIALOG BOX FOR AN APPLICATION GP FAULT IS INCORRECT. MESSAGE REFERENCES BUTTONS WHICH ARE NOT DISPLAYED PJ08941: WHEN CA_ORDEREDTARGETEMPH IS REFERENCED IT DOESN'T UNPAINT SOURCE EMPHASIS PJ08943: IPF PRINTS BLANK PAGE FOR HEADINGS WITH "NOPRINT" ATTRIBUTE PJ08947: CREATEDD DOESN'T PROCEED UNDER 2.1 -- CAN'T TAKE DUMP PJ08950: RESTORE RETURNING INTERNAL ERROR WITH A LARGE BACKUP DATA SET PJ08951: SYSTEM DUMP HANGS ON UNFORMATTED DISKETTE PJ08958: FAXWORKS/2 (PMFAX) APPEARS NOT TO RELEASE THE SERIAL PORT AFTER TERMINATION. SYS1798 ERROR. PROBLEM IS IN COM.SYS / VCOM.SYS PJ08963: FIND DOES NOT FIND OBJECTS IF THEY CONTAIN A / (FORWARD SLASH) PJ08966: VDMA.SYS RETURNING INCORRECT VERSION NUMBER TO DEVICE DRIVERS THAT QUERY ITS VERSION # UNDER WINOS2. SHOULD RETURN 2.0 PJ08967: CLIENT WINDOW DOESN'T GENERATE CONTEXT MENU ON SHIFT-F10 PJ08968: IF OS2 2.1 RESPONSE FILE HAS FORMAT PARTITION=1 THEN USEREXIT= CMD.EXE WILL NOT WORK PJ08980: THE ENHANCED EDITOR IS NOT CLEANING UP THE FRAME CONTROLS MENU PJ08983: PROBLEM WITH LISTBOX TAKING 3-5 MINUTES TO LOAD ENTRIES PJ08987: SMALL PRINT SCREEN WITH HP PAINTJET DRIVER (SMGXPJET.DRV) PJ08988: FOLDER NOT REPAINTED CORRECTLY AFTER MOVING AN OBJECT FROM IT PJ08989: SOME SYSTEMS WITH MMPM/2 HANG AT BOOTUP PJ08991: HARD ERRORS ARE NOT PROCESSED PROPERLY WHILE DISPLAYING A DISK PJ08996: IPE AT 0160 : FFFA4364 - 000D : 0004E364 LINE 1125 FILE 7023 PJ08998: SOME OF THE SVGA & 8514 FONTS FOR WIN-OS2 DOES NOT GET INSTALLED IN OS/2 2.1 PJ09002: TRUETYPE FONTS AND PRINTING ON HP LASERJET OR 4019 PJ09004: JOBS DISAPPEARING FROM PRINT QUEUE WHEN USING PRINTER-SPECIFIC AND 32-BIT POSTSCRIPT DRIVER PJ09005: OS/2 2.1 RESPONSE FILE INSTALL WITH WIN-OS/2DESKTOP=2 IS NOT PRESERVING ALL PROGRAM & PRINTER OBJECTS ON THE WIN-OS/2 DESKTOP PJ09010: MINIMIZED WINDOW VIEWER (MWV) IS NOT DISPLAYING ICONS PROPERLY IN 3270 OR 5250 EMULATOR SESSIONS PJ09012: SEMAINT HALTS CID INSTALL WITH CDROM DRIVE AND NO CD IN DRIVE PJ09013: MMSYSTEM.DLL OMITTED FROM SYSTEM.INI DURING OS/2 2.1 INSTALL PJ09017: SHUTDOWN HANGS WITH "PLEASE WAIT SHUTDOWN IN PROGRESS" & CHKDSK *RUNS* AT REBOOT TIME (AFTER SHUTDOWN) EVEN IF ALL APPLICATIONS CLOSED PJ09026: UNABLE TO TAKE DUMP IN 2.1. C/A/NL-NL DOESN'T DO ANYTHING PJ09027: COPYING DRIVES ICON CAUSES SHADOWS OF THE DRIVES TO BE CREATED BUT THEY CANNOT BE ERASED PJ09029: PMCHKDSK TRAPS WITH SYS3175 WHEN STARTED FROM COMMAND LINE WITHOUT ARGUMENT LOC. CS:EIP = F:27BA PJ09034: RE- PAINT / FOCUS PROBLEM, WITH SEAMLESS WINDOWS OPEN AND SWITCHING FROM WINDOW LIST TO ANY OTHER WINDOW PJ09036: AFTER RUNNING RSPINST OS/2 HANGS AFTER THE COMPUTER REBOOTS, THE CONFIG.SYS DOES NOT PROCESS PJ09037: OS/2 V2.1 RESPONSE FILE INSTALLATION TRAPES (TRAPE000D) IF THE RESPONSE FILE HAS CDROM=1 (CDROM AUTODETECT). ( OS2INSTL INSTL ) PJ09045: PMPRINT IS MISSING DATA WHEN OUTPUT IS SENT TO A PLOTTER PJ09048: MOD 9595 ONLY DUMPS FIRST 16MB OF MEMORY PJ09050: DOS APPS LIKE DOSKEY, LOTUS, ETC. PULSE SHOWS 100% CPU UTILIZATION EVEN THOUGH APPLICATION IS DOING NOTHING PJ09052: DUAL MONITOR SUPPORT FAILS WITH BORLAND WINDOW DEBUGGER PJ09054: 32K MEMORY LEAK EVERY TIME AN WIN-OS2 SESSION IS STARTED PJ09065: OS/2 2.1 ICON EDITOR GENERATED ICONS ARE NOT HANDLED PROPERLY BY SYSSETOBJECTDATA 'C' FUNCTION PJ09067: SSF_CONTROL_INVISIBLE FLAG TO DOSSTARTSESSION IGNORED AFTER SHFT_MAXIMIZE ON OS/2 COMMAND WINDOW PJ09068: MINIMIZE BUTTON IN SETTINGS FOR OS2 WINDOW SESSIONS DO NOT MINIMIZE VIEWS WHEN CHECKED PJ09069: INSTALLING 2.1 ON SYSTEM WITH 2 MONITOR ASKS FOR "BAD" DISK WITH CARROT SYMBOL AFTER DISPLAY DISK#1 PJ09076: WHEN DOING A RESPONSE FILE INSTL MIGRATEDATABASE DOES NOT WORK WHEN YOU DO NOT USE THE DEFAULT DATABASE NAME PJ09080: MLE CAUSES SCREEN TO REPAINT TOO OFTEN PJ09081: RING 0 TRAP REGISTERS NOT DISPLAYED PJ09082: WINOS2 IN VMB WILL GIVE CAN'T FIND FILES WITH MANY APPS OPEN PJ09085: TRAP000E CS:EIP= 0160 : FFFAAAE5 6.514 ON ISA/EISA BUS MACHINES WITH PARAMETERS PASSED TO COM.SYS. MKBCMAPAR PJ09086: LM_QUERYSELECTION RETURNS BAD VALUE IN DROP DOWN LIST PJ09088: OS2 2.1 OVER OS2 1.3EE FAILS WITH RESPONSE FILE INSTALL PJ09092: OS/2 HUNG-UP WITH DISKETTE ACCESS FROM DOS SESSION PJ09093: IN HPFS, COPY A FILE TO "..TEST", DIR SHOWS 2 ENTRIES PJ09094: CUSTOMERS APPLICATION TRAPS AND THEN LOCKS UP THE DESKTOP PJ09095: ISA MACHINES WITH >16 MB MEMORY NOT RECOGNIZED PJ09096: OS/2 2.0 HAS DIFFICULTY BOOTING DOS IMAGES PJ09097: NETWORK RESOURCES LOST,SYSTEM WILL GP FAULT ON NOVELL PJ09100: OBJECT RENAME FROM GENERAL PAGE OF SETTINGS IS IGNORED IF ALT-F4 IS PRESSED PJ09105: CTRL-SHIFT-ESC FROM WINDOW LIST MINIMIZES SELECTED ITEMS, EVEN THE DESKTOP ITSELF PJ09109: DELETING A PRINTER OBJECT WITH A JOB IN THE QUEUE DOES NOT COMPLETELY UPDATE THE INI FILES PJ09118: IBM CD ROM ON SERVER GIVES SYS0066 ON REQUESTER WHEN TRYING TO ACCESS A DOS APPLICATION PJ09121: IF SESMGR CANNOT FIND A POINTER TO AN ENTRY IN THE SWITCH LIST FOR THE CURRENT SESSION, A TRAPD OCCURS IN DOSSMSWITCH PJ09122: IPE 7028 236 VDMTIME:VDHARMTIMERHOOK 6.514 0160 : FFF74A87 INT REVISION 6.514 PJ09138: PAGE MANAGER CORRUPTS PAGE TABLE LINKED LIST PJ09148: OS/2 V2.1 RESPONSE FILE KEYWORD "EARLYUSEREXIT" WILL NOT GET EXECUTED AFTER AN FDISK IS DONE PJ09150: MEMORY LEAKAGE WHEN CHANGING BITMAPS USING DESKTOP SETTINGS PJ09156: DLL'S MTE FREED BEFORE TERMINATION ROUTINE CALLED PJ09163: SWAPPER SIZE > 100M WILL CAUSE AN IPE ON SUBSEQUENT GROWTH PJ09164: SEAMLESS WINAP ICON IS CLICKED ON, IT HATCHES BUT APP NEVER STARTS AND ICON STAYS HATCHED,ON SHUTDOWN/REBOOT THE APP STARTS PJ09165: LOCATION OF MOUSE POINTER AFFECTS DIALOG BOX "MODALNESS" IF F1 IS PRESSED PJ09169: BACKGROUND BITMAP OF A FOLDER IS NOT DISPLAYED IF IT IS CLOSED FROM WINDOW LIST PJ09170: STACK OVERFLOW WITH DIR /S COMMAND PJ09171: FDISK.COM ONLY ALLOWS 4 DIGITS (SIZE <= 9999) WHEN ENTERING PARTITION SIZE PJ09173: SUBCLASS OF WPFOLDER OR WPDATAFILE CANNOT BE RECOGNIZED BY WPSHL IF THE VENDOR'S APPLICATION IS NOT INSTALLED PJ09177: 'RESTORE' DELETED FROM SYSTEM MENU WHEN MINIMIZED TO THE MINIMIZED WINDOW VIEWER PJ09179: ICONS OVERLAY IN FOLDER AS THEY ARE CREATED PJ09184: ERROR 288 FROM DOSRELEASEMUTEXSEM: OTHER PROBLEMS ARE WITH DOS APPLICATIONS RUNNING ON PENTIUM MACHINES. SEE PJ10641 PJ09186: SYSTEM CLOCK BORDER WIDTH NOT SAVED PJ09187: CODING SUPPRESSPOPUPS IN CONFIG.SYS MAY CAUSE THE SYSTEM TO HANG PJ09189: OS2DASD.DMD NOT ALLOWING ACCESS TO ALL SECTORS OF THE DISK. WHEN THE DISK IS 1 HPFS PARTITION, CHKDSK MAY YIELD SYS0551 ERRORS PJ09190: IPF LEFT MARGIN IS INCORRECT WITHIN AND FOLLOWING LISTS PJ09191: TRAP 000E AT 160:FFF5FC82 RUNNING A VDM PJ09192: VIDEO_MODE_RESTRICTION = CGA IN DOS SETTINGS NOT WORKING PJ09193: INCORRECT BATCH FILE STARTED WHEN SEVERAL ARE IN THE STARTUP FOLDER PJ09194: POSTSCRIPT DRIVER LOOSES FONTS PJ09201: PM TERMINAL AND OTHER APPLICATIONS HANG DESKTOP. CTRL-ESC CLEARS THE HANG - MESSAGE PROCESSING CONTINUES PJ09202: COPYING FILES VIA DRAG AND DROP WILL NOT PREFORM PROPERLY IF DISK BECOMES FULL BEFORE ALL FILES ARE COPIED PJ09207: WINOS2 SESSION HANGS WHEN CREATIVE LABS SOUND BLASTER PRO MIDI DRIVERS ARE LOADED, AND A MIDI FILE IS PLAYED PJ09208: WINSETPRESPARAM DOSEN'T CHANGE BACKGROUND AND FOREGROUND COLORS PJ09209: ET4000 VIDEO CARDS DO NOT CLEAN UP THE SELECTED FOLDER DOTTED LINE WHEN IN 640X480 C256 OR 800X600 C256 MODE PJ09213: IPFC LIST FORMATTING IS NOT COMPATIBLE BOOKMASTER LISTS PJ09215: DOSPEEKNMPIPE RETURNS STATE=4 DURING 1ST DOSCALLNMPIPE PJ09216: WLO APPLICATION CAUSES MEMORY ERROR DURING CUT/COPY PJ09218: OS/2 V2.1 SEDISK.EXE DOES NOT WORK PROPERLY IF THE OS/2 SOURCE IS ON A CDROM PJ09219: FIVE (5) SECOND DELAY BEFORE PROMPT APPEARS WHEN TERMINATING DOS APPLICATIONS THAT DIRECTLY ACCESS THE PARALLEL PORT HARDWARE PJ09228: IBM4019 PPDS DRIVER IS CAUSING AN EXTRA PRINTOUT ON THE BOTTOM LEFT CORNER OF THE PAGE WHEN PRINTING FROM TIME AND PLACE/2 PJ09231: STANDALONE DUMP DURING OS/2 BOOT UP CAUSES TRAP 000D PJ09239: EXCEL VERTICAL GRID LINES DISAPPEAR PJ09240: ATTEMPTING TO DEBUG PMSHELL.EXE USING IPMD OR SD386 GENERATES TRAPS PJ09241: VIRTUAL PARALLEL PORT DEVICE DRIVER (VLPT) TRAPS ACCESS OF DOS APPLICATIONS THAT PROGRAMS THE PARALLEL PORT HARDWARE DIRECTLY PJ09243 APEX2 RAN IN 1024X768X256 MODE OR XGA CAUSE SCREEN CORRUPTION PJ09246: NEGATIVE ERROR LEVEL CHECKING FROM DOS BATCH FILES GIVES SYNTAX ERRORS WITH OS/2 2.1 PJ09250: WINAPS REPORT "WRONG DOS VERSION" REGARDLESS OF THE VERSION VALUE GIVEN IN THE SETTING PJ09251: POSTSCRIPT DRIVER FAILING WHEN PRINTING MORE THAN 64000 ARC COORDINAT- ES PJ09252: CHANGING THE VIEWMATRIX CAUSES COSMETIC LINES TO BE CHANGED WHEN USING THE POSTSCRIPT DRIVER PJ09258: WPSHELL LOCKUP: MULTIPLE DIALOGS FOR INITIAL PASSWORD TRAPS PJ09264: SETTING TIME ON ISA BUS MACHINE SLOWS TIMER TICKS TO TIME CRITICAL TASK PJ09265: BSESUB.H, PRAGMA PACK(2) SET BUT NEVER RESET PJ09267: DEFAULT TYPE FOR ICON, BITMAP, AND POINTER OBJECTS IS INCORRECT IN OS2 2.1 GA PJ09268: NETWORK PRINTER SETTINGS NOTEBOOK IS NOT DISPLAYED ON THE SCREEN EVEN THOUGH IT SHOWS AS OPENED IN THE WINDOW LIST PJ09272: CANNOT CORRECTLY CHANGE THE COSMETIC LINE WIDTH WITH THE POSTSCRIPT PRINTER DRIVER PJ09273: IF LENGTH OF PATH/FILENAME + PARAMETERS FOR A WINOS2 PROGRAM EXCEEDS 80 BYTES, OS/2 CANNOT FIND PROGRAM PJ09275: FOR A REQUEST PACKET WITH A SECTOR COUNT >= 80H (64K) THE DASD MANAGER GENERATES A S/G LIST ENTRY WITH A BYTE COUNT OF 0 RATHER THEN 10000H. PJ09279: REGR-ICONS UNHATCH WHILE PROGRAMS ARE OPEN/MINIMIZED. APPS CAN THEN BE FOUND IN TASK LIST TO GIVE FOCUS AND RESUME PJ09280: SETTINGS BOOK, GENERAL PAGE DEFAULT AND UNDO BUTTONS DO NOT FUNCTION PROPERLY ΓòÉΓòÉΓòÉ 4.11. Summary of APARs fixed in Service Pak XR06200 Part 2 ΓòÉΓòÉΓòÉ Summary of APARs fixed in Service Pak XR06200 Part 2 PJ09293: RICOH SCANNER AND FUTURE DOMAIN FD16-700.ADD, FD8XX.ADD, AND FD7000EX.ADD DRIVERS PJ09294: COM.SYS NOT BEHAVING CORRECTLY WITH RTS=TOG. WHEN READING FROM THE SERIAL PORT, COM.SYS IS RAISING RTS. THIS IS INCORRECT PJ09297: XGA DRIVER CANNOT LOAD CUSTOM FORMATTED BITMAP PJ09299: HIGH ACTIVITY IN WINOS2 EXCEL WINDOWS RESULTS IN SYS3171 CS:EIP 157:5156 CSLIM B17F PJ09300: LANTASTIC PEER TO PEER NETWORK FAILS IN VMB WITH A SYS3176 ERROR PJ09305: PRINTER JOB PROPERTIES ARE LOST AFTER INSTALLING 2..1 OVER 2.0 PJ09313: DRAG & DROP A SCHEME FROM SCHEME PALETTE SETS WRONG SCREEN BACK- GROUND COLOR IF THE BACKGROUND TYPE IS AN IMAGE PJ09314: LASERJET DRIVER IS CAUSING AN EXTRA PRINTOUT ON THE BOTTOM LEFT CORNER OF THE PAGE WHEN PRINTING FROM TIME AND PLACE/2 PJ09315: IF 2 SESSIONS OF PC/FOCUS ARE STARTED THE SYSTEM WILL IPE IN _TKDECLAREINVERSION() PJ09316: ICONEDIT.EXE DOES NOT HANDLE 2.0 FORMAT FILES CORRECTLY PJ09318: RC COMPILER ERRORS WHEN PARSING ICON STATEMENTS PJ09319: ICON EDITOR HANGS IF LARGE INVERSE AREA IS ATTEMPTED TO BE COLOR FILLED PJ09321: COMPATIBILITY BETWEEN CSET++ AND LINK386 WHEN LOADING SYMBOLS PJ09323: WINOS/2 POSTSCRIPT IS NOT PROPERLY ROTATING THE PAGE PJ09324: DOSSLEEP() SAYS TO USE INCORRECT #DEFINE PJ09328: HELPMGR SYS3175 AT 5B:1A3A1CF5 OR 5B:1A3A26CC WHEN CLOSING HELP PANEL OR BOOK PJ09330: COPY COMMAND NOT MAKING BACKUP FILES CORRECTLY FROM OS/2 VDM PJ09344: TRAP D IN CALL TO FAR32RECEIVEMESSAGE, INCORRECT SELECTOR PRIVILEGE LEVEL PJ09348: KWIKINF SUPPLIED WITH CSET++ GA DOES NOT RUN UNDER 2.1 PJ09357: TRAP AT 0160 : FFF7809F IN 6.514 KERNEL WHEN STARTING A TIMER WITH INVALID HTIMER POINTER PJ09363: VIOCREATELOGFONT GIVES BLANK CHARACTERS ON 8514 PJ09364: VIOCREATELOGFONT GIVES BLANK CHARACTERS ON SVGA PJ09367: INSTALL W/CD-ROM ASKS FOR INSERTION OF CD-ROM EVEN IF CD-ROM IS INSERTED FD16-700.ADD NEC CDR 25 /!SN PJ09369: MINIMIZED WINDOW VIEWER DOESN'T REPAINT CORRECTLY PJ09370: TRAP 000D ON DISK 1 OS/2 2.1 OEM M/C CS:EIP=160:FFF58086 PJ09372: CA-REALIA,COBOL LANG. APP GETS SYS3176 ON ISA BUS PCS PJ09373: ICONS ARE NOT REFRESHED WHILE VIEWING WITH 'DRIVE A' OBJECT PJ09374: GPIOPENSEGMENT() PMERR_INSUFFICIENT_MEMORY X203E PJ09375: AUTOCAD 12 FOR WINDOWS ZOOM FAILS IN XGA PJ09384: CODE PAGE INCOMPATIBILITY PSCRIPT DRIVER UNDER OS/2 2.1 PJ09389: BORLAND C++ V1.0, WORKSHOP CREATES A SYS3175 ERROR IN 8514 MODE PJ09392: TRAP E IN PMWP.DLL IN OBJ_WPDELFROMOBJUSELIST() ROUTINE PJ09394: COPYING LARGE FILES TO THE PARALLEL PORT DEVICE DRIVER (PRINT02) WITH THE SPOOLER DISABLED CAUSES DATA CORRUPTION ON PRINTER PJ09399: RESPONSE FILE INSTALLATION OF OS/2 V2.1 SOMETIMES PUTS WRONG ENTRIES IN SETTINGS OF THE COUNTRY ICON PJ09405: WORKPLACE SHELL FREQUENT RESTART CAUSES UNPREDICTABLE RESULTS PJ09407: WINSETSYSPOINTERDATA HIDES MOUSE ON XGA & 8514A SYSTEM PJ09410: AN SPM/2 SPMILOG THREAD IN DOSEXIT(EXIT_THREAD,0) PROCESSING GETS A PAGE FAULT TRYING TO DEREFERENCE A POINTER WHILE DEREGISTERING A PERFVIEW MONITOR PJ09413: JOB PROPERTIES ARE IGNORED WHEN PM PRINT TO FILE WITH THE PSCRIPT DRIVER PJ09423: GP FAULT IN GDI.EXE RUNNING EXCEL 4.0 SLIDESHOW. LOCATION VARIES DEPENDING ON VERSION OF OS2 PJ09424: 32-BIT GPISETLINETYPE() GPISETLINEWIDTH() RET CODE IN LOW WORD PJ09428: SYSTEM HANGS WHEN EXITING A WIN-OS/2 SEAMLESS APP., WITH A BLACK SCREEN PJ09432: PARAMETERS FOR DOS DD IN DOS_DEVICES ARE NOT CASE MAPPED PJ09433: ILLEGAL OP CODE OCCURS ON DOS/V-J WHEN USING DOSKEY.COM PJ09434: OS/2 V2.1 RSPINST.EXE FAILS TO UPGRADE V2.0 SYSTEMS WHILE TRYING TO LOAD PRINTER DRIVERS IF RMPI WAS USED EARLIER PJ09436: WHILE COPY / PASTE BETWEEN TWO DOS APPS IS IN PROGRESS, ALT+HOME WILL HANG THE SESSION AND SOME TIMES HANGS THE SYSTEM PJ09437: WINOS2 FULLSCREEN: FILE/EXIT HANGS SYSTEM IF WINOS2 EXIT DIALOG BOX IS ALREADY DISPLAYED ON THE PM DESKTOP PJ09449: TRACK APPLICATION CAUSES TRAP 000D IN 8514_32.DLL PJ09450: INVALID EXPORT INTERNAL NAME CONFLICT MSG GENERATED PJ09457: ACCESS DENIED OVER LAN WITH NO ATTRIB RIGHTS BUT FILE COPIES OK PJ09458: DRAG & DROP TO AN HP 4L USING 4L DRV RESULTS IN WINGDING FONT. WHEN HP III DRV IS USED PRINT OUT IS FINE PJ09459: INCORRECT MESSAGE FROM FONT PALETTE AFTER ADDING FONT PJ09463: SYSTEM HANGS AFTER ATTEMPT TO RENAME FILE IN FLASH MEMORY PJ09471: RUNNING OUT OF SWAPPER SPACE CAUSING HANG AND OTHER PROBLEMS IN 2.1 PJ09474: XCOPY DROPS ADDITIONAL FILES WHEN CAN'T COPY OVER OPEN FILES PJ09478: BOOTING THE INSTALL DISKETTE, THEN INSERTING DISKETTE #1, THEN PRESSING ESC AND TRING TO START AN OS/2 APPLICATION CAUSE A TRAP 000D PJ09480: TRAP 000E DURING SHUTDOWN IF DETAILS VIEW OF PRINT JOB STILL OPEN PJ09481: DOSKILLTHREAD RETURNS RC != 0 EVEN WHEN SUCCESSFUL PJ09482: PM PRINTSCREEN IS VERY SMALL ON A HIGH RESOLUTION DISPLAY USING THE A4 FORM PJ09487: GP FAULT IN SFTSETUP.EXE AT 0004:0B3D INSTALLING MS ACCESS 1.1 FROM SERVER UNDER WINOS2 3.1 (OS/2 2.1) PJ09488: THEWORKPLACESHELL MESSAGE PROCESSING APPEARS TO BE HUNG. THE CMD PROCESSOR IS IN A LOOP IN THE PMVIOP:NEWPROCESS CODE PJ09492: VIDEO DRIVER ATTRIBUTE PROBLEM WD90C30 OS2 FULL SCREEN TEXTBASED APPLICATIONS. BLINKING WHEN SET TO 'BRIGHT' PJ09498: STANDALONE DUMP FACILITY IS NOT AVAILABLE ON YOUR SYSTEM IS DISPLAYED TRYING TO TAKE TRAP DUMP PJ09502: EA'S DISCARDED MSG WHEN XCOPYING A SUBDIRECTORY TO A ROOT DIRECTORY PJ09503: EA'S CORRUPTED WHEN XCOPYING AND RESTORING TO A SYDOS DRIVE(WHEN USED AS REMOVABLE MEDIA) PJ09514: A MODE COMMAND AGAINST THE IBM PCMCIA DATA/FAX MODEM RETURNS BUFFER = N/A. THIS IS INCORRECT AS THE DEVICE IS BUFFERED PJ09525: ERROR OCCURS WHILE RUNNING DOS APPLICATIONS SUCH AS F17A FLIGHT SIMULATION, ABLE V 4.0 AND A COMPILER WHICH USES PHARLAP 386 DOS EXTENDER PJ09526: SYS3175 IN IBMXGA32.DLL FROM GPIDRAWBITS API PJ09531: COPY GETS ACCESS DENIED ERROR ON SOURCE FILE DOSAPAPAR INT 21 6C, 3D PJ09537: INT 21 440E FOR A CDROM DRIVE IS NOT COMPATIBLE WITH DOS PJ09541: FONTS ARE PRINTED SMALL WHEN PRINTING IN 300 RESOLUTION WITH THE HP IV LASERJET FROM A PM HELP FILE PJ09542: INTERRUPT 2FH-FUNCTION 15H, SUBFUNCTION 08H ABSOLUTE DISK READ. RETRIEVE ONE OR MORE SECTORS FROM CDROM BY PHYSICAL SECTOR PJ09543: LOADER ATTACHES NEW PROCESS TO BAD LAN DLL PJ09544: MIGRATEAPPLICATIONS NOT WORKING DURING RESPONSE FILE INSTALLATION OF OS/2 V2.1 PJ09547: A VERY LARGE AND ONLY HALF OF A PM PRINTSCREEN IS PRINTED WHEN THE HP 4 IS MANUALLY SET TO 300 RESOLUTION PJ09548: SVGA STATUS IMPROPERLY REPORTS CIRRUS LOGIC CHISPET GD-5422 CHIPSET AS A GD-5426, CAUSING SVGA DRIVERS NOT TO LOAD PJ09550: INSTALLING OS221 OVER 20 DELETES NETWARE.DRV FROM WINOS2\SYSTEM PJ09554: BUG IN THE PRESENTATION MANAGER CONTAINER CONTROL PJ09555: MYOB IS GP FAULTING IN SEAMLESS MODE OS/2 2.1 GA ON VGA PJ09557: DOS VDM, SET PATH FILENAME CAN BE DISPLAYED TWICE PJ09563: PANIC 'MFT_LPTR OR MFT_SPTR FIELD NOT 0' WHEN FILE NOT UNLOCKED PJ09597: FOLDERS INSIDE A WORK AREA FOLDER NEEDS TO BE DOUBLE CLICKED TWICE IN ORDER TO OPEN THEM PJ09603: XCOPY DOESN'T REMOVE TEMPORARY DIRECTORIES ON ABNORMAL TERMINATION PJ09605: THE INABILITY TO CREATE A SUBDIRECTORY OF AN EXISTING DIRECTORY DURING A MOVE PJ09606: REMARKING OUT THE IBM2FLPY.ADD IN THE CONFIG.SYS WILL GIVE A SYS0038 ERROR WHEN REDIRECTING THE OUTPUT OF A COMMAND TO A FILE PJ09608: VMOUSE.SYS INT33-FUNCTION 0021 CAUSES TRAP 000E PJ09609: MITNOR PRINTSCREEN WITH A COLOR BACKGROUND RESULTS IN BLACK PRINT PJ09619: HP 4SI DOES NOT HAVE DUPLEX OPTION ENABLED UNDER PSCRIPT MODE PJ09620: TRAP 14 (0EH)WHEN CHANGING PRINT QUEUE TO HOLD WITH QUEUE CONTAINING A LARGE (> 1450) NUMBER OF PRINT JOBS PJ09627: COPY FILES TO AN HPFS PARTITION RESETS CREATION TIME TO THE CURRENT TIME, XCOPY DOES NOT PJ09629: "WORKPLACE SHELL CAN NOT BE LOCATED" ON FIRST REBOOT AFTER AN APPARENTLY SUCCESSFUL INSTALLATION OF OS/2 V2.1 PJ09632: SYSTEM HANGS WHEN PRINTING IMAGES FROM DESCRIBE 4.0 FOR OS/2 ON OS/2 2.1 PJ09635: PBOS2 HANGS SESSION ON EXIT PJ09639: PACK CANNOT ACCEPT A LIST FILE GREATER THAN 64K WITHOUT TRAPPING PJ09642: VIRTUAL MEMORY LEAK WITH DLL'S AND DOSDEBUG PJ09643: TRAP 000D CS:EIP 0140 0000B853 CSLIM 0000E973 RUNNING RM *\*\FILENAME PROGRAM FROM MKS DEVELOPERS TOOLKIT PJ09646: ALDUS PERSUASION 2.1 GP FAULT WITH PASTE EMBED SH FROM CLIPBOARD PJ09647: CHKDSK ON CD-ROM DRIVE THROUGH WPSH DOES NOTHING PJ09649: SYS3175 IN HELPMGR.DLL ATTEMPTING TO ACCESS EXTERNAL DATABASE LINK PJ09656: CLOSING HELP WINDOW IN EASEL/2 APP CAUSES SYS3175 IN PMWIN.DLL PJ09657: SYS 3171 IN DOSCALL1.DLL AT OR VERY CLOSE TO EIP 1A021B94 PJ09658: RUNNING MAKEINI ON 8514A CAUSES HANG WITH BLANK BLACK SCREEN AND BLINKING CURSOR ON NEXT REBOOT PJ09664: VDISK OS2 2.1 SIZE DISPLAY INCORRECT - APPENDS SECTOR SIZE TO VDISK SIZE PJ09669: WRITE ACCESS DENIED WHEN DRAG/DROPING A FILE TO A LAN DRIVE EVEN THOUGH WRITE ACCESS IS ON PJ09672: NETWORK DRIVE SETTINGS ARE NOT SAVED BETWEEN LOGONS FOR NOVELL DRIVES PJ09674: UPON RESIZE A HORIZONTAL LINE OF JUNK APPEARS IN THE CONTAINER CON- TROL WINDOW PJ09675: DOUBLE SLANT AS COMMENT IN WPOBJECT.H CAUSES ERRORS WHEN COMPILING WITH DEFAULT OPTIONS PJ09680: PCMCIA.SYS MUST FOLLOW COM.SYS. THIS IS NOT CORRECT AS CARD SERVICES SHOULD LOAD BEFORE CLIENT DEVICE DRIVERS. PCMCIA PJ09683: OS2 APP. EXECUTES ON 2.0 BUT FAILS ON 2.1 PJ09684: NETWARE REQUESTER FOR OS/2 TAKES 10-30 SECS TO BRING UP SETTING MENU OR START A PROGRAM FROM A NETWORK PGM ICON IN OS/2 V2.1.N PJ09688: TRAP IN PMGRE.DLL IN CREATELOGICALFONT32+283 (%1AC58B87) PJ09695: DOS APPLICATIONS HOOKING INT 08 OR INT 1CH FAILING WITH LOCKUP OR TRAP 000D ON PENTIUM PROCESSOR EQUIPPED MACHINES PJ09697: IPMD HANGS ON DOSDEBUG CALL FOR STEP COMMAND PJ09700: ERROR ON PAGEFAULT OF 16 BIT SHARED RO SEG DATA WITH LDR FIXUPS PJ09701: FCHILDRENOFTHEDESKTOP CAUSES SEAMLESS WINDOWS PAINT PROBLEMS PJ09704: MEMORY LEAK USING IMAGE ADAPTER IN HIGH RESOLUTION MODE PJ09706: HPFS CHKDSK USES TOO MUCH MEMORY: 1.3FIX NOT PORTED PJ09725: WRONG TITLE IN SHUTDOWN DIALOG BOX TITLE BAR PJ09729: ASCEND 4.0 FOR WINDOWS WILL NOT RUN SEAMLESSLY. WHEN RUN FROM THE PROGRAM MANAGER IT SEEMS TO FUNCTION FINE (Duplicate of PJ08851) PJ09732: ICONEDIT 2.1 DOES NOT SAVE/LOAD OPTIONS/PREFERENCES PJ09733: ERROR DIALOG BOX FROM PAINTBRUSH DOES NOT REPAINT PROPERLY PJ09736: FINDDEVNAME MUST HANDLE ITS OWN EXCEPTIONS PJ09740: MIGRATING CONFIG.SYS WHEN INSTALLING 2.1 OVER 2.0 ON SYSTEM WITH HPFS 386, THE 2ND HARD DRIVE CAN NOT BE ACCESSED PJ09754: TURKISH KEYBOARD CODEPAGE 850 WRONG CHAR KEY D11 PJ09759: PM ACCELERATOR KEYS BEHAVIOR DIFFERS FROM 2.0 IN 2.1 PJ09760: 2.88 DISK DRIVE, CAN'T ACCESS FILE COPIED TO 2.88 FLOPPY IN DOS, COPIED FROM OS/2 2.1, DISKS CAN'T BE USED IN DOS AND DOS 6.0 PJ09763: DOSCONNECTNPIPE/DOSDISCONNECTNPIPE FAILS RC=231 W/ TESTCASE PJ09770: IBM LAPTOP 486SL GENERATES A SYS3176 WHEN DOS_UMB=ON PJ09774: DEFAULT PUSHBUTTON DOESN'T FOLLOW CUA CONVENTION PROPERLY PJ09777: MMIO KERNAL HANGS WHEN STARTING WINOS/2 APPLICATIONS PJ09788: ERROR SIGN PUT UP BY WINMESSAGEBOX HAS CHANGED FROM 2.1 TO 2.0. AND OTHER CHOICES ARE SIMILAR PJ09791: GPIPOINTARC FAILS TO TRACE THE ORIGINAL ARCH FIGURE WITH SEVERAL CENTER POINTS PJ09793: DSMANAGER PROGRAM NOT COPYING FILES INTO CORRECT DIRECTORIES DURING EXECUTION PJ09797: CANNOT PRINT IN DRAFT MODE WHEN USING VARIOUS EPSON PRINTER DRIVERS PJ09804: OS/2 2.1 PRINTER SETTINGS NOT VISIBLE PJ09805: WPSCANSETUPSTRING METHOD NEVER CHECKS TO SEE IF THE BUFFER SIZE PASSED IS BIG ENOUGH TO STORE OUR RETURN PJ09807: MEDIA SENSE CAPABILITY DOES NOT WORK PJ09810: DOSOPENQUEUE TRAPS IN DOSSEMREQUEST(). DOSSEMREQUEST MODIFIES SEMHANDLE EVEN WHEN IT FAILS PJ09822: 2.1 INSTALL HANGS WHEN DPT SCSI CONTROLLER IS CONFIGURED TO LEVEL TRIGGER OPERATION PJ09823: SYS3175 IN HELPMGR.DLL WHEN EXITING VIEW.EXE AND 'LINKING NOT FOUND' MSG APPEARS IN THE BACKGROUND PJ09835: APPLICATION IS TERMINATED WHEN A WINDOW IS CREATED AND MINIMIZED WITH WINSETWINDOWPOS PJ09836: SFT ENTRY LEAK WITH BAD PATH PARAMETERS FROM LOADER PJ09838: UNABLE TO UNDATE REAL NAME IN DETAILS VIEW PJ09841: UNIVERSAL NAMING CONVENTION FILENAMES NOT WORKING AT ALL IN OS/2 VDM'S. EFFECTS NOVELL REQUESTER/MS SERVER PJ09845: RECEIVE MORE THAN ONE BUTTON3DOWN EVENT WHEN CLICK AND DRAG WITH 3 BUTTON MOUSE PJ09847: PRFRESET API DOES NOT UPDATE FOR COLORS AND ANY PREFERENCES THAT CAN BE SET PJ09850: STARTUP.CMD FAILSTO AUTOSTART WHEN OS/2 2.1 MACHINE IS REBOOTED PJ09854: MOVING FOLDERS BETWEEN PARTITIONS AND DOING A REFRESH CAUSES DUPLICATE ICONS TO BE CREATED PJ09855: RUNNING 8514 WITH AN ATI ULTRA GRAPHICS WILL CAUSE THE "A" FOR THE ADOBE TYPE TO APPEAR ON THE DESKTOP, AND WILL NOT DISAPPEAR PJ09858: GPISETCHARSTRINGAT ERROR 0X405E USING GPISETTEXTALIGNMENT AND GPISETCHARANGLE PJ09859: SYSTEM INI FILES NOT UPDATING. FILES FREEZING WITH THE READ ONLY ATTRIB ON AND STAYING THAT WAY PJ09869: HIGH STRESS COPIES IN FAT CAUSES MISCOMPARES PJ09871: "E" EDITOR RETURNS DISK FULL AFTER ATTEMPT TO SAVE TO A WRITE PROTECTED PJ09873: SYSTEM HANG DURING GPIFLOODFILL ON 16-COLOR DRIVERS PJ09883: MINIMIZED ICON FOR SEAMLESS WINDOWS APPLICATION IS DISPLAYED ON THE TOP LEFT CORNER OF THE DESKTOP WITHOUT THE TITLE PJ09885: SYSTEM TRAPS WHEN MOVING 3270 WINDOW ON THE DESKTOP IN SVGA PJ09886: FM_LOADDRIVERS LOCAL VARIABLE CAN BE REDUCED FREEING STACK SPACE PJ09888: CTRL+SPACEBAR KEY COMBINATION PUTS A BLANK SPACE IN AN MLE TEXT PJ09891: PROCOMM BLINKING CURSOR WILL MOVE ONE SPACE TO RIGHT IF A DOS WINDOW TITLE BAR IS PLACE ON THE SAME LINE PJ09893: NETVIEW MONITOR APP. GIVES TRAP D ON DIRTY HPFS PJ09905: WHEN INSTALLING OS/2 V2.1 OVER 2.0 EVERYTHING WITH REGARDS TO THE DESKTOP MIGRATES JUST FINE, EXCEPT THE COLOR SCHEME PJ09906: LOTUS NOTES 3.0 TRAPS THE LOTUS NOTES SERVER WHEN RUNNING THE CHRONOS MACRO PJ09909: THE BPROGTYPE OF THE SWCNTRL STRUCTURE IS NOT BEING SET PJ09912: CID INSTALL OF OS221 OVER IBM PC-DOS 5.0 TRAPS WITH SYS0318 IN RSPINST.EXE PJ09915: *ALIAS WHEN USED AS THE REMOTECOMPUTER NAME FOR A NETWORK PRINT OBJECT ACTUALLY STORES LS:\\COMPUTERNAME NOT LS:*ALIAS IN .INI PJ09917: SHARED DRIVER BETWEEN 8514 AND XGA CAUSES TWO CLIPPING REGIONS PJ09918: PRFQUERYPROFILESTRING API - 2.1 BUFFER LENGTH CHECK STILL THERE PJ09924: DEFAULT 'OPEN' ACTION CAN NOT BE RESTORED FOR EXECUTABLE FILES PJ09925: AFTERDARK 2.0 NOT WORKING IN SEAMLESS WINDOWS, WITHIN OS/2 2.1 AND OS/2 2.0 PJ09932: MINIMIZED ICON TITLE IS TRUNCATED IF THE ICON TEXT IS MORE THAN ONE LINE PJ09938: UNNECESSARY DIALOGUE BOX IS DISPLAYED WHILE COPYING A FILE ON MORE THAN ONE DISKETTE PJ09942: REDIRECTION IN A VMB NOT WORKING PJ09943: RC COMPILER FAILS TO UNDERSTAND ULONG DATATYPE WHILE PM CALLS REQUIRE IT PJ09950: CREATING ANOTHER FROM SHADOWS, DOES NOT USE THE CORRECT NEW NAME PJ09956: THE LIST BOX DOWN ARROW IS NOT REPAINTED TO BLACK WHEN MORE THAN 30 ITEMS IS LISTED IN THE BOX PJ09958: WIN-OS/2 PAINTBRUSH DOES NOT READ SOME CLIPBOARD BITMAPS PJ09962: REPEATED CALLS TO PRFREMOVEPROGRAM & PRFADDPROGRAM CORRUPTS PROGRAM OBJECTS PJ09970: FS REG BEING SET TO 0 BY FAILURE OCCURRING DURING DOSMUXSEMWAIT PJ09986: SYS3171 IN DOSCALL1.DLL WHILE PRINTING CS:EIP 005B : 1A02CA39 SS:ESP 0053 : 012A00C8 PJ09993: COMBO BOX WILL NOT REPAINT WHEN USING THE RADIO BUTTON TO CHANGE PAGE IN A NOTEBOOK PJ10008: DOS EDITOR EDWIN CAUSES VDM ENVIRONMENT VARIABLE CORRUPTION WITH OS/2 2.1 PJ10010: UNABLE TO MAKE A DUPLICATE OS2 FOLDER IN ANOTHER PARTITION PJ10013: PROBLEM LINKING PROGRAM WHERE ONE DNT ENTRY > 64K PJ10028: INSTALLING PED SOFTWARE'S JOURNALIST LIVE PAGE LAYOUT PJ10029: .FNT FILES IN \OS2\DLL\HP\PCL DIRECTORY YIELD SYS0005 IF COPIED IN VDM OR VMB, BUT WILL COPY OK USING OS/2 COPY COMMAND PJ10030: TRAP 000E CS:EIP= 0160 : FFF6A5B0 WHEN DELETING IN DETAIL VIEW PROBLEM IN:FUNCTION NAME: _PTFINDNODE + 0X55 PJ10035: CATSEYE XGA CAUSES DOS SESSION NOT TO GIVE PROMPT PJ10039: SEARCHLIGHT BBS CAUSES THE SYSTEM DATE TO INCREMENT TWICE EACH 24 HOURS. COULD HAPPEN WITH ANY DOS APPLICATION PJ10040: WRONG CODEPAGE IN CONFIG.SYS WITH ARABIC COUNTRY AND ARABIC KEYBOARD PJ10044: CORRUPTION IN WORDPERFECT 5.2 FOR OS/2 WITH 8514 32-BIT DRIVERS PJ10054: DOSOPEN TO LPT DEVICE NOT WORKING...RC=6 PJ10055: APPLICATION IN ICON AUTHOR CAUSE THREE (3) SIGNALS TO BE SENT IN WINOS2 BUT ONLY SEND ONE IN WINDOWS 3.1 PJ10071: OPTICAL DRIVE HANGS CHANGING OPTICAL DISK BEING ACCESSED PJ10097: POINTER GOES TO I-BAR ON LAST PAGE OF PROGRAM SETTINGS DIALOG PJ10099: ALL INSTANCE OF VIEW ARE CLOSED WHEN ONE IS CLOSED FROM THE WINDOW LIST PJ10109: SUBMENU ADDED TO THE DESKTOP POPUP MENU DISAPPEARS. MOSTLY IN HPFS SYSTEMS. AFTER SEVERAL REBOOTS PJ10120: WHEN PRFOPENPROFILE IS USED TO OPEN A USER .INI FILE, IT FREEZES/ LOCKSUP/HANGS THE SYSTEM UNDER OS/2 2.1 PJ10133: >64K DOSWRITES CAUSES CORRUPTION IN FAT WHEN CACHE BYPASS IS ENABLED PJ10137: MENU ITEM GETS DISABLED IN 1.3 BUT DOESN'T IN 2.0 PJ10139: MOVE FROM A COMMAND LINE OF A FOLDER WON'T MOVE ABSTRACT OBJECTS PJ10140: FOXPRO DISTRIBUTION KIT 2.5 FAILS WITH SETUP.APP PJ10146: DOCUMENTATION FOR LISTBOX CONTROL DOES NOT INCLUDELIT_CURSOR OPTION PJ10147: MATHEMATICA 2.2 GP FAULT 0006:0A26 WHEN SESSION SWITCH PJ10148: THE HOME 3270 OF THE PCS3270 VER. 3.0 ENTRY LEVEL DOS DOES NOT WORK IN OS/2 2.1 VDM. ACCESSING PCS3270 LOCKS THE HOST SESSION PJ10150: DRAG AND DROP DIFFERENT SIZE FONT TO WINDOW LIST. SHUTDOWN AND RE- BOOT. THE FONT IS SAVED, BUT THE LINE SPACING IS NOT PJ10151: OS2 PMSHELL HANG WHEN 82 SESSIONS ARE STARTED PJ10163: PC SUPPORT - MULTIPLE DPMI CLIENTS DO NOT RUN IN ONE VDM - THEY CAUSE TRAPS PJ10165: PC SUPPORT - VIRTUAL MOUSE DRIVER TRAPS IN WINOS2 PJ10167: PC SUPPORT - MULTIPLE DPMI CLIENTS DO NOT RUN IN SAME VDM PJ10168: FOXPRO 2.5 SEAMLESS FAILS WITH WINDOWS MINIMIZED PJ10169: PC SUPPORT - DS AND ES CORRUPTED WITH TWO DPMI CLIENTS PJ10170: PC SUPPORT - IPE IN PGSET.C WHEN RUNNING MULTIPLE DPMI CLIENTS IN ONE VDM PJ10187: SEMAINT FAILS IF USING OS221 DISK IMAGES FROM CDROM ON SERVER PJ10191: TRAP 000E IN PMWP.DLL. THIS IS THE ROOT OF ALL THE BLANK/BLACK ICON PROBLEMS WITH THE PROGRAM OBEJCTS PJ10196: VDHREQESTVDD: INVALID PARAMETER PANIC WHEN VDPMI NOT LOADED PJ10200: PROBLEMS USING THE IBM (TORONTO LABS) PCMCIA DATA/FAX MODEM UNDER OS/2 2.1. DROPPING CHARACTERS, ETC PJ10202: IPE IN 2.0 AND 2.1 DUE TO RSC: SFT NOT IN SFT LIST PJ10217: GPISETCHARBREAKEXTRA IGNORES EXTRA VALUE OF DBCS OUTLINEFONT PJ10230: GPISETPATTERN WITH DIAGHATCH CAUSES SYS3175 IN PMGRE.DLL PJ10233: SEM PROCESSING NEEDS TO BE ENABLED TO PREVENT SYS3175 IN PMGRE PJ10239: CID INSTALL OF OS221 OVER OS213 FAILS TO INSTALL 42XX PRINTER DRIVER CORRECTLY PJ10243: LINK386 DOES NOT APPLY PROPER FIXUPS WHEN DIRECTORY PATH FOR IBMCPP IS THREE CHARS LONG AND DEBUG CODE GENERATED PJ10247: NAMED PIPE CONNECTION BROKEN WHEN THIRD WINDOW GIVEN FOCUS PJ10253: CUSTOMER GETS A SYS3171 EXCEPTION ERROR IN PMWP.DLL WHEN USING CUSTOMER DEFINED ICONS IN FOLDER TREE VIEW PJ10256 : MEMORY OBJECT SHORT TERM LOCKED, AND LOCK IS HELD LONGER THAN 10 SECONDS CAUSING PANIC. VMOB: SHORT TERM LOCK FOR > 10 SECS: HOB PJ10261: 16BIT NMPIPE APP FAILS IN 2.X, WORKED IN 1.3..CLIENT WRITE RC=107, SERVER SEMREQUEST RC=111 PJ10264: IN A DOS VDM, A SMALL 'C' PRG EXE CALLS INT 21, 69H FOR THE FUNCTION OF GET/SET DISK VOLUME & NO RETURN VALUE PJ10269: DOCUMENTATION SHOULD BE UPDATED FOR PMERR_WIN_DEBUGMSG OR A DIFFERENT ERROR MESSAGE SHOULD BE USED PJ10274: WHEN A SYSTEM IS UNDER STRESS, WAITER OF DOSWAITTHREAD MAY WAKEUP WITH AN ERROR_INTERRUPT FROM TKSLEEP AND TRAP 000E PJ10275: PERFORMANCE HOOKS IN KERNEL NOT FREEING ALL ALLOCATED MEMORY PJ10278: TRAP 000D DURING XCOPY LONG-PATH-NAME DIRECTORIES PJ10281: WHEN USING A PROGRAM OBJECT TO START A REXX PROGRAM, A LEADING BLANK IS PASSED IN FRONT OF PARAMETER.ITWORKS FROM COMMAND LINE PJ10282: CTL-086 ON CYCLE DOWN RO UNAVAILABLE PJ10284: BACKGROUND COLOR IN A GROUP BOX HEADING IS DISPLAYED ALL THE WAY TILL THE END PJ10285: UNDELETE FEATURE FAILS IN WINOS2 PJ10289: THE LIST SEPARATOR ":" IS REQUIRED IN "COUNTRY SETTINGS - COUNTRY" FOR SWEDEN: AND OTHER COUNTRIES SUCH AS GERMANY PJ10297: WINFOCUSCHANGE IS IGNORED/DOES NOT WORK WITH AUTOMATIC LOCKUP TURNED ON PJ10305: GPIFLOODFILL GENERATES PMERR_PEL_NOT_AVAILABLE 0X20F0 ON 8514 DIS- PLAY DRIVER PJ10309: DESKTOP - ICON VIEW MISSING FROM WINDOW LIST, WHEN SHELL IS ALLOWED TO COME UP AFTER AN SYS0039-DRIVE A NOT READY ERROR PJ10314: RUNNING CERTAIN DOS APPLICATIONS CAUSE TRAP AT 0148 :00007D13 PJ10321: IN DRIVES FOLDER, LAN DRIVE WON'T SAVE ITS SETTINGS FOR DETAILS VIEW PJ10340: RSPINST INSTALL PUTS VGA STATEMENTS IN INI.RC ON A XGA SYSTEM PJ10363: SYSFILETREE RETURNS CURRENT DIRECTORY WHEN AN INVALID DIRECTORY IS SPECIFIED ON NOVELL DRIVES PJ10366: CDROM=1 IN RESPONSE FILE DOES NOT AUTO DETECT CDROM AND DOES NOT INSTALL ANY CDROM SUPPORT DURING OS/2 2.1 INSTALLATION PJ10373: UNABLE TO EXTRACT CORRECT VOLUME ID OFF FLOPPY DRIVE USING WILD CHARACTERS WITH DOS_FINDFIRST PJ10379: PROGRAM MANAGER FILE | RUN DOES NOT WORK WITH SUBST DRIVES PJ10396: CAN'T CHANGE THE NAME OF THE SERVER ICON PJ10401: CAN'T CHANGE SETTINGS ON WPNETWORK (FOLDER) PJ10408: LARGE 1.3 METAFILES AND METAFILES WITH BITMAPS NOT SAVING ON 2.1 PJ10416: PRFOPENPROFILE FAILS - ERROR CODE IS 0X41112 PMERR_MEMORY_ALLOCATION _ERRR PJ10425: GLOBALPAGEUNLOCK RETURNS ERROR VALUE IN WIN0S2 AND NOT IN WINDOWS 3.1 PJ10428: FORMAT & CHKDSK ENHANCEMENT FOR HPFS386 : THIS WILL NOT FIX ANY CHKDSK PROBLEM WITH HFS0102 MESSAGE PJ10444: LINKER ERROR L1086 WHEN LINKING LARGE C++ EXE PJ10450: UNABLE TO ELIMINATE CONTEXT MENU OPTIONS USING DESKMAN/2 PACKAGE PJ10454: RC COMPILER FAILS WHEN APPLYING TO *.RES FILE TO EXE THAT ALREADY HAS ATTACHED RESOURCES PJ10456: LOADER INIT IS EXECUTING DLL INIT'S IN INCORRECT ORDER CAUSING A TRAP PJ10459: FONTS IN MLE ARE NOT WORKING PROPERLY USING WINSETPRESPARAM AND MLM_SETFONT PJ10468: TRAP AT 0148 : 00007D13 INTERNAL REVISION 6.514 AFTER PRINT SCREEN WITH AT LEAST ONE DOS OR WINDOWS APPLICATION ACTIVE PJ10475: PERFVIEW WHILE IN D_CONFIG NEEDS SERIALIZATION PJ10476: MESSAGE Q OVERFLOW IND NOT CLEARED DURING CONFIGUREPERF-> CC INIT->ET FL MSGQ PJ10489: APM DOES NOT WORK WITH FUTURE DOMAIN SCSI DEVICE DRIVER PJ10495: DOCUMENTATION NEEDS TO BE CHANGED FOR WPSAVEIMMEDIATE METHOD PJ10499: CAN NOT SET BORDER COLORS ON ANY CONTROL EXCEPT ENTRY FIELD PJ10501: PMX(TCP/IP) IS CAUSING DESKTOP TO CHANGE SHADES OF COLOR PJ10503: ADDITIONAL HPFS SUPPORT FOR DCF/2 PJ10507: STARTING SYSTEM EDITOR FROM THE COMMAND LINE USING 'START' WITH THE /MIN OR /MAX OPTION CAUSES PROBLEMS PJ10508: GPILOADFONT(...) 16-BIT APP RETURNS GPI_ERROR ON OS/2 2.1 LOADING A FONT ACROSS THE NETWORK PJ10518: POSTSCRIPT 4039 DRIVER RETURNS A "DICTSTACKUNDERFLOW" ERROR WHEN PRINTING USING THE DUPLEX OPTION PJ10520: CHKDSK /F ON DISKETTE WITH DELETED EA DATA. SF HANGS/TRAPS PJ10523: GPIPLAYMET AND GPISAVEMET FUNCTIONS FAIL WHEN CALLED IN CONJUNCTION WITH THE ET-4000 CHIPSET PJ10542: POSTSCRIPT DRIVER SHOULD NOT BE PASSING BACK MARKSYM FONT ON A GPIQUERYFONTS CALL PJ10561: TRAP IN INSTAID.EXE DURING CID INSTALL OF ES 1.0 ON OS/2 2.1 PJ10564: M_WPPRINTERNEWCLASS IS NOT INCLUDED IN THE OS2386.LIB PJ10585: TRAP 13, USING RC COMPILER ON LARGE RESOURCE FILES PJ10855: FILE LOCKING VIOLATIONS. GETTING RC = 1,33. THIS IS A NORMAL AND CORRECT RESPONSE. SERVER SHOULD ALLOW 3 RETRIES, BUT IT'S NOT PJ10598: S3 VIDEO_MODE_RESTRICTION = CGA DOES NOT DISPLAY TEXT PJ10619: WPSAVEDEFERRED METHOD WILL CAUSE THE DIRTY LIST TO BE CORRUPTED PJ10631: DOSWRITE IS NOT UPDATING DATE/TIME OF LAST WRITE WHEN CALLED AFTER A DOSSETFILEINFO API PJ10641: DOS EDIT PROGRAM FAILING ON PENTIUM MACHINE PJ10643: TRAP AT VDHFREEZEMEM +0X0C BECAUSE VVSYSREQPROC() CALLS VVSYSSETLOCK () WITH INVALID_HVDM AS THE HVDM PJ10656: INSTALL FROM CDROM WITH FD16-700.ADD /!SN COPIES 2 INSTANCES TO CONFIG.SYS ON HARD DRIVE. PJ10664: INCORRECT FIXUPS FOR COMDATS IN EXPLICIT DATA SEGMENTS PJ10668: SCREEN SWITCH CAUSES TRAP-0 IN SHIELD PJ10673: SINGLE STEP TRACE DOES NOT ADVANCE IP IN DEBUG.COM ON PENTIUM AND OTHER 486-BASED SLC PROCESSORS.... OTHER CPUS POSSIBLY TOO PJ10682: DOSPEEKNMPIPE AND RELATED FUNCS FAIL ON HANDLE 0,1,2 EVEN IF HANDLES POINT TO FILES - DOSAPAR - INT 21, 5FXX PJ10694: LOADER HANGS ON LS REQUESTER ATTEMPTING TO LOAD A DLL FROM THE LS SERVER WHEN THE SERVER IS STOP PJ10700: NEED ADDITIONAL SUPPORT FOR HPFS386 MM IN OS2DASD.DMD PJ10729: DOS APPS. GIVING SYS3176 ERRORS WITH OS/2 2.1. FAILURES ARE SYSTEM- SPECIFIC AND CAN BE ALLEVIATED BY 2.0 VBIOS PJ10730: TERMINAL EMULATOR IN DOS VDM MAKES A INT21, 47H CALL AND RETURN VALUE IS NOT CORRECT PJ10737: WORKPLACE SHELL DOES NOT SHOW FILE COPIES ACCURATELY PJ10758: MEMORY LEAK WHEN USING DOSSTARTSESSION WITH OPTIONAL ICON PARAME PJ10767: GPI MARKER TRANSFORM INCORRECT PJ10779: BOCASOFT WIPEOUT HANGS SYSTEM IF IT ACTIVATES BEFORE SYSTEM LOCK PJ10782: FORMATPARTITION=0 RESPONSE FILE INSTALL KEYWORD IS NOT WORKING PJ10797: SYS3175 IN VIEWDOC.EXE VIEWING FOOTNOTE AND SELECT PREVIOUS PJ10847: CZECHOSLAVAKIA'S LAYOUT ID 245 HAS BROKEN VERTICAL VS UNBROKEN PJ10849: PM DOES NOT RECOGNIZE SECOND KEYBOARD LAYOUTS PJ10853: DOSCOPY API RETURNING ERROR CODE 267 IN NETWARE WHEN IT SHOULDN'T PJ10855: FILE LOCKING VIOLATIONS. GETTING RC = 1,33. THIS IS A NORMAL AND CORRECT RESPONSE. SERVER SHOULD ALLOW 3 RETRIES, BUT IT DOES NOT PJ10884: CDFS DRIVER NOT HANDLING FILE LOOKUPS PROPERLY PJ10952: CLOCK MOUSE RANDOMLY JUMPS AROUND WHEN PLACED OVER A FIND BOX IN OS2 PJ10954: NCOPY-4.01-130: ERROR WHEN USING NETWARE NCOPY IN PRIVATE DOS 5.O VMB ON 4.01 SERVER PJ10963: TRAP 0008/HANG INSTALLING ON AMBRA WITH SCSI 540MB HARD DRIVE AMBRA INSTALL SCSI PORT 6260 ADAPTEC BUILT INTO MOTHERBOARD PJ10968: WINAPS MSWORD AND EXCELL IS HANGING IN VPIC HANGING THE WHOLE SYSTEM PJ10969: IF FSFILTER.SYS IS LOADED, INT 21H FUNC 5H PRINT CHAR, WILL GO TO SCREEN INSTEAD OF PRINTER IN A VMB PJ10980: CHANGING ICON NAME FOR A DOMAIN AT SERVER ISN'T REFLECTED WITHIN REQUESTOR'S LAN SERVER FOLDER PJ10993: INT21/7H CAUSES IPE AT &07A:343A DOSKRNL:FILEINPUT (DIRECT CHARACTER INPUT WITHOUT ECHO)... PJ10995: IPMD DEBUGGER NOT WORKING CORRECTLY WITH WINLOCKINPUT PJ11011: LANTASTIC 5.0 IN OS/2 DOS VMB, TRY TO USE DEL *.* CMD, FAILS WITH PATH NOT FOUND ERROR MSG.DOSAPAR PJ11076: PRINTER ALIAS REMAINS IN THE 'ALIASES FOR LOGON DOMAIN' EVEN AFTER THE PRINTER IS DELETED ON THE SERVER PJ11091: INT 21 FUNCTION 4400 GET BLOCK DEVICE PARAMETER DOES NOT RETURN THE CORRECT DRIVE LETTER. ROOTS 3 UNDER OS/2 2.1 PJ11110: LINKER ABORTS BECAUSE SYMBOL ARRAY BOUNDS OVERWRITTEN PJ11125: MEMORY LEAK IN PMWIN (XQUERYVISIBLEREGION) PJ11192: SYSTEM HANGS DUE TO LOOP IN PMVIOP.DLL WITH MULTIPLE SESSIONS PJ11215: _WPMAKEDORMANT IS BEING CALLED MULTIPLE TIMES FOR THE SAME OBJECT PJ11234: POSSIBLE HOLE IN THE _USAGECOUNT WHICH MANIFESTS IN HANGS OR TRAPS IN SHELL PJ11257: THE WIN_RUN_MODE SETTINGS CAN NOT BE SAVED PJ11275: (NSC-ISEL J2.1+PMGRE BCJ004) INNERGREFREE FREE STACK DATA! PJ11299: MATHCAD 3.1 FILE ASSOCIATE DOES NOT WORK CORRECTLY UNDER WINOS2. CANNOT CHANGE FILE ASSOCIATION IN DOCUMENT PJ11310: CUSTOMER USES DESKMAN/2 TO MAKE AN OBJECT NON-RENAMEABLE: HOWEVER THEY CAN RENAME THE OBJECT FROM THE WINDOW LIST PJ11373: OS/2 !! SYS03147 & SYS02027 ERROR WHEN BOOTING UK 2.1 PRELOAD UTILITY DISKETTE PJ11377: SYSSEARCHPATH SEARCHES THE CURRENT DIRECTORY REGARDLESS OF WHAT PATH YOU SPECIFY PJ11379: SYS3175 IN IBMXGA32.DLL AT 1AE58B87 WHEN DISPLAYING PROPRIETARY LOGO IN PMWORD PJ11396: FINDFIRST FAILS ON DOSAPS AND SUBDIRECTORIES PJ11422: IPE OCCURRED WHEN RUNNING THE LEGATO PJ11427: REDRAW PROBLEM ON PM WINDOW (II) PJ11456: DEVICE DRIVERS ARE BEING RANDOMLY FREED FROM THE SYSTEM PJ11493: KERNEL FILSYS ROUTINE TRANSPATH2 TRAPS ON INVALID PATH INPUT PJ11496: TRANSPARENT BITMAPS NOT WORKING PROPERLY USING THE CIRRUS OR GENERIC SVGA DRIVER PJ11520: CANNOT LOAD DEVICE DRIVERS > 32K PJ11530: DEVESC_STARTDOC STRING TOO SHORT FOR PSCRIPT.DRV PJ11572: SYSTEM HANGS WHEN PERFECT IMAGE/2 SENDS IMAGE TO HP550C PJ11573: PRINT OBJECT CORRUPTION WHEN NOTEBOOK SETTINGS ARE OPENED PJ11603: STICKY PAD APPLICATION REMAINS CROSS-HATCHED EVEN AFTER THE APPLICAT- ION IS CLOSED PJ11706: LOCKUP AUTODIM BROKEN IN POST 2.1 GA BUILDS PJ11755: VALUEPOINT/PENTIUM WITH BANYAN VINES, VBAN.SYS FILE WILL TRAP 000E WHEN TRYING TO START A DOS VDM PJ11787: FILESYSQUERYAWAKEOBJECT TRAPS IF TESTING AN OBJECT WHILE RENAMED PJ11798: DISKCACHE HELP DISPLAYS INCORRECT INFORMATION FOR "N" PARAMETER. DISPLAYS MESSAGE "1024-BYTE" BLOCKS, SHOULD BE "1024-KB" BLOCKS PJ11825: SHUTDOWN DOESN'T COMPLETE IF APPLICATIONS ARE STARTED FROM NOVELL SERVER 3.12 PJ11848: PMGRE.DLL HANGS DURING INITIALIZATION WITH DCAF 1.2 PJ11873: DRIVE A: ERROR MESSAGE SYS0108 DOES NOT ALLOW CONTROL TO RETURN TO THE PROGRAM PJ11927: (PMCTLS) CONTAINER RECTANGLE WAS REMAINED PJ12039: OS/2 APM FAILS ON TOSHIBA T4700CT LAPTOP BECAUSE APM BIOS IS DISABLED AFTER POWERUP PN41144: SVGA BANDING PROBLEM ON APPLICATION SPECIFIED WINDOWS PN41158: REPEAT VIDEO PROBLEM_ PN41161: MTV: MOVIE DOESN'T SHOW WHEN APP WINDOW AT MAX SIZE PN41162: TRAP 000D IN SOUND BLASTER DRIVER PN41163: TRAP ON MULTIPLE OPENS PN41682: IMAGE ADAPTOR CO-EXISTENCE WITH XGA CAUSES HANG PN41685: MMPM/2 INSTALLATION REQUIRES MORE DISK SPACE THAN DOCUMENTED PN41967: MMPM/2 INSTALL PROBLEM WITH RESPONSE FILES PN42107: SOUND BLASTER LINE IN PROBLEM. NO AUDIO PASSTHRU PN42109: SOUNDBLASTER NO RESET ON CLOSE (FM CHIP) PN44770: PLAYING SMV VIDEO FROM A POLLING CD PERFORMS POORLY PN45151: TRAP E WHEN PLAYING .AVI FILES PN45488: EDITING A .WAV FILE RECORDED IN STEREO USING THE SELECT ALL EDIT FEATURE AND MODIFYING THE .WAV FILE SIZE, TERMINATES APPLICATION PN45489: CAN'T PLAY MS VIDEO FOR WINDOWS INDEO AVI FILES UNDER MMPM/2 PN46372: PROBLEM USING DOSOPEN AND PASSING HANDLE TO MMIOOPEN PN46466: ULTIMOTION PRODUCES POOR COLORS WHEN USED WITH A CATSEYE XGA/2 CARD IN 256 COLOR MODE PN46598: MISSING RECTANGLE DEALLOCATION AFTER CLOSE KIOSK ENVIRONMENT - REBOOT REQUIRED PN48644: MOVIE PLAYBACK FAILS AFTER 3 HOURS OF CONTINUOUS USE ΓòÉΓòÉΓòÉ 4.12. Thinkpads and OS/2 ServicePak 6200 ΓòÉΓòÉΓòÉ Thinkpads and OS/2 ServicePak 6200 ThinkPad 750c ---------------------------------------------------------------------------- CSD Installation Problem: Symptom: The ThinkPad 750c may boot to a blank screen with a flashing cursor after installation of the XR06200 CSD. Cause: The ThinkPad 750c comes with an option disk which contains an OS/2 SVGA driver for the video chipset built into the ThinkPad. Neither the OS/2 2.1 package nor the XR06200 CSD contain these drivers. If you have installed these drivers from the option disk, installation of the XR06200 CSD may result in your system booting to a blank screen with a flashing cursor. Workaround: Use RSPDSPI.EXE to restore VGA mode.... RSPDSPI /PK:VGA /SK:NONE /S:A:\ /T:C:\ Use the display driver disks from the XR06200 CSD, not from the OS/2 GA shrinkwrap package. In order to use the video features disk to restore SVGA on the system once VGA has been restored, use the following steps: 1) Delete the IBMVESA directory from your boot drive root directory. 2) REM out the statement that runs CHKRES.EXE in CONFIG.SYS 3) Run DSPINSTL and choose Generic SVGA (not the WD C30 option that will be highlighted). 4) Use the Display Driver Disks from the CSD when prompted for them. Do not use the Display Driver disks from the OS/2 2.1 shrinkwrap package. 5) Shutdown and reboot. 6) Start an OS/2 Full Screen session (MUST BE FULL SCREEN, NOT A WINDOW). 7) Use the video features disk provided with your ThinkPad to install the ThinkPad's SVGA drivers. 8) Shutdown and reboot, you should be back to SVGA. We are continuing to work towards a less complicated fix (and one that does not require sending a utility to the customer), but this is what we have so far in terms of workarounds... The device driver installation tool that we provided to System Test and FVT is able to recover the ThinkPad system to VGA and then to SVGA without all of the complicated steps above.... ΓòÉΓòÉΓòÉ 4.13. OS/2 SERVICE PACK TIPS ΓòÉΓòÉΓòÉ OS/2 SERVICE PACK TIPS March 13, 1994 In answering some questions that have come up, I'd like to pass along a few tips. 1. It's worthwhile to read the README and README.INS files. eg.Several questions regarding why the PRINTER DRIVERS are not requested during the update process have been asked by customers. It's explained in README.INS lines 32-34. 2. In the documentation, it's called out to take the Readonly, System, Hidden attributes for several files. Make sure you do this! On MY OWN system, I used ATTRIB -H -R -S *.* /S from the root directory. This insures all the OS2 files get updated. The caveat being, I don't have any private or secure files that I'm worried about altering. In particular, I go back and verify that OS2KRNL gets updated. Besides, the Service Pack puts the correct attributes back on the OS/2 files. ************************************************************** ** THE FOLLOWING IS NOT AN OFFICIALLY SUPPORTED PROCEDURE. ** ** and I've only tested it in a single user environment. ** ************************************************************** 3. But, if for one reason or another the user decides to backout the Service Pack and reinstall OS/2 Base GA code, a message will pop up: Display driver installation detected an invalid argument count in a configuration file ".DSC". Check the configuration file. This is a little frustrating because it occurs during the reading of the first Printer Driver diskette. You have already loaded all of the first 17 diskettes. At this point you can SOLVE the problem! Control-Escape. This will bring up the OS/2 Setup and Installation menu. Select it. In the upper left hand corner of the fullscreen that will be showing, select options. Then select COMMAND PROMPTS. It will give you an OS/2 Full Screen. At this point, type: DEL \OS2\INSTALL\PSS3.DSC and enter. Control-Escape back to the desktop and tag the OK button. You will see another message that 'Initialization has failed' and it keeps on going. This message does not seem to matter at this point. The install program will then ask for the next set of driver disks and you will get another error message regarding: C:\OS2\DLL\DSPRES.DLL is newer than the source code. Do you want to overwrite the target file? Yes. You can save yourself some heartburn by deleting the PSS3.DSC file BEFORE feeding the diskettes, and you will only be prompted for the overwrite the DSPPRES.DLL question. 4. Thinkpad 750 & 750 CE. There is a file on the IBM Raleigh BBS. 1-919-517-0001 called SY750104.EXE. It is the latest BIOS for the 750's. Although not necessary for the application of the Service Pack, it enables the 750 to use some settings a little more effectively. My recommendation, put the new BIOS fix on. You will need a couple of disks. It uncompresses to a .dsk format and you will need to LOADDSKF it. The correct LOADDSKF is included on the file you get from the BBS. ΓòÉΓòÉΓòÉ 5. OS/2 2.11 Documentation Updates ΓòÉΓòÉΓòÉ OS/2 2.11 Documentation Updates ΓòÉΓòÉΓòÉ 5.1. ServicePak 6200 Documentation Updates Part 1 ΓòÉΓòÉΓòÉ ServicePak 6200 Documentation Updates Part 1 +--- Note ---------------------------------------------+ | | | Before using this information and the product it supports, be sure | | to read the general information under Appendix A, "Notices" on | | page 9. | | | +-----------------------------------------------------+ Contents ------------------------------------------------------------------ Part 1: Changes to OS/2 2.1 Installation Guide . . . . . . . . . . . . . ii About This Book . . . . . . . . . . . . . . . ii Before You Begin . . . . . . . . . . . . . . ii Chapter 1. Choosing an Installation Procedure ii Chapter 2. Installing OS/2 2.1 as the Only Operating System (Basic Installation) . . . ii Chapter 3. Adding OS/2 2.1 to a DOS System (Dual Boot) . . . . . . . . . . . . . . . . ii Chapter 4. Installing Multiple Operating Systems (Boot Manager) . . . . . . . . . . . ii Chapter 5. Using a Response File to Install ii Appendix A. Adding Features and Changing Your System Configuration . . . . . . . . . . . . ii Appendix B. Diagnosing System Problems . . . ii Appendix F. Migrating from OS/2 Extended Edition to OS/2 2.1 . . . . . . . . . . . . ii Appendix G. Upgrading the BIOS of Your Computer . . . . . . . . . . . . . . . . . . ii Appendix H. Notices . . . . . . . . . . . . ii ------------------------------------------------------------------------------ Part 2: Changes to OS/2 2.1 Using the Operating System . . . . . . . . . ii About This Book . . . . . . . . . . . . . . . ii New Features in OS/2 2.1 . . . . . . . . . . ii Chapter 1. Getting Started with OS/2 2.1 . . ii Chapter 4. System Setup . . . . . . . . . . 1 Power . . . . . . . . . . . . . . . . . . . 1 PCMCIA . . . . . . . . . . . . . . . . . . 5 Chapter 5. Startup . . . . . . . . . . . . . 5 Chapter 6. Drives . . . . . . . . . . . . . 5 Chapter 8. Productivity . . . . . . . . . . 6 Chapter 10. Information . . . . . . . . . . 6 Chapter 12. Drive A . . . . . . . . . . . . 6 Chapter 16. Printers and Plotters . . . . . 6 Chapter 17. Preparing Your Programs . . . . 6 Chapter 18. Using Windows Programs . . . . . 6 Chapter 23. Audio Support for Applications . 6 Part 5: Extra Help . . . . . . . . . . . . . 6 Chapter 24. Solving Problems . . . . . . . . 6 Chapter 26. Software Support . . . . . . . . 6 Chapter 27. Video Support . . . . . . . . . 6 Chapter 28. Printer Support . . . . . . . . 6 Chapter 29. Hardware Support . . . . . . . . 6 Appendix B. Error Messages . . . . . . . . . 8 Appendix C. Backing Up and Restoring Your Desktop . . . . . . . . . . . . . . . . . . 8 Appendix F. Removing Programs . . . . . . . 8 Appendix A. Notices . . . . . . . . . . . . 9 Trademarks and Service Marks . . . . . . . . 9 About This Booklet The purpose of this booklet is to provide you with updates to the OS/2 2.1 Installation Guide and the OS/2 2.1 Using the Operating System book. Keep this booklet as a reference and look here first before referring to the Guide or Using book. HOW TO USE THIS BOOKLET _______________________ This booklet should be used in conjunction with the Installation Guide and Using the Operating System book. Only chapters that have changes are listed in this booklet. All changes begin with a reference to the page in the original documentation on which the change is to be made. Note: Because some of these changes are lengthy, you might want to make a notation on the original page referring to the update located in this booklet. HOW THIS BOOKLET IS ORGANIZED _____________________________ This booklet is organized into the following parts: o Part 1 contains changes to the OS/2 2.1 Installation Guide. o Part 2 contains changes to the OS/2 2.1 Using the Operating System. CONVENTIONS USED IN THIS BOOKLET ________________________________ The following conventions are used in this booklet to help distinguish elements of the text: +---------------+--------------------------------+ | Text Element | Use | +---------------+--------------------------------+ | bold | Indicates the name of an item | | | you that you can select. | +---------------+--------------------------------+ | italics | Indicates the first time a new | | | term is used. A definition of | | | the term immediately follows | | | the italicized terms. Italics | | | are also used to indicate a | | | book title or variable | | | information that must be | | | replaced by an actual value. | +---------------+--------------------------------+ | monospace | Indicates an example such as a | | | fictitious path and file name | | | or text that is displayed on | | | your screen, such as an error. | +---------------+--------------------------------+ | UPPERCASE | Indicates a file name, command | | | name, or acronym. | +---------------+--------------------------------+ | * | Indicates trademarks of the | | | IBM Corporation. | +---------------+--------------------------------+ | ** | Indicates trademarks of other | | | companies. | +---------------+--------------------------------+ PART 1: CHANGES TO OS/2 2.1 INSTALLATION GUIDE Part 1 contains information that is new or different from the information in the OS/2 2.1 Installation Guide. The chapter numbers and titles in this booklet are the same as those used in the Installation Guide; only those chapters of the Guide that are changed are included here. ABOUT THIS BOOK _______________ > On page x, add the following entry to the list in the section titled "How This Book Is Organized": o Appendix H provides information on creating a startup diskette for OS/2(*) 2.1. Note: The original Appendix H, "Notices" is now Appendix I, "Notices". BEFORE YOU BEGIN ________________ > On page xiii, replace the second paragraph with the following: Late-breaking information about installation can be found in the README.INS file. This file is located on Diskette 3 of the diskette package and on Diskette 1 of the CD package. > On page xiii, add the following minimum requirement: o At least CGA video support. > Under the section titled "Questions About Your Current Computer System" on page xiv, add the following questions and answers: o Are you installing on an EISA system with an Adaptec(**) 1742A controller card? If you have an EISA system with an Adaptec 1742A controller card and you want to install OS/2 2.1, you must run the Setup Configuration program provided on the Adaptec Card Setup Diskette. To set up the Adaptec card in the configuration using the Setup Diskette, do the following: 1. Set the Enhanced mode setting to OFF. 2. Set the Standard mode setting to ON. 3. Set the Hex Address setting to C800. 4. Set the I/O Port setting to 230H. 5. Set the DMA channel setting to 5. 6. Set the Parity Check setting to OFF. 7. Set the Synchronous Negotiation setting to ON. If CD-ROM is not recognized, set this setting to OFF. 8. Set the Enabled Disconnect setting to YES. 9. Set the IRQ setting to 11 (default is 2). o Are you installing OS/2 2.1 on an IBM(*) ThinkPad(*) with a Docking Station(**)? If you are installing OS/2 2.1 on an IBM ThinkPad 700, 700C, 720, or 720C attached to a 3550 Docking Station, you need to replace the ABIOS files on the OS/2 Installation Diskette with files from the Reference Diskette. Do the following: 1. Detach the ThinkPad from the Docking Station. 2. Create a Reference Diskette by following the documentation that came with the ThinkPad. 3. Make a copy of the Installation Diskette. 4. Remove the copy and insert the original Installation Diskette into drive A. 5. Turn on the computer. If it is already on, press and hold Ctrl+Alt and press Del to restart the system. 6. When you are prompted to do so, remove the Installation Diskette, insert Diskette 1, and press Enter. 7. When the Welcome screen is displayed, press Esc to display the command prompt. 8. Insert the copy of the Installation Diskette into drive A. 9. Type: A:\DEL *.BIO and press Enter. 10. Remove the copy of the Installation Diskette, and insert the Reference Diskette you created in step 2 into drive A. 11. If your computer has more than one diskette drive, insert the copy of the Installation Diskette into drive B. In the next two steps, you will be prompted to insert diskettes into both drive A and drive B. If your computer has only one diskette drive, when you are asked to insert a diskette into drive A, insert the Reference Diskette into your diskette drive. When you are asked to insert a diskette into drive B, insert the copy of the Installation Diskette into your diskette drive. 12. Type: COPY A:\*.BIO B:\ and press Enter. 13. Type: COPY A:\ABIOS.SYS B:\ and press Enter. 14. Turn off the ThinkPad and return it to the Docking Station. 15. Restart the installation procedure by inserting the copy of the Installation Diskette into drive A. o Are you installing on a system with an AOX upgrade? If you have a system with a 286 processor that has been upgraded to a 386SX with an AOX upgrade and you want to install OS/2 2.1, you must start the system with DOS and run the AOX232.EXE. To request the AOX232.EXE, contact the AOX Technical Support Group at 1-800-232-1269. > On page xv, add the following note after the question "Is your display adapter an ATI(**) Graphics Ultra(**) Pro?": Note: If you have a Gateway 2000(**) system, refer to "Black Lines on an OS/2 Logo Screen" for further instructions. > On page xvii, add the following header before the third paragraph: SCSI-Based CD-ROM Support > On page xvii, add the following section to the end of the page: Non-SCSI CD-ROM Support for Sony, Panasonic, and Mitsumi For the Sony(**), Panasonic(**), and Mitsumi(**) non-SCSI drives to be recognized by OS/2, the base port address specified on the CD-ROM BASEDEV statement in CONFIG.SYS must match the base I/O port address specified on the CD-ROM host adapter card. Note: If you are installing OS/2 2.1 from a CD-ROM, you might first need to modify the BASEDEV statement for your CD-ROM device driver in the CONFIG.SYS file on the diskette labeled Diskette 1. Modifying CONFIG.SYS for the Sony CDU-31A Device Driver: The examples that follow illustrate how this CD-ROM is attached to the most common host adapters and indicate the required parameter switch settings for each CD-ROM drive. Example 1: The Sony CDU-31A CD-ROM drive is attached to a Sony CDB-334 host adapter. The Sony CDB-334 host adapter supports base I/O port addresses of 320h, 330h, 340h, or 360h. If the host adapter is set to its default port address of 340h, the CONFIG.SYS statement does not need to be modified and should appear as follows: BASEDEV=SONY31A.ADD If the CDB-334 host adapter is set to any port address other than the default of 340h, the CONFIG.SYS statement must be modified. For example, if the Sony CDB-334 host adapter is set to a base I/O port address of 360, the line in the CONFIG.SYS file should appear as follows: BASEDEV=SONY31A.ADD /A:0 /P:0360 Example 2: The Sony CDU-31A CD-ROM drive is attached to a Media Vision(**) ProAudio Spectrum(**) 16 host adapter. In this case, the line in CONFIG.SYS must be modified and should appear as follows: BASEDEV=SONY31A.ADD /A:0 /AT:08 Example 3: The Sony CDU-31A CD-ROM drive is attached to a Creative Labs Sound Blaster(**) Pro, Sound Blaster 16, or Sound Blaster 16 MultiCD host adapter. The port address specified on the BASEDEV statement in CONFIG.SYS should be 10h above the base I/O port address specified on these adapter cards. For example, if the Sound Blaster card is set for a base I/O port address of 220h, the line in CONFIG.SYS should appear as follows: BASEDEV=SONY31A.ADD /A:0 /P:0230 Modifying CONFIG.SYS for the Panasonic Device Driver: The Panasonic device driver (SBCD2.ADD) supports the following CD-ROM drives: - Panasonic CR-521,522,523,562,563 - Creative Labs OmniCD - IBM ISA CD-ROM drive The examples that follow illustrate how this CD-ROM is attached to the most common host adapters and indicate the required parameter switch settings for each CD-ROM drive. Example 1: A Panasonic, Creative Labs OmniCD or IBM ISA CD-ROM drive is attached to a standard Panasonic or IBM CD-ROM host adapter. The standard Panasonic or IBM host adapter supports base I/O port addresses of 300h, 310h, 320h or 330h. For example, if the adapter is set to a base I/O port address of 300, the line in the CONFIG.SYS file should appear as follows: BASEDEV=SBCD2.ADD /P:300 Example 2: A Panasonic, Creative Labs OmniCD or IBM ISA CD-ROM drive is attached to a Creative Labs Sound Blaster Pro, Sound Blaster 16, or Sound Blaster 16 MultiCD. If the Sound Blaster card is set for a base I/O address of 220h, the line in CONFIG.SYS should appear as follows: BASEDEV=SBCD2.ADD /P:220 Example 3: A Creative Labs OmniCD is attached to a standard Creative Labs CD-ROM host adapter. The standard Creative Labs host adapter supports base I/O port addresses of 250h or 260h. For example, if the adapter is set to a base I/O port address of 250, the line in the CONFIG.SYS file should appear as follows: BASEDEV=SBCD2.ADD /P:250 /T:2 Modifying CONFIG.SYS for the Mitsumi CD-ROM Device Driver: The examples that follow illustrate how this CD-ROM is attached to the most common host adapters and indicate the required parameter switch settings for each CD-ROM drive. Example 1: A Mitsumi CD-ROM drive is attached to a Mitsumi host adapter. The Mitsumi host adapter supports I/O port address ranges from 300h to 3FCh. If the Mitsumi host adapter is set to a base I/O port address of either 300h or 340h, the statement in CONFIG.SYS does not need to be modified and should appear as follows: BASEDEV=MITFX001.ADD If the Mitsumi host adapter is set to an address other than those specified above, the BASEDEV statement needs to be modified. For example, if the Mitsumi host adapter is set to a base I/O port address of 320, the line in the CONFIG.SYS file should appear as follows: BASEDEV=MITFX001.ADD /P:320 Example 2: A Mitsumi CD-ROM drive is attached to a Creative Labs Sound Blaster 16 MultiCD. If the Mitsumi CD-ROM port on the Sound Blaster 16 MultiCD is set to an I/O port address of 320, the line in CONFIG.SYS should appear as follows: BASEDEV=MITFX001.ADD /P:320 > On page xviii, add the following note before the second paragraph: Note: Use the LOADDSKF utility program to create diskette images, which are compressed, binary images of a diskette. The LOADDSKF.EXE is in the \DISKIMGS directory of the CD. LOADDSKF can be run from either the DOS or OS/2 operating system. > On page xix, add the following additional note to the section titled "Additional Notes for Users of OS/2": o To avoid desktop problems such as a blank desktop or duplicated icons, you need to run CHKDSK /F and have at least 20MB of free space in your OS/2 partition. CHAPTER 1. CHOOSING AN INSTALLATION PROCEDURE ______________________________________________ > On page 6, replace paragraph 3 with the following: The amount of space you need for the OS/2 2.1 partition depends upon which features of the operating system you are going to install. The amount of space required is also related to how much system memory your computer has and how many applications will be running at the same time. If you are going to install all features of the operating system, you need approximately 40MB of free disk space and a minimum of 10MB of space for the SWAPPER.DAT file. If you are going to install selected features, you need from 20MB to 40MB. These installation choices are described in more detail in Chapter 2, " Installing OS/2 2.1 as the Only Operating System (Basic Installation)". If you are going to install multimedia support, you need up to an additional 5MB of hard disk space. CHAPTER 2. INSTALLING OS/2 2.1 AS THE ONLY ___________________________________________ OPERATING SYSTEM (BASIC INSTALLATION) _____________________________________ > On page 16, replace the first 3 paragraphs with the following: Install preselected features If you select this predetermined set of OS/2 features, you will need approximately 32MB of total disk space for the operating system and its features and a minimum of 10MB for the swapper file. Install all features If you select all features, you will need approximately 40MB of total disk space for the operating system and its features and a minimum of 10MB for the swapper file. Select features and install If you decide to select the features you want to install, you need from 20MB to 40MB of total disk space for the operating system and its features and a minimum of 10MB for the swapper file. > On page 24, add the following paragraph before the sentence "To make a selection different from the one listed in this window...": For non-SCSI CD-ROM drives, if you cannot access your CD-ROM device after installation, ensure that the port address in the BASEDEV statement in the CONFIG.SYS file on your startup partition (hard drive) matches the port address on the CD-ROM host adapter card. See "Non-SCSI CD-ROM Support for Sony, Panasonic, and Mitsumi". > On page 33, replace the second paragraph of the second list entry with the following: When the Update Windows desktop when WIN-OS/2 desktop is modified option is selected during the installation, the WIN-OS/2(*) PROGMAN.INI file points to the Microsoft(**) Windows(**) group files. However, WIN-OS/2 does not use the Microsoft Windows PROGMAN.INI file. Two different PROGMAN.INI files exist and each one is maintained by the respective system (OS/2 or Windows). Because both desktops share group files, they will reflect the changes when an existing group of files is modified. However, if a modification to the PROGMAN.INI file is necessary (add/remove a group file), the desktops will differ. New groups will not be reflected on the Microsoft Windows desktop. CHAPTER 3. ADDING OS/2 2.1 TO A DOS SYSTEM (DUAL _________________________________________________ BOOT) _____ > On page 37, add the following warning after the first paragraph: Warning: While it is possible to install OS/2 2.1 and DOS in the same partition, you might experience problems during the installation. To avoid these problems, use Boot Manager instead of Dual Boot. Refer to Chapter 4, "Installing Multiple Operation Systems (Boot Manager)" for more information. > On page 48, replace the boxed note with the following: +--- What to Do if Dual Boot Does Not Work --+ | | | If the BOOT command is unsuccessful when | | you try to switch from DOS to OS/2 2.1, | | you might have one or more active | | terminate-and-stay-resident (TSR) or DOS | | cache programs. If so, end the programs | | before you use the BOOT command. For TSR | | programs that are loaded from | | AUTOEXEC.BAT, you must deactivate the | | programs before using the BOOT command. | | | +--------------------------------------------+ CHAPTER 4. INSTALLING MULTIPLE OPERATING SYSTEMS _________________________________________________ (BOOT MANAGER) ______________ > On page 50, add the following note after the first paragraph: Note: If you have a system with a VESA(**) SUPER I/O controller and two disk drives, the system will not start DOS from the Boot Manager menu. Instead, it will display a non-system disk or disk error message. For more information on this message, check the VESA controller documentation or contact the manufacturer. > On page 52, add the following note after the third paragraph: Note: If a partition is going to contain an operating system, the partition cannot be larger than 1 GB (gigabyte) or 1024 cylinders. > On page 70, replace the table entry for OS/2 2.1 with the following: +----------+------------+------------------------+ | OS/2 2.1 | 20-40MB | (For operating system) | | | | | | | Minimum of | (For swapper file) | | | 10MB | | | | | (For multimedia | | | 5MB | support) | | | | | | | | OS/2 2.1 can be in a | | | | primary partition or | | | | logical drive. If you | | | | choose a minimum size | | | | for the partition, you | | | | might want to place | | | | the swap file on | | | | another partition. To | | | | do this, select Select | | | | features and install | | | | from the OS/2 Setup | | | | and Installation | | | | window. Then, select | | | | Software | | | | configuration. You | | | | can also install the | | | | WIN-OS/2 support in | | | | another partition. To | | | | do this, select | | | | WIN-OS/2 Support and | | | | its associated More | | | | push button from the | | | | OS/2 Setup and | | | | Installation window. | | | | | | | | If you want to install | | | | all features and you | | | | want the swap file on | | | | the same partition, | | | | consider making the | | | | OS/2 partition larger. | +----------+------------+------------------------+ > On page 83, add the following section before the section titled "Bypassing the Boot Manager Menu": Installing the Upgraded Version of MS-DOS 6.x If you are running a Dual Boot or Boot Manager configuration and you want to install the upgraded version of MS-DOS(**) 6.x, do the following: 1. Start your system with a current version of MS-DOS using a bootable MS-DOS diskette; do not use a Dual Boot or Boot Manager session. 2. Prepare an Uninstall Diskette so you can restore your previous version of DOS if needed. (Refer to your MS-DOS documentation for instructions.) 3. Edit the CONFIG.SYS and AUTOEXEC.BAT files. a. Type REM before each command line that starts a disk-caching, delete-protection, or antivirus program. Note: You need to disable the startup command for the MS-DOS SMARTDrive program. b. Disable any automatic message service, such as a network pop-up or a printing notification that is displayed on your screen. c. Save your changes to the CONFIG.SYS and AUTOEXEC.BAT files. d. Restart your system with the current installed version of MS-DOS, but not from a Dual Boot or Boot Manager session. 4. Insert the MS-DOS 6.x SETUP Diskette 1 into drive A. 5. At the DOS command prompt, type: A:SETUP 6. If your system is setup to use OS/2 Boot Manager, you will receive a message that states "This partition will not be available when using MS-DOS 6.x." Ignore this message and choose Continue Setup. If your system is setup to use OS/2 Dual Boot, you will receive a message prompting you to remove the non-MS-DOS operating system files from the drive. Ignore this message and choose Do Not Remove the Files. You will also receive a message stating "The operating system on the drive may be disabled." Ignore this message and choose Continue Setup. 7. Follow the instructions on your screen. If you need help during any of these procedures, press F1 for Help. 8. When you are prompted to do so, insert the diskette created in step 2 into drive A. 9. Restart your system when you have completed the Setup program. The system should start in MS-DOS 6.x. Warning: The MS-DOS 6.x installation program suggests that you run the MS-DEFRAG and MS(**) DOUBLE SPACE utility programs. These utility programs are not compatible with the OS/2 environment, and might cause data loss in OS/2 if executed. Other MS utility programs that perform direct diskette I/O, such as Interlink and UNDELETE, could compromise the OS/2 file system and are not supported. 10. To make the OS/2 system partition active again: o If your system is setup to use OS/2 Boot Manager, do the following: a. Type FDISK at the command prompt. b. When the FDISK screen appears, choose option 2; then press Enter. c. Choose the number that corresponds with the Boot Manager partition; then press Enter. d. When the confirmation screen appears, press Esc. e. Press Esc again to exit FDISK. f. Restart your system. o If your system is setup to use OS/2 Dual Boot, copy the COMMAND.COM file from the \DOS directory to the root directory. Note: SETUP places your previous DOS files in a directory named OLD_DOS.x. If you are sure you do not want to restore your previous version of DOS, you can delete the directory and its contents by typing DELOLDOS at the command prompt. ΓòÉΓòÉΓòÉ 5.2. ServicePak 6200 Documentation Updates Part 2 ΓòÉΓòÉΓòÉ ServicePak 6200 Documentation Updates Part 2 CHAPTER 5. USING A RESPONSE FILE TO INSTALL ____________________________________________ > On page 87, replace the instructions after the first paragraph with the following: This procedure requires unpacking compressed files. To do this, copy the UNPACK2.EXE file from Diskette 2 to your hard drive. Any unpack instructions should be performed from this hard drive. 1. Make a copy of Diskette 1. You will modify only this copy. 2. Make extra room on the copy of Diskette 1 by deleting the following files, which will not be needed in a response file installation: a. Delete the MOUSE.SYS, SYSINST2.EXE, and BUNDLE files from the copy of Diskette 1. Note: Deleting the BUNDLE file is not necessary for CD-ROM installation. b. If you are installing OS/2 2.1 on a Micro Channel(*) computer, delete the IBM1*.ADD file from the copy of Diskette 1. c. If you are installing OS/2 2.1 on a non-Micro-Channel computer, delete the IBM2*.ADD and *0S.SYS files from the copy of Diskette 1. 3. Edit the CONFIG.SYS file on the copy of Diskette 1: a. Change the SET OS2_SHELL statement from "SET OS2_SHELL=SYSINST2.EXE" to the following: SET OS2_SHELL=RSPINST.EXE A:\OS2SE20.RSP b. Delete the following statement: DEVICE=MOUSE.SYS c. If you are installing OS/2 2.1 on a Micro Channel computer, delete the following statements in the CONFIG.SYS file on the copy of Diskette 1: BASEDEV=IBM1FLPY.ADD BASEDEV=IBM1S506.ADD d. If you are installing OS/2 2.1 on a non-Micro-Channel computer, delete the following statements in the CONFIG.SYS file on the copy of Diskette 1: BASEDEV=IBM2FLPY.ADD BASEDEV=IBM2ADSK.ADD BASEDEV=IBM2SCSI.ADD 4. Use the following statement to unpack the compressed file REQUIRED that is located on Diskette 11 and copy the SAMPLE.RSP file contained within it to the root directory of your hard drive: UNPACK2 A:\REQUIRED C:\ /N:SAMPLE.RSP a. Use an editor (such as the System Editor) to modify and save the file. The file contains comments that explain each of the installation options. b. Copy this modified response file to the copy you made of Diskette 1 and rename it OS2SE21.RSP. For example: COPY C:\SAMPLE.RSP A:\OS2SE21.RSP 5. Use the following statement to unpack the compressed file REQUIRED that is located on Diskette 7 and copy the RSPINST.EXE file contained within it to the root directory of your hard drive: UNPACK2 A:\REQUIRED C:\ /N:RSPINST.EXE 6. Copy the RSPINST.EXE file to the copy of Diskette 1. 7. If you have a Micro Channel computer and the Reference Diskette contains ABIOS.SYS and *.BIO files, you will also need to modify the Installation Diskette: a. Make a copy of the OS/2 2.1 Installation Diskette. b. Delete the *.BIO and ABIOS.SYS files from the copy of the Installation Diskette. c. Copy the *.BIO and ABIOS.SYS files from the Reference Diskette to the copy of the Installation Diskette. Note: This Installation Diskette copy is now system-specific. You will need to create a modified Installation Diskette for each type of system on which you are installing OS/2 2.1. d. Use this copy of the diskette during the installation process. 8. Begin the installation of the workstation by inserting the copy of the Installation Diskette and restarting the system. 9. When prompted for Diskette 1, insert the modified copy of Diskette 1 and press Enter. From this point, the installation program will prompt only for the insertion of diskettes. No other installation actions are necessary. 10. When prompted to insert Diskette 1 again, insert the original copy of Diskette 1 into drive A. Note: If you are installing from diskettes, you will be prompted to insert the Installation Diskette after the display driver diskettes; insert Diskette 1 instead. Response files can be used to install the same set of options on multiple workstations. You must ensure that the workstations are set up with the same set of options and hardware. > On page 88, add the following after the first paragraph under the section titled "Installing OS/2 2.1 from a Local Area Network Source": Requirements for remote installation of OS/2: o The RAM requirements vary from 6MB to 10MB or more, depending on the installation variables. -- Redirected remote installation requires more RAM than disk installation because the SWAPPER.DAT file is not active. -- If you are doing a redirected remote installation without CID, you only need about 6MB of RAM. -- When using CID, the RAM requirements usually range from 6MB to 8MB. -- If you are using a process on top of CID, like NVDM/2, 8MB to 10MB (or more) might be required. The main variable with CID is the size of the REXX procedure and which dynamic link libraries it pulls in. With remote installation, the LAN connection utility programs are the main variables. The version of OS/2 that you are installing is another variable. -- The reduced diskette version of OS/2 2.1 (20 diskettes) requires more RAM because of the new UNPACK2.EXE routine. o During remote installation, the SWAPPER.DAT file is not active because the disk partition containing the active swapper file cannot be formatted during installation. The SWAPPER.DAT file can be made active, but the disk partition has to be a local partition and preformatted. In order to activate the SWAPPER.DAT file, the CONFIG.SYS file has to be edited. To do this, replace the existing MEMMAN=NOSWAP statement with the following: MEMMAN=SWAP,PROTECT SWAPPATH=D:\ 2048 4096 o Personal Computers might require more RAM as the network drivers might have to store more data into the RAM buffers until the processor is able to handle the data. APPENDIX A. ADDING FEATURES AND CHANGING YOUR ______________________________________________ SYSTEM CONFIGURATION ____________________ > On page 107, add the following note before the section titled "Description of the System Configuration Choices": Note: Make sure that the same diskettes used for the installation of OS/2 2.1 are used for Selective Install. There are two levels of diskettes, compressed and uncompressed. These diskettes are identical except for the purpose of Selective Install. The compressed diskettes have salmon-colored labels, and the uncompressed diskettes have blue-colored labels. > On page 114, add the following note after the heading titled "Installing Display Drivers Using Display Install": Note: If you want to install display drivers using Display Install, you must have OS/2 DOS Support installed. APPENDIX B. DIAGNOSING SYSTEM PROBLEMS _______________________________________ > On page 117, replace the first list entry with the following: o Single inline memory modules conflicts You might encounter problems if the single inline memory modules of your computer system were produced by different manufacturers, are of different classes, or operate at different speeds. Refer to the TRAP0002 message for more information. > On page 118, add the following after the last list entry: o Disk Read Error Systems with a HYPERACE(**) 486 Upgrade might receive a "Disk Read Error" when trying to read Diskette 1 during installation. Several switches on the HYPERACE card might need to be disabled: 1. Switch 1 - disables the main cache. 2. Switch 2 - disables the HIMEM cache. 3. Switch 4 - disables the BIOS cache. After installation, reset the switches to enable the caches. For more information on the procedures, check the HYPERACE card documentation. > On page 119, replace the line "Messages beginning with "TRAP"" with the following: Messages beginning with "TRAP0002" > On page 121, add the following messages: +--------------------------------------------+ | | | An error occurred when System Installation | | tried to locate the KBD01.SYS file. | | | +--------------------------------------------+ Explanation: The installation program could not locate the KBD01.SYS file on a system with a Micropolis(**) SCSI hard drive. This file is not located in the default path or the path specified in the CONFIG.SYS file. Action: (1) Edit the CONFIG.SYS file and add the following statement: DEVICE=KBD01.SYS (2) Disable the "Read ahead cache" in the UTIL.EXE. +--------------------------------------------+ | | | An error occurred when System Installation | | tried to load the dynamic link library. | | | +--------------------------------------------+ Explanation: The installation program could not load the dynamic link library because there is not enough random access memory (RAM). Action: Add more system memory (RAM). +--------------------------------------------+ | | | A disk read error occurred. | | | +--------------------------------------------+ Explanation: The BIOS level of the Future Domain(**) adapter is not compatible. Action: Contact Future Domain for a BIOS upgrade if you own: o Future Domain TMC-850/860/875/885 with BIOS revision level 7.0. o Future Domain TMC-1660/1670/1680 with BIOS revision level 2.0. > On page 122, replace the COUNTRY.SYS message with the following: +--------------------------------------------+ | | | COUNTRY.SYS file cannot be found | | | +--------------------------------------------+ Explanation: The OS/2 operating system does not recognize the hard disk or diskette. (1) If you have a PS/2(*) P70, you need to request an engineering change. (2) A diskette drive or a hard disk drive controller might have an additional device (such as a tape backup) attached to it. (3) The diskette drive or hard disk drive controller might not reside at its own interrupt request (IRQ) level. (4) The hard disk partition on which you are installing OS/2 2.1 was compressed with a DOS data compression program. (5) If you have a Gateway(**) Nomad(**) laptop computer with Phoenix(**) BIOS 1.02, you will have to update the BIOS to the next level. (6) If your system is using an AMI(**) Fast Disk or a Fast Disk II SCSI adapter, they will be recognized as Adaptec adapters. (7) You have more than two (2) hard drives in the system. Action: (1) Contact your IBM customer engineer or computer dealer and request the engineering change announcement "ECA068." (2) Disconnect the device, if possible. (3) Refer to the operations manual that came with your computer for information about the IRQ setting. (Refer to OS/2 2.1 Using the Operating System for more information about setting IRQ levels.) (4) Use the data compression program to decompress the partition, and then retry the installation. (5) Update your Gateway Nomad Laptop computer with Phoenix BIOS 1.03 or later. (6) After installation, edit the CONFIG.SYS file as follows: o Delete any line with the following: BASEDEV=AHA1xxx.ADD where xxx can be any character. o Ensure that the statement BASEDEV=IBMINT13.I13 is included. (7) Check the partitions on any drives beyond the first two drives. If they are primary partitions, back up the data and re-partition them as logical drives. > On page 123, replace the TRAPxxx message with the following: +--------------------------------------------+ | | | TRAPxxx | | | +--------------------------------------------+ Explanation: In general, traps are symptoms of software-related problems. After you have pursued these symptoms from a software failure perspective, you should consider the potential of a hardware cause relating to caches and memory. (1) If your computer has an 80486 microprocessor, your computer might require faster RAM chips (60ns or 70ns). (2) There might be a problem with the external (level 2) CPU memory cache or main memory system on ISA or EISA systems. Action: (1) From the setup/diagnostics diskette or the BIOS Setup program built into the computer, try disabling all shadow RAM and external (level 2) CPU memory cache. (2) If problems persist during the installation of OS/2 after performing the above action, turn off the turbo switch (if one is available) on your system and retry the operation. Disable caching during installation or turn the turbo switch off. > On page 123, add the following messages: +--------------------------------------------+ | | | TRAP0002 | | | +--------------------------------------------+ Explanation: A TRAP0002 error can be a memory parity error on the system board or on an adapter card. (1) Your computer system might have single inline memory modules that were produced by different manufacturers or that operate at different speeds. Or, your computer system might have different classes of single inline memory modules. (For example, a 1x9 module cannot be used with a 1x3 module.) Action: (1) Remove any defective single inline memory module. It might also be necessary to replace one or more modules. (2) If your IBM computer is a 33 MHz and the microprocessor card part number is 84F9356, contact your local IBM representative and request an ECA053. (3) If the Memory Riser card part number is N33F4905 or 84F9356 on an IBM Model 8590 system, contact your local IBM representative and request an ECA084. +--------------------------------------------+ | | | SYS0005 | | | +--------------------------------------------+ Explanation: When trying to do a redirected remote installation of OS/2 2.1 using SYSINST2 for panel installation, the error message SYS0005 appears while attempting to copy UNPACK.EXE. Action: This Access Denied Error is caused by damage to the extended attribute data on the NetWare(**) Server. To correct this problem, delete the old disk images on the server and create new OS/2 disk images. > On page 124, add the following message: +--------------------------------------------+ | | | SYS1719 | | | +--------------------------------------------+ Explanation: The file IBM386FS\HPFS386.IFS does not contain a valid device driver or file system driver. Action: Edit your CONFIG.SYS file and delete the following line: IFS=x:\OS2\HPFS.IFS > On page 124, replace the SYS2025 message with the following: +--------------------------------------------+ | | | SYS2025 | | | +--------------------------------------------+ Explanation: A disk read error occurred. This might be a disk error or a damaged system boot record. Action: (1) If this error occurred while the system was loading, follow the procedure under "Recovering from Errors on the Hard Disk". (2) If this error occurred when the system was reading the installation diskettes, there might be an error on the diskette. If you already have an operating system installed on your computer, use the DISKCOPY command to make a copy of the installation diskettes. Retry the installation with the newly copied diskettes. (3) If your computer has BIOS supplied by AMI or Phoenix, you might need to upgrade the BIOS. Refer to Appendix G. (4) If your system has a local bus IDE controller card, disable the BIOS on the 32-bit local bus IDE controller card and use the generic INT13 driver instead of IBM1S506.ADD. (5) Make sure that there is not a hardware problem with your hard disk controller or your diskette drive. > On page 125, replace the SYS2026 message with the following: +--------------------------------------------+ | | | SYS2026 | | | +--------------------------------------------+ Explanation: The file OS2LDR cannot be found. This is a hidden system file and must reside in the root directory of the drive from which the operating system is started. Action: (1) Make sure a non-system diskette is not in the diskette drive. If necessary, remove the non-system diskette and restart the system. (2) If the OS2LDR file is missing from the hard disk, start up the system using the Installation Diskette. Insert Diskette 1 and press Enter. (3) Copy the OS2LDR file from the Installation Diskette to the OS/2 partition. > On page 127, add the following after the paragraph under the heading titled Diskette 1: If you are installing on a system with an Allways(**) IN2000 SCSI adapter, an IPE or FDISK error is displayed during the installation of Diskette 1. Upgrade your system to the current BIOS level of VCN:1-02. The Allways IN2000 SCSI adapter might require an EPROM upgrade to operate with OS/2 2.1. You might find that you have some problems when trying to install over DOS partitions. To correct these problems, you need to install the EPROMS and reformat the hard drive. If you are installing OS/2 2.1 on a MYLEX system, a TRAP0008 error occurs during the installation of Diskette 1. For more information on this error, contact MYLEX. If you are installing on a Compaq(**) 386/331 Deskpro system, a TRAP000D error occurs during the installation of Diskette 1. To correct this problem, do the following: 1. Make a copy of Diskette 1. You will modify the copy. 2. Use an editor to edit the CONFIG.SYS file that exists on the copy of Diskette 1. 3. Delete the following statements: BASEDEV=IBM2M57.ADD BASEDEV=IBM2SCSI.ADD 4. Use the copy of the diskette during the installation process instead of the original. > On page 127, add the following list entry after Diskette 3: o Diskette 6 If the system refuses Diskette 6 and makes a beeping sound, your system might be infected with the Joshi virus. The Joshi virus is a DOS virus that interferes with OS/2 and seems to cause random lockups. The Joshi virus: -- Operates by trapping disk reads and writes. If the virus is active in memory, programs that try to locate the virus on diskette will have problems detecting it. -- Is carried on the boot sector of an infected data diskette or system diskette. This virus originated in DOS but can survive in OS/2. When you start an infected system, the virus resides in memory and survives a Ctrl+Alt+Del startup. If the user does not type in the text "Happy Birthday Joshi", the system will stop. -- Is copied to the boot sector of every diskette. The virus will be transferred to any computer on which the user performed any diskette operation that included reading from, or writing to, the infected diskette. -- Spreads from infected diskettes to DOS and OS/2 systems when the systems are started from diskettes. -- Interferes with the startup from the hard disk of OS/2-based systems. The warning that OS/2 will give is that the IBM1FLPY.ADD file is bad or missing. Many antivirus packages are effective at detecting this virus. In DOS, The Norton Antivirus(**) Version 2.1 can both detect and clear the virus. The Joshi virus can also be cleared from DOS-based systems with the undocumented FDISK parameter MBR. However, the FDISK.EXE must be copied to and run from each partition. Type the following: FDISK /MBR This procedure causes the master boot record to be refreshed by the system, and the Joshi virus is overwritten. However, this procedure does not remove the virus from memory. The system needs to be restarted and rescanned for the virus. In OS/2, Central Point(**) Antivirus can detect the virus. McAfee(**) Clean and Scan can both detect and clear the virus. For more information on this antivirus program, contact McAfee Associates at (408) 988-3832. > On page 127, add the following to the end of the page: Installation on a Quantum II XL Hard Card If you have a Quantum(**) hard card, you must make a modification to the BASEDEV=IBM1S506.ADD line in the CONFIG.SYS file. To modify the BASEDEV statement, do the following: 1. Edit the CONFIG.SYS file on Diskette 1. 2. Change the BASEDEV statement to: BASEDEV=IBM1S506.ADD /A:1 /IRQ:11 3. Save the CONFIG.SYS file. 4. Install OS/2 2.1. (These are the default settings for the Quantum hard card.) Black Lines on a OS/2 Logo Screen During the installation on a Gateway 2000 with an 80486/66MHz processor, a local bus, and an ATI Graphics Ultra Pro, the system will get to the screen with the colorful OS/2 full-screen symbol, and then the installation will stop. The display screen shows horizontal bands of video separated by black bands that scroll horizontally across the screen. To correct this problem, do the following: 1. Start DOS. 2. Change the OS/2 directory to MACH32. 3. Type: INSTALL 4. At the Main Selection screen select Set Power up Configuration. 5. Select Monitor Type, and press Enter. 6. Select 1572 Monitor with 72Hz Refresh Rate, and press Enter. 7. Select IBM Default as the new display. Note: After OS/2 is successfully installed, repeat the steps to reselect the 1572 Monitor type. White Screen Appears during Installation If the display screen is white during the installation of OS/2 2.1 and there is no system activity, set the video adapter to operate on an 8-bit mode and move the adapter to an 8-bit slot. Do the following: 1. Turn off the system and disable the autosensing capability of the video adapter. 2. To modify the settings, refer to the documentation that came with your video adapter. 3. Place the adapter in an 8-bit slot until you have successfully installed OS/2 2.1. 4. The adapter can be returned to the 16-bit slot and set back to the 16-bit mode. > On page 128, add the following to the list entries: o System is unable to access the CD-ROM drive o Redirection of XGA$DMQS Directory is ignored o An error appears when using Dual Boot o White screen or blank screen after installation o OS/2 2.0 desktop does not migrate o Slow SCSI support o System will not start DOS > On page 129, add the following after the section titled "Adding Support for a Mouse": System Unable to Access CD-ROM Drive If you clicked on the CD-ROM check box on the System Configuration screen during the installation of OS/2, the installation program put the entry None in the CD-ROM text box and the CD-ROM files were not copied. Because some drives are not directly supported by the device drivers shipped with the OS/2 product, you must now select OTHER from the selection list to enable CD-ROM support. For Sony, Mitsumi, or Hitachi(**) users, if you cannot access your CD-ROM drive, restart your system and do the following: 1. Copy the following files from Diskette 1 to the hard disk: COPY A:\OS2CDROM.DMD C:\OS2 COPY A:\CDFS.IFS C:\OS2 2. Edit your CONFIG.SYS file on the hard disk and add the following statements: DEVICE=C:\OS2\OS2CDROM.DMD /Q IFS=C:\OS2\CDFS.IFS /Q 3. Perform a shutdown and restart the system. For Sound Blaster users with the device driver SBPCD2.SYS, if you cannot access your CD-ROM drive, restart your system and do the following: 1. Copy the following file from Diskette 1 to the hard disk: COPY A:\CDFS.IFS C:\OS2 2. Edit the CONFIG.SYS file on the hard disk and add the following statement: IFS=C:\OS2\CDFS.IFS /Q 3. Restart your system to OS/2. 4. Start the Selective Install program in the System Setup folder. a. Click on the CD-ROM Device Support check box on the System Configuration screen. b. Click on OK to display the CD-ROM selection list. Scroll to the bottom of the list, select the choice OTHER and click on OK. 5. Continue the Selective Install process until completed. 6. Edit the CONFIG.SYS file and delete the following line: REM DEVICE=C:\OS2\OS2CDROM.DMD /Q 7. Perform a shutdown and restart the system. > On page 130, add the following before the section titled "Problems with a Mouse Not Working": Redirection of XGA$DMQS Directory Ignored during Installation The installation program copied the XGA$DMQS files to the same partition as the operating system. To correct this problem, do the following: 1. XCOPY the XGA$DMQS directory from the drive containing OS/2 2.1 to the redirected drive. a. Start an OS/2 session. b. Type XCOPY C:\XGA$DMQS D:\XGA$DMQS / S (where C is the drive containing OS/2 2.1 and D is the redirected target drive) c. Press Enter. 2. Edit the C:\CONFIG.SYS file. 3. Add the following line to the file: SET DMQSPATH=D:\XGA$DMQS 4. Save the changes and exit the editor. 5. Perform a shutdown and restart the system. > On page 131, add the following sections before the section titled "LOGO Screen Problems": Mouse Not Working after Selective Install If you did a selective installation of a new mouse and the mouse is not working, you will need to edit your CONFIG.SYS file. To edit the CONFIG.SYS file, do the following: 1. Open OS/2 Window. 2. Type: e config.sys and press Enter. 3. Delete the mouse device driver statements. For example: DEVICE=C:\OS2\MOUSE.SYS Note: If your mouse device driver is not for a Microsoft or PS/2 mouse, you might have two DEVICE= statements to delete. 4. Save the file. o Pull-down the File menu by pressing F10 and then Enter. o Select Save As. o Type in the CONFIG.SYS file name and press Enter. 5. Exit the System Editor by pressing Alt+F4. 6. Shut down and restart the system. Error When Using Dual Boot on a PS/1 System On PS/1(*) systems preinstalled with DOS 5.0, using Dual Boot from OS/2 to DOS results in an error. To correct this problem, press and hold Ctrl+Alt, and press Del to restart the system. > On page 132, change the heading to "White Screen or Blank Screen Problems" and add the following information after the first paragraph: On restarting the system after the complete installation of OS/2, the desktop appears to be blank. If the display screen is blank, performing CHKDSK on the drive connected to the ProComm(**) Micro Channel SCSI adapter might result in the system not working. To correct this problem, contact ProComm to receive the device driver needed for the SCSI card. > On page 132, add the following section before the section titled "Making the Boot Manager Startable": The OS/2 2.0 Desktop Does Not Migrate After OS/2 2.1 Installation After you install OS/2 2.1, you might have some problems migrating the OS/2 2.0 desktop. o If you have a desktop problem, do the following: 1. Insert the Installation Diskette and turn on the computer. 2. Insert Diskette 1 3. Press Esc at the Welcome screen to get to the command prompt. 4. Delete the DESKTOP directory. 5. Restart the system; the desktop should be re-created. 6. If the problem continues, you must run the MAKEINI program. o If you have moved program groups off the desktop and into a folder, you should move them back on the desktop before installing OS/2 2.1. Otherwise, duplicate icons could appear on the screen. If you try to delete these icons, the original icons will also be deleted. o If you want to recover a backed up OS/2 2.0 desktop, you can use the following procedure: 1. Insert the Installation Diskette, and turn on the computer. 2. Press Esc to get to the command prompt. 3. Delete or rename the INI files on the hard disk. 4. Copy the backup INI files to the OS/2 subdirectory. 5. Run the MAKEINI OS2.INI INI.RC program. 6. Run the MAKEINI OS2SYS.INI INISYS.RC program. 7. Delete the DESKTOP directory. 8. Restart the system. Notes: 1. If you try to recover the backed up OS/2 2.0 desktop, the customization for the OS/2 2.1 desktop will be lost. 2. The name of your DESKTOP directory might be slightly different. To find the actual name of your DESKTOP directory currently in use, display the Settings notebook for the desktop and select the File page. The current desktop name is shown under Physical name. > On page 133, add the following section before the section titled "Existing Application Not Migrated": Slow SCSI Support or Missing Icons After installation, slow SCSI support occurs. In addition, evidence of data damage such as missing icons might also occur. Check the documentation for the hard drive and the controller card to ensure that their settings are both set for the ASYNCH mode or the SYNCH mode. > On page 133, add the following sections to the end of the page: System Will Not Start DOS from the Boot Manager Menu On a system with a VESA SUPER I/O controller and two disk drives, the system will not start DOS from the Boot Manager menu. It will display a non-system disk or disk error message. For more information on this message, check the VESA controller documentation or contact the manufacturer. Running CHKDSK To run CHKDSK /F using diskettes: 1. Insert the Installation Diskette into drive A. 2. Turn on the computer. If the computer is already on, press and hold Ctrl+Alt, and press Del to restart the system. 3. When you are prompted to do so, remove the Installation Diskette and insert Diskette 1. 4. Press Enter. 5. When the Welcome screen is displayed, press Esc to display the command prompt. 6. Remove Diskette 1 and insert Diskette 2. Type: CHKDSK C: /F and press Enter. Note: If your operating system resides on a drive other than C, use the appropriate drive letter instead. > On page 137, add the following to the end of item 7: To run CHKDSK from a CD-ROM: 1. Insert the Installation Diskette into drive A. 2. Shut down and restart the system. 3. When prompted to do so, remove the Installation Diskette and insert Diskette 1; then press Enter. 4. When prompted to do so, insert the CD in the CD-ROM drive, and then press Enter. 5. When the Welcome screen is displayed, press Esc to display the command prompt. 6. To change directories, type: CD\ and press Enter. 7. Type: CD OS2SE2 and press Enter. 8. Type: CD DISK_2 and press Enter. 9. Type: CHKDSK x: /F (where x is the drive letter of your OS/2 system partition) and press Enter. ΓòÉΓòÉΓòÉ 5.3. ServicePak 6200 Documentation Updates Part 3 ΓòÉΓòÉΓòÉ ServicePak 6200 Documentation Updates Part 3 APPENDIX F. MIGRATING FROM OS/2 EXTENDED EDITION _________________________________________________ TO OS/2 2.1 ___________ > On page 166, add the following note to the end of the page: Note: If you are installing OS/2 2.1 on a system with a LAN SERVER 3.0 and a HPFS386, you will get a SYS1719 error message. Refer to the "SYS1719" message for more information. APPENDIX G. UPGRADING THE BIOS OF YOUR COMPUTER ________________________________________________ > On page 167, replace the sentence about Phoenix BIOS with the following: For questions about products that use Phoenix BIOS, call the computer manufacturer directly. If there are additional questions, call Phoenix at (714) 440-8080. APPENDIX H. NOTICES ____________________ > On page 171, add the following new appendix: Note: "Notices" will then become Appendix I. Appendix H. Creating an OS/2 Startup Diskette The following procedure explains how to create a startup diskette for OS/2 2.1. 1. Insert the Installation Diskette into drive A. 2. Copy the SYSINSTX.COM file to your OS/2 directory. 3. Remove the Installation Diskette from drive A. 4. Insert Diskette 1 into drive A. 5. Copy the KEYBOARD.DCP and SYSINST1.EXE files to a subdirectory on your hard disk. 6. Use the ATTRIB command to display the OS2KRNL, OS2LDR, and OS2LDR.MSG files. 7. Remove Diskette 1 from drive A. 8. Insert a blank, formatted diskette into drive A and type: SYSINSTX A: 9. Copy the OS2KRNL, OS2LDR, and OS2LDR.MSG files to the startup diskette, and then use the ATTRIB command to hide the files. 10. Copy the KEYBOARD.DCP and SYSINST1.EXE files from the subdirectory to the startup diskette. 11. Copy the following libraries from the \OS2\DLL directory to the startup diskette: ANSICALL.DLL DOSCALL1.DLL NLS.DLL NPXEMLTR.DLL BKSCALLS.DLL KBDCALLS.DLL OS2CHAR.DLL BMSCALLS.DLL MOUCALLS.DLL QUECALLS.DLL BVHINIT.DLL MSG.DLL SESMGR.DLL BVSCALLS.DLL NAMPIPES.DLL VIOCALLS.DLL 12. Copy the HARDERR.EXE and COUNTRY.SYS files from the \OS2\SYSTEM directory to the startup diskette. 13. Copy the SYSLEVEL.OS2 file from the \OS2\INSTALL directory to the startup diskette. 14. Copy the CMD.EXE, DOS.SYS, IBMINT13.I13, and OS2DASD.DMD to the startup diskette from the \OS2 directory. If you are planning to use HPFS, you need to copy the HPFS.IFS file to the startup diskette. 15. If you have an AT(*) system, copy the CLOCK01.SYS, KBD01.SYS, PRINT01.SYS, SCREEN01.SYS, and IBM1FLPY.ADD files to the startup diskette. 16. If you have a Micro Channel PS/2 system, copy the CLOCK02.SYS, KBD02.SYS, PRINT02.SYS, SCREEN02.SYS, and IBM2FLPY.ADD files to the startup diskette. The following command is used to copy the ABIOS.SYS file on the startup diskette for a PS/2 system: ECHO . > A:ABIOS.SYS 17. If you have a SCSI hard drive, copy the IBM2SCSI.ADD file (or the .ADD file from the manufacturer). If you have a hard drive other than a SCSI hard drive, copy the IBM1S506.ADD file to the startup diskette. 18. Using an editor, create the following CONFIG.SYS file on the startup diskette (in this case, for HPFS): IFS=HPFS.IFS /CACHE:64 BUFFERS=32 IOPL=YES MEMMAN=NOSWAP PROTSHELL=SYSINST1.EXE SET OS2_SHELL=CMD.EXE DISKCACHE=64,LW PROTECTONLY=YES LIBPATH=.;\; PAUSEONERROR=NO CODEPAGE=850 DEVINFO=KBD,US,KEYBOARD.DCP DEVICE=\DOS.SYS SET PATH=.;\ SET DPATH=\; SET KEYS=ON BASEDEV=PRINT0x.SYS (where x is 1 for AT; 2 for Micro Channel BASEDEV=IBMxFPLY.ADD (where x is 1 for AT; 2 for Micro Channel BASEDEV=IBMINT13.I13 BASEDEV=OS2DASD.DMD a. If you have a SCSI drive on a Micro Channel computer, add the following statement to this file: BASEDEV=IBM2SCSI.ADD b. If you have a hard drive other than a SCSI drive on a non-Micro Channel computer, add the following statement to this file: BASEDEV=IBM1S506.ADD c. If you have any space left on your diskette, copy the CHKDSK.COM file from the \OS2 directory to the startup diskette. PART 2: CHANGES TO OS/2 2.1 USING THE OPERATING SYSTEM Part 2 contains information that is new or different from the information in the OS/2 2.1 Using the Operating System book. The chapter numbers and titles in this booklet are the same as those used in the Using the Operating System book; only those chapters of the Using book that are changed are included here. ABOUT THIS BOOK _______________ > On page xxvi, replace the last three entries of the list in the section titled "How This Book is Organized" with the following list entries: o Appendix A describes the keys and mouse actions used in tasks. o Appendix B contains some of the most common error messages. o Appendix C describes how to back up and restore the desktop. o Appendix D describes the OS/2 file systems. o Appendix E describes the file locations. o Appendix F describes how to remove programs. o Appendix G contains forms for recording information about your computer. o Appendix H contains warranty and service information for the mini-applications and productivity aids. o Appendix I describes the Memory Dump process. o Appendix J contains the trademarks and service marks. o Glossary of the terms used in this book. o Index. NEW FEATURES IN OS/2 2.1 ________________________ > On page xxx, replace the list entry "The Ultimotion(*) software motion video formats" with the following: o Ultimotion and Video software motion video formats CHAPTER 1. GETTING STARTED WITH OS/2 2.1 _________________________________________ > On page 23, add the following instructions at the end of the section titled "Renaming an Object": You can also change the object name by performing the following steps: 1. Select the object whose name you want to change. 2. Press Shift+F9. 3. Type the new name in the Title field. 4. Press the Enter key on the numeric key pad. Note: Press Ctrl+Shift+Enter for any computer that does not have a numeric keypad. > On page 40, replace the first set of lockup instructions in the section titled "Locking Up Your System" with the following: To lock your system manually: 1. Point to an empty area on the desktop. 2. Click mouse button 2. 3. Select Lockup now. If this is the first time you have locked up the keyboard, a window appears where you can set up a password. (You will use this password later to unlock the keyboard so that you can use the computer.) 4. Type your password. 5. Carefully type your password again for verification. Note: If you forget your password, you must turn the computer off and then on again to unlock the keyboard. Any information that was not saved before the keyboard was locked will be lost. First Edition (January 1994) The following paragraph does not apply to the United Kingdom or any country where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you. This publication could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time. It is possible that this publication may contain reference to, or information about, IBM products (machines and programs), programming, or services that are not announced in your country. Such references or information must not be construed to mean that IBM intends to announce such IBM products, programming, or services in your country. Requests for technical information about IBM products should be made to your IBM authorized reseller or IBM marketing representative. (C) Copyright International Business Machines Corporation 1994. All rights reserved. Note to U.S. Government Users -- Documentation related to restricted rights -- Use, duplication or disclosure is subject to restrictions set forth in GSA ADP Schedule Contract with IBM Corp. --------------- (*) Trademark of the IBM Corporation. (**) Trademark of Adaptec, Inc. (*) Trademarks of the IBM Corporation. (**) Docking Station is a trademark of NEC Home Electronics, Inc. (**) ATI and Ultra are trademarks of ATI Technologies, Inc. Gateway 2000 is a trademark of Gateway 2000, Inc. Sony is a trademark of Sony Corporation. Panasonic is a trademark of Matsushita Electric Industrial Co., Ltd. Mitsumi is a trademark of Mitsumi Denki Kabushki Kaisha. (**) Media Vision and ProAudio Spectrum are trademarks of Media Vision, Inc. Sound Blaster is a trademark of Creative Labs, Inc. (*) Trademark of the IBM Corporation. (**) Microsoft and Windows are trademarks of the Microsoft Corporation. (**) VESA is a trademark of Video Electronics Standards Association. (**) MS-DOS is a trademark of the Microsoft Corporation. (**) MS is a trademark of the Microsoft Corporation. (*) Trademark of the IBM Corporation. (**) HYPERACE is a trademark of Hypertec Pty. Limited. (**) Micropolis is a trademark of Micropolis Corporation. Future Domain is a trademark of Future Domain Corporation. (*) Trademark of the IBM Corporation. (**) Gateway is a trademark of Gateway Systems Corporation. Nomad is a trademark of Gateway 2000, Inc. Phoenix is a trademark of Phoenix Technologies, Ltd. AMI is a trademark of American Megatrends, Inc. (**) NetWare is a trademark of Novell, Inc. (**) Allways is a trademark of Funk Software, Inc. Compaq is a trademark of Compaq Computer Corporation. (**) The Norton Antivirus is a trademark of Symantec Corporation. (**) Central Point is a trademark of Central Point Software, Inc. McAfee is a trademark of McAfee Associates. Quantum is a trademark of Quantum Corporation. (**) Hitachi is a trademark of Hitachi Ltd. (*) Trademark of the IBM Corporation. (**) ProComm is a trademark of Datastorm Technologies, Inc. (*) Trademark of the IBM Corporation. (*) Trademark of the IBM Corporation. CHAPTER 4. SYSTEM SETUP ________________________ > On page 68, add the following note to the end of the page: Note: If the keyboard speed is set in WIN-OS/2, when that WIN-OS/2 session is started, the keyboard speed for the entire system is reset and remains reset even after that WIN-OS/2 session is closed. > Replace the Power section at the end of this chapter with the information that follows. POWER The Power object manages and tracks power consumption in battery-powered computers that support the Advanced Power Management (APM) standard. The APM standard defines the way the hardware and software work together to reduce power consumption and help extend battery life. If your computer supports the APM standard, the Power object might be automatically installed during the OS/2 2.1 installation process. If it was not installed, you can install it by using Selective Install and selecting Advanced Power Management. For information about Selective Install, see "Selective Install". Note: This power management feature is not available if your computer does not have APM BIOS or a device driver that emulates APM BIOS. OS/2 2.1 APM support relies on the power status information returned from the BIOS on your computer. You might notice incorrect battery life or status within the Power icon on your computer. If this occurs, rely on the LEDs on your computer for accurate power status information. Turning the APM setting to Off also turns off the BIOS power management. If you want to turn off APM, but not the BIOS power management, place REM before the APM device driver statement in your CONFIG.SYS file, and then restart your system to invoke the change. For example: REM DEVICE=C:\OS2\APM.SYS Power Object To open the Power object: 1. Open OS/2 System. 2. Open System Setup. 3. Open Power. To display the Power pop-up menu: 1. Point to the Power object. 2. Click mouse button 1 or 2. Power Settings To set power management support: 1. Display the Power object pop-up menu. 2. Select the arrow to the right of Open. 3. Select Settings. The Power - Settings notebook appears. 4. Select Power. 5. Set Power management to On or Off. If set to On, power consumption will be reduced and power status will be tracked. If set to Off, the suspend mode, power status, and battery status features are disabled. 6. Set Confirm on power state changes if you want to confirm requests to go to suspend mode. (See "Suspend Mode.") To set the default status view of the status window: 1. Display the Power object pop-up menu. 2. Select the arrow to the right of Open. 3. Select Settings. The Power - Settings notebook appears. 4. Select View. 5. Select Full status or Battery only for Default status view. 6. Set Refresh (of the status window) to On or Off. 7. If you set Refresh to On, select the number of minutes (from 1 to 30) for Refresh rate. The system will automatically update the status window at the intervals you specified. You can also update the status window by selecting Refresh Now from the Power object pop-up menu. Power Status To display the power status: 1. Display the Power object pop-up menu. 2. Select the arrow to the right of Open. 3. Select Full status or Battery status. A full-status Power window or a power-gauge Power window is displayed, depending on your selection. Note: You cannot change the size of the Power window. A full-status Power window displays the following information: o Battery life. This information is displayed as a power gauge that shows the power level of the battery compared to the capacity of the battery. When the power gauge indicator is completely shaded, the battery is at full power. The shaded area of the gauge moves up or down as the battery power level increases or decreases. When the power gauge indicator is dimmed, there is no battery in the computer or the computer cannot provide battery information. o Power source for the computer. If the system cannot determine the power source, no power source information is displayed. o Battery state, which is the charge state of the battery. Battery state information is displayed as follows: High Battery charge is OK; continue using your computer. Low Recharge the battery or switch to another power source such as another battery or AC power. Critical Battery charge is depleted. Recharge the battery or switch to another power source immediately to avoid a system failure or data loss. Charging System is restoring the battery charge. Unknown System cannot determine the battery state or there is no battery in your computer. Suspend Mode To set the suspend mode: 1. Display the Power object pop-up menu. 2. Select Suspend. When suspend mode is activated, battery power is conserved by dimming the display and turning off devices that are not in use. If Confirm on power status changes is set in the Power - Settings notebook, a message that asks you if you want to continue is displayed before switching to suspend mode. Note: Different computers have different procedures for exiting suspend mode and resuming operation. Refer to the documentation that came with your computer for information about its suspend mode features. After you exit suspend mode, you will notice a startup delay before you can resume operation of your system. This delay might be a few seconds, depending on your system. PCMCIA OS/2 2.1 provides software support for Personal Computer Memory Card International Association (PCMCIA) hardware. PCMCIA(**) is the standard for PC card adapters associated with portable computers. A PC card is a small form-factor adapter about the size and shape of a credit card. You can use PC cards with laptops, notebooks, tablets, and other portable computer systems that are equipped with a PCMCIA slot. To install PCMCIA, use Selective Install and select PCMCIA. For information about Selective Install, see "Selective Install". CHAPTER 5. STARTUP ___________________ > On page 93, replace all text after the first paragraph with the following: If you add hard disk drives or partitions after the installation of the OS/2 operating system, you should edit the CONFIG.SYS file and update the AC:x parameter to reflect the new additions. AC: starts the auto-check feature on the specified drives when the system shuts down improperly. The value x represents the letters of the disks or partitions on the system that you want to check. For example, if you want to check disks C and D and your existing DISKCACHE statement is: DISKCACHE=64,LW Add the AC: parameter to the statement as follows: DISKCACHE=64,LW,AC:CD CHAPTER 6. DRIVES __________________ > On page 95, add the following note before the section titled "About Hard Disks and Diskettes": Note: Drive objects cannot be copied. > On page 97, add the following note to the Tree view paragraph: Note: When an additional folder is opened from a folder that is in tree view, if the default for the additional folder is also tree view, it is overridden and displayed in an icon view. There is no need to open it again in tree view because it is already shown in the parent folder's tree view. --------------- (**) PCMCIA is a trademark of Personal Computer Memory Card International Association. > On page 101, replace the instructions in the section titled "Moving Objects" with the following: To move an object from a drive to another location: 1. Open the drive containing the object you want to move. 2. Point to the object you want to move. 3. Press and hold mouse button 2. 4. Drag the object to a folder, the desktop, or another drive object. 5. Release mouse button 2. > On page 102, replace the moving instructions with the following: To move an object from another location to a drive: 1. Point to the object you want to move. 2. Press and hold mouse button 2. 3. Drag the mouse to the drive object. 4. Release mouse button 2. > On page 109, replace instruction #16 with the following: 16. Type the following information into the data file: DEVICE=FSFILTER.SYS DEVICE=C:\OS2\MDOS\HIMEM.SYS DEVICE=C:\OS2\MDOS\EMM386.SYS DOS=HIGH,UMB DEVICEHIGH=C:\OS2\MDOS\ANSI.SYS FILES=20 BUFFERS=20 CHAPTER 8. PRODUCTIVITY ________________________ > On page 117, add the following note to the section titled "Picture Viewer": Note: Picture Viewer does not support multiple-page metafiles. CHAPTER 10. INFORMATION ________________________ > On page 133, replace line 3 of the instructions in the section titled "Printing the README" with the following: 3. Drag the README object to a printer object. CHAPTER 12. DRIVE A ____________________ > On page 139, add the following note before the section titled "Display the Objects on a Diskette": Note: The Drive A object cannot be copied. > On page 141, replace all the instructions following the note in the section titled "Copying Objects to or from a Diskette" with the following: To copy an object from a diskette in Drive A to another location: 1. Place a diskette into drive A. 2. Open Drive A. 3. Point to the object you want to copy. 4. Press and hold Ctrl. 5. Press and hold mouse button 2. 6. Drag the object to a folder, the desktop, or another drive object. 7. Release mouse button 2. 8. Release Ctrl. To copy an object from another location to a diskette in Drive A: 1. Place the diskette you want to copy the object to into drive A. 2. Point to the object you want to copy. 3. Press and hold Ctrl. 4. Press and hold mouse button 2. 5. Drag the mouse to the Drive A object. 6. Release mouse button 2. 7. Release Ctrl. > On page 142, replace all the instructions following the note in the section titled "Moving Objects to or from a Diskette" with the following: To move an object from the diskette in Drive A to another location: 1. Place a diskette into drive A. 2. Open Drive A. 3. Point to the object you want to move. 4. Press and hold Shift. 5. Press and hold mouse button 2. 6. Drag the object to a folder, the desktop, or another drive object. 7. Release mouse button 2. 8. Release Shift. Note: When moving an object from a diskette, the Shift key must be used with mouse button 2. To move an object from another location to the diskette in Drive A: 1. Place the diskette you want to move the object to into drive A. 2. Point to the object you want to move. 3. Press and hold Shift. 4. Press and hold mouse button 2. 5. Drag the object to the Drive A object. 6. Release mouse button 2. 7. Release Shift. Note: When moving an object to a diskette, the Shift key must be used with mouse button 2. CHAPTER 16. PRINTERS AND PLOTTERS __________________________________ > On page 166, add the following instruction between lines 7 and 8: 7a. Select Install new printer driver. CHAPTER 17. PREPARING YOUR PROGRAMS ____________________________________ > On page 185, add the following note before the section titled "Viewing Program Object Settings": Note: The PgUp and PgDn keys on the numeric keypad should not be used to move between pages. ΓòÉΓòÉΓòÉ 5.4. ServicePak 6200 Documentation Updates Part 4 ΓòÉΓòÉΓòÉ ServicePak 6200 Documentation Updates Part 4 CHAPTER 18. USING WINDOWS PROGRAMS ___________________________________ > On page 196, replace the last sentence in the section titled "Character Map" with the following: Character Map works with Windows and OS/2 programs. > On page 199, replace all the text after the first paragraph in the section titled "Locating Window Programs" with the following: When you run the Migrate Applications program for existing Windows programs, the WIN-OS/2 Groups folder is created and placed on the desktop. The WIN-OS/2 Groups folder contains folders of Windows application programs that reside in the default groups, WIN-OS/2 Accessories and WIN-OS/2 Main. A group is a set of Windows programs that are related. The Windows Programs folder contains Windows programs that have settings preselected to optimize the performance of your program. Windows programs that do not belong to any group are migrated to the Windows Programs folder. The Additional Windows Programs folder contains Windows programs that have default settings for your programs. (If these programs do not run correctly, you can specify other settings.) For example, if you have CorelDraw(**) for Windows installed, when you run the Migrate Applications program, a folder for all the CorelDraw programs is created and placed in the Additional Window Programs folder. Now you have access to all the CorelDraw programs in one folder. For more information about migrating programs, see "Migrate Applications". > On page 201, replace the paragraph at the top of the page with the following: When you change the value of a setting before you start a session, the changes affect all programs running in that session. When you change the value of a setting while the session is running, the changes will not have any effect until you restart the session. If you want the changes to remain whenever you start a specific session or program, you must save the changes. > On page 201, add the following note before the section titled "Running Window Programs in WIN-OS/2 Sessions": Note: The changes will not take effect until you restart the session. > On page 202, replace the last sentence with the following: To run more than one Windows program, repeat the above steps as needed. > On page 205, replace the last paragraph before the section titled "Using the Clipboard and Dynamic Data Exchange Features" with the following: To switch between active WIN-OS/2 sessions, press Alt+Tab. CHAPTER 23. AUDIO SUPPORT FOR APPLICATIONS ___________________________________________ > On page 259, move the sentence that reads "If there are cells that have audio, each of these cells is shown, one by one, as selected and unshaded." to the end of the page. > On page 260, move the first paragraph beginning with "If the cell you select..." to after the delete instructions. Move the paragraph beginning with "If the work sheet is not synchronized..." to after the second set of instructions. PART 5: EXTRA HELP ___________________ > On page 263, replace the entry list with the following: o What to do when you have a problem o Tuning the performance of your system o Software support, including information about the OS/2 clipboard and Dynamic Data Exchange (DDE) o Video support, including information about Super VGA, XGA(*) systems, and laptop LCD displays o Printing support, including information about installing and configuring printer drivers o Hardware support, including information about high-resolution displays, CD-ROM drives, Advanced Power Management (APM), and mobile computing CHAPTER 24. SOLVING PROBLEMS _____________________________ > On page 267, replace the sentence in the first Action column that begins "Refer to 'Adding online documentation...'" with the following: Refer to "documentation, adding after installation" in the Master Help Index. > On page 273, replace the first paragraph in the Action column with the following: Download the program and try to run it without the network. If the program runs, the problem is probably related to the network. Ask your network administrator for assistance. > On page 282, replace the DOS setting "MOUSE_EXCLUSIVE_ACCESS DOS setting" in the Action column with the following: MOUSE_EXCLUSIVE_ACCESS > On page 285, replace the example beginning with "MODE COM3 ..." in the Action column with the following: MODE COM3 IDSR=OFF ODSR=OFF OCTS=OFF > On page 285, replace the paragraph beginning with "Fax programs must..." in the Action column with the following: DOS fax programs must operate at less than 9600 bps. Use an OS/2 fax program for high-speed faxing. CHAPTER 26. SOFTWARE SUPPORT _____________________________ > On page 301, delete the first sentence under Enhanced Editor. > On page 301, add the following section after Enhanced Editor: ES 1.0 Database Manager o To properly install the ES 1.0 Database Manager, the file ESSTART.BAK must be copied from the OS/2 2.1 Installation Diskette to the ES 1.0 installation diskette and renamed ESSTART.CMD. > On page 309, replace the statement beginning with "123MEMSIZE=2048 ..." with the following: SET 123MEMSIZE=2048 CHAPTER 27. VIDEO SUPPORT __________________________ > On page 334, replace the statement "UNPACK A:G.FON" with the following: UNPACK A:*G.FON CHAPTER 28. PRINTER SUPPORT ____________________________ > On page 353, add the following Lexmark(**) bulletin board phone number to the end of the first sentence in the section titled "IBM 4019 and IBM 4029 Printers": (1-606-232-5238) CHAPTER 29. HARDWARE SUPPORT _____________________________ > On page 363, replace the last entry under the Model column with the following: CR-501, LK-MC501S, MC501B > On page 366, replace the first paragraph in the Comments column with the following: IBM SCSI and Future Domain 16-bit SCSI adapters might work, but are not supported by IBM. > On page 373, each BASEDEV example should contain all of its parameters on one line. > On page 378, replace the example beginning with "DEVICE=X ..." with the following: DEVICE=X:\OS2\COM.SYS (n,a,i,s) > On page 383, add the following section: Advanced Power Management Support for Laptop Computers Laptop computers with the following are compatible with OS/2 2.11 Advanced Power Management: o 16-bit protect-mode APM in BIOS o 32-bit protect-mode APM in BIOS Laptop computers that have no APM support in BIOS or have only real-mode APM are not supported by OS/2 2.11 Advanced Power Management. The DOS utility program APMHERE, which is available on the IBM BBS, can quickly determine whether your machine has Advanced Power Management support in conformance to the APM 1.0 Specification (dated 1/91). Systems with BIOS dates prior to January 1991 will not have the protect-mode APM support in their BIOS. Laptop Computers with APM Support The table that follows lists the laptop computers that have Advanced Power Management support. (This list represents only systems tested as of January 27, 1994.) --------------- (**) CorelDraw is a trademark of Corel Systems Corporation. (*) Trademark of the IBM Corporation. (**) Trademark of Lexmark International, Inc. +------------------+--------------+--------------+ | Manufacturer | Model | Comments | +------------------+--------------+--------------+ | Acer America | AcerNote 730 | BIOS | | Corp. | | information | | | | displayed on | | | | start up: | | | | | | | | PhoenixBIOS|TM) A486 | | | Version 1.0| R1.0 +------------------+--------------+--------------+ | Acer America | AcerNote 750 | | | Corp. | | | +------------------+--------------+--------------+ | AST Research, | PowerExec | | | Inc. | 4/25SL | | +------------------+--------------+--------------+ | AST Research, | PowerExec | Perform the | | Inc. | 4/25SL Color | following | | | Plus | steps: | | | 486SL/25 | | | | Active | 1. Press FN | | | Matrix Color | F1 keys | | | | to get | | | | BIO | | | | access | | | | 2. Select | | | | Power | | | | Managemen| | | | 3. Click on | | | | Power | | | | Managemen| | | | Section | | | | 4. Follow | | | | the | | | | Character|ze | | | the | | | | Battery | | | | instructi|ns +------------------+--------------+--------------+ | Compaq Computer | 4/25 | | | Corp. | | | +------------------+--------------+--------------+ | Compaq Computer | CONTURA 4/25 | | | Corp. | Monochrome, | | | | VGA | | +------------------+--------------+--------------+ | Compaq Computer | CONTURA | | | Corp. | 4/25C | | | | 486SL/25 | | | | Active | | | | Matrix | | +------------------+--------------+--------------+ | Compaq Computer | CONTURA | See Note 1. | | Corp. | 4/25cx | | +------------------+--------------+--------------+ | Compudyne | 4SL/25 | BIOS | | | SubNOTEBOOK | information | | | | displayed on | | | | start up: | | | | | | | | PhoenixBIOS|TM) LAP486SL | | | Version 1.0| | | | PhoenixMISE|(TM) 486L v2.0 | | | 80486SL BIO| | | | Version 1.1| 5/28/93 +------------------+--------------+--------------+ | Gateway 2000, | ColorBook | | | Inc. | 486SX/25 | | | | 486SX/25 | | | | Dual Scan | | | | Color | | +------------------+--------------+--------------+ | Gateway 2000, | ColorBook | See Note 1. | | Inc. | 486DX/33 | Requires | | | 486DX/33 | corrected | | | Dual Scan | BIOS from | | | Color | System Soft, | | | | Inc.; see | | | | Note 2. | +------------------+--------------+--------------+ | Gateway 2000, | HandBook | See Note 1. | | Inc. | 486DX2/40 | Requires | | | 486DX2/40 | corrected | | | Monochrome | BIOS from | | | | System Soft, | | | | Inc.; see | | | | Note 2. | +------------------+--------------+--------------+ | IBM Corporation | P/S NOTE | For OS/2 | | | 425, 425c | 2.11, use F1 | | | | to display | | | | the | | | | configuration| | | | panel and | | | | set Resume | | | | on Alarm to | | | | OFF when | | | | running the | | | | Alarm | | | | applet. | +------------------+--------------+--------------+ | IBM Corporation | ThinkPad | Version 1.2 | | | 700, 700C, | of the | | | 720, 720C, | reference | | | 750 | and | | | | diagnostic | | | | diskettes | | | | are | | | | required. | +------------------+--------------+--------------+ | NCR Corporation | NCR(**) 3150 | BIOS | | | 486SX/25 | information | | | Active | displayed on | | | Matrix Color | start up: | | | | | | | | PhoenixBIOS|TM) A486 | | | Version 1.0| | | | (C)1989-199| | | | Phoenix Tec|nologies Ltd. | | | All Rights |eserved. | | | Reference I| 15 +------------------+--------------+--------------+ | NCR Corporation | SAFARI | Battery | | | | Life, Power | | | | Source, and | | | | Battery | | | | State | | | | information | | | | is | | | | incorrect. | +------------------+--------------+--------------+ | NEC Corporation | UltraLite | | | | Versa | | +------------------+--------------+--------------+ | Sharp | 6800 | Battery | | | | Life, Power | | | | Source, and | | | | Battery | | | | State | | | | information | | | | might be | | | | incorrect. | +------------------+--------------+--------------+ | Texas | TravelMate(**| | | Instruments, | 4000, | | | Inc. | 486DX2, | | | | 50MHz | | +------------------+--------------+--------------+ | Toshiba | T1950, | | | Corporation | T1950CS, | | | | T1950CT | | | | 486DX2/40 | | | | Mono, Dual | | | | Scan Color, | | | | Active | | | | Matrix Color | | +------------------+--------------+--------------+ | Toshiba | T3400, | | | Corporation | T3400CT | | | | 486SX/33 | | | | Monochrome, | | | | Active | | | | Matrix Color | | +------------------+--------------+--------------+ | Toshiba | T4700CS | | | Corporation | 486DX2/50 | | | | Dual Scan | | | | Color | | +------------------+--------------+--------------+ | Toshiba | T4700CT | | | Corporation | 486DX2/50 | | | | Active | | | | Matrix Color | | +------------------+--------------+--------------+ | Toshiba | T6600C, | | | Corporation | T6600C/CD, | | | | T6600C/CDV | | | | 486DX2/66 | | | | Active | | | | Matrix Color | | +------------------+--------------+--------------+ | Twinhead Corp. | SubNote | Does not | | | 486DX/33 | have the CPU | | | 486DX/33 | clock | | | Monochrome | slowdown | | | | feature; see | | | | Note 3. | +------------------+--------------+--------------+ | Zenith | MastersPort | | | Electronics | 386SLe | | | Corp. | | | +------------------+--------------+--------------+ | Zenith | ZNOTE 325L | | | Electronics | | | | Corp. | | | +------------------+--------------+--------------+ Note 1: To run OS/2 2.11 in these models, change the "BASEDEV=IBM1S506.ADD" statement in CONFIG.SYS to the following: BASEDEV=IBMINT13.I13 Note 2: For these models, the following BIOS information is displayed on start up: Systems Soft Bios for 80486/82C463 v1.01 (2069-09) Contact Systems Soft, Inc. (508-651-0088) for a corrected version of BIOS. Note 3: The OS/2 APM calls the BIOS APM once per second to check if it is OK to do a suspend. The following BIOS do not return OK to suspend if the video display is active or changes during the CMOS suspend timeout: o PhoenixBIOS Version 1.03 o Phoenix NoteBIOS 486/OPTi463 Version 1.03 o PhoenixMISER V2.0 Laptop Computers without APM Support The table that follows lists the laptop computers that do not have APM support in their BIOS; however, they can be configured to run OS/2 2.11 if APM is not installed. (This list represents only systems tested as of January 27, 1994.) If you have installed OS/2 APM, ensure that it is removed properly by doing the following: o Remove the following two APM device statements from CONFIG.SYS: DEVICE=C:\OS2\APM.SYS DEVICE=C:\OS2\MDOS\VAPM.SYS o Delete the APM.SYS and VAPM.SYS files from the corresponding hard-disk subdirectories. This gains about 1 second in startup and frees up hard-disk space. +------------------+--------------+--------------+ | Manufacturer | Model | Comments | +------------------+--------------+--------------+ | Compaq Computer | LTE-386s/25 | See Note 1. | | Corp. | | | +------------------+--------------+--------------+ | Compaq Computer | LTE LITE | See Note 1. | | Corp. | 25/c 386SL | | +------------------+--------------+--------------+ | Compaq Computer | LTE LITE | See Note 1. | | Corp. | 4/25e, | | | | 4/25c, | | | | 486SL/25 | | | | Active | | | | Matrix | | +------------------+--------------+--------------+ | Compudyne | 3SXL/25 | BIOS | | | SLIMNOTE | information | | | | displayed on | | | | start up: | | | | | | | | PhoenixBIOS|TM) for | | | VLSI Laptop|80386 BIOS | | | Version 1.0| R2-1 06/09/92 +------------------+--------------+--------------+ | IBM Corporation | L40SX | Discontinued | | | | product. | | | | See Note 2. | +------------------+--------------+--------------+ | IBM Corporation | P/S NOTE, | For OS/2 | | | Model 2141 | 2.11, use F1 | | | | to get the | | | | configuration| | | | panel and | | | | set Resume | | | | on Ring and | | | | Resume on | | | | Alarm to | | | | OFF. | +------------------+--------------+--------------+ | IBM Corporation | PS/2 N51 | Install | | | 386SX/SLC | using | | | 8551-025 | UINSTALL. | +------------------+--------------+--------------+ | Librex | T386SX | If screen is | | | | black after | | | | resume, | | | | toggle the | | | | F1 key | | | | (Suspend | | | | key) to | | | | refresh | | | | screen. | +------------------+--------------+--------------+ | Northgate | ZX Portable | BIOS | | Computer Systems | 486SX/25 | information | | | | displayed on | | | | start up: | | | | | | | | Phoenix A48| version 1.01 | | | | | | | See Note 3. | +------------------+--------------+--------------+ | Texas | TravelMate | See Note 3. | | Instruments, | 4000 WinDX2, | | | Inc. | 486DX/25 MHz | | +------------------+--------------+--------------+ | Texas | TravelMate | See Note 3. | | Instruments, | 4000 | | | Inc. | WinSX(**) | | +------------------+--------------+--------------+ | Texas | TravelMate | See Note 3. | | Instruments, | 4000e SX25 | | | Inc. | Passive | | | | Matrix Color | | +------------------+--------------+--------------+ | Texas | TravelMate | See Note 3. | | Instruments, | 4000e | | | Inc. | WinDX2/50 | | | | Active Color | | +------------------+--------------+--------------+ | Texas | TravelMate | See Note 3. | | Instruments, | 4000 | | | Inc. | WinDX2/50 | | | | 486DX2/50 | | | | Monochrome | | +------------------+--------------+--------------+ | Toshiba | T1800 | See Note 4. | | Corporation | 386SX/20 | | | | Monochrome | | +------------------+--------------+--------------+ | Toshiba | T1850, | See Note 4. | | Corporation | T1850C | | | | 386SX/25 | | | | Monochrome, | | | | Dual Scan | | | | Color | | +------------------+--------------+--------------+ | Toshiba | T1900, | See Note 4. | | Corporation | T1900C | | | | 486SX/20 | | | | Monochrome, | | | | Dual Scan | | | | color | | +------------------+--------------+--------------+ | Toshiba | T2200SX | See Note 4. | | Corporation | 386SX/20 | | | | Monochrome | | +------------------+--------------+--------------+ | Toshiba | T3100SX | See Note 4. | | Corporation | 386SX/16 | | | | Mono Plasma | | +------------------+--------------+--------------+ | Toshiba | T3300SL | See Note 5. | | Corporation | 386SL/20 | | | | Monochrome | | +------------------+--------------+--------------+ | Toshiba | T4400SX, | See Note 4. | | Corporation | T4400SXP, | | | | T4400SXC | | | | 486SX/25 | | | | Mono, | | | | Plasma, | | | | Active | | | | Matrix Color | | +------------------+--------------+--------------+ | Toshiba | T4400C | See Note 4. | | Corporation | 486DX/33 | | | | Active | | | | Matrix Color | | +------------------+--------------+--------------+ | Toshiba | T4500, | See Note 4. | | Corporation | T4500C | | | | 486SX/20 | | | | Monochrome, | | | | Active | | | | Matrix Color | | +------------------+--------------+--------------+ | Toshiba | T4600, | See Note 5. | | Corporation | T4600C | | | | 486SL/33 | | | | Monochrome, | | | | Active | | | | Matrix Color | | +------------------+--------------+--------------+ Note 1: To run OS/2 2.11 in these models, change the "BASEDEV=IBM1S506.ADD" statement in CONFIG.SYS to the following: BASEDEV=IBMINT13.I13 Note 2: For OS/2 2.11 APM, access the IBM BBS and download the following 3 files: o TGSFX.COM (located in file area 4) o RFL40SXA.TG0 (located in file area 27) o L40PWR.ZIP (located in file area 37) --------------- (**) NCR is a trademark of the NCR Corporation. TravelMate is a trademark of Texas Instruments, Inc. (**) WinSX is a trademark of Texas Instruments, Inc. Execute TGSFX.COM to install the TELEGET.EXE program. Then do the following: 1. Create a new L40SX reference diskette by using TELEGET.EXE to unpack RFL40SXA.TG0 onto a 1.44MB formatted diskette. 2. Use PKUNZIP to unzip the L40PWR.ZIP to obtain new IDLE.EXE and PWRMGMT.SYS files. 3. Replace the IDLE.EXE and PWRMGMT.SYS files on the newly created L40SX reference diskette with the new IDLE.EXE and PWRMGMT.SYS files obtained from the previous step. 4. Restart L40SX with the resulting reference diskette in A drive and configure with APM. 5. Verify the APM configuration by selecting VIEW configuration from the installation menu. 6. Exit the configuration. 7. Power off the computer and restart OS/2. Note 3: Contact the manufacturer for newer versions of their BIOS that have APM support. Note 4: These models require the Toshiba APM driver (OS2RES.EXE) available from the Toshiba BBS (714-837-4408). This driver will provide partial power management capabilities under OS/2 2.11. Note 5: While running OS/2, you can use the special power-saving keys but the additional capability of OS/2 protect-mode APM is not supported. APPENDIX B. ERROR MESSAGES ___________________________ > On page 422, replace the paragraph under Action: for the SYS0206E message with the following: Correct the file name or the extension; then retry the command. For more information about file names, refer to "types of files, description" in the Master Index. APPENDIX C. BACKING UP AND RESTORING YOUR DESKTOP __________________________________________________ > On page 431, replace the last note with the following: Note: The name of your DESKTOP directory might be slightly different if you use HPFS or if you previously replaced your desktop. To find the actual name of your DESKTOP directory currently in use, display the Settings notebook for the desktop and select the File page. The current desktop name is shown under Physical name. > On page 431, replace the last line with the following: BACKUP C:\OS2\DESKTOP A: /S > On page 433, replace lines #10, #11, and #12 with the following instructions: 10. Delete the existing desktop directory and its subdirectories. 11. Use the RESTORE command to copy the DESKTOP directory and its subdirectories from the diskette to the hard drive. RESTORE A: C:\OS2\DESKTOP /S This will ensure that the desktop folders are displayed correctly. 12. Remove the diskette from drive A. 13. Press Ctrl+Alt+Del to restart the computer. APPENDIX F. REMOVING PROGRAMS ______________________________ > On page 453, replace the bit-map paths with the following: \OS2\BITMAP\BLOCKS.BMP \OS2\BITMAP\BOX.BMP \OS2\BITMAP\BRICK.BMP \OS2\BITMAP\BUTTERFL.BMP \OS2\BITMAP\COLUMNS.BMP \OS2\BITMAP\DELFT.BMP \OS2\BITMAP\FLAMINGO.BMP \OS2\BITMAP\FLEUR.BMP \OS2\BITMAP\LEAVES.BMP \OS2\BITMAP\LINES.BMP \OS2\BITMAP\LINKS.BMP \OS2\BITMAP\MAZE.BMP \OS2\BITMAP\MERCADO.BMP \OS2\BITMAP\ORCHIDS.BMP \OS2\BITMAP\ROOF.BMP \OS2\BITMAP\SCALES1.BMP \OS2\BITMAP\SCALES2.BMP \OS2\BITMAP\SHELL.BMP \OS2\BITMAP\SPIRAL.BMP \OS2\BITMAP\STARS.BMP \OS2\BITMAP\TILE.BMP \OS2\BITMAP\TOOTH.BMP \OS2\BITMAP\WAVE.BMP \OS2\BITMAP\WEBB.BMP \OS2\BITMAP\ZIGZAG.BMP > On page 455, replace the RIPL .HLP path with the following: \OS2\INSTALL\RIPLINST.HLP > On page 455, replace the TUTORIAL.HLP path with the following: \OS2\HELP\TUTORIAL\TUTORIAL.HLP > On page 456, replace the KLONBGA.DLL path with the following: \OS2\APPS\DLL\KLONBGA.DLL > On page 456, replace the NEKO.DLL path with the following: \OS2\APPS\DLL\NEKO.DLL > On page 458, replace the PMSEEK.DLL path with the following: \OS2\APPS\DLL\PMSEEK.DLL > On page 458, replace the .DLL paths for Scramble with the following: \OS2\APPS\DLL\SCRAMBLE.DLL \OS2\APPS\DLL\SCRCATS.DLL \OS2\APPS\DLL\SCRLOGO.DLL > Starting on page 458, replace the .DLL paths for SoftTerm with the following: \OS2\APPS\DLL\CTLSACDI.DLL \OS2\APPS\DLL\OACDISIO.DLL \OS2\APPS\DLL\OANSI.DLL \OS2\APPS\DLL\OANSI364.DLL \OS2\APPS\DLL\OCHAR.DLL \OS2\APPS\DLL\OCM.DLL \OS2\APPS\DLL\OCOLOR.DLL \OS2\APPS\DLL\OCSHELL.DLL \OS2\APPS\DLL\ODBM.DLL \OS2\APPS\DLL\OFMTC.DLL \OS2\APPS\DLL\OIBM1X.DLL \OS2\APPS\DLL\OIBM2X.DLL \OS2\APPS\DLL\OKB.DLL \OS2\APPS\DLL\OKBC.DLL \OS2\APPS\DLL\OKERMIT.DLL \OS2\APPS\DLL\OLPTIO.DLL \OS2\APPS\DLL\OMCT.DLL \OS2\APPS\DLL\OMRKCPY.DLL \OS2\APPS\DLL\OPCF.DLL \OS2\APPS\DLL\OPM.DLL \OS2\APPS\DLL\OPROFILE.DLL \OS2\APPS\DLL\ORSHELL.DLL \OS2\APPS\DLL\OSCH.DLL \OS2\APPS\DLL\OSIO.DLL \OS2\APPS\DLL\OSOFT.DLL \OS2\APPS\DLL\OTEK.DLL \OS2\APPS\DLL\OTTY.DLL \OS2\APPS\DLL\OVIO.DLL \OS2\APPS\DLL\OVM.DLL \OS2\APPS\DLL\OVT.DLL \OS2\APPS\DLL\OXMODEM.DLL \OS2\APPS\DLL\OXRM.DLL \OS2\APPS\DLL\SACDI.DLL \OS2\APPS\DLL\SAREXEC.DLL Appendix A. Notices References in this publication to IBM products, programs, or services do not imply that IBM intends to make these available in all countries in which IBM operates. Any reference to an IBM product, program or service is not intended to state or imply that only IBM's product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any of IBM's intellectual property rights or other legally protectable rights may be used instead of the IBM product, program, or service. Evaluation and verification of operation in conjunction with other products, programs, or services, except those expressly designated by IBM, are the user's responsibility. IBM may have patents or pending patent applications covering subject matter in this document. The furnishing of this document does not give you any license to these patents. You can send license inquiries, in writing, to the IBM Director of Licensing, IBM Corporation, 208 Harbor Drive, Stamford, Connecticut 06904-2501, USA. TRADEMARKS AND SERVICE MARKS ____________________________ The following terms, denoted by an asterisk (*) in this publication, are trademarks or service marks of the IBM Corporation in the United States or other countries: AT IBM Micro Channel OS/2 PS/1 PS/2 ThinkPad Ultimotion WIN-OS/2 XGA The following terms, denoted by a double asterisk (**) in this publication, are trademarks of other companies as follows: Trademark Owner Adaptec Adaptec, Inc. Allways Funk Software, Inc. AMI American Megatrends, Inc. ATI ATI Technologies, Inc. Central Point Central Point Software, Inc. Compaq Compaq Computer Corporation CorelDraw Corel Systems Corporation Docking Station NEC Home Electronics, Inc. Future Domain Future Domain Corporation Gateway Gateway Systems Corporation Gateway 2000 Gateway 2000, Inc. Hitachi Hitachi Ltd. HYPERACE Hypertec Pty. Limited Lexmark Lexmark International, Inc. McAfee McAfee Associates. Media Vision Media Vision, Inc. Micropolis Micropolis Corporation Microsoft Microsoft Corporation Mitsumi Mitsumi Denki Kabushki Kaisha MS Microsoft Corporation MS-DOS Microsoft Corporation NCR NCR Corporation NetWare Novell, Inc. Nomad Gateway 2000, Inc. Panasonic Matsushita Electric Industrial Co., Ltd. PCMCIA Personal Computer Memory Card International Association Phoenix Phoenix Technologies, Ltd. ProAudio Spectrum Media Vision, Inc. ProComm Datastorm Technologies, Inc. Quantum Quantum Corporation Sony Sony Corporation Sound Blaster Creative Labs, Inc. The Norton Antivirus Symantec Corporation TravelMate Texas Instruments, Inc. Ultra ATI Technologies, Inc. VESA Video Electronics Standards Association Windows Microsoft Corporation WinSX Texas Instruments, Inc. ΓòÉΓòÉΓòÉ <hidden> ΓòÉΓòÉΓòÉ IBM National Support Center (NSC) BBS (919) 517-0001 ΓòÉΓòÉΓòÉ <hidden> ΓòÉΓòÉΓòÉ IBM FAX-back Information Service, 1-800-IBM-4FAX.