Try patching it with this, if it doesn't work then you might have a corrupt file.

http://gbatemp.net/index.php?showtopic=72631

 

-immensely loud and deep gulp-
i hope ur pulling my chain, but you're probably right. Good side is that i've already beaten ML:SS a few years ago on my comp. But besides the fact that i missed some things, i want a more 'authentic' gameplay. The temptations of emulators to constantly load save slots for perfect scores, is not only overwhelming but gets old and annoying, while also ruining the game.

By the way, is there a faster way to check if the patching works? I mean like, instead of being surprised 5days later, is there a way to quick check or speed up the process?

 

Phew, that's good to hear. It seems to be solid after one day (not surprising). I'll repost in about a week, sooner, if it doesnt work. *fingers crossed*

EDIT: Oh! Almost forgot: Let's say the ROM has been patched, if i use a sav file from an unpatched ROM, will the patched effects be dismissed? Or do i need to just re-save it with the patched ROM, and it'll all be gravy?

 

Lol, sorry for the late responses.
And um, you confused me just a TAD bit. But to be more clear: The sav file was created on my comp, from the unpatched ROM; but i'm playing the patched rom on my Elink. I would've just loaded a state from the unpatched onto the patched and then create the sav file from the patched version, but i tried that and for some reason elink won't take certain sms sav files. i dont fully understand that, but as far as i know, it's only taking the sav files from the unpatched version. Now like i said, i'm not fully sure about that last part, but i mentioned it just in case.

 

Yes, Elink does come with a patcher, but i made sure to try that out way before i started asking for assistance. And it's not that the Patched rom can't read the unpatched file (i can't fully explain it well), Elink does won't write/burn/add certain sms sav files, so far the only ones i'm aware of are the ones from patched games. everything's holding up good so far, so i dont think it's a big deal. And if it does fail, oh well, you can't have it all.

 

No probs, glad it helped. I've just released a newer version if you want it, it's fixed a bug in a save type and has much faster detection routines.

 

The bug wasn't to do with patching values, I was trying to move 20 bytes into a 2 byte array. D'oh.

I've just checked my source code and the values in my post are correct, it should definitely be $48, $48, $e0.

edit : I've just checked the post against my source and there was a couple of changes needed doing. Here's the ones I just changed, all I did was shorten the arrays.

Fixes (03/12/08)
Changed unpatched/patched block 1 for Flash1M_V102
Changed unpatch/patched blocks 2 and 3 for Flash_v125

edit2 : Actually you could be right, I think I might have come across the same problem cos in my compare strings I'm only using the first 20 bytes. I'll do a tidy up of my source and do an edit in the original thread.