Hi,

I've been using EAC for a couple of years with no problems. A couple of weeks ago I bought a CD that I wanted to rip, but as soon as EAC started reading the disc, the error correction grid started to fill up with red blocks. I thought maybe there was a problem with the disc, or it was copy protected, so I tried other CDs that I'd ripped successfully in the past and the problem occured with all of them.

I uninstalled EAC, rebooted, then downloaded the latest version and installed that. I tried ripping the new CD I'd bought and it worked fine. I received another CD in the post today and now I'm having the exact same problem and again, it affects all discs, even ones that I've ripped successfully in the past.

The computer has two optical drives, a BenQ DW-1650 and an LG GSA-4163B, both with the latest firmware. This problem affects them both. I've tried ripping discs with WMP and it works just fine, but obviously I'd much prefer to use EAC if possible.

Does anyone have any ideas on what could be causing this? Thanks in advance.

Moderation: Moved to CD Hardware/Software.

Have configured your offsets correctly?

Any chance you have used Alcohol software in the meantime?

(I've seen reports of people having problems with EAC after messing with Alcohol)

I don't think an unconfigured offset will explain for the ripping problems funkinlesson described...

But as I understood correctly you're ripping problems started overnight, a fresh install solved the problem temporarily (you were able to rip 1 disc without a problem) but they started again without plausible cause ? Are you sure you didn't install any software which might have corrupted your aspi layer ? Did you try to use an external aspi-layer and if you already did that, did you try the native one ?

It looks like that may have been the problem. I've always used the DLL file that came with Nero, but I've just altered the settings in EAC to use the native ASPI layer and it appears to work. I wonder why it worked OK for months and suddenly stopped working though.

Anyway, thanks for the prompt responses. I'll be back if it breaks again, haha.