davyd Posted September 5, 2016 Posted September 5, 2016 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 unless I use "Unlocker" to kill the process, losing the ini again.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. I am uncertain why the Emul does want to make this copy, but isnt it strange also that HyperLaunch locks does not unlock the file when closed? Did anyone experience this problem before? HyperLaunch version is 3.0.0.9 running on WinXP. Thanks in advancedavyd
Recommended Posts
Archived
This topic is now archived and is closed to further replies.