Page 302 of 354
Re: DiscImageCreator
Posted: Wed Sep 01, 2021 1:11 pm
by Jackal
Neon Beast wrote:Hi, I have this Chinese release of Heroes of Might and Magic III, I got two copies with identical ring codes, but hashes don't match, and I can't get a consistent dump. It has DiscGuard protection, don't know if this is causing the problem.
Dumped with the latest test build.
Logs:
https://mega.nz/folder/XzB3SYyL#0g-CNMwckW9kQgmEFv-iRQ
DiscGuard needs a special treatment. I think there were some sectors without EDC where the random errors needed to be cleaned manually. Maybe reentrant remembers.
https://redump.info/discs/quicksearch/dis … tion/only/
Re: DiscImageCreator
Posted: Thu Sep 02, 2021 11:47 am
by Neon Beast
sarami wrote:Neon Beast wrote:Dumped HoMM 3 again, still got different hashes.
How about the other 2 discs?
According to CD Media World
https://www.cdmediaworld.com/hardware/c … uard.shtml, DiscGuard has IOSLINK.VXD and IOSLINK.SYS but your HoMM 3 doesn't have them.
The installed game will have these two files, and other discs are still getting different hashes. As Jackal pointed out, it needs a special treatment, and other DiscGuard entries show different error patterns, so it just happened to have the same pattern on these three games.
Logs:
https://mega.nz/folder/Ozom3K5C#gkdXa-p9XR041mZzMf0Vxg
Re: DiscImageCreator
Posted: Thu Sep 02, 2021 2:29 pm
by sarami
rosewood wrote:Is there anything that be done about this problem or did I miss the solution?
The problem may be that there is not EDC in LBA 16. Perhaps it can read using 0xbe, not 0xa8. I don't fix it yet.
Neon Beast wrote:The installed game will have these two files
There are some cab and hdr files in the disc. If they are Microsoft cabinet files, you need to use /mscf to detect DiscGuard.
The protection of 7K2 was detected as DiscGuard.
Code: Select all
Detected a protected file [IOSLINK.VXD]. LBA 302 to 330
Jackal wrote:I think there were some sectors without EDC where the random errors needed to be cleaned manually.
According to the 3 logs of Neon Beast, LBA 299 to 1498 do not have EDC. These should be replaced to 0x55 like SafeDisc?
Re: DiscImageCreator
Posted: Thu Sep 02, 2021 3:52 pm
by matura713
on Nintendo disc with DiscImageCreator I get:
Failed to read BCA.
and that's it, but the same disc dumps successfully with RawDump 2.0, I am attaching the logs. Am I doing something wrong?
Re: DiscImageCreator
Posted: Fri Sep 03, 2021 10:01 am
by Neon Beast
sarami wrote:There are some cab and hdr files in the disc. If they are Microsoft cabinet files, you need to use /mscf to detect DiscGuard.
The protection of 7K2 was detected as DiscGuard.
Code: Select all
Detected a protected file [IOSLINK.VXD]. LBA 302 to 330
Dumped again with /mscf flag.
Logs:
https://mega.nz/folder/vvpm3aZJ#vcXQYWPCX_PzsLwPqNBU0Q
Re: DiscImageCreator
Posted: Fri Sep 03, 2021 12:21 pm
by Jackal
sarami wrote:rosewood wrote:Is there anything that be done about this problem or did I miss the solution?
The problem may be that there is not EDC in LBA 16. Perhaps it can read using 0xbe, not 0xa8. I don't fix it yet.
Neon Beast wrote:The installed game will have these two files
There are some cab and hdr files in the disc. If they are Microsoft cabinet files, you need to use /mscf to detect DiscGuard.
The protection of 7K2 was detected as DiscGuard.
Code: Select all
Detected a protected file [IOSLINK.VXD]. LBA 302 to 330
Jackal wrote:I think there were some sectors without EDC where the random errors needed to be cleaned manually.
According to the 3 logs of Neon Beast, LBA 299 to 1498 do not have EDC. These should be replaced to 0x55 like SafeDisc?
No, not replaced with 0x55 but they can be "cleaned" somehow. I think the sectors match surrounding sectors except for the random error bytes which need to be cleaned so that they match (besides header). Perhaps it can be accomplished by rereading sectors and keeping the bytes that are most consistent between reads.
Re: DiscImageCreator
Posted: Fri Sep 03, 2021 10:56 pm
by sarami
matura713 wrote: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.
Neon Beast wrote:Dumped again with /mscf flag.
There is not IOSLINK.VXD.
Jackal wrote:No, not replaced with 0x55 but they can be "cleaned" somehow. I think the sectors match surrounding sectors except for the random error bytes which need to be cleaned so that they match (besides header). Perhaps it can be accomplished by rereading sectors and keeping the bytes that are most consistent between reads.
Ok, but who guarantees the kept bytes is correct?
Re: DiscImageCreator
Posted: Sat Sep 04, 2021 2:55 am
by Jackal
sarami wrote:Jackal wrote:No, not replaced with 0x55 but they can be "cleaned" somehow. I think the sectors match surrounding sectors except for the random error bytes which need to be cleaned so that they match (besides header). Perhaps it can be accomplished by rereading sectors and keeping the bytes that are most consistent between reads.
Ok, but who guarantees the kept bytes is correct?
If the sectors after "cleaning" the random errors all have data that matches the data in the previous or next sector, it's pretty safe.
Re: DiscImageCreator
Posted: Sat Sep 04, 2021 5:48 am
by Neon Beast
sarami wrote:Neon Beast wrote:Dumped again with /mscf flag.
There is not IOSLINK.VXD.
I check the file again, they are InstallShield cabinet files instead of Microsoft ones, and the install folder does have IOSLINK.VXD.
Re: DiscImageCreator
Posted: Sat Sep 04, 2021 6:19 pm
by reentrant
Jackal wrote:Neon Beast wrote:Hi, I have this Chinese release of Heroes of Might and Magic III, I got two copies with identical ring codes, but hashes don't match, and I can't get a consistent dump. It has DiscGuard protection, don't know if this is causing the problem.
Dumped with the latest test build.
Logs:
https://mega.nz/folder/XzB3SYyL#0g-CNMwckW9kQgmEFv-iRQ
DiscGuard needs a special treatment. I think there were some sectors without EDC where the random errors needed to be cleaned manually. Maybe reentrant remembers.
https://redump.info/discs/quicksearch/dis … tion/only/
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).