PRINT SELECTION FOR APAR - II06065 92/07/14 APAR= II06065 SER= DD DOC INSTALLATION PROBLEMS FOR OS/2 2.0 FOR IBM SYSTEMS AND PCM OEM SYSTEMS OS2INFOAPAR OS2INSTL STAT= INTRAN FESN5NFO000-000 CTID= II0000 ISEV= 4 SB92/06/04 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/04 RT SC FT RE PT UP LP PV AP EN FL LC92/06/17 RU92/06/04 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: Keywords: OS2INFOAPAR OS2INSTL PROBLEM: OS/2 INSTALL FAILS - GENERAL INFORMATION LOCAL FIX: ====================== KNOWN INSTALL PROBLEMS ====================== ************************ MEMORY PROBLEMS ************************ Common Symptom: Trap 2, Trap 6 or other Trap at 60000x:9084. These problems are caused by: Mismatched memory simms (from different manufactures) - this is especially common if you recently added memory to your system, or if it was assembled from parts (not a recognized brand of clone). Mismatched memory simms (different classes) 1x9 simms cannot be mixed with 1x3 simms. Also, the 1x9 simms seem to be more reliable than the 1x3 simms. Slow memories on 486 machines (you may need 60 or 70ns memories). Cache problems. Solution: Replace memory and/or tune wait states, disable cache during install, turn turbo switch off. ****************** SCSI PROBLEMS ****************** These problems are caused by: incorrect BIOS need OS/2 compatible driver from manufacturer incorrect identification of adapter by OS/2 mismatched settings of SYNCH/ASYNCH mode for SCSI controller, hard drive, causes slow drives, misssing icons - see OS2TNT, V2TECH Solution: Update BIOS, get driver from manufacturer, change settings. Known problems: AMI SCSI - slow, noisy disk - BASEDEV workaround - see APAR II06081 FUTURE DOMAIN 16XX SCSI controller - hang on LOGO screen after reboot following good install - check for interrupt conflict - see APAR II06081 Always Technology SCSI - BIOS upgrade - see APAR # II06081 Bernoulli Boxes - UNSOLVED problem with IOMEGA ADAPTER - see APAR # II06081 Colorado Memories Tape Drive - fix available from Colorado - see APAR II06081 PROCOMM+ SCSI disk adapters (Microchannel) - UNSOLVED, talk to PROCOMM - see APAR # II06081 Early versions of IBM 16-bit SCSI adapters - update microcode - see APAR # II06081 dependencies - stick with IBM and Toshiba SCSI CD-ROM drives - others later - see readme Removable media support - Bernoulli (IOMEGA), and SyQuest - support is limited, treats them like big floppies - see readme All Adaptec adapters - SCSI hard disks must be configured as SCSI target ID 0 or 1 to be able to start up from that hard disk - see readme BIOS will not recognize - configure as non startup drive - see readme Adaptec AHA-174x adapter with IBM WDS-3180 80MB SCSI, IBM WDS-3160 160MB SCSI - Adapter will not recognize in 'STANDARD MODE' (AHA-154x emulation). Adapter should be configured in 'ENHANCED MODE' - see readme Future Domain TMC-850/860/875/885 w/BIOS revision level 7.0, and Future Domain TMC-1660/1670/1680 w/BIOS revision level 2.0 can cause "Disk Read Error" on installation disk for model 35 and 40 - need BIOS upgrade - see readme AMI "Fast Disk" and AMI "Fast Disk II" SCSI adapters are incorrectly recognized as Adaptec adapters - see readme for workaround Always IN2000 SCSI adapter - causes Internal Processing Error - need BIOS upgrade VCN1-02 - see APAR # II06081 Quantam Plus Hardcard - need EPROM upgrade - see APAR # II06081 SUMO SCSI adapters don't seem to work with OS/2 - talk to manufacturer ******************** FDISK PROBLEMS ******************** Some common problems: selections to dump or more disk. Insufficient disk space for swapper file growth on low memory systems - suggest install selections to dump or more disk. Incorrect setup information in CMOS memory for hard drive being used - see if it works under another operating system. Slow, noisy disk or FDISK errors (especially on RLL, MFM, or ESDI disks) - BASEDEV workaround - see APAR II06078 Nonstandard or out of date BIOS (especially with IDE drives) - disk inaccessible or FDISK errors. Look for Phoenix or AMI standard BIOS and check dates in MORETIP or info APAR #II06078 Incorrect identification of adapter by OS/2 Trying to install on a drive which was compressed using a stacker utility - suggest uncompressing the disk or reformatting. Trying to install over a Beta version of OS/2 2.0 (1.3 is OK) - reformat first. Trying to install HPFS with less than 6M of memory - dump HPFS or get more memory. Trying to install on less than 4M (user may think he has 4M, but some cache arrangements or ROM to RAM remapping can steal some) - try to disable these features in CMOS setup. Disk corruption/failure (it won't even support DOS) - try high and low level format or get new drive. Quantum IDE hard disks require a free ROM update from Quantum. Install hangs on Disk 1 - this may be caused by having disk caching enabled on the drive controller card - try disabling it - also try turning off the controller's asynchronous memory refresh capabilities if applicable. already reside on the hard disk. IBM OS/2 2.0 can only be installed from Drive A, like DOS (unless you swap drive cables/change CMOS setup to fool system) Automatic migration of your DOS CONFIG.SYS and AUTOEXEC.BAT files can cause problems and is not recommended - recover using original config.sys in OS2 SYSTEM. If you have Windows 3.1 installed on your system do not migrate your Windows desktop. 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. COUNTRY.SYS problems are usually a symptom of a disk which is not recognized by OS/2, and may be caused by the following: Conflict with another device attached to the same controller card. Try removing anthing like a tape backup, which may be the cause of the conflict. On a P70, you need ECA068, contact IBM CE. ****************** BIOS PROBLEMS ****************** Many of the problems above have old bios as their root cause, so there is a lot of overlap between this and other problems - see details on how to check dates in MORETIP or info APAR #II06078 Some common causes: - Wrong keyboard BIOS - Outdated video adapter BIOS In many cases these problems stem from old standard BIOS which is easily replaced, but in some cases, customer has old "custom" BIOS (manufacturer has included functionality specific to the motherboard on the BIOS). In this case there may be no upgrade path and the motherboard may need to be replaced. For more detailed information on BIOS, see INFO APAR II06082 ************************************ ADAPTER CONFLICT PROBLEMS ************************************ On ISA machines, interrupt conflicts and memory mapping conflicts can cause a variety of problems. 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. Also, Soundblaster boards use INT 7, which conflicts with many printers. Adapters must cooperate in their use of memory and interrupts and must not share address space or interrupts. Callers should be encouraged to check interrupt level settings on their boards. Also try removing cards that are not needed during install. Sometimes you will get a Trap D at 160:FFFxxxxx. ******************************** VIDEO ADAPTER PROBLEMS ******************************** Install problems resulting from video adapter conflicts typically occur on disk 6 or later. This is when the graphical install icons come up, and it is the first place where more complex calls are made to the video BIOS. One notable exception is the Oak video card. Try another video card during install, or try the card in an 8 bit slot during install. Try some different adapter DIP switch settings listed in your adapter manual. Make sure video card is in VGA mode with auto-sense turned off. Some specific problems: If you have a super VGA adapter, install should always be done as VGA. If you have an ATI Ultra, Vantage, or other 8514/A hardware compatible ada ter, use 8514/A driver for install. C0000005 is displayed on the screen during install (e.g. Western digital PVGA1D) - need fixed version of BVHSVGA.DLL Hang on Disk1 right after LOGO screen caused by OAK video card BIOS problem. Workaround is to patch loader file - see Install Adapter APAR video card is in VGA mode with auto-sense turned off. White screen after installation with no system activity - Try setting the video card to 8 bits and moving the video card to an 8-bit slot, also disable the auto-switching capability of the card if possible. Out of Synch/Install problems - caused by problems addressing card in 16-bit mode, switch to 8 bit mode (using jumpers or dip switches on board) and put in 8 bit slot. Install Adapter APAR Some super VGA cards have ROMs with conflicting addresses for some hard disks. ************** OTHER PROBLEMS ************** Failures very early on install disk (especially Zeos notebooks) - try applying patch to sysinstx.com in Install Other APAR Dual Boot feature does not allow boot back to OS/2 from DOS - there may be a disk cacheing utility or a TSR which blocks this.