General Category > General Discussion

Addon Manager **SOLVED**

<< < (10/14) > >>

virtuali:
I urge everyone using FS Copilot to launch the Stand-alone Addon Manager installer again, because we have another update that *might* fix the problem.

If it works, it only confirms what I was suspecting, that was a problem of system libraries conflict, because nothing has changed in the Addon Manager actual code, just a compiler settings to use system library in a slightly different way (which wasn't touched in ages so, it means it has been broken by a Windows Update).

Is still not very stable, because I still get a consistent crash when exiting from FSX, but only if FS Copilot is enabled. However, since it does exactly the same in FS9, which never had any problems together with the Addon Manager, it might be an entirely different issue.

allybear21:
Not sure what you did, but all is working again!  I used the new addon manager and have no more problems with start up or with FSINN/FSCOPILOT.  Thank you for fixing this issue so quickly.  Ok, now back to my cockpit!

papalimabravo:
Hi Virtuali
I've got some little problems with these sceneries (LSGG/KJFK/KLAS/KORD/LSZH): no building appears now and I don't understand why. I've tried to reinstalled the sceneries and the new addon manager but nothing are working.
I can't explain why. I red all the forum lines about the problem which occurs many time but I didn't understood how to resolve it I'm sure its should be not a big problem but I need help.
Thank you for your extremely patienza (when reading the forum!) and also for taking time for me (if you can).
Got any solution?
Thanks by advance
Phil

bojote:

--- Quote from: virtuali on January 25, 2010, 02:35:19 pm ---just a compiler settings to use system library in a slightly different way (which wasn't touched in ages so, it means it has been broken by a Windows Update).

--- End quote ---

Umberto, care to share? I know this is unrelated, but I'm trying to help fix a bug in the Level-D 767 ground menu. It ocasionally shows a ntdll.dll CTD error when opening. I want to contact Wade (the developer) with some solid evidence of this being a 'possible' bug with the Level-D and since you mention compiler settings, Im guessing (like you said) Windows Update changed something along the way that could be the cause of CTD's.

My guess is:
ms vc++ 2005 redistributable and some define somewhere plus a security fix preventing/breaking compatibility, correct?

virtuali:

--- Quote from: bojote on January 26, 2010, 04:12:39 pm ---ms vc++ 2005 redistributable and some define somewhere plus a security fix preventing/breaking compatibility, correct?
--- End quote ---

No, I haven't changed anything in the program code, and not even in the actual c++ compiler: it was related to how the code is wrapped when signed, and how this interacts with installed system libraries.

That's might be a reason. There are several security hotfixes that updates files related to those runtimes, one of them might have broken compatibility between a standard library call that was used by both programs.

In fact, is more complex than that, because there's also the issue of the Windows Side-by-Side loading mechanism, which should in theory fix those problems, but it requires all the apps using those libraries to have an embedded manifest (which the Addon Manager has, the FS Copilot hasn't, that's why their eventual dependencies of different versions of the same library can't be solved with the Side-by-side system)

And, there's also the side-by-side policies mechanism, which is a file that automatically "upgrades" a program to use a newer version of a .DLL (if found), even if that program had a manifest that specified an older version. But, of course, nobody can be 100% sure that the newer version doesn't break compatibility with programs compiled for earlier version.

The main issue here is, as usual, security: there's a conflict between the simple Side-by-side, which allows programs written for different version of the same library to run together, each one loading its own version (which wasn't possible before side-by-side) and the policies, that upgrades those older programs to use the newer libraries, which are supposed to be more secure, but there's an added risk of breaking compatibility.

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version