2. A text configuration file known as vba-over.ini
3. A clean un-hacked/patched copy of a special case GBA ROMhttp://www.megaupload.com/?d=OTQ5XSHZ GBA Bioshttp://www.sendspace.com/file/uay5uq vba-over.iniEdit:
Added a vba-over.ini file with modified entries for the Classic NES Series games
Must have VBA 1.8.0 to make them work correctly.
http://www.megaupload.com/?d=UI858LEIFirst check if your BIOS file is named "gba.rom", in all small letters, without quotes, if not rename it. As soon as you rename it, the file type MAY change, this is normal so don't worry. You put the gba.rom file on your vba's root directory, that is, the folder where you have your vba in.
Run VisualBoyAdvance then go to options > emulator > select BIOS file.
A window should open asking you where the BIOS file is, it can't initially "see" your file so you must type its name, usually by typing the letter "g" it should see your file, now confirm your file. Go again to options > emulator, now check Use BIOS file, & presto!!!loony said there were problems getting the file on the link I've posted, but maybe you might get lucky. If you do get it, place that in your vba's root directory & you're done!! Just disable the real time clock setting in vba & let the vba-over.ini file determine which setting is best to make the emulation run smoothly :)NOTE:The vba-over.ini file solves a lot of game loading problems, not just for Pokemon games. It is a notepad configurations setting text document that you can actually open & view. In it are a list of configurations settings for vba to run specific games, which are listed on it*UPDATE* Saturday August 30, 2008, 10:04:16 PMOkay, so someone PMed me about this guide. Apparently I forgot one minor detail:If you're going to use this method to play games like Pokemon Emerald/Ruby/Sapphire, Dragonball Z Legacy of Goku & the other games this method fixes, make sure you DELETE any existing .sav files associated with said games. For example, like the guy's problem:He got VBA & wanted to play Pokemon Emerald, he loads the game then naturally encounters the "The Battery has run dry error". He searched the net (or RomUlation) for a fix, then he comes across this thread. He got the gba.rom BIOS file & vba-over.ini file & did the steps I mentioned. He reloads the game then... White Screen of death!I did forgot to mention, in this case you should delete the .sav file VBA created PRIOR to my solution, doing so fixes this problem."What .sav file? I haven't even gotten to play yet *&@#!?", you might ask in rage. Well, as soon as you load a game, VBA (& I guess every other emulator) will create a .sav file for the game (which contains data to the game's save battery functions) if said game needs it, so even if you haven't yet made a "physical" save, the emulator has made one by itself.*UPDATED Yet again :) * :Okay so I decided to update this thread again for several reasons:1. I noticed that several people do not check this thread out first when it comes to making some GBA ROMs run smoothly on VisualBoyAdvance, this is partly because of my bad title for it. Yes because I specified "Pokemon" people normally think that this thread only solved GBA Pokemon ROMs issues, but it doesn't.2. I just found out that there is an issue with VisualBoyAdvance version 1.8 beta 3 with regards to one game, this game being "Petz Vet". If you run Petz Vet on version 1.8 beta 3, you will notice that the in-game text dialogues of characters (the text that normally appear on the white text bar below the screen) will not appear. You will hear the text being written but won't see it. The solution is to run the game on VBA version 1.7.2. Other than this VBA 1.8 Beta 3 is your best choice as it runs everything else better than 1.7.2 .3. The solution that the vba-over.ini file gives to every version of Boktai 1 & 2 is half-useless. Yes it automatically configures VisualBoyAdvance to recognize the best settings for the Boktai games but it doesn't fix the solar sensor issues. If you run the Boktai games on VBA with the vba-over.ini file solution the game will still crash as it still doesn't detect an active solar sensor. There are two ways to remedy this, one is to download a solar sensor patch in these two links for both Boktai 1 & 2:http://bubbz.pocketheaven.com/?system=gba§ion=patch_info&patch_id=1045 <- This is for the US Boktai 1 game, sadly there's no patch for the European release.http://bubbz.pocketheaven.com/?system=gba§ion=patch_info&patch_id=1224 <- This is for the European Boktai 2 game, strange that this time the patch was for the European version, oh well.Once you get these patches, apply them onto your ROMs with a patching utility like LunarIPS which you can get here:http://www.romhacking.net/utils/240/Now if this solution is too complicated for you, you could try option two which is to run these two Boktai games on no$gba2.6a as this emulator has an onboard solar sensor emulator that you can even set depending on how bright or dark you want the sun too be :)Another great Update to this tutorial courtesy of TirithRR:So anyway, thanks to TirithRR we can now play Classic NES (or the Japanese equivalent FamiCom Mini) series games (in ROM format ofcourse) smoothly on VisualBoyAdvanced with an even better updated vba-over.ini file you can get at this link:http://www.megaupload.com/?d=UI858LEIThanks for the great tip TirithRR :)