I wouldn't go as far as saying that msvcr80.dll is part of Windows. I have
Windows XP Pro Sp1a and I do not have msvcr80.dll. I do not have dot NET
either.

MS sez msvcr80.dll is Microsoft® C Runtime Library. Comes with Microsoft
SQL 2005 Server Enterprise and Microsoft Visual Studio 2005 Professional.
http://support.microsoft.com/dllhelp...l&S=1&x=9&y=11

I do not doubt that msvcr80.dll is also included with dotNET.

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In news:MHEuf.599$WY5.576@newsread2.news.pas.earthlin k.net,
JP <jp@private.nospam> hunted and pecked:
> "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_6595b64144
ccf1df_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 ???

Thanks for that, it could explain a few things, I belive the DOT Net was part
of XP SP2, but I am not completely sure. It did appear just after I updated
to SP2.. So did a few glitches ????

Thanks again
--
EREITIZ
But I am not quite sure what IT is ???


"Wesley Vogel" wrote:

> I wouldn't go as far as saying that msvcr80.dll is part of Windows. I have
> Windows XP Pro Sp1a and I do not have msvcr80.dll. I do not have dot NET
> either.
>
> MS sez msvcr80.dll is Microsoft® C Runtime Library. Comes with Microsoft
> SQL 2005 Server Enterprise and Microsoft Visual Studio 2005 Professional.
> http://support.microsoft.com/dllhelp...l&S=1&x=9&y=11
>
> I do not doubt that msvcr80.dll is also included with dotNET.
>
> --
> Hope this helps. Let us know.
>
> Wes
> MS-MVP Windows Shell/User
>
> In news:MHEuf.599$WY5.576@newsread2.news.pas.earthlin k.net,
> JP <jp@private.nospam> hunted and pecked:
> > "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_6595b64144
> ccf1df_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 ???
>
>

Now that I think about it, .NET Framework may have come with SP1 or as an
update, I can't remember. I got rid of it though. The only thing that I
have is a .NET passport and I wouldn't have that if I didn't need it for
some MVP stuff. ;-)

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In news:CB1BB763-0DC5-4392-AFD9-C03308E02B91@microsoft.com,
Pete @ ereitiz <pete.hunt(removethis)@ntlworld.com> hunted and pecked:
> Thanks for that, it could explain a few things, I belive the DOT Net was
> part of XP SP2, but I am not completely sure. It did appear just after I
> updated to SP2.. So did a few glitches ????
>
> Thanks again
> --
> EREITIZ
> But I am not quite sure what IT is ???
>
>
> "Wesley Vogel" wrote:
>
>> I wouldn't go as far as saying that msvcr80.dll is part of Windows. I
>> have Windows XP Pro Sp1a and I do not have msvcr80.dll. I do not have
>> dot NET either.
>>
>> MS sez msvcr80.dll is Microsoft® C Runtime Library. Comes with
>> Microsoft SQL 2005 Server Enterprise and Microsoft Visual Studio 2005
>> Professional.
>>
http://support.microsoft.com/dllhelp...l&S=1&x=9&y=11
>>
>> I do not doubt that msvcr80.dll is also included with dotNET.
>>
>> --
>> Hope this helps. Let us know.
>>
>> Wes
>> MS-MVP Windows Shell/User
>>
>> In news:MHEuf.599$WY5.576@newsread2.news.pas.earthlin k.net,
>> JP <jp@private.nospam> hunted and pecked:
>>> "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_6595b64144
>> ccf1df_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 ???

Thanks Wesley
I wish I knew how much of the junk on my C: drive I could get rid of without
causing problems with any programmes, I suspect about 50% of windows & office
would be about right, freeing up loads of space and possibly stopping some of
the conflicts and slow-downs..

Thanks again

Byeeeeeeee
--
EREITIZ
But I am not quite sure what IT is ???


"Wesley Vogel" wrote:

> Now that I think about it, .NET Framework may have come with SP1 or as an
> update, I can't remember. I got rid of it though. The only thing that I
> have is a .NET passport and I wouldn't have that if I didn't need it for
> some MVP stuff. ;-)
>
> --
> Hope this helps. Let us know.
>
> Wes
> MS-MVP Windows Shell/User
>
> In news:CB1BB763-0DC5-4392-AFD9-C03308E02B91@microsoft.com,
> Pete @ ereitiz <pete.hunt(removethis)@ntlworld.com> hunted and pecked:
> > Thanks for that, it could explain a few things, I belive the DOT Net was
> > part of XP SP2, but I am not completely sure. It did appear just after I
> > updated to SP2.. So did a few glitches ????
> >
> > Thanks again
> > --
> > EREITIZ
> > But I am not quite sure what IT is ???
> >
> >
> > "Wesley Vogel" wrote:
> >
> >> I wouldn't go as far as saying that msvcr80.dll is part of Windows. I
> >> have Windows XP Pro Sp1a and I do not have msvcr80.dll. I do not have
> >> dot NET either.
> >>
> >> MS sez msvcr80.dll is Microsoft® C Runtime Library. Comes with
> >> Microsoft SQL 2005 Server Enterprise and Microsoft Visual Studio 2005
> >> Professional.
> >>
> http://support.microsoft.com/dllhelp...l&S=1&x=9&y=11
> >>
> >> I do not doubt that msvcr80.dll is also included with dotNET.
> >>
> >> --
> >> Hope this helps. Let us know.
> >>
> >> Wes
> >> MS-MVP Windows Shell/User
> >>
> >> In news:MHEuf.599$WY5.576@newsread2.news.pas.earthlin k.net,
> >> JP <jp@private.nospam> hunted and pecked:
> >>> "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_6595b64144
> >> ccf1df_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 ???
>
>

Thanks Wesley
I wish I knew how much of the junk on my C: drive I could get rid of without
causing problems with any programmes, I suspect about 50% of windows & office
would be about right, freeing up loads of space and possibly stopping some of
the conflicts and slow-downs..

Thanks again

Byeeeeeeee
--
EREITIZ
But I am not quite sure what IT is ???


"Wesley Vogel" wrote:

> Now that I think about it, .NET Framework may have come with SP1 or as an
> update, I can't remember. I got rid of it though. The only thing that I
> have is a .NET passport and I wouldn't have that if I didn't need it for
> some MVP stuff. ;-)
>
> --
> Hope this helps. Let us know.
>
> Wes
> MS-MVP Windows Shell/User
>
> In news:CB1BB763-0DC5-4392-AFD9-C03308E02B91@microsoft.com,
> Pete @ ereitiz <pete.hunt(removethis)@ntlworld.com> hunted and pecked:
> > Thanks for that, it could explain a few things, I belive the DOT Net was
> > part of XP SP2, but I am not completely sure. It did appear just after I
> > updated to SP2.. So did a few glitches ????
> >
> > Thanks again
> > --
> > EREITIZ
> > But I am not quite sure what IT is ???
> >
> >
> > "Wesley Vogel" wrote:
> >
> >> I wouldn't go as far as saying that msvcr80.dll is part of Windows. I
> >> have Windows XP Pro Sp1a and I do not have msvcr80.dll. I do not have
> >> dot NET either.
> >>
> >> MS sez msvcr80.dll is Microsoft® C Runtime Library. Comes with
> >> Microsoft SQL 2005 Server Enterprise and Microsoft Visual Studio 2005
> >> Professional.
> >>
> http://support.microsoft.com/dllhelp...l&S=1&x=9&y=11
> >>
> >> I do not doubt that msvcr80.dll is also included with dotNET.
> >>
> >> --
> >> Hope this helps. Let us know.
> >>
> >> Wes
> >> MS-MVP Windows Shell/User
> >>
> >> In news:MHEuf.599$WY5.576@newsread2.news.pas.earthlin k.net,
> >> JP <jp@private.nospam> hunted and pecked:
> >>> "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_6595b64144
> >> ccf1df_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 ???
>
>

If you want to be an expert, just start deleting stuff. Stop one step ahead
of rendering your machine in-operable. Just kidding. :-)

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In news:6F85A7C4-1ABC-4AA1-B0ED-BA02F058B10F@microsoft.com,
Pete @ ereitiz <pete.hunt(removethis)@ntlworld.com> hunted and pecked:
> Thanks Wesley
> I wish I knew how much of the junk on my C: drive I could get rid of
> without causing problems with any programmes, I suspect about 50% of
> windows & office would be about right, freeing up loads of space and
> possibly stopping some of the conflicts and slow-downs..
>
> Thanks again
>
> Byeeeeeeee
> --
> EREITIZ
> But I am not quite sure what IT is ???
>
>
> "Wesley Vogel" wrote:
>
>> Now that I think about it, .NET Framework may have come with SP1 or as an
>> update, I can't remember. I got rid of it though. The only thing that I
>> have is a .NET passport and I wouldn't have that if I didn't need it for
>> some MVP stuff. ;-)
>>
>> --
>> Hope this helps. Let us know.
>>
>> Wes
>> MS-MVP Windows Shell/User
>>
>> In news:CB1BB763-0DC5-4392-AFD9-C03308E02B91@microsoft.com,
>> Pete @ ereitiz <pete.hunt(removethis)@ntlworld.com> hunted and pecked:
>>> Thanks for that, it could explain a few things, I belive the DOT Net was
>>> part of XP SP2, but I am not completely sure. It did appear just after I
>>> updated to SP2.. So did a few glitches ????
>>>
>>> Thanks again
>>> --
>>> EREITIZ
>>> But I am not quite sure what IT is ???
>>>
>>>
>>> "Wesley Vogel" wrote:
>>>
>>>> I wouldn't go as far as saying that msvcr80.dll is part of Windows. I
>>>> have Windows XP Pro Sp1a and I do not have msvcr80.dll. I do not have
>>>> dot NET either.
>>>>
>>>> MS sez msvcr80.dll is Microsoft® C Runtime Library. Comes with
>>>> Microsoft SQL 2005 Server Enterprise and Microsoft Visual Studio 2005
>>>> Professional.
>>>>
>>
http://support.microsoft.com/dllhelp...l&S=1&x=9&y=11
>>>>
>>>> I do not doubt that msvcr80.dll is also included with dotNET.
>>>>
>>>> --
>>>> Hope this helps. Let us know.
>>>>
>>>> Wes
>>>> MS-MVP Windows Shell/User
>>>>
>>>> In news:MHEuf.599$WY5.576@newsread2.news.pas.earthlin k.net,
>>>> JP <jp@private.nospam> hunted and pecked:
>>>>> "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_6595b64144
>>>> ccf1df_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 ???