Technical Notes Note: Before using this information and the product it supports, read the general information under Appendix A, Notices. First Edition (November 2001) This edition applies to IBM(R) OS/2(R) Warp Server for e-business, IBM OS/2 Warp 4, and to all subsequent releases and modifications until otherwise indicated in new editions. (C) Copyright International Business Machines Corporation 2001. All rights reserved. U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. ------------------------------------------------------------------------ Contents Preface 1.0 New and updated features 1.1 PCI Support in the OS/2 Serial Device Driver 1.2 DVD/UDF Support 1.2.1 Supported Drive Models 1.2.2 Adding UDF Support to OS/2 Boot Diskettes 1.2.3 UDF Restrictions in PM Mode 1.2.4 FORMAT and CHKDSK parameters 1.2.5 Specific handling of CD-RW disks 1.3 Universal Serial Bus (USB) Removable Media and CD-ROM Device Driver Support 1.3.1 Hardware Requirements 1.3.2 Configuration Parameters 1.4 New driver for resetting system display mode 1.5 New RAS utilities 1.6 JFS Lazywrite parameters in CONFIG.SYS 1.7 Platform-specific drivers 1.8 Directory Limits support for JFS File Systems 1.8.1 JFS block sizes 1.8.2 Directory limits alert parameters 1.8.3 Directory limits backup and restore utilities 1.9 NETLOGON command changes 1.9.1 Initial setup 1.9.2 Domain controller precautions 1.9.3 Correcting NET3229 "Refuse to synchronize" error 1.9.4 NET.ACC file recovery improvements 1.10 NET STATUS command changes 1.11 NET ACCOUNTS command changes 1.12 Support for Intel Multiprocessor Specification 1.4 and APIC 1.13 Netware Client option removed 1.14 Updates to online help 1.14.1 RESTORE command 1.15 Process Dump Size Increased 1.16 Additional Controls During Boot 1.17 New DevHelp Flag for Address Allocation 1.18 Making Java Programs Faster 2.0 Troubleshooting 2.1 Application and component considerations 2.1.1 IBM OS/2 Warp Developer Kit, Java(TM) 2 Technology Edition Version 1.3 incompatibilities 2.1.2 Changing the LIBPATH after installing Lotus(R) Notes(R) Domino(TM) Server 2.1.3 Network printing 2.1.4 StarOffice 5.1x 2.1.5 Power Management 2.1.6 Display Data Channel detection 2.1.7 DBCS language-specific fonts 2.1.8 FTP 2.1.9 OS/2 Window default size 2.1.10 Products that add locked file device driver statements 2.1.11 Lotus Domino Go Webserver DLLs 2.1.12 TCP/IP NFS and IBM VisualAge C++ compatibility problem 2.1.13 Tivoli Management Agent 2.1.14 TME 10 Distributed Monitoring 2.1.15 WorkSpace On-Demand 2.1.16 DBCS: Fonts are displayed incorrectly 2.1.17 Adobe Type Manager 2.1.18 WebSphere(TM) Application Server Standard Edition 3.02 for OS/2 2.1.19 Running JAVAKEY 2.1.20 Creating partitions with LVM command-line interface 2.1.21 Syntax Highlighting in DBCS version of EPM 2.1.22 TCPBEUI on a DHCP client 2.1.23 ACLs on JFS volumes 2.1.24 Screen savers on security-enabled servers 2.1.25 File server alias path modification 2.1.26 Lotus SmartSuite(R) 97 2.1.27 Multiple server names 2.1.28 Performance Tuning Assistant is informational only 2.2 Remote IPL 2.2.1 "TR Shared RAM" Token Ring Adapter on RIPL clients 2.2.2 RIPL for clients must be restarted manually after running TCPCFG2 2.2.3 RIPL for DBCS OS/2 Warp 4 clients 2.2.4 OS/2 RIPL clients 2.2.5 RIPL disk space 2.2.6 RIPL for NLV-enabled OS/2 Warp 4 clients 2.2.7 RIPL capability removal 2.2.8 RIPL tree 2.2.9 RIPL for Arabic OS/2 Warp 4 clients 2.2.10 JFS support for OS/2 Warp 4 RIPL clients 2.3 Commands, CONFIG.SYS statements, and Messages 2.3.1 Kernel file message 2.3.2 VIRTUALADDRESSLIMIT 2.3.3 XCOPY 2.3.4 PREPACL 2.3.5 SYS1718 error message 2.4 Associated bitmap-fonts 2.5 Hardware device and device driver considerations 2.5.1 3Com Fast Etherlink XL network adapter boot problem 2.5.2 Dell OptiPlex GX110 2.5.3 Device driver adapters 2.5.4 IBM ISDN Co-processor adapters 2.5.5 802.2 RIPL with a DOS Network Adapter device driver 2.5.6 IBM Token-Ring adapters 2.5.7 CPU initialization on a Compaq 4500 2.5.8 SMP system with OS2APIC.PSD 2.5.9 IBM ServeRAID adapters 3.0 Fixed IDE Hard Drive and Removable Media Support 3.1 Hard Drive Considerations 3.1.1 Cannot Mark a Partition Installable 3.1.2 Internal Processing Error on Restart, "Trap D" 3.1.3 Application Install Fails With "Not Enough Space" 3.1.4 Performance Problems with Two Devices on a Single Channel 3.1.5 Install Diskettes or Utility Diskettes Hang on Boot (APAR JR12065) 3.1.6 Connecting an External Floppy Disk Drive 3.1.7 Additional Parameters for IDE Device Drivers 3.2 Removable Media Support 3.2.1 Configuring Partition Support (OS2DASD) 3.2.2 Ejecting the Media 3.2.3 Limitations of Partitioned Removable Media Support 3.2.4 Large Floppy Removable Media (LS-120) 3.2.5 CD-ROM Device Manager (OS2CDROM.DMD) 3.2.6 CD-RW Media Support in IBMIDECD.FLT 3.3 Supported IDE Controllers, Known Restrictions and Limitations 3.3.1 Supported Chipset Table 4.0 LSI Logic SDMS Support 4.1 LSI Logic Devices Supported 4.2 Driver Order in the CONFIG.SYS File 4.3 Command-line Options 4.3.1 Using the /VERBOSE (or /V) Option 4.3.2 Using the /!DM Option 4.3.3 Using the /!SM Option 4.3.4 Using the /EXCLUDE (or /X) Option 4.3.5 Using the /SYNCH_RATE (or /SR) Option 4.3.6 Using the /SYNCH_OFFSET (or /SO) Option 4.3.7 Using the /TIMEOUT (or /T) Option 4.3.8 Using the /DISCONNECT (or /DC) Option 4.3.9 Using the /PARITY (or /P) Option 4.3.10 Using the /QTAG (or /QT) Option 4.3.11 Using the /WIDTH (or /W) Option 5.0 I2O Storage and Transport Device Drivers Version 1.0 6.0 PCI Support in the OS/2 Parallel Port Device Driver 6.1 Implementation 7.0 OS/2 GRADD Device Drivers 7.1 Supported Features 7.2 Drivers Included 7.3 Supported Resolutions 7.4 Functional Restrictions 7.5 Installing GRADD Drivers 7.5.1 Installing in a CID Environment 7.5.2 File Extraction 8.0 Plug'n'Play for PCMCIA 8.1 Systems Supported 8.2 Limitations 8.3 Parameter Definitions 8.3.1 Socket Services (IBM2SS14.SYS) 8.3.2 Card Services (PCMCIA.SYS) 8.4 Using Point Enablers with the Plug'n'Play for PCMCIA Package 8.5 Hints and Tips 8.5.1 Problems with Adapter Cards 9.0 IBM Plug'n'Play for PCMCIA CID Installation 9.1 Response File Format 10.0 Adaptec Ultra160 Family Manager Set 10.1 Supported Hardware 10.2 Known Issues 10.3 Additional Notes 10.4 Command-line Options 10.4.1 Universal Parameters 10.4.2 General Unit Parameters 10.4.3 Configuration Examples 11.0 Adaptec 7800 Family Manager Set 11.1 Supported Hardware 11.2 Known Issues 11.3 Additional Notes 11.4 Command-line Options 11.4.1 Universal Parameters 11.4.2 General Unit Parameters 11.4.3 Configuration Examples 12.0 REXX functions 12.1 SysQueryExtLIBPATH 12.2 SysQuerySwitchList 12.3 SysSetExtLIBPATH 12.4 SysSwitchSession 12.5 SysDumpVariables 12.6 SysSetFileDateTime 12.7 SysGetFileDateTime 12.8 SysStemCopy 12.9 SysStemDelete 12.10 SysStemInsert 12.11 SysStemSort 12.13 SysVersion 12.14 SysUtilVersion 13.0 Appendix A. Notices 13.1 Trademarks ------------------------------------------------------------------------ Preface This document is a supplement to the IBM OS/2 product documentation and contains non-installation related technical information. ------------------------------------------------------------------------ 1.0 New and updated features ---------------------------- The Convenience Packages include many new or updated features. This section contains information about these features. ------------------------------------------------------------------------ 1.1 PCI Support in the OS/2 Serial Device Driver ------------------------------------------------ The Asynchronous Communications Device Driver (COM DD) is the OS/2 physical installable device driver that enables OS/2 application programs or systems programs to utilize the serial COM ports. The current version of the COM DD is extended to support serial port PCI add-on cards (controllers) with IRQ sharing implemented through software. This support is available to a maximum of four legacy and PCI COM ports with the reserved device names COM1, COM2, COM3, and COM4. The COM DD with PCI support accepts the same CONFIG.SYS parameters as a legacy COM DD (see the OS/2 Command Reference for details on these parameters). Note: PCI serial controllers are identified by PCI device class/interface codes: o Base class: 0x07 (Simple communication controllers) o Sub-class: 0x00 (Serial controllers) o Interface: from 0x00 (Generic serial controller) to 0x06 (16x50-compatible serial controller) Encodings for class codes are provided in the PCI Local Bus Specification, Revision 2.2, Appendix D. ------------------------------------------------------------------------ 1.2 DVD/UDF Support ------------------- This section contains the latest information on Digital Video Disc/Universal Disk Format (DVD/UDF) Support for OS/2 Warp Server for e-business and Convenience Packages for OS/2 Warp 4 and OS/2 Warp Server for e-business (also called the "Convenience Packages"). 1.2.1 Supported Drive Models ---------------------------- This software package provides full CD-RW, DVD-ROM and DVD-RAM file system support for OS/2 Warp Server for e-business and Convenience Packages. The following CD-RW and DVD drive models have been tested: * TOSHIBA SD-M1202 * HITACHI GD-2500 * CREATIVE LABS DVD-5240E * PHILIPS DRD-5200 * SONY DDU-220E * PANASONIC LF-D100 * AOpen DVD-520S * HEWLETT-PACKARD 9100 * HEWLETT-PACKARD 9200 All previously supported CD-ROM drive models are also still supported. 1.2.2 Adding UDF Support to OS/2 Boot Diskettes ----------------------------------------------- To add UDF support to OS/2 booted from diskettes: 1. Using a text editor, open the CONFIG.SYS file of Diskette 1. 2. Locate the line containing the following statement: DEVICE=\MOUSE.SYS 3. Add the following statement after the line located in step 2: DEVICE=\UNICODE.SYS 4. Add the following lines to the end of CONFIG.SYS: SET COPYFROMFLOPPY=1 IFS=UDF.IFS /Q 5. Copy the file, C:\OS2\BOOT\UNICODE.SYS to Diskette 2. 6. Copy the file, C:\OS2\BOOT\UDF.IFS to Diskette 2. 7. Create the directory LANGUAGE\CODEPAGE on Diskette 2. 8. Copy the file C:\LANGUAGE\CODEPAGE\IBM into the LANGUAGE\CODEPAGE directory on Diskette 2, where code_page is the code page used in the statement, CODEPAGE= in CONFIG.SYS file on Diskette 1. 1.2.3 UDF Restrictions in PM Mode --------------------------------- The current version of the UDF file system driver does not support PMFORMAT and PMCHKDSK utilities. Presentation Manager (PM) applications that use these utilities will not work correctly. In addition, you cannot use items "Check disk..." and "Format disk..." in the context menu for the drive. 1.2.4 FORMAT and CHKDSK parameters ---------------------------------- This section describes the syntax and parameters for the FORMAT and CHKDSK commands for use in a UDF file system. FORMAT parameters The syntax of the FORMAT command for UDF file system is the following: FORMAT drive /FS:UDF [/S:SETID] /V:LABEL [/F] [/L] [/ONCE] [/Y] drive A drive letter, for example, C:. /S:SETID Volume Set Identifier. /V:LABEL Volume label. /F or /L Low-level formatting. /Y Assume a YES response to all questions asked by FORMAT. /ONCE Format without any questions issued to the user. CHKDSK parameters The syntax of the CHKDSK command for UDF file system is the following: CHKDSK drive [/y|/n] [/c] [/F] [/f] [/q|/v|/V] [/t: S] drive A drive letter, for example, C:. /y Assume a YES response to all questions asked by CHKDSK. /n Assume a NO response to all questions asked by CHKDSK. /c Check the volume for a clean unmount (return a 0 if clean, 1 if not). /F Force the check of a cleanly unmounted volume. /f Fast check. Check blocks/sizes and the free list. /q Quiet mode. Error messages only are output. /v Verbose mode. /V Very verbose mode. /t: S Optional scratch file, where S= filename. Notes: 1. Parameters for the CHKDSK command are case-sensitive. 2. If d: is the current disk and you run the CHKDSK d: command, you will get the message "Drive busy". To avoid the message, the current disk must differ from checked disk or define a scratch file on the disk that differs from checked file. 1.2.5 Specific handling of CD-RW disks -------------------------------------- The following items apply to CD-RW disks: * For CD-RW disks, write-protection (like diskette and DVD-RAM) is not provided. * Prior to using a CD-RW disk that has never been written on, you must format it using the /F parameter: FORMAT d: /FS:UDF /F * If a CDFS or other file system has written on a CD-RW disk and you want to use that CD-RW disk in the UDF file system, you must format it using /F parameter: FORMAT d: /FS:UDF /F * CD-RW disks prepared in Adaptec DirectCD for Windows(R) cannot be written to in OS/2 and vice versa. Compatibility is only available for reading. ------------------------------------------------------------------------ 1.3 Universal Serial Bus (USB) Removable Media and CD-ROM Device Driver Support ------------------------------------------------------------------------------- 1.3.1 Hardware Requirements --------------------------- Removable media/CD-ROM drivers are designed to work with all devices manufactured according USB mass storage device specifications. Tests are performed for following devices: * VST and Newer Technology USB Floppy Drives * Imation or Winstation SuperDisk (LS-120) drives * Iomega 100MB and 250MB portable USB Zip drives * Hewlett-Packard USB CDWriter 8200 * USB Sony Spressa CD-RW 1.3.2 Configuration Parameters ------------------------------ After installation, USB-Removable Media / CD-ROM drivers serve: * One floppy device (including LS-120 Super Disk devices) * One removable media device (like Iomega Zip drive) * One CD-ROM/CD-RW device The number of devices served for each device category may be changed using CONFIG.SYS parameters. These parameters are described next. Parameter Function /CDS:n The number of CD-ROM/CD-RW devices to be served. The default is 1. This parameter is used in the statement BASEDEV=USBCDROM.ADD. For example, the following statement serves two CD-ROM/CD-RW devices: BASEDEV=USBCDROM.ADD /CDS:2 In order to remove service, the key value must be set to 0. Note: For Warp 3 systems, the number of CD-ROM devices served must be specified on the USBMSD.ADD statement in CONFIG.SYS as follows: BASEDEV=USBMSD.ADD /CDS:1 /FLOPPIES:n The number of floppy devices to be served. The default is 1. In order to remove service, the key value must be set to 0. /MAX_FLOPPY The USB driver stack, by default, does not support 120MB media formatting in USB LS-120 devices. This is caused by limitations introduced by XDFLOPPY.FLT filter support. These two features are exclusive and only one can be supported at once. To support superdisk media (120MB) formatting, the statement in CONFIG.SYS for the USBMSD driver must contain the /MAX_FLOPPY switch. For example: BASEDEV=USBMSD.ADD /MAX_FLOPPY /REMOVABLES:n The number of removable media devices to be served. The default is 1. For example, the following statement serves two floppy devices (including LS-120 Super Disk devices), and three removable media devices (like Iomega Zip drive). BASEDEV=USBMSD.ADD /FLOPPIES:2 /REMOVABLES:3 In order to remove service, the key value must be set to 0. Removable media volumes can be processed as large floppies or partitioned volumes (default processing type). You can serve removable disks as partitioned volumes. Parameter Function /REMOVABLE_AS_FLOPPY The system uses removable disks as partitioned volumes. For example: BASEDEV=USBMSD.ADD /REMOVABLE_AS_FLOPPY /MP:(device_number, partition_count) The number of partitions for device number. The default is 1. This parameter is used in the BASEDEV=OS2DASD.DMD statement. For example: BASEDEV=OS2DASD.DMD /MP:2,2 ------------------------------------------------------------------------ 1.4 New driver for resetting system display mode ------------------------------------------------ When you press the Alt-F1 key during system startup, it takes you to the Recovery Choices screen. The F3 key, when pressed from the Recovery Choices screen, resets the system video mode during system startup. In previous releases of the operating system, the key's function was to "reset to VGA." In the Convenience Package, this has been changed to reset to another general purpose display driver with a higher resolution and better color capabilities than VGA mode (the Recovery Choices screen still says "F3 - Reset primary video display to VGA and reboot", but the system is reset to the new driver). The new driver is called the "Generic VESA Unaccelerated & VGA GRADDs". This default GRADD driver is also the driver now chosen by default on non-migration installations, when no other, more-specific driver is available for your display adapter. The original VGA driver is still installed automatically for when using F4 from the Recovery Screen to go to the Maintenance Desktop. The original VGA driver is still available for troubleshooting purposes, by pressing Alt-F1 at system startup, then pressing F2 to get to an OS/2 command prompt, then entering the SETVGA command, and then typing EXIT to close the command prompt. Generally, you can use the new Alt-F1 and F3 at system startup whenever the documentation for another display driver requires you to "reset to VGA" prior to installing the driver. However, if you experience problems installing another display driver, then using SETVGA for "reset to VGA"-- instead of Alt-F1 and F3 -- as part of the installation process for the other display driver might solve these problems. If you experience problems or are otherwise unsatisfied with the display driver chosen automatically for your display adapter by the install process, use Selective Install to choose either of the following as a possibly slower, but generally dependable alternative: Generic VESA Unaccelerated GRADD Generic VESA Unaccelerated & VGA GRADDs Alternatively, you can try the latest version of the IBM Special Edition of SciTech Display Doctor, or one of the other display drivers available through the OS/2 Device Driver Pak Online at the following Web address: http://service.software.ibm.com/os2ddpak/index.htm The README.TXT for that driver includes a continually updated extensive list of display adapters for which the driver provides support which generally includes hardware acceleration and selectable refresh rates. Updates to other display drivers are available at the same Web address. ------------------------------------------------------------------------ 1.5 New RAS utilities Two new RAS (reliability, availability, and serviceability) utilities are included: PSFILES.EXE and PSSEMS.EXE. PSFILES.EXE can dump information about open files on the system. By default, PSFILES dumps the information for all processes. Alternately, "PSFILES xxx" dumps information for PID xxx (where xxx is a hexadecimal number, for example from PSTAT). PSSEMS.EXE can dump information about open 32-bit semaphores on the system. By default, it prints all the shared (for example, system-wide) semaphores. Usage is as follows: pssems [/n] [hex_pid | /a] where /n suppresses shared semaphores and /a prints private semaphores for all system processes. Note: These RAS utilities are added to the OS2 directory on your system. ------------------------------------------------------------------------ 1.6 JFS Lazywrite parameters in CONFIG.SYS ------------------------------------------ The parameters for the Journaled File System (JFS) installable file system are as follows: IFS=jfs.ifs /L:OFF IFS=jfs.ifs /L:synctime,maxage,bufferidle JFS ignores any characters between the L (or l) and the colon; valid flags are /L: /LAZY: /LW: /lazywrite: and so on. OFF Forces asynchronous writes to be immediately initiated. Synctime The interval at which the synchronous thread runs. The default is 64. maxage The longest time that a frequently-modified file is kept in cache. The default is synctime*4. bufferidle The time indicating a recent change. Changes newer than this value are not written unless the last write was older than maxage. The default is MIN(1,synctime/8) Note: All parameters are in seconds. The following are some usage examples: IFS=C:\OS2\JFS.IFS /L:64 synctime = 32, maxage = 128, bufferidle = 4 IFS=C:\OS2\JFS.IFS /LW:10,60,5 synctime = 10, maxage = 60, bufferidle = 5 IFS=C:\OS2\JFS.IFS /LAZYWRITE:4,60 synctime = 4, maxage = 60, bufferidle = 1 IFS=C:\OS2\JFS.IFS /lazy:off All writes initiated immediately (synctime=1, maxage=bufferidle=0) Note: The synchrounous thread still runs since things like marking an inode accessed are still deferred. The CACHEJFS.EXE command allows the lazywrite parameters to be changed immediately. The syntax is similar to the IFS line, except that the /L: prefix is optional. In addition, the CACHEJFS command can modify the minimum and maximum number of free cache buffers to be maintained. Calling CACHEJFS with no parameters reports the current settings. CACHEJFS [[/LAZYWRITE:]{OFF|syncTime[,maxAge[,bufferIdle]]}] /MINFREE:minfree /MAXFREE:maxfree ------------------------------------------------------------------------ 1.7 Platform-specific drivers ----------------------------- In the Convenience Packages, all platform-specific code has been removed from the operating system and placed it into platform-specific drivers. These drivers provide an abstraction layer for the underlying hardware by allowing the operating system to call generic functions to perform platform-specific operations without concern for the actual hardware implementation. This facilitates support for new platforms without modifying the operating system. Platform-specific drivers (PSDs) are specified in CONFIG.SYS by using the PSD keyword, and must conform to the 8.3 file naming convention (for example, PSD=BELIZE.PSD). They cannot contain either drive, or path information because OS/2 cannot process such information at the stage of the startup sequence when the PSD statements are processed. The root directory of the startup partition is first searched for the specified file name, then the \OS2 directory of the startup partition. If drive or path information is included in a PSD statement, an error is generated. PSD parameters may be specified after the PSD's name, and may be a maximum of 1024 characters long. The parameter string is not interpreted or parsed by OS/2; it is passed verbatim, as an ASCIIZ string when the PSD's install function is invoked. If multiple PSD statements are encountered, OS/2 loads each PSD in the order listed in CONFIG.SYS and calls the PSD's install function. The first PSD which successfully installs is the one OS/2 uses. PSD statements are processed before BASEDEV, IFS, and DEVICE statements. Note that anytime you add or make changes to the CONFIG.SYS file, you must restart the system for the changes to become effective. The CONFIG.SYS file is read only during system startup. Anything added to this file after system initialization does not work until you restart the system. This PSD has the following syntax for its argument line: [/apic] [/p=] [/nmi=[l]int] [/pic=[l]int] [/prec=] Where: /apic Indicates that the PSD should enable symmetric interrupt mode. /p Indicates that the system should be configured for processors where is a decimal number (for example, 5, 8, 12). /nmi Indicates the default signal route for non-maskable interrupts (NMIs). This allows the route to be specified for NMIs if a route is not defined by the MP configuration tables set up by BIOS. By using the /prec option (see below), you can override the MP configuration tables if they have been built incorrectly by the BIOS. The argument is "int" or "lint". The first case indicates the interrupt PIN number to which the NMI signal is wired on the I/O APIC. The second case indicates the interrupt PIN number to which the NMI signal is wired on the local APIC is a decimal number (for example 0, 3, 12). The /pic indicates a default signal route for the 8259 interrupt controller when the system is running in "virtual wire" mode. This allows the route to be specified for the interrupt controller if the route is not defined by the MP configuration tables set up by BIOS. By using the /prec option (see below), you can override the MP configuration tables if they have been built incorrectly by the BIOS. /prec Indicates the precedence order to be used in determining the routing for the NMI signal and the interrupt signal from the interrupt controller. This allows control over the choosing of a routing entry when there is more than one entry. There are three possible entries that can describe a route: * Route to the I/O APIC * Route to the Local APIC * Route described by an argument or arguments to the PSD The first two entries may be specified in the MP configuration tables that are built by the BIOS. The third entry may be specified on the argument line to the PSD. Each type of route is described by one letter: i I/O APIC routes l Local APIC routes d Routes described by the argument line to the PSD The precedence string is exactly three characters long. The first character indicates the type of routes to be considered first. The second character indicates the routes to be considered next, and the third character indicates the routes that are to be considered last. As an example, "ild" indicates that I/O APIC routes are to considered first, followed by local APIC routes, and finally routes specified on the argument line. In contrast, "dil" indicates that routes on the argument line are to be considered first, then the I/O APIC, and finally the local APIC. Note: The arguments to the PSD are not case sensitive. ------------------------------------------------------------------------ 1.8 Directory Limits support for JFS File Systems ------------------------------------------------- The Convenience Package for OS/2 Warp Server for e-business supports directory limits on JFS volumes. Directory limits are set using the NET DASD commands and APIs used to set limits on 386 HPFS volumes. 1.8.1 JFS block sizes --------------------- Directory limits on JFS volumes are enforced in multiples of the block size. The default block size for JFS is 4KB. When you set a directory limit on a JFS volume, the size of the limit is rounded down to the nearest block size. For example, if the JFS block size is 4KB and you set a directory limit of 10KB, the resulting directory limit is 8KB, a multiple of the block size, instead of the 10KB requested. 1.8.2 Directory limits alert parameters --------------------------------------- The parameters for directory limits alerts are now located in the IBMLAN.INI file instead of the HPFS386.INI file. In the IBMLAN.INI file, you cannot set the same parameter on multiple lines as you can in the HPFS386.INI file. All settings for a parameter must appear on one line. For example, if you want to alert the user when the directory limit has been reached on volumes C:, D:, and F:, but not on volumes, E:, G: and H:, you could set the DirFullAlertUser parameter in IBMLAN.INI as follows: DirFullAlertUser = cdf: yes e: no gh: no 1.8.3 Directory limits backup and restore utilities --------------------------------------------------- You can back up and restore directory limits using the BackDLim and RestDLim utilities. BackDLim BackDLim saves directory limits information in a readable ASCII format. The syntax for BackDLim is: BackDLim [\\server [d:\[path]] | [d:][\][path] | \\server\sharename[\path]] [/i:input-file] [/o[:output-file]] [/s[:level]] [/c] [/l[:log-file]] [/vf:file] [/vl[:level]] [?] [/?] [/h] You can specify which directory limits to backup in the following ways: (none) all local drives \\server all local drives on a server [d:][\][path] a local drive\path \\server d:[\path] a local drive\path on a server \\server\sharename[\path] a shared directory on a server You can specify the source directory for the backup of directory limits as a local path or as the path on a server share name. A server name can be specified to back up directory limits on a given server. If no path name or server name is given, BackDLim backs up the directory limits on all drives on the local system. If a server name is given without a specific path, BackDLim backs up the directory limits on all drives on the remote system. Options: /i:input-file Name of an input file that specifies various source directories. An input file can also be given to BackDLim by redirecting it through standard input. For example: BackDLim < input-file /o[:output-file]Name of the output file. By default, BackDLim writes its output to the standard output (the display). If /o is given without a file name, the default output file name is dlim.bak in the current directory. /s[:level] Number of subdirectory levels to search for directory limits. If /s is specified with no number, all subdirectories are searched for directory limits. /c Prompts for confirmation before saving each directory limit. /l[:log-file] Writes a log of the progress when processing directory limits. If /l is used without a file name, the default is to add the log information to the file named backdlim.log in the current directory. /vl[:level] Displays step-by-step output about the progress of BackDLim. The level sets the amount of detail that is displayed. /vf:file Step-by-step output about the progress of BackDLim is written to the file instead of to the display. ? /? /h Displays help information. RestDLim The RestDLim utility restores directory limits saved by the BackDLim utility. The syntax for RestDLim is: RestDLim [input-file ...] [/s] [/f] [/c] [/l[:log-file]] [/vf:file] [/vl[:level]] [?] [/?] [/h] The input file contains the directory limits information backed up by BackDLim. RestDLim requires the name of at least one file that contains the directory limits to be restored. RestDLim can process multiple input files. The input file can be specified as a parameter to RestDLim or it can be directed through standard input (STDIN). For example: RESTDLIM < input-file RestDLim can handle an input file redirected through standard input along with input files specified on the command line. Options: /s Sets "soft limits." If the current usage on a directory is greater than the limit to be restored, the limit for the directory is set to the current usage. /f Forces "hard limits." The limit for a directory will be restored regardless of whether the current usage is greater than the limit to be restored. /c Prompts for confirmation before saving each directory limit. /l[:log-file] Writes a log of the progress when processing directory limits. If /l is used without a file name, the default is to add the log information to the file named backdlim.log in the current directory. /vl[:level] Displays step-by-step output about the progress of RestDLim. The level sets the amount of detail that is displayed. /vf:file Step-by-step output about the progress of RestDLim is written to the file instead of to the display. ? /? /h Displays help information. ------------------------------------------------------------------------ 1.9 NETLOGON command changes ---------------------------- The Netlogon service has a new option for additional servers to synchronize user and group serial numbers. User and group serial numbers, which help identify users and groups on a server, might vary from one server to another. Among other things, the serial numbers are used in permission entries for 386 HPFS access control lists (ACLs) to identify the user or group by a unique id number rather than by name. The new option, /SYNCSERIALS on the NET START NETLOGON command or syncserials= in the [netlogon] section of the IBMLAN.INI file, enables additional servers to maintain the same user/group internal identifiers within the domain. This is mainly to enable the exchange of 386 HPFS volumes between servers in the domain without requiring that ACLs be removed and then re-added on the new server. The feature provides consistency in access permissions for 386 HPFS volumes moved from server to server within the same domain. This can be beneficial for removable media that is formatted for 386 HPFS with ACLs applied or disks shared between servers that might mount one another's 386 HPFS volumes. By default, the /SYNCSERIALS option is set to NO. The /SYNCSERIALS option is ignored at the domain controller. The /UPDATE Netlogon service option is ignored when the /SYNCSERIALS option is set to YES. This safeguards against an unintentional forced replication from a replacement NET.ACC file on the domain controller. See Initial setupfor the steps required to enable the feature. 1.9.1 Initial setup ------------------- To enable additional servers to synchronize the user and group serial numbers as they exist on the domain controller, follow these steps. You must do these steps only once for the initial setup: 1. Install the Convenience Package to the domain controller and any additional servers that require the feature. Shut down and restart the servers but do not enable the SYNCSERIALS option yet. 2. On the additional servers, execute PREPACL to back up and remove access control information for all 386 HPFS volumes. 3. On the additional servers, edit the IBMLAN.INI file, place the line syncserials=yes below the [netlogon] section, and save the file changes. 4. Issue the NET STOP REQUESTER command on the additional servers. 5. Execute FIXACC on the additional servers. 6. After FIXACC is complete, issue NET START SERVER on the additional servers. 7. Allow the Netlogon service to completely synchronize user and group information from the domain controller to the additional servers. You can monitor the progress and completion of the synchronization on each additional server with the NET STATUS command. 8. When the synchronization status is "OK" on the additional servers, execute PREPACL to restore the previously removed access control information. 1.9.2 Domain controller precautions ----------------------------------- The following are suggested actions to avoid the NET3229 synchronization error on additional servers running with syncserials=yes if replacing the NET.ACC file on the domain controller: * Rather than replace the NET.ACC file with a blank one or an older version, use FIXACC to clean or correct any problems in the existing NET.ACC file. FIXACC will maintain the original serial numbers for groups and users. * If you need to replace NET.ACC on the domain controller, follow one of the two suggested actions described in the Correcting NET3229 Refuse to synchronize error section, specifically either using the NET.ACC file from an additional server in the domain running with syncserials=yes or following some of the same basic steps found in initial setup. 1.9.3 Correcting NET3229 "Refuse to synchronize" error ------------------------------------------------------ To protect additional servers from accepting serials numbers from an older backup NET.ACC file, a newly created NET.ACC file or one from another domain controller (DC), the Netlogon service on the additional server logs a NET3229 error log entry if it detects a replacement NET.ACC file on the DC. This safeguard is intended to prevent applying potentially different serial numbers automatically, which would then affect 386 HPFS permission entries, and therefore access to 386 HPFS resources for users and groups. The NET3229 message is as follows: NET3229: The NET.ACC file located on the primary domain controller for domain %1 cannot be used for synchronization. To correct the condition, the administrator must do one of the following: * On the domain controller, revert to the NET.ACC file prior to the new one. * On the domain controller, apply a NET.ACC file belonging to an additional server in the domain running with syncserials=yes and then set the role to primary with the NET ACCOUNTS /ROLE:PRIMARY command. Pick a NET.ACC file from an additional server running with syncserials=yes that has the highest UAS serial number using the the NET ACCOUNTS command (see NET STATUS command changes for more details). It is important that the NET.ACC file be from a server running with syncserials=yes. If the file comes from a server in the domain running with syncserials=no, the NET.ACC might still get accepted but provide additional servers with different/incorrect user and group serial numbers. It might be necessary to recreate access control information for non-386 HPFS and non-JFS resource with this method because ACLs for these resources are stored in the NET.ACC file. * The last alternative method involves some of the basic steps used in initial setup. Follow these steps for all additional servers running with syncserials=yes: 1. Execute PREPACL to back up and remove access control information for each 386 HPFS volume. 2. Issue the NET STOP REQUESTER command. 3. Execute FIXACC. 4. Issue NET START SERVER. 5. Allow the Netlogon service to completely synchronize user and group information from the new NET.ACC file on the domain controller to the additional server. Check the status of the synchronization with the NET STATUS command (see NET STATUS command changes for details). Proceed to he next step when the status indicates OK. 6. Execute PREPACL to restore the previously-removed access control information. 1.9.4 NET.ACC file recovery improvements ---------------------------------------- Additional servers running with syncserials=yes have an added benefit if a NET.ACC file becomes corrupt and FIXACC is unable to repair it for some reason. Because these servers synchronize the user and group serial numbers that get used in 386 HPFS access permissions, the administrator does not need to back up and remove all 386 HPFS ACLs if replacing the NET.ACC on the additional server. This is because the same serial numbers would be created for the users and groups that were previously used when the first full synchronization completes with the domain controller. It might be necessary to recreate access control information for non-386 HPFS and non-JFS resource with this method because ACLs for these resources are stored in the NET.ACC file. ------------------------------------------------------------------------ 1.10 NET STATUS command changes ------------------------------- The NET STATUS command now contains additional information that enables you to determine the status of the Netlogon service user/group account synchronization as well as the value of the /SYNCSERIALS NETLOGON option. The additional fields are presented only in the NET STATUS output of an additional server when the Netlogon service is running. The fields are displayed regardless of whether the /SYNCSERIALS option is enabled. Sample output: System error 5 Disk error (K) 300 Idle session time (min) -1 Max. audit-log size (K) 100 Number of network buffers 48 Network buffer size 4096 Number of big buffers 6 Synchronization status OK Synchronize serials enabled Yes Netname Resource Remark ----------------------------------------------------------------- IPC$ Remote IPC ADMIN$ C:\IBMLAN Remote Admin C$ C:\ D$ D:\ The Synchronization status is described in the following table: Status | Description ----------------------------------------------------------------- OK | UAS Database (NET.ACC) is currently in sync Error | An error occurred during synchronization Pending | An update request is currently pending In Progress | Synchronization is currently in progress "Synchronize serials enabled" corresponds to the value for the /SYNCSERIALS option, which is either "Yes" if this server will request synchronization of user and group serials numbers or "No" if it does request synchronization. ------------------------------------------------------------------------ 1.11 NET ACCOUNTS command changes --------------------------------- The NET ACCOUNTS command now displays the User Accounts Subsystem Database (NET.ACC file) serial number. This serial number is essentially a running counter of all updates to the NET.ACC file. Servers in the domain use this value to determine if they are in synchronization with the domain controller and to determine the number of changes between them. An additional server that is "in sync" with a domain controller would have the same User Accounts Subsystem Database serial number. [C:\]NET ACCOUNTS Force user logoff how long after time expires: Never Minimum password age (days): 0 Maximum password age (days): Unlimited Minimum password length: 4 Length of password history maintained: 8 Maximum bad password retries: 0 Server role: MEMBER Domain controller for requester domain: \\GUNSLINGER Accounts database serial number: 3107 The command completed successfully. The new field can be useful in conjunction with the new fields in the NET STATUS command for determining the progress of User Accounts Subsystem Database synchronization. ------------------------------------------------------------------------ 1.12 Support for Intel Multiprocessor Specification 1.4 and APIC ---------------------------------------------------------------- The Convenience Package includes support for Intel's MultiProcessor Specification 1.4 (MPS). One of the features of MPS 1.4 is the Advanced Programmable Interrupt Controller (APIC). If you have a system that supports MPS 1.4 and you want to use the APIC, you must add the "/APIC" flag to the PSD= line in the CONFIG.SYS file as follows: PSD=OS2APIC.PSD /APIC ------------------------------------------------------------------------ 1.13 Netware Client option removed ---------------------------------- The Netware Client option on the OS/2 Warp Version 4 Setup and Installation panel is no longer available during installation. ------------------------------------------------------------------------ 1.14 Updates to online help --------------------------- This section describes several new updates to the online help. 1.14.1 RESTORE command ---------------------- The date syntax for the RESTORE command is: yyyy-mm-dd For example: 2001-12-22 1.15 Process Dump Size Increased -------------------------------- Process dumps can now be greater than or equal to 2GB in size. ------------------------------------------------------------------------ 1.16 Additional Controls During Boot ------------------------------------ The following control are available during boot: * Alt-F2 now shows .EXE files and virtual device drivers as they are being loaded or executed. * Alt-F3 works as though you were using both Alt-F1 and Alt-F2. * Alt-F4 pauses before processing each of the following statements in the CONFIG.SYS file: o DEVICE= o IFS= o CALL= o RUN= When the system encounters these statements and pauses, you can either process the line or skip to the next line. BASEDEV and PSD statements cannot be skipped, but they will be displayed just as they are when Alt-F2 is used. * Alt-F5 works as though you were using both Alt-F4 and Alt-F1. * The existence of a file named ALTF2ON.$$$ in the root or \OS2\BOOT directory will automatically enable Alt-F2 processing; that is, filenames will be displayed at each reboot. * The existence of a file named OS2NOREV.$$$ will suppress the display of the internal revision number at each reboot. ------------------------------------------------------------------------ 1.17 New DevHelp Flag for Address Allocation -------------------------------------------- A new function for device drivers is available. Adding flag 0x20 to a call to DevHelp VMGLobalToProcess specifies that an address allocation should be made in the high private arena (addresses above 0x1fffffff). ------------------------------------------------------------------------ 1.18 Making Java Programs Faster -------------------------------- You can add the following line to CONFIG.SYS to make some of the faster systems execute Java programs (and some other programs) faster: CLOCKSCALE=$ Note that this statement is not a SET statement. Java programs will run faster, but there will be additional task-switching overhead. So, the amount of increase will vary depending on the system. ------------------------------------------------------------------------ 2.0 Troubleshooting ------------------- The following sections provide information about restrictions and potential problems that might occur after you have installed this product. ------------------------------------------------------------------------ 2.1 Application and component considerations -------------------------------------------- Read the following sections for information about the Convenience Package's components and applications. 2.1.1 IBM OS/2 Warp Developer Kit, Java(TM) 2 Technology Edition Version 1.3 incompatibilities ---------------------------------------------------------------------------- The upgrade from IBM OS/2 Warp Developer Kit, Java(TM) Technology Edition, Version 1.1.8 to IBM OS/2 Warp Developer Kit, Java(TM) 2 Technology Edition, Version 1.3 introduced many changes in the functional specification. These changes include renamed classes and deprecated APIs. Applications written for IBM OS/2 Warp Developer Kit, Java(TM) Technology Edition, Version 1.1.8 might not run unchanged on IBM OS/2 Warp Developer Kit, Java(TM) 2 Technology Edition, Version 1.3. It is recommended that you do not make IBM OS/2 Warp Developer Kit, Java(TM) 2 Technology Edition, Version 1.3 the default Java Virtual Machine on your system. 2.1.2 Changing the LIBPATH after installing Lotus(R) Notes(R) Domino(TM) Server After installing Lotus Notes(R) Domino Server 4.52 or 4.6x (also called Domino), you must manually adjust the LIBPATH in the CONFIG.SYS file. Domino inserts its DLL directories at the beginning of the LIBPATH, which causes a conflict with the IBM OS/2 Warp Developer Kit, Java(TM) Technology Edition, Version 1.1.8 installed with the Convenience Pack. Move the Domino LIBPATH entry to after the JAVA11 path entries, or to the end of the LIBPATH, in the following manner: After Notes Installation: LIBPATH=c:\notes;C:\JAVA11\DLL;C:\JAVA11\ICATJAVA\DLL;... Manually change to: LIBPATH=C:\JAVA11\DLL;C:\JAVA11\ICATJAVA\DLL;...;c:\notes; 2.1.3 Network printing ---------------------- To use a network printer, the printer drivers on both the client and the server must be at the same level. 2.1.4 StarOffice 5.1x --------------------- StarOffice 5.10 does not install correctly; version 5.1A of StarOffice installs successfully. 2.1.5 Power Management ---------------------- The Convenience Package adds several power management functions in support of the Intel SpeedStep(R) power management technology. These functions enable you to fine-tune your system's power/performance behavior. The functions are accessible through the Power icon in the System Setup folder, in the following manner: * Open the Power object. The window displayed will contain a field titled Power and Performance Optimization, which displays the current SpeedStep state. On systems which do not support SpeedStep technology, the state is always Maximum Performance and cannot be changed. * The system menu in the Power Window will have a Performance selection which enables you to toggle between two states: Battery Optimized and Maximum Performance. * If you right-click the Power icon and select Properties, the Properties notebook displayed has a tab named Performance. Click the help button on the Performance page for more information on using the SpeedStep features. Note that SpeedStep functions are also displayed on systems that do not have SpeedStep-enabled processors. Altering SpeedStep settings on unsupported systems is harmless, but has no effect. Refer to your system's documentation to determine if it has a SpeedStep-enabled processor. 2.1.6 Display Data Channel detection ------------------------------------ Some computer monitors have an interface that enables the operating system to automatically determine the characteristics of the monitor. This interface is called a Display Data Channel (DDC). At times the information gathered by the operating system is not correct, and you must set the monitor characteristics manually. On the Convenience Package, this will most often manifest itself on the Screen page of the System settings notebook (in the System Setup folder). The resolution or refresh rate or both might be blank or incorrect. If you experience this problem, you can disable automatic detection by adding the following line to your CONFIG.SYS file: SET VCFG_NO_DDC=TRUE You must restart your system for the change to take effect. After restarting your system, go back to the Screen page in the System settings notebook, and manually select a monitor type. To do so: 1. Open the System settings notebook in the System Setup folder. 2. Click the Screen tab along the top of the panel. 3. Click the + on the folded-down-page icon in the top right corner of the Screen page to go to page 2. 4. Select your monitor type. 5. Close the System settings notebook and reopen it. 6. You should now see a correct list of available display modes. An example of this type of behavior is found in some models of IBM ThinkPad(R) 770 computers, if you are using a Trident Cyber 9397 Family GRADD driver. The resolution and refresh rate fields on the screen might be blank, preventing you from changing the display mode. If this is the case, use the solution above and in step 4, select "IBM ThinkPad 1024X768" for the monitor type. 2.1.7 DBCS language-specific fonts ---------------------------------- The Convenience Package includes fonts specifically designed for each Double-Byte Character Set (DBCS) country or region. Each font is dependent on information from the code page for which it was encoded. If you install a language-specific font on a system with a different language, the font names might appear incorrectly. If you need to display and print documents in multiple languages, use the Unicode-encoded fonts, Monotype Sans Duospace WT and Times New Roman WT. You should install a font for a language different from your system's only if you need to print documents formatted on a client using that font. 2.1.8 FTP --------- Some clients might have difficulty displaying directory information correctly when connecting to an OS/2 ftp server. In particular, the following problems might occur: * Directory listings might appear empty, even if there are files in the directory. * File names might appear as numbers. * File names in a directory might be missing or incorrect. To avoid these problems, try the following on the client: * Configure the server type in the client's preferences as OS/2. If the OS/2 choice is not available or does not resolve the problem, try using one of the other system types. * If the ftp client does not have the above options, or if the problem still exists, have the client use FTP from the command line. 2.1.9 OS/2 Window default size ------------------------------ In OS/2 Warp 4.0 and later versions, OS/2 windows open maximized to a default position. If you run customized applications that require the window to open to a specific size, you can remove the default size. To remove the default window size and position: 1. Open an OS/2 command window. 2. Move the mouse pointer to the restore icon in the upper-right corner of the window. 3. Press and hold the Shift key and right-click the restore icon. 4. Release the Shift key. 2.1.10 Products that add locked file device driver statements ------------------------------------------------------------- If you are installing a product (such as IBM eNetwork Communications Server V5.0) that adds locked file device driver statements to the CONFIG.SYS file, change the order of these statements before you restart your system. Locked file device driver statements must come after all IFS statements. For example, if you are installing IBM eNetwork Communications Server V5.0, your CONFIG.SYS file contains the following lines: IFS=C:\OS2\JFS.IFS /AUTOCHECK:* /CACHE:37272 DEVICE=C:\OS2\INSTALL\CMLIB\IBMCMLK.SYS C:\OS2\INSTALL\CMLIB\REBOOT.LST RUN=C:\OS2\INSTALL\CMLIB\IBMCMLK.EXE C:\OS2\INSTALL\CMBLIB\REBOOT.LST IFS=C:\OS2\HPFS.IFS\ /CACHE:2048 /CRECL:4 /AUTOCHECK:C Move the DEVICE and RUN statements after the IFS statements: IFS=C:\OS2\JFS.IFS /AUTOCHECK:* /CACHE:37272 IFS=C:\OS2\HPFS.IFS\ /CACHE:2048 /CRECL:4 /AUTOCHECK:C DEVICE=C:\OS2\INSTALL\CMLIB\IBMCMLK.SYS C:\OS2\INSTALL\CMLIB\REBOOT.LST RUN=C:\OS2\INSTALL\CMLIB\IBMCMLK.EXE C:\OS2\INSTALL\CMBLIB\REBOOT.LST Note: Each entry should be on only one line. The lines above are split for printability. 2.1.11 Lotus Domino Go Webserver DLLs ------------------------------------- If you install, or have installed, version 4.6.2.6 or earlier of Lotus Domino Go Webserver, there might be conflicts with some of the DLLs installed. To avoid potential conflicts with Lotus Domino Go Webserver DLLs, always ensure the \WWW\DLL entry on the LIBPATH statement that Lotus Domino Go Webserver places at the beginning of the LIBPATH statement follows the C:\IBMGSK\LIB entry on the LIBPATH statement in CONFIG.SYS. 2.1.12 TCP/IP NFS and IBM VisualAge C++ compatibility problem ------------------------------------------------------------- If you receive a SYS3175 error when starting NFSD.EXE and you have VisualAge C++ installed, remove \IBMCPP\LOCALE from the SET LOCPATH statement in the CONFIG.SYS file and restart your system. 2.1.13 Tivoli Management Agent ------------------------------ When you uninstall Tivoli (TM) Management Agent, you will receive an incorrect EPFIE231 error message. Ignore this error. Also, if you uninstall TMA, not all the files are removed. You must manually remove the files in the \TIVOLI subdirectory. 2.1.14 TME 10 Distributed Monitoring ------------------------------------ If you are using TME 10 Distributed Monitoring to monitor an OS/2 Warp Server for e-business, you might receive an Exit Code 1001 message. If this occurs, contact Tivoli support for a fix to Tivoli PMR 82307. 2.1.15 WorkSpace On-Demand -------------------------- The following sections contain information about WorkSpace On-Demand. Installing public applications If you installed LAN Server RIPL support in a volume (other than 386 HPFS) and you want to install public applications (such as Lotus Notes) that use IBM Software Installer on a WorkSpace On-Demand client, you must set the EPFINSTDIR parameter of the application's installation object to a directory where the client has write access. To set the EPFINSTDIR parameter: 1. Double-click LAN Server Administration. 2. Right-click the application's installation object. 3. On the Parameters page, set the EPFINSTDIR parameter to a directory where the WorkSpace On-Demand client has write access. For example, if a WorkSpace On-Demand client has the following FIT file entry: Z:\EPFTEMP \\\share> WorkSpace On-Demand documentation If you are using the Convenience Package to remotely administer WorkSpace On-Demand servers and want access to the WorkSpace On-Demand documentation, you can copy the "WorkSpace On-Demand 2.0 Administrator's Guide" from the WorkSpace On-Demand 2.0 CD (\INSTALL\SERVER\NET\A4E11MST.INF). WorkSpace On-Demand 2.0 removal When you uninstall WorkSpace On-Demand 2.0, you can reclaim the space allocated to the WorkSpace On-Demand 2.0 and WorkSpace On-Demand 2.0 client directory trees on the server as follows: 1. Log on the LAN with Administrator authority. 2. Delete all the WorkSpace On-Demand clients. 3. Delete all the WorkSpace 2.0 clients. 4. Log off the LAN and stop the server. To reclaim the space used by the WorkSpace On-Demand 2.0 files, delete the following directory subtrees: \IBMLAN\RPL\BB20.cc \IBMLAN\RPL\MACHINES\BB20.cc \IBMLAN\RPL\MACHINES\MACADDR (if present) Where cc is the country code or region. 2.1.16 DBCS: Fonts are displayed incorrectly -------------------------------------------- In DBCS countries or regions, some fonts at some sizes might be displayed incorrectly. For example, the top of some DBCS characters might be cut off. In particular, this problem occurs with the "8.Helv" font. If this problem occurs, try changing to another font or font size. For this example, changing the "8.Helv" font to "8.Helv Combined" or "8.Helvetica" corrects the problem. 2.1.17 Adobe Type Manager ------------------------- For Adobe Type Manager font support in WIN-OS/2(R) for Thailand, enable the WIN_ATM setting for the WIN-OS/2 command prompts. 1. Right-click WIN-OS/2 Window in the Command Prompts folder and click Properties. 2. Click the Session tab. 3. Click WIN-OS/2 Properties. 4. Select WIN-OS/2 Settings and click OK . 5. Select WIN_ATM from the list and change the value to ON. 6. Save the settings and close the Properties notebook. 2.1.18 WebSphere(TM) Application Server Standard Edition 3.02 for OS/2 ---------------------------------------------------------------------- If you receive the following error message when installing WebSphere Application Server Standard Edition 3.02 for OS/2 (WebSphere), it indicates an incompatibility with your system's default Java(TM) Virtual Machine (JVM): Library file CPPOS2.DLL not found To correct the problem: 1. Open an OS/2 window 2. On the command line, type the following command to determine the system's default JVM: java -fullversion If it is the JVM from IBM OS/2 Warp Developer Kit, Java(TM) 2 Technology Edition, Version 1.3, you must change the PATH statement in the CONFIG.SYS file. 3. Open the CONFIG.SYS file in a text editor. 4. Locate the following entries in the PATH and move them to the end of the PATH: x:\java13\jre\bin;x:\java13\bin 5. Shutdown and restart your machine for the change to take effect. After rebooting, when the operating system searches the PATH for the JVM, the entry from IBM OS/2 Warp Developer Kit, Java(TM) Technology Edition, Version 1.1.8 is found first, and its JVM is used. After you have performed these steps, start the WebSphere installation program again. 2.1.19 Running JAVAKEY ---------------------- To run JAVAKEY, you must add the following line to the CONFIG.SYS file: SET SHELLHANDLESINC=10 2.1.20 Creating partitions with LVM command-line interface ---------------------------------------------------------- To create a partition using the LVM command line interface, the Free space ID parameter must not have any leading or trailing spaces between it and the surrounding commas. 2.1.21 Syntax Highlighting in DBCS version of EPM ------------------------------------------------- If you are using the EPM editor to edit .CMD files on a DBCS version of the Convenience Package, some of the characters might not be visible if you are using Syntax Highlighting. The characters are present in the file, but they are not visible because they are displayed in the same color as the background. To correct this, you must edit the Syntax Highlighting configuration file that is used when you are editing .CMD files. On the boot drive of your system, change to the \OS2\APPS directory and edit a file named EPMKWDS.CMD. Once the file is open, search for lines whose last two entries are -1 and 15. On each of those lines, change the 15 to a 12. This makes the text display in a color that is different from the background color, making it visible. 2.1.22 TCPBEUI on a DHCP client ------------------------------- To configure TCPBEUI protocol on a server, use a static host name and IP address in the TCP/IP configuration. To configure TCPBEUI protocol on a server that is a DHCP client, use a NetBIOS Name Server to allow your TCPBEUI clients to resolve the IP address of the server. Assign the TCPBEUI parameter "Seconds to pause between TCP/IP interface checks" a value of 1 (or INTERFACERATE = 1, in the protocol.ini file). The default value is 300. It is recommended that you do not configure the server as a DHCP client. 2.1.23 ACLs on JFS volumes -------------------------- On a LAN File and Print Server system, if an Access Control List (ACL) exists for one or more directories on a JFS volume, make sure the server is started before running commands that use the ACLs, such as BACKACC and NET ACCESS. If the server is not started before the commands are run, a SYS3175 trap message might occur. 2.1.24 Screen savers on security-enabled servers ------------------------------------------------ On security-enabled servers, the Presentation Manager lockup/autodim function is disabled. To restore the autodim function to guard against display phosphor burn-in, you can specify a sequence of up to 100 bitmaps to be displayed. Currently, the following line in the CONFIG. SYS file causes OS/2 Security Enabling Services to display the bitmap continuously while awaiting logon: SET BACKGROUNDBITMAP="bitmap.BMP" where bitmap.BMP is the fully-qualified name of a bitmap file. If no file is specified, a default OS/2 logo bitmap is used. To enable the Screen Saver function, add the following line to your CONFIG.SYS file: SET BACKGROUNDBITMAP2="bitmap.BMP" where bitmap.BMP is the fully-qualified name of another bitmap you want to use. If the file name is in the form bitmapNN, where NN represents digits 00-99, the file name specifies that it is the first of a sequence of files to be displayed cyclically. To specify the delay interval between the bitmaps, add the following lines to your CONFIG.SYS file: SET BACKGROUNDBITMAPDELAY=300 SET BACKGROUNDBITMAPDELAY2=60 where the BACKGROUNDBITMAPDELAY value is the amount of time, in seconds, to display the BACKGROUNDBITMAP file before displaying the first bitmap in the sequence. The default is 300 seconds or 5 minutes. The BACKGROUNDBITMAPDELAY2 value is the amount of time, in seconds, to delay between the display of the bitmap sequence designated by BACKGROUNDBITMAP2. The default is 60 seconds or 1 minute. The minimum delay values for both statements are 1 second, and the maximum values 3999 seconds. To minimize processing overhead, the bitmaps should be small in size and the display interval time fairly long. 2.1.25 File server alias path modification ------------------------------------------ If you want to change the path of an alias that is already being shared, you must first stop sharing that alias and then change the path in the Properties notebook of the alias. To change the path of an alias: 1. View the users connected to the share by typing NET SHARE at an OS/2 Window. 2. If no users are connected, type NET SHARE /D to stop sharing the alias. 3. In the LAN Server Directory Resource Definitions folder, right-click the alias definition icon, and from the pop-up menu, click Properties. 4. Type the resource path for the alias in the Path field. 5. Close the Properties notebook. If the alias is shared at server startup, it is automatically restarted. 2.1.26 Lotus SmartSuite(R) 97 ----------------------------- For Lotus SmartSuite 97 on SMP machines, you must run EXECMODE against each of the following applications: * Lotus 1-2-3 (TM) * Lotus Freelance Graphics (TM) * Lotus WordPro (TM) * Lotus Approach (TM) * Lotus Organizer To run this exec, type the following at the command line: execmode xxxxxx.exe Where xxxxxx.exe is the name of executable file for the application. 2.1.27 Multiple server names ---------------------------- OS/2 Warp Server for e-business provides support for multiple server names. If you implement this support, you must tune your server for the number of server names multiplied by the number of clients using those names. For example, if you have 20 clients that each connect to the server using two server names, tune the server as though 40 clients are connecting to it. If you have 50 clients, half of which connect to the server using one server name and the other half using two server names, tune the server as though 75 clients are connecting to it. 2.1.28 Performance Tuning Assistant is informational only --------------------------------------------------------- The Performance Tuning Assistant (NSTUNE.EXE) is now informational only. It provides a starting point from which you can begin tuning your server and workstations, but the apply button is disabled and the program will not make permanent changes to your files. ------------------------------------------------------------------------ 2.2 Remote IPL The following sections contain information about troubleshooting for Remote IPL (RIPL). There are two key points to make initially about Remote IPL: * RIPLing a Convenience Package for OS/2 Warp 4 client A Convenience Package for OS/2 Warp 4 client can be RIPLed only from a Convenience Package for OS/2 Warp Server for e-business server. * RIPLing from a Convenience Package for OS/2 Warp Server for e-business server A Convenience Package for OS/2 Warp Server for e-business server can RIPL either OS/2 Warp 4 clients or Convenience Package for OS/2 Warp 4 clients but not both at the same time. 2.2.1 "TR Shared RAM" Token Ring Adapter on RIPL clients -------------------------------------------------------- Using "TR Shared RAM" Token Ring adapters in both a RIPL server and a RIPL client might produce a trap when the RIPL client is started. This trap does not occur with every system restart. A simple workaround is to restart the RIPL client. A longer-term solution is to upgrade to a newer, PCI Token Ring card. 2.2.2 RIPL for clients must be restarted manually after running TCPCFG2 ----------------------------------------------------------------------- If you configure TCP/IP on a RIPL client that does not have the Boot Manager installed, you might have to reboot manually after completing TCP/IP configuration with TCPCFG2. At the end of TCP/IP configuration of a RIPLed client, a dialog box notifies you that the changes will not take affect until you reboot and that you should click the OK button to reboot the machine. However, clicking OK does not restart the machine. It returns you to the OS/2 command prompt with the following message: Reboot Server Boot manager not installed If this message displays, restart your system manually. 2.2.3 RIPL for DBCS OS/2 Warp 4 clients --------------------------------------- To use RIPL on DBCS OS/2 Warp 4.0 systems, perform the following steps in the server RIPL tree (IBMLAN\RPL\OS2.40): 1. Install OS/2 Warp 4.0 FixPak FX05005 and the PTF for your country or region from the list below using the directions that accompanied them. Japan: PTF JR12961 Taiwan: PTF TW99002 China: PTF CN99002 2. Delete the OS2DBCS and OS2DBCS.FNT files. To obtain the OS/2 Warp 4.0 FixPak FX05005 and the correct PTF, contact your IBM representative. 2.2.4 OS/2 RIPL clients ----------------------- If you installed the \IBMLAN\RPL or the \IBMLAN\RPLUSER directory on a non-386 HPFS volume, your OS/2 RIPL clients might not boot. To fix this, update the \IBMLAN\IBMLAN.INI file and increase the MAXOPENS parameter in the [server] section. The recommended values are as follows: * For OS/2 only: MAXOPENS = (# of RIPL clients) * 70 * For OS/2 plus CM/2: MAXOPENS = (# of RIPL clients) * 115 Other applications that use RIPL clients and have their file trees located in the \IBMLAN\RPL directory tree (or somewhere else on the FAT volume), also contribute to the number of open files and must be accounted for in the MAXOPENS parameter. 2.2.5 RIPL disk space ---------------------- For this version, disk space for RIPL is not checked. RIPL can put \IBMLAN\RPL and \IBMLAN\RPLUSER on different drives than LAN Server itself. \IBMLAN\RPL needs 70MB and \IBMLAN\RPLUSER needs 40MB (110MB total). However, additional space must be reserved for each OS/2 version that will be RIPLed. Some example space requirements in \IBMLAN\RPL are: OS/2 Warp 4 182MB OS/2 Warp 4, DBCS 280MB Convenience Package for OS/2 Warp 4 155MB Convenience Package for OS/2 Warp 4, 235MB DBCS WorkSpace On-Demand 2.0 195MB WorkSpace On-Demand 2.0, DBCS 250MB 2.2.6 RIPL for NLV-enabled OS/2 Warp 4 clients ---------------------------------------------- If you want to RIPL to and install a FixPak on an NLV-enabled client, you must perform the following steps on the server: Note: The following steps use a Canadian-French client and an English server as examples. 1. Install an English version of the Convenience Package and make it the domain controller. Note: Do not select OS/2 RIPL support during installation. 2. Following a successful installation, using Selective Install, install the Canadian-French codepage and keyboard. 3. After installation, at an OS/2 Window, change to the \CID\SERVER\IBMLS directory of the OS/2 Warp Server for e-business CD. 4. Type the following and press Enter: LANINSTR /SRV 5. From the displayed protocol window, select and add IBM IEEE 802.2 support. 6. From the Install and Remove window, select OS/2 Remote IPL support and click OK. 7. Shut down and restart the system. 8. Follow the directions in the "Network Administrator Tasks" book to create the Canadian-French RIPL client. 9. Install the latest OS/2 Warp 4 FixPak on the RIPL tree that resides on the server. 10. Type the following command at an OS/2 window: GETRPL /O:os2.40 11. Create the OS/2 client image for the Canadian-French client. 12. Type the following command at an OS/2 window to start Remote IPL: NET START RPL 2.2.7 RIPL capability removal ----------------------------- If you want to remove RIPL capability from a server, make sure that the following things are true of the machine from which RIPL capability is being removed: * The machine has no RIPL clients * WorkSpace On-Demand 2.0 is not installed. If it is, follow the directions in the section WorkSpace On-Demand 2.0 removal. 2.2.8 RIPL tree --------------- To service a RIPL tree, you must use the latest version of the SERVICE.EXE or FSERVICE.EXE file. This can be obtained through your IBM Service representative. If you are unable to obtain the latest version of either of these files, you can manually perform the actions that these files perform automatically. To do this, change the order of all of the IFS statements in the CONFIG.SYS file so that they are immediately after the PAUSEONERROR= statement. For example, if your CONFIG.SYS file contains the following lines: PAUSEONERROR=NO IFS=D:\OS2\JFS.IFS /AUTOCHECK:* /CACHE:1024 DEVICE=D:\OS2\INSTALL\IBMCSFLK.SYS D:\OS2\INSTALL\IBMCSFLK.LST CALL=D:\OS2\INSTALL\IBMCSFLK.EXE D:\OS2\INSTALL\IBMCSFLK.LST IFS=D:\OS2\HPFS.IFS /CACHE:2048 /CRECL:4 /AUTOCHECK:CD move the second IFS statement after the first: PAUSEONERROR=NO IFS=D:\OS2\JFS.IFS /AUTOCHECK:* /CACHE:1024 IFS=D:\OS2\HPFS.IFS /CACHE:2048 /CRECL:4 /AUTOCHECK:CD DEVICE=D:\OS2\INSTALL\IBMCSFLK.SYS D:\OS2\INSTALL\IBMCSFLK.LST CALL=D:\OS2\INSTALL\IBMCSFLK.EXE D:\OS2\INSTALL\IBMCSFLK.LST 2.2.9 RIPL for Arabic OS/2 Warp 4 clients ----------------------------------------- Configuring RIPL for Arabic OS/2 Warp 4 clients requires the following preparation: 1. Install the US English version of the Convenience Package, configured for an Arabic country and keyboard. 2. After the initial installation of the Convenience Package, install the OS/2 Remote Boot (RIPL) service on the server using the LANINST command in the \IBMLAN\INSTALL directory on the drive where LAN services were installed. 3. Install the Arabic OS/2 Warp 4 RIPL tree on the server using Arabic OS/2 Warp 4 RPLINST. 4. Run the GETRPL command. 5. Make the following changes to the RIPL tree \IBMLAN\RPL\MACHINES\DEFALT40\CONFIG.DEF file: a. Change COUNTRY code from 966 to 785 as follows: Before the change: COUNTRY=966,Z:\OS2\SYSTEM\COUNTRY.SYS After the change: COUNTRY=785,Z:\OS2\SYSTEM\COUNTRY.SYS b. Change keyboard DEVINFO to AR238 or AR470 as follows: DEVINFO=KBD,AR238,Z:\OS2\KEYBOARD.DCP or DEVINFO=KBD,AR470,Z:\OS2\KEYBOARD.DCP AR238 is the regular Arabic 102 keyboard. AR470 is the Arabic 101 keyboard. The server does not need to be shut down or rebooted after these changes are made in the RIPL tree. After these changes are made, the client remote IPL requester icons may be created, and the remainder of the OS/2 Warp 4 RIPL preparation can be completed as usual. 2.2.10 JFS support for OS/2 Warp 4 RIPL clients ----------------------------------------------- Journaling File System (JFS) support can be added to OS/2 Warp 4 RIPL clients by adding the following line to the client CONFIG.SYS file: IFS=Z:\OS2\JFS.IFS /AUTOCHECK:* Update CONFIG.SYS in the IBMLAN\RPLUSER\%clientname% directory, if it exists. If the IBMLAN\RPLUSER\%clientname% directory does not exist, make the change to the CONFIG.SYS file in the IBMLAN\RPL\MACHINES\%clientname% directory. Adding the line to the CONFIG.SYS in the IBMLAN\RPL\MACHINES\DEFALT40 directory gives support for any clients created after the change. ------------------------------------------------------------------------ 2.3 Commands, CONFIG.SYS statements, and Messages ------------------------------------------------- The following section contains information about OS/2 commands, CONFIG.SYS statements, and error messages. 2.3.1 Kernel file message ------------------------- If you receive the error message "A kernel file is missing from the disk," the missing file is one of the following: OS2KRNL, OS2LDR, OS2BOOT. These files are hidden in the root directory of the server. You receive this message if you have deleted one of these files or if your disk becomes corruped. If your disk is corrupted, replacing the files might fix the problem. 2.3.2 VIRTUALADDRESSLIMIT ------------------------- The default value of the VIRTUALADDRESSLIMIT CONFIG.SYS statement has been changed from 2048 (2 gigabytes) to 1024 (1 gigabyte). 2.3.3 XCOPY ----------- In the XCOPY command syntax using the /S and /E parameters together, if a source is specified without a trailing backslash "\", (for example XCOPY d:\aaa), that source could be either a file or a directory. Because of this, if the source cannot be found, the root directory tree is replicated on the target. This occurs even if the source not found is a file. For more information about XCOPY, refer to the Command Reference. 2.3.4 PREPACL ------------- On some systems, especially those with MMOS2 installed, you might have a problem running PREPACL, a 386 HPFS command. To determine if you will have this problem, run PREPACL with no parameters, for example: PREPACL If no help text is displayed, the system is not finding the correct LSI.MSG file. To work around this problem, type the following command at a command prompt and press Enter: DPATH d:\IBMLAN\INSTALL;%DPATH% Where d: is the directory where \IBMLAN is located. 2.3.5 SYS1718 error message --------------------------- If you receive a SYS1718 error message about missing IBMLANLK files after you install a product and restart your system, perform the following steps: 1. Insert the Convenience Package for OS/2 Warp Server for e-business CD. 2. At an OS/2 window, change to the \CID\SERVER\IBMLS\IBM500S1 directory on the CD. 3. Type the following commands to restore the missing locked file device drivers: PKUNZIP2 SRVINSTR.ZIP C:\OS2\INSTALL OS2\INSTALL\IBMLANLK.* PKUNZIP2 SRVINSTR.ZIP C:\OS2\INSTALL OS2\INSTALL\LSI.MSG PKUNZIP2 SRVINSTR.ZIP C:\OS2\INSTALL OS2\INSTALL\LSIH.MSG 4. Shut down and restart your system to process the locked files and complete the product installation. ------------------------------------------------------------------------ 2.4 Associated bitmap-fonts --------------------------- Note: This feature is available only for the following languages: o Japanese o Traditional Chinese o Simplified Chinese The Associated Bitmap-fonts feature displays higher-quality characters in small point sizes by using bitmap fonts instead of outline fonts. It also improves the rendering performance because the bitmap fonts display more quickly. Note: Install all DBCS bitmap fonts for this feature to work effectively. The following limitations and restrictions apply to Associated Bitmap-fonts: * If you want to print output that is identical to your screen layout, disable Associated Bitmap-fonts. To disable this feature: 1. From the System properties notebook (OS/2 System --> System Setup --> System), click the Font page. 2. Click the + symbol to move to the second Font page. 3. Clear the Activate check box. 4. Close the System properties notebook and restart the system. * Unicode fonts are not supported. * The sample characters in the OS/2 font dialog box cannot switch to a bitmap font. * The IME Conversion String cannot switch to a bitmap font. Japanese users can refer to the "Japanese User's Guide (Nihongo-ban Goshiyou no Tebiki)" for more information. ------------------------------------------------------------------------ 2.5 Hardware device and device driver considerations ---------------------------------------------------- The following sections contain information about hardware devices and device drivers. 2.5.1 3Com Fast Etherlink XL network adapter boot problem --------------------------------------------------------- If you install the Convenience Package on a PC 365 computer with a 3Com Fast Etherlink XL network adapter, you may experience a system hang during boot. There are two workarounds possible for this problem: * Disable Hardware detection by pressing Alt-F1 then F6 on bootup. This is most appropriate when you are installing from a CD. * Remark out Serial.snp in the snoop.lst file. This is most appropriate when you are installing from a CID server. 2.5.2 Dell OptiPlex GX110 ------------------------- Customers may experience an error when installing the Convenience Package on a Dell OptiPlex GX110 with an integrated Ethernet adapter. This system has an integrated 3Com Ethernet adapter that appears to the operating system to be a 3Com Fast Etherlink XL/Etherlink XL OS/2 adapter. This causes the incorrect device drivers to be installed (EL90X.OS2 dated 01/24/99 and EL90XIO2.NIF dated 01/09/97) and when the system is restarted, the following message is displayed: 3Com Fast Etherlink XL/Etherlink XL OS/2 NDIS driver v4.0z ERROR: Network adapter not found or not responding. Updated device drivers are available from the following 3Com Web site: http://support.3com.com Search for "3C905C" and "3C90XN2.EXE" to locate the panel with the correct download file, then download the EtherCD v5.2 Disk 2 of 2 for the 3C90X Adapter Family, file named 3C90XN2.EXE. This is a self-extracting file. On the diskette created when the file is extracted is a directory named \ndis2\os2. In that directory is the driver for the 3Com Fast Etherlink/ Etherlink Family OS/2 adapter. The files are EL90XIO2.NIF dated 01/09/97 and EL90X.OS2 dated 11/09/99. This driver will work with the integrated adapter in the Dell OptiPlex GX110. 2.5.3 Device driver adapters ---------------------------- * Refer to the Device Driver Pak Online for information regarding device drivers and to download device drivers. Go to the following Web address for more information: http://service.software.ibm.com/os2ddpak/ * The IBM EtherStreamer MC32 Adapter is not supported. 2.5.4 IBM ISDN Co-processor adapters ------------------------------------ Intermittent problems can occur on systems with more than two IBM Integrated Services Digital Network (ISDN) co-processor adapters. A message might indicate that an adapter has stopped responding. Attempts to restart the adapter, through Call and Port Management, may result in an error message stating that an internal processing error has occurred in the ISDN Co-processor Support Program. 2.5.5 802.2 RIPL with a DOS Network Adapter device driver --------------------------------------------------------- When you use the 802.2 Remote IPL method to boot a new machine, your client system might hang after loading the DOS network adapter device driver. If you experience this problem, contact the network adapter manufacturer and obtain the latest version of the DOS device driver for the network adapter. Copy the new device driver to the \IBMLAN\DOSLAN\LSP\DOS directory on the drive where IBMLAN is installed. 2.5.6 IBM Token-Ring adapters ----------------------------- Certain IBM token-ring adapters might cause a system to hang when the remote IPL client downloads the 802.2 RIPL Boot record. This problem might occur with the following adapters: * Turbo 16/4 Token-Ring ISA adapter * Auto Wake Token-Ring ISA adapter * Auto 16/4 Token-Ring ISA adapter When the system hangs, the screen usually displays a value of 0001 or 0002 for SF count, and a value of 0001 for SN count. If this occurs: 1. Go to the following Web address for an update of the microcode for the token-ring adapter: http://www.networking.ibm.com 2. Follow the directions on the Networking Tech Support pages to download the IBM Auto 16/4 Token-Ring Network ISA Adapter. 3. Download the files in the flash update package. 4. Follow the instructions in the flash documentation file to install the flash update. You can use a temporary workaround until the adapter microcode can be updated: 1. Modify the remote IPL control file that describes the remote IPL boot block for adapters that are compatible with the IBM token-ring. The path and name of this file is: d:\IBMLAN\RPL\OS2xxNTR.CNF Where xx is 30 or 40. 2. Make a backup copy of the original file, and then use an ASCII text editor to modify the file. Move the "RPL DOS\RPLBOOT.SYS" statement down so that it follows the "DAT DOS\UFSD.SYS" statement. 3. After you update the network token-ring adapter microcode on all remote IPL clients, restore the original version of the OS2xxNTR.CNF file. 2.5.7 CPU initialization on a Compaq 4500 ----------------------------------------- If a CPU is removed from a Compaq 4500 computer with multiple CPUs (leaving a gap), OS/2 Warp Server for e-business does not see the remaining CPUs that sequentially are after the removed CPU. For example, if the number 2 CPU is removed from a machine containing four CPUs, after a reboot, the remaining CPUs are initialized, but CPU 3 and CPU 4 are not be seen or used by the software. Only CPU 1 will be used. 2.5.8 SMP system with OS2APIC.PSD --------------------------------- SMP systems using OS2APIC.PSD (such as the Intel MPS-compliant systems) might experience a hang after running normally for some time. If this happens, try adding /APIC to the end of the PSD= statement in the CONFIG.SYS file. 2.5.9 IBM ServeRAID adapters ---------------------------- The IPSRAID.ADD shipped with this product is version 3.50.01. If you are using the IBM ServeRAID adapter, go to the following Web site for an update (version 4.00 or later) of the BIOS and IPSRAID.ADD: http://www.pc.ibm.com ------------------------------------------------------------------------ 3.0 Fixed IDE Hard Drive and Removable Media Support ----------------------------------------------------- 3.1 Hard Drive Considerations ----------------------------- This section identifies a number of scenarios you might have to take into account as you implement integrated drive electronics (IDE) support for high-capacity hard drives. 3.1.1 Cannot Mark a Partition Installable ----------------------------------------- There is a basic input/output system (BIOS) restriction on many older computers that installable (startable) or bootable partitions must be contained within the first 1024 logical cylinders of the disk. This is true for both enhanced integrated drive electronics (EIDE) and small computer system interface (SCSI) hard disk drives. If LVM fails to allow a partition to be marked installable, the partition is either above 1024 cylinders or the partition spans the first 1024 logical cylinders of the disk. Use LVM to reduce the size of the startable or bootable partition by sufficient MBytes. One way to calculate the correct partition size is to do the following: 1. Edit your CONFIG.SYS file and add the /W or /V parameter to the BASEDEV=IBM1S506.ADD statement. 2. Save this change and restart the system. 3. At initialization, record the far left-hand column of numbers of the geometry information under the "OS2:log" heading; for example, where C=cylinder, H=head, and S=sector: OS2:log C 1027 H 63 S 128 4. Calculate the 1024 cylinder size in MBytes as ( H x S ) / 2. (round down). All bootable partitions must be contained within this size. In this example, the bootable partition must be contained in the first 4032MB of the disk and cannot exceed a single partition size of 4032MB within this area. No bootable partition may extend beyond the first 4032MB. 5. Use the LVM command to resize the partitions then restart the system. 3.1.2 Internal Processing Error on Restart, "Trap D" ---------------------------------------------------- If you experience a Trap D upon system restart when using the /FORCE parameter on IBM1S506.ADD, and you have the NetFinity client installed, use the REMark statement to comment out the BASEDEV=NFDASD.FLT statement in CONFIG.SYS. 3.1.3 Application Install Fails With "Not Enough Space" ------------------------------------------------------- File allocation table (FAT) partitions under OS/2 are limited to a 2.1GB maximum size. High performance file system (HPFS) partitions are limited to a 64GB maximum size. This 2.1GB value is the maximum number that fits into a signed 32-bit integer. Some application software installation programs query OS/2 about the available remaining space in the partition and save the result into a signed 32-bit integer. If more than 2.1GB is available, an overflow occurs giving the appearance that no space is available, and the installation program refuses to continue. Two solutions are: * Partition the remaining space into maximum 2GB partitions. * Retain the large partition, but before trying to install software, create a large temporary file that reduces available space to less than 2.1GB. After installation of the application, delete the temporary file. 3.1.4 Performance Problems with Two Devices on a Single Channel --------------------------------------------------------------- With certain planars, two devices attached to the same IDE channel exhibit performance problems when one device is a slow non-direct memory access (DMA) device like a CD-ROM or removable drive, and the other device is a faster disk drive. To alleviate this problem, move the slow device to the other channel, where it is the only device or is paired with a similar slow device. If moving the device is not possible, you can disable bus mastering for that channel by specifying parameters on the BASEDEV statement for IBM1S506.ADD in CONFIG.SYS. For example, if you wanted to disable bus mastering for the secondary controller, add the parameters "/A:1 /!BM" to the IBM1S506.ADD line in CONFIG.SYS. 3.1.5 Install Diskettes or Utility Diskettes Hang on Boot (APAR JR12065) ------------------------------------------------------------------------ Diskette 1 of the Install or Utility diskette sets may appear to hang on boot, waiting for a removable media device to respond. To avoid this problem: 1. Edit the CONFIG.SYS file on Diskette 1 of the set. 2. Use the REMark statement to comment out the BASEDEV=ibmint13.i13 statement and save the file. 3. Restart the system. 3.1.6 Connecting an External Floppy Disk Drive ---------------------------------------------- When connecting external an floppy disk drive to a ThinkPad 600 or T2x computer with Ultrabay(TM) support installed, the drive letter the system assigns the floppy disk drive (FDD) may not be the drive letter you expect. Check Table 1 for your corresponding configuration to determine the assigned drive letter. Table 1. Floppy disk drive assignment table Configuration ThinkPad 600 T2x Boot with internal FDD Internal: A: Internal: A: only Boot with external FDD External: A: External: A: only Boot with both FDDs Internal: A: Internal: A: External: B: External: B: Boot with no FDD, Internal: A: Internal: A: suspend, connect internal FDD Boot with no FDD, External: B: External: A: suspend, connect external FDD Boot with no FDD, Internal: A: Internal: A: suspend, connect both FDDs External: B: External: B: Boot with external FDD, Not supported Internal: A: suspend, connect internal FDD External: B: 3.1.7 Additional Parameters for IDE Device Drivers -------------------------------------------------- Additional parameters for IDE device drivers are as follows: Parameter Function /V Verbose Mode, displays controller status and drive geometry information during OS/2 initialization. /W Verbose Mode, displays controller status and drive geometry information during OS/2 initialization. Initialization stops after displaying the information for each device, with a "Press Enter to Continue" message. It is possible that the message buffer overflows, resulting in a "Lost message" message. This parameter works correctly on Warp 3 with FP35 or later systems and on Warp 4 systems with FP6 or later. /FORCE Forces the emulation of an IDE CD-ROM drive, even though the drive is not present during OS/2 initialization. For example, the following statements support inserting an internal CD-ROM drive into the Ultrabay of a ThinkPad 755CD after suspend, even though the drive is not present during initialization: BASEDEV=IBM1S506.ADD /A:1 /U:0 /ATAPI /FORCE BASEDEV=IBMIDECD.FLT /UDMA:x If the system is ultra direct memory access (UDMA) capable, this parameter may be used to limit a highest UDMA mode for a system to use. The limit is specified by "x"and it can range from 1 to 9. If the specified value is higher then the maximum UDMA capability, or is 0, the parameter is ignored. ------------------------------------------------------------------------ 3.2 Removable Media Support --------------------------- Removable media devices attach to the system by a variety of interfaces. IDE Integrated drive electronics (IDE) supported with the OS/2 supplied IBM1S506.ADD device driver. EIDE Enhanced IDE (EIDE) supported with the OS/2 supplied IBM1S506.ADD device driver. ATAPI Advanced Technology Attachment Packet Interface (ATAPI) supported with the OS/2 supplied IBMATAPI.FLT device driver. ATA Advanced Technology Attachment (ATA) supported with the OS/2 supplied IBM1S506.ADD device driver. Iomega Zip ATA drives are supported only as single-partition media and can be configured in ATA Compatibility Mode. SCSI Small Computer System Interface (SCSI). Supported with the OS/2 device driver for the SCSI controller to which the device is attached. Many SCSI drivers are supplied with OS/2. If your device is not recognized, you must acquire the proper device driver from the vendor. Consult http://service.software.ibm.com/os2ddpak/html/diskands/index.htm. To ensure correct operation with the Adaptec 1542 SCSI adapter, partition sizes must be less than 1GB. PP Parallel Port-attached devices are supported with vendor-supplied drivers. The device driver must have an ".ADD" extension for the media to be supported as partitioned removable. For example, the SyQuest SyJet parallel drive is properly supported by the vendor-supplied EPST.ADD driver. The Iomega Zip parallel drive uses a vendor-supplied *.SYS driver and is not supported by the partitioned removable support. The SyQuest SparQ and Iomega Zip Plus parallel drives have no OS/2 drivers at all. USB Universal serial bus (USB). Floppy and removable media devices (including CD-ROM, CD-RW devices) are supported with the OS/2 supplied USBMSD.ADD device driver and special CD-ROM class device driver, USBCDROM.ADD. Removable media devices are supported in one of two ways: LARGE FLOPPY The LS-120 drive. PARTITIONED All other magnetic removable media devices. This media appears as a removable hard drive. 3.2.1 Configuring Partition Support (OS2DASD) --------------------------------------------- The configuration statement used to configure partition support is as follows: BASEDEV=OS2DASD.DMD [/LF] [/MP:(disk,count)[,(disk,count)]] Parameter Description /LF Forces all removable devices to be treated as Large Floppy rather than partitioned media. /MP Used to support allocating a predetermined number of drive letters for a partitioned removable media device. Note that this option only applies to partitioned removable devices, and is ignored for any other device type. If the /MP parameter is used, additional parameters apply: disk The integer disk number of the device, as reported by LVM, or the wildcard character * to specify all partitioned removable devices. count The integer count of the number of partitions to reserve for the device. If the wildcard character * is used, it specifies a default number of drive letters to reserve for all partitioned removable devices. Specifying a count for a particular disk overrides this default. Also, if there is media in the device at boot time, and it has more partitions which are eligible to receive drive letters than there are drive letters reserved for the device through the /MP option, the number of drive letters reserved for the device is increased so that every eligible partition on the media has a drive letter. If the /MP parameter is not used, the rules for determining the number of drive letters reserved for a partitioned removable media device are as follows: * If there is no media in the drive at boot time, or the media in the drive has no valid partitions, one drive letter is reserved for the device. * If there is media in the drive at boot time and the media has valid partitions which are eligible for drive letters, the number of drive letters is equal to the number of eligible partitions on the media. Media which is formatted in floppy mode is treated as a single partition and allocated a single drive letter. 3.2.2 Ejecting the Media ------------------------ OS/2 prevents the media from being ejected during data transfers or while there are pending file transactions. The hardware manual eject button is disabled during these times. The eject button is enabled when the media can be safely ejected. There is a new OS/2 utility, EJECT.EXE, that provides a command line method for ejecting the media. The Workplace drive icon now supports the software eject option for these drives as well. For example, the command: EJECT x: where x: is the logical drive letter of one of the partitions on the media, causes the media to be ejected. In order for this command to succeed, there must be no open files in any of the partitions on the media and no open search operations. Removable media that is shared on a server cannot be ejected because of open file handles. If it is necessary to remove the media without restarting the system, issue the following command: CHKDSK x: /F where x: is the logical drive letter of one of the partitions on the media. This frees the media and a subsequent EJECT command to that drive causes the media to be ejected. 3.2.3 Limitations of Partitioned Removable Media Support -------------------------------------------------------- The following limitations apply to partitioned removable media support: * Applications that manipulate partitioned devices, such as file managers, must be updated to test the fixed/removable flag in order to account for partitioned removable devices. Such applications that have not been updated treat the removable devices as fixed and the results are unpredictable whenever media is not present. * Due to the variability of hardware adapter support, installing to or restarting the system from partitioned removable media is not supported. * Optical drive support is unchanged. Partitioned removable media and HPFS do not support optical drives. You should continue to use OPTICAL.DMD and OS2SCSI.DMD. * The following devices were tested during the development of the Partitioned Removable Media Support. Similar devices should operate correctly, as should other removable media devices that are made available with a supporting ADD device driver: o Iomega SCSI Jaz 1GB and 2GB personal hard drives o Iomega Zip ATA 100MB drives (supported only as single-partition media) o Iomega Zip ATAPI 100MB drives o SyQuest SCSI SyJet 1.5GB portable hard drives o SyQuest IDE SyJet 1.5GB portable hard drives o SyQuest SparQ IDE portable hard drives 3.2.4 Large Floppy Removable Media (LS-120) ------------------------------------------- The LS-120 drive supports 120MB diskettes and is compatible with 3.5 inch 1.44MB standard diskettes with improved performance. Limitations of LS-120 Support The following limitations apply to LS-120 support: * If you have an LS-120 drive as drive B, you must not format it from an OS/2 windowed- or full-screen session where the current drive is drive A or drive B. The current drive for an OS/2 windowed- or full-screen session is given as part of the command prompt. For example, if the command prompt in an OS/2 windowed- or full-screen session is [C:\], then drive C is the current drive. * The following devices were tested during the development of the Large Floppy Removable Media Support. Similar devices should operate correctly: o Imation LS-120 o SuperDisk LS-120 3.2.5 CD-ROM Device Manager (OS2CDROM.DMD) ------------------------------------------ The CD-ROM Device Manager (OS2CDROM.DMD) has the following additional features: * Support for read/write blocks for CD-RW media * Support for USB CD-ROM, CD-RW, DVD-ROM, DVD-RAM devices * Low-level formatting for CD-RW and DVD-RAM media * New IOCtl functions added: o Format and Verify Disk (Cat: 8, Funct: 45h) o Execute SCSI-command (Cat: 80h, Funct: 7Ah) o OS2CDROM Features (Cat: 82h, Funct: 63h) o Get CD-ROM Drives (Cat: 82h, Funct: 60h) o Query device parameter (Cat: 08h, Funct: 63h) IOCTL_DISK (08h) ++++++++++++++++ This IOCtl function formats and verifies the disk. Function DSK_FORMATVERIFY (45h) Parameter Packet format struct FmtVerify_param { UCHAR Command; // Bit 7: 0 - start formatting, // 1 - format status }; Data Packet format struct FmtVerify_data { UCHAR Status; // Percent of formatted volume, if such feature supported // 0, if not supported }; Returns 02h Device not ready 03h Bad command (this IOCtl function is not supported) 13h Unsupported parameter 14h Device already in use a3h Uncertain media Compatibility problem If IOCtl function DSK_FORMATVERIFY (45h) is used in an earlier version of OS2CDROM.DMD, return code 03h is returned. It means this version of OS2CDROM.DMD is not supported. IOCTL_CDROMDISK (80h) +++++++++++++++++++++ This IOCtl function executes SCSI a command. Function CDROMDISK_EXECMD (7Ah) Parameter Packet format struct ExecCMD { ULONG ID_code; // 'CD01' USHORT data_length; // length of the Data Packet USHORT cmd_length; // length of the Command Buffer USHORT flags; // flags UCHAR cmd_buffer[16]; // Command Buffer for SCSI command }; flags: #define EX_DIRECTION_IN 0x0001 #define EX_PLAYING_CHK 0x0002 EX_DIRECTION_IN 0, if transfer data to device, 1, if transfer data from device EX_PLAYING_CHK 0, if don't check playing audio, 1, if device plays audio return error Data Packet format Content of the Data Packet depends on the SCSI command. Length is defined by the data_length field in the Parameter Packet. Returns 02h Device not ready 03h Bad command (this IOCtl function is not supported) 13h Unsupported parameter 14h Device already in use Compatibility problem If IOCtl function CDROMDISK_EXECMD (7Ah) is used in an earlier version of OS2CDROM.DMD, return code 03h is returned. It means this version of OS2CDROM.DMD is not supported. IOCTL_CDROMDISK2 (82h) ++++++++++++++++++++++ This IOCtl function returns features of the current DM version, if applied to "CD-ROM2$" device name. Function CDROMDISK2_FEATURES (63h) Parameter Packet format None Data Packet format ULONG driver_status; #define FEATURE_USB_SUPPORT 0x00000001L #define FEATURE_CDRW_SUPPORT 0x00000002L #define FEATURE_EXECMD_SUPPORT 0x00000004L Returns 03h Bad command (this IOCtl function is not supported) Compatibility problem If IOCtl function CDROMDISK2_FEATURES (63h) is used in an earlier version of OS2CDROM.DMD, return code 03h is returned. It means this version of OS2CDROM.DMD does not support this function. IOCTL_CDROMDISK2 (82h) ++++++++++++++++++++++ Returns drive letters for CD-ROM devices if applied to the "CD-ROM2$" device name. Function CDROMDISK2_DRIVELETTERS (60h) Parameter Packet format None Data Packet format struct DriveLetters { USHORT DriveCount; // number of supported CD-ROM drives USHORT DriveFirst; // letter of the first CD-ROM drive }; Returns 03h Bad command (this IOCtl function is not supported) Compatibility problem This function did not work correctly in previous versions of OS2CDROM.DMD. IOCTL_DISK (08h) ++++++++++++++++ This IOCtl function queries device parameters. Function DSK_GETDEVICEPARAMS (63h) Parameter Packet format and Data Packet format Parameter and data packet formats are standard but the values of two fields of BIOSPARAMETERBLOCK depend on the device and media type. Media Descriptor contains information about the media type: Table 2. Media type Value CD-R 4 CD-ROM 5 DVD-ROM 6 DVD-RAM 7 CD-RW 8 DVD-R 9 DVD-RW 10 DVD+RW 11 If the media allows writing but cannot be written at the moment (for example, the device cannot write to such media type or the disk is write-protected), 128 is added to the value. The Device Type field contains information about the device type. If the device cannot write on the disk inserted, the value 7 is returned. If the device allows writing on the disk inserted (for example, DVD-RAM disk in the DVD-RAM device or CD-RW disk in the CD-Writer), the value 8 is returned. 3.2.6 CD-RW Media Support in IBMIDECD.FLT IBMIDECD.FLT now supports IDE CD-Writers for reading and writing. 3.3 Supported IDE Controllers, Known Restrictions and Limitations ----------------------------------------------------------------- This section provides a table listing the supported IDE controllers and identifies known restrictions and limitations. 3.3.1 Supported Chipset Table ----------------------------- The OS/2 IDE Controller Adapter Device Driver (IBM1S506.ADD) supports the following PCI IDE Controllers: Table 3. Supported PCI IDE Controllers Controller Controller Name Information Highest UDMA Comments CMD640 First CMD640 RZ1000 First RZ1000 I82371FB INTEL82371FB PIIX3 Intel PIIX3 IDE ORION INTEL_ORION PIIX4 Intel PIIX4 IDE ATA 33 I82801AA Intel 82801AA IO ATA 66 See Intel chipsets HUB restrictions. I82801AB Intel 82801AB IO ATA 33 HUB I82801BA Intel 82801BA IO ATA 100 See Intel chipsets HUB restrictions. CMD646 CMD 646 PCI 2 IDE ATA 33 CMD648 CMD 648 PCI 2 IDE ATA 66 VIA586B VIA 586B PCI 2 IDE ATA 33 See VIA chipsets restrictions. VIA596B VIA 596B PCI 2 IDE ATA 66 See VIA chipsets restrictions. VIA686A VIA 686A PCI 2 IDE ATA 66 See VIA chipsets restrictions. SIS630 SIS 630 PCI 2 IDE ATA 66 See SiS chipsets restrictions. Restrictions and Limitations This section covers some restrictions for IBM1S506.ADD. These restrictions are caused mainly by hardware problems. Intel chipsets restrictions In case there are two devices on a channel on any Intel 82801 chip, the top UDMA mode is limited to UDMA 2. VIA chipsets restrictions IBM1S506.ADD has the following limitations for VIA IDE controllers listed above: * All of the chipsets have a problem with 40-pin cable detection. To ensure the proper operation, check the type of IDE cables being used. If you have a 40-pin cable on any channel, specify the parameter /UDMA:2 in CONFIG.SYS. Usage of this parameter is described above. * Any VIA chipset, which is not in the list above, but has the same Device ID, is detected as VIA586B and performance is dropped down to UDMA 2. SiS chipsets restrictions IBM1S506.ADD has the following limitations for SiS IDE controllers listed above: * Since there is a problem for these IDE controllers to work in UDMA mode with the secondary channel when 40 pin cable is installed, the driver drops to PIO mode on this channel if 40-pin cable is detected. This restriction does not apply to the primary channel. * Do not use /UDMA:x parameter on SiS IDE controllers. ------------------------------------------------------------------------ 4.0 LSI Logic SDMS Support -------------------------- This section discusses the LSI Logic Storage Device Management System (SDMS) support. ------------------------------------------------------------------------ 4.1 LSI Logic Devices Supported ------------------------------- The SYM8XX.ADD driver supports the following devices and their associated LSI Logic host adapters: SYM53C810, SYM53C810A, SYM53C810AE (SYM8100S, SYM8100ASP, SYM20810) SYM53C815 (SYM815XS, SYM8150SP) SYM53C825, SYM53C825A (SYM8250S, SYM8251S, SYM8251D, SYM8250ASP, SYM8251ASP, SYM8251AD) SYM53C860, SYM53C860AE (SYM8600SP, SYM20860) SYM53C875, SYM53C875E (SYM8750SP, SYM8751SP, SYM8751SPE, SYM8751D) SYM53C876 (SYM22801, SYM22802) SYM53C885 SYM53C895 (SYM8951U, SYM8952U) SYM53C895A (SYM8953U) The SYM_HI.ADD driver supports the following devices and their associated LSI Logic host adapters: SYM53C895A (SYM8953U) SYM53C896 (SYM22910, SYM21002, SYM22902) SYM53C1010 (SYM8955U, SYM22915, SYM21040, SYM22903) Note: Both the SYM8XX.ADD and SYM_HI.ADD drivers support the SYM53C895A chip. If both drivers have been installed, whichever driver appears first in the CONFIG.SYS file controls the SYM53C895A chip. Refer to the section Driver Order in the CONFIG.SYS File in this document to understand the importance of driver order. ------------------------------------------------------------------------ 4.2 Driver Order in the CONFIG.SYS File --------------------------------------- Because of the way OS/2 assigns drive letters, the order in which drivers appear in the CONFIG.SYS file is important. The drivers must appear in the order in which the drive letters are to be assigned. In particular: * OS/2 will install the BASEDEV= line at the beginning of the target system's CONFIG.SYS file regardless of where the line is located in that file on Diskette 1. You may need to rearrange the order in which drivers appear in the CONFIG.SYS file for the target system. * The driver for the host adapter to which the boot device is attached must appear before all other BASEDEV= drivers in the CONFIG.SYS file. * If you are installing both SDMS drivers and a host adapter containing the SYM53C895A chip, the driver that will control that host adapter will be the driver that appears first in the CONFIG.SYS file. If one of the two SDMS drivers is controlling the boot drive, that driver will also control the SYM53C895A chip, since it must appear first in order for the boot drive to be recognized. Refer to the OS/2 documentation to fully understand this requirement. ------------------------------------------------------------------------ 4.3 Command-line Options ------------------------ Your host adapter has a default configuration that consists of optimal values for operation. You may decide to alter these default values if there is a conflict between device settings or if you need to optimize system performance. Some values may be changed using the SCSI BIOS Configuration Utility provided with some members of the LSI Logic family of host adapters. Refer to the PCI Storage Device Management System SDMS 4.0 User's Guide for information on the availability and use of the SCSI BIOS Configuration Utility. In addition, the SDMS OS/2 device drivers have several embedded functions that can be accessed by using switches on the command line in the CONFIG.SYS file. Note: Values are applied in the following order: o Manufacturer's settings o SCSI BIOS Configuration Utility changes o Command-line options When applying new values using the command-line options, changes in synchronous and wide negotiations may only decrease speed or reduce width. Any changes that attempt to increase speed or width are ignored. The options available using command-line switches are described below. The SYM8XX.ADD driver is used in all examples; SYM_HI.ADD may be substituted for SYM8XX.ADD with identical results. The following conventions are used: * The term "hba" represents the logical number of a host adapter as displayed by the Verbose option in the column headed HBA. This is not the SCSI ID of the host adapter. Use an hba value with no ID following it to indicate all devices on an adapter. * The term "id" represents a SCSI target ID on the indicated adapter. To indicate all devices on a host adapter, do not use the SCSI ID of the host adapter for the id value. Instead, use the hba value as indicated in the preceding paragraph. * Square brackets [ ] indicate optional information * Asterisk * indicates the pattern enclosed in the [ ] may be repeated Table 4 lists the command-line options discussed. Table 4. Command-line options Option Function /VERBOSE Display banner, version number, and SCSI bus information. /!DM Disable use of the IBM-supplied DASD manager. /!SM Disable use of the IBM-supplied SCSI manager. /EXCLUDE Disable a host adapter. /SYNCH_RATE Set the maximum synchronous transfer rate. /SYNCH_OFFSET Set the maximum synchronous offset. /TIMEOUT Set a timeout mechanism to detect certain errors. /DISCONNECT Disconnect from the bus during an I/O transfer. /PARITY Enable or disable the SCSI bus data integrity checking. /QTAG Queue outstanding command per SCSI device. /WIDTH Set data transfer rate. 4.3.1 Using the /VERBOSE (or /V) Option --------------------------------------- This option appears on the command line by default. It enables display of a banner, version number, and SCSI bus information during startup of the system. Usage: /VERBOSE For example, to see more detailed information displayed when you boot, the line in the CONFIG.SYS file that loads SYM8XX.ADD should look like this: BASEDEV=SYM8XX.ADD /VERBOSE or BASEDEV=SYM8XX.ADD /V To disable this feature, remove this switch from the command line. 4.3.2 Using the /!DM Option --------------------------- This option disables use of the IBM-supplied DASD manager (OS2DASD.DMD) for the devices listed. The DASD manager supports direct access devices such as hard drives. Usage: /!DM[,]* For example, to disable OS2DASD.DMD for devices on host adapter 0 at target IDs 3 and 5, the line in the CONFIG.SYS file that loads SYM8XX.ADD should look like this: BASEDEV=SYM8XX.ADD /!DM<0:3>,<0:5> 4.3.3 Using the /!SM Option --------------------------- This option disables use of the IBM-supplied SCSI manager (OS2SCSI.DMD) for the devices listed. The SCSI manager supports SCSI tape drives. Usage: /!SM[,]* For example, to disable OS2SCSI.DMD for devices on host adapter 0 at target IDs 3 and 5, the line in the CONFIG.SYS file that loads SYM8XX.ADD should look like this: BASEDEV=SYM8XX.ADD /!SM<0:3>,<0:5> 4.3.4 Using the /EXCLUDE (or /X) Option --------------------------------------- This option disables a host adapter so that it is not seen by the SDMS OS/2 device drivers. This allows a host adapter to be ignored without physically removing the board from the system. This may be necessary if the adapter in question is causing a resource conflict. Note: If you exclude the adapter to which the boot device is attached, you will not be able to boot. Usage: /EXCLUDE[,]* chip A unique identifier that indicates the LSI Logic board type. The Verbose option displays a table with this value appearing in the "CHIP" column. bus Represents the PCI bus number into which the adapter is plugged. The Verbose option displays a table with this value appearing in the "BUS" column. dev/func The number derived by combining the PCI device and function numbers and serves as a unique board identifier in conjunction with the PCI bus. The Verbose option displays a table with this hexadecimal value appearing in the "DEV/FUNC" column. It may contain an A, B, C, D, E, or F as part of its value. For example, to exclude a host adapter with chip type F, PCI bus number 0 and dev/func number A0, the line in the CONFIG.SYS file that loads SYM8XX.ADD should look like this: BASEDEV=SYM8XX.ADD /EXCLUDE or BASEDEV=SYM8XX.ADD /X 4.3.5 Using the /SYNCH_RATE (or /SR) Option ------------------------------------------- This option sets the maximum synchronous transfer rate (in MB transfers per second) to negotiate with a particular device. The allowable values for this setting are 0, 5, 10, 20, and 40 MB transfers per second, if the adapter is capable of the specified speed. All host adapters in the LSI Logic family support at least 10 MB transfers per second; some support 20 or 40MB transfers per second. To turn off synchronous transfers for a particular device, specify 0 (zero). The value set by this option only defines the maximum transfer rate negotiated. The actual rate also depends on the device's capability. The default value is the fastest transfer rate that is supported by a particular host adapter. Note: The maximum synchronous transfer rates effectively double when the adapter and device permit wide transfers (See the /WIDTH option). For example, a synchronous transfer rate setting of 40MB transfers per second will actually produce a transfer rate of 80MB transfers per second if the adapter and device both allow and are set to perform wide transfers. Usage: /SYNCH_RATE=n[,n]* n The rate of Mbyte transfers per second. Allowable values are 0, 5, 10, 20, or 40. The following examples illustrate how to use this option: * To turn off synchronous transfers to ID 3 on host adapter 0, the line in the CONFIG.SYS file that loads SYM8XX.ADD should look like this: BASEDEV=SYM8XX.ADD /SYNCH_RATE=0<0:3> * To set synchronous transfers to 10MB transfers per second on all devices on host adapter 1, the line in the CONFIG.SYS file that loads SYM8XX.ADD should look like this: BASEDEV=SYM8XX.ADD /SR=10<1> 4.3.6 Using the /SYNCH_OFFSET (or /SO) Option --------------------------------------------- This option sets the maximum synchronous offset to negotiate with a particular device. The allowable values for this setting are 0 to the maximum synchronous offset supported by the specified adapter. The LSI Logic controller chips support offsets up to 31. Refer to your host adapter user's guide for information on the maximum offset supported by your host adapter. If 0 (zero) is specified for the synchronous offset value, synchronous transfers are turned off for any specified device. The value set by this option only defines the maximum offset that is negotiated. The resulting rate also depends on the device's capability. The default value is the maximum offset that is supported by a particular host adapter. Usage: /SYNCH_OFFSET=n[,n]* n Represents synchronous offset. This value can be 0 up to the maximum synchronous offset for the adapter. For example, to change the synchronous offset to 6 for ID 3 on host adapter 0, the line in the CONFIG.SYS file that loads SYM8XX.ADD should look like this: BASEDEV=SYM8XX.ADD /SYNCH_OFFSET=6<0:3> or BASEDEV=SYM8XX.ADD /SO=6<0:3> 4.3.7 Using the /TIMEOUT (or /T) Option --------------------------------------- The SDMS device drivers use a timeout mechanism to detect certain errors. When the driver issues a command to a SCSI device, a timer is started. If the timer expires before the command completes, the driver assumes that something is wrong with the device, and takes steps to recover. The default value for this is 10 seconds. If you set the value to be less than the system has allocated for a particular device, your value is ignored. To turn off the timeout mechanism for a particular device, set the value to 0 (zero). Usage: /TIMEOUT=n[,n]* n The timeout value, in seconds, for the device. The value can be 0-65535. For example, if you have a particularly slow device at ID 3 on host adapter 0 and you wish to extend the timeout on this device to 60 seconds, then the line in the CONFIG.SYS file that loads SYM8XX.ADD should look like this: BASEDEV=SYM8XX.ADD /TIMEOUT=60<0:3> or BASEDEV=SYM8XX.ADD /T=60<0:3> 4.3.8 Using the /DISCONNECT (or /DC) Option ------------------------------------------- SCSI devices have the ability to disconnect from the bus during an I/O transfer. This option allows (or does not allow) a device to disconnect during an I/O transfer. If a particular adapter has parity checking disabled, then you must use this option to disable disconnects for all devices on that adapter that do not generate parity. Refer to the /PARITY option for more information. Usage: /DISCONNECT=n[,n]* n Disconnect indicator. Specify one of the following: ON Allow disconnects. This is the default value for all devices. OFF Do not allow disconnects. For example, to disable disconnects on the device at ID 2 on host adapter 0, the line in the CONFIG.SYS file that loads SYM8XX.ADD should look like this: BASEDEV=SYM8XX.ADD /DISCONNECT=OFF<0:2> or BASEDEV=SYM8XX.ADD /DC=OFF<0:2> 4.3.9 Using the /PARITY (or /P) Option -------------------------------------- The LSI Logic chips are capable of enabling or disabling the SCSI bus data integrity checking feature known as parity. Some non-compliant SCSI devices sold as SCSI devices do not generate parity. You can use this option to disable parity checking. The LSI Logic chips always generate parity (for outputs), but may optionally check the parity (for inputs). Note: When disabling parity checking, you must disable disconnects for any device that does not generate parity, as the LSI Logic chips cannot disable parity checking for that device during the reselection phase. If a device does not generate parity and it disconnects, the I/O never completes as the reselection never completes. Refer to using the /DISCONNECT option for more information about disabling disconnects for a device. Usage: /PARITY=n[,n]* n Parity indicator. Specify one of the following: ON Enable parity checking. This is the default for all devices. OFF Disable parity checking. For example, to turn off parity checking on host adapter 0, the line in the CONFIG.SYS file that loads SYM8XX.ADD should look like this: BASEDEV=SYM8XX.ADD /PARITY=OFF<0> or BASEDEV=SYM8XX.ADD /P=OFF<0> 4.3.10 Using the /QTAG (or /QT) Option -------------------------------------- Queue tagging allows more than one outstanding command per SCSI device. Some non-compliant SCSI devices sold as SCSI devices do not allow queue tags, in which case queue tagging needs to be disabled. The value given in the command line will be the depth of the queue for queue tags for the device(s) indicated. To disable queue tag support, a value of 0 or 1 should be given. Usage: /QTAG=n[,n]* n The number of queue tags allowed for a device. The value can be 0-256. The following examples illustrate how to use this option: * To turn off queue tagging for ID 3 on host adapter 0, the line in the CONFIG.SYS file that loads SYM8XX.ADD should look like this: BASEDEV=SYM8XX.ADD /QTAG=0<0:3> * To set the queue depth to 5 for all devices on host adapter 2, the line in the CONFIG.SYS file that loads SYM8XX.ADD should look like this: BASEDEV=SYM8XX.ADD /QT=5<2> 4.3.11 Using the /WIDTH (or /W) Option -------------------------------------- Devices attached to a SCSI bus are narrow or wide devices. Narrow devices transfer data one byte (or 8 bits) at a time. Wide devices transfer two bytes (or 16 bits) at a time. The value given in the command line option determines the size of data transfers. Usage: /WIDTH=n,[,n]* n Data transfer rate. Specify one of the following: 8 Transfer data at 8 bits (1 byte) at a time. 16 Transfer data 16 bits (2 bytes) at a time. The following examples illustrate how to use this option: * To have the device at ID 3 on host adapter 0 treated as a narrow device, the line in the CONFIG.SYS file that loads SYM8XX.ADD should look like this: BASEDEV=SYM8XX.ADD /WIDTH=8<0:3> * To have all devices on host adapter 2 treated as 8-bit devices, the line in the CONFIG.SYS file that loads SYM8XX.ADD should look like this: BASEDEV=SYM8XX.ADD /W=8<2> ------------------------------------------------------------------------ 5.0 I2O Storage and Transport Device Drivers Version 1.0 -------------------------------------------------------- The I2O Storage and Transport Device Drivers are a set of OS/2 Storage Operating System Modules (OSM) that enables the OS/2 DASD Device Manager (OS2DASD.DMD) to communicate with storage class devices being driven by their Hardware Device Modules (HDM) executing in the IRTOS environment on the I960 processor located on the PCI bus. Additional technical information can be obtained from the Intelligent I/O Architectural Specification Version 1.5. ------------------------------------------------------------------------ 6.0 PCI Support in the OS/2 Parallel Port Device Driver ------------------------------------------------------- The OS/2 Parallel Port Device Driver (PP DD) is a base device driver that supports the parallel port interface for OS/2. There are two distinct versions of the parallel port device driver: * PRINT01.SYS, which supports parallel ports on (Extended) Industry Standard Architecture (ISA/EISA) and Peripheral Component Interconnect (PCI) PCs * PRINT02.SYS, which supports parallel ports on Micro Channel(R) Architecture (MCA) PCs. Only one of these parallel port device drivers is resident for each PC running in OS/2. ------------------------------------------------------------------------ 6.1 Implementation ------------------ The PRINT01.SYS device driver is modified to support PCI parallel ports. The parallel port device driver supports up to three PCI parallel ports in the Standard Parallel Port (SPP) mode. By default, the OS/2 parallel port device driver uses the polling transmission method. If the transmission protocol is changed to the interrupt method by specifying the /IRQ parameter on the BASEDEV statement, the parallel port device driver supports PCI parallel ports in an interrupt-driven manner. In that case, the parallel port device driver attempts to set the interrupt service routine (ISR) for PCI IRQ to be not-shared at task time. If this attempt fails, the parallel port device driver sets the ISR for PCI IRQ to be shared. In addition, if the /SHR parameter is specified, the parallel port device driver sets ISRs for PCI IRQs to be shared at initialization time. Interrupt sharing at the parallel port device driver interrupt time is handled using the interrupt pending (occurred) bit in the PCI parallel port status register. The PP DD with PCI support accepts four BASEDEV= command parameters: three legacy parameters (/IRQ, /MPL, and /TOU:ddd) and new /SHR parameter. The parameters can be specified in any combination of uppercase and lowercase characters. Parameter Function /IRQ Directs the driver to use IRQs for printing rather than polling. /SHR This parameter, in conjunction with /IRQ parameter, directs the PP DD to service PCI IRQs as shared. Note: If your printer (for example, old dot matrix printer) generates IRQs without setting the interrupt pending (occurred) bit in PCI PP status register correctly, you cannot use PCI IRQ sharing and must not use the /SHR parameter. /MPL Directs the driver to use modified polling for printing. This helps lower CPU utilization and enable better performance for other tasks while the printer is being accessed. /TOU:ddd Specifies the maximum wait time in seconds before canceling the print request. This is a 3-decimal digit value (by default - 120 seconds). ------------------------------------------------------------------------ 7.0 OS/2 GRADD Device Drivers ----------------------------- Graphics Adapter Device Drivers (GRADD) is an IBM OS/2 architecture that makes it easier to support new graphics hardware as it becomes available. Enhanced performance of Presentation Manager(R) (PM) applications can be realized when using accelerated GRADD drivers. Several new and updated GRADD drivers are included with this package. ------------------------------------------------------------------------ 7.1 Supported Features ---------------------- The GRADD device drivers provide seamless support for accelerated and unaccelerated display graphics and advanced color depth and resolutions. They conform to the OS/2 32-bit flat memory model and are designed to function as 32-bit Presentation Manager graphics display drivers under the OS/2 32-bit graphics engine. ------------------------------------------------------------------------ 7.2 Drivers Included -------------------- The following accelerated GRADD drivers are included: * ATI Mach64/Rage GRADD (M64GRADD) * Chips & Technology 6555x GRADD (CHPGRADD) * Matrox Millenium/Mystique/G100/G200 GRADD (MGAGRADD) * NeoMagic 2090/2093/2097/2160/2200/2360 GRADD (NMGRADD) * S3 86x/96x/Trio/Trio3D/Savage3D/Savage4 GRADD (S3GRADD) * S3 Virge GRADD (S3DGRADD) * Trident 3DImage975/Cyber9397 GRADD (TRIGRADD) Also included are generic VGA and SVGA support. * Video Graphics Array GRADD (VGAGRADD) * Generic VESA Unaccelerated GRADD (GENGRADD) * Generic VESA Unaccelerated & VGA (Default) GRADDs (G_VGRADD) If an accelerated GRADD driver is not included for your adapter, GENGRADD may provide UNACCELERATED support for display graphics at enhanced resolutions and colors depths. GENGRADD works with most adapters that include a VESA-compliant BIOS; and the performance, which varies depending on system configuration, is not as good as an accelerated driver. ------------------------------------------------------------------------ 7.3 Supported Resolutions ------------------------- Supported resolutions and color depths are adapter dependent and vary depending on the amount of graphics memory and the adapter implementation. ------------------------------------------------------------------------ 7.4 Functional Restrictions --------------------------- Current known restrictions include the following: * IBM has tested many computers and adapters incorporating the graphics devices for the accelerated drivers listed. Testing was only done on computers with PCI bus graphics, although a PCI bus is not a specific requirement. * Sniff testing on ISA bus graphics adapters has worked. However when trying to restore your previous "PM" driver, there was a sometimes a problem detecting the adapter. Powering off the computer to initialize the adapter after restoring VGA should solve the problem. ATI Mach 64 ISA Bus adapters are currently not supported. * All the GRADD drivers, except for VGAGRADD, require VESA-compliant video BIOS (Version 1.2 or greater) or an appropriate SVGADATA.PMI file. For older non-VESA adapters with SVGA PM driver support from IBM, GENGRADD may often be used as an alternative SVGA driver set by following the GRADD Graphics BBS drivers SETUP installation command with the command "SVGA ON INIT" from an OS/2 or DOS Full Screen prompt to create an SVGADATA.PMI file, before rebooting to use the GRADD drivers. * M64GRADD and S3GRADD: Problems have been seen with certain adapters with hardware cursor support. The symptoms vary from the pointer appearing as a solid black rectangle to corruption occurring on the screen where the cursor passes. A workaround has been provided which forces the use of a software cursor. Adding the following line to CONFIG.SYS and rebooting should solve the problem: SET HW_CURSOR=OFF You can find future fixes and updates for the GRADD and other graphics device drivers via the internet at: http://service5.boulder.ibm.com/pspfixpk.nsf At the above Web address, choose "All Fix packages - By Product" and then search for "GRADD". ------------------------------------------------------------------------ 7.5 Installing GRADD Drivers ---------------------------- This sections discusses how to install GRADD drivers. 7.5.1 Installing in a CID Environment ------------------------------------- Notes: 1. Create a directory on the server (e.g. X:\BBS\GRADD) and extract the installation files from the self extracting GRADDBB*.EXE file to the X:\BBS\GRADD installation directory as described in the section File Extraction. 2. You must have OS/2 successfully installed on the client using the CID (Configuration Installation Distribution) method. 3. To configure display selection, resolution, and refresh rate, refer to the file "README.CFG" in this package. To install a device driver using CID, use the following information to modify your LCU command file. The following example installs the ATI Mach64/Rage GRADD (M64GRADD). Note: The following information is meant as a guide. Your LCU command file might be different. /*****************************************************/ /* LCU PRODUCT DATA SECTION */ /*****************************************************/ . . . x.graddvideo = 15 x.15.name='ATI Gradd Video' x.15.statevar = 'CAS_' || x.15.name x.15.instprog = 'x:\bbs\gradd\SETUP.CMD', ' ATI', ' x:\bbs\gradd ' || bootdrive, ' /u' x.15.rspdir = '' x.15.default = '' /*****************************************************/ /* NUMBER OF PROGRAMS SET UP IN THE */ /* PRODUCT DATA SECTION */ /*****************************************************/ NUM_INSTALL_PROGS = 15 /*****************************************************/ /* INSTALLATION SECTION */ /*****************************************************/ . . . when OVERALL_STATE = 2 then do if RunInstall(x.graddvideo) == BAD_RC then exit Call CheckBoot end . . . /******************************************************/ /* ROUTINE SECTION */ /* The following information should already exist in */ /* the LCU command file. */ /******************************************************/ . . . RebootAndGotoState: parse arg new_state, other rc2 = SetState(new_state, 'RebootAndGotoState', 1) /* Set the state */ /* to go to in */ /* OVERALL_STATE */ Call SaveStates /* Save the environment vars */ Call Reboot /* Reboot the computer */ return . . . /*****************************************************/ /* END OF LCU INFORMATION TO BE ADDED */ /*****************************************************/ 7.5.2 File Extraction --------------------- To set up the GRADD Graphics BBS driver installation directory, do the following: 1. Open an OS/2 full-screen or OS/2 window session. 2. Before running the GRADDBB*.EXE self extracting zip file (the exact name depends on the release build number), change the current directory to the "installation directory" in which you wish to store the GRADD Graphics BBS driver installation files. A suggested name is C:\BBS\GRADD. At the OS/2 command prompt, type the following commands: C: MD C:\BBS MD C:\BBS\GRADD CD C:\BBS\GRADD 3. Use the -DIR and -OVER options on the GRADDBB*.EXE self extracting zip file to create the installation directory tree. You may wish to copy the GRADDBB*.EXE self extracting zip file to the installation directory first. Then, at the OS/2 command prompt, type the following command: GRADDBB* -DIR -OVER 4. Use SET LANG= to set the correct language. The language may already be correctly set in your CONFIG.SYS. If not, then at the OS/2 command prompt, type one of these SET LANG= commands to choose your language: SET LANG=ar_AA for Arabic (English with Arabic graphics formatting) SET LANG=pt_BR for Brazil SET LANG=zh_CN for Simplified Chinese SET LANG=de_DE for Germany SET LANG=da_DK for Denmark SET LANG=es_ES for Spain SET LANG=el_GR for Greece (English with Greek graphics formatting) SET LANG=fi_FI for Finland SET LANG=fr_FR for France SET LANG=iw_IL for Israel (English with Hebrew graphics formatting) SET LANG=it_IT for Italy SET LANG=ja_JP for Japan SET LANG=ko_KR for Korea SET LANG=nl_NL for Netherlands SET LANG=no_NO for Norway SET LANG=sv_SE for Sweden SET LANG=zh_TW for Taiwan SET LANG=en_US for English (default) Each language has its own copy of this README.TXT file, which may be translated from English, as well as other language dependent files. 5. The SETUP command in the installation directory may then be used to install the proper language-dependent files and configuration information from the install directory onto your boot drive. Running SETUP without any options gives brief syntactic help about the SETUP command in your chosen or default language. To see this help, at the OS/2 command prompt, type the following command: SETUP ------------------------------------------------------------------------ 8.0 Plug'n'Play for PCMCIA -------------------------- This section discusses Plug'n'Play for PCMCIA software for IBM ThinkPads using OS/2 Warp 4.0. ------------------------------------------------------------------------ 8.1 Systems Supported --------------------- This package has been tested on IBM ThinkPads with the following PCMCIA controllers: Texas Instruments TI1130 Texas Instruments TI1131 Texas Instruments TI1225 Texas Instruments TI1250A Texas Instruments TI1251 Texas Instruments TI1251B Texas Instruments TI1420 Texas Instruments TI1450 Cirrus Logic CL-PD6729 ------------------------------------------------------------------------ 8.2 Limitations --------------- When utilizing cardbus cards, this code only supports the two PCMCIA slots in the base system unit. Non-cardbus (16-bit cards) function in all available slots (base system unit and docking station). ------------------------------------------------------------------------ 8.3 Parameter Definitions ------------------------- This section describes the configuration parameters you can specify for Socket Services and Card Services. 8.3.1 Socket Services (IBM2SS14.SYS) ------------------------------------ Parameter Function /C0=z/C1=z These parameters define the IRQ level to be used by the /C1=z Socket Services driver. The new Card Services and Socket Services drivers for OS/2 do not use a hardware interrupt to notify the Personal Computer Memory Card International Association (PCMCIA) status change, so you do not need these parameters. /IG0=y This parameter defines a slot number, which Socket Services ignores, where yrepresents the socket number as follows: o 1- upper socket o 2- lower socket If you use the "Point enabler" supplied with a PCMCIA card, you should take into consideration the coexistence with Socket Services. For example, "/IG0=1" defines that slot 1 is reserved for a "Point enabler" and Socket Services ignores the slot. /RI0=x This parameter defines a slot number, where Socket Services disables the RI_OUT signal, where x represents the adapter number as follows: o 0 - in notebook computer o 1 - docking station If you are using a modem card with a ThinkPad computer, and you cannot enable the "suspend" or "hibernation" function while the modem card is inserted, try this parameter. For example, "/RI0=1" specifies slot 1. /D This parameter enables "Warm docking" as it relates to PCMCIA hardware. By adding this parameter, two additional PCMCIA slots are reserved for the docking station. /APOFF This parameter turns off the Auto-Power Mode. If the Auto-Power Mode is ON, a PCMCIA card is automatically turned ON by the hardware when it is inserted. The default for Auto-Power Mode is ON. /IO0=s This parameter defines the slot number, for which Socket Services will change the way the -IOCS16 signal is generated. By default, the -IOCS16 signal is generated based on the -IOIS16 signal from the PCMCIA card. If this parameter is specified, the -IOCS16 signal is generated based on the I/O data size which is specified by the client program. This option is needed for some cards which do not generate the -IOIS16 signal. You must verify this information with PCMCIA card vendors. For example, "/IO0=1" specifies that the -IOCS16 signal for slot 1 is to be generated based on the I/O data size specified by the client program. 8.3.2 Card Services (PCMCIA.SYS) -------------------------------- Parameter Function /R:200 Specify that card services conform to the PCMCIA 2.0 standard. This is the default value. /R:500 Specify that card services conform to the PCMCIA 5.0 standard instead of the PCMCIA 2.0 standard which is the default value. /P In previous releases, this parameter disabled the hardware interrupt which was used by OS/2 Socket Services drivers to notify clients of a change in status. Neither the new Card Services nor Socket Services drivers for OS/2 use a hardware interrupt to signal PCMCIA status changes. So this parameter is no longer needed. ------------------------------------------------------------------------ 8.4 Using Point Enablers with the Plug'n'Play for PCMCIA Package ---------------------------------------------------------------- Point Enabler Adapter card drivers are device drivers that support specific adapter cards without requiring the use of the Card and Socket services provided in the Plug'n'Play for PCMCIA package. Problems using these Point Enabler device driver occur when used in conjunction with the Card and Socket Services. The problem that occurs is that the Point Enabler adapter card does not function. The Plug'n'Play for PCMCIA indicates that the card type is incorrect and the status of the card is "IN" instead of "READY". In order to use an adapter card with the Point Enabler device driver, a configuration parameter must be added to the IBM2SS14.SYS device driver entry in CONFIG.SYS. The parameter is /IG0=y, where y defines the slot number that contains the adapter card using the Point Enabler device driver. After the system has been rebooted, the slot specified in the configuration parameter is ignored by Card and Socket Services, allowing that slot to be used by Point Enabler device drivers. It also means the following: * The Plug'n'Play for PCMCIA program does not detect the insertion or removal of adapter cards in that slot. * Adapter cards with device drivers that utilize Card and Socket Services can no longer use that slot. The following is a list of adapter cards that use Point Enabler device drivers: * IBM 10/100 EtherJet(TM) Cardbus Adapter * IBM 10/100 EtherJet Cardbus Adapter with 56K modem * Intel PRO/100 Cardbus II * Xircom CreditCard Ethernet Adapter II * Xircom CreditCard Ethernet Adapter 10/100 ------------------------------------------------------------------------ 8.5 Hints and Tips ------------------ This sections provides various hints and tips to assist you when using this support. You can see current system resource information with RMVIEW.EXE program. The RMVIEW.EXE is a standard OS/2 utility program which is included in OS/2. To run this program, type "RMVIEW" at the OS/2 command prompt and press Enter. You can see short help with "/?" option. 8.5.1 Problems with Adapter Cards --------------------------------- If problems occur with an adapter card failing to work properly, there are two suggestions that may correct the problem: * The adapter card may be using a Point Enabler device driver, in that case refer to Using Point Enablers with the Plug'n'Play for PCMCIA Package and set the /IG0=y parameter in the CONFIG.SYS entry for IBM2SS14.SYS. * The adapter may require the use of the 2.0 version of Card Services. In that case, set the /R:200 parameter in the CONFIG.SYS entry for PCMCIA.SYS. 3270 Adapter Cards ++++++++++++++++++ On IBM 600 series ThinkPads, IBM 3270 adapter cards must be placed in the lower adapter card slot (slot 2). The 3270 adapter card may also be used in either adapter slot on attached docking stations. Storage PCMCIA Cards ++++++++++++++++++++ * Before using a brand-new FLASH PCMCIA card, initialize the card with one of the following: o FFORMAT.EXE o FCHECK.EXE o FFORMAT2.EXE o FCHECK2.EXE * If you see the following message: << Attention >> This card isn't supported formally It is possible that it doesn't work correctly while the FFORMAT.EXE, FCHECK.EXE, FFORMAT2.EXE or FCHECK2.EXE program is running, the card is formatted as if it has 256KB-erase-zone size and the write/erase logic of Intel 28F020 or 28F010. * If you see the following message: The size of this card is too small for the card to be formatted while the FFORMAT.EXE, FCHECK.EXE, FFORMAT2.EXE or FCHECK2.EXE program is running, the card cannot be formatted because its size is too small to accept the transfer unit. (At least one transfer unit is required for FTL.) * You cannot use the SRAM region of the IBM FLASH & SRAM combo card on OS/2 even if you install PCM2SRAM.SYS (SRAM device driver). The card appears to be a FLASH card if you install FLSH2MTD.SYS (FLASH memory technology driver), PCM2FLSH.SYS (FLASH device driver), or other drivers. * OS/2 Warp includes a flash memory card device driver that can enable only IBM flash memory cards. The flash memory card device driver in this IBM Plug'n'Play for PCMCIA Installation Program cannot enable cards formatted with the one in OS/2 Warp. * In case of formatting two or more Storage PCMCIA cards, run and exit the FORMAT program for every card. You must not format two or more Storage PCMCIA cards from a single invocation of FORMAT. * You cannot use the DISKCOPY program for the Storage PCMCIA card drive. * If your PC has two or more PCMCIA slots, do not insert or remove a storage PCMCIA card in the slot while you are executing DOS commands, such as FORMAT or COPY to a storage PCMCIA card in another slot. * If your system has three or more PCMCIA slots, for example a notebook computer with docking station which has PCMCIA slots, the total number of PCMCIA slots which will be used for Storage PCMCIA cards must be specified. For example, if you have four PCMCIA slots: BASEDEV=PCM2ATA.ADD /S:4 /!DM /NOBEEP Others ++++++ * For the Auto Configurator driver and Utility, refer to the AUTODRV.DOC file for more details. * For the PCMCIA cards, refer to the PCMCIA.CRD file for more details on the support level. * For the PCMCIA, sample installation/configuration files (CONFIG.SYS, AUTOEXEC.BAT, and so on) are available on your "Plug'n'Play for PCMCIA Installation Program for OS/2" diskette. Refer to the \SAMPLES directory on the diskette. * If you use a docking station with your notebook computer, the adapter cards or the devices in the docking station may use resources such as I/O port, memory window, IRQ. Exclude these resources from the usable area of the Card Services. To exclude resources from the usable area, RESERVE.SYS can be used. See "4.0 For OS/2" (RESERVE.SYS) in this document. * Add the /INT option if an error or a timeout occurs while the ATA(HDD) card is used. For example: DEVICE=...PAWATA.SYS /INT or DEVICE=...PAWATAS.SYS /INT or DEVICE=...PAWATASF.SYS /INT In this case, 4KB memory window is required for every ATA(HDD) card. * If you have an Adaptec SCSI PCCard, find the following statement in CONFIG.SYS: REM BASEDEV=AHA152X.ADD Change that statement to look like the following: BASEDEV=AHA152X.ADD * If you have a Future Domain SCSI PCCard, find the following statement in CONFIG.SYS: REM BASEDEV=FD16-700.ADD Change that statement to look like the following: BASEDEV=FD16-700.ADD ------------------------------------------------------------------------ 9.0 IBM Plug'n'Play for PCMCIA CID Installation ----------------------------------------------- This section describes the optional parameters for use with the IBM Plug'n'Play for PCMCIA for CID installations. PCMINST2 /S: /R: /R: /L1: /L2: /T: If the "/S:<..>" notation is not specified, the installation programs assume that CID is not required, and work as normal mode which need user intervention. /S: Specify the drive and path to the Plug'n'Play for PCMCIA files existing on the SDM code server. Examples of valid /S: parameter usage: /S:d: /S:d:\ /S:d:\ppp /S:d:\ppp\ Where d: is the drive name (A-Z,a-z). ppp: is the path name. /T: Specify the target drive and path for the product installation at the client workstation. Examples of valid /T: parameter usage: /T:d: /T:d:\ /T:d:\ppp /T:d:\ppp\ Where d: is the drive name (A-Z,a-z). ppp: is the path name. /R: Specify the drive, path and name to the client response file existing on the SDM code server. Examples of valid /R: parameter usage: /R: (assumes PCMINST2.RSP in the source path) /R:fff (assumes fff in the source path) /R:d:\ppp\fff Where d: is the drive name (A-Z,a-z). ppp is the path name. fff is the response file name. /G: Specify the drive, path and name to the group response file existing on the SDM code server. Examples of valid /G: parameter usage: /G: (assumes PCMINST2.RSP in the source path) /G:fff (assumes fff in the source path) /G:d:\ppp\fff Where d: is the drive name (A-Z,a-z). ppp is the path name. fff is the response file name. /L1: Specify the drive, path and name to the error log file existing on the SDM code server. Examples of valid /L1: parameter usage: /L1: (assumes PCMINST2.ERR in the source path) /L1:fff (assumes fff in the source path) /L1:d:\ppp\fff Where d: is the drive name (A-Z,a-z). ppp is the path name. fff is the response file name. /L2: Specify the drive, path and name to the error history file existing on the SDM code server. Examples of valid /L2: parameter usage: /L2: (assumes PCMINST2.HST in the source path) /L2:fff (assumes fff in the source path) /L2:d:\ppp\fff Where d: is the drive name (A-Z,a-z). ppp is the path name. fff is the response file name. ------------------------------------------------------------------------ 9.1 Response File Format ------------------------ The format of the response file is as follows: #--- Comment ------------- Target=C:\TEST ReBoot=N UpdateConfig=Y ForceReplace=Y Use2ndSS=N *--- Comment ------------- Target= Used to specify the target drive and path for the product installation at the client workstation. Examples of valid Target= parameter usage: Target=d: TARGET=d:\ TaRgEt=d:\ppp Target=d:\ppp\ Where d: is the drive name (A-Z,a-z). ppp is the path name. ReBoot= This keyword is valid only for OS/2. If the Plug'n'Play for PCMCIA for OS/2 is installed to the system which has already been with a installed previous Plug'n'Play for PCMCIA, the current installation program removes the previous Plug'n'Play for PCMCIA and then asks the user to restart the system. Under the latest Warp, the system restart is not necessary, but is required in the previous version. This keyword specifies whether to restart the client workstation, if the workstation has an old Plug'n'Play for PCMCIA. Specify one of the following: NO Do not restart the system. This is the default. YES Restart the system. Examples of valid ReBoot= parameter usage: ReBoot=N ReBoot=Y REBOOT=NO REBOOT=Yes UpdateConfig= Specifies whether to update the CONFIG.SYS and SYSTEM.INI files. Specify one of the following: NO Do not update CONFIG.SYS and SYSTEM.INI files. If specified, updated sample files, named CONFIG.PCM and SYSTEM.PCM, are created at the target directory. YES Update CONFIG.SYS and SYSTEM.INI files. This is the default. Examples of valid UpdateConfig= parameter usage: UpdateConfig=N UpdateConfig=Yes UPDATECONFIG=NO ForceReplace= Specifies whether to replace the Plug'n'Play for PCMCIA files if the client workstation has more recently-dated Plug'n'Play for PCMCIA files. Select one of the following: NO Do not replace the Plug'n'Play for PCMCIA files. If specified, installation is terminated. YES Replace the Plug'n'Play for PCMCIA files. This is the default. Examples of valid ForceReplace= parameter usage: ForceReplace=N ForceReplace=Yes FORCEREPLACE=NO Use2ndSS= This keyword is valid only for Win3.1 and DOS on the TP760E system. The TP760E needs two SS drivers, one for the CardBus controller (IBMDSS14), and the other is for the legacy PCIC controller (IBMDSS04). This keyword specifies whether the legacy SS driver is enabled. Specify one of the following: NO The SS driver is not enabled. This is the default. When specified, the DEVICEHIGH= statement for this driver is commented out in the CONFIG.SYS file. YES The SS driver is enabled. Examples of valid Use2ndSS= parameter usage: Use2ndSS=N Use2ndSS=Yes USE2NDSS=NO ------------------------------------------------------------------------ 10.0 Adaptec Ultra160 Family Manager Set ---------------------------------------- This section describes the Adaptec Ultra160 Family Manager Set support. ------------------------------------------------------------------------ 10.1 Supported Hardware ----------------------- The following Adaptec SCSI Host Adapters are supported by the Adaptec Ultra160 Family Manager Set: AIC-7892 Single Channel PCI-to-Ultra160 SCSI ASIC AIC-7899 Dual Channel PCI-to-Ultra160 SCSI ASIC AHA-3960D/39160 Dual Channel 64-bit PCI-to-Ultra160 SCSI Host Adapter 29160 Single Channel 64-bit PCI-to-Ultra160 SCSI Host Adapter 29160N Single Channel 32-bit PCI-to-Ultra160 SCSI Host Adapter (OEM) 29160LP Single Channel 64-bit Low Profile PCI-to-Ultra160 SCSI Host Adapter ------------------------------------------------------------------------ 10.2 Known Issues ----------------- * Intel Errata #8511 lists known data integrity issues with the processor cache on the Saturn-1 chipset (82424TX). For this reason, Adaptec recommends that processor cache be disabled via the CMOS setup to avoid data corruption. For more information, see Intel Errata #8511. You may get this from Intel's FaxBack system at 800.628.2283 or 916.356.3105. * There are installation problems when installing on the maximum hard disk drive partition size supported by OS/2 v3.0. On OS/2 v3.0 it is a known problem. Refer to IBM for further information. IBM's APARs PJ15988 and PJ6151 deal with this issue. * There are known installation problems installing OS/2 Warp v4.0 on a Micron (LSI chipset) 64-bit PCI system. * There are known installation problems installing OS/2 Warp with 8MB of RAM unless all the third-party BASEDEV statements are removed from CONFIG.SYS. * There are known installation problems installing OS/2 using two SCSI host adapters on a "Marl" motherboard. * Whenever you have a LVD HDD on one Ultra160 host adapter and a HDD, CD-ROM, and removable SyJet on another UltraSCSI host adapter, SyJet conflicts with the CD-ROM and the system is unable to access the CD-ROM. ------------------------------------------------------------------------ 10.3 Additional Notes --------------------- * This version of the Ultra160 Family Manager Set driver supports the AIC-7892/99 Family of Host Adapters. Adapter numbers are first assigned to boards with their BIOS enabled. The numbers are assigned from lowest BIOS address to highest address. Any remaining boards are assigned numbers by scanning slots. Each slot is a combination of a bus number and a device number pair starting from lowest to highest numbers, and the adapters are assigned a number in the order they are found. For example, Bus 0, device 0 assigned as adapter 0; Bus 1, device 1 assigned as adapter 1, and so on. * There are no switches for controlling OS2ASPI.DMD directly. IBM did not define them in their specification and Adaptec cannot be sure that other host adapters will have the same switches. * OS2SCSI.DMD will only allocate devices when a device driver requests it, but this will prevent OS2ASPI from accessing it. There is nothing in the ASPI specification regarding device allocation so OS2ASPI must rely on other managers to fairly share targets. This should only be a problem if you have two drivers that use different managers and you want them both to access the same target at the same time. * Do not disable DASD manager access to target 0 if you are booting from your SCSI host adapter. This prevents the system from booting. * Fault Tolerance is supported in the driver. However, ABORT and SCSI BUS RESET only works for targets that are properly behaved. * IBM does not support installing the operating system onto magneto optical devices. Additionally, OPTICAL.SYS (OS/2 3.0) or OPTICAL.DMD (OS/2 4.0) allows magneto optical devices to be supported as though they were large floppy devices. LOCKDRV.FLT allows removable media such as MO's to be supported as though they were fixed hard drives. * It is not possible to install OS/2 3.0 on drives with capacity greater than 8GB, nor in a partition greater than 4GB. The following is the suggestion from IBM on this problem: Problems with large partitions and installation or booting: There is a BIOS restriction that installable (startable) or bootable partitions must be contained within the first 1024 physical cylinders of the disk. The LVM command does not enforce this limitation. If you have installation or boot failures, this could be the reason. Use the LVM command to reduce the size of your startable or bootable partition by sufficient MBs. One way to calculate the correct size partitions is to do the following: 1. Edit your CONFIG.SYS and add the following parameter to the BASEDEV=IBM1S506.ADD line as below: BASEDEV=IBM1S506.ADD /V 2. Save this change. 3. Restart your system. 4. At initialization, record the far left-hand column of numbers of the Geometry information under the ACT heading. For example: ACT Cyl 1027 Head 63 Sec 128 (head x sec) /2 = bootable partition must be contained within this boundary in MBytes (round down) This is the maximum size of a bootable partition in MBytes. Any bootable partition must also be contained from the beginning of the drive to this number of MBytes. A bootable partition may be smaller than the maximum size but still must be contained within this boundary. In this example the bootable partition must be contained in the first 4032MB of the disk and cannot exceed a single partition size of 4032MB within this area. No bootable partition may extend beyond the first 4032MB. Use this information when configuring your bootable partition with the LVM command. * OS/2 will allocate the SCSI devices as the order in CONFIG.SYS if two drivers (such as the AIC7870.ADD and AICU160.ADD) are loaded. * OS/2 will assign drive letters for SCSI devices first then IDE devices. ------------------------------------------------------------------------ 10.4 Command-line Options ------------------------- OS/2 adapter device drivers (.ADD files) are normally installed automatically and require no further information from the user. However, in certain situations the user may wish to modify the behavior of the driver to meet their specific needs. Note: Proceed cautiously with the following information. The standard format for command-line switches is: BASEDEV=AICU160.ADD [Universal Parameter][Adapter ID] [Unit Parameter]{[SCSI Target ID]} [Universal Parameter] An option that applies to all adapters controlled by the driver. [Adapter ID] /A:n, where n is the number (zero relative) of the adapter installed in the system. The adapter ID is determined when the driver is loaded based on the order that adapters are found in the system. (Refer to the Configuration Examples in the General Unit Parameters section below for information on how to use this option.) [Unit Parameter] Modifies the behavior of the selected host adapter. [SCSI Target ID] The targets to which the Unit Parameter are applied. This parameter may be a single ID (d) or list of IDs (d,d,d). 10.4.1 Universal Parameters --------------------------- /ET Allow embedded targets. This parameter indicates that the ADD should assume that all targets have more than one logical unit (LUN) defined. /!ET Do not allow embedded targets. This is the default. This parameter indicates that the ADD should assume that all targets have only one logical unit (LUN) defined. /V Load driver verbosely. This parameter displays the driver name as well as the version number and Adaptec copyright if the driver loads successfully. Information on all targets found in the system are also displayed. 10.4.2 General Unit Parameters ------------------------------ /I Ignore the specified adapter. This allows another driver to share the adapters that the ADD would normally use. /DM Enable DASD manager support. This is the default. This parameter allows OS2DASD.DMD to control the specified target or targets if they are identified as DASD (hard disk) devices. /!DM Disable DASD manager support. This parameter prevents OS2DASD.DMD from controlling the specified target or targets. /SM Enable SCSI manager support This is the default. This parameter allows OS2SCSI.DMD to control the specified target or targets if they are identified as NON-DASD SCSI devices. All SCSI hard drives are controlled by OS2DASD.DMD. /!SM Disable SCSI manager support. This parameter prevents OS2SCSI.DMD from controlling the specified target or targets. /TAG Specifies the maximum number of tagged commands for all target devices on the host adapter (1-16). A value of 1 disables tagged queuing. The maximum number allowed is 16. (The default is 8.) /UR Enables reporting of under runs. This is the default. /!UR Disables reporting of under runs. 10.4.3 Configuration Examples ----------------------------- This section presents several configuration examples using many of the parameters discussed. Example 1: Suppose that you had a removable hard drive as target 3 and you wanted to control the hard drive with an ASPI application and driver. Normally OS2DASD allocates this device, treats it as a large floppy and prevents you from sending any SCSI commands via ASPI. The following command line prevents OS2DASD.DMD from accessing the target and still allows OS2SCSI.DMD and OS2ASPI.DMD to share access to it. BASEDEV=AICU160.ADD /A:0 /!DM:3 Example 2: Suppose that you had a multi-disk CD-ROM as target 4 on host adapter 0 and two DASD devices as targets 1 and 5 on host adapter 1. The following command line prevents OS2SCSI.DMD from accessing the CD-ROM and prevents OS2DASD.DMD from controlling the DASD devices. The driver also searches for multiple LUNs on all host adapters. BASEDEV=AICU160.ADD /ET /A:0 /!SM:4 /A:1 /!DM:1,5 Special Unit Parameters /TAG: Sets the number (1-16) of tagged commands for all target devices on the host adapter. A value of one disables tagged queuing. Sixteen is the maximum number allowed and 8 is the default value. /TAG:1 Disables tagged queuing for all target devices on a given host adapter. The driver maintains a maximum of 2 non-tagged commands per target internally. The driver treats all target devices as non-tagged devices, and sends only one command at a time per target to the host adapter. In the following example, the statement sets the number of tagged commands for all target devices on the first host adapter to 8. BASEDEV=AICU160.ADD /A:0 /TAG:8 ------------------------------------------------------------------------ 11.0 Adaptec 7800 Family Manager Set ------------------------------------ This section describes the Adaptec 7800 Family Manager Set support. Adaptec 7800 Family Manager Set v3.02 features enhancements from the previous v3.01 version. These features include support for a wider variety of Ultra2SCSI PCI IC's and host adapters. ------------------------------------------------------------------------ 11.1 Supported Hardware ----------------------- The following Adaptec SCSI Host Adapters are supported by the 7800 FMS v3.02. The first list (Fast/Ultra Adapters) is supported by the AIC7870.ADD driver, while the second list (Ultra2 Adapters) is supported by the AIC78U2.ADD driver. Fast/Ultra Adapters Description ------------------- ----------- AHA-2910C PCI-to-Fast SCSI (non-bootable) AHA-2915C PCI-to-Fast SCSI (non-bootable) AHA-2920C PCI-to-Fast SCSI AHA-2930C PCI-to-Ultra Single-ended SCSI AHA-2940 PCI-to-Fast SCSI AHA-2940W PCI-to-Fast and Wide Single-ended SCSI AHA-2940AU PCI-to-Ultra Single-ended SCSI AHA-2940U PCI-to-Ultra Single-ended SCSI AHA-2940U Dual DualChannel PCI-to-Ultra Wide Internal Single-ended SCSI with 50-pin external connector AHA-2940UW PCI-to-Ultra Wide Single-ended SCSI AHA-2940UW Dual DualChannel PCI-to-Ultra Wide Single-ended SCSI with 68-pin external connector AHA-2944W PCI-to-Fast and Wide Differential SCSI AHA-2944UW PCI-to-Ultra Wide Differential SCSI AHA-3940 MultiChannel PCI-to-Fast SCSI AHA-3940W MultiChannel PCI-to-Fast and Wide SCSI AHA-3940U MultiChannel PCI-to-Ultra SCSI AHA-3940UW MultiChannel PCI-to-Ultra Wide SCSI AHA-3940UWD MultiChannel PCI-to-Ultra Wide SCSI with dual external connectors AHA-3944UWD MultiChannel PCI-to-Ultra Wide Differential SCSI with dual external connectors AHA-3940AU MultiChannel PCI-to-Ultra SCSI AHA-3940AUW MultiChannel PCI-to-Ultra Wide SCSI AHA-3940AUWD MultiChannel PCI-to-Ultra Wide SCSI with dual external connectors AHA-3944AUWD MultiChannel PCI-to-Ultra Wide Differential SCSI with dual external connectors AHA-4944W Quad Channel PCI-to-Fast and Wide Differential SCSI AHA-4944UW Quad Channel PCI-to-Ultra Wide Differential SCSI AIC-7850 Single-chip PCI-to-Fast SCSI AIC-7855 Single-chip PCI-to-Fast SCSI AIC-7856 Single-chip PCI-to-Fast SCSI AIC-7860 Single-chip PCI-to-Ultra SCSI AIC-7870 Single-chip PCI-to-Fast and Wide SCSI AIC-7880 Single-chip PCI-to-Ultra Wide SCSI AIC-7895 Single-chip PCI-to-MultiChannel Ultra Wide SCSI Ultra2 Adapters Description --------------- ----------- AHA-2940U2 OEM PCI-to-Ultra2 Wide LVD/Single-ended SCSI AHA-2940U2B PCI-to-Ultra2 Wide LVD SCSI AHA-2940U2W PCI-to-Ultra2 Wide LVD/Single-ended SCSI AHA-2950U2B 64-bit PCI-to-Ultra2 Wide LVD SCSI AHA-3950U2B 64-bit PCI-to-MultiChannel Ultra2 Wide LVD SCSI AIC-7890 Single-chip PCI-to-Ultra2 SCSI AIC-7891 Single-chip 64-bit PCI-to-Ultra2 SCSI AIC-7896 Single-chip PCI-to-MultiChannel Ultra2 SCSI AIC-7897 Single-chip 64-bit PCI-to-MultiChannel Ultra2 SCSI ------------------------------------------------------------------------ 11.2 Known Issues ----------------- * This version of the Adaptec 7800 Family Manager Set v3.02 driver added a new switch named /!PCIHW, which enables the driver to skip accessing the PCI hardware registers directly, and use PCI BIOS instead. This switch could be useful for users having problems loading the driver included with OS/2 Warp or Server. Modify the CONFIG.SYS file to include the following line: o For Ultra2SCSI host adapters: BASEDEV=AIC78U2.ADD /!PCIHW o For UltraSCSI or earlier host adapters: BASEDEV=AIC7870.ADD /!PCIHW * Intel Errata #8511 lists known data integrity issues with the processor cache on the Saturn-1 chipset (82424TX). For this reason, Adaptec recommends that processor cache be disabled via the CMOS setup to avoid data corruption. For more information, see Intel Errata #8511. You may get this from Intel's FaxBack system at 800.628.2283 or 916.356.3105. * There are installation problems when installing on the maximum hard disk drive partition size supported by OS/2 v3.0. On OS/2 v3.0 it is a known problem. Refer to IBM for further information. IBM's APARs PJ15988 and PJ 6151 deal with this issue. * There are known installation problems installing OS/2 Warp v4.0 on a Micron (LSI chipset) 64-bit PCI system. * There are known installation problems installing OS/2 Warp with 8MB of RAM unless all the third-party BASEDEV statements are removed from CONFIG.SYS. * There are known installation problems installing OS/2 using two SCSI host adapters on Marl mother board. * Whenever you have a LVD HDD on one Ultra2SCSI host adapter and a HDD, CD-ROM, and removable SyJet on another UltraSCSI host adapter, SyJet conflicts with the CD-ROM and the system is unable to access the CD-ROM. ------------------------------------------------------------------------ 11.3 Additional Notes --------------------- * This version of the Adaptec 7800 Family Manager Set v3.02 driver supports the AIC-7800 Family of Host Adapters. Adapter numbers are first assigned to boards with their BIOS enabled. The numbers are assigned from lowest BIOS address to highest address. Any remaining boards are assigned numbers by scanning slots. Each slot is a combination of a bus number and a device number pair starting from lowest to highest numbers, and the adapters are assigned a number in the order they are found. Example: Bus 0, device 0 assigned as adapter 0, Bus 1, device 1 assigned as adapter 1, etc. * On some PCI systems, users may sometimes have problems loading the driver when the host adapter board is seated in a particular slot. Moving the host adapter board to another slot may solve the problem. If the problem still persists, it may be occurring because the Adaptec 7800 Family Manager Set v3.02 driver is unable to access the PCI hardware registers directly. To overcome this, users should use the /!PCIHW switch. Modify the CONFIG.SYS file to include the following line: o For Ultra2SCSI host adapters: BASEDEV=AIC78U2.ADD /!PCIHW o For UltraSCSI or earlier host adapters: BASEDEV=AIC7870.ADD /!PCIHW * There are no switches for controlling OS2ASPI.DMD directly. IBM did not define them in their specification and we cannot be sure that other host adapters will have the same switches. * OS2SCSI.DMD will only allocate devices when a device driver requests it, but this will prevent OS2ASPI from accessing it. There is nothing in the ASPI specification regarding device allocation so OS2ASPI must rely on other managers to fairly share targets. This should only be a problem if you have two drivers that use different managers and you want them both to access the same target at the same time. * Do not disable DASD manager access to target 0 if you are booting from your SCSI host adapter. This will prevent the system from booting. * Fault Tolerance is supported in the driver. However, ABORT and SCSI BUS RESET will only work for targets that are properly behaved. * IBM does not support installing the operating system onto magneto optical devices. Additionally, OPTICAL.SYS (OS/2 V3.0) or OPTICAL.DMD (OS/2 V4.0) allows magneto optical devices to be supported as though they were large floppy devices. LOCKDRV.FLT allows removable media such as MO's to be supported as though they were fixed hard drives. * It is not possible to install OS/2 3.0 on drives with capacity greater than 8GB, nor in a partition greater than 4GB. The following is the suggestion from IBM on this problem: Problems with large partitions and installation or booting There is a BIOS restriction that installable (startable) or bootable partitions must be contained within the first 1024 physical cylinders of the disk. The LVM command does not enforce this limitation. If you have installation or boot failures, this could be the reason. Use the LVM command to reduce the size of your startable or bootable partition by sufficient MBytes. One way to calculate the correct size partitions to do the following: 1. Edit your CONFIG.SYS and add the following parameter to the BASEDEV=IBM1S506.ADD line as below: BASEDEV=IBM1S506.ADD /V 2. Save this change. 3. Reboot your system. 4. At initialization, record the far left hand column of number of the Geometry information under the ACT heading. Example: ACT Cyl 1027 Head 63 Sec 128 (head x sec) /2 = bootable partition must be contained within this boundary in MBytes (round down) This is the maximum size of a bootable partition in MBytes. Any bootable partition must also be contained from the beginning of the drive to this number of MBytes. A bootable partition may be smaller than the maximum size but still must be contained within this boundary. In this example the bootable partition must be contained in the first 4032MB of the disk and cannot exceed a single partition size of 4032MB within this area. No bootable partition may extend beyond the first 4032MB. Use this information when configuring your bootable partition with the LVM command. * OS/2 will allocate the SCSI devices as the order in CONFIG.SYS if two drivers (AIC7870.ADD and AIC78U2.ADD) are loaded. * OS/2 will assign drive letters for SCSI devices first then IDE devices. ------------------------------------------------------------------------ 11.4 Command-line Options ------------------------- OS/2 adapter device drivers (.ADD files) are normally installed automatically and require no further information from the user. However, in certain situations the user may wish to modify the behavior of the driver to meet their specific needs. Note: Proceed cautiously with the following information. The standard format for command-line switches is: * For Ultra2SCSI host adapter: BASEDEV=AIC78U2.ADD [Universal Parameter][Adapter ID] [Unit Parameter]{[SCSI Target ID]} * For UltraSCSI or earlier host adapters: BASEDEV=AIC7870.ADD [Universal Parameter][Adapter ID] [Unit Parameter]{[SCSI Target ID]} [Universal Parameter] An option that applies to all adapters controlled by the driver. [Adapter ID] /A:n, where n is the number (zero relative) of the adapter installed in the system. The adapter ID is determined when the driver is loaded based on the order that adapters are found in the system. (Refer to the Configuration Examples in the Universal Parameters section below for information on how to use this option.) [Unit Parameter] Modifies the behavior of the selected host adapter. [SCSI Target ID] The targets to which the Unit Parameter are applied. This parameter may be a single ID (d) or list of IDs (d,d,d). 11.4.1 Universal Parameters --------------------------- /ET Allow embedded targets. This parameter indicates that the ADD should assume that all targets have more than one logical unit (LUN) defined. /!ET Do not allow embedded targets. This is the default. This parameter indicates that the ADD should assume that all targets have only one logical unit (LUN) defined. /V Load driver verbosely. This parameter displays the driver name as well as the version number and Adaptec copyright if the driver loads successfully. Information on all targets found in the system are also displayed. /PCIHW Enables driver to access PCI configuration hardware registers. This switch is implemented because in some PCI systems, accessing PCI configuration space through PCI BIOS function calls causes problems. This switch is enabled by default. /!PCIHW Disables the PCIHW switch. This parameter causes the driver to access the PCI configuration space through PCI BIOS function calls. 11.4.2 General Unit Parameters ------------------------------ /I Ignore the specified adapter. This allows another driver to share the adapters that the ADD would normally use. /DM Enable DASD manager support. This is the default. This parameter allows OS2DASD.DMD to control the specified target or targets if they are identified as DASD (hard disk) devices. /!DM Disable DASD manager support. This parameter prevents OS2DASD.DMD from controlling the specified target or targets. /SM Enable SCSI manager support This is the default. This parameter allows OS2SCSI.DMD to control the specified target or targets if they are identified as NON-DASD SCSI devices. All SCSI hard drives are controlled by OS2DASD.DMD. /!SM Disable SCSI manager support. This parameter prevents OS2SCSI.DMD from controlling the specified target or targets. /TAG Specifies the maximum number of tagged commands for all target devices on the host adapter (1-16). A value of 1 disables tagged queuing. The maximum number allowed is 16. (The default is 8.) /UR Enables reporting of under runs. This is the default. /!UR Disables reporting of under runs. 11.4.3 Configuration Examples ----------------------------- This section presents several configuration examples using many of the parameters discussed. Example 1: Suppose that you had a removable hard drive as target 3 and you wanted to control the hard drive with an ASPI application and driver. Normally OS2DASD allocates this device, treats it as a large floppy and prevents you from sending any SCSI commands via ASPI. The following command line prevents OS2DASD.DMD from accessing the target and still allows OS2SCSI.DMD and OS2ASPI.DMD to share access to it. BASEDEV=AIC78U2.ADD /A:0 /!DM:3 Example 2: Suppose that you had a multi-disk CD-ROM as target 4 on host adapter 0 and two DASD devices as targets 1 and 5 on host adapter 1. The following command line prevents OS2SCSI.DMD from accessing the CD-ROM and prevents OS2DASD.DMD from controlling the DASD devices. The driver also searches for multiple LUNs on all host adapters. BASEDEV=AIC7870.ADD /ET /A:0 /!SM:4 /A:1 /!DM:1,5 Special Unit Parameters /TAG: Sets the number (1-16) of tagged commands for all target devices on the host adapter. A value of 1 disables tagged queuing. Sixteen is the maximum number allowed and 8 is the default value. /TAG:1 Disables tagged queuing for all target devices on a given host adapter. The driver maintains a maximum of two non-tagged commands per target internally. The driver treats all target devices as non-tagged devices, and sends only one command at a time per target to the host adapter. In the following example, the statement sets the number of tagged commands for all target devices on the first host adapter to 8. BASEDEV=AIC78U2.ADD /A:0 /TAG:8 ------------------------------------------------------------------------ 12.0 REXX functions ------------------- This chapter describes the following REXX functions: REXX Function Purpose SysQueryExtLIBPATH Return the current path to be searched before or after the system LIBPATH. SysQuerySwitchList Obtain information about the entries in the window list. SysSetExtLIBPATH Define the current path to be searched before or after the system LIBPATH. SysDumpVariables Dump all variables in the current scope either to the specified file (new data is appended) or to STDOUT. SysSetFileDateTime Modify the "Last Modified"date of the specified file. SysGetFileDateTime Return the selected file date time attribute of the specified file. SysStemCopy Copy elements from the source stem to the target stem. SysStemDelete Delete the specified item at index startitem in the stem. SysStemInsert Insert a new item at the specified position in the stem. SysStemSort Sort all or the specified items in the stem. SysVersion Return a string to identify the operating system and its version. SysUtilVersion Return a version number that identifies the current level of the REXX utilities package. 12.1 SysQueryExtLIBPATH ----------------------- Return the current path to be searched before or after the system LIBPATH. Syntax SysQueryExtLIBPATH(flag) Parameters flag The flag controlling which extended LIBPATH should be returned: B Return the BEGINLIBPATH setting. E Return the ENDLIBPATH setting. Remarks This function returns the current path to be searched before or after the system LIBPATH when locating DLLs. Return Values Current BEGINLIBPATH or ENDLIBPATH. Example /* Show the current setting of the extended LIBPATH */ say "BEGINLIBPATH is:" SysQueryExtLIBPATH("B") say "ENDLIBPATH is: " SysQueryExtLIBPATH("E") 12.2 SysQuerySwitchList ----------------------- Obtain information about the entries in the window list. Syntax SysQuerySwitchList(stem, [flags])) Parameters stem The name of a REXX stem variable. SysQuerySwitchList sets REXX variable stem.0 to the number of window list entries and stores the individual entries in stem.1 to stem.n. flags Any combination of the following: T Include invisible entries in the list. G Include grayed entries in the list. N Include entries in the list that are not jumpable. D Return the list in the detailed form: PID SID Visibility Jumpable ProgType Name Remarks By default, only visible and jumpable entries are returned. Return Values Returned values are taken directly from the SWCNTRL structure. For a description of the possible values, see the Presentation Manager Guide and Reference. Example /* Type the Window List */ call SysQuerySwitchList "list." do i = 1 to list.0 say 'Entry' i 'is' list.i end 12.3 SysSetExtLIBPATH --------------------- Define the current path to be searched before or after the system LIBPATH. Syntax SysSetExtLIBPATH([path], flag) Parameters path The extended LIBPATH string. The string can be up to 1024 characters long. The extended LIBPATH may contain the strings "%BEGINLIBPATH%" or "%ENDLIBPATH%", in which case the current values are inserted in the resulting extended LIBPATH. However, if the resulting extended LIBPATH is longer than 1024 characters, the function returns an error. To remove the current extended LIBPATH, specify an empty string or omit this parameter. flag Flag controlling which extended LIBPATH should be set: B Set the BEGINLIBPATH. E Set the ENDLIBPATH. Remarks This function defines the current path to be searched before or after the system LIBPATH when locating DLLs. Return Values The OS/2 error code is returned (0 if successful). Example /* Add D:\TEST to BEGINLIBPATH and delete ENDLIBPATH */ Call SysSetExtLIBPATH "D:\TEST;%BEGINLIBPATH%", "B" Call SysSetExtLIBPATH, "E" 12.4 SysSwitchSession --------------------- Make a specific program the active program. Syntax SysSwitchSession(name) Parameters name The name of the session to switch to. The name must match the appropriate program name as used in the window list (see function SysQuerySwitchList). Return Values The function returns the error code from WinSwitchToProgram (0 if successful). 12.5 SysDumpVariables --------------------- Dump all variables in the current scope either to the specified file (new data is appended) or to STDOUT. Syntax result = SysDumpVariables([filename]) Parameters filename The name of the file to which variables are appended (dump is written to STDOUT if omitted). Remarks This function dumps all variables in the current scope either to the specified file (new data is appended) or to STDOUT if the filename parameter is omitted. The format of the data is (one variable per line): Name=MYVAR, Value="This is the content of MYVAR" Return Values 0 Successful -1 Failure during dump Example Call SysDumpVariables "MyVars.Lst" /* append vars to file */ Call SysDumpVariables /* list vars on STDOUT */ 12.6 SysSetFileDateTime ----------------------- Modify the "Last Modified" date of the specified file. Syntax result = SysSetFileDateTime(filename [,newdate] [,newtime]) Parameters filename The name of the file to update. newdate New date to set specified in YYYY-MM-DD format. newtime New time to set specified in HH:MM:SS format (24-hour format). Remarks This function can be used to modify the "Last Modified" date of the specified file. If no new date or new time is specified, the file date and time is set to the current time (TOUCH). If only newdate is specified, the time is left unchanged. If only newtime is specified, the date is left unchanged. For OS/2 and Windows NT, the filename may also specify a directory name. This convention does not work with Windows 95, Windows 98, AIX(R), or Linux however. The file you want to change must not be open by another process or at least it must allow shared writes in order to update the timestamp. Return Values 0 Successful -1 Failure attribute update Example Call SysSetFileDateTime "MyFile.Log" /* touch file */ Call SysSetFileDateTime "MyFile.Log", "1998-12-17" Call SysSetFileDateTime "MyFile.Log",, "16:37:21" Call SysSetFileDateTime "MyFile.Log", "1998-12-17", "16:37:21" Call SysSetFileDateTime "C:\MyDir" /* touch dir on OS/2, NT */ 12.7 SysGetFileDateTime ----------------------- Return the selected file date time attribute of the specified file. Syntax result = SysGetFileDateTime(filename [,timesel]) Parameters filename The name of the file to query. timesel The file time to query: CREATE, ACCESS, or WRITE. Remarks This function returns the selected file date time attribute of the specified file, if this is supported by the operating and file system (for example, FAT does not provide Create/Access). The selector (timesel parameter) for the time to be returned can be abbreviated with its first character. For example: C CREATE A ACCESS W WRITE For OS/2 and Windows NT, the filename may also specify a directory name. This convention does not work with Windows 95, Windows 98, AIX, or Linux however. The file you want to query must not be opened by another process or at least it must allow shared reads in order to query the timestamp. Return Values -1 File date/time query failed other Date and time as YYYY-MM-DD HH:MM:SS Example Say "File creation time:" SysGetFileDateTime("MyFile.Log", "C") Say "File last access time:" SysGetFileDateTime("MyFile.Log", "A") Say "File last update time:" SysGetFileDateTime("MyFile.Log", "W") Say "Directory creation time:" SysGetFileDateTime("C:\MyDir", "C") 12.8 SysStemCopy ---------------- Copy elements from the source stem to the target stem. Syntax result = SysStemCopy(fromstem, tostem, [from], [to], [count] [,insert]) Parameters fromstem The name of the source stem. tostem The name of the target stem. from The first index in the source stem to copy. The default value is 1. to The position where items are copied or inserted in the target stem. The default value is 1. count The number of items to copy or insert. The default is to copy all items in the source stem. insert Specify "I" to indicate insert; specify "O" to indicate overwrite. Remarks Elements in the source stem are copied starting at the from index into the target stem beginning at the to index. The number of items to copy to the target stem can be specified with count. You can optionally specify that the items should be inserted into the target stem at the position and the existing items are shifted to the back accordingly. This function operates only on stem arrays that specify the number of elements in stem.0 and all elements must be numbered from 1 to n with no omitted index. Return Values 0 Successful -1 Stem copy failed Example Source.0 = 3 Source.1 = "Hello" Source.2 = "from" Source.3 = "REXX" Call SysStemCopy "Source.", "Target." Call SysStemCopy "Source.", "Target.", 1, 5, 2, "I" 12.9 SysStemDelete ------------------ Delete the specified item at index startitem in the stem. Syntax result = SysStemDelete(stem, startitem [,itemcount]) Parameters stem The name of the stem where the item is deleted. startitem The index of the item to delete. itemcount The number of items to delete if more than one. Remarks If more than one item is to be deleted, then the count of items can be specified as the third parameter. After deleting the requested items, the stem is compacted and items following the deleted items are shifted up into the vacant positions. This function operates only on stem arrays that specify the number of elements in stem.0 and all elements must be numbered from 1 to n with no omitted index. Return Values 0 Successful -1 Delete failed Example Call SysStemDelete "MyStem.", 5 Call SysStemDelete "MyStem.", 5, 4 12.10 SysStemInsert ------------------- Insert a new item at the specified position in the stem. Syntax result = SysStemInsert(stem, position, value) Parameters stem The name of the stem where the item is inserted. position The index where the new item is inserted. value The new item value. Remarks All existing items in the stem from the specified position are shifted up by one to make room for the new item. This function operates only on stem arrays that specify the number of elements in stem.0 and all elements must be numbered from 1 to n with no omitted index. Return Values 0 Successful -1 Insert failed Example Call SysStemInsert "MyStem.", 5, "New value for item 5" 12.11 SysStemSort ----------------- Sort all or the specified items in the stem. Syntax result = SysStemSort(stem, order, type, start, end, firstcol, lastcol) Parameters stem The name of the stem to sort. order "A" for ascending or "D" for descending for sort order. The default is ascending order. type "C" for case or "I" for ignore for comparison type. The default is to recognize case. start The first index to sort. The default value is 1. end The last index to sort. The default is the last item. firstcol The first column to use as the sort key. The default value is 1. lastcol The last column to use as the sort key. The default is the last column. Remarks The sort order can be specified as ascending or descending. The comparison type can respect or ignore the case of the strings being compared. The sorting can further be narrowed by specifying the first and last item to be sorted or by specifying the columns used as the sorting key. The sort uses a quicksort algorithm, so the order of equal elements according to the sort key is undetermined. This function operates only on stem arrays that specify the number of elements in stem.0 and all elements must be numbered from 1 to n with no omitted index. Return Values 0 Successful -1 Sort failed Example /* sort all elements descending, use cols 5 to 10 as key */ Call SysStemSort "MyStem.", "D",,,,5, 10 /* sort all elements ascending, ignore the case */ Call SysStemSort"MyStem.", "A", "I" /* sort elements 10 to 20 ascending, use cols 1 to 10 as key */ Call SysStemSort "MyStem.",,,10, 20, 1, 10 12.13 SysVersion ---------------- Return a string to identify the operating system and its version. Syntax result = SysVersion() Parameters None Remarks The returned string contains an identifier for the operating system as the first word and then the version in the second word. This function can be used to replace the operating system-specific functions SysOS2Ver(), SysWinVer(), and SysLinVer(). Return Values Operating system and version. Possible output for operating systems supported by Object REXX: Say SysVersion() -> "WindowsNT 4.00" Say SysVersion() -> "OS/2 2.40" Say SysVersion() -> "AIX 4.2" Say SysVersion() -> "Linux 2.0.34" Example Say SysVersion() /* show OS and version */ 12.14 SysUtilVersion -------------------- Return a version number that identifies the current level of the REXX utilities package. Syntax result = SysUtilVersion() Parameters None Remarks This function can be used to verify that certain functions are available. Return Values The REXXUTIL version number is returned in the format (n.mm), where n is the version number and mm is the modification level. Example Since this function was not part of the original packaging, a sample logic to check for a certain level of REXXUTIL could look like this: If RxFuncQuery("SysUtilVersion") = 1 |, SysUtilVersion() < "2.00" Then Say "Your REXXUTIL.DLL is not at the current level" If a specific function should be used that was added at a later REXXUTIL level, a similar check can be performed by querying that function: If RxFuncQuery("SysSetFileDateTime") = 1 Then Say "Your REXXUTIL.DLL is not at the current level" ------------------------------------------------------------------------ 13.0 Appendix A. Notices ------------------------ This information was developed for products and services offered in the U.S.A. IBM might not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-IBM product, program, or service. IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not give you any license to these patents. You can send license inquiries, in writing, to: IBM Director of Licensing IBM Corporation North Castle Drive Armonk, NY 10504-1785 U.S.A. For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to: IBM World Trade Asia Corporation Licensing 2-31 Roppongi 3-chome, Minato-ku Tokyo 106-0032, Japan The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you. This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice. Any references in this information to non-IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk. IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you. Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact: IBM Corporation Department LZKS 11400 Burnet Road Austin, TX. 78758 U.S.A. Such information may be available, subject to appropriate terms and conditions, including in some cases, payment of a fee. The licensed program described in this information and all licensed material available for it are provided by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement, or any equivalent agreement between us. Any performance data contained herein was determined in a controlled environment. Therefore, the results obtained in other operating environments may vary significantly. Some measurements may have been made on development-level systems and there is no guarantee that these measurements will be the same on generally available systems. Furthermore, some measurements may have been estimated through extrapolation. Actual results may vary. Users of this document should verify the applicable data for their specific environment. Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products. All statements regarding IBM's future direction or intent are subject to change or withdrawal without notice, and represent goals and objectives only. All IBM prices shown are IBM's suggested retail prices, are current and are subject to change without notice. Dealer prices may vary. COPYRIGHT LICENSE: This information contains sample application programs in source language, which illustrate programming techniques on various operating platforms. You may copy, modify, and distribute these sample programs in any form without payment to IBM, for the purposes of developing, using, marketing or distributing application programs conforming to the application programming interface for the operating platform for which the sample programs are written. These examples have not been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of these programs. You may copy, modify, and distribute these sample programs in any form without payment to IBM for the purposes of developing, using, marketing, or distributing application programs conforming to IBM's application programming interfaces. Each copy or any portion of these sample programs or any derivative work, must include a copyright notice as follows: (C) (your company name) (year). Portions of this code are derived from IBM Corp. Sample Programs. (C) Copyright IBM Corp. 2001. All rights reserved. ------------------------------------------------------------------------ 13.1 Trademarks --------------- The following terms are trademarks of International Business Machines Corporation in the United States, or other countries, or both: AIX EtherJet IBM Micro Channel OS/2 Presentation Manager ThinkPad WebSphere WIN-OS/2 Ultrabay Lotus is a registered trademark of Lotus Development Corporation. Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both. Java and all Java-based trademarks and logos are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States and other countries. Pentium is a trademark of Intel Corporation in the United States, other countries, or both. Other company, product, and service names may be trademarks or service marks of others. ------------------------------------------------------------------------