I'm not really in the mood to check all posts, but I just wanted to let you guys know that the mastering tool for Xbox discs is in the SDK, so maybe the algoritm for the padding can somehow be traced there.

502

(1 replies, posted in News)

New Xbox1 dumping guide is added. It's a really simple dumping method (thanks to all the talented people involved, excluding myself tongue), but requires a DVD drive that is flashed with Kreon firmware. These Kreon compatible drives are fairly cheap in most parts of the world, so now the time has come to dump those Xbox discs!

Stuff needed:
- Xbox Backup Creator 2.9.0.425
- ss_sector_range_1.0e
- FreeCell 0.2-RC1
- abgx360 v1.0.6

XBOX 1 dumping instructions:

Instructions for Kreon drives:
- Dump the SS/PFI/DMI .bin files using Xbox Backup Creator.
- After you closed Xbox Backup Creator, press the eject button of the drive twice so that it will remount the Xbox partitions.
- Run 'ss_sector_range.exe SS.bin >sectors.txt' in the folder containing the SS.bin.
- Run 'FreeCell.exe Drive: sectors.txt' in the folder containing the sectors.txt.
- Now the Xbox game will be dumped to 'Track 01.iso'!

Instructions for 0800 drives (thx Starshadow):
- Grab Xbox Backup Creator 2.9.0.425
- On the Options tab, check "Build Clean ISO".
- On the Read tab, uncheck "Use Sector Mapper (Xbox One)".
- Click the Start button on the Read tab.
- A read error should occur shortly after starting the dump. This is normal. Check the box "Apply zero fill to all remaining sector errors." and click the "Zero-Fill Sector(s)" button.
- When the dump is complete, make sure that the log window reports exactly 65536 unrecoverable sectors. These are the security sectors. If the number is higher, this means there were actual read errors and your dump is likely bad.

XBOX 360 (XGD2/XGD3) dumping instructions:
- Use Xbox Backup Creator 2.9.0.425 with 'Build Clean ISO' option checked. XGD3 discs can only be dumped with 0800 drives.
- If a Kreon drive is used for dumping, mark SS as SSv1 in comments.
- If a 0800v3 drive is used, mark SS for XGD3 discs as SSv2 and SS for XGD2 discs as SSv1. (see note [1] below)
- After extracting the SS, run ss_sector_range on the SS.bin file to clean it and to obtain the security sector ranges.
- Finally, open the cleaned SS.bin file with ABGX360 and copy the text that is shown after "SS CRC =".

To see all the required information when submitting your dump, just look up some existing dumps in the db.

Some additional info on ring/dmi string pointing to supported regions:
W = World
A = USA (America)
J = Japan (or Asia)
E = Europe (might be Germany only for example, or any other European country)
K = (USA, Japan) or (USA, Asia)
L = (USA, Europe)
H = (Japan, Europe)

Good luck!

Notes:
[1] ss_sector_range will convert/downgrade original XGD2 SSv2 files to SSv1, so that 0800 drive SS files will match Kreon drive SS files

504

(5 replies, posted in General discussion)

Are you dumping backups too?  mad  lol

505

(11 replies, posted in General discussion)

Okay, the majority of people prefers more 'accurate' dumps, so I guess the current method will stay.

I just hope that it will be possible some day to make these dumps without the need of a modded console.

506

(11 replies, posted in General discussion)

Well, you beat me to it, I was still editing my post.. But the point that I was trying to make is that, if you sacrifice some (seemingly irrelevant) data, it would make it much easier to dump and secure these images, which is in the end at least as important as getting dumps that are a bit more true to the original, but still not exactly.

507

(11 replies, posted in General discussion)

Security placeholders are actually skipped by the dumping software, because of error sectors, so that data isn't preserved (16 x 4096 sectors). If random padding was skipped too, the dumping software could just copy the filesystem data, so then it also wouldn't have to worry about security placeholder locations. So the security placeholders can be labeled 'problematic' because of the inability to dump them in a reliable manner.

A practical disadvantage of the random padding is that scene rips don't include it, so unlike Wii/GC/Xbox360, it's impossible to convert Xbox1 dumps to Redump format without needing several gb's worth of 'patches' just for the random pattern, which isn't really game data. But I guess a similar situation occured with Dreamcast rips <> raw dumps. But AFAIK this is the only system that we have were maybe 75% of the dump data would consist of just random byte patterns that don't have any real use. I guess this point is only valid for 'Collectors' but it also means that less people will be interested in dumping/preserving these games.

508

(11 replies, posted in General discussion)

Checksum and size, of what? the image containing the padding?

To clarify, the random padding is used to fill non-Game sectors, so it's not a section, but it's spread across the entire image (except for the first part, which is the video partition).

509

(11 replies, posted in General discussion)

Here are some pros and cons of the random padding that is currently present in all Xbox1 dumps in the database:

Pros:

- It's on the disc. It can be dumped and therefore SHOULD be dumped for complete preservation.

Cons:

- It doesn't appear to have any purpose, not for security, not for anything else
- It makes it impossible to dump xbox games properly on pc drives (at least for now)
- It's not part of the actual game data, or the file system, so why preserve it?
- It also hurts the preservation aspect as far as the size goes: If there is 2gb of game data on the disc, there will be 5gb of random padding. This random padding can't really be compressed, so images are much larger than they can be, and this just for some random useless bytes!

I think in the end it all depends on the interpretation of the word 'preservation'. Valid points can be made for and against including this data. Personally, I don't see how the padding is any more relevant than:

- Ring data on saturn/dreamcast discs which Redump doesn't include in dumps
- Lead-in and lead-out and pregap and postgap data which Redump doesn't include in dumps
- Subchannels which Redump doesn't include in dumps

Redump seems to focus on dumping all relevant game data, so in this perspective, excluding the random padding wouldn't interfere with our goals.

Plz vote in the poll, and I hope the staff will use the results to determine the future direction for this system.


edit: POLL RESULT: 7 votes for keeping the current method, and 3 for removing the random padding

ArhiAngel wrote:

Dear moderators, wtf ??? Where my dumps OPS2M #27 and #30 SCED-52619 and SCED-52981 ?

Titles are wrong, or it's the wrong region.. plz check the filesystem label.. and/or make a scan of the discs... was hoping that ir0b0t already contacted you about it.

511

(32 replies, posted in General discussion)

Dunno, you can try hotswapping a gamecube/wii disc with the samsung and see how fast it goes  wink

512

(32 replies, posted in General discussion)

I'm sorry, but those tests won't help us much.. all these systems can be dumped with other software.. the only real obstacle are gamecube and wii discs, and speed won't be nearly as good then.

513

(32 replies, posted in General discussion)

Well.. now you said it.. it's a normal dvd-video.. so that's why it's so fast.. I even doubt if you need friidump for it.. it might also work with isobuster.

514

(32 replies, posted in General discussion)

What speeds did you get on the samsung? and did you swap?

I haven't tested swapping with samsung, so hoping to hear from you.

515

(3 replies, posted in General discussion)

Open garbage bin. Drop books. Close garbage bin.

smile

516

(8 replies, posted in General discussion)

Ok, but what's the problem then? can't you just recheck the discs or the images with the correct settings?

517

(8 replies, posted in General discussion)

Sorry, but you're saying that:

1. You don't have the discs or the images anymore
2. You checked the images and recorded the info in the past
3. But now you're not sure if you used the correct setting then?

If so, then any new dumps that aren't in the db can be prone to error..

518

(8 replies, posted in General discussion)

Our IRC chan is crowded enough (~35 people average) and works well enough imo.

519

(11 replies, posted in General discussion)

N64 emulator discussions are for emulation forums, not Redump. Topic closed.

http://cgi.ebay.de/Plextor-PX-755A-16x- … 2305b106c6

I you want the best, look for a PX-760A or PX-755A

521

(2 replies, posted in News)

From 6000 to 11000 in less than a year!

I think fuzzball is the top dumper (with 1000 dumps soon, wow!), followed by iR0b0t with almost 900 (he must dump more lol lol).

Congrats!

Yeah this is a known problem.. plextors try to correct errors automatically for some reason (or at least that's the effect), so if you have a disc like Actua Soccer with hundreds/thousands of these sectors you won't be able to match it. Like themabus said, dumping scrambled and then descrambling can be a solution, but otherwise you can just stick to another drive for these discs. This is also why verifying on 2 drives is always recommended.

523

(1 replies, posted in General discussion)

As suggested in the chan, the only tool that's available that can do this appears to be px_d8, but you can only read single sectors.

Maybe that German F1REB4LL fan used to work in a CD factory?  (forgot his name) lol

525

(32 replies, posted in General discussion)

Now that we have RAW DVD dumping capability, I will be doing some experiments.

I've already tried to compare the dvdtoimg output of a DVD movie with friidump in 2048 mode.. friidump aborts at the layer change.. and another difference is that the friidump output has an offset difference of -6 bytes.

@themabus, is there anything that could explain this offset difference? The dvdtoimg offset seems correct.