(GBA) Chu-Chu Rocket saving problem

For some odd reason, Chu-Chu Rocket roms for the GBA never seem to properly save to the .sav files, regardless of what version of the game I use. I even tried using one of the double-packs that has it; same problem. I've got no problem using savestates, but I'd been hoping to show it to someone distinctly un-emulator savvy and it's a general pain.
I'm using vboyadvance, and I've got the save type set to Automatic and Flash 128K. The fast that it's giving me this headache even on the double-pack confuses the heck out of me.
Any suggestions?

 

Change the save type around until you can properly save and load. If that doesn't work, maybe this will. https://www.romulation.org/forum/index.php/topic,6326.0.html

 

Ok set your VBA Save type settings according to the specs shown on this link:
http://releases.pocketheaven.com/?system=gba&section=release&rel=0036

 

well, according to the one link, Chu-Chu Rocket's only got a 64K flash save system, so that might solve it.

If I change that, though, won't that screw up all my other games' save files? I know Pokemon at the least would throw a fit over this...

 

I'm a bit puzzled here, doesn't it work if you set the save settings to Automatic 64k? By the way, what OS is this version of vba are you using, there are a lot of people who actually had save issues on vba for linux, us windows users can easily resolve this

 

Win98SE.

Only thing I was worried about was whether or not setting the flash size to 64K would screw up all the saves that use the 128K option, like Red Rescue Team. I had that "1M sub-circuit not installed" problem with Fire Red until I set the emulator to 128K, and reading other posts here said that that was what solved my problem there. I didn't want to solve one problem only to open up fifteen much bigger problems.

I just made a clone of the emulator to test this out, and setting the flash size to 64K fixes up the problem nicely. I can use that for my less-than-emulator-savvy friend, but now it's my other saves for my normal copy of vboyadvance I have to worry about.

 

Well see that post of anandjones? that link he posted solves the Pokemon problem (& others like it) just read the instructions there, download the two files recommended & your problems will be solved

 

Problem solved using the vba-over.ini technique, though I don't know if any other saves were lost in the meantime. How many games even used the 64K flash option? Setting it to 128K only seemed to afflict the one game, but I have a near-perfect Advance Wars 2 save I'd like to keep intact, and I really don't want to have to start Harvest Moon over again.

I also had to ditch the old .sav file (not that anything was in it) before it would work straight. Too bad I couldn't keep my savestates either...

Two questions in regards to the technique, since I didn't see them in the sticky thread and can't remember if it's locked or not.
1. Will using "Skip BIOS" afflict this solution in any way?

and 2. Will this technique also work with that version of Vboyadvance that was specially modified to allow for multiple instances on one computer for link purposes? I know it creates multiple standard .ini files under normal use, but since it's an unofficial version I'm not sure vba-over.ini even works on it.

 

Skipping the BIOS shouldn't affect it in any way. If you're using VBALink etc. it should work like normal, as they are based on the same source code as the original emulator.