I'd like to know where this emulator revision stores it's configuration data, also it hangs the instant i tell it to open a GBA or GBC ROM, it closes the file open dialog before it freezes/goes unresponsive.
Â
I'd try a fresh install if I knew where the configuration file is stored as changes made in revision 1025 don't seem to have any effect on the previous 1012 revisions configuration which is stored at C:\Users\%username%\AppData\Roaming\VBA-M
1025 would be a fresh configuration regardless as it now uses vbam.ini instead of vba.ini. changes were made to accomodate having 1.8 and earlier in the same directory as vba-m.
Â
are these roms within an archive?
No they are not.
But where is this vbam.ini? It isn't on my Windows partition.
if you are using the wxwidgets based interface then the vba-over.ini file is built into the interface so it can use it directly or if any updates exist then can be loaded manually via the ini file, however in the release I made like I said it's a built in resource.
Okay so I'd have to replace the EXE file with a fresh one to reset configuration then, right?
no, the wxwidgets interface uses a different configuration than the old mfc interface
Yeah so how do I reset it's configuration? Do I replace the revision 1025 builds exe with a fresh copy of the 1025 build since the configuration file is embedded in it? I want to reset it and see if a default configuration exhibits the problems.
zach was referring to vba-over, not the configuration (vbam.ini) file.
The settings for wxVBA-M are stored in the Windows Registry at HKCU/Software/wxvbam.
Â
Additionally, it appears that in 1025 you cannot set the bios files separately for GB and GBA. Changing one in the interface also changes the other.
DO NOT WANT.
Â
Zach, move the settings back to an ini file.
the whole point was portability.
