Of course you must have noticed it a long time ago but, just for the record, it's happening again:
When I updated Java to 8u202, I found out atmzzrSystemCheck v3.5 thinks it's 8u20 !!!
However, Oracle has fixed it on their side, so atmzzrSystemCheck v3.5 recognizes 8u212 correctly, at last!
So, here'se some good news, for a change!
Forum for anything else which doesn't fit in the above forums. Site feedback, random talk, whatever, are welcome.
When I tried the atmzzrSystemCheck utility I noticed that VC++ 2005/2008/2010 had not been detected which could be remedied by placing msdia80.dll, msdia90.dll, and msdia100.dll in the %ProgramFiles%\Common Files\Microsoft Shared\VC folder. The reason for the absence of these files was that I had updated VC++ 2005/2008/2010 using yumeyao's [Addon] Microsoft Runtime Libraries Collection(x86) 2.0.7 which I have updated myself. I remember reading in the forum an expert member assuring us that msdia80.dll, msdia90.dll, and msdia100.dll are unnecessary for 99% of users, and can be safely omitted. I have since discovered that these dlls have the description Microsoft® Debug Information Accessor, and need to be registered on the system so that applications can access debug information stored in program database (.pdb) files generated by Microsoft postcompiler tools.automizzer wrote: ↑Fri Dec 27, 2013 11:21 amThe same thing with VC++ - installer (in CP) version is different than files and also main fileversions differ from each other. Another tough one to decide but after I've downloaded all the older releases and analyzed all together I've decided to check for the .dll's that are present in every build and are known as the main runtime dlls:
2005 -> msdia80.dll
2008 -> msdia90.dll
2010 -> msdia100.dll
2012 -> msvcp110.dll
2013 -> msvcp120.dll
I am considering revising my update for the Microsoft Runtime Libraries Collection(x86) 2.0.7 to include these dlls, and at the same time enabling the addon to be used in the DX WinNT6.x True Integrator which I know how to do.