Fixpak (XR06300A) - United States

********************** IBM ******************************************* * :nick.XR06300A :sec.IBM :disk.OS2CSD * :title.OS/2 V2.11 For Windows ServicePak XR06300 U.S.(3.50") * :version.2.11 :date.94/05/11 :summary. :support.N * :oname.OS2CSD :onode.KGNVMC :ouser.PRODCTR * :aname.PSP Local Control Group :anode.AUSVM8 :auser.AUSLCG * :ops.OS/2 V2.11 For Windows * :abs.This ServicePak contains the fixes for OS/2 version 2.11 for * Windows. Also included are Display Drivers, and Printer Drivers., * A list of APARS that are included in this ServicePak is located in * the XR06300.XRF which is on the last ServicePak diskette (twelve) * of this package in the \FIX\OS2\ Directory. * Pertinant information regarding this ServicePak may be obtained from * README and README.INS located on Diskette one. Also review XR06300 * AVAIL that accompanies this package. * * 5.25" media may be obtained by ordering XR06300. ************************************************************************* * Diskettes can be created using the LOADDSKF utility, this utility * may be obtained from the /ps/tools directory. * There are 23 files/images included in this package. ************************************************************************* * The diskettes contained in this package may be distributed to * IBM customers who are already licensed owners of OS/2 Version 2.1 * For Windows by IBM marketing personnel authorized to service that * customer. ************************************************************************ XR06300 AVL * ServicePak information (ascii) XR06300A LAB * Diskette Labels for ServicePak (ascii) DOC211 ZIP * OS/2 2.1 Installation guide (binary) 06300B1 DSK * Disk 1 of 12, ServicePak Diskette CRC=X'9403' (binary) 06300B2 DSK * Disk 2 of 12, ServicePak Diskette CRC=X'87A8' (binary) 06300B3 DSK * Disk 3 of 12, ServicePak Diskette CRC=X'DFCB' (binary) 06300B4 DSK * Disk 4 of 12, ServicePak Diskette CRC=X'5529' (binary) 06300B5 DSK * Disk 5 of 12, ServicePak Diskette CRC=X'ED14' (binary) 06300B6 DSK * Disk 6 of 12, ServicePak Diskette CRC=X'537D' (binary) 06300B7 DSK * Disk 7 of 12, ServicePak Diskette CRC=X'ABFD' (binary) 06300B8 DSK * Disk 8 of 12, ServicePak Diskette CRC=X'8856' (binary) 06300B9 DSK * Disk 9 of 12, ServicePak Diskette CRC=X'F46E' (binary) 06300B10 DSK * Disk 10 of 12, ServicePak Diskette CRC=X'D344' (binary) 06300B11 DSK * Disk 11 of 12, ServicePak Diskette CRC=X'0DCE' (binary) 06300B12 DSK * Disk 12 of 12, ServicePak Diskette CRC=X'7A46' (binary) 06300B13 DSK * Disk 01 of 03, Printer Driver Disk CRC=X'2CB2' (binary) 06300B14 DSK * Disk 02 of 03, Printer Driver Disk CRC=X'1AAF' (binary) 06300B15 DSK * Disk 03 of 03, Printer Driver Disk CRC=X'3B11' (binary) 06300B16 DSK * Disk 01 of 03, Display Driver Disk CRC=X'D268' (binary) 06300B17 DSK * Disk 02 of 03, Display Driver Disk CRC=X'A439' (binary) 06300B18 DSK * Disk 03 of 03, Display Driver Disk CRC=X'4608' (binary) 06300B19 DSK * Disk 01 of 02, Multimedia Service CRC=X'CCB7' (binary) 06300B20 DSK * Disk 02 of 02, Multimedia Service CRC=X'B09A' (binary) * End of package * OS/2 FOR WINDOWS SERVICEPAK README Welcome to OS/2* for Windows ServicePak. It includes service updates for licensed users of OS/2 2.1 for Windows. This ServicePak allows you to continue running DOS, Windows, and OS/2 applications on the same desktop. This README contains helpful hints found in our testing as well as updated information that did not make the original OS/2 for Windows printed publications. Following are the README features: o Table of Contents (to help you access information) o Page Numbers (at the beginning of topics) - It is formatted for viewing on your display to make it easy to go directly to a specific topic. NOTE: You can use the Find option in the Edit menu of the OS/2 Editor to help you locate information in this Readme, or you can print the file. Use this information in conjunction with the "OS/2 2.1 Installation Guide", and the "OS/2 2.1 Using the Operating System" manual. Also, you should obtain the new "Updates to: Installation Guide and Using the Operating System" booklet, as instructed in "Start Here" booklet included in the ServicePak. Throughout the documentation provided with your original OS/2 for Windows product, all references to WIN-OS/2* also apply to running your Windows Version 3.1 programs under the OS/2 for Windows ServicePak. NOTE: A separate README file for MMPM/2 is contained with the MMPM/2 program. CONTENTS ________ ----------------------------------------------- SECTION 1. GENERAL CONSIDERATIONS . . . . 1 Desktop Considerations . . . . . . . . . . . . . 1 INI Files . . . . . . . . . . . . . . . . . . . 1 Running CHKDSK . . . . . . . . . . . . . . . . 2 Video . . . . . . . . . . . . . . . . . . . . . 3 System Shut Down . . . . . . . . . . . . . . . 4 Application Migration . . . . . . . . . . . . . 4 Recorder Application . . . . . . . . . . . . . 4 Screen Savers . . . . . . . . . . . . . . . . . 5 DOS Images . . . . . . . . . . . . . . . . . . 5 CD-ROM . . . . . . . . . . . . . . . . . . . . . 5 Printers . . . . . . . . . . . . . . . . . . . . 6 Scanners . . . . . . . . . . . . . . . . . . . . 7 Audio Adapters . . . . . . . . . . . . . . . . . 7 Preinstalled Systems . . . . . . . . . . . . . 12 Advanced Power Management Support for Portable Computers . . . . . . . . . . . . . . . . . . 13 Laptop Computers with APM Support . . . . . . 14 Laptop Computers without APM Support . . . . 22 International Standards Organization (ISO) Fonts 29 ----------------------------------------------- SECTION 2. DUAL BOOT OR BOOT MANAGER INFORMATION . . . . . . . . . . . . . . 31 Using Dual Boot or Boot Manager . . . . . . . . 31 ----------------------------------------------- SECTION 3. DISPLAY INFORMATION . . . . . 33 New SETVGA Procedure . . . . . . . . . . . . . 33 SVGA Information . . . . . . . . . . . . . . 35 XGA Considerations . . . . . . . . . . . . . . 36 8514 Considerations . . . . . . . . . . . . . . 38 Display Adapters (IMAGE, SVGA, XGA, 8514) . . . 39 ----------------------------------------------- SECTION 4. S3 FUNCTIONAL RESTRICTIONS . 42 After Dark . . . . . . . . . . . . . . . . . . 42 Ventura Publisher . . . . . . . . . . . . . . . 42 Lotus 1-2-3 . . . . . . . . . . . . . . . . . . 42 WordPerfect . . . . . . . . . . . . . . . . . . 43 MMPM/2 . . . . . . . . . . . . . . . . . . . . 43 ----------------------------------------------- SECTION 5. WINDOWS APPLICATION INFORMATION 45 Windows and WIN-OS/2 Application Compatibility 45 Windows and WIN-OS/2 Application Notes: . . . 48 ----------------------------------------------- SECTION 6. DOS APPLICATION INFORMATION . 54 DOS Application Compatibility . . . . . . . . . 54 DOS Application Notes: . . . . . . . . . . . 56 ----------------------------------------------- SECTION 7. OS/2 APPLICATION INFORMATION 59 OS/2 Application Compatibility . . . . . . . . 59 OS/2 Application Notes: . . . . . . . . . . . 61 ----------------------------------------------- SECTION 8. MULTIMEDIA APPLICATION INFORMATION . . . . . . . . . . . . . . 65 DOS and WIN-OS/2 Multimedia Application Compatibility . . . . . . . . . . . . . . . . 65 DOS and WIN-OS/2 Multimedia Applications Notes: 65 ----------------------------------------------- SECTION 9. NETWORK INFORMATION . . . . . 67 Netware Considerations . . . . . . . . . . . . 67 Upgrading to Netware Requester for OS/2 . . . 71 Novell DOS Requester . . . . . . . . . . . . 73 ----------------------------------------------- SECTION 10. TRADEMARKS . . . . . . . . . 78 Page 1 SECTION 1. GENERAL CONSIDERATIONS __________________________________ DESKTOP CONSIDERATIONS ______________________ INI FILES 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 you restart your system the INI files are updated. o When OS/2 for Windows ServicePak is installed as a SVGA system in 1024x768 resolution, and you dual boot to DOS in low resolution, the fonts are too large for the display. 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 dual boot back to OS/2 for Windows ServicePak, 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. Page 2 RUNNING CHKDSK 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 pop-up 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. Page 3 VIDEO 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 When you use the Windows Version 3.1 Control Panel the changes to the 386 Enhanced mode settings are ignored and you might receive an error message. Disregard the error message. o Do not run the Windows Setup program. It is recommended that you do not change your video configuration for Windows. Page 4 SYSTEM SHUT DOWN 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 complete, then press Ctrl+Alt+Del to restart your system. APPLICATION MIGRATION After installing OS/2 for Windows ServicePak 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. RECORDER APPLICATION The Recorder application located in the Accessories Program Group of your Windows product will not run with OS/2 for Windows ServicePak. Running this application can lead to undesirable and unpredictable results. Page 5 SCREEN SAVERS It is recommended that you do NOT turn "ON" the OS/2 screen savers and the Windows screen savers at the same time. DOS IMAGES 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. CD-ROM ______ 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. Page 6 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. Page 7 SCANNERS ________ If you have a Logitech hand scanner on an AT bus computer, run the scanner at the 100, 200, or 300 DPI setting. 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. Page 8 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 Page 9 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. Page 10 o 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. Page 11 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. 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. Page 12 PREINSTALLED SYSTEMS ____________________ 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. Page 13 ADVANCED POWER MANAGEMENT SUPPORT FOR PORTABLE ______________________________________________ COMPUTERS _________ This version of OS/2 for Windows ServicePak includes additional APM support that was not available for the original OS/2 2.1 release. Laptops 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 ServicePak Advanced Power Management (APM): 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 are not supported by OS/2 for Windows ServicePak 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. Page 14 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 to date.) Page 15 MANUFACTURER MODEL COMMENTS --------------------------------------------------- Acer AcerNote 730 BIOS information displayed on start up: PhoenixBIOS** A486 Version 1.03 R1.0 Acer AcerNote 750 AST Research PowerExec 4/25SL Inc. 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 Page 16 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** LAP486SL Version 1.03 PhoenixMISER** 486L v2.0 80486SL BIOS Version 1.11 5/28/93 Gateway 2000 ColorBook 486SX/25 486SX/25 Dual Scan Color Page 17 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 ServicePak use F1 to display the configuration panel and set RESUME ON ALARM to OFF when running the Alarm mini-application. Page 18 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** 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. Page 19 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 Page 20 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 Page 21 NOTES: 1. To run OS/2 for Windows ServicePak in these models, change the statement "BASEDEV=IBM1S506.ADD" in CONFIG.SYS to the following: BASEDEV=IBMINT13.I13 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. 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 4. Reinstall the ThinkPad video drivers after you finish installing OS/2 for Windows ServicePak. Page 22 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 for Windows ServicePak if APM is not installed. (This list represents only systems tested to date.) 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. Page 23 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** for VLSI Laptop 80386 BIOS Version 1.01 R2-1 06/09/92 IBM L40SX Discontinued product. See NOTE 2. Page 24 IBM P/S NOTE, Model For OS/2 for Windows 2141 ServicePak 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 UNINSTALL. 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. Page 25 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 Page 26 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 Page 27 Toshiba T4600, T4600C See NOTE 5. 486SL/33 Monochrome, Active Matrix Color NOTES: 1. To run OS/2 for Windows ServicePak in these models, change the statement "BASEDEV=IBM1S506.ADD" in CONFIG.SYS to the following: BASEDEV=IBMINT13.I13 2. For OS/2 for Windows ServicePak 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) Execute TGSFX.COM to install the TELEGET.EXE program. Then do the following: Page 28 a. Create a new L40SX reference diskette by using TELEGET.EXE to unpack RFL40SXA.TG0 onto a 1.44MB formatted diskette. b. Use PKUNZIP to unzip the L40PWR.ZIP to obtain new IDLE.EXE and PWRMGMT.SYS files. c. 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. d. Restart L40SX with the resulting reference diskette in A drive and configure with APM. e. Verify the APM configuration by selecting VIEW CONFIGURATION from the installation menu. f. Exit the configuration. g. Power off the computer and restart OS/2. 3. Contact the manufacturer for newer versions of their BIOS that have APM support. 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 ServicePak. 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. Page 29 INTERNATIONAL STANDARDS ORGANIZATION (ISO) FONTS ________________________________________________ OS/2 for Windows ServicePak 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. Page 30 /* */ 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. Page 31 SECTION 2. DUAL BOOT OR BOOT MANAGER _____________________________________ INFORMATION ___________ USING DUAL BOOT OR 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 to have similar statements as in the Windows** version of these files. Page 32 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. Page 33 SECTION 3. DISPLAY INFORMATION _______________________________ 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 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 Diskette 8 C: is the drive where OS/2 2.1 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:\; then press Enter /T:\ where C: is the drive where OS/2 2.1 is installed /S:A: where A: is the diskette drive you use to install OS/2 Page 34 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:\; then press Enter /T:\ where C: is the drive where OS/2 2.1 is installed /S:E: where E: is the CD-ROM or LAN drive Page 35 SVGA INFORMATION 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 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. Page 36 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 damage when the XGA display is set to a resolution with 65536 colors. This damage 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. Page 37 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 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 When running VGA DOS graphics applications on the OS/2 desktop without VGA support, your desktop might be damaged. Page 38 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. Page 39 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. Page 40 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. Page 41 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 for Windows ServicePak. 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. Page 42 SECTION 4. S3 FUNCTIONAL RESTRICTIONS ______________________________________ AFTER DARK __________ After Dark** for Windows** images that move from left to right do not perform properly at 640x480x16M resolution. VENTURA PUBLISHER _________________ To avoid a General Protection fault while loading Ventura Publisher** for Windows be sure it is in one of the 256 color resolutions. LOTUS 1-2-3 ___________ To avoid a trap in Lotus** 1-2-3** for OS/2 do not attempt to run the program at 16.7 million colors. Page 43 WORDPERFECT ___________ 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. MMPM/2 ______ 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. An OS/2 2.1 pervasive fix package is now available electronically. 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. Page 44 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. Page 45 SECTION 5. WINDOWS APPLICATION INFORMATION ___________________________________________ WINDOWS AND 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. 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. Page 46 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 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. Page 47 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 for Windows ServicePak 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. Page 48 WINDOWS AND WIN-OS/2 APPLICATION NOTES: o Access Dr. Watson** Hollywood** WinRoach** Run in a WIN-OS/2 full-screen session. o 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 o 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. Page 49 o Borland Turbo and Pascal debugger Run in a full-screen session. o CorelDRAW** 2.0 Install from a DOS or OS/2 session. o 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. Page 50 o 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. o FoxPro** 2.5 Install using a WIN-OS/2 Enhanced-compatibility mode session, but run in a WIN-OS/2 standard-mode session o FrameMaker** Use a mouse to select table cells. Page 51 o 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. o Lotus Freelance Graphics** 2.0 If you are running Lotus Freelance Graphics 2.0 on any machine with an Intel** 386 16Mhz, it is recommended that you use a Math Coprocessor. o Lotus** Improv 2.0 for Windows Must be installed with WIN-OS/2 running in enhanced mode, to install and configure correctly. o Mathematica** 2.2 Must be run in a WIN-OS/2 window session. Page 52 o 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. o Norton Desktop** 2.0 Run in a WIN-OS/2 full-screen standard-mode session. o 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. o 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. Page 53 o Windows** Version 3.1 with Pen Extensions Not supported. o WindowWorks** Install in a WIN-OS/2 full-screen session. o WinTach** Run this application in a WIN-OS/2 full screen session. Page 54 SECTION 6. DOS APPLICATION INFORMATION _______________________________________ 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 by pressing and holding Ctrl + Alt keys; then press Del. Page 55 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. Page 56 DOS APPLICATION NOTES: o 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. o Fotoman** If you have problems running Fotoman, set the DOS COM_DIRECT_ACCESS setting ON. o Paradox V4.0 If you have problems running Paradox V4.0 change the DOS setting DPMI_DOS_API = ENABLE. o Wayne Gretzky's Hockey Game Not supported. Page 57 o Wing Commander** II Set HW_TIMER to OFF. o WordPerfect V6.0 - If you have problems running WordPerfect V6.0 change the DOS setting DOS_FILES = >99. - If you are using an OS/2 integration disk and if you created a WordPerfect printer, the drag-drop method might not work. You can use the WordPerfect print pull-down from the title bar, or the drag-drop method on an OS/2 for Windows printer object. o Terminator game Must use a joystick. o 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. o Microsoft MSCDEX Change the DOS INT_DURING_IO setting to ON. Page 58 o 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. 6. Change the value of the DOS_AUTOEXEC setting for the object to FAX.BAT. 7. Save and exit the Settings notebook. Page 59 SECTION 7. OS/2 APPLICATION INFORMATION ________________________________________ OS/2 APPLICATION COMPATIBILITY ______________________________ 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. Page 60 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 for Windows ServicePak. 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. Page 61 OS/2 APPLICATION NOTES: o 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 o 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 appears 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. Page 62 o 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. o 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 for Windows ServicePak 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 for Window ServicePak level of MIRRORS.DLL with the backed up copy you previously created. Page 63 o 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. o IBM LAN Server 3.0 Remote Installation Program Load (RIPL) An updated version from version 3.0 is needed to run with OS/2 for Windows ServicePak. 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 for Windows ServicePak. Page 64 o 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. Page 65 SECTION 8. MULTIMEDIA APPLICATION INFORMATION ______________________________________________ DOS AND WIN-OS/2 MULTIMEDIA APPLICATION COMPATIBILITY _____________________________________________________ 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 DOS AND WIN-OS/2 MULTIMEDIA APPLICATIONS NOTES: o 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:\ Page 66 o Animation Works** 1.0 Run in 1024x768 resolution. o 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. o Linkway** Live 1.0 (Tool Series) Use the following DOS setting to make the demo run properly: DOS_RMSIZE=576 o MIDI Make sure that the MIDI mapper and channels (in the Control Panel) is properly set to the sound adapter. o Nautilus** 1.6 and 1.76 Run in a WIN-OS/2 full-screen session. Page 67 SECTION 9. NETWORK INFORMATION _______________________________ NETWARE CONSIDERATIONS ______________________ 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 for Windows ServicePak. 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. Page 68 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. Page 69 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), type, REM next to 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. Page 70 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 utility, 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. Page 71 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. Page 72 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. Page 73 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 for Windows ServicePak 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 Page 74 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 for Windows ServicePak 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 Page 75 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. Page 76 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. Page 77 o Dual Boot If you install OS/2 for Windows ServicePak 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. 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 that attempts to utilize the LAN adapter such as Communications Manager. Using the NetWare Requester for the OS/2 operating system might remove some of the limitations of this configuration. Page 78 SECTION 10. 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 LinkWay Micro Channel Presentation Manager NetView 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: Page 79 Trademark: Owner: ------------------------------------------------------------- Action! Expertelligence ALR Advanced Logic Research, Inc. AmiPro Lotus Development Corporation Animation Works Gold Disk Inc. ATI ATI Technologies, Inc. Borland Borland International, Inc. C++ AT&T, Inc. Canon Canon Kabushiki Kaisha CompuServe CompuServe Incorporated CorelDRAW Corel Systems Corporation DeScribe Lenname Advanced Products DeskJet Hewlett-Packard Company Dr Watson Empirical Tools and Technology Facelift Bitstream Inc. FlexView Advanced Logic Research Inc. FormBase Xerox Corporation FotoMan Logitech International FoxPro Fox Software, Inc. FrameMaker Frame Technology Inc. Freelance Graphics Lotus Development Corporation Hollywood Claris Corporation HP Hewlett-Packard Company LaserJet Hewlett-Packard Company IconAuthor AimTech Corporation Intel Intel Corporation Legend Sigma Designs Inc. Logitech Logitech, Inc. Lotus Lotus Development Corporation Page 80 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 Panasonic Matsushita Electric Industrial Co., Ltd. Paradox Borland International, Inc. PostScript Adobe Systems Inc. PowerPoint Microsoft Corporation SatisFAXtion Intel 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 Wing Commander Origins Systems, Inc. WinTach Texas Instrument WordPerfect WordPerfect Corporation Zenith Data Systems Zenith Electronics Corporation ZEOS ZEOS International Ltd. Page 81 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. OS/2 FOR WINDOWS SERVICEPAK INSTALLATION README Welcome to OS/2* for Windows ServicePak. It includes service updates for licensed users of OS/2 2.1 for Windows. This ServicePak allows you to continue running DOS, Windows, and OS/2 applications on the same desktop. This README information is for use after installing the OS/2 for Windows ServicePak. It contains helpful hints found in our testing as well as updated information that did not make the original OS/2 for Windows printed publications. Following are the README features: o Table of Contents (to help you access information) o Page Numbers (at the beginning of topics) - It is formatted for viewing on your display to make it easy to go directly to a specific topic. NOTE: You can use the Find option in the Edit menu of the OS/2 Editor to help you locate information in this Readme, or you can print the file. Use this information in conjunction with the "OS/2 2.1 Installation Guide", and the "OS/2 2.1 Using the Operating System" manual. Also, you should obtain the new "Updates to: Installation Guide and Using the Operating System" booklet, as instructed in the "Start Here" booklet included in the ServicePak. Throughout the documentation provided with your original OS/2 for Windows product, all references to WIN-OS/2* also apply to running your Windows Version 3.1 programs under the OS/2 for Windows ServicePak. CONTENTS ________ ----------------------------------------------- SECTION 1. GENERAL CONSIDERATIONS . . . . 1 PCMCIA Communication Device . . . . . . . . . . . 1 ThinkPad 750c . . . . . . . . . . . . . . . . . . 2 Desktop . . . . . . . . . . . . . . . . . . . . 3 Printers . . . . . . . . . . . . . . . . . . . . 4 Extended Services (ES) 1.0 . . . . . . . . . . . 6 Preinstalled Systems . . . . . . . . . . . . . . 7 Ultimedia . . . . . . . . . . . . . . . . . . 10 ----------------------------------------------- SECTION 2. SPECIAL INSTALLATION PROCEDURES 11 General Video Support . . . . . . . . . . . . . 11 Installing Device Drivers Using Selective Install 12 SCSI-Based CD-ROM Support . . . . . . . . . . . 13 New CD-ROM Drives Support . . . . . . . . . . 14 New SCSI Drives Supported . . . . . . . . . . 15 Obtaining Additional CD-ROM Support . . . . . 16 Installing with CID and SEMAINT . . . . . . . . 17 CID and NVDM/2 Notes . . . . . . . . . . . . . 18 LCU Examples and NVDM/2 Examples . . . . . . . 19 LCU CID Option . . . . . . . . . . . . . . . 19 LCU S2 Option . . . . . . . . . . . . . . . . 19 NVDM/2 CID Option . . . . . . . . . . . . . . 20 NVDM/2 S2 Option . . . . . . . . . . . . . . 20 Installing OS/2 for Windows ServicePak using RIPL 21 ----------------------------------------------- SECTION 3. GENERAL DISPLAY DRIVERS/ADAPTERS SUPPORT . . . . . . . . 23 DPMS-Supported Displays . . . . . . . . . . . . 23 General Display Adapter Support . . . . . . . . 24 Installation of Specific Video Adapters . . . 24 Installing High-Resolution and Color . . . . . . 25 IHV Display Drivers Tested by IBM . . . . . . 25 ----------------------------------------------- SECTION 4. S3 VIDEO INFORMATION . . . . 39 S3 IBM Tested Display Adapters . . . . . . . . 30 S3 Video Accelerator Driver for OS/2 for Windows ServicePak . . . . . . . . . . . . . . . . . . 33 S3 Graphics and Color Resolution Support . . 34 S3 Driver Installation . . . . . . . . . . . . 35 S3 Installation from Diskette . . . . . . . . 36 S3 Installation from CD-ROM . . . . . . . . . 37 S3 Installation in a CID Environment . . . . 38 ----------------------------------------------- SECTION 5. TRADEMARKS . . . . . . . . . 42 Page 1 SECTION 1. GENERAL CONSIDERATIONS __________________________________ PCMCIA COMMUNICATION DEVICE ___________________________ If you 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 before the COM.SYS device statement, or your communications device might not function. Page 2 THINKPAD 750C ____________________________ o After installing this version of the ServicePak, you might find that your DOS full screen session does not work correctly. To fix this problem: - You MUST reinstall the video driver from the ThinkPad video features diskette. o If you experience a video problem with the ThinkPad 750c, do the following: 1. Start your system using the Installation diskette 2. Type SETVGA X: (where X=your OS/2 start up drive) and then press Enter 3. Edit your CONFIG.SYS file type: REM in front of the following statements: SET SPRITEENABLE=ON RUN=CHKRES.EXE SET HARDWAREBITBLIT=ON 4. Restart your system, then reinstall the ThinkPad 750c video drivers. o If you are using an IOMEGA PC Powered Pro 9 adapter, you must call the IOMEGA service number and request OAD Driver Version 2.3. Page 3 DESKTOP ______________________ o You will notice that the default color scheme has changed for OS/2 for Windows ServicePak. o After you install this ServicePak, 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 while booting your system. This will restore your CONFIG.SYS and your OS/2 system INI files from the \OS2\INSTALL directory which were saved prior to installing this ServicePak. Page 4 PRINTER _______________________ If you need to add a Windows printer driver after installing this ServicePak, 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. The OS/2 printer drivers on the OS/2 for Windows ServicePak 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 for Windows ServicePak 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 for Windows ServicePak installed. You do not have to complete these steps to install a printer driver on a system that already has OS/2 for Windows ServicePak installed. NOTE: Do not install the new 32-bit PostScript driver (PSCRIPT.DR_) that came with OS/2 for Windows ServicePak 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. Page 5 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 for Windows ServicePak installed. 1. Open the OS/2 System folder. 1. Open the OS/2 Command Prompt folder. 2. At the command prompt type: MD X:\DRIVER Where X is a drive on your system. 3. Insert into drive A the OS/2 for Windows ServicePak 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_ 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. Page 6 EXTENDED SERVICES (ES) 1.0 _________________________________________ If you installed OS/2 for Windows ServicePak 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 for Windows ServicePak. (The ESSTART.BAK file is located in the OS2\INSTALL subdirectory.) If you are installing Extended Services over OS/2 for Windows ServicePak for the first time (that is, there is no Extended Services on the workstation), or if you are installing Extended Services from diskettes: 1. Rename the existing ESSTART.CMD file from the Extended Services Diskette 1. 2. Copy the file ESSTART.BAK from the \OS\INSTALL directory to Extended Services Diskette 1. 3. Rename the ESSTART.BAK file ESSTART.CMD 4. Begin the installation of Extended Services. Page 7 PREINSTALLED SYSTEMS ___________________________________ 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 step 4 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\*.* Page 8 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. Page 9 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. NOTE: 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. Page 10 ULTIMEDIA 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. Page 11 SECTION 2. SPECIAL INSTALLATION PROCEDURES ___________________________________________ GENERAL VIDEO SUPPORT _____________________ The following information pertains to video support for the OS/2 for Windows ServicePak. 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. Page 12 INSTALLING DEVICE DRIVERS USING SELECTIVE INSTALL _________________________________________________ If you are using Selective Install to install device drivers after installing 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 for Windows Installation diskettes. (The ServicePak 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 this ServicePak. 8. Shutdown and restart the computer to activate the changes. Page 13 SCSI-BASED CD-ROM SUPPORT _________________________ The majority of SCSI-based CD-ROM drives and adapters are supported by OS/2 for Windows ServicePak. ("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 for Windows can be found in the "Hardware Support" chapter of the "OS/2 2.1 Using the Operating System" manual and the "Updates to: Installation Guide and Using the Operating System" manual. Additional support of new CD-ROM drives and new SCSI drives certified for OS/2 for Windows are supported by this ServicePak. Following is a list of the new drives supported. Page 14 NEW CD-ROM DRIVES SUPPORT New drives supported in OS/2 for Windows 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 Page 15 NEW SCSI DRIVES SUPPORTED New SCSI drives certified to work in OS/2 for Windows ServicePak. Vendor CD-ROM Drive Model --------------------------------- IBM Enhanced CD-ROM II NEC MultiSpin 3Xe NEC MultiSpin 3Xi NEC MultiSpin 3Xp Philips LMS CM215 Texel DM-3028 Texel DM-5028 Page 16 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 for Windows ServicePak, 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. Page 17 INSTALLING WITH CID AND SEMAINT _______________________________ 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 megabyte 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. If you have a maintenance system installed with the OS/2 2.1 version of SEMAINT, you must re-install using SEMAINT from this version of the ServicePak. Page 18 CID AND NVDM/2 NOTES ____________________ For LCU and NVDM/2 users, you must unpack SEMAINT.EXE from the CID tree where OS/2 for Windows ServicePak resides, to the CID Code Server, directory ?:\EXE\OS2V21. When invoking SEMAINT.EXE supplied with OS/2 for Windows ServicePak the following rules apply to your installation procedures: 1. FSERVICE.EXE corresponds to the ServicePak for the product you are installing. Therefore, you must make sure your installation procedures access the corresponding version of FSERVICE in the appropriate ServicePak Install tree. 2. When invoking FSERVICE.EXE for OS/2 for Windows ServicePak, 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 started by diskette. 3. Installation of the OS/2 for Windows ServicePak requires the specification of the "/S2:<CSDpath>" during the invocation of SEMAINT.EXE. 4. Installation of any ServicePak in your procedures FOLLOWING the installation of OS/2 for Windows ServicePak requires that the "/S2:<CSDpath>" parameter be specified during the invocation of SEMAINT.EXE. 5. Installation of any ServicePak in your procedures PRIOR to the installation of OS/2 for Windows ServicePak requires that the "/S2:<CSDpath>" parameter be omitted during the invocation of SEMAINT.EXE. Page 19 LCU EXAMPLES AND NVDM/2 EXAMPLES ________________________________ LCU CID OPTION 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' LCU S2 OPTION 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 = '' Page 20 NVDM/2 CID OPTION 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 NVDM/2 S2 OPTION 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: /S:$(SourceDir) /S2:$(SA)\IMG\CSD\OS2V21 /T:$(TargetDir) /L1:$(LogFile1) SourceDir = SA:\IMG\OS2V21 LogFile1 = SA:\LOG\OS2V21\$(WorkStatName).LOG End Page 21 INSTALLING OS/2 FOR WINDOWS SERVICEPAK USING RIPL _________________________________________________ When installing OS/2 for Windows ServicePak using the IBM LAN Server 2.0 and 3.0 Remote Installation Program Load (RIPL), the OS/2 for Windows ServicePak RIPLINST.EXE program is dependent upon the OS/2 for Windows ServicePak UNPACK.EXE file. Therefore, if you are using the OS/2 for Windows ServicePak RIPLINST.EXE program 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: Page 22 1. Insert OS/2 for Windows ServicePak 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 for Windows ServicePak RIPLINST.EXE program. Page 23 SECTION 3. GENERAL DISPLAY DRIVERS/ADAPTERS ____________________________________________ SUPPORT _______ This ServicePak updates the display driver files that came with your original OS/2 for Windows product package. (Such as the BVHVGA.DLL, BVHSVGA.DLL, VGA.SYS, and VSVGA.SYS.) If you install display drivers that replace these files after you have installed the ServicePak, the updates applied might be removed. 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. Page 24 GENERAL DISPLAY ADAPTER SUPPORT _______________________________ 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 OS/2 for Windows ServicePak 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. Page 25 INSTALLING HIGH-RESOLUTION AND COLOR ____________________________________ If you want to install a display driver that is higher than 640 x 480 x 16 and you obtained it from a source other than this ServicePak, then use the installation procedures provided in the README file that comes with the display driver. NOTE: The following information pertains to video support. 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. IHV DISPLAY DRIVERS TESTED BY IBM Following is a list of Independent Hardware Vendor (IHV) display drivers that are shipped separately from OS/2 for Windows tested by IBM to date. You might have obtained them from a Bulletin Board Service or directly from the hardware vendor. Refer to the notes following the this table for exceptions and workarounds that apply to the display drivers listed in the following table. Page 26 ___________________________________________________________ Chip Set/ Use README README Board/System provided Driver Name Date Tested on with driver ___________________________________________________________ ATI** Mach32 1-24-94 ATI Graphic Y Ultra Pro Cirrus** 542x 1-17-94 Diamond Y Speedstar Pro Compaq** QVision** 3-21-94 Compaq QVision Y Adapter IBM Image Adapter 2.00 6-4-93 Image Adapter/A Y 6-4-93 Image Adapter/I Y IBM Thinkpad 7-12-93 IBM ThinkPad Y Matrox** MGA 2-22-94 Matrox MGA Y (ULT/2/M/H) (tested on MCA** hardware only) S3** 801/805/928 9-12-93 Actix GE32 Plus (801) (1) 5-23-93 NumberNine GXE (928) (1) STB** S3 (16-bit) 9-12-93 STB PowerGraph (805) (1) S3** 911/924 10-4-93 Orchid FahrenHeit Y 1280 Trident** 8900C 6-10-93 Trident 8900C Y (2) (16-bit) Weitek** P9000 2-17-94 Diamond Viper Y (3) Page 27 NOTES: 1. 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 OS/2 for Windows ServicePak. This 32-bit display driver better utilizes the S3 chip sets. 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 Driver Installation" section in this file. 2. You can reinstall the Trident-supplied 16-bit display driver, but the OS/2 for Windows ServicePak SVGA 32-bit display driver better utilizes the Trident 8900C cards. IBM provides service for the OS/2 2.1 ServicePak SVGA 32-bit display driver and recommends that you install the new version of this driver. 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 VGA driver. Page 28 To install the OS/2 for Windows ServicePak SVGA 32-bit display driver, follow these steps: 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 for Windows Installation diskettes. (The ServicePak might need to be reapplied to ensure your system is at the proper level.) 7. When you see the Primary Display Adapter Type window, select Trident 8900C. 8. 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. 3. After you install the OS/2 for Windows ServicePak, 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. Page 29 SECTION 4. S3 VIDEO INFORMATION ________________________________ 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 shut down and then restart your system. Page 30 S3 IBM TESTED DISPLAY ADAPTERS ______________________________ IBM has tested many display adapters containing the S3 chips sets. However, certain display adapters in combination with certain chip sets might not be supported. The display adapters that have tested successfully to date are listed following. Page 31 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 Page 32 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 NOTE: If you have a Dell 466/ME system, you must edit the SVGADATA.PMI file located in the \OS2 directory. Change the following statement from: HI-COLOR DAC by AT&T Microelectronics, Inc. to: HI-COLOR DAC by unknown to make the changes effective you must shut down and then restart your system. OS/2 only supports 256 color mode under the current chipset. Page 33 S3 VIDEO ACCELERATOR DRIVER FOR OS/2 FOR WINDOWS ________________________________________________ SERVICEPAK __________ 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. Page 34 S3 GRAPHICS AND COLOR RESOLUTION SUPPORT 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 OS/2 for Windows ServicePak 32-bit flat memory model and is designed to function as a 32-bit Presentation Manager* display driver under the OS/2 for Windows ServicePak 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 Page 35 S3 DRIVER INSTALLATION ______________________ This video accelerator driver is compatible with the OS/2 for Windows ServicePak. NOTE: Do NOT install it on previous versions of OS/2. Use the SVGA install instructions to install S3 video device drivers. Refer to Appendix A in the "OS/2 2.1 Installation Guide." The following information pertains to installing S3 video support. Page 36 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 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 for Windows Installation diskettes. (The ServicePak might need to be reapplied to ensure your system is at the proper level.) 7. When you see the Primary Display Adapter Type window, select "32 bit S3 Display Drivers". 8. 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. Page 37 S3 INSTALLATION FROM CD-ROM Notes: 1. You must create the installation diskettes from the diskette images on the original OS/2 2.1 for Windows CD-ROM. 2. You must create the display driver diskettes from the diskette images on the OS/2 for Windows ServicePak 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 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 for Windows Installation diskettes. (The ServicePak might need to be reapplied to ensure your system is at the proper level.) 7. When you see the Primary Display Adapter Type window, select "32 bit S3 Display Drivers". 8. 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. Page 38 S3 INSTALLATION IN A CID ENVIRONMENT NOTE: OS/2 for Windows ServicePak 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. The following information is meant as a guide, your LCU command file might be different. Page 39 /*****************************************************/ /* 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:\imglos2v21', ' /t:' || bootdrive, ' /mc:8' x.16.rspdir = '' x.16.default = '' /*---------------------------------------------------*/ /* NUMBER OF PROGRAMS SET UP IN THE */ /* PRODUCT DATA SECTION */ /*---------------------------------------------------*/ NUM_INSTALL_PROGS = 16 Page 40 /*****************************************************/ /* 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 /*****************************************************/ Page 41 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: /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: where C: is the drive where OS/2 for Windows ServicePak 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 640 x 480 x 256. Page 42 SECTION 5. TRADEMARKS ______________________ The following terms, denoted by an asterisk (*) in this README file, are trademarks or registered trademarks of the IBM Corporation in the United States or other countries: IBM Presentation Manager OS/2 PS/2 PS/ValuePoint ThinkPad XGA Page 43 The following terms, denoted by a double asterisk (**) in this README file, are trademarks of other companies as follows: Trademark Owner ------------------------------------------------------- Actix Actix Systems Corporation Artist Graphics Artist Graphics ATI ATI Technologies, Inc. AT&T American Telephone & Telegraph Company Cirrus Cirrus Logic, Inc. Compaq Compaq Computer Corporation 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 Legend Sigma Designs Inc. Matrox Matrox Electronic Systems, Ltd. Metheus Metheus Corporation Nth Graphics Nth Graphics Number Nine Number Nine Computer Corporation Orchid Orchid Technology, Inc. Panasonic Matsushita Electric Industrial Co., Ltd. PCG Personal Computer Graphics Corporation QVision Compaq Computer Corporation STB STB Systems, Inc. S3 S3 Incorporated Trident Trident Microsystems, Incorporated Tseng Tseng Laboratories, Inc. Vermont Vermont Microsystems Video 7 Video Seven, Inc. Video 7 Win.Pro Video Seven, Inc. Volante National Design Inc. Weitek Weitek Corporation Windows MicroSoft 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. (C) Copyright IBM Corporation, 1993, 1994. All rights reserved.