I've just downloaded an installed SP5 for VB6 (http://msdn.microsoft.com/vstudio/sp/vs6sp5/default.asp)

I've created a dummy project with one form, and used the package and deployment wizard to create a setup routine that I can run on all of my workstations to get them up to SP5. I am thinking I must have done something wrong, since SETUP.LST shows 2000 datestamps on the VB runtime.

****
[Bootstrap Files]
File1=@VB6STKIT.DLL,$(WinSysPathSysFile),,,6/1/99 12:00:00 AM,101888,6.0.84.50
File2=@COMCAT.DLL,$(WinSysPathSysFile),$(DLLSelfRegister),,5/31/98 12:00:00 AM,22288,4.71.1460.1
File3=@STDOLE2.TLB,$(WinSysPathSysFile),$(TLBRegister),,6/3/99 12:00:00 AM,17920,2.40.4275.1
File4=@ASYCFILT.DLL,$(WinSysPathSysFile),,,3/8/99 12:00:00 AM,147728,2.40.4275.1
File5=@OLEPRO32.DLL,$(WinSysPathSysFile),$(DLLSelfRegister),,3/8/99 12:00:00 AM,164112,5.0.4275.1
File6=@OLEAUT32.DLL,$(WinSysPathSysFile),$(DLLSelfRegister),,4/12/00 12:00:00 AM,598288,2.40.4275.1
File7=@MSVBVM60.DLL,$(WinSysPathSysFile),$(DLLSelfRegister),,8/21/00 12:00:00 AM,1388544,6.0.89.64
***

Note the MSVBV60.DLL is August 200
VB6STKIT.DLL is 1999

This can't be right!

Have I not included the VB6 runtime in the project properly? There was no option to include or exclude the VB6 runtime.