FIXED IDE HARD DRIVE AND REMOVABLE MEDIA SUPPORT October 13, 1998 OS/2 Device Driver Development Network Computing Software Austin, Tx (c) Copyright International Business Machines Corporation, 1998. All rights Reserved. CONTENTS ________ 1.0 INTRODUCTION 2.0 INSTALLATION 2.1 Updating the Installation Diskettes 2.2 Updating a Previously Installed Warp System 3.0 LARGE HARD DRIVE CONSIDERATIONS 3.1 System Hang or Hard Drive Hesitation 3.2 Cannot Mark a Partition Installable 3.3 IPE on Boot, "Trap D" 3.4 Inconsistencies in Total Disk Space 3.5 Application Install Fails with "Not Enough Space" 3.6 Performance Problems With Two Devices on a Single Channel 3.7 Install Diskettes or Utility Diskettes Hang on Boot (APAR JR12065) 3.8 Additional Parameters For IDE Device Driver 4.0 REMOVABLE MEDIA SUPPORT 4.1 Partitioned Removable Media 4.1.1 Using Protected Media 4.1.2 Assignment of Drive Letters 4.1.3 Configuring Partition Support (OS2DASD) 4.1.4 Ejecting the media 4.1.5 Limitations of Partitioned Removable Media Support 4.2 Large Floppy Removable Media (LS-120) 4.2.1 Limitations of LS-120 Support 5.0 COPYRIGHT AND TRADEMARK INFORMATION 1.0 INTRODUCTION _________________ FixPak 35 (FP35) for Warp 3 and FixPak 6 (FP6) for Warp 4 extended support for fixed Enhanced IDE drives to sizes up to 8.4GB and added new caching HPFS and FAT file system support for removable media drives such as SCSI Syquest Syjet 1.5GB portable hard drive and the Iomega jaz 1GB and 2GB personal hard drives. This package contains updates to the support in FP35 and FP6, extending support to fixed Enhanced IDE drives greater than 8.4GB, fixing some prob- lems, and adding additional documentation on removable media support. If you install or have installed fixpaks newer than FP38 or FP9 then this package is not required. For Warp Server Advanced HPFS386 support of removable media, you additionally need LAN Server SelectPack IP_8508. These fixpaks are available from http://ps.software.ibm.com/ under the link "Downloads and News." Install the fixpaks first, carefully following the instructions with the fixpaks; then follow the directions in this README to install this package. If you are attempting to install Warp 3 or Warp 4 for the first time on a fixed hard drive greater than 4.3GB, then: 1. Follow the instruction on "Updating the Installation Diskettes" in this README and use the new diskettes to install Warp. 2. Install FP35 for Warp 3 or FP6 for Warp 4. 3. Follow the instructions in this README to install this package. 2.0 INSTALLATION _________________ 2.1 UPDATING THE INSTALLATION DISKETTES ________________________________________ If you are attempting to install Warp on a hard drive greater than 4.3GB then the Installation diskettes must be updated. 1. Make a backup copy of your Diskette 1 (D1). 2. Copy the new versions of IBM1S506.ADD, IBMIDECD.FLT and OS2DASD.DMD device driver files onto your D1 diskette. 3. Add the statement SET COPYFROMFLOPPY=1 to the CONFIG.SYS on D1. 4. Save the changes. 5. Start the installation with the Installation Diskette. 6. When you are prompted for Diskette 1, use the diskette you modified. 7. Proceed with the installation. 8. If during the installation process or when restarting your system, you lose connection to your hard disk or CDROM, make sure that the device driver statements are in the CONFIG.SYS file and the new versions of the IBM1S506.ADD, IBMIDECD.FLT and OS2DASD.DMD device driver have been copied to the \OS2\BOOT\ directory. Use the date of the files to distinguish the newer versions. 2.2 UPDATING A PREVIOUSLY INSTALLED WARP SYSTEM ________________________________________________ 1. (Optional) Save the existing (old) level of drivers in your system. a. Change Directory to the \os2\boot\ directory on your boot drive. b. Rename the drivers (for example, where the boot drive is C:). The IBMATAPI.FLT driver may not have been previously installed. [C:\os2\boot] rename IBM1S506.ADD IBM1S506.ORG [C:\os2\boot] rename IBMIDECD.FLT IBMIDECD.ORG [C:\os2\boot] rename OS2DASD.DMD OS2DASD.ORG [C:\os2\boot] rename IBMATAPI.FLT IBMATAPI.ORG 2. Device Driver Install o (Warp 3) Open the Device Driver Install program in the OS/2 System Folder/System Setup Folder. o (Warp 4) Open the Device Driver Install program in the OS/2 System/System Setup/Install-Remove Folder. 3. Point the Device Driver Install file dialogue to the directory where you have placed the new files in this package. 4. Reboot the system. 3.0 LARGE HARD DRIVE CONSIDERATIONS ____________________________________ 3.1 SYSTEM HANG OR HARD DRIVE HESITATION _________________________________________ The problem is the IDE chip sets on certain planars signal that they support busmastering but actually have a defect that prevents it from working cor- rectly. The driver detects busmastering support, turns on busmastering and attempts to use it. Some symptoms are: o System will not boot with IBM1S506.ADD. o CHKDSK command does not work properly. o Hard drive stops or hesitates for minutes at a time. This is a known problem with ThinkPad models 760E/ED/ELD/EL. However the chip set can, and does, show up on planars of other manufacturers. To correct: 1. Edit the CONFIG.SYS file on Diskette 1 or the boot drive. 2. Disable busmastering by adding the parameter /!BM to the driver; for example: BASEDEV=IBM1S506.ADD /A:0 /!BM /A:1 /!BM 3. Save the changes and reboot. 3.2 CANNOT MARK A PARTITION INSTALLABLE ________________________________________ There is a BIOS restriction that installable (startable) or bootable parti- tions must be contained within the first 1024 logical cylinders of the disk. This is true for both EIDE and SCSI hard disk drives. If FDISK 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 FDISK to reduce the size of the startable or bootable partition by sufficient MBytes. One way to calculate the correct partition size is to do the following: 1. Edit your CONFIG.SYS and add the parameter /W or /V to the BASEDEV=IBM1S506.ADD statement. 2. Save this change and reboot the system. 3. At initialization, record the far left hand column of numbers of the geometry information under the OS2:log heading; for example, where C=cylinder, H=head, and S=sector: OS2:log C 1027 H 63 S 128 4. Calculate the 1024 cylinder size in MBytes as ( H x S ) / 2. (round down). All bootable partitions must be contained within this size. In this example the bootable partition must be contained in the first 4032 MBbytes of the disk and cannot exceed a single partition size of 4032 MBytes within this area. No bootable partition may extend beyond the first 4032 MBytes. 5. Use FDISK to resize the partitions and reboot. 3.3 IPE ON BOOT, "TRAP D" __________________________ If you experience a Trap D on boot when using the /FORCE parameter on IBM1S506.ADD, and you have the NetFinity client installed, REMark out the BASEDEV=NFDASD.FLT statement in CONFIG.SYS. 3.4 INCONSISTENCIES IN TOTAL DISK SPACE ________________________________________ This version of IBM1S506.ADD allows the detection and correct reporting of some additional free space on certain drives. This "free space" is real and now can be accessed, either by creating a new partition or using a program such as PartitionMagic to add the free space to an existing partition. This will not cause any corruption or inaccessibility to the data currently on the disk. 3.5 APPLICATION INSTALL FAILS WITH "NOT ENOUGH SPACE" ______________________________________________________ FAT partitions under OS/2 are limited to a 2.1GB maximum size. HPFS parti- tions are limited to a 64GB maximum size. However there is the magic number, 2,147,483,647 (2.1GB). This 2.1GB value is the maximum number that will fit into a signed 32-bit integer. Some application software installation pro- grams query OS/2 about the available remaining space on the partition and save the result into a signed 32-bit integer. If more than 2.1GB is avail- able there is an overflow, it appears no space is available, and the instal- lation program refuses to continue. Two solutions are: o Partition the remaining space into maximum 2GB partitions. o Retain the large partition, but before trying to install software create a large temporary file that reduces available space to less than 2.1GB. After installation of the application delete the temporary file. 3.6 PERFORMANCE PROBLEMS WITH TWO DEVICES ON A SINGLE CHANNEL ______________________________________________________________ With certain planars, two devices attached to the same IDE channel will exhibit performance problems when one device is a slow non-DMA device like a CDROM 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, then you can disable busmastering for that channel, by specifying parameters on the driver IBM1S506.ADD in CONFIG.SYS. For example, if you wanted to disable bus mastering for the sec- ondary controller, you would add the parameters "/A:1 /!BM" to the IBM1S506.ADD line in CONFIG.SYS. 3.7 INSTALL DISKETTES OR UTILITY DISKETTES HANG ON BOOT (APAR JR12065) _______________________________________________________________________ Diskette 1 of the Install or Utility diskette sets may appear to hang on boot, waiting for a removable media device to respond. To avoid: 1. Edit the CONFIG.SYS on Diskette 1 of the set 2. REMark out the basedev=ibmint13.i13 statement and save the file. 3. Reboot 3.8 ADDITIONAL PARAMETERS FOR IDE DEVICE DRIVER ________________________________________________ PARAMETER FUNCTION /V Verbose Mode, displays controller status and drive geometry information during OS/2 initialization. /W Verbose Mode, displays controller status and drive geometry information during OS/2 initialization. Initialization stops after displaying the information for each device, with a "Press Enter to Continue" message. It is possible that the message buffer will overflow, resulting in a "Lost message" message. This parameter works correctly on Warp 3 with FP35 or later systems and on Warp 4 systems with FP6 or later. /FORCE Forces the emulation of an IDE CDROM drive, even though one is not present during OS/2 initialization. For example, the statements BASEDEV=IBM1S506.ADD /A:1 /U:0 /ATAPI /FORCE BASEDEV=IBMIDECD.FLT support inserting an internal CDROM drive into the Ultrabay of a ThinkPad 755CD after suspend, even though the drive is not present during initialization. 4.0 REMOVABLE MEDIA SUPPORT ____________________________ Removable media devices attach to the system by a variety of interfaces. IDE Supported with the OS/2 supplied IBM1S506.ADD device driver. EIDE Supported with the OS/2 supplied IBM1S506.ADD device driver. ATAPI Supported with the OS/2 supplied IBMATAPI.FLT device driver. ATA Supported with the OS/2 supplied IBM1S506.ADD device driver. Iomega Zip ATA drives are supported only as single partition media and be configured in ATA Compatibility Mode; that is, the jumpers are: Master Slave   þ Ä þ       SCSI Supported with the OS/2 device driver for the SCSI controller to which the device is attached. To ensure correct operation with the Adaptec 1542 SCSI adapter, partition sizes should always be less than 1GB. PP Parallel Port attached devices are supported with vendor- supplied drivers. The device driver must have an ".ADD" extension for the media to be supported as partitioned remov- able. For example, the Syquest Syjet Parallel drive is prop- erly supported by the vendor-supplied EPST.ADD driver, the Iomega Zip Parallel uses a vendor-supplied *.SYS driver and is not supported by the partitioned removable support, and the Syquest SparQ Parallel Iomega ZipPlus Parallel drives have no OS/2 drivers at all. Removable media devices are supported in one of two ways. LARGE FLOPPY The LS-120 drive. PARTITIONED All other magnetic removable media devices. This media appears as a removable hard drive. 4.1 PARTITIONED REMOVABLE MEDIA ________________________________ Features of the partitioned removable media support are: o Ability to partition removable media into multiple partitions o Ability to format with either HPFS or FAT o Ability to exploit caching performance o Ability to use HPFS long file names o Drag/drop capability through the Workplace drive icon o Operating system protection to safely eject media through software eject utility o Assignment of drive letters to end of disk drive lettering chain to prevent floating drive letters o Ability to predetermine a fixed number of drive letters for multiple par- titions for removable media 4.1.1 USING PROTECTED MEDIA There are some restrictions on the use of these devices. These restrictions deal with vendor-provided protection routines that either read/write or pass- word protect the media. You are unable to read or write HPFS formatted media that has been read, write or password protected by a vendor supplied protection utility. For all read and write protected media, remove the vendor protection prior to trying to read or write to the media. For instance, if you do not remove the pro- tection, you will get the following failures: o If you issue a DIR command to write or password protected media, you will receive a "Drive improperly stopped" error message. o If you try to FORMAT a write or password protected media, you will receive numerous error messages after a few minutes. o If you try to use desktop operations like drag/drop folders/files, you will receive numerous error messages. Once the vendor supplied protection is removed, then these errors will no longer occur. 4.1.2 ASSIGNMENT OF DRIVE LETTERS New Algorithm: no filters assumed Primary from fixed disk 1 Primary from fixed disk 2 Primary from fixed disk n Extended from fixed disk 1 Extended from fixed disk 2 Extended from fixed disk n Primary from removable disk 1 Extended(s) from removable disk 1 Primary from removable disk 2 Extended(s) from removable disk 2 Primary from removable disk n Extended(s) from removable disk n Lack of a primary partition (or Extended Partition only) is allowed. If no media is present at boot, a single logical drive is reported. Note that some drives, Syquest EZ135A for example, do NOT report correctly when no media is present and will not be seen at all. If media with multiple partitions is present at boot, then all partitions will be assigned drive letters. 4.1.3 CONFIGURING PARTITION SUPPORT (OS2DASD) BASEDEV=OS2DASD.DMD [/LF] [/MP:(disk,count)[,(disk,count)]] PARAMETER DESCRIPTION /LF Forces all removable devices to be treated as Large Floppy rather than partitioned media. /MP Used to support allocating a predetermined number of drive letters for a partitioned removable media device. Note that this option only applies to partitioned removable devices, and is ignored for any other device type. If the /MP parameter is used, then: SUB-PARAMETER DESCRIPTION DISK The integer disk number of the device, as reported by FDISK, or the wildcard character * to specify all partitioned remov- able devices. COUNT The integer count of the number of partitions to reserve for the device. If the wildcard character * is used, it specifies a default number of drive letters to reserve for all parti- tioned removable devices. Specifying a count for a particular disk will override this default. Also, if there is media in the device at boot time, and it has more partitions which are eligible to receive drive letters than there are drive letters reserved for the device through the /MP option, then the number of drive letters reserved for the device will be increased so that every eligible partition on the media will have a drive letter. If the /MP option is not used, the rules for determining the number of drive letters reserved for a partitioned removable media device are as follows: o If there is no media in the drive at boot time, or the media in the drive has no valid partitions, then one drive letter is reserved for the device. o If there is media in the drive at boot time and the media has valid par- titions which are eligible for drive letters, the number of drive letters is equal to the number of eligible partitions on the media. Media which is formatted in floppy mode is treated as a single partition and allocated a single drive letter. 4.1.4 EJECTING THE MEDIA OS/2 prevents the media from being ejected during data transfers or while there are pending file transactions. The hardware manual eject button is disabled during these times. The eject button will be 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 J:, where J: is the logical drive letter of one of the partitions on the media will cause the media to be ejected. In order for this command to succeed there must be no open files on any of the partitions on the media, nor any 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 rebooting you may issue the command CHKDSK J: /F, where J: is the logical drive letter of one of the par- titions on the media. This will free the media and a subsequent EJECT J: command will cause the media to be ejected. 4.1.5 LIMITATIONS OF PARTITIONED REMOVABLE MEDIA SUPPORT o Applications that manipulate partitioned devices, such as file managers, must be updated to test the fixed/removable flag in order to account for partitioned removable devices. Such applications that have not been updated treat the removable devices as fixed and the results are unpre- dictable whenever media is not present. o Due to the variability of hardware adapter support, installing to or booting from partitioned removable media is not supported. o Optical drive support is unchanged. Partitioned removable media and HPFS do not support optical drives. You should continue to use OPTICAL.DMD and OS2SCSI.DMD. o The following devices were tested during the development of the Parti- tioned Removable Media Support. Similar devices should operate cor- rectly, as should other removable media devices that are made available with a supporting ADD device driver. - Iomega SCSI jaz 1GB and 2GB personal hard drives - Iomega Zip ATA 100MB drives (supported only as single partition media). - Iomega Zip ATAPI 100 MB drives - Syquest SCSI Syjet 1.5GB portable hard drives - Syquest IDE Syjet 1.5GB portable hard drives - Syquest SparQ IDE portable hard drives 4.2 LARGE FLOPPY REMOVABLE MEDIA (LS-120) __________________________________________ The LS-120 drive supports 120-MB diskettes and is compatible with 3.5 inch 1.44-MB standard diskettes, with improved performance. 4.2.1 LIMITATIONS OF LS-120 SUPPORT o If you have an LS-120 drive as drive B, then you must not format it from an OS/2 windowed or full screen session where the current drive is drive A or drive B. The current drive for an OS/2 windowed or full screen session is given as part of the command prompt. For example, if the command prompt in an OS/2 windowed or full screen session is [C:\], then drive C is the current drive. o The following devices were tested during the development of the Large Floppy Removable Media Support. Similar devices should operate cor- rectly. - Imation LS-120 - SuperDisk LS-120 5.0 COPYRIGHT AND TRADEMARK INFORMATION ________________________________________ The following terms are trademarks of International Business Machines Corpo- ration in the United States and/or other countries. IBM OS/2 ThinkPad Ultrabay Other company, product, and service names may be trademarks or service marks of others.