| 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.
Fixed IDE Hard Drive and Removable Media Support
I2O Storage and Transport Device Drivers Version 1.0
PCI Support in the OS/2 Parallel Port Device Driver
IBM Plug'n'Play for PCMCIA CID Installation
Adaptec Ultra160 Family Manager Set
Adaptec 7800 Family Manager Set
This document is a supplement to the IBM OS/2 product documentation and contains non-installation related technical information.
The Convenience Packages include many new or updated features. This section contains information about these features.
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).
Encodings for class codes are provided in the PCI Local Bus Specification, Revision 2.2, Appendix D.
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").
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:
All previously supported CD-ROM drive models are also still supported.
To add UDF support to OS/2 booted from diskettes:
DEVICE=\MOUSE.SYS
DEVICE=\UNICODE.SYS
SET COPYFROMFLOPPY=1 IFS=UDF.IFS /Q
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.
This section describes the syntax and parameters for the FORMAT and CHKDSK commands for use in a UDF file system.
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]
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]
Notes:
The following items apply to CD-RW disks:
FORMAT d: /FS:UDF /F
FORMAT d: /FS:UDF /F
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:
After installation, USB-Removable Media / CD-ROM drivers serve:
The number of devices served for each device category may be changed using CONFIG.SYS parameters. These parameters are described next.
BASEDEV=USBCDROM.ADD /CDS:2
In order to remove service, the key value must be set to 0.
BASEDEV=USBMSD.ADD /CDS:1
BASEDEV=USBMSD.ADD /MAX_FLOPPY
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.
BASEDEV=USBMSD.ADD /REMOVABLE_AS_FLOPPY
BASEDEV=OS2DASD.DMD /MP:2,2
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.
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.
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.
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)
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
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:
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:
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. |
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.
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.
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
You can back up and restore directory limits using the BackDLim and RestDLim utilities.
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. |
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. |
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.
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:
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:
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:
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.
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.
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.
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
The Netware Client option on the OS/2 Warp Version 4 Setup and Installation panel is no longer available during installation.
This section describes several new updates to the online help.
The date syntax for the RESTORE command is:
yyyy-mm-dd
For example:
2001-12-22
Process dumps can now be greater than or equal to 2GB in size.
The following control are available during boot:
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.
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).
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.
The following sections provide information about restrictions and potential problems that might occur after you have installed this product.
Read the following sections for information about the Convenience Package's components and applications.
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.
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;
To use a network printer, the printer drivers on both the client and the server must be at the same level.
StarOffice 5.10 does not install correctly; version 5.1A of StarOffice installs successfully.
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:
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.
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:
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.
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.
Some clients might have difficulty displaying directory information correctly when connecting to an OS/2 ftp server. In particular, the following problems might occur:
To avoid these problems, try the following on the client:
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:
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
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.
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.
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.
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.
The following sections contain information about WorkSpace On-Demand.
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:
For example, if a WorkSpace On-Demand client has the following FIT file entry:
Z:\EPFTEMP \\<server>\share>
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).
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:
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.
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.
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.
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:
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.
x:\java13\jre\bin;x:\java13\bin
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.
To run JAVAKEY, you must add the following line to the CONFIG.SYS file:
SET SHELLHANDLESINC=10
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.
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.
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.
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.
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.
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:
If the alias is shared at server startup, it is automatically restarted.
For Lotus SmartSuite 97 on SMP machines, you must run EXECMODE against each of the following applications:
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.
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.
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.
The following sections contain information about troubleshooting for Remote IPL (RIPL).
There are two key points to make initially about Remote IPL:
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.
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.
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.
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.
To use RIPL on DBCS OS/2 Warp 4.0 systems, perform the following steps in the server RIPL tree (IBMLAN\RPL\OS2.40):
Japan: PTF JR12961 Taiwan: PTF TW99002 China: PTF CN99002
To obtain the OS/2 Warp 4.0 FixPak FX05005 and the correct PTF, contact your IBM representative.
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:
MAXOPENS = (# of RIPL clients) * 70
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.
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, DBCS | 235MB |
| WorkSpace On-Demand 2.0 | 195MB |
| WorkSpace On-Demand 2.0, DBCS | 250MB |
If you want to RIPL to and install a FixPak on an NLV-enabled client, you must perform the following steps on the server:
LANINSTR /SRV
GETRPL /O:os2.40
NET START RPL
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:
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
Configuring RIPL for Arabic OS/2 Warp 4 clients requires the following preparation:
Before the change:
COUNTRY=966,Z:\OS2\SYSTEM\COUNTRY.SYS
After the change:
COUNTRY=785,Z:\OS2\SYSTEM\COUNTRY.SYS
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.
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.
The following section contains information about OS/2 commands, CONFIG.SYS statements, and error messages.
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.
The default value of the VIRTUALADDRESSLIMIT CONFIG.SYS statement has been changed from 2048 (2 gigabytes) to 1024 (1 gigabyte).
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.
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.
If you receive a SYS1718 error message about missing IBMLANLK files after you install a product and restart your system, perform the following steps:
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
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.
The following limitations and restrictions apply to Associated Bitmap-fonts:
The following sections contain information about hardware devices and device drivers.
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:
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:
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.
http://service.software.ibm.com/os2ddpak/
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.
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.
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:
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:
http://www.networking.ibm.com
You can use a temporary workaround until the adapter microcode can be updated:
d:\IBMLAN\RPL\OS2xxNTR.CNF
Where xx is 30 or 40.
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.
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.
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:
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.
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:
OS2:log
C 1027
H 63
S 128
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.
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.
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:
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.
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:
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 only | Internal: A: | Internal: A: |
| Boot with external FDD only | External: A: | External: A: |
| Boot with both FDDs |
|
|
| Boot with no FDD, suspend, connect internal FDD | Internal: A: | Internal: A: |
| Boot with no FDD, suspend, connect external FDD | External: B: | External: A: |
| Boot with no FDD, suspend, connect both FDDs |
|
|
| Boot with external FDD, suspend, connect internal FDD | Not supported |
|
Additional parameters for IDE device drivers are as follows:
BASEDEV=IBM1S506.ADD /A:1 /U:0 /ATAPI /FORCE BASEDEV=IBMIDECD.FLT
Removable media devices attach to the system by a variety of interfaces.
Removable media devices are supported in one of two ways:
The configuration statement used to configure partition support is as follows:
BASEDEV=OS2DASD.DMD [/LF] [/MP:(disk,count)[,(disk,count)]]
If the /MP parameter is used, additional parameters apply:
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:
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.
The following limitations apply to partitioned removable media support:
The LS-120 drive supports 120MB diskettes and is compatible with 3.5 inch 1.44MB standard diskettes with improved performance.
The following limitations apply to LS-120 support:
The CD-ROM Device Manager (OS2CDROM.DMD) has the following additional features:
This IOCtl function formats and verifies the disk.
DSK_FORMATVERIFY (45h)
struct FmtVerify_param {
UCHAR Command; // Bit 7: 0 - start formatting,
// 1 - format status
};
struct FmtVerify_data {
UCHAR Status; // Percent of formatted volume, if such feature supported
// 0, if not supported
};
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.
This IOCtl function executes SCSI a command.
CDROMDISK_EXECMD (7Ah)
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
Content of the Data Packet depends on the SCSI command. Length is defined by the data_length field in the Parameter Packet.
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.
This IOCtl function returns features of the current DM version, if applied to "CD-ROM2$" device name.
CDROMDISK2_FEATURES (63h)
None
ULONG driver_status; #define FEATURE_USB_SUPPORT 0x00000001L #define FEATURE_CDRW_SUPPORT 0x00000002L #define FEATURE_EXECMD_SUPPORT 0x00000004L
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.
Returns drive letters for CD-ROM devices if applied to the "CD-ROM2$" device name.
CDROMDISK2_DRIVELETTERS (60h)
None
struct DriveLetters {
USHORT DriveCount; // number of supported CD-ROM drives
USHORT DriveFirst; // letter of the first CD-ROM drive
};
This function did not work correctly in previous versions of OS2CDROM.DMD.
This IOCtl function queries device parameters.
DSK_GETDEVICEPARAMS (63h)
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:
| 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.
IBMIDECD.FLT now supports IDE CD-Writers for reading and writing.
This section provides a table listing the supported IDE controllers and identifies known restrictions and limitations.
The OS/2 IDE Controller Adapter Device Driver (IBM1S506.ADD)
supports the following PCI IDE Controllers:
Table 3. Supported PCI IDE Controllers
| Controller Name | Controller 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 HUB | ATA 66 | See Intel chipsets restrictions. |
| I82801AB | Intel 82801AB IO HUB | ATA 33 |
|
| I82801BA | Intel 82801BA IO HUB | ATA 100 | See Intel chipsets 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. |
This section covers some restrictions for IBM1S506.ADD. These restrictions are caused mainly by hardware problems.
In case there are two devices on a channel on any Intel 82801 chip, the top UDMA mode is limited to UDMA 2.
IBM1S506.ADD has the following limitations for VIA IDE controllers listed above:
IBM1S506.ADD has the following limitations for SiS IDE controllers listed above:
This section discusses the LSI Logic Storage Device Management System (SDMS) support.
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)
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:
Refer to the OS/2 documentation to fully understand this requirement.
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.
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:
Table 4 lists the command-line options discussed.
| 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. |
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.
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<hba[:id]>[,<hba[:id]>]*
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>
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<hba[:id]>[,<hba[:id]>]*
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>
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.
Usage:
/EXCLUDE<chip:bus:dev/func>[,<chip:bus:dev/func>]*
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<F:0:A0>
or
BASEDEV=SYM8XX.ADD /X<F:0:A0>
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.
Usage:
/SYNCH_RATE=n<hba[:id]>[,n<hba[:id]>]*
The following examples illustrate how to use this option:
BASEDEV=SYM8XX.ADD /SYNCH_RATE=0<0:3>
BASEDEV=SYM8XX.ADD /SR=10<1>
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<hba[:id}>[,n<hba[:id]>]*
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>
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<hba[:id]>[,n<hba[:id]>]*
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>
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<hba[:id]>[,n<hba[:id]>]*
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>
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).
Usage:
/PARITY=n<hba[,hba]*>[,n<hba[,hba]*>]*
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>
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<hba[:id]>[,n<hba[:id]>]*
The following examples illustrate how to use this option:
BASEDEV=SYM8XX.ADD /QTAG=0<0:3>
BASEDEV=SYM8XX.ADD /QT=5<2>
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,<hba[:id]>[,n<hba[:id]>]*
The following examples illustrate how to use this option:
BASEDEV=SYM8XX.ADD /WIDTH=8<0:3>
BASEDEV=SYM8XX.ADD /W=8<2>
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.
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:
Only one of these parallel port device drivers is resident for each PC running in OS/2.
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.
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.
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.
The following accelerated GRADD drivers are included:
Also included are generic VGA and SVGA support.
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.
Supported resolutions and color depths are adapter dependent and vary depending on the amount of graphics memory and the adapter implementation.
Current known restrictions include the following:
ATI Mach 64 ISA Bus adapters are currently not supported.
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".
This sections discusses how to install GRADD drivers.
Notes:
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).
/*****************************************************/
/* 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 */
/*****************************************************/
To set up the GRADD Graphics BBS driver installation directory, do the following:
C: MD C:\BBS MD C:\BBS\GRADD CD C:\BBS\GRADD
GRADDBB* -DIR -OVER
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.
SETUP
This section discusses Plug'n'Play for PCMCIA software for IBM ThinkPads using OS/2 Warp 4.0.
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
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).
This section describes the configuration parameters you can specify for Socket Services and Card Services.
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.
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.
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.
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.
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 following is a list of adapter cards that use Point Enabler device drivers:
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.
If problems occur with an adapter card failing to work properly, there are two suggestions that may correct the problem:
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.
<< 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.
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.)
BASEDEV=PCM2ATA.ADD /S:4 /!DM /NOBEEP
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.
REM BASEDEV=AHA152X.ADD
Change that statement to look like the following:
BASEDEV=AHA152X.ADD
REM BASEDEV=FD16-700.ADD
Change that statement to look like the following:
BASEDEV=FD16-700.ADD
This section describes the optional parameters for use with the IBM Plug'n'Play for PCMCIA for CID installations.
PCMINST2 /S:<product source> /R:<specific response file>
/R:<group response file> /L1:<error log file>
/L2:<history log file> /T:<target>
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.
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.
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.
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.
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.
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.
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.
The format of the response file is as follows:
#--- Comment ------------- Target=C:\TEST ReBoot=N UpdateConfig=Y ForceReplace=Y Use2ndSS=N *--- Comment -------------
Examples of valid Target= parameter usage:
Target=d: TARGET=d:\ TaRgEt=d:\ppp Target=d:\ppp\
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:
Examples of valid ReBoot= parameter usage:
ReBoot=N ReBoot=Y REBOOT=NO REBOOT=Yes
Examples of valid UpdateConfig= parameter usage:
UpdateConfig=N UpdateConfig=Yes UPDATECONFIG=NO
Examples of valid ForceReplace= parameter usage:
ForceReplace=N ForceReplace=Yes FORCEREPLACE=NO
Examples of valid Use2ndSS= parameter usage:
Use2ndSS=N Use2ndSS=Yes USE2NDSS=NO
This section describes the Adaptec Ultra160 Family Manager Set support.
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
For example, Bus 0, device 0 assigned as adapter 0; Bus 1, device 1 assigned as adapter 1, and so on.
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:
BASEDEV=IBM1S506.ADD /V
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 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.
The standard format for command-line switches is:
BASEDEV=AICU160.ADD [Universal Parameter][Adapter ID]
[Unit Parameter]{[SCSI Target ID]}
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
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
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.
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
BASEDEV=AIC78U2.ADD /!PCIHW
BASEDEV=AIC7870.ADD /!PCIHW
BASEDEV=AIC78U2.ADD /!PCIHW
BASEDEV=AIC7870.ADD /!PCIHW
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:
BASEDEV=IBM1S506.ADD /V
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 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.
The standard format for command-line switches is:
BASEDEV=AIC78U2.ADD [Universal Parameter][Adapter ID]
[Unit Parameter]{[SCSI Target ID]}
BASEDEV=AIC7870.ADD [Universal Parameter][Adapter ID]
[Unit Parameter]{[SCSI Target ID]}
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
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
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. |
Return the current path to be searched before or after the system LIBPATH.
Syntax
SysQueryExtLIBPATH(flag)
Parameters
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")
Obtain information about the entries in the window list.
Syntax
SysQuerySwitchList(stem, [flags]))
Parameters
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
Define the current path to be searched before or after the system LIBPATH.
Syntax
SysSetExtLIBPATH([path], flag)
Parameters
To remove the current extended LIBPATH, specify an empty string or omit this parameter.
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"
Make a specific program the active program.
Syntax
SysSwitchSession(name)
Parameters
Return Values
The function returns the error code from WinSwitchToProgram (0 if successful).
Dump all variables in the current scope either to the specified file (new data is appended) or to STDOUT.
Syntax
result = SysDumpVariables([filename])
Parameters
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
Example
Call SysDumpVariables "MyVars.Lst" /* append vars to file */ Call SysDumpVariables /* list vars on STDOUT */
Modify the "Last Modified" date of the specified file.
Syntax
result = SysSetFileDateTime(filename [,newdate] [,newtime])
Parameters
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
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 */
Return the selected file date time attribute of the specified file.
Syntax
result = SysGetFileDateTime(filename [,timesel])
Parameters
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:
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
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")
Copy elements from the source stem to the target stem.
Syntax
result = SysStemCopy(fromstem, tostem, [from], [to], [count]
[,insert])
Parameters
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
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"
Delete the specified item at index startitem in the stem.
Syntax
result = SysStemDelete(stem, startitem [,itemcount])
Parameters
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
Example
Call SysStemDelete "MyStem.", 5 Call SysStemDelete "MyStem.", 5, 4
Insert a new item at the specified position in the stem.
Syntax
result = SysStemInsert(stem, position, value)
Parameters
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
Example
Call SysStemInsert "MyStem.", 5, "New value for item 5"
Sort all or the specified items in the stem.
Syntax
result = SysStemSort(stem, order, type, start, end,
firstcol, lastcol)
Parameters
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
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
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 */
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"
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 LicensingFor 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 CorporationThe 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 CorporationSuch 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.
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.