VBA-M gameshark codes won't save

[mitch103]

Hi, I recently downloaded the emu paradise visual boy advance emulator for macs. I found that I am unable to enter gameshark codes while the game is running (it is greyed out) so I entered a code then booted up pokemon fire red. obviously the code didn't work so after closing the rom I checked to see if i had entered the code correctly and it was no longer there. I repeated the process multiple times for gamesharkadvance and codebreakeradvance but the codes for some reason are not saving. Anyone know anything about this strange issue? Thanks!

[Zorlon]

Sounds like it's a disabled feature PC version you can enter codes while playing in-fact you can create your own codes while playing

Try using the normal version of VBA (I presume you wanted M for it's link up features) well you are playing Pokemon you only link up when trading so 90% of the time you are not linking anything

Download Links:
Links are hidden from guests. Please register to be able to view these links. VBA 1.7 official Mac Binary
Download Links:
Links are hidden from guests. Please register to be able to view these links. VBA 1.7.4 unofficial Mac Binary

[mitch103]

Thanks for the response, however when trying to run either of those I got the error "PowerPC applications are no longer supported." Crap!

[Zorlon]

You must be using an Intel Mac then I would of thought.

Download Links:
Links are hidden from guests. Please register to be able to view these links. This is another one to try I don't own a Mac so I don't knoow if it has the same features but what led me to that was a post saying that it is the same as VBA just named MacBoyAdvance instead of VirtualBoyAdvance, I presume it uses the source code for VBA though so should be the same

The above is an Intel Mac Binary though rather than a PowerPC binary

[mitch103]

Yes I have an intel mac. I tried that intel mac binary vba and am getting the infamous 'unable to write save state' problem that I've had in the past. Thats the reason I started using VBA-M (not interested in linking). I've searched for so long but nobody seems to know how to fix it. What's the point of playing if I can't save right?

[Zorlon]

I always say don't use save states because if you do any some setting is wrong and you run into issues you can't recover from them using a save state, use in-game saves instead

for setting up the saves though for Fire Red

Make Sure

Real Time Clock is enabled

Save Type = 0 (EEPROM)
Save Size = 131072 (Flash 128K)

That will let you save normally that can be done at any time in-game (out of battle anyway)

Save states I would avoid mostly

[mitch103]

Unfortunately there is no such option to adjust save type and save size in this mac version that I have

[Zorlon]

Just as well I gave you the incorrect type info anyway

vba-over.ini will auto fix it though http://www.emuparadise.me/links-and-downloads/?catid=5

or it should do, just make sure you remove the old save first or it will revert to using that or I can just send you a correct save file over (no game started yet)

[mitch103]

Yes the problem is there arent any .sav files because I haven't been able to successfully save the game. I put the .ini file in the same directory as the vba.exe and it did not fix anything

[Zorlon]

try the save method then :/

extract it to your save folder for vba or the folder that all your saves are stored in

make sure the name of the save is the same as the rom

or you can use the import battery file option if the mac version has that

All this fuss so you can cheat...

There might be a Pokemon save hack as well out there not looked in years for that sort of thing but there was for the original Red Blue and Yellow games for the Super GameBoy/GameBoy Color

[mitch103]

I appreciate your time in trying to help me fix this but I think it may just not be possible.

[Zorlon]

It is hard to help when I use a totally different OS the save thing should work though if it is loading the battery save file, you can try the import battery file option if you have that otherwise it needs to be correctly named and located to be seen by the emulator for that game