|
|
BuildPC * CustomizeWindows * InstallOS * Internet * HardwareProblems * E-Mail * Home |
CD-ROM and DVD Drive
CARING FOR COMPACT
DISCS: A compact disc is a remarkably reliable long-term storage
media (conservative expectations place the life estimates of a current CD at
about 100 years. However, the longevity of a CD is affected by its storage and
handling—a faulty CD can cause file and data errors that you might otherwise
interpret as a defect in the drive itself. Here are some tips to help protect
and maintain the disc itself:
Don’t bend the disc Polycarbonate is a forgiving material, but
you risk cracking or snapping (and thus ruining) the disc.
Don’t heat the disk Remember, the disc is plastic. Leaving it
by a heater or on the dashboard of your car might cause it to melt.
Don’t scratch the disc Laser wavelengths have a tendency to “look
past” minor scratches, but a major scratch can cause problems. Be especially
careful of circular scratches (one that follows the spiral track). A circular
scratch can easily wipe out entire segments of data, which would be unrecoverable.
Don’t use chemicals on the disc Chemicals containing solvents,
such as ammonia, benzene, acetone, carbon tetrachloride, or chlorinated cleaners,
can easily damage the disc’s plastic surface.
Q&A:
expected”?Why
does my drive have trouble accepting or rejecting a CD?
This problem is typical of motorized CD-ROM drives, where the disc is accepted
into a slot or placed in a motorized tray. Before performing any disassembly,
check the assembly through the CD slot for any obvious obstructions. If nothing
is obvious, expose the assembly and check each linkage and motor drive gear
very carefully. Carefully remove or free any obstruction. Be gentle when working
around the load/unload assembly. Notice how it is shock mounted in four places.
Disconnect the geared dc motor assembly and try moving the load/unload mechanism
by hand. If you feel any resistance or obstruction, you should track it down
by eye and by feel. Replace any worn or damaged part of the mechanism, or replace
the entire load/unload assembly. Also check the geared motor for any damage
or obstruction. Broken or slipping gear teeth can interfere with the transfer
of force from motor to mechanism. Replace any damaged gears or replace the entire
geared assembly. You might also simply replace the CD-ROM drive mechanism outright.
Why is it that my optical read head
does not seek?
An optical head is used to identify pits and lands along a CD-ROM, and to track
the spiral data pattern as the head moves across the disk. The optical head
must move very slowly and smoothly to ensure accurate tracking. Head movement
is accomplished using a linear stepping motor (or linear actuator) to shift
the optical assembly in microscopic increments—head travel appears perfectly
smooth to the unaided eye. Check the drive for any damaged parts of obstructions.
When the optical head fails to seek, the easiest and fastest fix is simply to
replace the CD-ROM mechanism outright.
Why is it
that my CD cannot be read or skips?
You may need to slow or speed up the speed of your CD reading
device. Fluctuation in speed may be causing your device to skip or have reading
errors due to the speed in which the CD device is operating in. To adjust the
speed of your device :
Why is it that my disc cannot be
read?
This type of problem might result in a DOS level “sector not found” or “drive
not ready” error. Before you reach for your tools, however, check the CD itself
to ensure that it is the right format, inserted properly, and physically clean.
Cleanliness is very important to a CD. Although the laser will often “look past”
any surface defects in a disc, the presence of dust or debris on a disc surface
can produce serious tracking (and read) errors. Try a different disc to confirm
the problem. If a new or different disc reads properly, the trouble might indeed
be in (or on) the original disc itself. Not only the disc must be clean, but
the head optics must also be clear. Gently dust or clean the head optics, as
suggested by your drive’s particular manufacturer. If read problems persist,
check the physical interface cable between the drive and its adapter board.
Be sure that the cable is connected correctly and completely. Many CD drives
use SCSI interfaces—if you are using multiple SCSI devices from the same controller
card and other SCSI devices are operating properly, the SCSI controller board
is probably intact. If other SCSI devices are also malfunctioning, try a new
SCSI host controller board. At this point, either the drive’s optical head or
electronics are defective. Your best course here is to replace the drive. If
problems persist on a drive with a proprietary interface, replace the adapter
board.
Why isn't my disc turning?
The disc must turn at a Constant Linear Velocity (CLV) that is directed and
regulated by the spindle. If the disc is not spinning during access, check to
be sure that the disc is seated properly, and is not jammed or obstructed. Before
beginning a repair, review your drive installation and setup carefully to ensure
that the drive is properly configured for operation. If the drive’s BUSY LED
comes on when drive access is attempted (you might also see a corresponding
DOS error message), the drive spindle system is probably defective. If the computer
does not recognize the CD drive (i.e., “invalid drive specification”), there
might be a setup or configuration problem (either the low-level device driver
or MSCDEX might not have loaded properly). If your particular drive provides
you with instructions for cleaning the optical head aperture, perform that cleaning
operation and try the drive again. A fouled optical head can sometimes upset
spindle operation. If operation does not improve,
replace the CD-ROM drive mechanism.
Why is it that the optical
head cannot focus its laser beam?
A CD-ROM drive must focus its laser beam to microscopic precision to properly
read the pits and lands of a disk. To compensate for the minute fluctuations
in disc flatness, the optical head mounts its objective lens into a small focusing
mechanism, which is little more than a miniature voice-coil actuator—the lens
does not have to move very much at all to maintain precise focus. If focus is
out or not well maintained, the laser detector might produce erroneous signals.
This might result in DOS drive error messages. If random, but consistent, DOS
errors appear, check the disc to be sure that it is optically clean—dust and
fingerprints can result in serious access problems. Try another disc. If a new
disc continues to perform badly, try cleaning the optical aperture with clean
(photography grade) air. If problems persist, the optical system is probably
damaged or defective. Replace the CD-ROM drive mechanism outright.
Why am I not getting audio from
my drive?
Many CD-ROM drives are capable of not only reading computer data, but reading
and reproducing music and sounds under computer control. Audio CDs can often
be played in available CD-ROM drives through headphones or speakers. Start your
investigation by testing the headphones or speakers in another sound source,
such as a stereo. Once you have confirmed that the speakers or headphones are
working reliably, check the drive’s audio volume setting, which is usually available
through the front bezel. Set the volume to a good average place (perhaps midrange).
Be sure that the disk you are trying to play actually contains valid Red Book
audio. Check any software required to operate the CD drive’s audio output (usually
set with a “mixer applet”) to be sure that it is installed and loaded as expected.
CD-ROM's will not play audio CDs without an audio driver. Also check the line
output, which would drive amplified speakers or stereo inputs. If speakers work
through the line output but headphones or speakers do not work through the front
bezel connector, the volume control or output audio amplifier might be defective.
If the headphone output continues to fail, replace the headphone PC board or
replace the entire CD-ROM drive outright.
Why isn't any audio being played
by the sound card?
Normally, the sound card will not play Red Book audio from a CD—that is usually
fed directly to the CD’s headphone or line output. However, audio can be channeled
to the sound board for playback. Most CDs offer an audio connector that allows
audio signals to be fed directly to the sound board. If this “CD audio cable”
is missing or defective, Red Book audio will not play through the sound board.
Check or replace the cable. If the cable is intact (and audio is available from
the CD-ROM headphone output), check the sound board’s configuration for any
“mixer” applet (see that any control for CD audio is turned up, and remember
to save any changes). If problems persist, replace the sound board. If the CD
audio cable is intact (and audio is not available from the CD-ROM headphone
output), the audio amplifier circuit in the CD-ROM is probably defective—replace
the CD-ROM drive.
Why do I see a “Wrong DOS version”
error message when attempting to load MSCDEX?
You are running MS-DOS 4, 5, or 6 with a version of MSCDEX which does not support
it. The solution is then to change to the correct version of MSCDEX. The version
compatibility for MSCDEX is:
without
changing the file size or date.Why can't I access the CD-ROM drive
letter?
You might see an error message, such as “Invalid drive specification.” This
is typically a problem with the CD-ROM drivers. The MS-DOS extension MSCDEX
has probably not loaded. Switch to the DOS sub-directory and use the MEM /C
function to check the loaded drivers and TSRs. If you see the low-level driver
and MSCDEX displayed in the driver list, check the CD-ROM hardware. Be sure
that the data cable between the drive and adapter board in inserted properly
and completely. If problems persist, try replacing the adapter board. If you
do not see the low-level driver and MSCDEX shown in the driver list, inspect
your CONFIG.SYS and AUTOEXEC.BAT files. Check that the drivers are included
in the startup files to begin with. Be sure that the label used in the /D switch
is the same for both the low-level driver and MSCDEX. If the label is not the
same, MSCDEX will not load. If you are using MS-DOS 5.0, be sure that the SETVER
utility is loaded. You could also try updating MSCEDX to v2.30. 2
Why does an error appears when
trying to load the low-level CD-ROM driver?
Check that you are using the proper low-level device driver for your CD-ROM
drive. If you are swapping the drive or adapter board, you probably need to
load a new driver. If the driver fails to load with original hardware, the adapter
board might have failed or its jumper settings might not match those in the
driver’s command line switches. Check the signal cable running between the drive
and adapter board. If the cable is crimped or scuffed, try replacing the cable.
Next, try replacing the adapter board. If problems persist, try replacing the
CD-ROM drive mechanism itself.
Why am I getting an error, such
as “Error: not ready reading from drive D:”?
Check that a suitable disc is inserted in the drive and that the drive is closed
properly. Be sure that the low-level device driver and MSCDEX are loaded correctly.
If the drivers do not load, the problem might be with the adapter board or drive
mechanism itself. Also check that the data cable between the drive and adapter
is connected properly and completely. If problems persist, suspect that a weakness
is in the PC power supply (especially if the system is heavily loaded or upgraded).
Try a larger supply in the system. If problems persist, replace the CD-ROM drive.
If a new drive does not correct the problem, try a different interface adapter.
Why is SmartDrive not caching the CD-ROM
properly?
The version of SmartDrive supplied with DOS 6.2x provides three forms of caching,
although older forms of SmartDrive (such as the ones distributed with Windows
3.1, DOS 6.0 and 6.1) will not adequately cache CD-ROM drives. The BUFFERS statement
also does not help caching. So, if you are looking to SmartDrive for CD-ROM
cache, you should be using the version distributed with DOS 6.2x. You should
also set BUFFERS=10,0 in the CONFIG.SYS file,and the SmartDrive command line
should come after MSCDEX. When using SmartDrive, you can change the buffers
setting in the MSCDEX command line (/M) to 0. This allows you to save 2KB per
buffer.
SmartDrive is not used by Windows 95, which uses
its own CD-caching scheme. Try disabling SmartDrive when running under Windows
95.
Why is it that CD-ROM drivers will
not install properly on a drive using compression software?
This is usually because you booted from a floppy disk and attempted to install
drivers without loading the compression software first. Before doing anything
else, check the loading order—allow your system to boot from the hard drive
before installing the CD-ROM drivers. This allows the compression software to
assign all drive letters. As an alternative, boot from a compression-aware floppy
disk. If you must boot the system from a floppy disk, be sure that the diskette
is configured to be fully compatible with the compression software being used.
Why do I see an error
indicating that the CD-ROM drive is not found?
This type of problem might also appear as loading problems with the
low-level driver. There are several possible reasons why the drive hardware
cannot be found. Check the power connector first and be sure that the 4-pin
power connector is inserted properly and completely. If the drive is being powered
by a Y-connector, be sure that any interim connections are secure. Use a voltmeter
and measure the +5-V (pin 4) and +12-V (pin 1) levels. If either voltage (especially
the +12-V supply) is unusually low or absent, replace the power supply. Check
the signal connector next and see that the drive’s signal interface cable is
connected securely at both the drive and controller. If the cable is visibly
worn or damaged, try a new one. Inspect the drive interface adapter and be sure
that the adapter’s IRQ, DMA, and I/O address settings are correct. They must
also match with the command line switches used with the low-level driver. If
the adapter is for a CD-ROM alone, you might also try installing the adapter
in a different bus slot. If your CD-ROM uses a SCSI interface, be sure that
the SCSI bus is properly terminated at both ends. If problems persist, replace
the drive adapter.
Why after installing the CD-ROM
drivers, system reports significantly less available RAM?
This is usually a caching issue with CD-ROM driver software, and you
might need to adjust the CD-ROM driver software accordingly. This type of problem
has been documented with Teac CD-ROM drives and CORELCDX.COM software. If the
software offers a command line switch to change the amount of XMS al-located,
reduce the number to 512 or 256. Check with tech support for your particular
drive for the exact command line switch settings.
Why in a new installation,
do the driver fails to load successfully for the proprietary interface card?
In almost all cases, the interface card has been configured improperly. Check
the drive adapter card first. Be sure that the drive adapter is configured with
the correct IRQ, DMA, and I/O address settings, and check for hardware conflicts
with other devices in the system. In some cases, you might simply enter the
drive maker (i.e., Teac) as the interface type during driver installation. Be
sure that the interface is set properly for the system and your particular drive.
Check the driver’s command line next—the driver’s command-line switches should
correctly reflect the drive adapter’s configuration.
Why after the CD-ROM driver loads,
but I see an error, such as: “CDR101” (drive not ready), or: “CDR103” (CD-ROM
disk not HIGH SIERRA or ISO)?
You are using a very old version of the low-level driver or MSCDEX. Check your
driver version (it might be outdated). Contact the drive manufacturer’s tech
support and see that you have the very latest version of the low-level driver.
For very old drives, a later “generic” driver might be available. Check your
version of MSCDEX next. Because low-level drivers are often bundled with MSCDEX,
you might also be stuck with an old version of MSCDEX. You can usually download
a current version of MSCDEX from the same place you get an updated low-level
driver, or download it from Microsoft at: http://www.microsoft.com.
Why am I having trouble setting
up more than one CD-ROM drive?
You must be concerned about hardware and software issues. Check the drive adapter
first—be sure that the drive adapter will support more than one CD-ROM on the
same channel. If not, you will have to install another drive adapter to support
the new CD-ROM drive. Low-level drivers present another problem because you
will need to have one copy of a low-level driver loaded in CONFIG.SYS—one for
each drive. Be sure that the command line switches for each driver match the
hardware settings of the corresponding drive adapter. Finally, check your copy
of MSCDEX. You need only one copy of MSCDEX in AUTOEXEC.BAT, but the “/D:” switch
must appear twice—once for each drive ID.
Why does my CD-ROM drive refuses to work with
an IDE port?
The drive might use a nonstandard port (other than IDE). Try replacing the drive
adapter board. You must connect the CD-ROM drive to a compatible drive adapter.
If the drive is proprietary, it will not interface to a regular IDE port. It
might be necessary to purchase a drive adapter specifically for the CD-ROM drive.
Why is it that I cannot get the CD-ROM
drive to run properly when mounted vertically?
CD-ROM drives with “open” drive trays cannot be mounted vertically— disc tracking
simply will not work correctly. The only CD-ROM drives that can be mounted vertically
are those with caddies, but you should check with those manufacturers before
proceeding with vertical mounting.
Why is it that the SCSI CD-ROM
drive refuses to work when connected to an Adaptec SCSI interface?
Other drives are working fine. This is a common type of problem among SCSI adapters,
and is particularly recognized with Adaptec boards because of their great popularity.
In most cases, the Adaptec drivers are the wrong version or are corrupted. Try
turning off Sync negotiations on the Adaptec
SCSI interface, and reboot the system. Your SCSI drivers might also be buggy
or outdated. Check with Adaptec technical support (http://www.adaptec.com) to
determine if you should use a later driver version instead.
Why do I see a “No drives found”
error when the CD-ROM driver line is executed in CONFIG.SYS?
In most cases, the driver command-line switches do not match the hardware configuration
of the drive adapter. Your low-level driver might be missing or incomplete.
Open CONFIG.SYS into a word processor and see that the low-level driver has
a complete and accurate command line. See that any command line switches are
set correctly. Check the MSCDEX command line next. Open AUTOEXEC.BAT into a
word processor and see that the MSCDEX command line is accurate and complete.
Also confirm that any MSCDEX command-line switches are set correctly. If you
are using SmartDrive with DOS 6.0 or later, try adding the /U switch to the
end of your SmartDrive command line in AUTOEXEC.BAT. Check for hardware conflicts.
Be sure that no other hardware devices are in the system that might be conflicting
with the CD-ROM drive controller. If problems persist, replace the drive controller.
Why does my CD-ROM LCD displays an error
code?
Even without knowing the particular meaning of every possible error
message, you can be assured that most CD-based error messages can be traced
to the following causes (in order of ease):
Why when a SCSI CD-ROM drive is connected
to a SCSI adapter, the system hangs when the SCSI BIOS starts?
In most cases, the CD-ROM drive supports Plug and Play, but the SCSI controller’s
BIOS does not. Disable the SCSI BIOS through a jumper on the controller (or
remove the SCSI BIOS IC entirely) and use a SCSI driver in CONFIG.SYS instead.
You might need to download a low-level SCSI driver from the adapter manufacturer.
Why do I see an error, such
as: “Unable to detect ATAPI IDE CD-ROM drive, device driver not loaded”?
You have a problem with the configuration of your IDE/EIDE controller hardware.
Check the signal cable first, and be sure that the 40-pin signal cable is attached
properly between the drive and controller. IDE CD-ROM drives are typically installed
on a secondary 40-pin IDE port. Be sure that no other device is using the same
IRQ or I/O address as your secondary IDE port. Finally, be sure that any command-line
switches for the low-level driver in CONFIG.SYS correspond to the controller’s
hardware settings.
Why is it that my CD-ROM drive
door will not open once the 40-pin IDE signal cable is connected?
You should only need power to operate the drive door. If the door stops when
the signal cable is attached, check for some possible problems. Check the power
connector first and be sure that both +5 and +12 V are available at the power
connector. See that the power connector is attached securely to the back of
the CD-ROM drive. Check the IDE signal cable next—the 40-pin signal cable is
probably reversed at either the drive or controller. Try a different signal
cable. Also be sure that the 40-pin IDE drive is plugged into a “true” IDE port—not
a proprietary (non-IDE 40-pin) port. If problems persist, try a known-good CD-ROM
drive.
Why is it that I am using an old CD-ROM
and can play CD audio, but cannot access directories
or other computer data from a CD?
Older, proprietary CD-ROM drives often used two low-level drivers—one for audio
and one for data. You probably only have one of the drivers installed. Check
your low-level drivers first, and see that any necessary low-level drivers are
loaded in the CONFIG.SYS file. Also see that any command-line switches are set
properly. Some older sound boards with integrated, proprietary CD-ROM drive
controllers might not work properly with the drivers required for your older
CD-ROM drive. You might have to alter the proprietary controller’s IRQ, DMA,
or I/O settings (and update the driver’s command-line switches) until you find
a combination where the driver and controller will work together.
Why is it that the front-panel
controls of my SCSI CD-ROM drive do not appear to work under Windows 95?
Those same controls appear to work fine in DOS. Windows 95 uses SCSI
commands to poll removable media devices every two seconds to see if the status
has changed. Because SCSI commands to the CD-ROM generally have higher priority
than front-panel controls, the front-panel controls might appear to be disabled
under Windows 95. Try pressing the front-panel controls repeatedly. You might
be able to correct this issue by disabling the CD-ROM polling under Windows
95.
Why is it I cannot
change the CD-ROM drive letter under Windows 95?
You need to change the drive’s settings under the Device manager:
I installed Windows 95 from a CD-ROM disc using DOS drivers, but when I removed the real-mode CD-ROM drivers from CON-FIG. SYS, the CD-ROM no longer works? You need to enable protected-mode drivers by running the Add new hardware wizard from the Control panel:
Why is it that
my CD-ROM drive’s parallel port-to-SCSI interface worked with Windows 3.1x,
but does not work under Windows 95?
This problem is typical of the NEC CD-EPPSCSI01 interface, and is usually
caused by a problem with the driver’s assessment of your parallel-port type
(i.e., bi-directional, unidirectional, or enhanced parallel port). Start your
CMOS setup routine first and see what mode your parallel port is
set to operate in. Be sure it is set to a mode that is compatible with your
parallel-port drive. Next, update your version of MSCDEX. Change the MSCDEX
command line in AUTOEXEC.BAT to load from the C:\WINDOWS\CONTROL\ directory,
and remove the /L:x parameter from the end of the MSCDEX command line (if present).
Finally, cold boot the computer. Because typical parallel port-to-SCSI interfaces
get their power from the SCSI device, the external drive must be powered up
first. If you’re using real-mode drivers for the interface, place a switch at
the end of the interface’s command line that tells the driver what mode your
parallel port is operating in. For example, the Trantor T358 driver (MA358.SYS)
uses the following switches (yours will probably be different):
As an alternative, disable your real-mode drivers. Remove or REMark out any references to the interface’s real-mode drivers in CONFIG.SYS, then remove or disable the MSCDEX command line in AUTOEXEC.BAT. Start Windows 95, open the Control panel, select the System icon, then choose the Device manager page. Find the SCSI adapter settings and expand the “SCSI controllers” branch of the device tree. Select the device identification line for your parallel port-to-SCSI interface, then click on the Properties button. Click on the Settings page. In the Adapter settings dialog box, type in the same parameter that would have been used if you were using real-mode drivers. Click on the OK buttons to save your changes, then select Yes to reboot the system. If problems persist, check the technical support for your parallel port-to-SCSI adapter and see if there are any known problems with your particular setup, or if any updated drivers are available for download.
Why do I
see a message that the: “CD-ROM can run, but results might not be as expected”?
This simply means that Windows 9x is using real-mode drivers. If protected-mode
drivers are available for the CD-ROM drive, you should use those instead.
Why is it that the CD-ROM
works fine in DOS or Windows 3.1x, but sound or video appears choppy under Windows
9x?
Several factors can affect CD-ROM performance under Windows 9x. Windows 9x performance
(and stability) is severely degraded by real-mode drivers, so start by removing
or disabling any real-mode drivers. Try installing the protected-mode drivers
for your CD-ROM drive instead. If protected- mode drivers are not available
for your drive, you might consider upgrading the CD-ROM hardware. Also, avoid
using DOS or Windows 3.1x applications under Windows 9x. Real-mode applications
run under Windows 9x can also cripple performance. Try exiting any DOS or Windows
3.1x applications that might be running on the Windows 9x desktop. Also exit
unneeded Windows 9x applications because additional applications take a toll
on processing power. Exit any Windows 9x applications that might be running
in the background. Finally, reboot the system to ensure that Windows 9x has
the maximum amount of resources available before running your CD-ROM
application.
Why can’t
I read a Video CD-I disc in Windows 9x using any ATAPI/IDE CD-ROM drive?
The built-in ATAPI driver in Windows 9x cannot read raw data in 32-bit disk-access
mode. Such symptoms can also happen to any ATAPI/IDE-compatible CD-ROM as long
as they are using the built-in ATAPI driver in Windows 9x. You should update
the CD-ROM’s ATAPI driver to a current manufacturer-specific version. As another
alternative, you can use the following procedure:
1 Disable the 32-bit disk-access
feature of Windows 9x.
2 Under the Windows 95 Desktop, click Start and choose Settings and Control
panel.
3 Click on System icon and select the Performance option.
4 Choose File system and select the Troubleshooting option.
5 At the Troubleshooting dialog, click on “Disable all 32-bit disk access.”
6 Edit AUTOEXEC.BAT and append the following line (where {path} is the path
name of your Windows 95 software): C:\{path}\COMMAND\MSCDEX.EXE /D:MSCD000
Why is that an IDE CD-ROM is not
detected on a 486 PCI motherboard?
This is a known problem when using Aztech CD-ROM drives and 486 PCI motherboards
with SIS 82C497 chipsets. The motherboard bus noise is far too high, which results
in the misinterpretation of the IDE interface handshaking signals (namely DASP,PDIAG).
As a consequence, the CD-ROM drive sometimes (or always) is not detected. You
might be able to resolve this problem by connecting the IDE CD-ROM drive as
a “slave” device to the hard disk—although you might need to slow the hard drive’s
data-transfer mode to accommodate the slower CD-ROM drive.
Why is it that an IDE CD-ROM is not
detected when “slaved” to an IBM hard drive?
This is a known problem with Aztech IDE CD-ROM drives and IBM Dala 3450 hard
drives. The pulse width for the drive-detection signal (DASP) is not long enough
for the CD-ROM to identify itself properly. This results in the improper detection
of an Aztech IDE CD-ROM. You should make the CD-ROM drive a master device on
its own IDE channel, or (if possible) upgrade the CD-ROM drive’s firmware to
utilize more reliable timing. If the CD-ROM manufacturer has no firmware upgrades
available, and you cannot reconfigure the CD-ROM on another IDE channel, you’ll
need to replace the CD-ROM or hard drive.
Why is it that the CD-ROM
drive will not read or run CD Plus or Enhanced CD titles?
This is a known problem with Acer CD-ROM models: 625A, 645A, 655A, 665A, 525E,
743E, 747E, and 767E. The CD Plus (or Enhanced CD) titles use a new data format
that was recently released by Sony. The new format is for interactive CD titles
that incorporate video clips and music, and the data structures on these CDs
cannot be recognized by these CD-ROM drive models. In this case, you’ll need
to upgrade the CD-ROM drive outright to a newer model that can accommodate newer
file types.
Why is it that the LED indicator
on the CD-ROM is always on?
The drive seems to be working properly. This is not necessarily a problem. Some
CD-ROM drive models (such as the Acer 600 series) use the LED indicator as a
“ready” light instead of as a “busy” light. Whenever a CD is loaded in the drive,
the LED will be lit, and will remain lit whether the drive is being accessed
or not. This feature tells the user whether or not a CD-ROM disc is currently
loaded in the drive by simply checking the LED. The CD-ROM drive might have
a jumper that allows you to switch the indicator light from “Ready” mode to
“Busy” mode.
Why can't I play CD-audio
on a particular CD-ROM under Windows 9x?
Replacing the CD-ROM resolves the problem. This is a known incompatibility
issue with Acer 525E CD-ROM drives and Windows 9x (this does not affect the
integrity of programs and data). Windows 9x will mute the CD-audio on this and
many other brands of double-speed IDE CD-ROMs. If you cannot obtain a patch
directly from Microsoft or the CD-ROM manufacturer, your only
real alternative is to replace the CD-ROM drive.
© ICEDHOUSE Productions 2000