I did try installing the Patch on my XP laptop, and I am able to get the initial splash screen to load before a Matrix error (error 200) pops up. [I'm pretty sure that error is because there is no TOAW 3.2 present on the laptop - but I do get the TOAW startup screen, and only when I click play do I see error 200.] I tried the laptop install as part of my own debugging.
Pardon me for asking a really stupid question, but we have to consider everything. Did you install TOAW III first, before installing the 3.4 update?
In fact, could we get the details of the installation procedure you chose? In other words, did you do a complete uninstall with everything deleted before reinstalling TOAW III followed by the 3.4 update? Or did you just add the 3.4 update to an existing 3.2 installation? Or something else?
For perhaps the only time in my existence on this forum, I get to tell you -- that is not a stupid question.
I am not concerned about the laptop -- and since I did NOT install TOAW 3.2 earlier, that undoubtedly is the cause of the laptop error.
And as far as the resizing error on the desktop XP, it was just Lutzow's comment that made me post since I barely have time presently to check the forum (what is it about getting a house ready to paint that consumes almost all time, in all units of measure, in the perceived universe ?)let alone do a decent job of beta.
I thought similar errors on a fairly brand new system (Lutzow) and on an old StoneAge like mine might be instructive to Ralph. If the production release has the fix, that will great.
Well, I stumbled onto the solution to my problem. And it's embarassing to specify it, but since there may be someone else in the same ditch, here's what happened :
0. Fuhgeddabout the laptop -- using that as a test machine does not matter.
1. Around Aug. 21 2010 I wanted to preserve my TOAW 3.2 settings, so I planned to install the beta in a way that if I didnt like it, I could easily revert to 3.2. So I built a new folder under the Matrix Games folder, and labeled it TOAW 34 Beta.
I installed the patch to this folder.
2. I did not change this basic approach with all my wiping, power downs, and re-installs.
3. After a week of struggling with real life (and about 3 or 4 different re-installs), I was skimming forums about the beta install, and some comment somewhere got me thinking - "How can the damn patch run separated from its 'ancestor' ?"
I didn't know.
4. Re-backed up everything; cleared out all Beta files (used Search to track the lil sobs down); copied over the TOAW 32 folder, pasted the copy in under the Matrix directory with a new name; powered down. Started up, tested my new shortcut to the newly renamed 3.2 -- worked just fine.
5. Installed the beta patch over the original TOAW 3.2 folder; got a succesful install message - again. Re-started. Went to the TOAW folder, saw that opart3.exe now had an August 2010 date and clicked on it to load.
6. I forgot to work thru the toaw config file so I suffered through the intro -- well, I deserved that.
Summary
I'm a week or more later than everyone but the beta version runs fine for me once I saved my older version under a new name, and then updated the ancestral folder of TOAW with the patch.
Big thank yous to all who posted/replied with suggestions and reminders on my problems. And thank you to everyone who posted their own problems, and the folks who replied to them - that's what got me thinking about what I might have done wrong.
As always, HUGE thank you to Ralph for his ridiculously fast responses.
Well, I stumbled onto the solution to my problem. And it's embarassing to specify it, but since there may be someone else in the same ditch, here's what happened :
0. Fuhgeddabout the laptop -- using that as a test machine does not matter.
1. Around Aug. 21 2010 I wanted to preserve my TOAW 3.2 settings, so I planned to install the beta in a way that if I didnt like it, I could easily revert to 3.2. So I built a new folder under the Matrix Games folder, and labeled it TOAW 34 Beta.
I installed the patch to this folder.
2. I did not change this basic approach with all my wiping, power downs, and re-installs.
3. After a week of struggling with real life (and about 3 or 4 different re-installs), I was skimming forums about the beta install, and some comment somewhere got me thinking - "How can the damn patch run separated from its 'ancestor' ?"
I didn't know.
4. Re-backed up everything; cleared out all Beta files (used Search to track the lil sobs down); copied over the TOAW 32 folder, pasted the copy in under the Matrix directory with a new name; powered down. Started up, tested my new shortcut to the newly renamed 3.2 -- worked just fine.
5. Installed the beta patch over the original TOAW 3.2 folder; got a succesful install message - again. Re-started. Went to the TOAW folder, saw that opart3.exe now had an August 2010 date and clicked on it to load.
6. I forgot to work thru the toaw config file so I suffered through the intro -- well, I deserved that.
Summary
I'm a week or more later than everyone but the beta version runs fine for me once I saved my older version under a new name, and then updated the ancestral folder of TOAW with the patch.
Big thank yous to all who posted/replied with suggestions and reminders on my problems. And thank you to everyone who posted their own problems, and the folks who replied to them - that's what got me thinking about what I might have done wrong.
As always, HUGE thank you to Ralph for his ridiculously fast responses.
Ok, so, short version - you installed the 3.4 patch as a stand-alone install, without first installing the original TOAW III. That's what I feared when I posted. That probably accounts for Lutzow's issue as well.
I consider this to be a flaw in the update. It should check for the existance of a TOAW III installation before allowing users to procede with the update installation.
Ok, so, short version - you installed the 3.4 patch as a stand-alone install, without first installing the original TOAW III. That's what I feared when I posted. That probably accounts for Lutzow's issue as well.
I consider this to be a flaw in the update. It should check for the existance of a TOAW III installation before allowing users to procede with the update installation.
So what you are saying is the update installs to the default location without giving the end users the opportunity to verify that the game is indeed in the default location?
Ok, so, short version - you installed the 3.4 patch as a stand-alone install, without first installing the original TOAW III. That's what I feared when I posted. That probably accounts for Lutzow's issue as well.
I consider this to be a flaw in the update. It should check for the existance of a TOAW III installation before allowing users to procede with the update installation.
So what you are saying is the update installs to the default location without giving the end users the opportunity to verify that the game is indeed in the default location?
It installs wherever the user tells it to install. But it doesn't check to make sure that there is a TOAW III installation there. We're trying to see if we can correct that.
Let's be clear: The 3.4 update is not a stand-alone program. You must first install TOAW III (any version), then "update" it with 3.4.
TOAW 3.4 is an update. It must be installed to (or over) the existing directory/folders where the user already has TOAW 3.2.
As an add-on, maybe remind them that they can copy the old TOAW 3.2 folder, save it under a new name, update any shortcuts if they want to preserve the older version somehow.
FWIW, if I saw your note that the user must already have TOAW 3.2, I'd have replied, "Got that. And I'm installing TOAW 3.4 right beside it."
Thanks for your assistance earlier.
And Panama, thanks for your jumping in with the examples of the logs -- it helped me find what was missing with my attempts.
FWIW, if I saw your note that the user must already have TOAW 3.2, I'd have replied, "Got that. And I'm installing TOAW 3.4 right beside it."
[:D] Good one that.
Squad Leader: "Fire at will."
Private: "Which one is he?"
That's why they don't have me writing the manuals, I guess.
Ralph Trickey
TOAW IV Programmer
Blog: http://operationalwarfare.com
---
My comments are my own, and do not represent the views of any other person or entity. Nothing that I say should be construed in any way as a promise of anything.
FWIW, if I saw your note that the user must already have TOAW 3.2, I'd have replied, "Got that. And I'm installing TOAW 3.4 right beside it."
[:D] Good one that.
Squad Leader: "Fire at will."
Private: "Which one is he?"
Make sure that if you download the Alpha 178 patch from operationalwarfare.com that you copy it onto an existing 3.4 installations (with the origianl game applied there first.)
Ralph Trickey
TOAW IV Programmer
Blog: http://operationalwarfare.com
---
My comments are my own, and do not represent the views of any other person or entity. Nothing that I say should be construed in any way as a promise of anything.
Could I possibly ask for some counselling regarding my issue? I think it's the same one, but can't be sure though so far. I posted the test report as an attachment in the "Public Beta Feedback" as the "Beta doesn't work for me ... " thread.[/align] [/align]Please advise.[/align]
"-What if one doesn't make it?
-Then we know he was no good for SpetsNaz. ..."
V. Suvorov, "Spetsnaz;the Story behind the Soviet SAS"
...No escape from Passchendaele .../ God Dethroned, "Passiondale"
FWIW, if I saw your note that the user must already have TOAW 3.2, I'd have replied, "Got that. And I'm installing TOAW 3.4 right beside it."
But then, if you'll check, you'll see that that's not what I said. It's fine to add further clarification, but I don't think there's a solution if you say one thing and the user is determined to hear something else entirely.
Did you install the game first, then install the 3.4 Beta patch? If not, what version are you running?
Thanks,
Ralph
Ralph Trickey
TOAW IV Programmer
Blog: http://operationalwarfare.com
---
My comments are my own, and do not represent the views of any other person or entity. Nothing that I say should be construed in any way as a promise of anything.
Hello,
Have a athlon xp also and coming up with the same problem and same windows error box. No log generated, turned the intro off and turned log on only ini. changes made. Installed base game and all patches in order, in same directory. It plays fine with the updates until the beta [the new graphics is what made me reinstall the game]. will the alpha 3.4.0.191 fix my issue or will something else?
thank you for any help you can provide.
Budd
Enjoy when you can, and endure when you must. ~Johann Wolfgang von Goethe
"Be Yourself; Everyone else is already taken" ~Oscar Wilde
*I'm in the Wargamer middle ground*
I don't buy all the wargames I want, I just buy more than I need.
That's why they don't have me writing the manuals, I guess.
