winSPWW2 v4.0 -- 3 CORRECTED OOBs - Page 4

Imp · #31 February 11th, 2010, 07:33 PM

This is just my view somehow people are mucking up bundling the checksum facility along with a text document of what the results should be for both v4 & v4 & the fix which will only have 3 diffrences will allow checking by that person if a problem arises.

Sgt_Walrus · #32 February 11th, 2010, 07:55 PM

Hi All

I really have no idea what you just said there Imp.
You need to use some full-stops (periods for you I guess) to help that make sense.

Anyway.
Andy...here is the file from my test with Imp. It showed an error 'P1 Obat.' This version was the v4.0 + OOB fix.

I am P2 and this is the file as I got it back from Imp.
This would be my T1.
My p/w is Fred.
USSR v USMC, normal battle set up.

Hope this helps.

Cheers
jason

Sgt_Walrus · #33 February 11th, 2010, 08:05 PM

Hi Andy

Here is another error.
This time it is Standard v4.0
I am P2, Fred Fjun set the battle up. We are ANZAC and Sweden, same as the previous test with Fred in v4.0+OOB fix.

Error showed up after I opened this file to play R2 T1.

So.
I have now done these tests, all having the exact same result.
Versus Fred.
We have done test in V4.0 and v4.0+OOB fix.
We have test with both of us setting up as P1.
ANZAC v Sweden

Versus Imp.
V4.0+Fix with him as P2 USSR v USMC

I really do not know what else I can do.
I know of at least three of four other pairs of players that have just had these error messages when playing my tourney game in V4.0+Fix.

So...as I said earlier, there is something going on for sure.
There is no way that suddenly multiple experienced PBEM SP players have all started making the exact same mistake (or having the same computer problems etc.)
The common factor with all this is the new v4.0 version.

I wish I could help more, but my time is loimited.

Please let me know if there is something more I can do.

Cheers
Jason

Mobhack · #34 February 11th, 2010, 10:11 PM

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 · #35 February 11th, 2010, 10:44 PM

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 · #36 February 11th, 2010, 11:29 PM

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

2ndLt_Fjun · #37 February 12th, 2010, 01:41 AM

Quote:

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.

Sgt_Walrus · #38 February 12th, 2010, 02:02 AM

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 · #39 February 12th, 2010, 04:33 AM

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 · #40 February 12th, 2010, 07:48 AM

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