General Category > General Discussion

Do I need VC+++ 2005?

(1/3) > >>

Frank Lindberg:
Hi,

I just saw in my add/remove programs folder that I have many VC++ from 2005 up to 2012. My question is now, do I need those from 2005 and how far can I delete them up to?

Paul J:
Don't delete any of them Lindberg! Each one of those is a specific (redistributable) version of the C++ programming language, and will be required by the application (or addon), that they were installed with.   ;)

All the Best,

pj

virtuali:
FSX itself needs the VC++2005 runtimes so, so Simconnect and any other FSX addon out there because, even those that were made using VC++2008 runtimes (like PMDG) have a double dependency to both the 2005 (because the Simconnect every FSX addon links to requires is) and the 2008 runtimes. All our products requires the 2005 (SP1) runtimes and if you have the 2010 and 2012, surely some other application installed them.

So, basically, unless you are trying to troubleshoot a problem, if everything seems to work, don't touch them.

Frank Lindberg:
ok, thx guys. It's just that my fsx is unstable  :-\ I get "fatal error" often. And yes I did tried the issue with the UIAutomationCore.dll. I run fsx as admin and run it in XP sp.2 mode. Any other idea? 

PS: See my pc spec. in my signature.

virtuali:

--- Quote from: Lindbergh72 on November 20, 2012, 06:14:51 am ---ok, thx guys. It's just that my fsx is unstable  :-\ I get "fatal error" often
--- End quote ---

Without knowing WHAT is crashing, it's not point meddling with the VC++ 2005 runtimes, so you need to check your Event Viewer to understand what crashed. If it's the G3D.DLL (most common crash in FSX), it's not related to the VC++ runtimes, that would be either a "runtime error" or an error in MSVCR80.DLL.



--- Quote ---I run fsx as admin and run it in XP sp.2 mode. Any other idea?  
--- End quote ---

It's not a problem running FSX as admin, but turn off the XP SP2 mode, because it only creates problems.

However, instead of running FSX as Admin, the best setup is to install FSX in a folder outside C:\Program Files, so you won't run into any permission issues with non-Vista/Win7 compliant addons, without having to run As Admin, which might be a bit unsafe, since a potential malware running inside FSX (like a virus that attached to an FSX module) would be able to get complete access to your system. Instead, if you had FSX installed into C:\FSX, and ran FSX as a regular user, it wouldn't be able to do much damage, except on that folder.

Navigation

[0] Message Index

[#] Next page