52
ULTRAPLEX 40X OPERATION MANUAL
If the SCSI device driver cannot be loaded properly, either a software or
hardware conflict exists. Software conflicts are generally caused by memory
managers; hardware conflicts by two peripherals vying for the same DOS
address space. Please read the next two sections on Software and Hardware
conflicts.
Software Conflict with Other Device Drivers
The SCSI interface board normally designates the CD-ROM driver as the first
device driver loaded by the computer. When the computer has a memory
manager (e.g., HIMEM.SYS, 386MAX.SYS, or QEMM.SYS), in most cases the
memory manager is loaded first and the CD-ROM driver loaded directly
thereafter.
If other device drivers are loading before the CD-ROM driver, place them after
the CD-ROM driver. If the memory manager tries to load the CD-ROM driver
into high memory (e.g., DEVICEHIGH or LOADHIGH), disable the function so
that the driver is loaded into conventional memory.
Hardware Conflict Between the Interface Board and Your Computer
The SCSI interface board may be in conflict with another peripheral in your
computer. Normally, this conflict can be settled by selecting a different address
for the SCSI interface board. In some cases, you may wish to select a different
address for the conflicting peripheral.
If the driver still does not recognize the interface board, try the following:
1) Remove all non-essential peripherals from your computer (e.g.,
network boards, fax boards, etc.) and their device drivers from the
CONFIG.SYS and AUTOEXEC.BAT files.
2) Reboot the computer and ensure that the SCSI card’s ASPI and
CD-ROM device driver recognizes the CD-ROM drive.
3) Turn OFF the computer and reinstall each peripheral and its device
drivers one at a time.
4) Repeat steps 2 and 3 until the problem reoccurs. This means that the
problem is with the last peripheral you installed.
Improper MSCDEX Installation
The Microsoft CD-ROM extensions (filename: MSCDEX.EXE) or equivalent
files are required to run your CD-ROM drive under MS-DOS. If the SCSI driver
was successfully loaded, check for proper installation of MSCDEX.EXE by
rebooting the computer and watching the AUTOEXEC.BAT file as it executes
for an error message.
CHAPTER 12 — Troubleshooting
Summary of Contents for PX-40TSe
Page 93: ......
