I've noticed that there have been a few cds that cause EAC to crash whenever I load them. The same cds affect versions 0.95b4, .099 pb1 and pb3 on a new computer I just put together. I've been using EAC for about a month on this new computer and have ripped about a dozen cds without problems I have, however, been able to successfully rip these problematic cds on a different computer. So basically I'm having a hard time pinpointing the exact problem: The DRIVE, the Firmware for the drive (which I updated, but that was a while ago) EAC, or the CD??? My computer only crashes once I load EAC after I've put in one of these cds, My DVD-drive (Lite-on SHM 165P6s - MSOR ) will detect the disc and I can even play it in foobar, but like I said when I launch EAC my computer freezes up. Does anyone have any suggestions?

What ASPI layer are you using?

EAC can also freeze up if you use the wrong gap detection method. Cycle through them until you find one that works.

I'm not sure... How can I find out?

In an effort to help determine the cause of the problem I swapped the drives on the computers. I was able to rip the problematic cd on the same Lite-on drive after I moved it to a different computer. So the problem is not with either the cd or the drive, but my computer. EAC seems buggy on it. In addition to the problem stated above I get a different problem when using a BEN Q 1650 drive with it: I have a "good" disc in the drive (one i've already ripped with the Lite-on), load EAC without problems, then click on "detect read features" and it tells me that I don't have a cd in the drive. EAC also crashes when trying to load one of the problematic cds with the BEN Q. I'm using a slipstreamed custom version of XP, b/c my new computer doesn't have an internet connection so I couldn't get the updates. I'm beginning to think this may be causing the problem. It just seems too buggy. I'm going to have to load the LAN drivers, then take it with me to work so I can download all of the updates for it, unless anyone thinks they may know the real cause of the EAC problems. Thanks.

EAC Options (F9) --> Interface tab

I have "Native Win32 Interface for Windows NT/2000/XP" selected. It's very strange. I just check it again. I put it 5 cds (that I had ripped successfully before) no problems .. EAC recognized them right away. The I put in one of these problem cds and it crashed... Is it possible I need to install an ASPI layer, or something?

Should I follow these steps: Problems Getting EAC to Read Discs

If you've downloaded EAC but it doesn't seem to recognize your drive or work properly, try these steps, listed in order of least possible change. If you have XP, see the notes below, too.

First step, start EAC, go to EAC, EAC Options, Interface. See if it works on either the Native Interface or the ASPI Interface. (If you change this, you have to close and restart EAC for the change to take effect.)

If that's not enough, this next step fixes things for lots of people with Win2K or XP: drop the Nero ASPI file (WNASPI32.DLL) in the same folder as your EAC program. (ASPI is a software layer that enables programs to communicate with devices.) You can get WNASPI32.DLL via the link at the bottom of the Nero Download Page. (Be sure you have EAC set to use the ASPI Interface, as above.)



Someone wrote that here about 5 years ago. Does it still apply today?

Just downloaded Nero's ASPI Layer (wnaspi32.dll) I'm going to give this a try.

That seemed to do the trick. Very simple. Thanks alot!

You're welcome!

The funny thing is that the Nero ASPI driver has been giving people problems lately that have been fixed by either using the native interface or using a different third-party interface. I'd very much like to get to the bottom as to why this is becoming such a widespread problem.

I'm not sure what guide you're using but I recently changed one of the wiki articles to provide better assistance in any of these situations...

They do appear to say the similar things, though.

Have been getting the same issue. Have used EAC for years and always had the Nero ASPI Driver in the EAC folder. Only ever got 99.9% accuracy reported.
Just recently I started getting clicking instead of audio after extraction or the extraction would take forever, just building up the red lights in Error Correction.
Just changed firstly to the Native and it is fine and similarly with the ForceASPI. Both show 100.0% accuracy.
What gives with the old Nero ASPI?

Dunno, but I don't think you need to worry about 100% vs. 99.9% quality. I'd honestly be surprised if you didn't ever find a situation where the very end of the track resulted in a single pass of re-reads with any given ASPI driver.

cheers greynol, but was not really concerned with the 100 vs 99.9. It was just an observation after changing from the Nero ASPI layer.
More worried by the clicking that started instead of audio in any extractions I did or the length of time it would take, usually just increasing the red lights in "error correction". Sometimes 20 m intes for 1 song and then it still had clicks all through it instead of audio.
Never had this before and all was working fine for a very long time.
Have now tried both of the alternative ASPI options and both fix the problem.
Was more concerned at why the Nero ASPI layer would die all of a sudden.

Thanks again

Well if one layer resulted in less seemingly unnecessary re-reads at the end of a track, I'd certainly use it. This can be quite annoying for those with drives that don't go much beyond 4x in secure mode.
I'd really like to know why this is happening all of a sudden and to so many people. Was it a Windows update? An update for some other program? An updated chipset driver? Moving to the new version of EAC? I don't really suspect the new version of EAC, but maybe it has something to do with the prefetch file that Windows creates?

I'm just grasping at straws here. I haven't been able to duplicate the problem on my system.

Cheers back

Nothing I can think of really, and had been using it with the current config for ages. Chipset et al were all done last year and being a Shuttle, don't come out too often. Have had SP2 in XP for ages, so not a windows update, and the only things I had installed recently that I could think of were Daemon Tools and MacDrive. Have removed Daemon and will try removing MacDrive to see it changes things. Funny, but it just started a few weeks ago. I thought it was my drive, which is a few years old and has had a fair workout. Bought a new Liteon and the same thing.
Very strange, but now with either ForceASPI or Native, it is fine. Will report back if it is MacDrive.

After uninstalling DAEMON Tools, you might also have to remove SPTD manually.
http://www.duplexsecure.com/en/downloads
Running the program should give you the choice to install or uninstall.

Victory greynol. Had uninstalled MacDrive and that wasn't it but that SPTD uninstaller found an old version of it and uninstalled it. Problem fixed now using the original Nero ASPI layer.

So how does one run Daemon Tools and EAC? Will have to do a search for a workaround.

Cheers for your help

What was the version?

Why did you decide to go back to using the Nero driver?

Try the current version of SPTD.

Not sure, but Daemon Tools was installed with the file daemon4091-x86.exe



Force of habit, really. Never had any problems with it until this. Is there a difference in quality of rips or reliability in any particular one?



Will give it a crack!

Cheers

I've run into my fair share of people who insist that Nero gives you a better rip and not a single one have them has ever been able to substantiate it with tangible evidence. Like with much of the other stuff you might read in online guidez, I chalk it up to FUD.

There are legitimate reasons to use a third-party ASPI layer, but I don't believe improved quality is one of them.

BTW, The version of SPTD that comes with DAEMON Tools 4.09.01 is 1.43. This version has been known to cause problems for EAC, I just haven't seen it brought up as an issue for a couple of months now.

http://www.digital-inn.de/exact-audio-copy...-using-eac.html
http://www.hydrogenaudio.org/forums/index....showtopic=55063
http://forum.duplexsecure.com/showthread.php?t=274

I'd still go with the latest version of SPTD since it rectifies even more issues with EAC.

I have also Native Win 32 ... interface. My problem is that sometimes it simply crashes sometimes it does not, no matter what kind of CD I have. It works well from time to time, but suddenly it is locked. I have to reboot my machine.

I have recently started to use EAC for ripping audio CDs to OGG, so I am quite new to this. As external encoder, I am using oggenc2 (with aoTuVb5). Should I use some older version of EAC or other Oggenc (for instance the one using libVorbis v1.2.0)? (By the way, what is the difference between those two oggenc encoders?) Is there some solution to the problem?