"Pete @ ereitiz" <pete.hunt(removethis)@ntlworld.com> wrote in message
news:70BEB9F2-5685-4513-9E7C-A4EBABEC2289@microsoft.com...
> JP
> Many thanks, I think it must be me who needs 'new' glasses, you are quite
> right about the file name, and I have completed the actions you suggested,
> with favourable results - so far...
> --
> EREITIZ
> But I am not quite sure what IT is ???


I appreciate your follow-up. I am glad my input (from my own experience,
actually) was of some help.

AFAIK: the msvcr80.dll is one of the Dynamic Link Library files that is a
component of MS Dot.NET v2.00, and thereby, presumably, of Windows itself. I
do not know the exact function, but Dot.NET uses it from the directory I had
pointed out earlier.

NSW however, expects all system files (or most of them at least) - including
such dlls - to be located within the default Windows\System32 directory
which is the *normal* location for most essential system files. Which is why
it comes up with the 20 or so instances where it tries to find "links" or
such to this file from MS Dot.NET pointing to the System32 directory. Which,
naturally, it does not. Hence those "errors" that it finds on a scan!

I am not dissing NSW but WinDoctor has a habit of labelling as an error
whenever it encounters such situations and apparently cannot (or will not)
recognize that such "missing" files do exist elsewhere!

Cheerio.

JP
---


> "JP" wrote:
>
>> Sorry, the location directory for msvcr.dll should read this way:
>>
>> C:\Windows\WinSxS\x86_Microsoft.VC80.CRT_1fc8b3b9a 1e18e3b_8.0.50727.42_x-ww_0de06acd
>>
>> Maybe I do need glasses after all as my better half always gently
>> suggests
>> from time to time.
>>
>> :-)
>>
>> JP
>> ---
>>
>>
>> "JP" <jp@private.nospam> wrote in message
>> news:SUyuf.5498$nu6.5105@newsread1.news.pas.earthl ink.net...
>> > Might be that the file is actually msvcr80.dll (not msver80.dll).
>> >
>> > AFAIK:
>> >
>> > This error usually is "caught" by NSW after a PC is updated with MS
>> > DotNET
>> > Version 2.0.
>> >
>> > The file is installed correctly in the appropriate directory:
>> > Windows\WinSxS\x86_policy.5.2.Microsoft.Windows.Ne tworking.Rtcdll_6595b64144ccf1df_x-ww_c7b7206f
>> >
>> > NSW gives the error because it thinks the file should actually be
>> > located
>> > in
>> > the Windows\System32 directory.
>> >
>> > You can either select "Ignore the problem" within NSW or simply copy
>> > (NOT
>> > move!) msvcr80.dll to Windows\System32 directory. That will keep NSW
>> > *happy*.
>> >
>> > Or one can always *Ignore NSW* - a course of action deemed wise by
>> > many,
>> > including yours truly.
>> >
>> > Double check the file name on your NSW error list before doing
>> > anything.
>> > The
>> > above suggestion is worthless if the file name is not msvcr80.dll.
>> >
>> > Anything you do, you do at your own risk.
>> >
>> > JP
>> > ---
>> >
>> > "Pete @ ereitiz" <pete.hunt(removethis)@ntlworld.com> wrote in message
>> > news:FD571C96-09C5-4BD1-9402-EA7F4EDA2851@microsoft.com...
>> >>I have been using NORTON systemworks for some years now with very
>> >>little
>> >> trouble but, since I obtained ntl broadband and installed the
>> >> appropriate
>> >> software i keep getting an error repeated 10 to 20 times every time I
>> >> run
>> >> 'one button checkup' .. Basically several applications are trying to
>> >> find
>> >> a
>> >> file "msver80.dll" .. I have searched my XP installation disk and all
>> >> the
>> >> other software I can think of to no avail. Can you tell me where I can
>> >> find a
>> >> copy of this file and where should I copy (or install) it to ??
>> >> --
>> >> EREITIZ
>> >> But I am not quite sure what IT is ???
>> >
>> >
>> >
>> >
>> >
>>
>>
>>