brutus1234

??? Oh, yes, you're right... So, why in my previously slipstreamed win2k this file was older? mmhh, I'll investigate this... To be honest, I really can't remember neither how nor where I got all these files. Of course MDGx was not my source, since I'm after italian hotfixes. I didn't even know that was unofficial. Having said this, I call your attention over KB838751, an official exe which provides Msvcrt.dll ver 6.1.9847.0 If this is a package with strong hardware dependence, then you should apply it only after installing the OS, isn't it?

I collected all the hotfixes listed onto bristols' page and nevertheless several ones are still floating around on my hard disks; I've tried to slipstream most of them. Here you have some new packages and the new files they provide (I will not list old/superseded files they provide). KB324446 disk.sys ver 5.0.2195.6901 explorer.exe ver 5.0.3900.6920 printui.dll ver 5.0.2195.6868 usbmon.dll ver 5.0.2195.6824 winspool.drv ver 5.0.2195.6825 KB837789 pathping.exe ver 5.0.2195.6906 ping.exe ver 5.0.2195.6906 tracert.exe ver 5.0.2195.6906 KB838018 fp4amsft.dll ver 4.0.2.8912 fp4awel.dll ver 4.0.2.8912 fpmmc.dll ver 4.0.2.8912 KB838141 rastapi.dll ver 5.0.2195.6824 KB896414 scesrv.dll ver 5.0.2195.7100 KB897711 wldap32.dll ver 5.0.2195.7059 KB932590 msvcrt.dll ver 6.1.9848.0 KB922667 (Windows 2000 Post-Service Pack 4 COM + 1.0 Hotfix Rollup Package 37) catsrv.dll ver 2000.2.3537.0 catsrvut.dll ver 2000.2.3537.0 clbcatex.dll ver 2000.2.3537.0 clbcatq.dll ver 2000.2.3537.0 colbact.dll ver 2000.2.3537.0 comadmin.dll ver 2000.2.3537.0 comrepl.dll ver 2000.2.3537.0 comsetup.dll ver 2000.2.3421.3537 comsvcs.dll ver 2000.2.3537.0 comuid.dll ver 2000.2.3537.0 mtstocom.exe ver 2000.2.3537.0 mtxdm.dll ver 2000.2.3537.0 mtxlegih.dll ver 2000.2.3537.0 stclient.dll ver 2000.2.3537.0 txfaux.dll ver 2000.2.3537.0 KB888111 (Universal Audio Architecture (UAA) High Definition Audio versione 1.0a) hdaprop.dll ver 5.10.1.5013 (previously unreleased) hdashcut.exe ver 5.10.1.5013 (previously unreleased) hdaudbus.sys ver 5.10.1.5013 (previously unreleased) hdaudio.sys ver 5.10.1.5013 (previously unreleased) hdaudres.dll ver 5.10.1.5013 (previously unreleased) portcls.sys ver 5.0.2195.6906 sysaudio.sys ver 5.0.2195.6906 KB811392 (Dskcache.exe tool) dskcache.exe ver 1.0.0.0 (previously unreleased) KB822834 Ntprint.dll ver 5.0.2195.6745 Hope I didn't forget anything! Edit: they all slipstream with no problems, now my new win2k system seems working as usual.

Well, I'm slipstreaming hotfixes into my win2000 subfolder and hfslip prints out messages I cannot fully understand. The message I worry about is "La sintassi del nome del file, della directory o del volume è incorretta." which means (I translate from Italian) "filename sintax, or directory sintax, or volume sintax is wrong" which in turn may mean "wrong command or filename" or sort of. In this stage, is hfslip calling a command? an executable? I don't know. Note that these messages only appear when slipstreaming Windows Media components (I am slipstreaming WMP9 Series). Are these messages alerts? Are they relevant? Have I to worry about'em?

So, tell me if I'm wrong, the whole setup is made of smaller steps, and each step if named after the average time remaining (to the setup completion)?

So, my script should detect the processor vendor (amd), then the processor model (Athlon, Athlon XP, Athlon MP, mobile Athlon 4, Duron), then if the motherboard has an agp port and finally integrate the registry patch... I'm sorry, this is way too much for my cmd knowledge...

It is not difficult to modify the IE6sp1 links on the bristols' updates page to get the italian packets, but here you can get them all in a second. BRANDING.CAB (8.3 kB) IEW2K_1.CAB (1.8 MB) IEW2K_2.CAB (1.7 MB) IEW2K_3.CAB (1.8 MB) IEW2K_4.CAB (2.1 MB) MAILNEWS.CAB (1.9 MB) OEEXCEP.CAB (20 kB) SCRIPTIT.CAB (803 kB) WAB.CAB (584 kB)

About the update page: I need help, I got confused. The entry SCRIPTEN.CAB (IE6sp1 component, the ita cab is named SCRIPTIT.CAB) is stated as `Script 5.6'. The issue is I am slipstreaming just Script 5.7 components/updates and there are several warnings about mixing different versions. So, if I just want Script 5.7, can I skip SCRIPTEN(SCRIPTIT).CAB?

I have found this update on amd's site, it is a tiny registry update for amd boxes with agp motherboards. Can hfslip slipstream it? If it can, is it harmless to integrate it in a generic installation CD (which can be installed on an intel box as well)?

Any...? Ehy, bristols! Look in the title bar, the box "Windows 2000 Updates (HFSLIP)" doesn't turn purple on mouse move!!! Well, aside from my joke, your page is very clear and the work is great, thank you for your effort!

Thank you guys! Should I also find what "T-13" is?

Mmhh, what if I actually want it to be installed? What is going to happen?

How can you say they aren't? I also would like to check if any of my hotfixes (in HF\ subdir) are actually slipstreamed but I don't know how. Maybe I can make HF\ subdir lighter...

I'm actually watching hfslip while it's slipstreaming a fresh new win2k installation disc with all my hotfixes. In early stages it extracts (I guess) the updated files stored into the hotfixes, while printing how many of them it's going to use, so I see: `N files copied' with several different N. Sometimes it happens N is 0 (no file copied), is this an expected behaviour? How is this possible? I am sure that hotfix does contain a new file (1 at least!). Why does hfslip copy no file? I must say, I know nothing about how hfslip works inside... can someone give me a hint?

Well, raw dotNET framework 2.0SP2 provides its files with version number 2.0.50727.3053. KB958481 updates many components to 2.0.50727.3082 KB974417 updates components to 2.0.50727.3603 (it's replaced by KB983583) KB976569 provides upgrade to 2.0.50727.3607 (GDR branch, whatever this means...) KB979909 updates some components to 2.0.50727.3613 (GDR branch) KB982167 is an update for some components to 2.0.50727.3614 (GDR branch) KB983583 updates components to 2.0.50727.3615 (replaces KB974417, GDR branch) KB2418241 update to 2.0.50727.3618 (GDR branch) Last, but not least, we have KB971111 a security update for GDIPLUS.DLL (jump to version 5.2.6001.22319)

It seems the GDR branch has been installed. No, it runs flawlessly and updates the files. Back soon with new data about these hotfix.

@Bristols: about your windows2000 updates page, I just slipstreamed Q828026 and I can confirm it is unneeded. As reported here, on windows 2000 it provides msdxm.ocx ver 6.4.9.1128 wmp.dll ver 9.0.0.3075 Well, msdxm.ocx is updated by KB891861 which provides ver 6.4.9.1129, and wmp.dll is updated by KB979402 which provides version 9.0.0.3367.

Well, I slipstreamed Windows2000-KB838417-x86-ITA.EXE sp5 release and the three files usbd.sys ver. 5.0.2195.7008 usbhub.sys ver 5.0.2195.7006 usbser.sys ver. 5.0.2195.7006 are onto the disc image, although usbser.sy_ will not be installed.

I need some help. In KB articles explaining about these updates for .net20sp2 I read there are two update branchs shipping into the package: GDR branch and LDR branch. I can't understand the difference. What will happen when trying to install such a package on a win2k system? Will GDR branch be installed? Will LDR branch? Perhaps will it refuse to run?

Well, I've got a Professional edition. Anyway, I'd like to include only the very latest build of these .sys files... ...Or slipstream it and see what happens!!!

Thank you, Bristols! Well, about kb838417 now I know which one I need. Here's my log: Windows2000-KB838417-x86-ITA.EXE sp5 release contains: usbd.sys ver. 5.0.2195.7008 usbhub.sys ver 5.0.2195.7006 usbser.sys ver. 5.0.2195.7006 Windows2000-KB838417-x86-ITA.EXE latest release contains: usbd.sys ver. 5.0.2195.6935 usbhub.sys ver 5.0.2195.6935 usbser.sys IS MISSING!

I just requested a bunch of these hotfixes, so microsoft let me download the packages. Now, I find two exe into the packages, one named as usual (Windows2000-KB872955-x86-ITA.EXE) and another with a `symbols' add (Windows2000-KB872955-x86-ITA-symbols.EXE). Am I supposed to use them together? Another question about KB838417: the italian page suggest two fixes, one labeled as `sp5' and another as `latest'! Which one is needed? Here's the link, thank you.

I found a couple of packages for windows2000 providing different runtimes and updates, they are the VisualBasic6sp6 runtimes, the updates for Common Controls and the VisualC2008sp1 runtimes. My questions are: are they still needed nowadays? (if they are) can hfslip slipstream them into win2k?

Mmmhhhh... Perhaps you meant "831375"?

You're right! Well, I stumbled into two more updates for dotNET2.0sp2: kb971111 and kb974417, here's a summary of my checks on microsoft's site: kb958481 released for winXPsp3 and winServer2k3 kb971111 needed! (replaces no bulletin) kb974417 needed! (replaces no bulletin) kb976569 released for winXPsp3 and winServer2k3 kb979909 needed! (replaces no bulletin) kb982167 released for winXPsp3 and winServer2k3 kb983583 released for winXPsp3 and winServer2k3 kb2418241 released for winXPsp3 and winServer2k3 Of course, new infos are welcome.

And beyond mine too. So, I will stay with 2.0SP2. Just wanted to add relevant hotfixes/security/critical update, if any. How can I know about them?