RE: Windows update destroyed my logfile!
To clarify: I am 99% sure that the crash/freeze was NOT caused by VASSAL itself. But VASSAL is very vulnerable to loss of data from random crash/freezes due to the issue with its architecture that I mentioned above. I mean, if I have to quit/save VASSAL after every PG activation to work around random (and unrelated) system crashes or inadvertent reboots for upgrades (which I now know to handle, time for a quit/save) then I will, but letting us save the logfile without quitting would be a nice fix in the future.
I am using VASSAL 3.2.17. Is there a later version?
|