Warzone crashes on execution

[The Wicked Flea]

Well, on Windows that would entail installing Visual Studio for its debugger. Dunno that I want to install it though. But we'll see in the short-run here, I may wind up needing it.

Now you can see why I'm so stumped about what is going on. I've checked everything I can think of, I happen to be a programmer as well so this is a lot, and nothing has made an ounce of a difference. I do think that only the debugger in Visual Studio can give a hint, as I did have it installed last time.

[Buginator]

1) I have a GeForce 9800GT without the latest drivers, they're the last stable driver version that I have found (I had previous trouble) though they are somewhat slower than the newest release. I downgraded purposefully, thinking initially that they were the cause of Warzone's trouble.

2) My Desktop resolution is 1280x1024, refresh rate is 75hz, color depth is at 32; dual monitors with the exact same specifications and settings. The last time I had this configuration, right before I had to reformat my system for maintenance, Warzone did run just fine and I turned my other monitor off due to super-saturation that occurred. This is normal in my experience: that the game allocates a handle and it is fit to a screen instead of both screens.

I've tried game-specific settings to turn on various compatibility extensions, turn down the high things that can make some games crash, and even the way the dual monitors are handled by the card. (Performance versus compatibility, etc.) Returning to a single display does nothing.

3) It was actually just hex dumps of the various files that were loaded, no locations of exceptions, etc. Error offset is purportedly 0x0025b0d1, wherever in the app that is. As I said, the rest is just hex dumps of given locations within all libraries and executables allocated by Warzone.


Is there anything the game does prior to allocating the log handle? Is it the absolute first thing done, or is there something else? I'm not even getting a 0-byte file on my harddrive from this, and every time I run the game I tell it to spit out a debug file.

It first checks the command line, then it inits physFS, then config dir & search paths.

If you got one of the nightly debug builds from trunk, and you entered this :
--flush-debug-stderr --debug all
on the command line, and still nothing, I am guessing it has to do with popt (command line parser lib).

Do you have any resident anti-virus programs on? If so, turn those off, and give it a try.

[tabaz]

well, iam having the same problem. Tried to track it down with sysinternals processmonitor.
It has probably something todo with the last access before crash: setupapi.dll
The logfile shows the requested dll (version: 5.1.2600.1106) in my warzone2100 dir, this was just for testing! (default location: Windows\system32)

Developers: uploaded logfile to: http://www.divshare.com/download/6619804-b6b

My system: Windows XP SP3, nvidia geforce 18x driver, nforce 650sli

[Buginator]

well, iam having the same problem. Tried to track it down with sysinternals processmonitor.
It has probably something todo with the last access before crash: setupapi.dll
The logfile shows the requested dll (version: 5.1.2600.1106) in my warzone2100 dir, this was just for testing! (default location: Windows\system32)

Developers: uploaded logfile to: http://www.divshare.com/download/6619804-b6b

My system: Windows XP SP3, nvidia geforce 18x driver, nforce 650sli

Can you upload bug reports to here instead? http://developer.wz2100.net/newticket

Also, try the new 2.1.2 out, and again, try with --debug all and post the logs in that ticket.
Thanks!