[NEED INFO] Empty configfile one Windows: game won't start

[kage]

i don't know about windows debugging (msvc probably can do something like this, but you probably have to pay for the $500 ide to get anything usable). djgpp more than likely has the tools for this.

also, you can install gcc for windows and use gdb, or you can install cygwin and gcc (in which case you'd have something like "gcc for unix for windows").

[Sento]

Maybe it help you:
Windows creates several crash reports the files are called:

Warzone2100.exe.hdmp
Warzone2100.exe.mdmp
appcompat
manifest

they look interesting... if you want them i can send it to you

[DevUrandom]

Sure, send them!
If possible put them into a zip (or 7zip) file and attach them here.
Else write a mail to warzone-dev at gna org. It is our mailinglist which is posting restricted, but I will allow your mail to go through the filter, when I see it.

[Sento]

okay they are unpacked together 30 mb packed around 1mb
the most (80%-90%) of the 30 mb are spaces

It crashed with a manual made config, before it crash the screen is maximized,the intro screen apears for a very short time. than it turn black and crash.

Without a config it crashes with a minimized whole time black screen. There is only one little file created similar to the appcompat

[DevUrandom]

Which version of Warzone did you say you use?
(I messed up the VersionInfo in the .exe, so I can't rely on it and there seem to be a lot of .dlls involved according to appcompat.txt, so I suspect it is 2.0.5_rc1?)

I'll have a look on that reports with MSVC. With only text editors (and MS' interesting UTF16 thingy) it doesn't make much sense...

But I'll keep this Windows Crash Reports in mind. Seems like they can be quite usefull...

EDIT:

MSVC reports that the exe the Mini Dump was created with is not the one I am using... So it seems as you were indeed not using 2.0.5...

And those report are actually not very usefull... They would be if I had compiled WZ with MSVC (which again would have required our users to install the MSVC redist). But as I don't have the MSVC Program Debug Databases (.pdb), MSVC can't help me anything.
And as I guess there is no way to use GCC debug information from within MSVC, I am quite stuck...

It seems as another discussion rises again: Shall I compile with MSVC and force our users to install the MSVC redist or shall I compile with GCC and be not able to use Microsoft Windows Debug Reports... *umpf*

[Sento]

yes it is the 2.0.5_rc1 i started it with grims gfx mod, but it crashs also when i start normal. i also tried a ealier version but its the same.

Did you found out something about the config bug?

[DevUrandom]

Could you try again with the 2.0.5? (Please uninstall _rc1 before!)

The backtrace of your crash is:

Code: Select all

Backtrace:
=>1 0x7c91eb94 in ntdll (+0xeb94) (0x0012cd5c)
  2 0x7c809c86 in kernel32 (+0x9c86) (0x0012cd78)
  3 0x6990763c in faultrep (+0x763c) (0x0012d704)
  4 0x699082b1 in faultrep (+0x82b1) (0x0012e778)
  5 0x7c863059 in kernel32 (+0x63059) (0x0012e9ec)
  6 0x78138b5e in msvcr80 (+0x8b5e) (0x0012ea0c)
  7 0x00407f93 in warzone2100 (+0x7f93) (0x0012ffc0)
  8 0x7c816d4f in kernel32 (+0x16d4f) (0x0012fff0)
  9 0x00000000 (0x00000000)

So it seems as if it was created by the msvcr80 (MSVC Runtime 8.0).

(BTW: Problem solved: WINE is able to load mdmp files, so I don't need MSVC.)

[Sento]

okay uninstalled and installed 2.0.5
when i start the programm now its closing after a second without a windows bug report.
The config file is empty.

There is something special on my system: im using the omega radeon driversbut its hard to imagine that that the problem.
i could try to install the original wz (1.00+ patches) when you think it could help.

[Kamaze]

Do you have a antivir running? or something similar wich could block the access to the config file!?

[Sento]

i have antivir running but the file is really empty i open it with the notepad there is nothing in
the file is created by warzone but empty. Maybe there is a problem with that part of the programm that write this file? I tried to deactivate av but it changes nothing

[DevUrandom]

I don't think that a virusscanner could be the problem... I have one installed (who doesn't?) and it works like a charm.

Maybe it didn't crash, but abort... That would explain the "missing" crash report...

I think I did not yet ask you to try to enable debug output:
Open the preferences of the Warzone 2100 shortcut and add "--debug all" to the commandline options ("...warzone2100.exe" --debug all).
Try this not on the Grim's graphics shortcut, but on the other one, and try starting that. Then send us the 2 files in the Warzone directory: stdout.txt and stderr.txt
Maybe this can clarify where the error is happening...

[Sento]

okay here ist it the other is empty

[Sento]

no ideas where the problem could be?

[Watermelon]

I think I had a similiar problem with msys+GCC builds in windows(no crash error or stderr or whatever,just crashes at 'Mornin' line),though I never had such problems with other IDE+GCC builds or MSVC builds.

[DevUrandom]

Sorry, without a backtrace it is really hard to debug.
Actually we have 2 problems:
1. Warzone writes a config "of size 0", which is very weird and I don't know a fix for.
2. It crashes somewhere after that for a yet unknown reason.