View Single Post
  #19  
Old 09-08-2006, 03:28 AM
bumbo bumbo is offline
Registered User
bumbo's Avatar
Join Date: Apr 2002
Location: Canada
Posts: 26
bumbo is on a distinguished road
Send a message via ICQ to bumbo Send a message via AIM to bumbo Send a message via MSN to bumbo
OK, sorry to bump an old topic but I thought everyone should know that downloading and copying this file is not the appropriate solution to the problem....I have been searching around the internet and have found several posts from Martyn Lovell, some C++ Architect at Mickey$oft, this is not the appropriate solution, as it will do nothing but cause catistrophic consequences in the future. Stefan, I suggest you contact this chap and see if the two of you can work out some sort of a solution to this issue, it will most likely require the redesign of the Graal system libraries and whatnot...

Quote:
Originally Posted by From the MSDN Forums, re:Norton Windoctor having the same issues as graal is apparently having

Hello everyone,

My name's Martyn Lovell, and I'm the development lead of the team that produces msvcr80.dll [The Visual C++ Libraries team]. There are a couple of things I'd like to clarify.

First, Norton WinDoctor is wrong. It incorrectly reports that msvcr80 is missing when in fact it is correctly installed in the WinSxS directly in the windows. folder. If you own WinDoctor, you should report this bug to Symantec so that they get it fixed.

Do NOT copy the this file to any of the folders WinDoctor recommends.

If you've already attempted to take corrective action for this issue (by copying msvcr80.dll or msvcr80d.dll to ...\system32 or to the .NET Framework directory), please undo this. These files do not need to be copied around, and doing so may cause problems in future.

Please feel free to contact me directly if you have more questions, as I don't read this forum regularly.

Martyn Lovell
Development Lead
Visual C++ Libraries
[email protected]
So as you can see, copying this file is not the appropriate solution...

Quote:
Originally Posted by More from Martyn re:Windoctor
I wanted to add one more comment on this thread, based on the subsequent discussion.

Creating a blank file in system32 with the name msvcr80.dll is also NOT the correct solution to this problem or a safe thing to do. If you've created a blank file, I strongly recommend deleting it.

The correct thing to do about this problem is NOTHING. Norton have been contacted, and will eventually fix their tool, but in the mean time, taking "corrective" action here is only risking causing problems later.

if you search around the net you can find several threads like this one with "solutions" to this problem that stop Norton reporting this error. None of them are a good idea. You should un-do them if you have done them.

Martyn Lovell
Development Lead
Visual C++ Libraries
Apparently this issue has been around since December of 2005, but this is the MSDN forum posting where I found the advice:
http://forums.microsoft.com/MSDN/Sho...61926&SiteID=1
__________________
[email protected]
Reply With Quote