Verification for Star Wars: Rebellion.
Logs: Star Wars: Rebellion.7z
Common disc info:
Title: Star Wars: Rebellion
System: IBM PC compatible
Medium: CD-ROM
Category: Games
Region: Germany
Language: German
Ring code:
Outer mastering code: Sono press ROM V-5078/STARREB598 A
Outer mastering SID: IFPI L022
Mould SID (data side): IFPI 0713
Barcode: 4 005209 023733
Error count: 1
Comment:
<b>Universal Hash (SHA-1)</b>: 05f506040608dab7afed19d1d559a264f51f05dd
<b>Volume Identifier (ISO9660)</b>: REBELLION
<b>Volume Identifier (Joliet)</b>: REBELLION
[T:VOL] REBELLION
Version and edition:
Edition: Original
Extras:
Primary Volume Descriptor (PVD):
0320 : 20 20 20 20 20 20 20 20 20 20 20 20 20 31 39 39 199
0330 : 38 30 36 30 33 31 35 33 33 35 33 36 36 BE 31 39 8060315335366.19
0340 : 39 38 30 36 30 33 31 35 34 31 35 39 33 32 68 00 98060315415932h.
0350 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0360 : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0370 : 00 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
Tracks and write offset:
ClrMamePro data:
<rom name="REBELLION.bin" size="803245632" crc="280cb710" md5="ee81e2712327f8771c4c7446ad04215b" sha1="44596d4d09443382ae92aa19fea9170109fb79bf" />
Cuesheet:
FILE "REBELLION.bin" BINARY
TRACK 01 MODE1/2352
INDEX 01 00:00:00
Write offset: -12
Matching information with DiscImageCreator 20250101T232049, and Redumper v2024.11.03 build_438.
Regarding the different checksums see this conversation on the Video Game Preservation Collective server:
usurper, Jackal: Do you remember why the checksums for Star Wars: Rebellion were changed? I just dumped two discs with redumper and DIC each and all hashes match the old values before the last edit.
Bitpool Protection, initially all Bad sectors have been 0x55 filled.
Then we have agreed to leave them as is
Check the Bad sectors of your dump, if they are not 0x55, then your dump is correct
My dump seems to be correct then. The sector contains 0x55 6 times, but the other 2042 bytes have other values. Thanks for the reply.
so the latest submission should be added to the verifications forum to be added to the database
it's worth pointing out in the comments what happened and why the hashes were changed, just in case