ugenn Posted September 16, 2004 Posted September 16, 2004 The CRCs of the encrypted roms decrypted by vconv.exe don't match what was posted earlier. This is what was posted earlier in the thread:samsh5sp:272-m1d.bin 524288 74f37225 < missing272-v1d.bin 16777216 e3aa568e < missing This is my encrypted V set (before running vconv)...272-v1.bin 8388608 76a94127272-v2.bin 8388608 4ba507f1 This is the decrpted V set (after running vconv)...272-v1d.bin 4194304 32156cfe272-v2d.bin 4194304 0e46d2f8272-v3d.bin 4194304 9aa45090272-v4d.bin 4194304 ad8fabb4 This is the above decrypted Vs merged into a single V...272-v1d.bin 16777216 3654e81f (doesn't match what was posted earlier, what gives???)
Agozer Posted September 16, 2004 Posted September 16, 2004 I didn't merge the V roms. Go me. ... Although I could merge them into two Vs, since that how it was in SSV. And I don't really care about CRCs, just needed to fiddle with the DAT a bit.
ugenn Posted September 16, 2004 Posted September 16, 2004 Agozer said: I didn't merge the V roms. Go me. ... Although I could merge them into two Vs, since that how it was in SSV. And I don't really care about CRCs, just needed to fiddle with the DAT a bit.When CRCs don't check out, there smells of some BS somewhere. Either the decrypted CRCs given earlier were bogus, or this vconv tool is BS.
Agozer Posted September 16, 2004 Posted September 16, 2004 (edited) ugenn said: Agozer said: I didn't merge the V roms. Go me. ... Although I could merge them into two Vs, since that how it was in SSV. And I don't really care about CRCs, just needed to fiddle with the DAT a bit.When CRCs don't check out, there smells of some BS somewhere. Either the decrypted CRCs given earlier were bogus, or this vconv tool is BS. I know. But for some reason I don't care about that at this point in time... I just want to test out the M1d. Edited September 16, 2004 by Agozer
Agozer Posted September 16, 2004 Posted September 16, 2004 ugenn said: What m1d might that be?The one that isn't out yet, of course.
James Posted September 16, 2004 Posted September 16, 2004 ugenn said: This is just a prelude post to some big nasty bold warning text you'd be expected to receive pretty soon.Granted
James Posted September 16, 2004 Posted September 16, 2004 (edited) Do Not Ask For or Post Rom Links !!!! Edited September 16, 2004 by James
Agozer Posted September 16, 2004 Posted September 16, 2004 Ahh... That text always makes me feel all fuzzy and warm inside.
random guy Posted September 16, 2004 Posted September 16, 2004 I used that vconv tool on my thingies, then just rezipped up the rom with the new v's and it worked fine. I didn't even have to change the dat files.
Gryph Posted September 16, 2004 Posted September 16, 2004 ugenn said: The CRCs of the encrypted roms decrypted by vconv.exe don't match what was posted earlier. This is what was posted earlier in the thread:samsh5sp:272-m1d.bin 524288 74f37225 < missing272-v1d.bin 16777216 e3aa568e < missing This is my encrypted V set (before running vconv)...272-v1.bin 8388608 76a94127272-v2.bin 8388608 4ba507f1 This is the decrpted V set (after running vconv)...272-v1d.bin 4194304 32156cfe272-v2d.bin 4194304 0e46d2f8272-v3d.bin 4194304 9aa45090272-v4d.bin 4194304 ad8fabb4 This is the above decrypted Vs merged into a single V...272-v1d.bin 16777216 3654e81f (doesn't match what was posted earlier, what gives???)I too seem to be getting a CRC problem. I mean, I'm sure I have the same encrypted Vs as everyone else but after running vconv, the V3D has a different CRC from K'dash. 272-v3d.bin,800000,400000,3F0F7554,0 but it's supposed to be 272-v3d.bin,800000,400000,9AA45090,0 Meh...
Recommended Posts