So I'm sure that the ripped tracks are ok. Now I burned CDs and when I rip the burned CDs with EAC again, no tracks could be verified as accurate. I also get the message "You may have a different pressing from the one(s) in the database". The tracks self are ok, they have all a quality of 100.0 %, e.g.:

I tried it, but my problem is not solved. My drive has an offset of +6. So I created with CUETools an Image (and CUE) with an offset of -6 (I thougt: +6-(-6)=0). After burning and ripping: "no tracks could be verified as accurate". After that I tried an offset of +6, same again: "no tracks could be verified as accurate".

What differences does CUETools show when you Verify the original CD rip and the rip from the uncorrected burned copy (post both CUETools logs if unsure, preferably from a CD with a single pressing in the AccurateRip section)?

What differences does CUETools show when you Verify the original CD rip and the rip from the uncorrected burned copy (post both CUETools logs if unsure, preferably from a CD with a single pressing in the AccurateRip section)?

My problem is solved, it was my mistake. I've entered my desired offset AND used the "fix offset"-script of CUETools. I misunderstood that: the fix-offset-script removes offests (to zero offset), so my offset was not considered.. The input file (with zero offset) was identically to the output file.Without the fix-offset-script the given offset is considered. After burning and ripping again, the log-files of EAC and CUETools are identically.