Quote:
Originally Posted by Imp
To Clarify.
Test game against opponent with only diffrence being security basic fails after deployment phase.
Full security as only change seems fine.
Playing against self on same install again full works fine.
Basic works fine so long as you keep the game open.
If you shut the game between loads it fails
"BASIC SECURITY WARNING! - Changes have been detected in Player 1's Obat file"
Hope that helps does seem its Basic security thats messing about.
|
basic security is already subject of a spurious OOB error in the recently released EXE. The
published work around till we release a new EXE is to ignore OOB errors in
basic mode for now. The new EXE already fixes the
BASIC mode OOB checksum error.
What I hae been trying to sort out is the assertion that
secure mode is showing an unexplained OOB error.
Now - please tell me if you guys have been using SECURE mode PBEM and seeing the problem?. Because all my testing has been in SECURE mode since that was the reported error (as I read the posts)...
(The current 4.05 EXE certainly has no problems in either SECURE or BASIC security as determined by my testing & debug tracing. But it has the routine for storing basic mode OOB checksums called in the correct places)
Andy