winSPWW2 v4.0 -- 3 CORRECTED OOBs

[Mobhack]

Do you see the problem if you play yourself "right hand vs left hand" on the same computer?

(I will have to try transferring the file between 2 different installs on the same computer tomorrow)

If not then it must be something to do with the transmission.

Andy

[Sgt_Walrus]

Hi Andy

Just did a left hand - right hand as you suggested.
I had zero errors.
I tried both my stock v4.0 and the OOB fix.

I will try between 2 different install next.

In the meantime, I created a PBEM to send to you to try.

Save slot 010

Stock v4.0
scen 000

Email it back if that's easier.
jason@sgtwalrus.com

Cheers
jason

[Sgt_Walrus]

Hi Andy
More data.

I am just starting a test with Imp using the v4.0+OOB Fix but trying it with full Security.
More info to follow.

Just out of interest.
I tried a left hand - right hand test between two installs.
They were not identical installs though.
One is stock v4.0, the other id v4.0 (cloned from the first) but has the OOB fix.

Now, it threw up a 'Player 2 obat error' that was quite differently worded than the common error we have been getting previously. also it shows a P2 error, not P1 like all the other error messages.
It also appeared as soon as i tried to enter a pw for P2.
This is much earlier than the error we have been hunting which only seems to appear as P1 plays T1 IIRC.

So...it seems that the slightly different OOB between these two versions (just the three changed obat files, everything else is stock.) gets an error message very quickly...as soon as P2 opens the game. This is quite different from the error we are hunting.
The error we are trying to sort out does not appear until the files have been passed back and forward a couple of time.
It allows p/w set up and buy and deploy but then appears when the game proper has started.

Most strange.

Cheers
jason

[Sgt_Walrus]

Hi Andy.

Ok..interesting data.

Imp and I just tested v4.0+OOB fix but using Full security.
No error. I am P2 and just played T1.
USSR v USMC

I upload the file as I got it to play that turn. pw=axel.
By now the other tests had error messages.

Possible Basic Security issue?

We just created the exact same situation where we got an error...and changing just the security setting, we got no error.

Anyway...hope that helps.

Cheers
Jason

[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.

[Mobhack]

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

[2ndLt_Fjun]

Originally Posted by Mobhack

(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

Hi Andy. Just so I get this right - what you are saying is that these bugs are already known and there is an unreleased .exe file where the problems have been solved already. So this is a really a non-issue and we only have to wait for the next release/fix to come out?

A follow up question - is this bug causing any harm/problems in the actual gameplay, apart from showing the error message?

[Sgt_Walrus]

Hi Andy

All my errors in recent PBEMs, and all my tests...excluding the very last one with Imp...have been using Basic Security.

I am sure that we mention this earlier in this thread. Appologies if we didn't.

If there is a fix coming for this, excellent.
I will post at The Blitz to just ignore the error messages when using Basic Security and that there is a fix on the way.

Cheers
Jason

[2ndLt_Fjun]

Originally Posted by Mobhack

Do you see the problem if you play yourself "right hand vs left hand" on the same computer?

(I will have to try transferring the file between 2 different installs on the same computer tomorrow)

If not then it must be something to do with the transmission.

Andy

Now this is pretty interesting. I tried this one:

1. Starting the game. Anzac vs. Sweden in -44. Basic security. 4.0 without OB fixes to rule out the possibility that I'm installing the 3 new ob's in an odd way and screwing up all other ob's in the progress. I kept the game running and went back and forth two turns without any issues, while keeping SPWW2 running and just clicking in the game to switch between players. Seemed to work.

2. Now I exited the program, zipped the files (WinZip like I always did and which always worked previously) unzipped in the same directory thus overwriting the save files. Starting the same again, and tried to enter as Anzac and got the error.

3. I played on one turn opened the game as Sweden, without turning off the program, and the error disappeared. Exited the program.

4. Zippped again, unzipped and overwrote the save files, started the game, and the error occured again.

And no, I didn't go in and edit my OB's meanwhile. All these maneuvers were done using the exact same installation.