MSVCR80.DLL Errors

[Inverness]

Ugh, someone please give instruction on how to make a manifest file.

EDIT

Well after some searching I've found out how to fix the problem with a manifest file. A text file called manifest.txt is attached to this post. Place the file in your Graal folder and rename it to Graal4.exe.manifest to fix the Graal4 error. Copy it and rename to RemoteControl2.exe.manifest to fix that also.

I copied and pasted the info thats in the files from a URL I found in a different Graal post.
The URL
The Post

[Inverness]

I would like to know if this actually helps anyone.

[Devil]

I'm getting the problem when I click on a URL in PM's.

Picture :

[Inverness]

Originally Posted by Devil

I'm getting the problem when I click on a URL in PM's.

Picture :

Did you try my solution?

[Devil]

Sorry I didn't read if there was one, it doesn't bother me, just thought I'd let you guys know it's happening, if you didn't already.

I'll check out the solution.

[Inverness]

I've found the solution to the ATL80.dll problem, here is updated manifest for it.
Place attached manifest.txt in Graal folder and rename to Graal4.exe.manifest. And for RC do the same.

[Admins]

The problem with those manifests is that they are only working if you have exactly the same bugged dlls on your computer. Graal is not using those dlls (they are not existing on the computer where Graal is compiled) that's why it cannot be linked against them anyway.

[Skyld]

Originally Posted by Stefan

The problem with those manifests is that they are only working if you have exactly the same bugged dlls on your computer. Graal is not using those dlls (they are not existing on the computer where Graal is compiled) that's why it cannot be linked against them anyway.

Is Graal on Windows being built using Visual C++?

[zwr]

Originally Posted by Stefan

The problem with those manifests is that they are only working if you have exactly the same bugged dlls on your computer. Graal is not using those dlls (they are not existing on the computer where Graal is compiled) that's why it cannot be linked against them anyway.

Graal may not be using them directly but perhaps certain components like the standard windows buttons/check boxes/etc use them?
I say this because the errors were only generated (for me atleast) when i tried to open the player pm history. Additionaly after using the manifest files all the default buttons used in graal (playerlist, options dialog, etc) appear to be more uhm stylish now

[Devil]

The manifests didn't work for me, and as I said I uninstalled Windows Defender, and that's the best way to get Graal to work again.

Has anyone reported or tried to report this problem to Microsoft?

[Draenin]

I'm having this issue too, but have not installed Windows Defender. I have, however, installed .NET updates from windowsupdate.

[theunknown]

I have had this issue before and it required, if you have it, to uninstall Windows Live Messenger, or get the newest .NET Framework.

[Draenin]

I've done both, still experiencing problems.

[Inverness]

Manifest is not working?

[TalonShriner]

Wow... this post would have been good to know about about 5 minutes ago before I deleted all of my Graal files and emptied my recycling bin... Now I can't even install Graal without the MSVCR80.dll problem comming up X_x Any ideas how I can get my graal back? =/