MSVCR80.dll and stop FSX ???

[pacojeal]

Hello to all

I am tres annoyed for 3 weeks because all my bought scene(stage) FSDT became out of order. I have them all and they worked before the intallation of Dallas 

When I want to use it one there is an arret of FSX   

In the code error there is a name of file this below

MSVCR80.dll   

Can use me

Thank you

[virtuali]

Surely it's not a problem of our sceneries and, it can't also caused by the Dallas installation, since the Dallas installer contains *EXACTLY* the same version of the Visual C++ 2005 runtime libraries ( MSVCR80.dll is part of them) we use for ALL our products so, it's just not possible Dallas created this problem, since the file it installs is exactly the same as for the other FSDT installers.

What might have happened, instead, is that ANOTHER product you installed, created a problem with the Visual C++ 2005 runtime libraries, which are also needed by FSX itself. A while ago, there was a known bug in the VC++ 2008 libraries, that corrupted the 2005 version (which is what FSX needs) if installed together. The bug has been probably fixed in later versions of the VC++ installers but, you might have installed a product which contained the bugged version. I know some PMDG products use VC++ 2008 libraries, but they might not be the only ones. Note that, this might happen even if installing something not related to Flight sim.

To fix your VC++ 2005 libraries, try this:

- Go in the Windows control panel, and Uninstall ALL the istances of the Visual Studio 2005 redistributable runtimes. You might have more than one version: remove them all.

- Then, after removing everything related to VS2005, reinstall again these 3 files:

http://www.microsoft.com/downloads/details.aspx?FamilyId=32BC1BEE-A3F9-4C13-9C99-220B62A191EE&displaylang=en
http://www.microsoft.com/downloads/details.aspx?FamilyID=200b2fd9-ae1a-4a14-984d-389c36f85647&displaylang=en
http://www.microsoft.com/downloads/details.aspx?familyid=766a6af7-ec73-40ff-b072-9112bab119c2&displaylang=en

[pacojeal]

In spite of the re install 3 files recommended but always the same problem

Only with scènery FSDT

All the rest works well

Message:

APPCRASH
fsx.exe
10.0.61637.0
46fadb14
MSVCR80.dll
8.0.50727.4927
etc...

Help me please

[virtuali]

Are you using a 64 bit OS ? If yes, remove again all 3 VC++ 2005 runtimes, and try to install the 64 bit versions.

In any case, I repeat the problem doesn't have anything to do with our sceneries. The fact you see it "Only with scenery FSDT", doesn't mean they are the *cause* of the problem. Instead, they are the *victim*. Fact you don't see it at other sceneries, it's because they don't need those libraries, which has been corrupted somehow on your system.

See this identical thread here:

http://www.fsdreamteam.com/forum/index.php?topic=3828.msg34297#msg34297

The user was also convinced it was a problem with our sceneries, because it happened only there, but in the end it was fixed by reinstalling FSX and Windows, which means the problem wasn't the scenery, but a problem with those libraries, which was fixed either by the FSX reinstall or the Windows reinstall.

[pacojeal]

I use a system 64 bits (Windows 7)

I think that the landscape FSDT are not responsible for the problem but that the anti system hacking is complex and that it is sensitive to the other add on

Thus there should be incompatibility with the others software and alone product FSDT stop

I cannot reinstall FSX and all add on regularly. Too much time is needed

A lot nobody stop purchases FSDT because they meet persistent problems

I am disappointed because the quality of the scenerys is remarkable but risks him not to take advantage of it completely is too important

I am thus going to have to stop the future purchases. Today I have toustes your scenerys

[virtuali]

I think that the landscape FSDT are not responsible for the problem but that the anti system hacking is complex and that it is sensitive to the other add on

Fact is, you are having a problem with the MSVCR80.DLL, which is part of VC++ 2005 runtimes, which are used by countless of software, even outside the Flight sim world so, being dependent on those libraries is not an indication of being "complex" and, of course, doesn't have *anything* to do with anti-piracy, since these are plain and simple C++ basic libraries that don't have any relationship with anti-piracy.

Thus there should be incompatibility with the others software and alone product FSDT stop

As I've said, a problem with such libraries might have been caused by any other software, not just flightsim-related. The main issue is, the Windows Side-by-Side mechanism, which is used by FSX itself AND by the VC++ libraries since VC++ 2005 and ALL subsequent versions, IS VERY FRAGILE, and easy to mess with AND COMPLEX. THIS is what is complex, NOT the Addon Manager, which is *forced* to use this system since, as with any other FSX module, needs to call into Simconnect, which is also using it.

See this post by Pete Dowson on Avsim:

http://forum.avsim.net/topic/323009-simconnect-gone-mad/page__p__1909995#entry1909995

He's saying exactly the same thing: when something goes wrong related to WinSxS, it's almost impossible to fix it without reinstalling the whole OS. And the VC++ runtimes are of course SxS, like almost all Windows system libraries. This was a system created to fix the infamous "Dll hell", but it created an even worse one.

Again on Avsim, a thread about MSVCR80.DLL crashing, maybe related to FSUIPC, but not entirely clear:
http://forum.simflight.com/topic/55841-fsx-crashes-to-desktop-ctd/

Another thread here, same MSVCR80.DLL error, fixed by reinstalling FSX:
http://flyawaysimulation.com/postt29372.html

And, another thread of the same error for an entirely different game:
http://forums.gaspowered.com/viewtopic.php?f=10&t=33349

As you can see, the MSVCR80.DLL error doesn't affect our products only, and doesn't affect FSX only either.

[pacojeal]

How to destroy MSVCR80.dll under Windows 7

These files seem lock

[virtuali]

Their uninstaller should be able to do it. Or, you can try booting in safe mode, and look for it (or multiple copies of it) in the C:\Windows\WinSxS folder, but then you'll have to reinstall all the redistributables.

Note that, this is a potentially very dangerous operation, you might easily end up with an unbootable system.

Before doing that, I'd start trying to understand if there might be a conflict with another addon (two modules running two different versions of the runtimes *should* be able to run together, but this doesn't always work).

Try the following:

- Open your %APPDATA%\Microsoft\FSX folder and look for those two files:

DLL.XML and EXE.XML

- MOVE them (don't copy) to a safe place (like your Desktop)

- Reinstall one of our sceneries. You'll see a prompt during the installation you had a problem with the XML files and the installer will suggest to create one from scratch, say YES.

This way, you'll have only our module running, and check if your problem was caused by a conflict with another module you have installed.

[pacojeal]

Always the same problem after the delete  EXE.dll and the XML.dll   

Apparently a proof that the problem comes from your softs :

[virtuali]

Apparently a proof that the problem comes from your softs

It's only a proof the problem doesn't come because of a conflict with another module, not that it comes from our own, otherwise *everyone* would have it. Instead, is proof the problem is a caused by one of your VC++  installed runtimes.

We can easily verify this in a different way: I'll send you by email or PM a different version of our module, which is exactly the *same*, save it's linked against a different version of the VC++ runtimes, one that is not (hopefully) broken on your system. It that works, it would be clear the problem was with one of the runtimes.

EDIT:

You have a PM

[pacojeal]

I loses a long time for 20 days without resolving this problem.

I have the problem with all the FSDT only

When I copy scenery manually there is not of stop fsx. The ground FSDT scenery appears without batiments

When I make an installation classique fsx stop as batiments loads

I reinstalled all C ++ 2005; C++ 2008 - C++ 2010 up to date

I discourage to find a solution

I put more than 150€ in your scenerys and today they remain unusable for 3 weeks

Please send me email with a part of 1 scenery without lock test if anti cracking is responsable

[virtuali]

I loses a long time for 20 days without resolving this problem

I have the problem with all the FSDT only

You are losing all this time, because you are insisting the problem is in our program, when instead the problem is your Windows install, which is AFFECTING IT. It's *not* CAUSED by our module, our module is being affected by a problem in your system.

Please send me email with a part of 1 scenery without lock test if anti cracking is responsable

Please, read again my last message. I've sent you a PM with instructions to download an alternate version which use a different VC++ version, 20 minutes before you posted your last message.

As I've said already, anti-piracy doesn't have anything to do with this: our sceneries would still require our module, because it does FAR MORE than "just" anti-piracy so, we'll use it even if we were to release a free scenery, and your system problem that is affecting it, wouldn't change even if there was no anti-piracy.

[pacojeal]

I do not know any more what to think on the origin of the problème

What I see it is that many of simmers have problems with airports  of FSDT

I congratulate nevertheless the ability to react of your assistance every day

[virtuali]

What I see it is that many of simmers have problems with airports  of FSDT

Wrong, first because your problem is completely different, and wrong, because only a FEW (not "many") users had problems, and with solved them ALL. And of course, most of the problems, were in fact caused by something else.

I congratulate nevertheless the ability to react of your assistance every day

Exactly, your problem is also being followed (and you know it) in a private way, on Sunday...

[pacojeal]

Always same problem today