i think the 0.5.0 worked because of the file system virtualization of windows 7
savegames where written to the virtualstore, so vegastrike must have tried to write to the game directory, but the writes where redirected.
but the exe of 0.5.1 is a 64bit binary and afaik for 64bit binaries virtualization is disabled
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
correction: the exe is 32 bit
but it has a manifest file with a requestedexecutionlevel and windows interprets this as "application is UAC aware and needs no file system virtualization" - so writes to the vega strike installation directory will fail.
which version of win7 32bit, 64bit? Do you have SP1 installed?
yes and yes,
i think the 0.5.0 worked because of the file system virtualization of windows 7
savegames where written to the virtualstore, so vegastrike must have tried to write to the game directory, but the writes where redirected.
but the exe of 0.5.1 is a 64bit binary and afaik for 64bit binaries virtualization is disabled
correction: the exe is 32 bit
but it has a manifest file with a requestedexecutionlevel and windows interprets this as "application is UAC aware and needs no file system virtualization" - so writes to the vega strike installation directory will fail.
http://windowsteamblog.com/windows/b/developers/archive/2009/08/04/user-account-control-data-redirection.aspx
Will try to find that in VC9 and see what can be done about it.
As far as .5, it saved to its install directory but it was also compiled with VC 2003 or 2005 and did not use as many compile options as .5.1
New code fix committed.