Hi - dbpoweramp uses AccurateRip as a checksum reference. Therefore you are slightly insulated from different drives, as if the rip is not accurate, ie the AccurateRip checksum is different, it will initiate a re-rip with a slightly usually slower strategy until it gives up or the cecksum is right.
dbPoweramp's ripping strategy is here
http://www.dbpoweramp.com/secure-ripper.htm
If you are ripping a disc that is not in AccurateRip, - there are a few such as very new discs or magazine covers - then it can be set to rip using at least two different strategies, which takes longer and cross checks them. If both the checksums correlate then you are very probably ok.
dBPoweramp on their ripping forum provide a constantly updated list of CD ROM drives that is derived from the AccurateRip checksum queries - and you can see the top performers. Its interesting to note that firmware update on CDROM drives can affect accuracy.
http://forum.dbpoweramp.com/sh...e-Accuracy-List-2011
So in short if you use AccurateRip the CD rom accuracy is not as crucial, if you rip CDs that are not in the database then you can optimize that ripper to take longer to produce a reliable rip that cross checks with different strategies.
Out of the 1000 odd CDs I have ripped. the only accuracy issues I have ever had is when the disk has been phsically damaged with heavy scratching or very occasionally on very long discs the ripper falls back to the backup ripper strategy on the end track - but still gets the CRC check correct.
I use a HL-DT-ST_DVD-RAM_GH10L
Simon