Page 1 of 1
VBA-M works in Windows 7
Posted: Sat Aug 15, 2009 4:51 pm
by spacy51
I did not expect otherwise anyhow ;)
SVN886:
Settings are now stored in "C:\Users\xxx\AppData\Roaming\VBA-M" for Vista. XP has a simliar structure.
File associations now work on a per-user basis with Vista and UAC enabled.
EDIT:
I just uploaded SVN888 to SourceForge.
I'd like to know if my current build environment breaks anything:
VBA-M works in Windows 7
Posted: Sat Aug 15, 2009 10:37 pm
by ZachBacon
can't say I like this change "Settings are now stored in "C:\Users\xxx\AppData\Roaming\VBA-M" for Vista. XP has a simliar structure." I believe in a truely portable vba-m now I know it will still work with the settings in the actual application folder itself but I work on VisualBoyAdvance-MPortable and well sad to say sometimes the launcher doesn't shutdown properly and settings get stuck in a place that isn't supposed to be in like C:\Users\xxx\AppData\Roaming\VBA-M, my suggestion is introduce something like a commandline -portable "path to settings file (IE) C:/vba-m or C:/Data/VBA-M" this would work better in the long run and will allow you to keep your idea but allow for a better setup for my project over at PortableApps.com
VBA-M works in Windows 7
Posted: Sun Aug 16, 2009 4:17 pm
by Squall Leonhart
Don't dynamically link libpng, for some reason doing so has the screen capture function crash the emulator
VBA-M works in Windows 7
Posted: Tue Aug 18, 2009 4:36 pm
by spacy51
SVN893: command line changes:
either:
vba.exe YOURROMHERE
or:
vba.exe --configpath YOURCONFIGPATHHERE
or:
vba.exe --configpath YOURCONFIGPATHHERE YOURROMHERE
YOURCONFIGPATHHERE must not end with a \ character
Don't try to change positions, as I was not in the mood to write a full-fledged command line parser. And I hate string handling.
VBA-M works in Windows 7
Posted: Sun Aug 22, 2010 12:42 pm
by SCHUMI4EVER
I know this thread is way out of date but if a user is stupid enough to put the emu into a protected folder like Documents or Program Files the change below (which is in all future VBA-M versions) causes problems cuz it remembers the original (protected) location when trying to create saves even once the emu has been moved to a neutral location in an attempt to get saving to work. It's best just to keep it in the folder same as before.
Settings are now stored in "C:\Users\xxx\AppData\Roaming\VBA-M" for Vista