|
23.269 bytes |
Service Hints & Tips |
Document ID: DSHY-3V2KCD |
Cross Brand - Installing OS/2 Warp
Applicable to: World-Wide
Although the installation of OS/2 Warp has been vastly improved over OS/2 V2.x, there are times when the process does not go as smoothly as hoped.
If the system hangs during the stage when it is loading the drivers, then there is a very useful function to find what is causing the problem. When the system starts to load OS/2 Warp, a white box is displayed in the top left of the screen. At this point, if you press Alt + F2 the system will display the name of the drivers as they are loaded. It is now possible to determine which driver is causing the problem. The next step is to edit the CONFIG.SYS file on Disk 1 and 'REMARK' out the offending driver.
The following table is a list of the drivers that OS/2 Warp tries to load during install. This information is taken from the CD-ROM DISK 1, as this loads the same drivers as the disk version plus the CD-ROM drivers.
basedev=print01.sys Printer port Required
basedev=ibmkbd.sys Keyboard Required
basedev=ibm1flpy.add ISA floppy Required
basedev=ibm1s506.add IDE, ESDI, ATAPI drives Required
basedev=ibm2flpy.add MCA floppy Required
basedev=ibm2adsk.add MCA embedded ESDI controller Not required on ISA machines
basedev=ibm2scsi.add MCA SCSI Not required on ISA machines
basedev=ibmint13.i13 Generic INT13 HDD If HDD not found by ibm1s506
basedev=os2dasd.dmd Drive manager Required
device=\testcfg.sys Used by migrate Required
basedev=xdfloppy.flt Filter to read XD floppies Required
ifs=cdfs.ifs CD-ROM filing system Required
basedev=aha152x.add Adaptec 152x SCSI cards Optional
basedev=aha154x.add Adaptec 154x SCSI cards Optional
basedev=aha164x.add Adaptec 164x SCSI cards Optional
basedev=aha174x.add Adaptec 174x SCSI cards Optional
basedev=aic7770.add Adaptec 7770 SCSI cards Optional
basedev=aic7870.add Adaptec 7870 SCSI cards Optional
basedev=btscsi.add BusTech SCSI cards Optional
basedev=fd16-700.add Future Domain FD16-700 SCSI cards Optional
basedev=fd8xx.add Future Domain FD8xx SCSI cards Optional
basedev=fd7000ex.add Future Domain FD7000 SCSI cards Optional
basedev=dpt20xx.add DPT SCSI cards Optional
basedev=chincds1.flt Chinon SCSI CD-ROM filter Optional
basedev=hitcds1.flt Hitachi SCSI CD-ROM filter Optional
basedev=neccds1.flt NEC SCSI CD-ROM filter Optional
basedev=sonycds1.flt Sony SCSI CD-ROM filter Optional
basedev=toshcds1.flt ToshibaSCSICD-ROMfilter Optional
basedev=ibmidecd.flt IBM IDE CD-ROM filter Optional
basedev=tmv1scsi.add Trantor SCSI card Optional
basedev=sony535.add Sony 535 CD-ROM Optional
basedev=sony31a.add Sony 31A CD-ROM Optional
basedev=lms206.add Phillips LMS 206 CD-ROM Optional
basedev=mitfx001.add Mitsumi CD-ROM Optional
basedev=sbcd2.add Panasonic CD-ROM Optional
basedev or device=os2cdrom.dmd CD-ROM drive manager Required
The most common problem you are likely to encounter is that the OS/2 Warp install disks will not recognise the CD-ROM attached to your system. This will probably be due to the fact that the base address used for the drive is different from the default. If the switch /V is placed after the device driver name, then the system will show details of any device found when the driver is loaded.
Note: for SCSI CD-ROM owners BOTH the SCSI card and the CD-ROM have to be supported in the CONFIG.SYS file.
Should you have a supported drive that is not recognised you can use a standard DOS or Windows text editor to modify the OS/2 CONFIG.SYS according to the information given below. If you do not know the address used for your CD-ROM drive then look in the DOS CONFIG.SYS and locate the DEVICE= line for your drive. This line should contain any optional parameters, the most common being /P:xxx where xxx is the CD-ROM base address.
It is advisable to make a backup copy of Disk 1 and make any changes to this disk.
o Sony 535
The OS/2 device driver SONY535.ADD supports the following drives:
o Sony CDU-531
o Sony CDU-535
o Sony CDU-6201
o Sony CDU-6205
o Sony CDU-7205
The following switches are available for this driver:
/P: nnn To set the port address of the interface card
/l: xx To set the IRQ of the interface card
/U: d To indicate the Unit ID of the connected CD-ROM drive; the default for this setting is 0
/V Verbose information when loading the driver.
o Sony 31A
The OS/2 device driver SONY31A.ADD supports the following Non-SCSI CD-ROM drives:
o Sony CDU-31A
o Sony CDU-33A
o Sony CDU-7305
o Sony CDU-7405
The SONY CDB-334 host adapter supports base I/O addresses of 320h, 330h, 340h or 360h. If the adapter is set to the default address of 340h then the BASEDEV line need not be modified. If the address is set to any other than the default then the CONFIG.SYS needs to be changed. For example if the host adapter is set to a base address of 360h the line should read:
basedev=sony31a.add /A:0 /P:0360
If the Sony CD-ROM drive is connected to a Media Vision Proaudio Spectrum 16 host adapter then the BASEDEV line must be modified and should appear as follows:
basedev=sony31a.add /A:0 /AT:08
If the SONY CD-ROM drive is connected to a Sound Blaster interface card that is set to a base I/O address of 220h then the line in CONFIG.SYS should read as follows:
basedev=sony31a.add /A:0 /P:0220
o Phillips LMS Series CD-ROM Drives
The OS/2 device driver LMS205.ADD supports the LMS series CD-ROM drives.
Should your CD-ROM not be recognised it may be necessary to modify the BASEDEV line in your CONFIG.SYS to set the address to the base address used by your host adapter. For example, if your drive is connected to a host adapter set to base address 320h then the BASEDEV line should read:
basedev=LMS206.add /P:320 /V
o Mitsumi
The OS/2 device driver MITFX001.ADD supports the new FX series of Mitsumi drives: the single speed CRMC-FX001 and the double-speed CRMC-FX001D. The device driver also supports the older Mitsumi CRMC-LU005 and CRMC-LU002 (also known as the Tandy CDR-1000 or BSR-6800).
The Mitsumi host adapter supports I/O port address ranges from 300h to 3FCh. The default address for the interface card is 300h and, in this case, no modifications are required. If the host adapter is set to an address other than this, then the BASEDEV statement needs to be modified. For example, if the address is set to 340h then the line in CONFIG.SYS should read:
basedev=mitfx001.add /P:340
The Mitsumi CD-ROM may also be connected to a Sound Blaster 16 MultiCD. However the same address parameters apply.
Another useful parameter which can be used is /V which reports a message that the driver has found the CD-ROM at time of loading.
For example,
basedev=mitfx001.add /P:340 /V
o Panasonic
The OS/2 device driver SBCD2.ADD supports the following drives:
o Creative Labs OmniCD
o IBM ISA CD-ROM Drive
o Panasonic CR-521,522,523,562,563
If the CD-ROM is connected to a Creative Labs Sound Blaster Pro, Sound Blaster 16 or Sound Blaster 16 MultiCD then the base address should be set to that of the Sound Card.
For example:
basedev=sbcd2.add /P:220
If the CD-ROM is connected to a standard Panasonic or IBM host adapter, these adapters support base I/O addresses of 300h,310h, 320h or 330h. The BASEDEV line should be modified accordingly.
For example, if the host card is set to address 300h, then the line in CONFIG.SYS should read:
basedev=sbcd2.add /P:300
If the CD-ROM drive is connected to a standard Creative Labs CD-ROM host adapter ( NOT SoundBlaster), this adapter supports base I/O addresses of 250h or 260h. In this case the BASEDEV line should be modified to read as follows, assuming address 250h:
basedev=sbcd2.add /P:250 /T:2
o Chinon
The OS/2 device driver CHINCDS1.FLT supports the Chinon 435 and 535 CD-ROM drives. The Chinon CD-ROM drive MUST be attached to a SCSI adapter that is supported under OS/2 with an OS/2 SCSI Adapter Device Driver (.ADD). Currently, there is no support for the Chinon SCSI adapter, which is typically bundled with the Chinon drive. Chinon are developing an OS/2 adapter device driver for their SCSI card, but it is not available at this time.
o IDE CD-ROM Drives
The new IDE CD-ROM drives that comply to the ATAPI standard are supported under OS/2 Warp and require the following drivers:
o IBM1S506.ADD
o CDFS.IFS
o IBMIDECD.FLT
o OS2CDROM.DMD
Some IDE CD-ROM drives complying to this standard (for example, the NEC260) require the following switches on the IBM1S506 driver:
basedev=IBM1S506.add /A:0 /U:1 /ATAPI /V
This tells the driver that the device connected to Adapter 1 and configured as Unit 1 (slave) is ATAPI compliant and to verbosly show information when the driver is loaded.
Owing to a slight change in the way the ATAPI standard is implemented, some of the latest IDE CD-ROM drives (such as the Mitsumi FX300 and some Sony drives) require a later level of drivers. These are available on the IBM PC Company Bulletin Board Service and are called ATAPI.ZIP. The files contained in this package should be used to replace the supplied files.
o Installation Tips
Installation problems for OS/2 usually relate to the individual hardware characteristics of the machines concerned. Also, installing OS/2 can show up hardware problems that DOS might apparently 'ignore'. Some typical examples of these problems and tips on how to get around them are given below.
The OS/2 compatibility list is available on the IBM PC Company Bulletin Board System and is called PCMTAB.ZIP. It shows details on supported hardware and details on associated drivers.
Note: OS/2 will not recognise compressed drives. You will need to un-compress your hard drive before you install OS/2. Should you require compression then there is a version of Stacker which will support DOS and OS/2.
Traps and Hangs During Install on ISA Bus It is always a good idea to disable all Caching and Shadow RAM and to turn off Turbo (in CMOS settings) before attempting to install onto ISA machines. If traps and hangs are being experienced then it could be that drivers loaded by the CONFIG.SYS on Disk 1 are the cause of the problem - some of them are only relevant to MCA (PS/2) machines.
To get round this, make a backup of Disk 1 and edit the CONFIG.SYS on it. Find the section:
basedev=print01.sys
basedev=ibm1flpy.add
basedev=ibm1s506.add
basedev=ibm2flpy.add
REM basedev=ibm2adsk.add
REM basedev=ibm2scsi.add
basedev=ibmint13.i13
basedev=os2dasd.dmd *** Required for disk subsystem support.
Do not REM ***
and REM out the MCA drivers as shown above.
If this still does not work, then REM out the line
basedev=ibm1s506.add.
This is the driver for ISA IDE hard disks - OS/2 sometimes does not like some IDE controllers. In this case, the IBMINT13.I13 will drive the hard disk. IBMINT13.I13 can drive nearly anything, but is slow.
If having tried all of the above, and a combination of the above two workarounds, and you are still getting traps, then you most likely have a hardware problem. Trap0002, trap0006 and trap0008 can all indicate faulty memory. The only real way to try and isolate memory problems is to swap out SIMMS until the system works. Also, OS/2 must have all SIMMS at the same speed - and better still if they are all made by the same manufacturer.
Should you experience an error in the form of COUNTRY.SYS not found or Error in IBM1S506ú driver then the system may not be able to locate your hard drive correctly. In this case, REM out the line reading
basedev=ibm1s506.add
and use the ibmint13.i13 driver.
Speeding up the Install
There are many CD-ROM drivers that are pre-configured on the installation disk and these are shown in the table at the beginning of this article. Before installation, modification may be required to these drivers as described. To speed up the loading of Disk 1 and to avoid conflicts, unused drivers may be REMARKED out.
If you do not have a SCSI card in your machine then the section headed SCSI Card Drivers may be removed. If you have a SCSI card then you can remove all lines except the one for your card. Please note however that the line
basedev=os2scsi.dmd
is required for SCSI support.
Likewise, the section marked SCSI CD-ROM Drivers may be removed if you do not have a SCSI CD-ROM.
Should you have an ISA CD-ROM drive then locate the line that supports your drive and make modifications if required. You may REM out all the unused ISA CD-ROM drivers. The line
basedev=os2cdrom.dmd
is required for all CD-ROM support.
Promise IDE Controllers
These controller cards may need some switch settings on the IBM1S506 driver to disable multiple support. In this case, the line should be modified to read
basdev=IBM1S506.add /A:0 /U:0 /!SMS /U:1 /!SMS
This disables multiple support for both Units 0 and 1 (master and slave). If this does not work then there is a specific driver available from Promise, which can be downloaded from the IBM UK PC Bulletin Board Service - file name PTI1S506.ADD.
Re-booting the Machine
If you have chosen an incorrect driver during install or have a problem with a corrupted display then you can re- set the video driver to VGA using the following process.
When you see the white OS/2 and block in the top left corner of the screen press ALT+F1 to start from the recovery menu. This will give you a number of options, one of which is to re-set the system to VGA by pressing V. After this, the system will continue to start, but will copy the VGA files in the process.
At the recovery menu, it is also possible to restore the original CONFIG.SYS files that were created during install and also to exit to a command prompt. At the prompt you can now edit the CONFIG.SYS using the TEDIT editor. This is very similar to the E editor in PC DOS, but you will need to press ESC after loading the file, to switch the cursor from the search bar to the edit screen.
Hardware Settings
There are a number of different 'features' of IBM compatible systems that may cause the installation of OS/2 to fail. However, if the installation can be completed, then OS/2 will run normally. Unfortunately, these 'features' can improve the execution of DOS on these machines.
Some problems that may arise are that the system hangs during the loading of the first disk or during the first re-boot. If you have a fast machine then it is advisable to slow it down during install. This can be performed by turning off Turbo on some machines. See also steps 'a' and 'd' below.
The most common 'features' to cause problems and their fixes are:
a. Internal and external (2nd Level) processor cache. From the BIOS set-up screen it should be possible to turn off any processor cache.
b. ROM shadowing to RAM. From the BIOS set-up screen, turn off any ROM shadowing.
c. Memory re-mapping. From the BIOS set-up screen, turn off any re-mapping.
d. Timing problems within the motherboard. From the BIOS set-up screen, or by changing settings on the motherboard, force the processor clock speed as low as possible.
e. High expansion bus speeds. From the BIOS set-up screen, set the expansion bus to run at the lowest speed. Use the highest clock divisor.
f. Adapter cards that have settings not possible under OS/2 or may be mis-identified by the OS/2 install program.
Remove any adapter cards that are not required for the normal operation of the system. Network cards are one type likely to cause problems during installation.
g. Some machines can have installation problems when fitted with more than 16MB of memory.
Remove RAM above 16MB and re-fit after installation.
Once OS/2 has been successfully installed it is normally possible to restore all the BIOS settings and insert adapter cards, configuring them one at a time, if they are compatible.
o After Installation
The first time OS/2 re-starts after installation it may take a while to boot and may at some point seem to have hung. If you encounter this situation, leave the machine for a few minutes because it is creating the desktop files and is also doing some cleaning of install files. Once these files have been processed, OS/2 will write them to disk and finish loading.
Rebuilding the OS/2 Desktop
Should the OS/2 desktop become corrupt, you can re-build it using the following procedure.
1. Boot from the two install disks and, when prompted, exit to an A:\ prompt.
2. Change to the OS/2 drive and change into the OS2 directory.
3. Remove the read only attributes on the OS2.INI and OS2SYS.INI using the following command:
ATTRIB -r <FileName>
then delete the files using the command:
DEL <FileName>
4. Re-create the files using the following commands:
MAKEINI OS2.INI INI.RC
MAKEINI OS2SYS.INI INISYS.RC
5. Change into the root directory of the drive and use the following commands to remove the file WP ROOT. SF
ATTRIB -s -r -h WP?ROOT.?SF
DEL WP?ROOT.?SF
6. Remove any diskettes and re-start the machine. It will take longer to boot while re-creating the Desktop.
|
Search Keywords |
| |
|
Hint Category |
Installation/Removal Procedures, OS/2 | |
|
Date Created |
01-06-98 | |
|
Last Updated |
02-06-98 | |
|
Revision Date |
01-06-99 | |
|
Brand |
Cross Brand | |
|
Product Family |
Various | |
|
Machine Type |
Various | |
|
Model |
| |
|
TypeModel |
| |
|
Retain Tip (if applicable) |
| |
|
Reverse Doclinks |