Celestia Forums

Hello,

When I try to launch Celestia 1.6 rc1 after installation on a Windows XP computer, I get this message.


The last line means something like “This application could not run because its configuration is incorrect. Reinstall the application could solve the problem.”

Actually, reinstalling does not solve anything.

I have installed the c++ runtime libraries and now that works fine.
Therefore I suspect that the setup program doesn’t install all the required libraries if there are not already present on the computer.

[EDIT]
Perhaps is it a variation of the bug reported by Guckytos about windows 98 complaining to not find MSVCP80.dll

Hi jogad,

have you tried replacing the RC1 Celestia.exe with one from the SVN builds? The one that was mentioned and linked in the RC0 thread?
This solved to my surprise the error on Win 98.
I think I had a similar error message for RC0 on my windows XP.

The same RC1 (used on 98 with trouble) installed without any trouble under XP for me. It's a strange world.

Hi,

I think that it is not Windows XP or Windows 98 themselves. It depends on the Microsoft C++ runtimes that are installed or not on the computer.
As Celestia RC1 executable for Window was compiled with MS VC++ 2008, I downloaded the
Microsoft Visual C++ 2008 Redistributable Package (x86)

Microsoft wrote:The Microsoft Visual C++ 2008 Redistributable Package (x86) installs runtime components of Visual C++ Libraries required to run applications developed with Visual C++ on a computer that does not have Visual C++ 2008 installed.

I suppose that it is possible that the installation program does this job.
If not, it should be clearly mentioned during the install process.

On Installation of RC1 I experienced the same problem as jogad, at least I got the same error message. My OS is Windows XP SP2. Installing vcredist (= Visual C++ runtime components) didn't solve the problem. Maybe Celestia does not find the libraries, because it doesnot know the correct path leading to them. (Actually they are not installed in windows\system32.)

Does anybody have another idea, how to get RC1 working?

lidocorc

Which version of vcredist did you install? There are several.

Apparently Celestia needs some runtime libraries which are not on your computer. I'm not certain which versions work, but my understanding is that RC1 was built with Visual Studio 2005. You might try installing the redistributable libraries available for Visual Studio 2005 SP1. They can be downloaded from Microsoft's Web site at
http://www.microsoft.com/downloads/deta ... 9c36f85647

Hopefully this problem will be fixed in RC2.

You should seriously consider upgrading to Windows XP SP3, too. It includes many bug fixes and security updates which are not in SP2. There were problems with SP3 on some computers which use AMD chipsets but were shipped with a configuration flag set which said they had Intel chipsets. You'll have to check the Website of the manufacturer of your computer to see if you need the patch which fixes that problem.

Now I gave RC2 a try and, I'm sorry to say that, this version is not working on my computer either.

Fortunately I found abramson's compilation in
cabfst28.cnea.gov.ar/~abramson/celestia/svnexec/celestia-svn4718.zip.

I changed celestia.exe by the one Guillermo compiled and now celestia is working as it should.

Now I ask myself, what is wrong with my computer (OS installation, display drivers, VisualC runtime libraries, etc.) or what is the secret behind why one compilation is working but the other one is not?

lidocorc

lidocorc,

Please provide a screenshot of the error message(s) that you see.

This is the error message I get, when I start celestia.exe as it is contained by the installation package of release candidate 2. I hope this might help, whereas the message itself doesn't seem to be very meaningful.

Translated from german: “This application could not be started because its configuration is not correct. Reinstallation of the application could solve the problem."

Annotation: There is a typo in the german text. It should read "..., weil die Anwendungskonfiguration nicht korrekt ist. ..."

Thank you, Selden, for taking care of this problem.

lidocorc

lidocorc,

Thanks for the screenshot!

You have no reason to thank me: I'm just the person who tries to get others to be specific in their problem reports

This is a problem which will have to be resolved by the person who creates the Windows installtion kit, i.e. Chris.

It would help a lot if others having a similar problem would post their screenshots, too. Unfortunately, those of us who have their computers configured to compile Celestia don't get this error.

I don't know how experienced you guys are with Windows. But there is a cute tool that is somewhat analogous to 'ldd' in UNIX, which sorts out the entire tree structure of the used APIs. You will also be told what is missing, if something is missing.

The tool is called

Dependency Walker. It's a free Microsoft product (originally) and quite sophisticated. I have used it often. It also runs under Vista.

Here is the URL:

http://www.dependencywalker.com/

Fridger

These installation problems should be fixed in 1.6.0 RC2. See this thread:

viewtopic.php?f=2&t=13822

If you've experienced installation troubles with RC1, please try RC2 and report your results. It would help us out in verifying that the installation problem is indeed fix. None of the people who build Celestia are able to test the fix, because we've all got the required libraries installed already.

--Chris

@chris:
Sorry for not having created a new title for my post. I should better have titled it: Ongoing installation problems with RC2

Perhaps this may be worth saying to give further hints:

The Windows installation kit of RC2 comes with runtime libraries for VC++ which are all stored in Celestia's home directory (msvcm80.dll, msvcp80.dll, msvcr80.dll).
With Guillermo's compilation of celestia.exe these libraries are not needed. On my computer these dlls even don't exist anywhere else, but there are msvcr71 and msvcr90 in %windir% subdirectories instead. (Sorry, I like programming with Delphi and know little about VC++.)

lidocorc

lidocorc wrote:Perhaps this may be worth saying to give further hints:

The Windows installation kit of RC2 comes with runtime libraries for VC++ which are all stored in Celestia's home directory (msvcm80.dll, msvcp80.dll, msvcr80.dll).
With Guillermo's compilation of celestia.exe these libraries are not needed. On my computer these dlls even don't exist anywhere else, but there are msvcr71 and msvcr90 in %windir% subdirectories instead. Sorry, I like programming with Delphi and know little about VC++.)

Exactly. I added the runtime libraries specifically to get around the problem. I think that Guillermo built Celestia with an older version of Visual C++, so you only need the msvcr71 libraries, which everyone should have already. But, we can't keep using older versions of the compiler. Visual C++ 2005 and later feature better code generation and improvements to the standard C++ libraries. In the next version of Celestia we will be using the Eigen library, which only supports SSE2/3 vector instructions with VC++ 2008 and later. Etc.

Does RC2 work ok for you?

--Chris

Unfortunately it does not. Because graphics drivers are often the root of all troubles, I updated them recently. What reasons are left now?

lidocorc wrote:Unfortunately it does not. Because graphics drivers are often the root of all troubles, I updated them recently. What reasons are left now?

Do you get the same error message as before?

--Chris

Yes, RC1 and RC2 show the same error message. Sorry.

lidocorc

lidocorc,

Have you tried running depends yet?
( v2.2 is available at http://www.dependencywalker.com/ )

It should list in red the dlls that are missing when you tell it to run Celestia.

selden wrote:lidocorc,

Have you tried running depends yet?
( v2.2 is available at http://www.dependencywalker.com/ )

It should list in red the dlls that are missing when you tell it to run Celestia.

Selden,

do you also sometimes look at other mails?

A few above this one, you might have read :

Fridger wrote:I don't know how experienced you guys are with Windows. But there is a cute tool that is somewhat analogous to 'ldd' in UNIX, which sorts out the entire tree structure of the used APIs. You will also be told what is missing, if something is missing.

The tool is called

Dependency Walker. It's a free Microsoft product (originally) and quite sophisticated. I have used it often. It also runs under Vista.

Here is the URL:

http://www.dependencywalker.com/

Fridger

That's why I wrote "have you tried depends yet"
Everything else was a brief reminder.

selden wrote:That's why I wrote "have you tried depends yet"
Everything else was a brief reminder.

Oha, that's sophisticated