General Category > General Discussion

PMDGSounds.dll problem **SOLVED**

<< < (2/3) > >>

mosteen:
Thanks, I did that after removing GSX with modules the first time. Installed both x86 and 64 from MS site.

After installing GSX again, I have two instances of the x86.

That's how I see that it is the one installed by GSX that is in an unknown language; if I try to uninstall, the dialog language is not in english.

Is it correct that AOM should install a duplicate C++ when I allready have the version installed?

virtuali:

--- Quote ---Is it correct that AOM should install a duplicate C++ when I allready have the version installed?
--- End quote ---

If the version numbers are identical, that's not a duplicate. It's only a duplicate entry in the uninstall registry key, which doesn't mean you have two version of the .DLL installed, you only have two ways of uninstall them.

I checked the MS website, and there's no Norwegian version of the VC++ redist so, it's possible the installer picked up a language related on the OS we compiled our installer under, which is Italian (that "strange" language you might have seen), I'll see if it could be possible to force to run the MS installer always into English mode.

But, again, this is just a cosmetic issue: it's simply the language the uninstaller will be displayed, it doesn't have any effect on the actual installed files. Thankfully, MS got rid of the hideous Side-by-side system with the VC++ 2013 runtimes, and they reverted to the good old system of just placing files in the Windows\System32 folder, and those are always the same files, and are:

MSVCR120.DLL
MSVCP120.DLL

So, regardless of which language used the installer/uninstaller, you'll always end up with these files only, and no duplicates.

mosteen:
Roger, thanks again, I'll try with re-arranging my entries to see if I can get the situation to change, will report back.

Cheers,

mosteen:
Finally managed to solve it, I rearranged my dll.xml, put bglmanx.dll at the very bottom, still got the error message when starting FSX, but this time when pressing OK on the question if I wanted to load PMDGSounds.dll anyway, there was no CDT.

Next time I started FSX, no error message!

Happy times!

Some of my hassle with this was bound to my ignorance; namely that I thought I had to get rid of the warning, no matter what. That was obviously not the case.

Thanks for your support Umberto, your direct and no-nonsense responses to our (sometimes nonsensical) quieries are much appreciated!

Regards,
Morten Steen

mosteen:
Sadly this issue resurfaced after downloading and installing the latest Addon Manager today.

I tried the usual remedies, rearranging dll.xml and re-trusting the modules, but no luck.

Weird stuff :)

Navigation

[0] Message Index

[#] Next page

[*] Previous page