PRINT SELECTION FOR APAR - II06078 92/07/14 APAR= II06078 SER= DD DOC FDISK INSTALLATION PROBLEMS OS2INFOAPAR OS2INSTL STAT= INTRAN FESN5NFO000-000 CTID= II0000 ISEV= 4 SB92/06/09 RC CL PD SEV= 4 PE= TYPE= I RCOMP= INFOPCLIB PC LIB INFO ITE RREL= R001 FCOMP= PFREL= F TREL= T ACTION= SEC/INT= DUP/ USPTF= PDPTF= DUPS 0 DW92/06/09 RT SC FT RE PT UP LP PV AP EN FL LC92/07/02 RU92/06/09 CUST INST LVL/SU= FAILING MODULE= FAILING LVL/SU= SYSROUTE OF: RET APAR= PS= COMP OPER ENV= SYSRES= SYSIN= SYSOUT= CPU= RE-IPL= OPTYPE= SPECIAL ACTIVITY= REGRESSION= PRE-SCREEN NO.= RSCP= RS000 ERROR DESCRIPTION: OSinfoapar os2instl LOCAL FIX: ************************************************* ************************************************* *** GENERAL INFO ON DRIVE PROBLEMS *** ************************************************* ************************************************* These problems can be caused by - incorrect setup information in CMOS memory for hard drive being used - disk corruption/failure - incorrect identification of adapter by OS/2 - trying to install on a drive which was compressed using a stacker utility - trying to install over a Beta version of OS/2 2.0 (1.3 is OK) controller/hard disk **************** Supported Drives **************** On (E)ISA bus machines, OS/2 specifically supports hard drive adapters which conform to the Western Digital chipset interface standard (i.e. nearly all MFM, RLL, IDE, and ESDI adapters) and Adaptec, Future Domain, and IBM SCSI adapters. In addition, "generic" INT13 support is provided for all other hard disk adapters. This "generic" support even embraces such devices as Iomega's Bernoulli and SyQuest's removeable media products. CD-ROM support is included as well. At present the OS/2 CD- ROM driver does not work with all brands, but the DOS device drivers, when suitably configured and installed, will still provide CD-ROM services to DOS/Windows programs. Printer and plotter support is discussed in Question 12. ---------------------------- Certain PC compatibles have difficulty accepting OS/2 2.0 (CSD level 02000 only; see Question 24), particularly AT bus systems with RLL, MFM, ESDI, or certain SCSI adapters (e.g. AMI SCSI adapters). The problem usually appears in the form of FDISK errors, extremely slow copying to the hard disk, or a whining/grating noise emanating from the hard disk. IBM suggests a simple workaround. First, DISKCOPY Diskette 1 of your OS/2 2.0 package. Set aside your original Diskette 1 and use the copy from now on as if it were the original. Using a text editor, modify the CONFIG.SYS file on Diskette 1 (the copy), replacing the line: BASEDEV=IBM1S506.ADD with REM BASEDEV=IBM1S506.ADD. Boot the Installation Diskette, and proceed through the installation procedure through the first five diskettes, then reinsert the Installation Diskette as directed. Then after files have been copied from the Installation Diskette the system prompts you to remove the diskette and press ENTER to reboot. Do so, but immediately reinsert the Installation Diskette as soon as the screen clears. Follow instructions (insert Diskette 1 and press ENTER when prompted), then press ESC when prompted. At the OS/2 command line, type: RENAME C: OS2 IBM1S506.ADD IBM1S506.XXX COPY C: OS2 IBMINT13.I13 C: OS2 IBM1S506.ADD replacing C: with the appropriate drive if you are installing elsewhere. Remove Diskette 1, then press CTRL-ALT-DEL to reboot to finish installation. Miscellaneos installation tips ****************************** Be sure adequate free disk space is available before installing, including space for a swap file. Drives compressed using Stacker or similar utilities should be uncompressed before installing (unless access to these drives is not needed). OS/2 2.0 is not presently compatible with Stacker or similar utilities. However, an OS/2 2.0 version of Stacker is forthcoming. with other adapters. For example, many SuperVGA adapters use large chunks of upper memory, and many hard disk adapters have on board ROMs which can be mapped into this area as well. Adapters must cooperate in their use of memory and interrupts and must not share address space or interrupts. Check your product manuals for more help. Do not select HPFS when installing if your machine has 6 MB of RAM or less. Doing so will likely result in diminished performance. Change the IFS=...HPFS... line in your CONFIG.SYS to REM IFS=... if necessary. Automatic migration of your DOS CONFIG.SYS and AUTOEXEC.BAT files is not recommended. If you have Windows 3.1 installed on your system do not migrate your Windows desktop. Be sure your CMOS setup parameters are set correctly, especially those relating to floppy drives. All shadow RAM should be disabled for best performance. RAM should be given sufficient wait states and precharge cycles. The AT bus should run at 8 MHz. If you are using the IBMINT13.I13 driver to access an MFM, RLL, or ESDI hard drive, and the hard drive has more than 1024 cylinders, be certain your hard disk adapter's sector translation mode is enabled. Certain Quantum IDE hard disks require a free ROM update from the manufacturer to work with OS/2. When installing over a beta version of OS/2 (except OS/2 2.0 level 6.177H, the Limited Availability release) be sure to reformat. To install the OS/2 2.0 DOS/Windows upgrade DOS or OS/2 must already reside on the hard disk. If Diskette 1 is not write protected then the installation program will record a file indicating that upgrade terms have been satisfied and, in the future, will not require DOS or OS/2 on the hard disk to install. OS/2 uses the same diskette format as DOS, so use DISKCOPY to backup the installation diskettes and verify that none have been corrupted. **************************************** Miscellaneous Questions/Problems/Answers **************************************** Question: How do I access HPFS partitions on my hard drive without booting from the hard drive? I'm getting error messages now -- how do I "repair" my hard disk? With IBM OS/2 2.0, insert the Installation Diskette, Shutdown (if necessary), and reboot. When prompted insert Diskette 1 and press ENTER. When prompted, press ESC. You will be given an OS/2 command line prompt. From there you can make necessary changes to your hard disk -- an OS/2 character mode text editor is handy for such changes. (Make sure you backup CONFIG.SYS before making any changes so that you can easily revert to the old version should things go wrong.) FAT or HPFS partitions. After you reach the command line, insert Diskette 2. Do not log to another drive. Type CHKDSK X: /F to repair most kinds of damage to your hard disk, replacing X with the appropriate drive letter. OS/2 CHKDSK will also remark your hard disk as accessible, if possible, should OS/2 "lock it out" for some reason. The best way to avoid the need to perform CHKDSK is to always select Shutdown. Click on the Workplace Shell desktop background using mouse button two to bring up the appropriate menu. Also, avoid deleting OS/2- related files when using native DOS. Problem: My install hangs on Disk 1. Resolution: In many cases, PCM hardware has disk caching enabled on the drive controller card. The hang can often be fixed by disabling the on-board caching. Another suggestion is if the card has asynchronous memory refresh capabilities, turn it off. This too may fix the problem. Problem: Can't install OS/2 2.0 from Drive B. What's wrong? Resolution: IBM OS/2 2.0 can only be installed from Drive A, like DOS (unless your BIOS supports booting from Drive B), or across a network (contact IBM for more information on network installation procedures). If you have the wrong disk size go back to your dealer and obtain the correct media. Otherwise you could go inside your machine and swap floppy drive cable connectors, use your system's setup utility to set the new CMOS parameters, and then install OS/2 from the "new" Drive A. Sometimes the floppy drive cable connectors will not be the same. If so you can obtain an adapter plug. Question: How should I partition my hard disk for OS/2? Answer: OS/2 should ideally be in a partition by itself, unless you are considering a dual boot system which requires DOS to be loaded first. The partition should be approx 40-50 megabyts in size for OS/2 alone, assuming you wish a full default install and the swap drive on the same partition. The lower amount of memory you have, the larger swap file (and partition) you will need. You should have at least 2 partitions, one for OS/2 and the other for data. Question: Do I need to reformat to install OS/2 2.0? Answer: It's always a good idea. However, the only versions of OS/2 you MUST reformat over is over ANY OS/2 beta EXCEPT for L.A. (6.177H) If you formatted during an install and the install aborted, reformat. If you did a "dirty" (unformatted) install and it died, try again without formatting. If that too fails, you may want to back up any needed data files from the target drive and reformat. There should be no other reason to install 2.0 G.A. over itself. If you want to add features, use the OS/2 System object, System Setup and Selective Install. You can add virtually any feature this way. COUNTRY.SYS not found Symptom: COUNTRY.SYS error message at bootup of first two diskettes or after first five diskettes, and reboot of machine by installation program. Problem: Invalid device driver for hard disk being used. Seems to occur more often on non-IDE/SCSI drives. More prevalent on ESDI/MFM/RLL drives. Country.SYS error messages almost always point to OS/2 not being able to recognize the hard drive media. Resolution: Follow instructions in #8 above. COUNTRY.SYS not found installing. Problem: Possible conflict with another device on the machine. Resolution: Disconnect any tape backup, CD-ROM or other devices not needed for installation. Reconnect once installation is complete. COUNTRY.SYS not found on a P70 Symptom: COUNTRY.SYS not found error message while installing on a P70. Resolution: Contact your IBM CE for ECA068. This is indicative of a problem recognizing the disk. ECA068 should remedy this. See APAR II06081 for more info on SCSI compatibility.