|
5.669 bytes |
Service Hints & Tips |
Document ID: DDSE-3QKKED |
|
This document is provided to IBM and our Business Partners to help sell and/or service IBM products. It is not to be distributed beyond that audience or used for any other purpose. |
Cross Brand - General OS/2 Warp problem and resolution tips
Applicable to: World-Wide
Problem Description:
When installing OS/2 Warp v3 from CD-ROM attached to the IBM PCI Controller, after inserting diskette 1, you are presented with a red screen saying that no CD-ROM drives can be found.
Resolution:
This is because OS/2 Warp v3 diskettes do not have drivers for the PC Server as standard. You will need to add these drivers manually by following the steps below.
1. Make a copy of Warp diskette 1. Label it up "OS/2 Warp v3 diskette 1 for PC Server" : diskcopy A: A:
2. Delete the Adaptec device drivers from the new diskette to make room for the PC 300 driver : delete a:\aha*.*
3. Copy the IBMPSCSI.ADD from the "IBM PCI Fast SCSI-2 Support Diskette" (shipped with the machine) to your "OS/2 Warp v3 diskette 1 for PC Server".
4. Edit the CONFIG.SYS of your new diskette 1 and add the line : BASEDEV=IBMPSCSI.ADD before the line :
BASEDEV=IBMINT13.I13.
Remove all references to adaptec drivers - AHA*.*
5. Re-boot the machine on the Installation diskette, and when asked to insert diskette 1 - use the "OS/2 Warp v3 diskette 1 for PC Server" you created earlier.
Installing OS/2 WARP On Valuepoint 6384-199 (P60/D)
Problem description:
On attempting to install OS/2 Warp from diskette on the above model, when booting from the installation diskette and loading diskette 1 when requested - it hangs with the diskette light on and logo displayed (ALT-F2 shows nothing). No driver has been loaded. Turning off internal/external cache and shadowing ROM does not help.
Resolution:
These ValuePoint systems come with the Flash EEPROM level 0.13.01.AV0M and it has an AMI BIOS. Users needs to download VPP60FL6.DSK from the IBM UK PC Bulletin Board Service. The new BIOS level is 1.00.06.AV0M.
Installing Warp from an internal CD connected to a soundcard.
Problem description:
The CDROM is not being recognised - "OS2CDROM.DMD not found"
Resolution:
This is a hardware related problem and is rectified by the following;
1. On the back of the CDROM drive is a jumper which controls the bus device number. OS/2 install requires it to be on 0 (zero). Most sound board manufacturers leave it at the factory default of 1. If it is anything other than 0, the install disk #1 will not load the driver " OS2CDROM.DMD " and will stop installation with a red screen saying it can't find the CDROM
WIN-OS/2 under OS/2 Warp fails to load
Problem Description:
WIN-OS/2 will fail to launch if there is no mouse type specified in the MOUSE.INI. If WIN-OS/2 /B is un from an OS/2 session the OOTLOG.TXT has as its last statement, "LOADSTART=MOUSE.DRV"
Resolution:
When starting any WIN-OS/2 session (FS or seamless), it will terminate before it starts. If initiated from an icon it will hatch then unattach. If initiated from a command line, "Loading Please Wait..." will appear, then the session prompt will re-display. If starting a WIN-OS/2 session from a command line with a "/B" switch the BOOTLOG.TXT file will show LOADSTART=MOUSE.DRV as the last statement in the file. A look at MOUSE.INI reveals that MOUSETYPE=. This statement must equal the type of hardware installed on the system. When running in DOS/WINDOWS the system will query the hardware attached and update MOUSE.INI accordingly. Until a resolution of why the MOUSE.INI file is not being updated as it is in DOS/WINDOWS, ensure that the MOUSETYPE= the MOUSE.INI equals the mouse type described in the boot description section in SYSTEM.INI.
|
Search Keywords |
| |
|
Hint Category |
Installation/Removal Procedures, OS/2 | |
|
Date Created |
23-08-95 | |
|
Last Updated |
11-08-98 | |
|
Revision Date |
10-08-99 | |
|
Brand |
Cross Brand | |
|
Product Family |
Various | |
|
Machine Type |
Various | |
|
Model |
Various | |
|
TypeModel |
| |
|
Retain Tip (if applicable) |
| |
|
Reverse Doclinks |