winSPWW2 v4.0 -- 3 CORRECTED OOBs

[Sgt_Walrus]

Hi Andy

I cannot speak for the other guys.

- Are both of you using the same operating system, or is one using say 64 bit windows 7?

I use XP SP2 as my OS.
Have done for all previous versions of Panthers since you went to windows versions.

other than someone having had a slip-up with the OOB at some point.

No chance, I never touch the OOBs...always played stock. It's the best plan for PBEM.

- Are you both using the same file compression utility to pass the files (WinRAR or WinZip or whatever).

I use winzip to send. Always have. Never any trouble with the tens of different PBEM players over the last 9 years.
I sometimes get .rar in the mail...they don't make any difference at my end. Never had any issues.
These file were all made via winzip as far as I can see.

- And just as a final thought - no player is trying to "share" a PBEM slot for several ongoing secure mode games?. That is a recipe for disaster.

Not at my end. I have multiple installs of the CD version, so no need for that. Not aware of Fred doing that for these tests.

So...I will continue to pass data, at least for one more test with a different player.
It is most perplexing as it is a rash of error messages since v4.0. Impossible for everyone to suddenly be screwing around with their normally solid set-ups and ways of doing PBEM.
As I am a moderator at Blitz SP, I am always watching the boards, and I have never noted as many reports of this sort of thing before.

BTW...all my (3) MBT v 4.5 games are behaving rock solid while all this has been going on...so if it were some computer based issue (compression utilities, OS etc.) surely I would be seeing issues there too.

OK...cheers
jason

[2ndLt_Fjun]

Well, I haven't messed with the OOB's other than installing the patch. I had OOB issues with the 4.0 version, w/o the extra OOB patch. Since the previous game was Sweden vs. Anzac it shouldn't be affected anyway by the OOB patch if I understand things right?

I've managed to install the previous patches successfully and played a significant number of PBEM's without ever seeing OB errors. I'm not playing multiple games and the 000 slot was only used for the test game. I'm never playing 'full security' games and stick with 'basic security' since it seems more stable. I've installed 4.0 on two of my SPWW2 installations (yes, these were upgraded to the latest patch before 4.0 before installing) and both of these show the error message.

I run Win XP, latest upgrade, WinZip for sending the files (which always worked thus far).

[Imp]

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]

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]

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]

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

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