1

(2 replies, posted in General discussion)

Really helpfull tools, thanks for the share.

A 'read speed' option would be nice.
Now i have to set read speed through a external program like plextools.

Maybe have a variable speed setting (try lower speed on read errors)?

Other then that, DCDumper has been working great for me.

I've got dcdumper to work on my 162c using my usb bridge.
I set the read speed to 4x using plextools. That seems to have done the trick.

DCdumper.exe f -sf -t5

only one read error on first disc access, but it got corrected by fake-reading on first try.
Everything dumped correctly afterwards.

Its a lot easier having this drive externally on usb then having it hang there on a IDE cable.

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..

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...

I don't see how the media could be a problem... as long as the drive reads the modified toc, it shouldn't care about the media, no?

I own a no-brand ebay bought Sata/ide combo to usb 2.0  cable (ID 152d:2338 JMicron Technology Corp. / JMicron USA Technology Corp. JM20337 Hi-Speed USB to SATA & PATA Combo Bridge)

That's exactly what I'm doing. but i'm having a hard time getting it to read the high density area.
When the drive is on a IDE-USB adapter it does not read anything at all. Just constant read errors.

i've been using dcdumper, and have been able to sporadically read the high dense area, with the help of its fake read functionality, but cdrwin is a no-go.

I flashed the drive back to stock, thinking that maybe the kreon fw could be causing problems, to no avail.

Anyone ever tried dumping DC on LinuxDC (dreamcast linux port).
A.f.a.i.k. there is a GDrom driver and broadband adapter driver.

So if we had full access to the drive, wouldn't we be able to read the GDrom and dump it over lan?
Since I've been having only sporadic success using the swap trick, I am looking for a more easy solution.