Support with Super Nintendo emulation

[Apollo08]

I don't know what this means and or how to fix it?

 

[Tonberry]

Have you patched it manually? You might've used the wrong Rom if that's the case.

 

[Apollo08]

No, it was already patched. Should I patch it manually? The game seems to run fine despite this but I don't know if it will mess something up later on.

 

[Tonberry]

As long as the game runs fine you should be good, then.

Bad checksum usually means that you've used a rom file that doesn't correspond with the patch (there's always just like one rom out there with the proper name that works) but for some games it just seems like snes9x reads it in a weird way.

 

[Strategist]

Sometimes the rom patches don't set the checksum flags properly for the size of the ROM and the emulator detects a mismatch (i think). Like these errors happen when a patch increases the size of the ROM and the emulator gets an unexpectedly large file. These are security measures to prevent from code injections and things like that. But if you already know the file has been altered by a patch it is not a big deal.

If I'm wrong about this, someone correct me, but I believe this is correct.

 

[Tonberry]

Like these errors happen when a patch increases the size of the ROM and the emulator gets an unexpectedly large file.

Yeah, I think you're right. I forgot about this part, too.

 

[RageBurner]

Its probably a header issue. SMT1 is finicky and the patch expects a specific ROM revision. If you are applying QoL and. bugfix patches on top (you should, vanilla patch is bad), then it will take some more work.

 

[Clippy]

So long as the game works you should be fine. You may want to use save states in addition to normal game saves just in case but other than that you should be fine.

 

[Apollo08]

Its probably a header issue. SMT1 is finicky and the patch expects a specific ROM revision. If you are applying QoL and. bugfix patches on top (you should, vanilla patch is bad), then it will take some more work.

what do they add? The QoL and bugfix patches I mean.

Post automatically merged: Friday at 2:36 AM

So long as the game works you should be fine. You may want to use save states in addition to normal game saves just in case but other than that you should be fine.

I see, thank you!!!

 

[MasterEn]

what do they add? The QoL and bugfix patches I mean.

increased speed for text, stuff from newer versions added in. ff1 and 2 don't have an auto lock on for attacks. if a character targets an enemy and it dies before the action occurs; the character will attack empty air. run buttons. ff4 snes doesn't have a run button in the american version. japanese version does. rpgs may have the level and money grinding adjusted to take less overall time to do. things like that.

 

[RageBurner]

what do they add? The QoL and bugfix patches I mean.

The vanilla patch has several bugs. You can't buy guns early, for one, and one of the ending paths is impossible to complete. There is a patch that fixes this, there is a QoL patch that allows you to invoke the automap using a single button (as in SMT2) and there are several smaller cosmetic patches that improve status screens and the like.

If you want to have a good time, I strongly suggest you don't play the game without these added in. I can help you if you require it.

 

[AnonymousCookieMonster]

I remember occasionally seeing bad checksum warnings... That was on roms though. If the game runs properly don't worry about it. If it doesn't boot up, then i question it.

 

[Spike]

No, it was already patched. Should I patch it manually? The game seems to run fine despite this but I don't know if it will mess something up later on.

If it runs fine you can ignore it,
All it says is that the game CRC is different than expected.
And it makes sense because the game has patches applied.
The CRC changed, nothing to do just an information.