That’s expected, as this was only a diagnostic build which you ran.
What are the modification times for
C:\Users\MyUser\AppData\Roaming\VASSAL\Preferences and
C:\Users\MyUser\AppData\Roaming\VASSAL\tmp6568354715655364413.zip?
That’s expected, as this was only a diagnostic build which you ran.
What are the modification times for
C:\Users\MyUser\AppData\Roaming\VASSAL\Preferences and
C:\Users\MyUser\AppData\Roaming\VASSAL\tmp6568354715655364413.zip?
After you’ve checked that and let us know the modification times, try
the following:
Start VASSAL.
Go to the Preferences in the Module Manager. (Do NOT open a module.)
Change something in the Preferences and hit Ok.
Close VASSAL.
Does that trigger an error? If not, does that cause the modification
time of the Preferences file to change?
That’s expected, as this was only a diagnostic build which you ran.
What are the modification times for
C:\Users\MyUser\AppData\Roaming\VASSAL\Preferences and
C:\Users\MyUser\AppData\Roaming\VASSAL\tmp6568354715655364413.zip?
After you’ve checked that and let us know the modification times, try
the following:
Start VASSAL.
Go to the Preferences in the Module Manager. (Do NOT open a module.)
Change something in the Preferences and hit Ok.
Close VASSAL.
Does that trigger an error? If not, does that cause the modification
time of the Preferences file to change?
Finally:
If, after this, you are still getting the same error message, try:
Close VASSAL.
Replace the Preferences file with the temporary ZIP file in the
error message.
Modification times are:
C:\Users\MyUser\AppData\Roaming\VASSAL\Preferences - 2013-07-17 21:04:31 (probably time when I closed VASSAL after test)
C:\Users\MyUser\AppData\Roaming\VASSAL\tmp6568354715655364413.zip - 2013-07-17 20:55:19
Start VASSAL. - DONE
Go to the Preferences in the Module Manager. (Do NOT open a module.) - DONE
Change something in the Preferences and hit Ok. - DONE (I changed JVM maximum heap from 512 to 1024)
Close VASSAL. - DONE
It didn’t trigger an error.
Modification time of the Preference file is 2013-07-17 23:23:50
I am trying your next instructions.
I will post in few minutes.
Replace the Preferences file with the temporary ZIP file in the
error message.
Restart VASSAL.
Load a module.
and I still get the same error message when I try open new module.
If I restart VASSAL I don’t have this module in Module Manager, but if I try to open this module, it runs without problems.
But if I restart VASSAL again I still don’t have module in Module Manager.
I’ve read ( https://forum.vassalengine.org/t/preferences-file-problems/6142/1 ) that you are going to change Preference file.
I suppose that it will be in next release of VASSAL. Am I right?
What is the better way in my case - downgrade to stable version (for me 3.2.6) or should I use 3.2.7 with this small (?) error?
How many problems could this error cause?
I’ve read ( viewtopic.php?f=5&t=6478[1] ) that you are going to change
Preference file.
I suppose that it will be in next release of VASSAL. Am I right?
Yes.
What is the better way in my case - downgrade to stable version (for me
3.2.6) or should I use 3.2.7 with this small (?) error?
How many problems could this error cause?
The only problem this will cause you is that preferences you change
won’t stick between runs.
This build contains some changes w/r/t how preferences are stored which might solve your problem. If you try this build, please report here if whether it solved the problem for you.