Mega Top 1

home *** CD-ROM | disk | FTP | other *** search

/ Mega Top 1 / os2_top1.zip / os2_top1 / INFO / FAQS / OS2FAX2 / OSINTIPS.FAX < prev next >

Wrap

Text File | 1994-08-13 | 52.3 KB | 1,182 lines

OSINTIPS.FAX OS/2 INSTALLATION TIPS AND INFORMATION ====================================== This section includes answers to the most frequently asked technical support questions about the installation of OS/2. Q1. I'm planning to install OS/2 on my system, how much space will it require on my hard drive? A1. It is recommended that you allow anywhere from 40 to 65 Megabytes for the OS/2 operating system. 65 Megabytes allows for all options to be installed, including Multimedia, and leaves enough room on your hard drive for a large swap file. For adequate system performance, at least 8 Megabytes of system RAM is recommended. OS/2 will run in 4 Megs, but all RAM shadowing must be turned off. You can turn off RAM shading using your BIOS setup procedure. Also, although not required, many analysts recommend that you maintain the operating system in its own partition and keep your data files and applications in a separate partition. This allows you to update the operating system partition without affecting your personal data. Q2. I would like to use OS/2 on the same system with DOS/Windows. I know I can configure my system to boot up with either operating system, but should I use the "dual boot" method or "Boot Manager"? A2. You should use Boot Manager. It is not advisable to install Windows and WIN-OS/2 in the same partition on your hard drive. Boot Manager will force you to install OS/2 and DOS in separate partitions. Q3. While I was installing OS/2, I received a TRAP 0 0 0 2 error message. What does this message mean? A3. A TRAP-2 is a hardware error. It usually relates directly to memory. Mismatched memory chips often cause TRAP-2 errors. If you have a variety of memory chips on your mother board, from a variety of manufacturers or with various memory access speeds, you will get a TRAP-2 while installing OS/2. If you have checked your memory hardware, and the problem persists, ensure that your system BIOS is of a recent date - 1991 or later, 1992 is recommended. Contact the manufacturer of your system BIOS for the latest version. ================================================= ADDITIONAL OS/2 INSTALLATION TIPS AND INFORMATION ================================================= The following list explains various reported solutions on on installing 2.1. Please review the "Installation Guide" and the README.INS file located on DISKETTE 3 prior to installing 2.1. There is a wealth of information on configuration and installation troubleshooting. If after reviewing the documentation you find that a specific hardware device in your configuration is not supported, it is recommended that you contact the supplier or manufacturer to see if they supply the device specific driver. =============================================================================== How much space is required for OS/2? =============================================================================== We usually recommend that customers allow anywhere from 40-60 Megabytes for the OS/2 system. 60 Megabytes allows for all options to be installed, including Multimedia, and leaves enough room for a good size swap file. =============================================================================== I want to use OS/2 with my existing DOS/Windows system. Should I use "dual boot" or "boot manager?" =============================================================================== It is not advisable to use Windows and WIN-OS2 in the same partition on your hard drive. Because of this, we recommend that you use BOOT MANAGER. =============================================================================== How should I set up boot manager? =============================================================================== Boot Manager has some specific requirements which should be kept in mind. The BOOT MANAGER partition must be placed on the FIRST PHYSICAL DRIVE in order to work correctly. Once this is done, and partition which would contain an operating system should be added in the BOOT MANAGER MENU. Also, if installing OS/2, the OS/2 partition must be SET INSTALLABLE. Boot manager can be configured additionally; such information is found in your Installation Guide. =============================================================================== My swap file has no more room to grow. How can I correct this? =============================================================================== Space needs to be left on the hard drive to allow the swap file to grow. If enough space is not left, and the swap file reaches its "threshold" limit, OS/2 will return an error. If this occurs, you should remove any unnecessary data from the drive, leaving more space for the swap file. If this is not an option, you can delete the swap file as a temporary solution. To do this, shut down the system and reboot with the Installation Diskette in the A: drive. When prompted, insert Diskette 1 and continue. When the screen "Welcome to OS/2" appears, press ESC to cancel the installation. This will give you an A:>] prompt. Then change to the \OS2\SYSTEM directory and delete the file SWAPPER.DAT. This is your swap file, and will be recreated when the system is rebooted. Remember, this is a TEMPORARY FIX, and will occur again as the swap file begins to grow. =============================================================================== Can I use DISK COMPRESSION with OS/2? =============================================================================== To date, the only supported DISK COMPRESSION utility is Stacker for OS/2. No others will work with OS/2, and will corrupt the drive and operating system. =============================================================================== Should I use any of the "Advanced Options" during installation? =============================================================================== NO. These are all options which can be performed after the installation had completed, and it is recommended not to do any of these. On some systems, these options can cause the system to hang or even corrupt itself. =============================================================================== What is the difference between the "blue" and "salmon" diskettes? =============================================================================== Nothing, as far as the software is concerned. The diskettes are grouped by color according to the amount of compression used to create the diskettes. The "salmon" diskettes are compressed tighter than the "blue" diskettes, and therefore the installation software does not require as many disks. PLEASE NOTE that the system remains aware of which diskettes were used to install the system. If "blue" disks were used to install OS/2, then a Selective Install using the "salmon" disks will not work. It will ask for diskettes based on the structure of the "blue" disks. Also keep in mind that the CD-ROM falls under this category as well. =============================================================================== I have the 3.5" diskettes, and my A: drive is a 5.25" drive. How can I install? =============================================================================== You can either access the IBM National Support Center BBS at (919) 517-0001 and download a "redirection fix" which will allow you to install from the B: drive, or you can physically change the drives in your system and CMOS settings. If you need the fix, there are two of them (one for "blue" disks, the other for "salmon"). They are named INST21L.ZIP (for the "blue"), and INST21M.ZIP (for the "salmon"). =============================================================================== Can DOS access a HPFS drive? =============================================================================== NO. DOS was designed to work only with the FAT file system. =============================================================================== Can HPFS files be transferred to a FAT file system? =============================================================================== YES. The file system simply refers to how the drive reads and writes data. If you copy a file from a HPFS drive to a FAT drive, it will automatically convert the file for use with the new file system, and vice versa. Just keep in mind that the FAT file system cannot interpret 256-character file names. =============================================================================== How can I run CHKDSK /F on my drive under OS/2? =============================================================================== Running CHKDSK /F under OS/2 is not quite as easy as DOS. Since OS/2 is multi-tasking, it is always accessing the hard drive, making it impossible to stop the drive and make corrections. Because of this, CHKDSK has to be run from the floppy drive after rebooting the machine. Shut down the desktop and reboot with the Installation Diskette in the A: drive. When prompted, insert Diskette 1 and continue. When "Welcome to OS/2" is displayed, press ESC to cancel the installation, and this will return an A:\>] prompt. From there, insert Diskette 2 and type CHKDSK x:/F (where x: is the drive you wish to check). =============================================================================== How can I set up Dual Boot after OS/2 is installed? =============================================================================== Normally, Dual Boot is an automatically installed feature if DOS already exists on the partition. However, a utility is available which will allow you to install the Dual Boot option after installing OS/2. This utility is call DBPREP.ZIP, and is on the IBM National Support Center BBS at (919) 517-0001. =============================================================================== How do I access the IBM National Support Center BBS? =============================================================================== Using a communications application and a 2400 or higher baud modem, dial the PCCBBS number at (919) 517-0001. Once connected, the system will ask you for your name, and then begin to register you as a BBS user. If it asks you right away for a password, then someone else may already be registered under the same name. The registration is fairly straightforward, as is the BBS interface. It is all menu driven, and will list any available choices at all times. If you have difficulty navigating through the BBS, you can choose the on-line help at any time. =============================================================================== What CD-ROM Drives and removable media are supported under OS/2? =============================================================================== OS/2 only supports SCSI compatible CD-ROM Drives in most cases. For some other devices, the manufacturer may supply device drivers to allow OS/2 to use this device. For further assistance, all of the tested CD-ROM drives are listed in the OS/2: Using the Operating Manual on page 362. If you need further assistance beyond the scope of this document, you can refer to the OS/2 Installation Guide and User's Guide, or to the README.INS on diskette 3 of the installation set. If you have the CD-ROM, this file will be in the subdirectory \OS2SE21\DISK_2. If after checking these resources you find you still can't answer your question, it is recommended to call your hardware manufacturer of the CDROM. =============================================================================== Hanging During INSTALL =============================================================================== In what way does the system hang? Loading please wait on diskette 1. Try the AT-Bus Workaround (IBM 1S506.ADD). Request the fax on AT-Bus Workaround from 1-800-992-4777. Hanging after first reboot (disk 5). Does the screen appear to have video problems? Yes. Do You have an ATI Graphics Ultra Video Adapter? Yes. You need to configure the adapter for proper refresh rates to work with OS/2. Request the Fax on MACH 32 setup utilities from 1-800-992-4777 . No. Try the response file installation. See RESPONSE FILE part of this fax. Hanging on disk 13/17 (end of install). Try the SETVGA Workaround. Fax on SETVGA. =============================================================================== SYS0318: Message file oso001.msg not found. System does not recognize the CD-ROM player for installation. =============================================================================== What brand and model SCSI interface are you using for the CD-ROM? Creative Labs Sound Blaster card. You need to obtain device drivers to use the SCSI interface on the Sound Blaster Card. Request Fax on MULTIMEDIA CD-ROM KITS (MMCDROM) from 1-800-992-4777. Media Vision Pro Audio Spectrum card. You need to obtain device drivers to use the SCSI interface on the Pro Audio Spectrum Card. Request Fax on MULTIMEDIA CD-ROM KITS (MMCDROM). Trantor SCSI card (usually bundled with NEC CD-ROM players) You need to obtain device drivers to use the trantor SCSI interface. Contact the manufacturer for the proper drivers. Do not have a SCSI interface. It is an ISA CD-ROM. What brand and model CD-ROM are you using? Sony CDU-31A CD-ROM You need to obtain device drivers from the IBM NSC BBS at (919) 517-0001. Request the fax on SONY31A from Service. IBM ISA CD-ROM You need to obtain device drivers from the IBM NSC BBS at (919) 517-0001. Request ISA CDROM Fax from Service. Mitsumi CD-ROM You need to obtain device drivers for your CD-ROM. These are available from third party vendors. Request fax on MITSUMI CDROM. =============================================================================== Trap During INSTALL =============================================================================== What kind of TRAP message do you get? Trap 0002. Trap 0002 is a HARDWARE ERROR. It usually relates directly to memory. If your memory is mismatched (chips are dissimilar), you will get this error. Please check your memory configuration and check to see if your BIOS is of a recent date (1991 or higher, 1992 recommended). =============================================================================== Configuration Problems =============================================================================== My 3.5" floppy drive is actually my B: drive, and I have the 3.5" diskettes. What color are the labels on these diskettes? Blue. You need to download a redirection fix from the IBM NSC BBS at (919) 517-0001. The file name is INST21L.ZIP. This will allow you to install from the B: drive. Salmon (pink). You need to download a redirection fix from the IBM NSC BBS at (919) 517-0001. The file name is INST21M.ZIP. This will allow you to install from the B: drive. ================================================================== SYS02025 AND SYS02027 ON NON IBM MACHINES WITH AMI BIOS ON DISKETTE #1 ================================================================== DESCRIPTION OF SYMPTOMS: During installation of OS/2 2.0 on OEM (Other Equipment Manufacturers) machines with AMI BIOS, the system will display two SYS error messages 02025 and 02027 after inserting Disk 1. SUMMARY OF RESOLUTION: 1. Make sure disk 1 is not bad. 2. Check the AMI BIOS date and Keyboard Controller Chip version. The date should be 5/9/91 and Controller Chip version should be F. 3. Ensure that there is not a hardware problem with the Floppy Controller or Floppy Drive. DETAILS OF RESOLUTION: 1. Try booting with the Disks on another machine that is already running OS/2 2.0. 2. Machine must have BIOS dated 5/9/91 and keyboard controller chip version KF. The following information will be seen by the user at (cold)boot time: AMI BIOS and AMI BIOS Plus: aaaa-bbbb-mmddyy-Kc AMI Hi-Flex BIOS: ee-ffff-bbbbbb-gggggggg-mmddyy-hhhhhhhh-c If an IDE hard drive is in the system, "mmddyy" should be 040990 or later. For other drives including MFM, RLL, ESDI, or SCSI, "mmddyy" should be 092588 or later. Controller chip version can be located on the bottom of that same screen. Check the last digit in the long stream of digits (the "c" above). The last digit will probably be either be 8, B, D, or F. The required level should be F for OS/2 v2.0 or v1.3. Pressing the INS key during bootup should cause this info to stay on the screen. If they are not up to date Call Washburn & Co. to order a new version. 3. If the above two steps do not solve the problem have some hardware diagnostics performed on the Floppy Controller and Floppy Drive. ============================================================= SYS 2025 & 2027 on the Installation ============================================================= Getting sys02025 and sys02027 on the install diskette. Check if customer swapped their floppy drives without updating their cmos. Setting the cmos correctly allowed them to install without getting the sys02025 and sys02027. This is different from 2.0 where it allowed you to install and then asked for a nonexistent diskette 16 at the end. ========================================================================= SYS02025 and SYS02027 on OEM with PHOENIX bios 1.03 on OS/2 2.1 Install Diskette. ======================================================================== Work around: 1) Make backup copy of OS/2 2.1 Install diskette. 2) Del OS2LDR /* from backup diskette */ Del OS2BOOT /* from backup diskette */ 3) Copy OS2LDR /* from original to backup */ Copy OS2BOOT /* from original to backup */ The SYS02025 and SYS02027 errors have also been found when the user swaps the floppy drive cables without updating CMOS. Updating CMOS corrects the problem (3.5 and 5.25 cable swap). Note that there is a tool available on the Raleigh BBS and Compuserve that allows you to install OS/2 2.X from the B drive, when the B drive is 3.5 and and A drive is 5.25 and the diskettes are 3.5. This utility is called INST21L (if you have blue labels on your disks) or INST21M (if you have salmon label on your disks). ================================================================== AFTER INSTALL BLANK DESKTOP AND NO SYSTEM ACTIVITY ================================================================== DESCRIPTION OF SYMPTOMS: After Installation and reboot the user gets a blank desktop with no system activity SUMMARY OF RESOLUTIONS: 1. If Using an ATI Ultra, or Ultra Graphics. a. Ensure the ATI board is setup as an 8514 PRIMARY display. b. Check the CONFIG.SYS for DEVICE=C:\OS2\MDOS\VSVGA.SYS c. Contact ATI for updated ROM chip. 2. Run chkdsk 3. Check CONFIG.SYS for duplicate SET USER_INI, and SET SYSTEM_INI statements. 4. Set video card to 8 bits and move it to an 8 bit slot. 5. If the above is not applicable or does not work, remake the desktop. DETAILS OF RESOLUTION: 1. The ATI 8514 Ultra, or Ultra Graphics. a. These boards MUST be set up as an 8514 PRIMARY display b. The correct DEVICE statement in the CONFIG.SYS should read DEVICE=X:\OS2\MDOS\VSVGA.SYS It will sometimes install as VVGA.SYS This must be changed. c. The older ATI ROM chips return the incorrect monitor ID when queried by OS/2. 2. Run Chkdsk a. Insert the Installation disk in drive A. b. Turn on the computer; if already on execute a proper shutdown and when prompted press Ctrl+Alt+Del. c. When prompted insert disk 1 and press enter. d. When the welcome to OS/2 screen is displayed hit the esc key to cancel and an A: prompt will appear. e. Insert disk2 and type chkdsk c: /f and press enter. f. If errors are displayed rerun the command until no errors are found. g. Run this command on all drive letters that exist. 3. Check the OS/2 CONFIG.SYS for duplicate INI statements. a. Boot from DOS or a DOS BOOTABLE DISKETTE. b. Open an editor session. c. Open the CONFIG.SYS. d. Locate the SET USER_INI, and SET SYSTEM_INI statements. e. Scroll through the CONFIG.SYS and make sure they are not repeated. If they are delete the second occurrence. f. Save any changes and exit the editor. 4. Set the Video card to 8 bit mode and place in an 8 bit slot. Consult the documentation that came with the card on the procedure to do this. 5. Remake the desktop. a. Restart the computer using the OS/2 Installation Diskette, then when prompted insert Diskette 1. b. When the Welcome To OS/2 screen appears press the Esc key to cancel the installation. c. At the A:> prompt type C: then press enter. d. Type CD \OS2 the press enter. e. Type ERASE OS2.INI then press enter. f. Type MAKEINI OS2.INI INI.RC then press enter. g. Type ERASE OS2SYS.INI then press enter. h. Type MAKEINI OS2SYS.INI INISYS.RC then press enter. i. Delete the hidden file WP ROOT. SF in the startable partition. 1) For FAT file systems i. Type ATTRIB -S -H WP?ROOT.?SF then press enter ii. Type DEL WP?ROOT.?SF then press enter 2) For HPFS file systems i. Type ATTRIB -S -H "WP ROOT. SF" press enter ii. Type DEL "WP ROOT. SF" then press enter j. Delete the desktop 1) For FAT CD to OS!2_2.0_D and delete this directory and all subdirectories under it. 2) For HPFS CD to "OS!2 2.0 DESKTOP" and delete this directory and all subdirectories under it. NOTE: If MAKEINI has been run before, or ALT-F1 was used, other desktops may have been created. Delete ALL desktops. (e.g. OS!2_21.0_D is another desktop.) ======================================================================= Hang with White screen after installation with no system activity: ====================================================================== * There is a fix available on Compuserve and the Raleigh BBS (919) 517-0001 for the following problems in a file called 21WPSF.ZIP. 1) White desktop after installing OS/2 2.1 over another version of OS/2. 2) "shutdown complete" message is displayed underneath the "shutting down please wait" message. 3) Mass duplication of template objects after creating a shadow. If you have the white desktop with the environment noted above it is recommended to get the 21WPSF.ZIP fix from Compuserve or the BBS. If however you do not have access to a modem the following workarounds have had a high success rate. 1) Do CHKDSK x: /f (for FAT ) CHKDSK x: /f:3 (for HPFS) on OS/2 Partition from OS/2 Installation diskettes. See Page 137 in the "Installation Guide for instructions on on how to running CHKDSK. 2) Check the OS/2 CONFIG.SYS file on the root directory for the following 2 statements. If you have more than one set of these two statements, REM out the first set in the config.sys file. SET USER_INI=C:\OS2\xxxxx.INI SET SYSTEM_INI=C:\OS2\xxxxxx.INI If you do have two sets, EDIT the CONFIG.SYS with any EDITOR by either copying the file to a diskette and editing on another machine or boot up with a DOS diskette and Run EDIT or EDLIN to "REM" out the duplicate set of SETUSER and SETSYSTEM lines. (e.g. REM USER_INI=C:\OS2\xxxxx.INI) ================================================================= INSTALLATION HANGS ON DISK 1 ================================================================= DESCRIPTION OF SYMPTOMS: Installation hangs on disk 1 of the installation process with the loading please wait message showing. SUMMARY OF RESOLUTION: Turn off disk caching, asynchronous memory refresh capabilities, turbo and shadowing, during the installation. These can be turned back on after a successful install. DETAILS OF RESOLUTION: The disk caching,async memory refreshes, and shadowing are enabled and disabled in the CMOS setup of the BIOS. The turbo is sometimes put on a switch on the casing of the computer or can also be set from the CMOS. Enter the setup utility and make the appropriate changes; consult the documentation that came with the computer on how to enter and change the setup. ================================================================== HANG ON DISK 1 OF INSTALLATION; WILL NOT DRAW THE OS/2 LOGO SCREEN ================================================================== DESCRIPTION OF SYMPTOMS: On systems that have video cards with a Western Digital Chipset, the installation will hang on disk 1 before the OS/2 logos are displayed. SUMMARY OF RESOLUTION: Video card may be set for a non-standard VGA mode, or autosense capability on the card is turned on. DETAILS OF RESOLUTION: 1. Make sure video card is in VGA mode with auto-sense turned off. 2. Try setting the video card to 8 bits and moving the video card to an 8-bit slot . ================================================================== HANG ON DISK 1 WHILE INSTALLING OS/2 2.1 ON A SYSTEM WITH A QUANTUM HARD CARD ================================================================== DESCRIPTION OF SYMPTOMS: While installing OS/2 2.1 on a system with a Quantum Hard Card the installation process will hang on Disk #1. SUMMARY OF RESOLUTION: 1. Modify the CONFIG.SYS on Diskette #1 of the OS/2 installation diskettes and add the default settings for the Quantum hard card to the BASEDEV=IBM1S506.ADD line. 2. The line should read as follows after editing. BASEDEV=IBM1S506.ADD /A:1 /IRQ:11 DETAILS OF RESOLUTION: 1. Make a Backup copy of Diskette #1 and use the copy for the following steps. 2. Boot the system with DOS or a DOS bootable diskette. 3. Insert the copy of Diskette #1 in Drive A: 4. Edit the CONFIG.SYS on the copy of Diskette #1. 5. Locate the BASEDEV=IBM1S506.ADD line. 6. Add /A:1 /IRQ:11 to the end of the line. 7. The edited line should now look like BASEDEV=IBM1S506.ADD /A:1 /IRQ:11 8. Save the changes and remove the diskette from Drive A: 9. Begin installation of OS/2 2.1 using the copy of Diskette #1 when asked to insert Diskette #1. ================================================================== INSTALLATION OF OS/2 2.1 HANGS ON THE INSTALLATION DISKETTE OR DISK 1 DURING INSTALL ON A MOD 8580 ================================================================== DESCRIPTION OF SYMPTOMS: OS/2 V2.1 hangs on Disk #1 or Installation Disk on MOD 8580. SUMMARY OF RESOLUTION: Copy the packed file BUNDLE on Disk 1 to another location on the diskette. DETAILS OF RESOLUTION: 1. If you have two diskette drives a. Insert a DOS bootable diskette in drive A and start the computer (if the computer is already running, you can restart it by pressing Ctrl+Alt+Del). b. Place a blank diskette in drive B. This diskette will become the replacement OS/2 diskette #1. c. At the DOS A> prompt, type: FORMAT B: /v (then press enter) e. When asked for a volume label type: DISK 1 (then press enter) f. When asked if you want to format another, type: N (then press enter) g. Remove the replacement OS/2 diskette #1 from drive B h. Insert the original OS/2 diskette #1 into drive B i. At the DOS A> prompt, type: XCOPY B: A: /p J. At the first (Y/N)? prompt, remove the DOS diskette from drive A and place the replacement OS/2 diskette #1 in drive A K. At the B:BUNDLE(Y/N)? prompt, type: N (then press enter) L. For all other (Y/N)? prompts, type: Y (then press enter) M. When the DOS A> prompt appears, type COPY B:BUNDLE A: (then press enter) 2. If you have one diskette drive a. Insert a DOS bootable diskette in the diskette drive and start the computer (if the computer is already running, you can restart it by pressing Ctrl+Alt+Del). b. At the DOS A> prompt, type: FORMAT B: /v (then press enter) c. When prompted, place a blank diskette in the diskette drive. This diskette will become the replacement OS/2 diskette #1. d. When asked for a volume label type: DISK 1 (then press enter) e. When asked if you want to format another, type: N (then press enter) f. When prompted to insert diskette for drive A, remove the replacement OS/2 diskette #1 from the diskette drive and place the DOS diskette in the diskette drive g. At the DOS A> prompt, type: DISKCOPY A: B: (then press enter) When prompted to insert SOURCE diskette in drive A:, place the original OS/2 diskette #1 in the diskette drive When prompted to insert TARGET diskette in drive B:, place a blank diskette in the diskette drive. This diskette will become the temporary copy of diskette #1 h. When asked if you want to copy another diskette, type N (then press enter) i. When prompted to insert disk with command.com in drive A, place the DOS diskette in the diskette drive. k. At the DOS A> prompt, type: ERASE B:BUNDLE (then press enter) When prompted to insert diskette for drive B:, place the temporary copy of diskette #1 in the diskette drive. When prompted to insert diskette for drive A:, place the DOS diskette in the diskette drive. l. At the DOS A> prompt, type: XCOPY B: A: (then press enter) When prompted to insert diskette for drive B:, place the temporary copy of diskette #1 in the diskette drive When prompted to insert diskette for drive A:, place the replacement OS/2 diskette #1 in the diskette drive m. When prompted to insert disk with command.com in drive A, place the DOS diskette in the diskette drive. n. When the DOS A> prompt appears, type XCOPY B:BUNDLE A: When prompted to insert diskette for drive B:, place the original OS/2 diskette #1 in the diskette drive When prompted to insert diskette for drive A:, place the replacement OS/2 diskette #1 in the diskette drive ================================================================== DURING INSTALLATION OF OS/2 2.1 THE FLOPPY DRIVE WILL BEGIN TO RAPIDLY SEEK BACK AND FORTH THEN GIVE A DISK READ ERROR MESSAGE ON DISK 1 ================================================================== DESCRIPTION OF SYMPTOMS: 1. At disk1 after the logo shows up, the floppy drive starts seeking rapidly back and forth, the screen clears and "A disk read error has occured. Restart the system." message appears. 2. This is known to happen on systems with AOX, HYPER ACE, and XTEND processor upgrade cards. SUMMARY OF RESOLUTION: 1. The cause of this error is a file on disk 1 called BUNDLE, size 344132. 2. Moving the position where this file resides on the disk 1 is known to fix the problem. DETAILS OF RESOLUTION: 1. Insert a DOS bootable diskette in the diskette drive and start the computer (if the computer is already running, you can restart it by pressing Ctrl+Alt+Del). 2. At the DOS A> prompt, type: FORMAT B: /v (then press enter) 3. When prompted, place a blank diskette in the diskette drive. This diskette will become the replacement OS/2 diskette #1. 4. When asked for a volume label type: DISK 1 (then press enter) 5. When asked if you want to format another, type: N (then press enter) 6. When prompted to insert diskette for drive A, remove the replacement OS/2 diskette #1 from the diskette drive and place the DOS diskette in the diskette drive 7. At the DOS A> prompt, type: DISKCOPY A: B: (then press enter) When prompted to insert SOURCE diskette in drive A:, place the original OS/2 diskette #1 in the diskette drive When prompted to insert TARGET diskette in drive B:, place a blank diskette in the diskette drive. This diskette will become the temporary copy of diskette #1 8. When asked if you want to copy another diskette, type N (then press enter) 9. When prompted to insert disk with command.com in drive A, place the DOS diskette in the diskette drive. 10. At the DOS A> prompt, type: ERASE B:BUNDLE (then press enter) When prompted to insert diskette for drive B:, place the temporary copy of diskette #1 in the diskette drive. When prompted to insert diskette for drive A:, place the DOS diskette in the diskette drive. 11. At the DOS A> prompt, type: XCOPY B: A: (then press enter) When prompted to insert diskette for drive B:, place the temporary copy of diskette #1 in the diskette drive When prompted to insert diskette for drive A:, place the replacement OS/2 diskette #1 in the diskette drive 12. When prompted to insert disk with command.com in drive A, place the DOS diskette in the diskette drive. 13. When the DOS A> prompt appears, type XCOPY B:BUNDLE A: When prompted to insert diskette for drive B:, place the original OS/2 diskette #1 in the diskette drive When prompted to insert diskette for drive A:, place the replacement OS/2 diskette #1 in the diskette drive ================================================================== IPE AT 0F00:7275 ON DISK 1 OF OS/2 2.1 INSTALL OR IPE AT 0F00:76A1 ON DISK 1 OF OS/2 2.0 INSTALL ON ROM LOADABLE MACHINES ================================================================== DESCRIPTION OF SYMPTOMS: 1. When trying to install OS/2 2.0 GA the installation program hangs on Install Disk 1 with an Internal Processing Error at ## 0F00 : 76A1 60000, 6000 Internal Revision 6.307 2. When trying to install OS/2 2.1 GA the installation program hangs on Install Disk 1 with an (Only in thinkpad 700C installing from cdrom attached to Docking Station.) Internal Processing Error at ## 0F00 : 7275 60000, 6000 Internal Revision 6.427 This error could be the same for machines that are currently running a. OS/2 2.0's preload code b. OS/2 2.0's 10/92 Service Pak I c. OS/2 2.1 but are missing the necessary ABIOS files; NOTE Also that it is NOT recommended to install OS/2 2.1 on top of an beta version of OS/2 2.1. 3. Occurs on a ROM loadable machine such as an IBM Model 9556 or 9557. SUMMARY OF RESOLUTION: Copy the .BIO file from the Reference Disk onto copies of the Installation Disk and Disk 1 then update the ABIOS.SYS files on these disks and use the copies for the install. This is known as the ABIOS workaround. DETAILS OF RESOLUTION: 1. Using DISKCOPY command make backup diskettes for OS/2 2.0 Installation Disk and Disk 1. It is very important that these backups are used for rest of the procedure. 2. Locate a file xxxx.BIO on the reference disk of your PS/2 or PS/VALUEPOINT. (If you don't have the reference disk then follow instructions that came with the machine to create one). 3. Copy this xxxx.BIO to INSTALL and DISK_1 diskettes. 4. Using a plain text editor, edit the file ABIOS.SYS on the INSTALL diskette and add a line, stating the name of the xxxx.BIO as in step 3, to the FIRST LINE of the file. Make sure that you you use the same format as used for other lines in this file. 5. Copy this modified ABIOS.SYS to the DISK_1. 6. Using these two modified disks the installation will continue beyond Disk 1. 7. This procedure is the same for OS/2 2.0 and OS/2 2.1. ================================================================== TRAP D ON DISK #1 DURING INSTALLATION OF OS/2 2.1 ON A COMPAQ 386/33I DESKPRO ================================================================== DESCRIPTION OF SYMPTOMS: Trap 000D on Disk 1 during install of OS/2 2.1 on a Compaq 386/33I Deskpro. CS:EIP=0538:00003823. SUMMARY OF RESOLUTION: 1. Make a copy of Disk #1 2. Using this copy and an editor, edit the CONFIG.SYS file on the copy of Disk #1 as follows: REM OUT: BASEDEV=IBM2M57.ADD BASEDEV=IBM2SCSI.ADD 3. Use the edited copy of Disk #1 to install. ================================================================== During the installation of OS/2 2.1 the process hangs after the first reboot, (DISK #5). ================================================================== SUMMARY OF RESOLUTION: Workaround is to reinstall OS/2 2.1 using a Response file. DETAILS OF RESOLUTION: WARNING: All installation selections must be made in the Response file BEFORE the installation begins. 1. Copying the Response file to Diskette #1. a. To copy the response file onto a diskette, you must make some modifications to Diskette 1. These modifications make room on the diskette for the response file. b. Make a copy of Diskette #1. You will modify the copy.(Ex. DISKCOPY A: B:) c. Make extra room on the copy of Diskette #1 by deleting files that will not be needed in a response file installation: 1) Delete the MOUSE.SYS file from the copy of Diskette 1. 2) Delete the SYSINST2.EXE file from the copy of Diskette #1. 3) Delete the BUNDLE file from the copy of Diskette #1. 4) If you are installing OS/2 2.1 on a Micro Channel(*) computer, delete the following file from your copy of Diskette #1: DEL IBM1*.ADD 5) If you are installing OS/2 2.1 on a non-Micro Channel computer, delete the following files from your copy of Diskette #1: DEL IBM2*.ADD DEL *02.SYS d. Edit the CONFIG.SYS file that exists on the copy of Diskette #1. 1) Change the SET OS2_SHELL statement from: SET OS2_SHELL=SYSINST2.EXE to: SET OS2_SHELL=RSPINST.EXE A:\OS2SE21.RSP 2) Delete the following statement: DEVICE=\MOUSE.SYS 3) If you are installing OS/2 2.1 on a Micro Channel computer, delete the following statements from the CONFIG.SYS file on your copy of Diskette #1: BASEDEV=IBM1FLPY.ADD BASEDEV=IBM1S506.ADD 4) If you are installing OS/2 2.1 on a non-Micro Channel computer, delete the following statements from the CONFIG.SYS file on your copy of Diskette #1: BASEDEV=IBM2FLPY.ADD BASEDEV=IBM2ADSK.ADD BASEDEV=IBM2SCSI.ADD e. Unpack the SAMPLE.RSP from disk#13, This file is in directory REQUIRED. UNPACK A:REQUIRED /N:SAMPLE.RSP) to the copy of diskette #1. f. Use an editor (such as the System Editor) to modify and save the file. The file contains comments that explain each of the installation options.(Default setting has worked fine in all cases) g. Copy the modified response file to the copy you made of Diskette #1. Use the name OS2SE21.RSP when you copy the file. EX. COPY SAMPLE.RSP A:OS2SE21.RSP h. Copy the RSPINST.EXE file (located in DISK#7 under directory REQUIRED UNPACK A:REQUIRED /N:RSPINST.EXE) to the copy of Diskette #1. 2. Begin the installation of the workstation by inserting the Installation Diskette and restarting the system. 3. When prompted for Diskette #1, insert the modified copy of Diskette #1, and press Enter. 4. From this point, the installation program will prompt only for the insertion of diskettes. No other installation screens will appear. 5. When prompted to insert Diskette #1 again, insert the original copy of Diskette #1. NOTE: This procedure can be used to install the same set of options on multiple workstations. Using a response file, you can make sure that a group of workstations is set up with the same set of options and HARDWARE ============================================================== MEMORY RELATED 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 =============================================================================== AMI SCSI - slow, noisy disk - ATBUS workaround - get ATBUS FAX =============================================================================== FUTURE DOMAIN 16XX SCSI controller - hang on LOGO screen after reboot following good install - check for interrupt conflict Always Technology SCSI - BIOS upgrade - Bernoulli Boxes - See IOMEGA Support Colorado Memories Tape Drive - fix available from Colorado - PROCOMM+ SCSI disk adapters (Microchannel) - Contact PROCOMM Early versions of IBM 16-bit SCSI adapters - update microcode 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 Quantam Plus Hardcard - need EPROM upgrade - see readme for more info SUMO SCSI adapters - Contact manufacturer ==================================================================== FDISK PROBLEMS ==================================================================== Some common problems: 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) - Request ATBUS Workaround FAX from Service. 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 - SEE BIOS FAX 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 - not supported 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.X 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. Failures very early on install disk (especially Zeos notebooks) - try applying patch to sysinstx.com in Install Request ZEOS Fax from Service. 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. Request DUALBOOT FAX