User manual PLEXTOR 12-20C

[. . . ] ---- CHAPTER 10 ---- Using CD-ROM Discs and Trays YOUR TASK: YOUR OBJECTIVE: YOUR METHOD: Learn how to handle, load, and care for your discs. Insert and eject discs properly so your drive operates without interruption. Practice loading discs into trays. Tray Loading and Operating 1) While the drive is powered up, push the Eject button. The tray drawer will slide out in 2--3 seconds. 2) Press the Eject button again and the tray will slide shut within 2--3 seconds. Note: We recommend you use the Eject button to close the tray in a smooth and secure manner. [. . . ] You can check to see if this is the case by doing the following: Unplug the audio cable from the rear of your 12/20PleX drive. Plug a set of headphones or speakers that you know are good into the jack on the front of the drive. If you can now hear music, you may conclude that you do, in fact, have a bad audio cable. Symptoms · Cannot view Photo CD discs · Can read only first session of a multisession disc · Receive error messages while reading Photo CD images Your 12/20PleX drive is capable of reading Kodak Photo CD multisession discs if you use the appropriate device drivers and you run a Photo CD viewing program (e. g. , Magic Lantern, Kodak's Photo CD Access). 48 12/20PLEX OPERATION MANUAL CHAPTER 12 ---- Troubleshooting Possible Causes and Solutions Device Drivers Need to Be Updated Contact Plextor Technical Support for device driver information. Bad Photo CD Disc If you can see a list of files from your Photo CD (after issuing a DIR command), but cannot read them, or experience errors while reading them, you may have a bad Photo CD disc. If it works, you should have the defective disc replaced. Symptoms · · · · Invalid Drive Specification No Device Found No SCSI Interface Board Found, or No Response from SCSI Interface Board · No Drives in Use Additional Symptom Error Appears upon Initial Installation of the CD-ROM Drive and Device Driver Software Possible Causes and Solutions Improper SCSI Device Driver Installation Your computer needs a SCSI software device driver to link the SCSI interface board to the CD-ROM drive. If this driver cannot be loaded properly, an error message will normally be displayed on the screen. Watch as the CONFIG. SYS file executes, and look for an error message to appear. You can press the Control and S keys simultaneously to freeze the display in order to read the error message (use the Control and S combination again to continue). 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 paragraphs 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. If you do not have either of these versions, and plan to use DOS 5. 0 with MSCDEX. EXE Ver 2. 2 (or lower), you can resolve this conflict by doing the following: 1) Type the following line into your CONFIG. SYS file: DEVICE=C:\DOS\SETVER. EXE 2) Switch to the DOS prompt. 3) Type the following: SETVER MSCDEX. EXE 4. 01, then press the Enter key. Conflict Between MS-DOS 6. 0 and Microsoft's CD-ROM Extensions (file name: MSCDEX. EXE) Version 2. 21 (or Lower) MSCDEX. EXE ver. Use of an earlier version will result in an INCORRECT DOS VERSION message. 2. 21 (or lower), your computer might still be recognizing this lower version rather than 2. 22 (or higher). To correct this problem, you must edit your AUTOEXEC. BAT file using a text editor or word processor. Your AUTOEXEC. BAT file will probably contain a line that looks something like this: C:\TSCSI\MSCDEX. EXE /D:TSLCD /M:10 In this example, ``C:\TSCI'' is the path to MSCDEX. EXE. The path name will vary depending on the type of SCSI device driver software you use. Change only the path of this line in your AUTOEXEC. BAT file so that it finds the updated MSCDEX. EXE file in your DOS directory. This line should be edited to read: C:\DOS\MSCDEX. EXE /D:TSLCD /M:10 Save the AUTOEXEC. BAT file and reboot your computer. 12/20PLEX OPERATION MANUAL 51 CHAPTER 12 ---- Troubleshooting Symptoms · No Device Found · No SCSI Interface Board Found or No Response from SCSI Interface Board Additional Symptom Driver Fails to Recognize the SCSI Interface Board Possible Cause and Solution Drive Not Resetting In some cases, even if you restart the computer by pressing its reset button or the Control, Alt, and Del keys simultaneously, the drive does not appear to respond. [. . . ] Defective CD-ROM Disc A fingerprint, contaminants, or deep scratches on the disc's surface may prevent the drive from reading data. You should also review the low performance symptom discussed on page 57. Bad Connection Between the CD-ROM Drive and the SCSI Interface Board Inspect the cable, drive, and interface card for recessed, broken, or bent pins. If a ribbon cable is used, inspect for any signs of distress, such as kinking. Symptom · CDR103----Not High Sierra Format Additional Symptom Occurs with Certain Discs Only Possible Cause and Solution Incorrect Disc The disc might be intended for another type of computer, such as a Macintosh or Sun, or it is not mastered in the High Sierra or ISO 9660 formats. 12/20PLEX OPERATION MANUAL 55 CHAPTER 12 ---- Troubleshooting Symptom · CDR103----Not High Sierra Format Additional Symptom Occurs Regardless of the Discs Used Possible Causes and Solutions Incorrect Jumper Setting You might have the block jumper set to ON. [. . . ]