General Category > General Discussion
MSVCR80.dll and stop FSX ???
virtuali:
--- Quote from: pacojeal on January 18, 2011, 10:01:13 pm ---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
--- End quote ---
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.
--- Quote ---Thus there should be incompatibility with the others software and alone product FSDT stop
--- End quote ---
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 :-X
Apparently a proof that the problem comes from your softs :
virtuali:
--- Quote from: pacojeal on January 22, 2011, 04:10:59 pm ---Apparently a proof that the problem comes from your softs
--- End quote ---
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
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version