Try this:
If you can confirn that it will continue to work as long as I can see the saves and still load them in this "ers" folder. Then I am completely fine with this, and don't need it to work any "better".
If it won't then, then I will give your options a go. 🙂
@Mjmandk wrote:
If you can confirn that it will continue to work as long as I can see the saves and still load them in this "ers" folder. Then I am completely fine with this, and don't need it to work any "better".
It should continue to work.
But neither ME2 nor the ME2 config utility will "see" your saves if they are in your game folder and there is a chance that ME2 gets the same problem.
This is also most properly not a Zip file in your "Document/Bioware/Mass Effect/save" location.
Windows only somehow assigned the file extension of the Saves to the Zip program. The "player.sav", "state.sav", and "WorldSavePackage.sav" files are the normal content of a ME1 save file.
I suspect that this either a botchered "BIOEngine.ini" or a permissions issue on your system.
There shouldn't be any permission issues since I am the only user on this PC, with full administrative rights.
If it is a botched BIOEngine.ini, I would suppose reinstalling it would work, al though that clearly didn't fix anything, since I had already reinstalled it twice.
I guess I will just deal with this issue when it comes to ME:2, next time. 🙂
@Mjmandk schrieb:
There shouldn't be any permission issues since I am the only user on this PC, with full administrative rights.
Since Windows Vista no user Administrator account has full administrative rights.
All programs are executed in user mode without administrative rights, that's why you get prompted for administrative permissions from time to time.
It gets even more complicated if it comes to write permissions for protected spaces like "Program Files (x86)".
Mjmandk schrieb:
I guess I will just deal with this issue when it comes to ME:2, next time. 🙂
Hope it works without problems. 🙂
