DiscImageCreator

[matura713]

on Nintendo disc with DiscImageCreator I get:

fixed. https://www.mediafire.com/file/eq80y20l … st.7z/file
But Nintendo disc dumping is extremely slow. If you merely want to dump the iso, use RawDump or cleanrip on wii.

thank you! I confirmed - it works now and the ISO is the same hash as the one made with RawDump. BTW, it still shows:

LBA[000000, 0000000]: [F:ReadDiscStructure][L:1505]
        Opcode: 0xad
        ScsiStatus: 0x02 = CHECK_CONDITION
        SenseData Key-Asc-Ascq: 05-24-00 = ILLEGAL_REQUEST - INVALID FIELD IN CDB
Failed to read BCA. cdb: ad, 00, 00, 00, 00, 00, 00, 03, 00, c0, 00, 00

but I guess that's for information, not to indicate any actual error, because the dump made is no doubt proper.

[sarami]

they are InstallShield cabinet files instead of Microsoft ones

Can you extract them of the _setup directory manually using i6comp.exe?

[Neon Beast]

they are InstallShield cabinet files instead of Microsoft ones

Can you extract them of the _setup directory manually using i6comp.exe?

Maybe I am doing it wrong I can't extract the files.

[sarami]

Maybe I am doing it wrong I can't extract the files.

Also try i6cmp13b.zip
https://www.sac.sk/files.php?d=7&l=I

[Neon Beast]

Maybe I am doing it wrong I can't extract the files.

Also try i6cmp13b.zip
https://www.sac.sk/files.php?d=7&l=I

Can't extract either.

[superg]

sarami, is it normal to have a separate set of (Subs indexes) where everything is the same as in primary TOC based split?
Logs: https://www.dropbox.com/s/4clypf96lu0zq … OR.7z?dl=0
Asking because my verification has identical (Subs indexes) but doesn't match what we have in the DB: https://redump.info/disc/15537/
I compared both dumps and the new data track is 1 sector more padded with zeroes and audio track is 1 sector less comparing to the DB one.

[sarami]

Can't extract either.

Unfortunately, their cabs do not support it.

(Subs indexes)

Try to use "/s 2"

[Neon Beast]

Hi,
Yes, I remember that disc. It was not possible to get consistent dump. If you look at scm file you'll notice that some bytes at discguard locations are always different. It's some kind of 'weak data' protection.

Such dumps need manual fixing. But you need to know the data to fix with. In my case it was easy as these weak bytes happened in the middle of a sector (surrounded by zeroes).

Hi, how can I fix my DiscGuard discs? Thanks.

[matura713]

Hi, how can I fix my DiscGuard discs? Thanks.

my understanding based on what @reentrant is saying is that you need:

1. identify the "weak bytes", i.e. those bytes that are different on every dump due to the protection
2. try to "guess" what is the correct value of each "weak byte"- in case of @reentrant dump it was looking like 00000XX00000 and so it was easy to guess that XX=00

however, in your case it could be not that easy to guess the "weak byte" value.

[superg]

Try to use "/s 2"

/s 2 didn't help.
My primary concern is that in my new dump the split is 1 sector earlier comparing to what we have in the DB.
e.g. in the new dump the data track last sector is audio track but in the DB it's not and it seems more correct. I have to identify which dump is correct, old or new.