Jump to content
Visual Boy Advance-M

Locked vbam.ini when launched thru HyperLaunch

Recommended Posts

Hi all,


when launching VBA-M (latest stable or git builds) thru HyperLaunch there is an error message shown (something to the extent of ...cannot copy config file to... *.tmp, etc.). When this happens and I close the applications down, vbam.ini is locked and cannot be opened by any other application anymore.


When I initially launch VBA-M directly this doesn't happen, so my assumption is that HyperLaunch is locking vbam.ini before VBA-M can make the copy.


What's the purpose of making that copy, and can it be disabled? Has anyone experienced HyperLaunch acting this way, and is there a way to solve from HL side?


I realize this may not be a VBA-M problem at all, but I'd really like this great emulator to work in that setup.


Thanks in advance


Share this post

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now