FreeOrion

What is the error message? You'll want to post it on the forum so that people can diagnose the problem. To copy the message from the "command prompt" you ran FreeOrion on, and into your post, right-click inside the prompt window, press "mark," highlight the text area you want to copy, and right-click on that selected area. (If you're wondering why it makes you do all that, don't ask me: I don't have any idea, either.) It should be on the clipboard, and you'll be able to paste it in your browser with ctrl-v or right-click->paste. If it comes up on a separate window, you'll probably be able to select the text normally.

Or take a screenshot and attach it to a post. If you don't know how to take a screenshot and save it, google it. Regardless, the point of doing that all was to know what, if anything, was output on the console after running freeorion from within it. Just that a message is shown doesn't help.

So we get a ogre.log, freeoriond.log, but no freeorion.log. Maybe I'm missing something here, but isn't that weird? The server isn't launched before a game is started, and El Barto doesn't ever get even near to that point because apparently freeorion.exe crashes even before it's own logging mechanism is started. So there should be no freeoriond.log anywhere.

El Barto, can you go to the folder where you found freeoriond.log and ogre.log, delete the entire contents of this folder, launch FreeOrion once more (which will subsequently crash), go to the folder again and tell us which files exactly are in this folder after the crash?

Another thing you can try is installing older test builds or rather the last point release 0.4 (can be downloaded here). Might be important to know if one of them works.

Sorry, I know, that's a bit tedious, frustrating and annoying, but the information gathered this way may help us diagnose the problem...

One final question: You have WinXP 32bit installed, right? Or do you happen to have WinXP 64bit?

Yes, it's strange. The date in freeoriond.log suggests it was created the day of or before his first post, so it's not from an older version having been run earlier. It's possible to run the server directly from the command line, which would result in a log similar to what was posted, which might be possible as I'm unsure of whether he was able to run things from the command line without explicit instructions to do so...
His first post says he tried FreeOrion 4961-Test-Win32. Builds from the last year or so probably wouldn't be any different in terms of starting up ogre setup stuff. Maybe some of the older v0.3.x releases would work differently.

I updated my driver from 11.4 to 12.4 - nothing have changed.
The usual error message in XP. Did you Able to understand the inscription in Russian?
Here it is: http://i46.tinypic.com/2vjsd8i.png
There is a file that windows created with an error message. It create the file in to the directory: C:\Documents and Settings\User Name\Local Settings\Temp
I attach a file (zipped) to this post.
I did it exactly as you asked.
http://i49.tinypic.com/2yuhhdh.png
http://i48.tinypic.com/3humd.png
I downloaded 7 different releases. Here the results:
FreeOrion-4961-Test-Win32-Setup - crash
FreeOrion-0.4-Setup.exe - crash
FreeOrion-0.3.17-Setup - crash
FreeOrion-0.3.13-Setup - crash
FreeOrion-0.3.12-Setup - crash
FreeOrion-0.3.11-Setup - working
FreeOrion-0.3.10-Setup - working

It turns out that 0.3.11 is the latest version, which works on my computer.
Yes! I am using now WIN XP pro SP3 32-bit.

What is your Windows user name?
Based on the commit logs, it appears that v0.3.11 was the last one before the client was built around Ogre, starting with v0.3.12. This doesn't tell me much, other than that it's a problem with Ogre, which was already apparent from the contents of ogre.log. Thanks for checking all those versions, though...

This is my personal information. It's a secret. Why do you need that?

Since you seem to be Russian, I'm wondering if it has any non-Latin characters which might cause problems with a filesystem library. Looks like I already asked that earlier though, so nevermind.
I was asking about any error messages on the command line; the point of going into cmd.exe and running from there was to be able to see anything output to the console after running and crashing.

I'm pretty much out of ideas for what else to check. If the problems start with v0.3.12, it's not an issue with executables built with MSVC 2010 specifically (since that compiler version wasn't used until at least v0.3.16). It's not an install corruption issue since you tried a bunch of different versions. It just seems that Ogre, or at least the OpenGL rendersystem, won't start on your system.

Maybe building against the latest version of Ogre would help, but I'm not very hopeful.

Although I can't read Russian at all, one of the screenshots seem to indicate a crash in the graphic card's GL drivers. Which would also point to Ogre.
Well, we can give it a try. I build r4999 against Ogre 1.8.0, the binary can be downloaded HERE. El Barto, can you install this build on your PC and try again?

Did you rebuild all the relevant dependencies, including ogre, against the same version of boost? If not, you may have dependency on multiple versions of boost, depending what version the ogre dlls you included (hopefully?) were built against... so you might need to include multiple versions of the boost dlls in the installer... Updating boost and ogre is not trivial, which I why I don't do it very often.

I did include the Ogre DLLs from the 1.8.0 SDK in the installer, but I didn't rebuild any dependencies against boost. I'm well aware of the problem, as boost is included in the Ogre SDK, and the version shipping with 1.8.0 is boost 1.49. Which is bound to cause issues as FO uses boost 1.47.

Nevertheless I gave it a try, just replaced the Ogre lib, include and DLL files with the ones from the 1.8.0 SDK, rebuild FO, produced the installer package and installed this FO package on my Windows test box. I wanted to see how far I can get this way, and was actually able to start FO, get to the intro screen and launch a game. As that's all what's needed to see if the current Ogre version can solve the issues on El Barto's system, I didn't bother going to all the trouble to rebuild all relevant dependencies. The build I put up isn't supposed to be a functional test build, it's only purpose is to see if El Barto can get to the intro screen and launch a game successfully (that's why I put it into an extra folder "Special purpose builds" on SF).

Should El Barto be able to successfully start FO and launch a game, then we can consider going through all the pain involved with switching to Ogre 1.8. Ugh...

I'm sorry, but it still crashes.

Ok, let's see what else we can do:

1.) I assume you have some kind of Antivirus Software running on your system. You can try the following: Uninstall FO, disable your AV, reinstall and run FO.

2.) Besides your AMD Radeon HD 5670, does your PC also have an integrated graphic processor? Like Intel GMA XXXX? If that's the case, maybe you can try to connect your display to the integrated graphics - however, for this solution to work you'd probably first have to enable the integrated graphics, and disable the AMD Radeon in your BIOS. As you already needed step by step instructions for the command line, messing with BIOS settings isn't something you should do on your own (because you should really know what you're doing if you try that). Maybe, if you have some computer savvy friends, they can help you with that.

3.) Finally, there's the option of reinstalling your OS from scratch. Which is of course a ridiculously huge amount of trouble to try to get one game running, and you'll probably need assistance for that one too.

Other than that, I'm out of ideas, sorry. There's only so much I can do from here, to provide further assistance I'd need to be at your place, which is obviously not possible

He could try running other programs built with a recent version of Ogre, to see if they will start up. In particular, if it's a driver issue, it might matter whether the OpenGL or Direct3D render systems are used. I don't feel like explaining how to do that, though.

Is it even possible to switch to the Direct3D render system without substantial modifications to the source code...?