Jump to content

Recommended Posts

Posted
I hate having to go back and read things, its much easier just to ask :P  <_<. anyway, anybody wanna hook me up with the -NO REQUESTS ALLOWED-, oh yeah btw, if anyone wants a gmail invite i have 5 to let go.

So much easier for you, so bothering for others...

  • Replies 478
  • Created
  • Last Reply

Top Posters In This Topic

Posted

Woah, that's weird. I'm not sure if anyone knew this or not, but MVS mode works for me, but the fatalities don't work without using Unibios's AES codes. Does this happen to anyone else?

Posted
Woah, that's weird. I'm not sure if anyone knew this or not, but MVS mode works for me, but the fatalities don't work without using Unibios's AES codes. Does this happen to anyone else?

Yes, we know about this. For quite some time too. ;)

Posted

it's around here somewhere, James posted it.

Posted
I hope you guys make another thread when the real/complete game comes out, I dont want to have to read through all this sheit.... thats all im waiting for at this point.

I am not sure if that will come true.

 

This is the official one for sure...

 

 

And by law of emulation..well, actually there is no law,

 

but anyhow, getting a perfect rom takes work, and it includes reading ;)

 

 

I personally think reading is one of the easiest tasks out there, compared to some others.

Posted (edited)

Can anyone give me the encrypted V r0m ?

 

 

 

Do Not Ask For Rom Links

Edited by James
Posted
Can anyone give me the encrypted V r0m ?

This is just a prelude post to some big nasty bold warning text you'd be expected to receive pretty soon.

Posted

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 < missing

272-v1d.bin 16777216 e3aa568e < missing

 

This is my encrypted V set (before running vconv)...

272-v1.bin 8388608 76a94127

272-v2.bin 8388608 4ba507f1

 

This is the decrpted V set (after running vconv)...

272-v1d.bin 4194304 32156cfe

272-v2d.bin 4194304 0e46d2f8

272-v3d.bin 4194304 9aa45090

272-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???)

Posted

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.

Posted
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.

Posted (edited)
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 by Agozer
Guest
This topic is now closed to further replies.

×
×
  • Create New...