redump.info Forum

I managed to get one previously undumpable to dump and ice exe said no errors (single track game) Your my personal saviour

But Im having a lot of read error issues with section 48, even with the disc i dumped, I had to remove sections 31-47, and redump them before the drive would physically dump section 48. Can you work on the section 48 bug please jamjam.

And BTW DDump did nothing when i ran it, CDRWin said my drive was 3:0:0 and mthat didnt work, in the end i tried jamjams setting 0:0:0 and that worked.

Jamjam maybe you need to right a tool that does the DDump part to get the drive id.

Ok, new version (0.2a) which adds the ability to change some options. If resuming from a previous dump, don't change the commandline options from what they were (as it may not resume or clean up files if options result in different sections to original options).
@Pikmin
I was talking about ddump, the program to dump safedisc discs. I'll rename to DCdumper to avoid confusion.

@tossEAC
Try the new version with option -c400000. Also, if it gets to the end of execution and hasn't dumped everything, there's no need to delete anything (unless it ended badly and didn't write a file properly). The program will resume where it left off.

-c400000 should also be used by "Lite-On SOHD-167T", to avoid the LBA errors.

Heres a fix that would be easy to implement with an option.

My drive struggles to initialise the dump from 44990, but it has no problem if it first trys from 50000, then i cancell, and jog back to 44990, then it will read no problem.

So the fix would be for Section:2 to be dumped first, then Section:1 then Section:3 --> onwards.

What do you think jamjam sound possible, ill try it out if you like.

Another suggestion for an option aswell as the other suggestion, would be to have it read three sections, then verify three sections, to avoid the drive going from the end to the start, which it doesnt do very well.

I just got a disc to dump section 1-49 initial dump, no read errors, but then when it went back to the start to verify, section 1+2 had read errors, im hoping all other sections get matches, as dumping the first two sections is not as big a problem as dumping the last two.

I fail to see the difference between faking a read from 50000, or trying to dump a different section then going back to the section with a read error (which is what it does currently). It doesn't matter if there are read errors, as long as any two times it gets dumped with the same hash (after the match it doesn't try again). However I can implement it if it is necessary, and I can see how it may be if there is one section left which errors, as there is nothing left to jog it.

If it says initial dump, it read the section for the first time, hash stored. Nothing to compare against so it may have been read wrong.
If it says read error, the read error has been caught, hash not stored. Likely it errored in the same way CDRWin wouldn't start to read anything. Not a major problem.
If it says match, the read just done matches one of the previous successful reads. Rejoice etc
If it says non-match, it was read, and there were previous reads, but the current read doesn't match any of the previous. All or all but one of the reads so far have errors.

How about reading from start to finish, then from finish to start? I assume the big jump from end to start may screw it up sometimes atm, this way may be more gentle and have the desired effect.

You sort of understand, but i dont think you see fully, and its not your programme at fault. Its great stuff

I'll explain a bit more later, at the moment im using a combination of cdrwin and your tool, cdrwin to dump the last sections.

I have been using it all day, and I understand how it works, i even have one good dump to prove it, its when it doesnt work, the main problem lies in going from the end of the disc to the start, this drive aint a native gdrom drive afterall.

I hope you can try those suggestions i made earlier at least try reading Section:2,1,3 in that order to see if it helps ill test it if you can writew the option, it wouldnt hurt to give it a try, then we can deal with the end sections later.

DOES this help, If it says initial dump, that means the drive has read the disc thats all, but good, but may contain errors.

If on the verification pass it says match, match, match.... sit back and relax.

If it says no match, then this is a big problem as its 99% certain that the discs scratches are causing the problem.

But if it says read error, then this is not because of scratches, its more to do with the drive, gdrom and software.

If you have a read error on SECTION 1 and 49, I Really dont think the samsung drive can read section 1 then go to section 49, Im pretty sure this is impossible. Not without reading somewhere in between, which could be the fix you need. By maybe telling the programme if it needs section 49, then try to start reading before that, but only read to memory then once it has found its position the read could be moved up one section untill it finds its position and repeated untill you get to the section you actually need ie. 49

So if section 1 and 49 read error. Then even after the tenth pass, it will just keep saying read error on and on.

But the first section is easy to fix just read it with cdrwin.

The 49th Section, is more difficult.

You can tell CDRWin to read from 477128-549150 then split it into 24199728 byte packages, and just keep the ones you need.

477128 was the highest position I could find that CDRWIN would start from, higher and you just get an error.

Does that make a bit more sense now jamjam

Trying a disc now, 49 Initial Dumps, no rewad errors, goes back to verify, guess what read error, Non-Match, Non Match.

Basically I think these non matches are because the first read error cocked it up.

This programme still needs lots of work, this ones giving every section non matches, i have had enough for today.

JamJam could you help me with this aswell if at all possible.

I have a xml file which i need to remove certain lines quickly

Example.

    <Event InTC="00:00:33:17" OutTC="00:00:33:19" Forced="False">
      <Graphic Width="1241" Height="966" X="47" Y="63">Ep 1_exp_exp_exp_0089.png</Graphic>
    </Event>
    <Event InTC="00:00:33:19" OutTC="00:00:33:20" Forced="False">
      <Graphic Width="1241" Height="966" X="47" Y="63">Ep 1_exp_exp_exp_0090.png</Graphic>
    </Event>
    <Event InTC="00:00:33:20" OutTC="00:00:33:20" Forced="False">
      <Graphic Width="1241" Height="966" X="47" Y="63">Ep 1_exp_exp_exp_0091.png</Graphic>
    </Event>
    <Event InTC="00:00:33:20" OutTC="00:00:33:22" Forced="False">
      <Graphic Width="1241" Height="966" X="47" Y="63">Ep 1_exp_exp_exp_0092.png</Graphic>
    </Event>

I would like a tool that could remove all the lines that have this one thing in common.

    <Event InTC="00:00:33:20" OutTC="00:00:33:20" Forced="False">
      <Graphic Width="1241" Height="966" X="47" Y="63">Ep 1_exp_exp_exp_0091.png</Graphic>
    </Event>

You see on this example I have InTC="00:00:33:20" & OutTC="00:00:33:20" and the times are both the same, I Want all lines from this xml to be removed if InTC = OutTC. You will probably need to find a way to remove the two lines below the lines with identical times to make it work. ie.

      <Graphic Width="1241" Height="966" X="47" Y="63">Ep 1_exp_exp_exp_0091.png</Graphic>
    </Event>

Would this be hard to make a programme to do this, if not do you need an example xml to try it on, this would save me hours and hours of work and make me very happy, and I'll find a few games I have dupes of and you can have them when you send me that drive, I have a few xbox games i could send if that will be a help, I dont have the space to keep all the games I have so getting rid of ten xbox games will at least make 10 spaces for games I havent got.