This morning I went to rip an Audio CD with Exact Audio Copy (EAC) v0.9 beta 4 and EAC did not recognize that a CD was in the drive. I have 2 CD drives, and with an Audio CD in each, the tracks weren't displayed in the main EAC window like usual after selecting either drive. I then went to My Computer and double clicked on the 1st CD Drive and instead of the usual displaying all the tracks on the CD (icons with Track1.cda, Track2.cda, etc.), it displayed this error message: "This file does not have a program associated with it for performing this action. Create an association in the Folder Options control panel." So I went there and "Play" is the only Action listed, but I can't edit it to see what program is set to play it. I added the default action "Open" using explorer.exe, which allowed me to double click on the CD icon to view the tracks on the CD, but it opened a new explorer window to display the tracks of the CD, not the same one like usual. I deleted both Play and Open and now it works like it used to, opening in the same window, and I no longer get that "This file does not have a program associated with it for performing this action..." error message. However, EAC still doesn't recognize audio CDs. I tried uninstalling EAC, deleting the EAC registry key under HKEY_CURRENT_USER\Software\AWSoftware and then reinstalling it, but it still doesn't recognize it. Then I tried installing the newest version of EAC, v0.9 beta 5 (which is not nearly as well tested as beta 4, which is why I don't have it and don't want to use this version), which doesn't use an installer (you just unzip it and put it where you want and run it), and right off the bat it detected the CDs in both drives. I don't know if this has to do anything with AutoRun or AutoPlay settings, as I messed those up pretty good with TweakUI as I had to do lots of things to get them to finally stop. I ran my weekly Spyware scans with Ad-Aware, Spybot, and Microsoft AntiSpyware last night and nothing was found. I just ran a virus scan with AVG Free Edition with up to date definitions and it came up negative as well. If anyone has any ideas, or more information is needed, or anything else like that, please let me know. Any and all help is greatly appreciated. Thanks.

I figured it out. I had to change the Interface from "Native Win32 interface for WIn NT & 2000" to "Installed external ASPI interface," using the wnaspi32.dll file.