I have tried a different approach this time:
Just use
EZ-Flash IV AIO and drag and drop the desired game to the sleephack box. That is, after you have overwrited the included patch.bin with the abstartselect one.
Worked like a charm and it's REALLY easy.
That's good to hear. Does make me wonder what exactly went wrong on the first attempt, but so long as it works.
On a somewhat related note, as I stated I'm too lazy to repatch everything through the ez4 client (mostly because of tracking down the original rom with whatever manual/translation/feature-improvement patches were applied), so I wrote a simple script that should (hopefully) allow repatching an already soft-reset patched rom with a new reset key.
Anyways, here it is
patch_ez4_reset_key.py. You'll need
Python 2.x to get it to work (most Mac OS X and Linux users should already have it). Like most my tools, it's command line and pretty straight forward (just invoke it without args for a small blurb on usage). A simple script should make it pretty easy to patch a lot of roms. Like:
Code:
for f in */*.gba; do echo "$f"; ~/patch_ez4_reset_key.py "$f" L+Start+Select; done > ~/patched_ez4.log
If you've got your roms in subfolders, have patch_ez4_reset_key.py in your home folder, what L+Start+Select as your new reset key, and want a patched_ez4.log in your home folder so you can later review what all was patched.
Anyways, I've done only minimal testing on this, so it'd be a good idea to backup everything before using it. Really, that's a good idea period as the EZ4 still might be unreliable in file save creation/modification*. But, I hope this is useful to others.
* It actually was pretty reliable so long as you made sure you didn't power off when it was writing to the sd card and made sure to have a properly named .sav file in the saver folder. The latter part is easy to mess up, though, when you're fiddling around with single-rom emulation roms with pocketnes/goomba/etc.