Dreamcast dumping on dclinux?

You're prolly better off finding out why it's not working like it should, instead of resorting to inferior methods. Are you dumping with the samsung drive and taking the cover off when swapping discs?

With a Scythe IDE/SATA to USB (JMicron based, ODDs runs fine with this) and NEC DV-5800E (Crossflashed to LT SHD-16P1S, Mediatek based DVD-ROM, like  SH-D162C) I can perform the trap disc (Burned in a Samsung CD-RW disc manufactured by Daxon, others) methode (Removing the cover and stoping the unit using startstop) and dump the high density area. However, the GD-ROM which I own is too damaged and (Once descrambled by ice.exe), so, the data tracks doesn´t match the ones in Redump´s database, whereas the audio tracks does.

At least as far as I tested, the optimal read speeds were 16x or 24x. Others only gave a lot of errors. I dumped the GD-ROM using CDTool by Truman (Setting manually the desired range to dump), which also allow the use of C2 pointers as a additional layer for catching read errors.

IMHO, you should try another disc for burn the trap disc. Maybe, you are employing a wrong type of media. I had to try lots of discs, until I found the correct one, the 10x Samsung CD-RW by Daxon I currently own for trap disc. Moreover, the IDE to USB adapter you are using is critical too. As far as I know, many IDE to USB adapters doesn´t operate properly with ODDs (ATAPI) drives.

Yeah it only reads the TOC afaik, so brand shouldn't matter.. just make sure that it's refreshed properly..

Some things that you can try is testing different read speeds, retrying a couple times with reading (sometimes it won't read a number of times, but then at one point it gets past the seeking and starts reading), and also making sure that clonecd device driver isn't running in the background (had some problems with this in the past).

I also bought one of those IDE>SATA usb convertors from ebay some weeks ago. I'll give it a try with my samsung drive when it arrives in the mail.

pablogm123, I am aware of the fact that different media have different reflective properties.
But isn't the laser power adjust at the factory, (with the pot-meter on the assembly) and therefor constant? (Please do correct me if i'm wrong)

btw Jackal, you mentioned my idea as a 'inferior method' in your reply. Could you elaborate one that?
I would think that having full access to the GD-drive, meant to read GD-roms in the first place, would be superior  to reading the dense area using hacked methods...

if it has a data track there should be no offset (due to sync).
If there is a audio track, offset could be calculated as usual (Read data track, and count bytes in last sector).

I see no reason why this would be a problem...
Except for maybe overreading into lead-out, but the 162 drive doesn't do this eighther..