Search options (Page 18 of 32)

Same here.. LG CH10LS28

Only one I know of: http://code.google.com/p/rubyripper/

Like I said, it's a command line (DOS) application.. You'll have to use the command prompt

German instructions: Öffnen Sie das Eingabeaufforderungsfenster, indem Sie auf die Schaltfläche Startklicken, auf Alle Programme klicken, auf Zubehör klicken und dann auf Eingabeaufforderung klicken.

Please be more specific.. tell us what command you used and provide a screenshot or text copy of the output.. You'll have to use the command prompt and use 'psxt001z --libcryptdrvfast [drive_letter]'

If that command doesn't work on the version I linked, then try this version (it's the same one that's mentioned in the guide): http://www.mediafire.com/?lpxbegqdt1tq23p .. If that one doesn't work either, try using a different drive.

Alternatively, you can provide the other dump details (track01 + track02 size/hashes, write offset, ring etc.) and we can add the libcrypt data from another source (once we add the complete dump into the db you'll be able to grab the .sbi). Here's the psxt001z sectors.log output from a German image:

MSF: 03:14:29 Q-Data: 41 01 01 03 12 09 00 03 14 2d cc c2
MSF: 03:15:24 Q-Data: 41 01 01 03 13 20 00 03 15 04 af d0
MSF: 03:21:55 Q-Data: 41 01 01 0b 19 55 00 13 21 55 44 48
MSF: 03:24:12 Q-Data: 41 01 01 03 02 12 00 03 20 12 30 0e
MSF: 03:25:03 Q-Data: 41 01 01 03 23 13 00 03 25 0b 96 1a
MSF: 03:28:28 Q-Data: 41 01 01 03 06 28 00 03 2c 28 ae 9b
MSF: 03:32:19 Q-Data: 41 01 01 03 30 59 00 03 32 1b 9d 6d
MSF: 03:34:51 Q-Data: 41 01 01 01 32 51 00 43 34 51 2a 66
MSF: 09:27:55 Q-Data: 41 01 01 0d 25 55 00 29 27 55 69 c0
MSF: 09:28:71 Q-Data: 41 01 01 08 26 71 00 89 28 71 96 71
MSF: 09:35:52 Q-Data: 41 01 01 09 73 52 00 09 37 52 c7 f5
MSF: 09:38:04 Q-Data: 41 01 01 01 36 04 00 19 38 04 cc 90
MSF: 09:38:58 Q-Data: 41 01 01 49 36 58 00 0b 38 58 aa b2
MSF: 09:41:59 Q-Data: 41 01 01 0b 39 59 00 49 41 59 a9 c2
MSF: 09:46:13 Q-Data: 41 01 01 09 44 1b 00 09 46 03 e8 90
MSF: 09:48:59 Q-Data: 41 01 01 09 44 59 00 09 08 59 68 07

Original sectors: 48
LC1 sectors:      0
LC2 sectors:      0
Other sectors:    16

And I wonder how many trurip dumps 

708 is known to have issues due to a problematic chipset.. You're prolly better of getting a newer version (like 716/755/760)  or a CDRW plexwriter if you can

You need to use MineSweeper for dumping the ISO.. XBC is only for SS+PFI+DMI.. please follow this guide: http://forum.redump.org/topic/6073/xbox … tructions/

You still have to get the offset using a PC drive.. and iR0b0t claims that low density and high density area's can have different write offsets  I don't think a gdrom drive can dump scrambled?

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?

BTW. I feel that this topic shouldn't be a sticky, because it states opinions rather than general policy

ps. I agree with themabus' feeling that things sorta got 'out of hand' and we just kept adding more systems which less and less suitable for our initial dumping method. Go have some talk with ripper about  'half sectors' and sector overlaps etc and you'll learn that your proposed solution prolly isnt even gonna cut it. A custom format would be needed in order to really preserve all these mastering errors and oddities.

And maybe it's a good idea to just mark any dump that isn't preserved correctly under the current standards as 'yellow'. Otherwise we just keep on mixing flawed dumps with known good ones (then again, how can we be sure a dump is good if we keep raising the bars and keep on adding new fields and new requirements?).

The dumping format is simply incomplete and out of date.. There's little point in asking people to dump subchannels if this data is mostly discarded and it only serves for a flawed interpretation of what the gaps should be like.

afaik it's buggy and hasnt been worked on for years. Just wait some more years for trurip or robotrip or whatever's supposed to come out (or code it yourself, I know you have the skills ).. Maybe we could have a decent open source project going if the authors of these programs didn't have such big ego's. Then again, if you have two parties who aren't sharing any knowledge, you can't expect one of them to start doing that.