Troubleshooting the installation

Solving problems during installation

This section covers solutions for some common problems that might occur while installing the software.

Installation CD fails to boot from bootable CD-ROM drive

If you have a system that supports bootable CD-ROM but the SCO OpenServer CD-ROM fails to boot, it is possible that your system BIOS is out-of-date. Check with your hardware vendor to see if there are any BIOS updates available.

Installation fails with IDE CD-ROM drive configured as slave device

If you attempt to install SCO OpenServer from an IDE CD-ROM drive that is configured as the slave device on the IDE controller, the installation may fail if there is no master IDE device configured.

To solve this problem, temporarily reconfigure the CD-ROM drive to be the master device. After the installation is complete, you can return to your previous configuration.

Installation fails with /cd-rom/.extra.d/usr/bin/swap error

If the installation halts with the following error message:

   /cd-rom/.extra.d/usr/bin/swap -a /dev/dsk/c0b0t1d0s1 failed.


   The installation has been aborted. To recover from this error
   you must restart the installation.

the problem may be caused by interference from an IDE device that is connected to the system. Disconnect any IDE devices that are not needed during installation and then restart the installation.

You can reconnect these IDE devices after the system is successfully installed.

USB devices can interfere with installation

Other than a USB keyboard, USB mouse, and, if desired, a USB CD-ROM drive for running the installation, we recommend that you remove other USB devices (especially USB storage devices) before starting the installation to minimize the chance of problems.

USB keyboard does not function properly

If you are using a USB keyboard and it seems the keyboard is either stuck or not functioning properly, press the <Alt> and <Enter> keys to get it to function properly again. This is especially true for certain keyboards when switching between virtual terminal screens.

Installation unresponsive when system attached to KVM switch

If your system console, mouse, and keyboard are connected to a KVM or multiscreen switch, the system may become unresponsive when the system attempts to detect your mouse (just after the installation CD-ROM is loaded). If this occurs, reboot the system, restart the installation, and press any key when the SCO OpenServer logo appears. When the [boot] prompt is displayed, enter:

[boot] IVAR_MOUSE=manual
[boot] boot

This bypasses mouse autodetection and allows you to manually configure your mouse during installation.
Signal detection is more robust with some KVM switches than others. With some units, it is possible for the connection between input devices (mouse and/or keyboard) and the system to be interrupted, even if momentarily, when switching from one system to another. If this happens with a PS/2 or serial mouse, the mouse connection will not recover. If you switch away in the middle of an installation and this problem occurs, you will need to restart the installation.
If your system is attached to a KVM or multiscreen switch and you experience problems with system unresponsiveness after switching screens, we recommend that you stay on the SCO OpenServer screen for the duration of the installation.

Number of mouse buttons incorrectly detected

If you are using a serial or PS/2 mouse, the mouse autodetection utility always configures the mouse for three buttons. If your serial or PS/2 mouse has fewer buttons, reset the mouse button count on the installation's Mouse Configuration screen. Or, after the installation is complete, manually reconfigure the mouse using mkdev mouse.

This issue does not apply to USB mice.