I'm finally taking some time to play around with this. Has anyone here successfully signed a CD-ROM image built with the SDK's laytool? I suppose there must be something specific to the System files from the Homebrew pack that is required for signing to work, like it's expecting a certain checksum?
I ran 3DOEncrypt.exe on an ISO of the Bounce demo, built directly from the SDK. It ran without errors, but when I tried to load it in FreeDO, it didn't recognize it as a valid disc. I tried both with and without the genromtags flag. It does boot in FreeDO when using a hacked ROM to allow unsigned content, but it doesn't boot with a retail BIOS.
When I decompiled the (unsigned, SDK-built) ISO, copied in the System files from the Homebrew pack, and recompiled, the signing worked and FreeDO booted it with the retail BIOS.
In case it's relevant, 3DOEncrypt reported different sets of tags for the SDK-built image when running with and without genromtags:
Code: Select all
Signing original ISO (no genromtags):
=====================================
Finding the rom tag files...
Found launchme at sector 891
Found signatures at sector 8C5
Searching for rom tags...
Found boot_code tag:
Starting sector 2
Length 2000
Found os_code tag:
Starting sector 6
Length 1C340
Found misc_code tag:
Starting sector 46
Length B5C
Found bannerscreen tag:
Starting sector E3
Length 25858
Unknown tag 17:
Starting sector 0
Length 0
Found end tag
Found 6 tags
Signing original ISO (with genromtags):
=======================================
Finding the rom tag files...
Found launchme at sector 891
Found signatures at sector 8C5
Searching for rom tags...
Found boot_code tag:
Starting sector 2
Length 176C
Found os_code tag:
Starting sector 6
Length 1C340
Found release data tag:
Encoded date ACBFF792
Found launchme tag:
Starting sector 19FF
Length 78
Found misc_code tag:
Starting sector 46
Length B5C
Found bannerscreen tag:
Starting sector E3
Length 25858
Found signatures tag:
Starting sector 8C4
Length 0
Found end tag
Found 8 tags
In the cases where the tag lengths don't match, the MD5s it later calculates are also different (not surprisingly).
When I have a chance, I will try pulling the System folder from the Homebrew pack into my Mac environment and lay out the CD with that version to see if that changes anything. For what it's worth, I'm using the 2p5 cdrommaster folder and laytool.