You may need to uninstall the given software and install again to hopefully get the appropriates settings and links back in order. The following should give you an idea of how those things work on an XP computer. Good luck.
1. The "Compact Disc File System (CDFS)" for Windows can read compact discs (CDs) formatted according to the ISO 9660 file system standard to include Joliet. The ISO 9660 specification defines three methods or interchange levels for recording and naming files on a CD and Windows supports up to interchange level 3. Please note, this article states that CDFS does not support the Rock Ridge Interchange Protocol extensions to ISO 9660 and reads only the ISO 9660 structure on such discs, and also states that if a CD-ROM drive is compatible, the standards for which the system can read recorded CDs. For your reading pleasure also, "Multimedia: Some CD-ROM Drives Can't Properly Read Disc (Q148351)."
2. When a CD-ROM is inserted into a CD or DVD drive, it may not run automatically and can occur because the Autorun.inf file and the programs that the Autorun.inf file is designed to run is not executed if the user is not logged on to Windows with either Power User or Administrator rights. By default, only users who are logged on to Windows with either of these rights are allowed to install software (an .inf file extension is considered to be a setup information files and therefore, the file is not executed), [Q314855].
a. Autoplay tab Missing and CD's Don't Autoplay: Since registered components on a system is invoked using the Shell Hardware Detection service and also because non-volume handlers are invoked through it, this service cannot be deactivated. If it is, a user may find they have no access to or can they use either Volume-based or Non-volume-based devices.
b. The primary purpose of Autoplay is to provide a software response to hardware actions initiated by the user on a machine. This feature remained roughly the same from Win95 though W2K and WinME because up until recently there have been very few new scenarios with regard to user-initiated hardware events that could trigger a useful Autoplay action. But lately, with the spread of digital multimedia content (music, graphics, and video) and of the many devices to generate or consume that content, many new scenarios are begging for expansion. In addition to refining the existing Autorun.INF mechanism, audio CD Autoplays, and DVD video Autoplay, support has been added to handle digital music (WMA/MP3), graphics, video, CD burning, video cameras, and other hardware devices.
c. If you've installed software from a CD, you've used an Autorun.INF which the majority of the setup CDs use. The typical user scenario is: a CD is inserted into the CD drive, the setup program runs automatically, and the user simply follows the on-screen instructions generated by the setup software. The Autorun.INF file sample section follows the typical format similar to the following where the first line contains the self-executing Exe file which also contains the text string for an icon. In addition, there could also be values of UseAutoPlay (when present, it will take precedence over the open and ShellExecute values and is intended primarily for use with multimedia content for which Autoplay support was added to Windows XP), label (used to represent the associated drive in the Windows shell), and ShellExecute (works with file associations to run the application associated with the specified file):
3. When determining what actions to suggest or perform in response to an event, Autoplay on WinXP considers the event in conjunction with the various programs registered on a computer. In contrast before, it would always statically run the same application pointed to in the Autorun.INF file, or play an Audio CD or DVD movie using the respective default application. Now, two categories of events are handled:
? Volume-based device events are events that affect devices that appear as volumes -- that is, all disk drives accessible via Windows file system APIs. This includes CD drives, removable disk drives, hard disk drives, removable media readers, and mass storage devices. Basically, if it shows up under My Computer with a drive letter, it's a volume-based device.
? Non-volume-based devices include, well, everything else. Specific examples of these devices include digital video cameras and portable music players that do not expose their content as a file system supported by WinXP. This does not mean that all video cameras and portable music players are non-volume devices. For example, newer digital cameras and portable music players that use the USB Mass Storage stack are treated as volume devices since they appear to the system as volumes. Digital camera devices which are non-volume devices get special treatment from Windows. Even though they are non-volume devices, they are handled by the Windows Image Acquisition (WIA) component for backward compatibility reasons.
4. The file "AutoPlay.exe" (62KB) provides some insight into the Shell Hardware Detection service processing of hardware events which listens for updates to the %SystemRoot%\Autoplay.log file and dumps the changes to its edit box. This tool is mostly useful for diagnosing non-volume Autoplay problems, but it can also be used in some cases to trace volume operations.
5. "Q310123" lists 33 error codes that may be reported by Device Manager and provides possible resolutions. A "TechNet" article covers up to 49.
6. Use the Windows "Drivers and Network Adapters" troubleshooter.
7. The article [Q321641] describes how you can troubleshoot issues reading CD-ROM or DVD-ROM optical discs and discusses how to troubleshoot common issues.
8. The article [Q824894] describes issues that may occur if your CD-ROM or DVD drive is not configured correctly, the program CD-ROM or DVD is damaged or dirty, or the Microsoft Data Access Components (MDAC) installation is damaged, and suggest troubleshooting tips which may assist.
9. The article [Q324129] describes how to troubleshoot issues such as the following that occur if you write data to compact disc recordable (CD-R) and compact disc re-writable (CD-RW) optical discs and how to troubleshoot issues with CD-R and CD-RW drives:
? You may receive various disc write error messages.
? You may experience issues with the drive and the built-in recording feature of Windows XP
? You may experience issues with third-party programs that you use to write data to the disc.
10. Supplemental reading:
a. "DMA Mode for ATA/ATAPI Devices in Windows XP."
b. "Device Settings Are Hard to Find in Windows (Q247426)."
c. "HOW TO: Manage Devices in Windows XP (Q283658)."
d. "Add or Remove a Windows Component in Windows XP (Q307894)."
e. "Troubleshooting Device Conflicts with Device Manager (Q310126)."
f. "TweakUI Not on Windows XP CD-ROM (Q310176)."
g. "CD Audio Is Played Even Though an Audio Cable Is Not Connected to Your CD-ROM Drive (Q310439)."
h. "How to Disable a Service or Device that Prevents Windows from Starting (Q310602)."
i. "Your Computer May Stop Responding After You Remove Either a CD-ROM Drive or a DVD Drive from the Drive Bay (Q310664)."
j. "Windows XP Hangs When You Try to Install Programs (Q313554)."
k. "CD-ROM Access Is Missing and Messages Cite Error Code 31, Code 32, Code 19, or Code 39 After You Remove Easy CD Creator (Q314060)."
l. "Incorrect Contents Are Displayed in Windows Explorer (Q314939)."
m. "Your IEEE 1394 or USB CD-ROM or DVD-ROM Drive May Not Be Recognized in Windows XP (Q323507)."