VCRedist and MSVCP60.dll

[Nick]

Well, the official way to redistribute those bits of MFC that I want is to
use VCRedist. But this doesn't run on Win2000 (why is this?? I've unpacked
it and looked at the .inf file but I'm not sure why....). Trouble is Win2000
doesn't have MSVCP60.dll, which I need. I have been copying this file by
hand (checking version numbers, of course) but I'd like to know what I
should really do with this. I have had a few machines say (something like):

"Win2000 has detected that the setup has replaced a vital system file.
Please insert Service Pack 1"

What is the correct way to get this file onto Win2000???

-Nick

[Doug Harrison [MVP]]

Nick wrote:

See this message:

http://groups.google.com/groups?as_umsgid=sgpbbucuk9ejh0hvr...@4ax.com

I don't know why Win2K is giving you that message, but I'd certainly
find out why. Which file is it talking about? If you're replacing this
file, what are the version numbers? You may have a bug in your setup
program.

--
Doug Harrison
Microsoft MVP - Visual C++
Eluent Software, LLC
http://www.eluent.com
Tools for Visual C++ and Windows

[Ed Dore [MS]]

Hi Nick,

Per the following KB article:

Vcredist.exe Installs the Latest Run-Time Components for Visual C++
Applications
http://support.microsoft.com/default.aspx?scid=kb;EN-US;q259403

VCRedist only targets NT4 and Win9x. It's primary purpose was to provide
for an easy installation of the most common runtime components people need
on those older OS's to ensure that their VC 6.0 applications would run
properly.

On newer operating systems where we've tried to lock down and stabalize the
OS (WinME, Win2K and XP) the bulk of the files in VCREDIST are considered
part of the OS, and are only updatable via OS service packs.

Unlike the MSVCRT.DLL and MFC42.DLL, the MSVCP60.DLL isn't considered a
part of the OS. I never did get a good answer on why this was the case. But
to answer your question, you'll want to install it as if it was a shared
component. That is, install it to the SYSTEM32 directory, and only when
it's not already there, or if the existing version is earlier than yours.

It's interesting that you're seeing that "replaced a vital system file"
message. Was this specific to installing the MSVCP60.DLL, or some other
file? I suspect the latter, as MSVCP60.DLL isn't in the known DLL list.
Also, would it be possible to determine if a specifc OS service pack was on
those problem systems?

Sincerely,
Ed Dore [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.