OS/2 Professional

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

/ OS/2 Professional / OS2PRO194.ISO / os2 / info / faq / os2_21 / install.txt < prev next >

Wrap

Text File | 1994-03-14 | 155.5 KB | 3,698 lines

Table of Contents During the installation of OS/2 2.1, the process hangs after the first reboot, (DISK #5). . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 Cannot install OS/2 2.1 on an EISA system with an Adaptec 1742A controller card.. . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 Before installation of the OS/2 2.1 Upgrade, the line SET DMQSPATH=D:\XGA$DMQS was added to the CONFIG.SYS and the XGA$DMQS directory had been copied from C: to D:. When the Installation migrated the existing CONFIG.SYS the above line was deleted from the CONFIG.SYS and all the DMQS files were copied to the same partition as the base system. . . . . . . . . . . . . . . . . . . . . . . . . 3 Problems installing OS/2 2.1 on system that have a HYPERACE 486 upgrade. 4 TRAP 0002 on Model 8590 OR 8595. . . . . . . . . . . . . . . . 4 Horizontal Black bands across the screen after DISK 5 reboot with the GATEWAY 2000 486/66 local bus and ATI Graphics Ultra Pro . . . . . . 5 Disk Read error has occurred when attempting to boot the Installation Diskette 5 SYS02025 AND SYS02027 on non-IBM Machines with AMI BIOS on Diskette #1.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 AMI Fast Disk and Fast Disk II SCSI adapters are recognized as ADAPTEC Adapters, gives COUNTRY.SYS error message on Boot-Up.. . . . 7 Installation hangs on Disk #1. . . . . . . . . . . . . . . . . 7 Hang on Disk #1 of Installation: Will not draw the OS/2 LOGO screen 8 Hang on Disk #1 while installing OS/2 2.1 on a system with a QUANTUM HARD CARD . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 Slow SCSI support or missing Icons on boot-up. . . . . . . . . 9 Installation of OS/2 2.1 hangs on the Installation Diskette or DISK 1 during install on a MOD 8580. . . . . . . . . . . . . . . . . . . . . . . . 9 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. . . . . 11 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. . . . . 13 TRAP D on Disk #1 during Installation of OS/2 2.1 on a COMPAQ 386/33I DESKPRO. . . . . . . . . . . . . . . . . . . . . . . . . . . 14 After Install, Blank Desktop and No System Activity. . . . . . 14 Installing OS/2 2.1 on a machine with an AOX/KINGSTON upgrade. 16 TRAP 2 OR TRAP 6 at 60000X:9084 during install . . . . . . . . 17 System asks for DISK 16 but there are only 15 disks plus the printer driver disks. . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 TRAP 8 on installation DISK # 1 on MYLEX systems . . . . . . . 18 SYS 0045 during install. . . . . . . . . . . . . . . . . . . . 18 COUNTRY.SYS not found. . . . . . . . . . . . . . . . . . . . . 18 Installing on TI Notebooks (TI4000/30, /40/& 50's.). . . . . . 19 SYS 2025 & 2027 on the installation. . . . . . . . . . . . . . 19 SYS 2025 & 2027 on the installation with PHOENIX BIOS. . . . . 19 AST machine and has added 3rd party memory to it he may encounter an error on install of 2.1, country.sys not found. . . . . . . . . . . . 20 Installation failure on 700C . . . . . . . . . . . . . . . . . 20 There is a potential workaround to the problem of hangs and SYS 3175's during selective installs.. . . . . . . . . . . . . . . . . . . . . 20 Did not select dual boot option when installing OS/2, and now want to add it. Can I do so without having to install DOS and then reinstall all of OS/2? 20 There is a problem installing OS2 2.1 on some PS2 8580, ESDI units. These units will install and run with OS2 2.0 but with 2.1 you cannot get past disk 1 of install set. . . . . . . . . . . . . . . . . . . . . . . . . 21 Installing OS/2 2.1 on a 486 machine. Error msg that states that "the BIOS was not compatible". . . . . . . . . . . . . . . . . . . . . . . 21 Selective Install fails. . . . . . . . . . . . . . . . . . . . 21 Installation failures on Gateway machines. . . . . . . . . . . 22 Enabling CACHE after having to disable CACHE for installation. 22 The 2nd stage of Install asks for Win3.1 disks -- but you have Microsoft Windows on CD ROM. . . . . . . . . . . . . . . . . . . . . . . . . . 22 Installing OS/2 with 4M RAM and UNPACK2.EXE and using CDROM during install. . . . . . . . . . . . . . . . . . . . . . . . . . . 22 Installing on a DPT SCSI Controller, TRAP 0008 . . . . . . . . 23 "SYSTEM CANNOT FIND THE FILE KBD01.SYS" ERROR MESSAGE ON BOOT UP AFTER A SUCCESSFUL INSTALL. . . . . . . . . . . . . . . . 23 Greater then 16 MB in MOD 80 will not install 2.1. . . . . . . 23 Installing OS/2 2.x on top of Lan Server 3.0 with HPFS386. . . 23 Hang with White screen after installation with no system activity: 24 Black Desktop. . . . . . . . . . . . . . . . . . . . . . . . . 26 If ATI 8514 Ultra or Graphics Ultra locks with white screen on bootup. 26 TRAP0002 on IBM 8590, 8595 . . . . . . . . . . . . . . . . . . 26 SYS02025 and SYS02027 on OEM with PHOENIX bios 1.03 on OS/2 2.1 Install Diskette.. . . . . . . . . . . . . . . . . . . . . . . . . . 27 SYS1201 boot error during (or after) installation of OS/2 2.1. 27 ISA bus workaround for installation problems on AT (ISA) BUS machines 29 IBM Premier Abios Systems Installation . . . . . . . . . . . . 31 Information on INSTALL BIOS PROBLEMS . . . . . . . . . . . . . 32 SOME BIOS COMPATIBILITY INFO . . . . . . . . . . . . . . . . . 33 Adapter: All Adaptec adapters . . . . . . . . . . . . . . . . 35 Adapter: Adaptec AHA-154x . . . . . . . . . . . . . . . . . . 35 Adapter: Adaptec AHA-174x . . . . . . . . . . . . . . . . . . 35 Adapter: Future Domain TMC-850/860/875/885 w/BIOS revision level 7.0. Future Domain TMC-1660/1670/1680 w/BIOS revision level 2.0. . . . . 35 Adapter: AMI SCSI Adapters. . . . . . . . . . . . . . . . . . 35 Adapter: Bernoulli Boxes. . . . . . . . . . . . . . . . . . . 36 Adapter: MC Enabler SCSI Host adapter . . . . . . . . . . . . 36 Adapter: IBM 16-bit SCSI cards (early versions) . . . . . . . 36 Slow hard drive speed and possibly no icons appearing. Other data corruption possible.. . . . . . . . . . . . . . . . . . . . . . . . . . 36 Installing OS/2 2.X on a PC using the Always IN-2000 SCSI Host adapter? 36 Known problems involving an AOX add-in processor card in a Micro Channel PS/2?. . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 Installing OS/2 2.0 on a L40, and getting CRC errors and the installation locks up. Tried several sets of diskettes with the same results. . . . 37 Installing OS/2 2.0 on a P70, and getting CRC errors and the installation locks up. Tried several sets of diskettes with the same results. . . . 37 Getting a C000005 error during installation and can't continue. 37 System is hanging during installation (or bootup). . . . . . . 37 Known INSTALL problems with AMI BIOS . . . . . . . . . . . . . 38 Installing with ATI VIDEO ADAPTERS . . . . . . . . . . . . . . 39 CDROM install with Sony 31A. . . . . . . . . . . . . . . . . . 40 CDROM install with Mitsumi . . . . . . . . . . . . . . . . . . 41 Non Supported CDROM Information. . . . . . . . . . . . . . . . 41 Installation of Super VGA display drivers. . . . . . . . . . . 42 Diamond Speedstar Adapter. . . . . . . . . . . . . . . . . . . 43 Diamond Stealth adapter. . . . . . . . . . . . . . . . . . . . 43 Diamond Speedstar 24X Card Configuration . . . . . . . . . . . 43 Country.Sys not found message on all Gateway Nomad "notebook" models. 44 Gateway machines with a 486 can potential have DIVIDE UNDERFLOW errors. 44 Gateway machines that Trap 2 on boot or install. . . . . . . . 45 Common Symptom: Trap 2, Trap 6 or other Trap at 60000x:9084. . 45 Cache problems.. . . . . . . . . . . . . . . . . . . . . . . . 45 SCSI install problems. . . . . . . . . . . . . . . . . . . . . 46 AMI SCSI - slow, noisy diskduring install. . . . . . . . . . . 46 FUTURE DOMAIN 16XX SCSI controller - hang on LOGO screen after reboot following good install . . . . . . . . . . . . . . . . . . . 46 Always Technology SCSI . . . . . . . . . . . . . . . . . . . . 46 Colorado Memories Tape Drive attached during install.. . . . . 46 PROCOMM+ SCSI disk adapters (Microchannel) . . . . . . . . . . 47 Early versions of IBM 16-bit SCSI adapters . . . . . . . . . . 47 Unable to install to removable media support - Bernoulli (IOMEGA), and SyQuest. . . . . . . . . . . . . . . . . . . . . . . . . . . 47 All Adaptec adapters . . . . . . . . . . . . . . . . . . . . . 47 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).. . . . . . . . . . . . . . . . . . . . . . . . . 47 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. . . . . . . 48 AMI "Fast Disk" and AMI "Fast Disk II" SCSI adapters are incorrectly recognized as Adaptec adapters. . . . . . . . . . . . . . . . . . . . . 48 Always IN2000 SCSI adapter - causes Internal Processing Error. 48 Quantam Plus Hardcard Attached . . . . . . . . . . . . . . . . 48 SUMO SCSI adapters don't seem to work with OS/2. . . . . . . . 48 FDISK problems during INSTALL. . . . . . . . . . . . . . . . . 48 Trying to install over a Beta version of OS/2 2.0 (1.3 is OK) fails 49 Trying to install HPFS with less than 6M of memory . . . . . . 49 Trying to install on less than 4MB . . . . . . . . . . . . . . 49 Install hangs on Disk 1. . . . . . . . . . . . . . . . . . . . 49 1024 Limit Problem during install. . . . . . . . . . . . . . . 50 COUNTRY.SYS problems . . . . . . . . . . . . . . . . . . . . . 50 BIOS PROBLEMS. . . . . . . . . . . . . . . . . . . . . . . . . 50 Adapter Conflict Problems. . . . . . . . . . . . . . . . . . . 51 Video Adapter Problems . . . . . . . . . . . . . . . . . . . . 51 If you have a super VGA adapter, install should always be done as VGA. 51 C0000005 is displayed on the screen during install . . . . . . 51 Hang on Disk1 right after LOGO screen caused by OAK video card BIOS problem. . . . . . . . . . . . . . . . . . . . . . . . . . . 52 Hang on disk 6 during install. . . . . . . . . . . . . . . . . 52 White screen after installation with no system activity. . . . 52 Out of Synch/Install problems. . . . . . . . . . . . . . . . . 52 IRQ conflicts. . . . . . . . . . . . . . . . . . . . . . . . . 52 Failures very early on install disk (especially Zeos notebooks) 52 Dual Boot feature does not allow boot back to OS/2 from DOS. . 53 SYS1200 error when attempting to Dual Boot to DOS with an error code indicating that the DOS environment cannot be created and you see an error code EC=00BF. . . . . . . . . . . . . . . . . . . . . . . . . . . 53 Installation on ZEOS notebook fails. . . . . . . . . . . . . . 53 Fails to reboot after pressing enter.. . . . . . . . . . . . . 54 IBM ISA CDROM INSTALLATION FOR OS/2 2.1. . . . . . . . . . . . 54 Setting up the ATI MACH32 chipset to emulate the IBM 8514, using the IBM 8514 Device drivers.. . . . . . . . . . . . . . . . . . . . . . . 56 Setting up adapters with the MACH8 chipset to emulate the 8514, using the IBM 8514 drivers . . . . . . . . . . . . . . . . . . . . . . . . 58 Information on MITSUMI CD-ROM Device Drivers for OS/2. . . . . 61 Installing support for Multimedia CD-ROM packages (Media Vision Pro Audio Spectrum, Creative Labs Sound Blaster) . . . . . . . . . . . 62 Microsoft MS-DOS 6.2 upgrade and OS/2 . . . . . . . . . . . . 65 Installing the upgrade on an OS/2 BOOT MANAGER system. . . . . 65 How to set up OS/2 for Windows for HPFS only?. . . . . . . . . 66 After installing OS/2 for Windows, the mouse does not work at all. 67 I have Windows 3.1. It was installed from a CD-ROM. When I install OS/2 for Windows, it tries to find disk #7 on the CD. It is not there. How can I fix this?. . . . . . . . . . . . . . . . . . . . . . . . . . . . 68 Installing with Paradise EGA 480 . . . . . . . . . . . . . . . 69 Paradise VGA+, VGA Pro and VGA 1024 . . . . . . . . . . . . . 69 Paradise VGA Accelerator . . . . . . . . . . . . . . . . . . . 69 Using a RESPONSE FILE to install OS/2 OS/2 2.1, 3.5 blue diskettes/CD too complicated, too manual. . . . . . . . . . . . . . . . . . . 71 What to try if the installation hangs on or after either the Blue Disk #17 or the Salmon Disk #13: . . . . . . . . . . . . . . . . . . . . . . 73 Installing with the Sony 31A CDROM . . . . . . . . . . . . . . 75 The following IDE controllers made by Adaptec are not supported: 78 Can not install wiht AOX Micromaster 486/33. . . . . . . . . . 78 Installing 2.1 over another version of OS/2 and various devices to not work after install. . . . . . . . . . . . . . . . . . . . . . . . . . . 78 OSO001.MSG message not found while on disk1 during initial install 78 OS/2 2.1 and do NOT install WIN-OS/2 or DOS Support and system does not boot after install. . . . . . . . . . . . . . . . . . . . . . . . 78 Failure on install diskette, disk1, disk2. . . . . . . . . . . 79 Failure after DISKETTE 5 . . . . . . . . . . . . . . . . . . . 79 Failure after DISKETTE 6 . . . . . . . . . . . . . . . . . . . 79 Hang on Disk #17 or after workaround . . . . . . . . . . . . . 79 ============================================== 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. ============================================== Cannot install OS/2 2.1 on an EISA system with an Adaptec 1742A controller card. ============================================== SUMMARY OF RESOLUTION: Run the Setup Configuration Program provided with the Adaptec card Setup diskette and setup the card to the configuration described below. DETAILS OF RESOLUTION: Set up the Adaptec Card in the following configuration using the Setup Diskette that came with the controller. 1. Enhanced Mode to OFF 2. Standard Mode to ON 3. Hex Address to C800 4. I/O Port to 230H 5. DMA Channel to 5 6. Parity Check to OFF 7. Synchronous Negotiation to ON 8. Enabled Disconnect to YES 9. IRQ to 11 (default is 2) ============================================== Before installation of the OS/2 2.1 Upgrade, the line SET DMQSPATH=D:\XGA$DMQS was added to the CONFIG.SYS and the XGA$DMQS directory had been copied from C: to D:. When the Installation migrated the existing CONFIG.SYS the above line was deleted from the CONFIG.SYS and all the DMQS files were copied to the same partition as the base system. ============================================== SUMMARY OF RESOLUTION: Add the line back to the new CONFIG.SYS and XCOPY the XGA$DMQS directory to D: DETAILS OF RESOLUTION: 1. Change the CONFIG.SYS a. Start an editor session. b. Open the OS/2 CONFIG.SYS. c. Add a line and type in SET DMQSPATH=D:\XGA$DMQS. d. Save the changes and exit the editor. 2. XCOPY the XGA$DMQS directory from C: to D:. a.Start an OS/2 session. b.Type XCOPY C:\XGA$DMQS D:\XGA$DMQS /S (then press enter) 3. Execute a proper shutdown and reboot the system. ============================================== Problems installing OS/2 2.1 on system that have a HYPERACE 486 upgrade. ============================================== DESCRIPTION OF SYMPTOMS: When the installation process prompts for Diskette 1 after pressing ENTER the diskette drive spins, trying to read the diskette, gives up and then displays the message Disk read error - please insert System disk. SUMMARY OF RESOLUTION: Disable the CACHE switches on the board itself. DETAILS OF RESOLUTION: 1. There are dip swithces on the Hyperace card that need to be disabled. a.Switch 1 is the main cache b.Switch 2 is the HIMEM cache c.Switch 4 is the BIOS cache 2. The main cache switch may be the only one needed to install but if the problem continues turn all the above off. 3. Consult the documentation that came with the card on the procedure for doing this. 4. After a successful installation the CACHES can be enabled by resetting the switches. ============================================== TRAP 0002 on Model 8590 OR 8595 ============================================== DESCRIPTION OF SYMPTOMS: Trap 0002 during installation of OS/2 2.X on a MODEL 8590, OR 8595. SUMMARY OF RESOLUTION: 1. Make sure SIMMS are not mismatched. 2. Check part numbers on the Microprocessor and Memory riser and check below to see if a new Engineering chages are needed. DETAILS OF RESOLUTION: 1. Ensure that the machines have matched pairs of single inline memory modules (SIMMS); they must be matched in size and speed. 2. If the computer is a 33 MHz system and the Microprocessor card part number is 84F9356, contact local IBM representative and request ECA053. 3. On the MODEL 90 if the Memory riser card is part number N33F4905 or 84F9356, contact local IBM representative and request ECA084. ============================================== Horizontal Black bands across the screen after DISK 5 reboot with the GATEWAY 2000 486/66 local bus and ATI Graphics Ultra Pro ============================================== DESCRIPTION OF SYMPTOMS: During install on a Gateway 2000 486 66 with local bus and ATI Graphics Ultra Pro the system gets as far as the screen that shows the colorful OS/2 fullscreen symbol. The display then shows 5 or 6 horizontal bands of video separated by black bands. The bands scroll horizontally across the screen. SUMMARY OF RESOLUTION: Run the Setup program for the ATI card and set up the monitor as an IBM default. DETAILS OF RESOLUTION: 1. Boot DOS. 2. Change directories to MACH32 3. Type INSTALL then press enter. 4. At the Main Selection screen select SET POWER UP CONFIGURATION. 5. At the next screen select MONITOR TYPE. 6. The next screen should have the 1572 Monitor with 72hz refresh rate highlighted, press enter to select it. 7. Select IBM default as the new Monitor. 8. After successful installation repeat steps to reselect the 1572 Monitor. ============================================== Disk Read error has occurred when attempting to boot the Installation Diskette ============================================== DESCRIPTION OF SYMPTOMS: Future Domain TMC-850/860/875/885 w/BIOS revision level 7.0. Future Domain TMC-1660/1670/1680 w/BIOS revision level 2.0. Will produce the message, "Disk read error has occurred" when attempting to start the Installation diskette. SUMMARY OF RESOLUTION: Contact Future Domain for a BIOS upgrade ============================================== 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 thisinfo 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. ============================================== AMI Fast Disk and Fast Disk II SCSI adapters are recognized as ADAPTEC Adapters, gives COUNTRY.SYS error message on Boot-Up. ============================================== DESCRIPTION OF SYMPTOMS: Country.sys cannot be found error message on boot up, using an AMI Fast Disk or Fast Disk II SCSI Adapters. SUMMARY OF RESOLUTION: 1. At the final restart after the installation is complete, delete from the CONFIG.SYS file, any line with "BASEDEV=AHA1xxx.ADD" (where "x" can be any character). 2. Ensure the line, "BASEDEV=IBMINT13.I13," appears in the CONFIG.SYS file. DETAILS OF RESOLUTION: 1. Boot DOS or from a DOS Bootable Diskette with a text editor on it. 2. Start the Editor and edit the OS/2 CONFIG.SYS. 3. Delete any line that references an Adaptec Driver. ie. any line with a reference to AHA1xxx.ADD (where xxx can be any character) 4. Ensure that the line BASEDEV=IBMINT13.I13 is present. If not add the line. 5. Save any changes and exit the editor. 6. Remove any disks from drive A, and Boot OS/2. ============================================== 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. ============================================== Slow SCSI support or missing Icons on boot-up ============================================== DESCRIPTION OF SYMPTOMS: Slow SCSI support and bad or missing icons after installation of OS/2 2.0. Also other data corruption may occur. SUMMARY OF RESOLUTION: Ensure that hard drive and card are matched in their settings of SYNCH and ASYNCH mode. DETAILS OF RESOLUTION: Consult the documentation for the Hard drive and controller card to make sure that the controller and drive and either both set for asynch mode or synch mode. ============================================== 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. ============================================== 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.) ============================================== Installing OS/2 2.1 on a machine with an AOX/KINGSTON upgrade ============================================== DESCRIPTION OF SYMPTOMS: Cannot install OS/2 2.1 on a machine with a 286 CPU upgraded to a 386SX with an AOX upgrade. SUMMARY OF RESOLUTION: Boot real DOS and run AOX232.EXE that can be obtained from AOX'S BBS or Technical Support group. DETAILS OF RESOLUTION: 1. Download AOX232.EXE from AOX'S BBS (617) 890-3393 or call the AOX Technical Support group(800-232-1269) and request it. 2. Boot the machine from DOS or a DOS bootable diskette. 3. Insert the disk with AOX232.EXE in drive A: 4. This needs to be run every time before installation of OS/2 2.1 5. Remove the disk from drive A and insert the OS/2 2.1 Installation diskette in drive A and press Ctrl + Alt + Del to reboot the system and restart the installation. ============================================== TRAP 2 OR TRAP 6 at 60000X:9084 during install ============================================== DESCRIPTION OF SYMPTOMS: Trap 2, Trap 6 or other Trap at 60000x:9084. SUMMARY OF RESOLUTION: 1) Disable cache during (Esp. Phoenix BIOS) 2) Turn turbo switch off. 3) Always IN2000 SCSI 4) Disable Shadows 5) Mismatch Memory 6) Old 8590 and 8595with N33f4905 or 84f9356 needs ECA084 or ECA053. DETAILS OF RESOLUTION: 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). 1. Make sure that all the simms in the machine are the same speed, type, and manufacturer. 2. Run memory checking diagnostics on the simms to ensure they are not bad. ============================================== System asks for DISK 16 but there are only 15 disks plus the printer driver disks ============================================== DESCRIPTION OF SYMPTOMS: The installation of OS/2 2.0 goes fine up to disk 15 but then the system prompts for disk 16, the problem is there are only disks 0-15 for installation and the printer driver diskettes. SUMMARY OF RESOLUTION: This problem usually occurs on systems which have had the A: and B: drives switched because OS/2 has to install from drive A: but drive A: was a 5.25 inch drive and the install disks are 3.5 inch. The drive cables must be physically switched and the CMOS setup has to be updated as to the new configuration. DETAILS OF RESOLUTION: Go inside the machine and swap floppy drive cable connectors, use the 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 an adapter plug can be obtained. ============================================== TRAP 8 on installation DISK # 1 on MYLEX systems ============================================== DESCRIPTION OF SYMPTOMS: Trap 8 on Disk 1 of installation on MYLEX systems. CS:EIP 0160 : FFF63898 IPE at ##0160:FFF6345F - 0008:A53F SUMMARY OF RESOLUTION: This is a known problem with MYLEX systems which they are aware of. For a fix contact MYLEX systems. ============================================== SYS 0045 during install. ============================================== Getting a SYS0045 Cannot find sector requested on D drive on disk1 of installation. If you run an OS2 CHKDSK on the drive it returns SYS1336 & SYS1374 File Allocation Table is bad on drive D. Use pc tools or norton disk editor to edit the boot record. There was a line in the boot record which said OEMID was pcformat, since it had been formatted with pctools. He changed that to IBM 5.0, and that solved the problem. Do not have to reformat. ============================================== COUNTRY.SYS not found ============================================== COUNTRY.SYS error message at bootup of first two diskettes or after first five diskettes, and reboot of machine by installation program. 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. ============================================== Installing on TI Notebooks (TI4000/30, /40/& 50's.) ============================================== The install work around for the TI notbook/Laptops is as follows. Goto CMOS Advanced settings. 1. Power Savings=Off 2. Time Out Interval=On 3. HDmotor Timeout=On 4. LCD Power=Low 5. Advanced OS Power=Off 6. External cache=Off 7. Turbo=Off. Note all settings can be set back to normal after the install has completed. The Power savings switch in the TI4000/33 is not compatible with OS2 2.1 power management software, and should not be used. ============================================== 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. ============================================== SYS 2025 & 2027 on the installation with PHOENIX BIOS ============================================== If you get a cust. with a 2025 & 2027 with the phoenix bios 1.03 m series,the cust. needs to do the following: 1) Make a copy of the installation disk 2) Rename the os2boot to os2bllt on the new install disk 3) Delete the os2ldr from the new instl disk 4) Delete the os2ldr.msg from the new installation disk 5) Copy the os2boot from the orignal installation disk to the copy the cust. made. 6) Copy the os2ldr from the orginal installation to the install disk the cust. made. 7) Copy the os2ldr.msg from the orginal installation disk to the install disk the cust. made. 8) Then reboot the system using the installation disk the cust. made. ============================================== AST machine and has added 3rd party memory to it he may encounter an error on install of 2.1, country.sys not found. ============================================== The explanation from AST is that the new 486 Notebook is designed for 3.3V memory modules and currently the 3rd party memory modules are 5.5V. ============================================== Installation failure on 700C ============================================== Receiving a sys0005 on the install disk after disk5 and would reference the WPHELP.HLP file. Can not get past install disk. Copy the ABIOS.SYS from the Thinkpad Reference onto the install and disk1. ============================================== There is a potential workaround to the problem of hangs and SYS 3175's during selective installs. ============================================== The workaround is to rename the \os2\drivers\fd16-700.exe to \os2\drivers\fd16-700.bak. ============================================== Did not select dual boot option when installing OS/2, and now want to add it. Can I do so without having to install DOS and then reinstall all of OS/2? ============================================== *** This answer applies to OS/2 versions 1.3 and 2.X *** You do not need to reinstall OS/2 in order to get the dual boot feature. If you are using OS/2 2.0, use TOOLCAT OS2CSD and order the DBPREP package. This package is: A utility to allow DOS 4.0, DOS 5.0, and DR DOS to be installed as a dualboot function on top of OS/2 2.0, and recover to OS/2 in case something goes wrong during the DOS install. ============================================== There is a problem installing OS2 2.1 on some PS2 8580, ESDI units. These units will install and run with OS2 2.0 but with 2.1 you cannot get past disk 1 of install set ============================================== Make a DISKCOPY of install disk 1. Delete the BUNDLE file from copy of disk 1. Format a new disk and label it "DISK 1". XCOPY the files from disk 1 copy to new disk. Copy the BUNDLE file from real disk 1 to new disk. Use the new disk for installation in place of disk 1. To speed things up, you can XCOPY files to a hard disk. ============================================== Installing OS/2 2.1 on a 486 machine. Error msg that states that "the BIOS was not compatible". ============================================== If the manufacturer of the opti-chip is Award, they will passed you to company called Pinnacle Sales. This company sells an upgrade chip that is compatible with OS/2. It costs $59.00. Pinnacle Sales:(408)453-7500. ============================================== Selective Install fails ============================================== There is a new fix available out on OS2CSD and now available on the OS2BBS It is call OS2CCP and might be a solution for anyone having problems with Selective Install. Here is the description: Starting in late June, OS/2 2.1 began shipping a reduced diskette package to take advantage of better diskette compression techniques. These diskettes are salmon in color (the original package contained blue diskettes.) Because the layout of the diskettes is different for the two packages, the enclosed CMD files will need to be run to allow selective installs to work correctly if the installation package is different from the package that is currently available to you. This diskette contains files which are to be used to alter the user's system to accommodate the other OS/2 package. This procedure is to be used only in those situations in which a user has a mismatch. If you are not sure if you have a mismatch, run the CHECK.CMD file to determine which version and type of package is installed. See the README file for more details. ============================================== Installation failures on Gateway machines ============================================== Gateway has released ADVOSOF.exe for OS2 installations. This file Disables all the power saver features and disables all caches and turns the turbo mode off. Gateway has this file on their BBS in the OS2/NoMAD drivers file area. Gateway's tech support recommends this file for both OS2 and Windows NT install Preperation. ============================================== Enabling CACHE after having to disable CACHE for installation ============================================== OS/2 trapping when you renable the shadow ram, cache and turbo after installing. Accel, the manufacturer of the motherboard and found out that if you go into the cmos advanced system settings and the A20 Gate Handler is disabled it will cause os/2 2.1 to trap when turning the shadow ram, cache and turbo back on. When the customer set the A20 Gate Handler to enabled os/2 no longer trapped. ============================================== The 2nd stage of Install asks for Win3.1 disks -- but you have Microsoft Windows on CD ROM ============================================== Your installation program accepts Win3.1 on CD -- BUT it treats the images as 5 1/4 disks and asks for #7 disk -- which image is not on CD ROM. And is asking and asking...dispite that the files required are on CD ROM. Workaround: 1) Install from the floppy drive 2) Install from CD ROM but get 5 1/4 DISK#7 for WIN3.1 3) Before installing from CD ROM make fake #7 floppy with DISK7 file with DISK7 text in it (AKA MS disk #6) -- and copy print drivers and stuff from 3.5 diskette 6. ============================================ Installing OS/2 with 4M RAM and UNPACK2.EXE and using CDROM during install. ============================================ Editing the config.sys on disk #1 (create partition before the procedure) change " memman=swap " and add " swappath=c:\ 64 1024 " and rem all unwanted basedev. Boot up from disk and go through install. After booting on os/2 edit the config.sys and rem statement that was added on the disk #1 in config.sys "memman and swappath " as well as any incorrect one. NOTE: For disk install adding swap might not be necessary. ============================================== Installing on a DPT SCSI Controller, TRAP 0008 ============================================== DPT SCSI controller and were getting a trap 0008 on diskette #1. Set the interrupt from 15 level to 15 edge upgrade the eprom to 5C ============================================== "SYSTEM CANNOT FIND THE FILE KBD01.SYS" ERROR MESSAGE ON BOOT UP AFTER A SUCCESSFUL INSTALL ============================================== On a system with a Micropolis SCSI 1 gig harddrive the user is getting "system cannot find the file KBD01.SYS this driver program or data file is not located in the default path or the path specified for it not in the config.sys file. Install this file in the correct directory or the appropriate config.sys file statement." Upon checking the CONFIG.SYS the correct statements are there and the file is located in the correct place on the harddrive. Workaround: Disable the "Read ahead cache" on the Micropolis Drive. There is a utility on the Micropolis BBS called UTIL.EXE which will allow the user to disable the "Read ahead cache" on the Micropolis 1 GB Drive Model 2112. ============================================== Greater then 16 MB in MOD 80 will not install 2.1 ============================================== Fix: The trick is to get the correct RAM init code installed on the hard drive using the Reference Diskette. This requires a modified FDDF.ADF file and EMO option diskette level 1.3. You can also remove the EMO card for the installation if you have 4 meg on the planer. ============================================== Installing OS/2 2.x on top of Lan Server 3.0 with HPFS386 ============================================== 1. Use the BACKACC command to back up all access control profiles on the drive containing OS/2 (e.g. BACKACC C:\ /S) 2. Use the NET command to delete all access control profiles for the drivce containing OS/2 3. Reboot from the ServicePak diskettes and install the service pack 4. On restart after installing the ServicePak, restart the server and use RESTACC to restore the access control profiles saved above (e.g. RESTACC C:\ /s) 5. At this point access control profiles should be reset as they were before. If the Service program still fails to find the SYSLEVEL files on reboot, I would suggest making sure that all directories have the ARCHIVE attribute bit removed before continuing. This can be done using the ATTRIB command. ============================================== 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 how to run 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) ============================================== Black Desktop ============================================== 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. Contact the manufacturer or hardware technical literature for instructions if necessary. ============================================== If ATI 8514 Ultra or Graphics Ultra locks with white screen on bootup. ============================================== The older ATI ROM chips return an incorrect monitor ID when queried by OS/2. Call ATI at 416-882-2626 to obtain an update. Remember, these boards MUST be set up as an 8514 PRIMARY display and the statement DEVICE=C:\OS2\MDOS\VVGA.SYS MUST be changed to DEVICE=\OS2\MDOS\VSVGA.SYS ============================================== TRAP0002 on IBM 8590, 8595 ============================================== If you are experiencing problems with a Model 90 or 95, ensure the system is at the latest engineering change (EC) level. Call 1-800-IBM-SERV if the following conditions are met. If the Model 90 or 95 is a 33 MHz system and you are having intermittent difficulty identifying memory parity errors such as TRAP 0002, forcing you to restart the system, then ECA053 might apply. If the microprocessor card has part number 84F9356, contact IBM representative to assist you with a replacement. If the Model 90 is experiencing intermittent memory errors, ECA084 might apply if the part number of memory riser card is N33F4905 or 84F9356. Contact 1-800-IBM-SERV. For both the Model 90 and 95, you must ensure that the single inline memory modules match in pairs. This means that each pair of single inline memory modules, as described in system technical reference manual, must be matched in memory size and speed. Mixing these modules can cause some computers to report memory errors. ============================================== 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). ============================================== SYS1201 boot error during (or after) installation of OS/2 2.1 ============================================== This fax will offer suggestions for resolving SYS1201 errors during boot of OS/2 2.1. The information provided is for the general availability release of OS/2 2.1. PROBLEM: SYS1201 - VMOUSE NOT INSTALLED... There appears to be a problem with the OS/2 2.1 installation program if there is any MOUSE.* on the drive where OS/2 2.1 is being installed. The symptom of this problem is the SYS1201 - VMOUSE NOT INSTALLED error. While this is not the ONLY reason for this error, the following steps should offer most users relief of this problem. 1) Review the CONFIG.SYS file for OS/2 2.1 and verify that the DEVICE= statement points to MOUSE.SYS in the x:\OS2 directory (where x: is the installed drive and is usually 'c:'). There has been one user who has reported that MOUSE.COM was loaded in the CONFIG.SYS file instead of MOUSE.SYS. This event HAS NEVER been duplicated in the IBM labs. There should be no reference to MOUSE.COM in the CONFIG.SYS file for OS/2 2.1. 2) Copy the MOUSE.SYS file from Program Diskette 1 (which is the second disk in the install series) to the x:\OS2 directory (where x: is the installed drive and is usually 'c:'). Shutdown OS/2 2.1 and reboot the computer. 3) If the problem persists after following the preceding instructions, you can "HOT PLUG" (unplug, wait and then plug in) the mouse. If this fixes the problem and you previously used the mouse under OS/2 2.0, you can try using the MOUSE.SYS from OS/2 2.0. This is also located on Program Diskette 1 of the install series of OS/2 2.0. PROBLEM: SYS1201 - COM.SYS NOT INSTALLED... or IRQ NOT AVAILABLE. 1) If you only have one (1) serial port AND you have a MOUSE plugged into the port, you will get this error. Edit the CONFIG.SYS file and place a remark (REM) statement before the "DEVICE=...\COM.SYS" and "DEVICE=...\VCOM.SYS" lines. 2) If you have a PS/2 or equivalent Microchannel Architecture (MCA) computer, you should not pass ANY parameters to the COM.SYS device driver. Only ISA and non-ABIOS computers require parameters for serial ports greater than COM2:. 3) If you have an Industry Standard Architecture (ISA or AT) computer, you will have to provide the CORRECT Input/Output (I/O) address and Interrupt Request Level (IRQ) for serial ports greater than COM2:. The parameters must match the PHYSICAL settings of the serial adapter(s). You will have to reference the documentation which should have come with the serial adapter to determine how to PHYSICAL change (or "jumper") the adapter. If you have an internal modem and have two external serial ports, we recommend that you try to set the modem to I/O address "3e8" and IRQ 5. (NOTE: You can only use IRQ 5 if you have only one (1) parallel port (LPT1:). The format of the parameter line is: DEVICE=...\COM.SYS (p,addr, irq) For example, if you have PHYSICALLY configured your internal modem to I/O address 3e8 (or COM3:) and have set the PHYSICAL IRQ to level five (5), you would set the following parameters: DEVICE=x:\OS2\COM.SYS (3,3e8,5) 4) If you provide an invalid address or IRQ, you will get messages that indicate that the "COMx" port was not installed or that the IRQ is not available. You will have to verify that the serial adapter (i.e. internal modem) is configured correctly. ============================================== ISA bus workaround for installation problems on AT (ISA) BUS machines ============================================== CONFIGURATION: AT-bus (ISA) machine non-SCSI disk controller (RLL, MFM, ESDI) sometimes occurs on IDE controllers. SYMPTOMS: Very slow install Very noisy hard disk during install FDISK errors Very slow operation There is a driver, IBM1S506.ADD that is available on the IBM NSC BBS as well as various other non-IBM OS/2 BBS's around the country. This driver fixes the symptoms described above. If you are unable to obtain the driver, the workaround described below will alternatively allow you to install and use OS/2 2.X, however, it is recommended that you obtain the driver. WORKAROUND BEFORE INSTALLATION: ------------------------------ Step 1: Use DOS to edit the CONFIG.SYS on Diskette 1 in the 2.X package. NOTE: Diskette 1 is the first diskette AFTER the Install diskette. Change the line - BASEDEV=IBM1S506.ADD to REM BASEDEV=IBM1S506.ADD Alternate to Step 1 Above: -------------------------- If you don't have access to DOS OR do not have a DOS editor to edit the CONFIG.SYS, as an alternate to editing the CONFIG.SYS file on Diskette 1, you may follow these steps: a) Insert the Installation Diskette into drive A b) Turn on the computer. If the computer is already on, press and hold Ctrl+Alt and press Del to restart the system. c) When you are prompted to do so, remove the Installation Diskette and insert Diskette 1. d) Press Enter. e) When the Welcome screen is displayed, press Esc to display the OS/2 command prompt. f) With Diskette 1 in the drive, rename the IBM1S506.ADD to IBM1S506.OLD by typing the following at the prompt: RENAME IBM1S506.ADD IBM1S506.OLD g) Continue with Step 2. Step 2: Insert the Installation Diskette into drive A. Step 3: Turn on the computer. If the computer is already on, press and hold Ctrl+Alt, and press Del to restart the system. Proceed with Diskette 1 through 5. Step 4: After Diskette 1 through 5 are processed, you will be asked to reinsert the Installation diskette. DO SO. After copying some files from the Installation diskette, you will be asked to remove the Installation diskette and press Enter to reboot. DO NOT DO THIS. LEAVE THE INSTALLATION DISKETTE IN THE DRIVE. NOTE: In OS/2 2.1 the installation is slightly different, it will ask for the installation diskette then diskette #1 at this point you will see the message take out the diskette and reboot. DO NOT DO THAT..INSTEAD PUT THE INSTALLATION DISKETTE BACK IN THE A: DRIVE. Step 5:Press and hold Ctrl+Alt and press Del to restart the system. Step 6:Your computer should now be rebooting off the Installation Diskette. Step 7:When you are prompted to do so, remove the Installation Diskette and insert Diskette 1. Step 8:Press Enter. Step 9:When the Welcome screen is displayed, press Esc to display the OS/2 command prompt. Step 10:You are now at a command line. If you are NOT attempting to install HPFS, continue on to the next step, otherwise execute the following steps to load the HPFS driver. Insert Diskette #2 in the drive, and enter the following command: chkdsk c: (If your operating system will reside on a drive other than C, use the appropriate drive letter instead.) Step 11: Enter the following commands: RENAME C:\OS2\IBM1S506.ADD IBM1S506.XXX COPY C:\OS2\IBMINT13.I13 C:\OS2\IBM1S506.ADD (If your operating system will reside on a drive other than C, us the appropriate drive letter instead.) Step 12: Remove the diskette from the drive. Press ALT-CTRL-DEL to reboot the system, and install should pick up where it left off. WORKAROUND AFTER INSTALLATION Open the system folder on the desktop, then open Command Prompts Folder Open OS/2 Window, at the prompt go the OS2 subdirectory on the drive that OS2 was installed on, and type: RENAME IBM1S506.ADD IBM1S506.XXX COPY IBMINT13.I13 IBM1S506.ADD Close all open folders and proceed with a proper shutdown. When the machine is rebooted the change will take effect. ============================================== IBM Premier Abios Systems Installation ============================================== At the time of the original release of OS/2 2.0, the installation code could not recognize new hardware with RAM loadable ABIOS. The architecture in the installation process has been changed to recognize this RAM loadable ABIOS and has been incorporated into the latest release. There is a workaround for the original GA release. Make a copy of the Installation Disk and Disk One of OS/2 2.0. Substitute the ABIOS.SYS from the Premier hardware reference disk to both the OS/2 2.0 Installation and Disk One. Copy the SF838XX.BIO file from the hardware reference disk (should be about 40K) to both OS/2 2.0 Installation Disk and Disk One. If there isn't enough space on the diskettes, get rid of the other .BIO files that exist on the Installation and Disk One. Then you are ready to begin installation of GA OS/2 2.0 on your Premier machine. Once OS/2 2.0 is loaded, you can apply the OS/2 Service Pack (xr06055) available on Compuserve, the Raleigh BBS (919) 517-0001 or call 1-800-3IBM-OS2. If the problem is with an IBM ThinkPad computer, there is another fax that deals with this special case of ABIOS.SYS problems. ============================================== Information on INSTALL BIOS PROBLEMS ============================================== LOCAL FIX: Due to the wide variety and many sources for PC compatible equipment, many different combinations of hardware components and BIOS revisions exist. OS/2 is an advanced operating system that may require an updated BIOS. Many install problems and other I/O related problems may be resolved by updating the BIOS. You will need to determine your BIOS manufacturer, version, and date, and this should be checked with the manufacturer for compatibility with OS/2. If you need help determining your BIOS information, see "TIPS ON GETTING BIOS INFO" below. ============================ SOME BIOS COMPATIBILITY INFO ============================ The following table lists dates and revision levels required for OS/2 to work with listed components: Component Date ("mmddyy") Revision Level AMI BIOS -------- IDE hard drives 040990 SCSI 092588 or later (need OS/2 compatible and may need special installation procedure) Other drives 092588 or later MFM, RLL, ESDI, etc. Keyboard controller F only * * Revision level 0 or revision level 9 with non standard ID code format indicates motherboard OEM manufacturer - nonstandard BIOS. This may or may not work with OS/2, and it may have "custom" functionality for the specific motherboard which may preclude upgrading. The motherboard manufacturer should be contacted for further information. Phoenix Bios 051192 1.03 Always IN2000 SCSI VCN:1-02 for host adapter: 2.5-2.7 Quantam Plus Hardcard 2.6 MC Enabler SCSI Host Apdater 2.0 TIPS ON GETTING BIOS INFO ========================= AMI BIOS's of modern vintage provide a Screen ID Code, visible at the lower left of the screen during the initial RAM count, and which can be made to return by resetting with Ctrl-Alt-Del. The format of this ID code is: AMI BIOS and AMI BIOS Plus: aaaa-bbbb-mmddyy-Kc AMI Hi-Flex BIOS: ee-ffff-bbbbbb-gggggggg-mmddyy-hhhhhhhh-c If the screen ID code is in a form other than this, the BIOS is either very old or was produced by a company with a source code license. In the former case, contact us for update information. But in the latter case, only the motherboard manufacturer will be able to provide further information or updates. Everex 386 BIOS's are in this latter category. BIOS UPDATES ============ If a BIOS prior to the dates noted above requires replacement, note the following: 1. AMI BIOS and BIOS Plus series BIOS (16 character ID code) for CACHED motherboards are customized for individual mother- board designs, and can ONLY be obtained from the motherboard OEM, with only THREE common exceptions: a) BIOS's with "aaaa" = E307 can often be replaced with a standard type. b) BIOS's for Northgate or Motherboard Factory motherboards EXCEPT the Northgate Slimline can, be replaced by a standard type. c) BIOS's with "aaaa" = DAMI, DAMX, or EDAMI are usually for cached boards designed and/or built by AMI, and if so, can be updated. 2. The complete Screen ID Code is required to properly address whether a BIOS update for other motherboards can be provided, and in the case of the Hi-Flex BIOS, the complete SECOND and THIRD lines of the ID Code are also necessary. If not visable immediately on the screen, they may be viewed by pressing the <INS> key during boot-up. 3. For these AMI BIOS updates, Call Washburn & Co. to order new versions. ============================================== Adapter: All Adaptec adapters ============================================== Note: SCSI hard disks must be configured as SCSI target ID 0 or 1 to be able to start up from that hard disk. ============================================== Adapter: Adaptec AHA-154x ============================================== Drive: IBM 0661 - 320MB SCSI Note: Adapter BIOS will not recognize the drive as target 0 or 1 (Drives 80, 81). For OS/2 2.0, the drive can be used as a non-startup drive. ============================================== Adapter: Adaptec AHA-174x ============================================== Drive: IBM WDS-3180 - 80MB SCSI, IBM WDS-3160 - 160MB SCSI Note: Adapter will not recognize these drives when config- ured in 'STANDARD MODE' (AHA-154x emulation). Instead, the AHA-174x adapter should be configured in "ENHANCED MODE'. This mode is supported by the OS/2 2.0 drivers, and the problem does not occur when the adapter is operating in enhanced mode. ============================================== Adapter: Future Domain TMC-850/860/875/885 w/BIOS revision level 7.0. Future Domain TMC-1660/1670/1680 w/BIOS revision level 2.0. ============================================== System: IBM Models 35 and 40 when the Future Domain adapter is controlling the startup diskette. Note: Will produce the message "Disk read error has occur- red" when you attempt to start the Installation diskette. Contact Future Domain for a free BIOS upgrade. ============================================== Adapter: AMI SCSI Adapters ============================================== Symptom: AMI "Fast Disk" and AMI "Fast Disk II" SCSI adapters are incorrectly recognized as Adaptec adapters. Problem: At the final restart after the installation is comp- lete, delete from the CONFIG.SYS file, any line with "BASEDEV=AHA1xxx.ADD" (where "x" can be any character) Ensure the line "BASEDEV=IBMINT13.I13", appears in the CONFIG.SYS file. ============================================== Adapter: Bernoulli Boxes ============================================== Notes: 44 and 89MB drives will work if connected to any other SCSI card other than Bernoulli's own card. The drive will work as a large diskette and will be non-bootable Iomega has drivers for the Bernoulli Boxes. ============================================== Adapter: MC Enabler SCSI Host adapter ============================================== Resolution: Requires ROM Revisions 2.00. or higher. ============================================== Adapter: IBM 16-bit SCSI cards (early versions) ============================================== Symptom: Early versions of the IBM 16-bit SCSI adapters may experience problems and report erroneously that the device is not functioning. Resolution: Replace SCSI card with a card with updated microcode ============================================== Slow hard drive speed and possibly no icons appearing. Other data corruption possible. ============================================== Problem: Hard drive and adapter card settings not correctly matched. Resolution: Ensure that hard drive and card are matched in their settings of SYNCH and ASYNCH mode. ============================================== Installing OS/2 2.X on a PC using the Always IN-2000 SCSI Host adapter? ============================================== Contact Always Technology to obtain BIOS upgrade VCN:1-02 for the controller. ============================================== Known problems involving an AOX add-in processor card in a Micro Channel PS/2? ============================================== If you encounter problems installing or booting OS/2 with this configuration, contact AOX for the latest "flash PROM" code update. ============================================== Installing OS/2 2.0 on a L40, and getting CRC errors and the installation locks up. Tried several sets of diskettes with the same results. ============================================== Some early L40s had inadequate shielding around the diskette drive that shows up when installing OS/2. The power supply, which is beside the drive emits more electromagnetic interference when multiple devices are running concurrently, such as when OS/2 is multitasking (while installing diskette 3, for example). If you have verified that the diskettes themselves are not defective, replace the diskette drive. ============================================== Installing OS/2 2.0 on a P70, and getting CRC errors and the installation locks up. Tried several sets of diskettes with the same results. ============================================== Some early P70s had an engineering defect that only shows up with multitasking operating systems (including OS/2 and AIX). There is an Engineering Change Announcement (ECA) that fixes this problem. Take your system in to your dealer and have them service the system under warranty. ECA068 will extend the warranty indefinitely for this particular problem, without charge. ============================================== Getting a C000005 error during installation and can't continue. ============================================== The problem results from a conflict with some SVGA cards. There is a replacement BVHSVGA.DLL file available on the IBM NSC BBS (404-835-6600) that allows installation. ============================================== System is hanging during installation (or bootup). ============================================== If you have a SVGA card that uses the Western Digital PVGA1D chipset, there is a replacement BVHSVGA.DLL file available on the IBM NSC BBS (404-835-6600) that corrects this problem. ============================================== Known INSTALL problems with AMI BIOS ============================================== Symptom: Various install problems. The suggestion to upgrade these items should always be made. Possible SYS2025, and SYS2027 at disk#1. Problem: 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. Resolution: 1. Call Washburn & Co. to order new versions. 2. Bad diskette. Format new diskette and diskcopy failing diskette to this new diskette. 3. Clean, swap or replace the diskette drive. 4. Disable system memory cache during installation. Washburn & Co. 716-248-3627 (AMI Bios Upgrade) 800-836-8026 (AMI Bios Upgrade) ========================================= Installing with ATI VIDEO ADAPTERS ========================================= ATI Wonder SVGA The ATI Wonder Super VGA board is supported in VGA mode only with the video drivers supplied with OS/2. However, ATI does have drivers for 800x600 and 1024x768 resolutions in 16 colors. As of this writing, there are no drivers for 256 colors. You c an call ATI at 416-756-0711 to get information on obtaining these drivers. If you have any problems with ATI drivers, you will need to speak to ATI, IBM will not be able to help you. ATI Vantage and Graphics Ultra These boards are almost identical, the major difference being that the Vantage uses DRAM and the Graphics Ultra uses the faster VRAM. The Graphics Ultra is probably the best choice for using the higher resolution modes under OS/2. It will provide 10 24 x 768 resolution with 256 colors for both OS/2 and full screen Windows applications using the drivers supplied with OS/2. ATI also has drivers for these boards which will provide 640x480, 800x600, and 1024x768 resolutions in 16 or 256 colors. You MUST have 1MB of memory on your video board to get 256 colors. Before installing OS/2, use the setup program (provided by ATI) to setup your video board. During installation, OS/2 should recognize the board as an 8514 and list that as your primary display. If not, the board is not set up properly. DO NOT attempt to use these boards as your secondary display, it MUST be the primary display. After the installation, you will need to modify a line in your CONFIG.SYS as follows: Change DEVICE=C:\OS2\MDOS\VVGA.SYS to DEVICE=C:\OS2\MDOS\VSVGA.SYS The IBM 8514 board uses VVGA.SYS, the ATI 8514 boards require VSVGA.SYS. As of this time, seamless Windows are not supported in the high resolution mode. You will be limited to using Windows as a full screen application only. If you must have seamless Windows, you MUST select medium resolution when installing OS/2 video dri vers. Medium resolution is VGA (640 x 480) so you will lose the advantage of having an 8514 compatible board. This will be added later this year as an enhancement to the OS/2 graphics engine. The only serious problems we have encountered with these boards is with switching from DOS and Windows full screen applications to the desktop or vice versa. You may occasionally have a DOS or Windows session lock up or appear to hang after the switc h. This can be resolved by turning VIDEO_SWITCH_NOTIFICATION to ON for each and every object on your desktop that launches a full screen session. If the problem persists, turn VIDEO_8514A_XGA_IOTRAP to ON also. These switches can be found in the DOS Settings in the "Open - Settings" notebook. If you do not have the VIDEO_8514A_XGA_IOTRAP setting listed, you do not have the proper drivers installed for 8514 operation. I would also recommend that you set these switches for each of the objects in your command prompts folder that launch a full screen session. ATI 8514 Ultra This board provides the same functionality as the Graphics Ultra, but requires a separate VGA or SVGA adapter in your system. All of the information listed above for the Graphics Ultra applies to this board as well. One additional problem has been encountered with this board though, you may get a blank white screen when booting (usually seen during the reboot required by the install process) and the system will hang. This is caused by an incorrect monitor ID being returned to OS/2 when it queries the device to see what kind of monitor is attached. ATI has corrected this problem with their latest 8514 Ultra ROM chip. You can call ATI at 416-756-0711 to obtain an update. General Considerations The 8514 compatible boards (Vantage, Graphics Ultra, and 8514 Ultra) are NOT Super VGA boards. You should NOT execute SVGA ON from the DOS command prompt as you would for other high resolution boards. This WILL cause problems with your video! You can c heck the C:\OS2 directory for the file SVGADATA.PMI to determine if the SVGA program has been executed. If this file exists, delete it, shutdown, and reboot your system. You may have heard that you need to put your board in an 8 bit slot in order to work properly, this is not true for ATI boards. You should have no problem using your board in 16 bit mode. ============================================== CDROM install with Sony 31A ============================================== The Sony 31A device driver is available on the IBM National Support Center BBS at (919) 517-0001. The file name is SONY31A.ZIP. ============================================== CDROM install with Mitsumi ============================================== The Mitsumi device driver can be obtained from two sources (maybe more). You can contact either Systems Integration Technologies at (305) 968-4605 or (305) 972-7038, or you can call Computer Discount Warehouse at (800) 800-4239 ext. 265 and speak with Neil. Both offer the driver for a nominal price. ============================================== Non Supported CDROM Information ============================================== When installing OS/2 2.1 from a nonsupported CDROM, the following procedure might work, but cannot be supported by the Support Center. If you have a nonsupported CDROM, the following instructions might allow the CDROM to operate under OS/2. If unsuccessful please contact the manufacturer or supplier of the CDROM. 1. Make the diskettes images from the CD ROM(DOS must be present) Go to the images subdirectory when booted in real DOS and use LOADDSKF to make the diskette images (LOADDSKF filename A:) 2. Disconnect the CD ROM 3. Install OS/2 v2.0 or v2.1 from diskette. 4. Copy devices drivers(ext. .ADD)to \OS2 directory (CD ROM/Sound card). 5. Copy the device drivers for the Controller/Adapter. 6. Connect the CD ROM and plug in Sound Card and Controller/Adapter. 7. Do a Selective install of for CDROM (modifies the CONFIG.SYS) Statements in CONFIG.SYS that should appear: EX: DEVICE=x:\OS2\OS2CDROM.DMD /Q IFS=x:\OS2\CDFS.IFS /Q BASEDEV=<device_driver_name> Where x: is the drive where OS/2 resides ** All device drivers MUST be compatible with OS/2 ** Most vendors will provide the technical support or literature to install on OS/2 if it is not in the supported list. IBM will not supply other suppliers device drivers to ensure that the latest updated drivers are received directly from the source. Please do not request non-IBM drivers from the IBM Support Centers. If you are unsuccessful installing OS/2 2.1 from CDROM on a non-supported CDROM please either contact your manufacturer, make the diskettes from the images on another PC or exchange your CDROM package for the diskette package. =============================================== Installation of Super VGA display drivers. =============================================== Display drivers that typically come from the display card manufacturers are replacements to the DISPLAY.DLL file in the OS2\DLL directory of the partition where you installed (For example, C:\OS2\DLL). To install a replacement display driver, following these steps: 1. From an DOS Full Screen, under OS/2 2.0, run the SVGA utility by typing: SVGA ON (See the OS/2 2.0 readme file for more information on SVGA). 2. Shutdown and reboot from either a DOS diskette (if you have FAT) or from the OS/2 installation diskettes. If you choose to boot from the Installation Diskettes, follow these steps, otherwise skip down to step 3. a.Insert the Installation Diskette into drive A. b.Turn on the computer. If the computer is already on, press and hold Ctrl + Alt and press Del to restart the system. c.When you are prompted to do so, remove the Installation Diskette and insert diskette 1. d.Press enter. e.When the Welcome screen is displayed, press Esc to display the command prompt. 3. Switch to the drive that you installed OS/2 on (i.e., C:)/ 4. Switch to the \OS2\DLL directory (by typing cd \os2\dll), and execute the following step to backup the existing display driver: rename display.dll display.old 5. Copy the new display driver provided by the board manufacturer (filename may vary), into the \OS2\DLL directory with the filename of DISPLAY.DLL. For example, if the filename of the display driver you have is DISP.DRV and is in the \TEMP directory, you would execute the following statement from the OS2\DLL directory: copy \TEMP\DISP.DRV DISPLAY.DLL This will copy DISP.DRV from the \TEMP directory and rename it to DISPLAY.DLL in the OS2\DLL directory since that is where you were when you issued the copy command. ============================================== Diamond Speedstar Adapter ============================================== Recommended video BIOS revision for this adapter is 4.23. Contact Diamond about the BIOS upgrade. ============================================== Diamond Stealth adapter ============================================== This adapter is currently not supported in high resolution mode. This however should not cause installation problems. After the installation is completed, edit the CONFIG.SYS and change the video related statements from SVGA to VGA (refer to the General considerations section for the outline of the VGA support). Recommended video BIOS revision is 2.32 forthis adapter. Contact Diamond about the BIOS upgrade. ============================================== Diamond Speedstar 24X Card Configuration ============================================== The following information is necessary for the proper configuration of the Diamond Speedstar 24X card and the CTX 5648NI monitor. They are incorrectly identified by the OS/2 installation process as an IBM 8514A adapter and a SONY 1302 monitor. One of the following changes must be made to the CONFIG.SYS: SET VIO VGA=DEVICE(BVHVGA,BVHSVGA) DEVICE=C:\OS2\MDOS\VSVGA (Super VGA set) (assuming you have the IBM corrective service update of the file "BVHSVGA.DLL" copied into the C:\OS2\DLL directory) -OR- SET VIO VGA=DEVICE(BVHVGA) DEVICE=C:\OS2\MDOS\VVGA.SYS ( Standard VGA set) (OS/2 2.0 will use standard VGA 640x480x16 mode for DOS, WIN/OS2, and OS/2 screens no matter which set you choose.) Once you make one of the above corrections, there will still be a problem with the WIN/OS2 screen being out of synchronization, off center, and reduced in size. This problem can be corrected by running 24XMODE from a DOS session. Choose "Custom" under monitor selection and use the highest acceptable non-interlaced rate (60-70hz) for 640, 800, and 1024 resolutions; then save the configuration. Add the line "24XMODE MONITOR" to the OS/2 AUTOEXEC.BAT. You must choose "Shutdown" from the workplace Shell to save/reboot so that the changes may take affect. This assumes that the Speedstar 24X utility " 24XMODE.COM" is loaded in the root directory of the boot drive. ============================================== Country.Sys not found message on all Gateway Nomad "notebook" models. ============================================== This is a problem with the BIOS on the Nomad machines according to Bill Williams. Nomad machines with Pheonix 1.02 BIOS will need to be upgraded. The Gateway 2000 Tech support group expects us to send the customer over to them on this problem. ============================================== Gateway machines with a 486 can potential have DIVIDE UNDERFLOW errors. ============================================== This problem is a bug on the 486 math coprocessor and will only be seen if the customer is running software that takes advantage of the coprocessor. The Rev E mother boards of 486 Gateway machines may exhibit this problem. If the customer is running into this problem we can send them to Gateway so they can upgrade to the Rev F version of the mother board. The Rev F board has a HW fix workaround for the coprocessor bug. ============================================== Gateway machines that Trap 2 on boot or install ============================================== This problem could be one of two things. The first is that the Read Ahead Cache on the mother board could be bad. Gateway has seen several cases of this. The workaround for this problem is to disable the external caching. This canbe done by hitting Ctl-Alt-Esc during POST to activate CMOS Setup. The real solution however would be to get another board from Gateway or let them fix the one the customer has. The second thing that could cause the Trap 2 is bad memory. In this case the only thing that will consistently fix the problem is locating the memory sim that is bad and replacing it. Sometimes - just moving the sims around helps though. - For either of the versions of the Trap 2 problems it is also okay to refer them to Gateway. ============================================== 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 install problems ============================================== Problem: FDISK error, hang during install, hang on disk1 or 2. Solutions: Incorrect BIOS date 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 ============================================== AMI SCSI - slow, noisy diskduring install ============================================== 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 ============================================== Colorado Memories Tape Drive attached during install. ============================================== disconnect tape drive during install. fix available from Colorado - ============================================== PROCOMM+ SCSI disk adapters (Microchannel) ============================================== Unsupport SCSI, refer to manufacturer. ============================================== Early versions of IBM 16-bit SCSI adapters ============================================== Update microcode ============================================== Unable to install to 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 Attached ============================================== Need EPROM upgrade - see APAR II06081 ============================================== SUMO SCSI adapters don't seem to work with OS/2 ============================================== Talk to manufacturer ============================================== FDISK problems during INSTALL ============================================== 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) - 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. - IMPROVED SNIFFERS NEEDED !!!!! ============================================== Trying to install over a Beta version of OS/2 2.0 (1.3 is OK) fails ============================================== Reformat first. ============================================== Trying to install HPFS with less than 6M of memory ============================================== Must have 6MB ============================================== Trying to install on less than 4MB ============================================== (User may think he has 4MB, but some cache arrangements or ROM to RAM remapping can steal some) - try to disable these features in CMOS setup. ============================================== 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. ============================================== 1024 Limit Problem during install ============================================== 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. ============================================== Adapter Conflict Problems ============================================== 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. ============================================== 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 adapter, use 8514/A driver for install. ============================================== C0000005 is displayed on the screen during install ============================================== (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 ============================================== Hang on disk 6 during install ============================================== 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. ============================================== IRQ conflicts ============================================== 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 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. ============================================== SYS1200 error when attempting to Dual Boot to DOS with an error code indicating that the DOS environment cannot be created and you see an error code - EC=00BF. ============================================== Ensure that you have not removed or remarked out any of the VIRTUAL DOS device drivers. If all else fails, rename your current CONFIG.SYS to CONFIG.XXX and copy your original CONFIG.SYS to the root directory. The original CONFIG.SYS can be found in the OS2 INSTALL directory. ============================================== Installation on ZEOS notebook fails ============================================== Follow the following steps: The fix for this problem assumes that you have access to a working copy of OS/2 2.0. Ask your local IBM dealer if they can provide an OS/2 2.0 machine for you to use for a few minutes, or ask a friend/co-worker with 2.0 installed. Bring your Installation diskette with you, along with a blank formatted high density 3.5 inch diskette. Step 1. Open the OS/2 System object on the OS/2 Desktop by double clicking with mouse button 1 (usually the left mouse button) Step 2. Open the Command Prompts folder (by double clicking on the folder object). Step 3. Double click on the OS/2 Window Object. Step 4. You should now be at an OS/2 Command Prompt. Step 5. Backup your Installation Diskette to the blank 3.5 inch high density diskette you brought with you. Enter the following command at the pronpt: DISKCOPY A: A:<enter> and follow the prompts. Step 6. With your backup diskette in the drive, enter the fol- lowing: PATCH SYSINSTX.COM<enter> Step 7. When asked for the offset address, enter: 96AF<enter> Step 8. On the line that is shown, enter 45 to replace 44 as the first byte in the line and then press <enter>. Step 9. When asked if you wish to apply patches, answer: Y <enter>. Step 10. At the OS/2 Command prompt again, enter: SYSINSTX A: Step 11. Install OS/2 on your ZEOS using the patched backup Installation Diskette. Step 12. The patch MUST be applied using OS/2. If it is not available, a diskette with the patch applied can be sent to you from IBM. ============================================== Fails to reboot after pressing enter. ============================================== Install requests the user to press enter to reboot at the end of the full screen portion of install, or at the end in the case of a remote install. In some cases this will cause the system to hang. This is a problem in the file system shutdown. WORKAROUND: If the machine does not reboot, try Ctl-Alt-Del, and if this fails power off/on the machine. This should not cause the user any problems, but running a checkdisk after the install completes 'just in case' wouldn't be a bad idea. ============================================== IBM ISA CDROM INSTALLATION FOR OS/2 2.1 ============================================== To properly install this drive you will need the following: 1.The switch settings on the interface card. Refer to your cd-rom manual. 2.The Diskette with the ISACDOS2.ADD driver. 3.The OS/2 diskettes or the CDROM install package. FOR INSTALLATION OF OS/2 2.1 1.Make a diskcopy of OS/2 DISK1. 2.Edit the CONFIG.SYS and add the device driver line. BASEDEV=ISACDOS2.ADD /M:xxx Where xxx is the hex address set on the switches. 3.Start the installation. AFTER OS/2 IS INSTALLED 1.Open the OS/2 SYSTEM ICON. 2.Open COMMAND PROMPTS. 3.Open OS/2 WINDOW. 4.Type E CONFIG.SYS. 5.Add the line BASEDEV=ISACDOS2.ADD /M:xxx Where xxx is the hex address set on the switches. 6.Save and exit. 7.Type exit 8.Close COMMAND PROMPTS. 9.Select SYSTEM SETUP. 10.Select SELECTIVE INSTALL. 11.Put a check mark in the CDROM BOX. 12.Click on OK. 13.This will bring up a list of CDROMS. Select OTHER. 14.Follow the online instructions for the driver installation. 15.SHUT DOWN and REBOOT. Check the DRIVES ICON for the presence of your CDROM. ============================================== Setting up the ATI MACH32 chipset to emulate the IBM 8514, using the IBM 8514 Device drivers. ============================================== Video Cards with the MACH32 Chipset ATI VGA Wonder GT ATI Graphics Ultra Plus ATI Graphics Ultra Pro ATI Ultra Professional Summary for setting up the adapters 1. Setup the ATI Mach32 Card to emulate the 8514 video adapter Select the monitor type as Custom and set the resolutions as follows a. 640x480 - Setup b. 800x600 - NON-SUPORTED (This is not supported!!!) c. 1024x768 - Setup d. 1280x1024 - NON-SUPORTED (This is not supported!!!) 2. Setup the Memory Aperture. a. ISA bus systems 1. Disable, if the system has more than 12MB of RAM 2. Enable, set to 96MB, the apature should show as 100MB b. EISA bus systems 1. Enable, set to 96MB, the apature should show as 100MB 3. Setup the VGA MEMORY a. 1MB of Video RAM on the video card Set VGA MEMORY to SHARED b. 2MB of Video RAM on the vidoe card Set VGA MEMORY to 512K or 1MB 4. Test video card 5. Check system information, for 1MB or 2MB of VRAM 6. Installation of OS/2 Install as a VGA system, then Selective install 8514. * Note: DO NOT run SVGA ON, it does not apply to this adapter!!! If the SVGADATA.PMI file exists delete it!!!! * Note: Monitor must be capable of the higher refresh rates. Check monitor specifications, to be sure DETAIL for setting up the adapters 1. Setup the ATI Mach32 Card to emulate the 8514 video adapter a. Boot off of a DOS diskette, with no memory management programs c. Place the ATI installation diskette in the computer d. Change to the Drive Type A: then press Enter (where 'A' is the drive the disk is in) e. Type INSTALL then press Enter f. Select POWER UP CONFIGURATION g. Select MONITOR TYPE h. Select CUSTOM * Take note of the Warning 1) Select 640X480 a. IBM Default / 60 Hz (whichever is present) 2) Select 800x600 a. Select "NON-SUPPORTED" 3) Select 1024x768 a. Select Highest refresh rate the monitor can handle * For refresh rates, check the monitor specifications b. If, there are no monitor specifications. 1) A good starting point is 72Hz 2) Select the desired refreash reate (72Hz) 3) Adjust the screen via the instructions on the screen * If you can not see the screen press ESC. to return, and select different refreash rate. * The possible refresh rates are 72Hz, 70Hz, 60Hz NonInterlaced, 87.5Hz Interlaced) 4) Continue until the screen is, as desired 4) Select 1280x1024 a. Select "NON-SUPPORTED" i. Press ESC, Hit "Y" to save changes j. Press F10 to save the Changes. 2. Setup the Memory Aperture. a. ISA bus systems 1. Disable, if the system has more than 12MB of RAM 2. Enable, set to 96MB, the apature should show as 100MB b. EISA bus systems 1. Enable, set to 96MB, the apature should show as 100MB 3. Setup the VGA MEMORY a. If 1MB of Video RAM on the video card Set VGA MEMORY to SHARED b. If 2MB of Video RAM on the vidoe card Set VGA MEMORY to 512KB or 1MB 4. Save Settings a. Return to the POWER UP CONFIGURATION menu b. Press F10, monitor will flicker while programming the EPROM. c. Shutdown system then turn system off. Restart system. 5. ESC until the main menu, Select UTILITIES a. Select system information 1) Check for 1MB of video memory, or 2MB (which ever the board has). 2) Press ESC b. Select TEST 1) Select RUN ALL TESTS 2) Select JUST ONCE, for number of times to run tests 6. Shutdown system then turn system off. Restart system. 7. Installation of OS/2 Install as a VGA system, then Selective Install 8514 * Note: DO NOT run SVGA ON, it does not apply to this adapter!!! If the SVGADATA.PMI file exists delete it!!!! 8. If the system is setup improperly. Or is not in the 8514 mode a. Do a selective installation of VGA support, then b. Do a selective installation of 8514 if the higher resolution is desired, and supported (at least 1MB of VRAM and a monitor which will support the higher resolution). * Note: Monitor must be capable of the higher refresh rates. Check monitor specifications, to be sure ============================================== Setting up adapters with the MACH8 chipset to emulate the 8514, using the IBM 8514 drivers ============================================== Video Cards with the MACH8 Chipset ATI Ultra ATI Graphics Vantage ATI 8514 Ultra Summary for setting up the Adapter 1. Setup the ATI Mach8 Card to emulate the 8514 video adapter Select the monitor type as Custom and set the resolutions as follows a. 640x480 - Setup b. 800x600 - NON-SUPORTED (This is not supported!!!) c. 1024x768 - Setup d. 1280x1024 - NON-SUPORTED (This is not supported!!!) 2. Test video card 3. Check system information, for 1MB of VRAM 4. Installation of OS/2 Install as a VGA system, then Selective install 8514. * Note: DO NOT run SVGA ON, it does not apply to this adapter!!! If the SVGADATA.PMI file exists delete it!!!! * Note: Monitor must be capable of the higher refresh rates. Check monitor specifications, to be sure Details for setting up the Adapter 1. Setup the ATI Mach8 Card to emulate the 8514 video adapter a. Boot off of a DOS diskette, with no memory management programs c. Place the ATI installation diskette in the computer d. Change to the Drive Type A: then press Enter (where 'A' is the drive the disk is in) e. Type INSTALL then press Enter f. Select POWER UP CONFIGURATION g. Select MONITOR TYPE h. Select CUSTOM * Take note of the Warning 1) Select 640X480 a. IBM Default / 60 Hz (whichever is present) 2) Select 800x600 a. Select "NON-SUPPORTED" 3) Select 1024x768 a. Select Highest refresh rate the monitor can handle * For refresh rates, check the monitor specifications b. If, there are no monitor specifications. 1) A good starting point is 72Hz 2) Select the desired refresh rate (72Hz) 3) Adjust the screen via the instructions on the screen * If you can not see the screen press ESC. to return, and select different refreash rate. * The possible refresh rates are 72Hz, 70Hz, 60Hz NonInterlaced, 87.5Hz Interlaced) 4) Continue until the screen is, as desired 4) Select 1280x1024 a. Select "NON-SUPPORTED" i. Press ESC, Hit "Y" to save changes j. Press F10 to save the changes, monitor will flicker while programming the EPROM. k. Shutdown system then turn system off. Restart system. 2. ESC until the main menu, Select UTILITIES a. Select system information 1) Check for 1MB or 1.5MB of video memory. 2) Press ESC b. Select TEST 1) Select RUN ALL TESTS 2) Select JUST ONCE, for number of times to run tests 3. Shutdown system then turn system off. Restart system. 4. Installation of OS/2 Install as a VGA system, then Selective Install 8514 * Note: DO NOT run SVGA ON, it does not apply to this adapter!!! If the SVGADATA.PMI file exists delete it!!!! 8. If the system is setup improperly. Or is not in the 8514 mode a. Do a selective installation of VGA support, then b. Do a selective installation of 8514 if the higher resolution is desired, and supported (at least 1MB of VRAM and a monitor which will support the higher resolution). * Note: Monitor must be capable of the higher refresh rates. Check monitor specifications, to be sure ============================================== Information on MITSUMI CD-ROM Device Drivers for OS/2. ============================================== The Mitsumi model CD-ROM players are not supported for use with OS/2. However, you can obtain device drivers that may allow the device to work. If you need such drivers, the following may be contacted for assistance: IBM National Support Center BBS (919) 517-0001 This driver is available free of charge. The name of the file is MITFX.ZIP. This driver works only for the Mitsumi models FX001, FX001D, and LU005 CD-ROM players. If you do not have one of these models, you may need to contact the other references listed below. Installation instructions are outlined in the README file supplied in the ZIP package. Systems Integration Technologies 1280 South Powerline Road Suite 171 Pompano Beach, FL 33069 Tel: (305) 968-4605 (305) 972-7038 Computer Discount Warehouse C/O Neil no address available Tel: (800) 800-4239 ext. 265 Both of these supply the necessary drivers for a minimal price. Other sources may have the drivers as well, but no information is available at this time. Until these drivers are acquired, the CD-ROM cannot be used with OS/2. If you have any questions or require additional assistance, please call (800) 992-4777. Please keep in mind that our assistance with Mitsumi CD-ROM units is limited, as it is an unsupported unit. ============================================== Installing support for Multimedia CD-ROM packages (Media Vision Pro Audio Spectrum, Creative Labs Sound Blaster) ============================================== These multimedia packages are unsupported through the IBM OS/2 Technical Support Center, but we have had some success with installing support for the Sound Blaster and Pro Audio Spectrum SCSI interfaces. Before proceeding with this setup, you need to obtain the OS/2 Device Drivers from the respective manufacturers. Windows and DOS drivers are not compatible with OS/2. The OS/2 drivers can be obtained from these areas: Creative Labs -- BBS (405) 742-6660 (2400 baud, 8 bits, no parity, 1 stop bit) Files can be found in the OS/2 Audio and CD-ROM Drivers section. They are: for single-speed CD-ROMs, you need CLIOS2CD.ZIP for double-speed CD-ROMs, you need SBCD2.ZIP also, Presentation Manager programs are in SBMMPM2.ZIP For help un-zipping these files, you can look in the New Users directory online. Media Vision -- BBS (510) 770-0968 (2400 baud, 8 bits, no parity, 1 stop bit) (510) 770-1661 (2400 baud, 8 bits, no parity, 1 stop bit) (510) 770-0527 (9600 baud, 8 bits, no parity, 1 stop bit) The file you need is called TMV1SCSI.ZIP. It contains the driver file and also a mixer program and readme file for more information. It can be found in the OS/2 section online. * * * * * Two methods are available. If you have installed OS/2 on your system and wish to add CD-ROM support with one of these packages, skip to step 2. If you want to install from the CD-ROM, use both of these proceedures. 1. Installing from the CD-ROM Make a backup copy of diskette 1 of the OS/2 2.1 installation package. We recommend using the DISKCOPY command, as this will make an exact duplicate of the disk. If you must use the COPY command, make sure that you copy every file and change the volume label of the destination disk to "DISK 1" (do not include the quotes in the volume name). Next, some files will need to be deleted from the backup copy you just created. Good targets for deletion would be the Adaptec and Future Domain SCSI drivers following: AHA152X.ADD AHA164X.ADD FD16-700.ADD FD7000EX.ADD AHA154X.ADD AHA174X.ADD FD8XX.ADD Then copy the manufacturer-supplied driver onto your copy of diskette 1. Next, edit the config.sys on diskette using any plain text editor toinclude the following statements: Lowercase will represent lines that already exist; CAPS represent lines you need to insert. This is to insure proper placement and installation. set cdrominst=1 ifs=cdfs.ifs /q BASEDEV=TMV1SCSI.ADD *** or substitute your driver filename *** Then, delete or REM any BASEDEV statements referring to the filenames which were deleted in the preceeding step (the Adaptec and Future Domain device drivers). REM-ing these statements is recommended for easier recognition of the changes made. From there, you may attempt the installation. If successful, you can go on to step 2. If not, you will need to create the installation disks from the CD "disk images" and install from the floppies. The proceedure for this is explained in your OS/2 Version 2.1 package. 2. Installing CD-ROM support after OS/2 2.1 is installed. Once OS/2 2.1 is installed, you need to make some changes to the CONFIG.SYS located in the root directory of the OS/2 partition in order to make your CD-ROM accessible. For demonstartion purposes, X: will represent the OS/2 partition. First, copy the following files to X:\OS2. These files are located in the following places according to the OS/2 package you own: CD-ROM Installation package ................... Diskette 1 3.5 Diskettes, Blue Label on disk ............. Diskette 10 (packed) 3.5 Diskettes, Salmon Label on disk ........... Diskette 12 (packed) 5.25 Diskettes, Blue Label on disk ............ Diskette 16 (packed) 5.25 Diskettes, Salmon Label on disk .......... Diskette 9 (packed) The files are named OS2CDROM.DMD and CDFS.IFS. If the files are on a "packed" disk, the syntax for unpacking the files is as follows: UNPACK A:\CDROMREQ /N:OS2CDROM.DMD UNPACK A:\CDROMREQ /N:CDFS.IFS Once these are copied, copy the manufacturer-supplied device driver to the X:\OS2 directory as well. From there, you need to edit the config.sys using a plain text editor. For example, to use the OS/2 system editor, open an OS/2 Window and type from the X:\ prompt: E CONFIG.SYS Once the editor is displayed, make the following changes. Lowercase will represent lines that already exist; CAPS represent lines you need to insert. This is to insure proper placement and installation. basedev=ibm1s506.add basedev=os2dasd.dmd DEVICE=X:\OS2\OS2CDROM.DMD /Q IFS=X:\OS2\CDFS.IFS /Q set bookshelf=x:\os2\book . . . further down . . . codepage=437,850 devinfo=kbd,us,x:\os2\keyboard.dcp BASEDEV=TMV1SCSI.ADD *** or your device driver filename *** devinfo=scr,vga,x:\os2\viotbl.dcp . . . Once these changes are complete, save the file and exit the editor. Then perform a shutdown and restart your computer to install the support. Once again, this support is not guaranteed to work in any case, since the drivers are made by other manufacturers. IBM does not supply these drivers at this time, but may in the future. For further assistance, you can contact the manufacturer of your device at the above listed phone numbers. ============================================== Microsoft MS-DOS 6.2 upgrade and OS/2 . . . ============================================== Before starting the upgrade, please refer to the Getting Started book with MS-DOS 6.2. Installing the upgrade on an OS/2 DUAL BOOT system: The MS-DOS 6.2 upgrade must be installed while DOS is the current operating system. If you are running OS/2 as the current operating system, the steps below should be taken: (1.) Boot to DOS by opening an OS/2 Window and typing: BOOT /DOS (2.) Once the boot procedure is complete, place the MS-DOS 6.2 upgrade diskette in the appropriate drive and type: A:SETUP (if the diskette is in the A: drive) or B:SETUP (if the diskette is in the B: drive) (3.) After a proper upgrade has been completed, please review the CONFIG.SYS and AUTOEXEC.BAT files for the proper OS/2 statements. If they are not there, please refer to the Installation Guide and place the statements as necessary. (4.) After these statements have been verified, dual boot should function as before. To return to OS/2, type: C:\OS2\BOOT /OS2 ============================================== Installing the upgrade on an OS/2 BOOT MANAGER system: ============================================== The MS-DOS 6.2 upgrade must be installed while DOS is the current operating system. If you are running OS/2 as the current operating system, the steps below should be taken: (1.) Complete a proper shutdown of OS/2 by placing the mouse cursor on the desktop and pressing your right mouse button. When the "pop-up" menu has appeared, choose Shutdown from the menu. Follow the instructions until the system has told you it is safe to turn of the system or reboot. Rather than turn the machine off, execute a warm boot by pressing CTRL - ALT - DEL. (2.) When the Boot Manager menu appears, choose to boot to the DOS partition. (3.) Once the boot procedure is complete, place the MS-DOS 6.2 upgrade diskette in the appropriate drive and type: A:SETUP (if the diskette is in the A: drive) or B:SETUP (if the diskette is in the B: drive) (4.) Once the upgrade has completed, use the DOS FDISK program to set the Boot Manager partition as ACTIVE, or refer to page 132 of the OS/2 2.1 Installation Guide on "making boot manager startable." If any problems occur while trying to upgrade to MS-DOS 6.2, please refer to Microsoft Technical Support. ============================================== How to set up OS/2 for Windows for HPFS only? ============================================== Details of Question: User has OS/2 For Windows and would like to set up the system for HPFS only. Answer Summary: The issue is that in order to enable Windows application support under OS/2 for Windows, real Microsoft Windows 3.1 must be installed. Windows 3.1 will not install under OS/2, only DOS. Since DOS cannot see or access HPFS drives, the problem is how to get Windows 3.1 on an HPFS drive. The user can install DOS and Windows, back up the Windows code to diskettes, install OS/2 for Windows, then restore the Windows code from diskettes, then use selective install from OS/2 to add the Windows application support. NOTE: IBM cannot authorize you to make a backup copy of non-IBM supplied code. If you wish to use this method, you are responsible for ensuring you have the right to make a backup copy of Windows 3.1. If you are unsure, please consult your license agreement for the product or contact the vendor. Detailed Answer: 1. Make sure your system has DOS and Windows 3.1 on it. 2. Back up to diskette the subdirectory(ies) that contain the Windows code only. There is no need to back up the DOS code, since you will not need it in this all-HPFS configuration. PLEASE REFER TO THE NOTE ABOVE. 3. Install OS/2 for Windows, choosing to reformat the partition with HPFS. 4. Create the appropriate directory on the target drive, and restore the Windows 3.1 code from diskettes. 5. Open the OS/2 System folder, then the System Setup folder, and start Selective Install. 6. Follow the steps to install Windows application support. ============================================== After installing OS/2 for Windows, the mouse does not work at all. ============================================== Details of Question: User installed OS/2 for Windows. After rebooting the system, the mouse does not work. When booting to DOS, the mouse works fine. Answer Summary: Sometimes if there is a DOS-based mouse device driver installed, the OS/2 mouse device driver does not get copied over. The solution is to unpack and copy over the OS/2 mouse device driver. Detailed Answer: The OS/2 mouse device driver can be found on diskette 1 of the installation package. 1. Copy the file MOUSE.SYS from the installation diskette 1 to the \OS2 directory on the boot drive. 2. The line containing MOUSE.SYS should be in the OS/2 CONFIG.SYS file. In any case, you will need to reboot the system for the device driver change to take effect. If it is not, use selective install to reinstall the mouse device driver support. a. Open the OS/2 System folder, then the System Setup folder, then open the Selective Install item. b. The first screen will indicate mouse support. Select the one appropriate for the user's hardware and select the OK pushbutton, then select the Install pushbutton and let the mouse device support reinstall itself. c. You must reboot the system for this change to take effect. ============================================== I have Windows 3.1. It was installed from a CD-ROM. When I install OS/2 for Windows, it tries to find disk #7 on the CD. It is not there. How can I fix this? ============================================== User installed Windows from a CD-ROM. During the installation of OS/2 for Windows, OS/2 asks for the Windows diskettes, but is treating the images on the CD as 5.25 inch images, where there are 7 diskettes. There is no 7th image on the CD. The user will either have to obtain a diskette #7, or fake out the installation program. Detailed Answer: There are 3 possibilities to fixing this situation: 1. Obtain a Windows 5.25 inch diskette #7. 2. Install Windows 3.1 from a floppy disk. Then use the floppies during OS/2 for WIndows installation. 3. Create a "fake" diskette #7. This can be done by: a. Format a blank 5.25 inch diskette. b. Use the LABEL program to label it DISK7, according to the Microsoft Windows diskette labels. c. Copy the files from diskette 6 from the CD to this diskette and use it when the installation program asks for diskette #7. ============================================== Installing with Paradise EGA 480 ============================================== This board is capable of higher, non-EGA resolution modes. Our drivers do not support these modes. In order to install properly with this adapter, set all dip switches to OFF, with the exception of switches number 2 and 3. The two switches that are causing the problems are switch #5 (auto switch capability) and switch #6( monitor sense switch). ============================================== Paradise VGA+, VGA Pro and VGA 1024 ============================================== These boards have problems installing OS/2. These are all 8/16 bit boards, with an autosense switch used for detection of the bus width. OS/2 will successfully install only if this capability is disabled. Set the dip switch to OFF or insert the board into an 8 bit slot. After you have successfully installed OS/2, you may put the board back into 16 bit bus mode. ============================================== Paradise VGA Accelerator ============================================== This board is based on the WD90C30 and WD90C31 chipsets with 1MB of video RAM and will have problems installing OS/2. After the first five diskettes, error message C000005 appears during the reboot. An official fix for BVHSVGA.DLL driver is available which will fix the problem. Call the 800 tech support line and request to be mailed a fix for APAR PJ03721. The fix is shipped with instructions on how to install the upgraded driver. There are a number of other video and motherboard manufacturers that are using Western Digital/Paradise chipsets. 8/16 bit chipsets are PVGA1A and PVGA1B, aka WD90C00. For boards built with these chipsets, apply the autosense OFF fix for the successful i nstallation. Boards using WD90c30 and c31 experiencing the C000005 error should apply PJ03721 fix. If you have installed successfully but experience video corruption problems when switching back into a previously opened WIN-OS2 session, set DOS parameter VIDEO_SWITCH_NOTIFICATION to ON in the DOS settings for the WIN-OS2 session in question. You can reach the settings screen by clicking with the right mouse button over the session icon and opening Settings notebook, Session page. If there are synch problems on the desktop with higher resolution adapters, check if the SVGA support has been successful ly installed and activated. OS/2 installation detects if the video adapter has higher-resolution capabilities and if so, specifies SVGA basic video support in the CONFIG.SYS. This support is currently limited to DOS session and VIO subsystem only. In order to activate the support, SVGA ON command must be issued from a DOS full screen session and the system should be shutdown after that. This will create a configuration file called SVGADATA.PMI in the OS2 directory. If you are not interested in the SVGA su pport, you may correct your CONFIG.SYS to indicate VGA support only. CONFIG.SYS statements for SVGA support are: SET VIO_VGA=DEVICE(BVHVGA, BVHSVGA) DEVICE=x:\OS2\MDOS\VSVGA.SYS (where x is your OS/2 system drive letter.) VGA support CONFIG.SYS statements are: SET VIO_VGA=DEVICE(BVHVGA) DEVICE=x:\OS2\MDOS\VVGA.SYS (where x is your OS/2 system drive letter.) If after the PMI file is generated, some of the high resolution modes in your DOS have video problems, you may consider regenerating the PMI file. First remove the \OS2\SVGADATA.PMI file. Locate a DOS mode changing utility that was shipped with the adapt er and run it in OS/2 DOS full screen session. Select the desired video mode and exit the utility. Run SVGA ON immediately after and reboot. This should ensure that timing information in the PMI file is correct for your adapter. ============================================== Using a RESPONSE FILE to install OS/2 OS/2 2.1, 3.5 blue diskettes/CD too complicated, too manual ============================================== WARNING: Make ALL install selections in response file BEFORE the installation. ********************************************************************* COPYING THE RESPONSE FILE TO DISK #1 ____________________________________ The following is a list of the steps you would perform to modify a response file and then place that response file on a copy of disk #1. This procedure requires UNPACK-ing compressed files. To do this, copy UNPACK.EXE from Diskette #2 of the OS/2 package to your hard drive. Any reference to UNPACK should be performed from the hard drive. To copy the response file onto a diskette, you must make some modifications to disk #1. These modifications make room on the diskette for the response file. 1.) Make a copy of disk #1. You will modify the copy only. DISKCOPY A: A: (to use the same drive as source and destination) DISKCOPY A: B: (to use different drives as source and destination) 2.) Make extra room on the copy of disk #1 by deleting files that will not be needed in a response file installation. a.) Delete the MOUSE.SYS file from the copy of disk #1 b.) Delete the BUNDLE file from the copy of disk #1 NOTE: This step is not necessary for CD-ROM installations. c.) Delete the SYSINST2.EXE file from the copy of disk #1 d.) If you are installing OS/2 2.1 on a Micro Channel(*) computer, delete the following file from your copy of disk #1: DEL IBM1*.ADD e.) If you are installing OS/2 2.1 on a non-Micro Channel computer, delete the following files from your copy of disk #1: DEL IBM2*.ADD f.) Edit the CONFIG.SYS 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:\OS2SE20.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 in the CONFIG.SYS file on the copy of disk #1. BASEDEV=IBM1FLPY.ADD BASEDEV=IBM1ADSK.ADD BASEDEV=IBM1SCSI.ADD 3.) Make a copy of the SAMPLE.RSP file, located in a compressed file named REQUIRED on disk #13 that has to be unpacked and then copied to the copy of disk #1: UNPACK A:\REQUIRED C:\ /N:SAMPLE.RSP This will place the file in the root directory of the C: drive. 4.) 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. 5.) Copy the modified response file to the copy you made of disk #1. Use the name OS2SE20.RSP when you copy the file: example: COPY C:\SAMPLE.RSP A:\OS2SE20.RSP 6.) Copy the RSPINST.EXE File, located in a compressed file named REQUIRED on disk #7 that has to be unpacked and then copied to your copy of disk #1: UNPACK A:\REQUIRED C:\ /N:RSPINST.EXE This will place the file in the root directory of your C: drive. 7.) Begin the installation of the workstation by inserting the installation diskette and restarting the system. 8.) When prompted for disk #1, insert the modified copy of disk #1 and press enter. From this point, the installation program will ask only for the insertion of diskettes. No other installation actions will be necessary. NOTE: When prompted to insert disk #1 again, insert the original disk #1 into drive a: Response files can be used to install the same set of options on multiple workstations. Ensure that the workstations are set up with the same set of options and hardware. ************************************************************************* ============================================== What to try if the installation hangs on or after either the Blue Disk #17 or the Salmon Disk #13: ============================================== Sometimes near the end of the installation, the system will hang and all system activity will freeze. If this happens, all hope is not lost! A workaround is available to get the system up and running. At this point, enough of the system has been loaded to get up to the desktop. The only things missing are the VIDEO statements in the CONFIG.SYS file on your hard drive. To create these statements . . . NOTE: If you installed your system from a CDROM, you will need to look at step #5 before beginning. (1) Place the Installation Diskette in the A: drive and reboot the system. If the keyboard is locked up, you may need to hard boot the system (turn it off, and then back on). (2) When prompted to insert Diskette 1, do so and press ENTER. This should display the "logo screen" and begin loading the system. (3) When the "welcome screen" is displayed, you will have the option of pressing either ENTER to continue, or ESC to cancel the install. YOU MUST PRESS ESC TO PERFORM THE WORKAROUND!!! (4) When the A:\> prompt is displayed, take the following steps: (a) Change to the drive on which OS/2 resides (C:, D:, etc...) (b) Change Directory to the \OS2 directory on your hard drive. EXAMPLE: CD \OS2 (c) Type: DIR *.* > SVGADATA.PMI (d) Type: SETVGA <d>: Where <d> is the Drive on which OS/2 resides. (5) Once SETVGA.CMD starts, it will ask you for Display Driver Disk 1. If you installed from CDROM, you must create this diskette. This can be done by typing from the prompt: <cd>:\DISKIMGS\LOADDSKF <cd>:\DISKIMGS\OS2\<size>\DISP1.DSK A: Where <cd> is the letter of your CDROM drive and <size> is the size of your diskette (35 for 3.5" disks, 525 for 5.25" disks). Once this process has completed, you can reboot the system to get to the desktop. Once there, go to an OS/2 Window and type DSPINSTL to install your video adapter and correct resolution for your video. Then, shutdown and reboot again, and do a Selective Install for your printer and WIN-OS2 support. If this is unsuccessful, you can also try a few other things . . . (1) Check in the \OS2\DLL subdirectory for the following files and status: a. IBMVGA32.DLL 42378 4-22-93 3:54P b. IBMDEV32.DLL 85326 4-22-93 4:08P c. BVHVGA.DLL 40892 4-25-93 4:04P d. DISPLAY.DLL 77120 4-29-93 9:24P If these files are not on your hard drive, you can get them by unpacking them from Display Driver Diskette #1 by placing the disk in your A: drive and typing: (from the c:\> prompt) \OS2\UNPACK A:\VGA The next step depends on which installation method you are using. If you have the 3.5 disks, you need either diskette #2 if the labels are blue, or diskette #3 if the labels are salmon. If you have 5.25 disks, you need diskette #4. If you have the CD, these files will be in a directory rather than on a physical disk. Once you have the proper disk, type the following: (Example: from the c:\> prompt) \OS2\UNPACK A:\BUNDLE /N:DISPLAY.DLL This will place these files on your hard drive in the \OS2\DLL subdirectory. Once those files are there, use a plain-text editor to check the CONFIG.SYS file on your hard drive for the following statements: DEVINFO=SCR,VGA,x:\OS2\VIOTBL.DCP SET VIDEO_DEVICES=VIO_VGA SET VIO_VGA=DEVICE(BVHVGA) DEVICE=x:\OS2\MDOS\VVGA.SYS Where x: is the partition on which OS/2 resides. ============================================== Installing with the Sony 31A CDROM ============================================== This CDROM is a non-supported, non-SCSI CDROM. If you follow the steps listed in this document, you should be able to use the Sony 31A both to install OS/2 and as a CDROM device from the OS/2 desktop. NOTE: Before starting the steps listed below, you need to get the correct device driver for your CDROM. The IBM National Support Center BBS number is (919) 517-0001, and the driver file is called SONY31A.ZIP. You will need a copy of PKUNZIP to un-zip the driver package. For installing support for the CDROM as an installation drive for OS/2, follow Parts A and B. For just adding support after OS/2 installation is complete, skip Part A and go immediately to Part B. ***** PART A ***** (1.) Make a DISKCOPY of the OS/2 Diskette #1. You will modify the copy and use it for the installation of OS/2. (2.) Use a plain-text editor to modify the CONFIG.SYS on your copy of Diskette #1. Look for a statement that reads: BASEDEV=AHA152X.ADD Directly ABOVE that statement, include your Sony 31A device driver as a BASEDEV: BASEDEV=SONYB31A.ADD (3.) Copy the driver onto your copy of Diskette #1. (4.) Use the copy of diskette #1 to install OS/2, and begin the install as normal. (5.) Once installed, the CDROM will not show up in your Drives Icon View, and cannot be accessed via command prompt. To fix this, please follow the steps outlined in Part B. NOTE: If you performed the steps above and the installation continued to fail, you will have to install using the floppy diskettes. You can use the CD through DOS to create the installation diskettes. This fax document is available through the Support Center at (800) 992-4777. This will be your only option, and the technical support representatives will not be able to assist you any further regarding the installation from this CDROM. It is unsupported, and may not work in EVERY case. ***** PART B ***** (1.) Boot up under OS/2. Once there, use an OS/2 Window (command prompt) to edit the CONFIG.SYS on your hard drive. Type: E CONFIG.SYS (2.) Once in the editor, look for a statement that reads: DEVINFO=KBD,US,X:\OS2\KEYBOARD.DCP (Where X: is the partition letter of your OS/2 system.) (3.) Directly below that statement, add the following line to the CONFIG.SYS on your hard disk: BASEDEV=SONYB31A.ADD (4.) Once these changes have been made, save the file and exit the editor. If it asks you to select a file type, choose "Plain Text" as the file type. (5.) Now all that remains is physically putting the drivers on your hard drive. The required files are OS2CDROM.DMD, CDFS.IFS, and SONYB31A.ADD. These all must be copied into the \OS2 directory on your hard drive. The first two files can be obtained by performing a Selective Install of your CD-ROM. a. Double-click the OS/2 System folder. b. Double-click the System Setup folder. c. Double-click the Selective Install object. d. On the system configuration screen, place a check mark in the box beside CD-ROM Device Support, and then click the OK button. e. Scroll to the bottom of the Select CD-ROM Device(s) listing and choose "Other", and then click the OK button. f. Once you return to the system configuration screen, click the OK button. g. The next screen is to install additional features. Since they do not relate to the CD-ROM install, click the Install button to proceed. h. Follow the instructions given, and this will add the other necessary files to the hard drive. Be SURE you have copied the SONYB31A.ADD file into the \OS2 directory on your hard drive. (6.) Perform a proper SHUTDOWN of your desktop and reboot. When the desktop comes up, use the Drives Icon View (OS/2 System folder) to check your CDROM. ============================================== The following IDE controllers made by Adaptec are not supported: ============================================== ACB-2320 ACB-2322 ACB-2320A ACB-2322A ACB-2322B ACB-2322B-8 ACB-2620 ============================================== Can not install wiht AOX Micromaster 486/33 ============================================== Disable the board and then install, the boards works fine once OS/2 is installed. ============================================== Installing 2.1 over another version of OS/2 and various devices to not work after install. ============================================== 2.1 REM's out line in config.sys it does not understand. Usually unremm'ing the lines works unless the existing driver does not work with OS/2 2.1. Recommend contacting manufacturer of the program or device for an updated driver. ============================================== OSO001.MSG message not found while on disk1 during initial install ============================================== Kernal can not find CDROM drive 1. Check CDROM drive for CDROM present 2. Unrecognized CDROM, SUPPORTED DRIVERS? 3. Unrecognized SCSI adapter (TRANTOR, Ultrastor) ============================================== OS/2 2.1 and do NOT install WIN-OS/2 or DOS Support and system does not boot after install ============================================== REM out DEVICE=X:\OS2\MDOS\VVGA.SYS ============================================== Failure on install diskette, disk1, disk2 ============================================== 1. Ensure floppy drive is jumered for AT mode 2. Make sure the BIOS hasn't been modified by the motherboard manufacturer and had change line support enabled. PJ05147 corrects this problem. 3. Disable CACHE ============================================== Failure after DISKETTE 5 ============================================== Video mode may have been incorrectly identified Disk type may have been incorrectly identified ============================================== Failure after DISKETTE 6 ============================================== ON some OEM machines unpack will go into a tight loop and hang install. Usually restarting installation fixes problem. ============================================== Hang on Disk #17 or after workaround ============================================== 1. Reboot with install disk, disk1 and then ESC to A prompt 2. Type X: were x=drive installed 3. Type CD\OS2 4. Type DIR *.* >SVGADATA.PMI 5. Type SETVGA (it will ask for display disk1, if installing from CDROM make the disk image using LOADDSKF as documented) 6. Reboot 7. After desktop, go to OS/2 window and type DSPINSTL for correct resolution 8. Reboot 9. Do a selective install for printer and WIN-OS2 support