EAC doesn't always accurately detect drive features.

What do you think?

Interesting. Never had the problems he's talking about though, even on badly scratched CD's. I couldn't find anywhere in the article where he mentions what kind of drive he has. I would guess it's more related to his drive than EAC.

Yeah, I thnk you're rigth. This is just a workaround if you have problems.

Well, he stumbled across the two most probable miss-detections EAC can do:
1. He has a drive that says it supports C2 error detection while it doesn't.
2. He has a drive that says it does not cache audio while it actually does.
If he had originally enabled the checkmark at "drive caches audio", he probably wouldn't have had any problem, because even with C2 detection turned on, EAC still reads every bit of audio twice in secure mode, so when EAC works around the drive cache, it should still find a problem, even if C2 missed it.
Sadly, and as André always said, there is no secure way for EAC to detect these two features (it can safely detect accurate stream though, but that only makes a 2% performance difference), so if you are in doubt, disable the C2 and enable the audio cache flags.

cu,
sven

EAC works wonderfully on my laptop, but when I first tried to rip on my main desktop machine I got WAV's full of silence. After a quick fiddle with the drive settings in EAC, I got the drive working.

I would be royally pissed if EAC incorrectly detected drive features. I depend on EAC to make accurate rips.

Calvin

No word from Andre yet about this..

I switched my EAC to "Drive caches audio data" and disabled C2 despite what the detect found. Since then, I have had flawless rips... Every once in a while I get a sync error, but after I clean the disk and re-rip that one track, everything is fine.