tomasz86

I uploaded the v2 version of the Rollup without the two USB-related updates (838417 & 843503).

Thank you very much for this input. Actually I've also had an issue with Webcam making my system freeze but until now I've associated it with the buggy driver of the cam (because the other cam worked without any problems). After reading your posts I think it's not the driver but the buggy usbhub.sys file that causes these instabilities. I also have a question - did you also find bugs in any other patches than KB838417? Should KB843503 also be avoided?

We're back to the v4 time but it's probably the only way to get it work without any problems, including FDV fileset. Windows2000-KB2479628-v7-IE5-x86-ENU.exe (3.12 MB) Windows2000-KB2479628-v7-IE6-x86-ENU.exe (3.69 MB) I also fixed the cosmetic issues, ie. moved *.map files to the separate folder so they are not copied by HFSLIP anymore and also added the additional tags (-v7-IEx) to the update name so they are easier to distinguish now.

WildBill, Some time ago you started to put *.map files in your unofficial updates. The problem is that HFSLIP treats them exactly the same as all other files and SLIPSTREAM (copy) them into i386 folder. In order to avoid it, they have to be put in a different folder, ex. If would be nice if you could do it when making future updates

It'll be a very hard task to get everything to work by just changing the update (2479628) The structure of the newest version (6a) is exactly the same as the official Microsoft's one used in 900725. HFSLIP and FDV fileset is the problem here, not the update. Ideally, the one to be modified should not the update but rather HFSLIP and FDV fileset. But the reality is different I'm trying doing my best to get it to work but I'm not sure if it's possible now.

Well, I think I found out why HFSLIP does not slipstream the file when FDV fileset is used. What I managed to do so far is: 1. By changing the checking mechanism it is possible to make the new browseui.dll being installed on a running Windows 2000 system regardless of the registry settings. It can be done by changing the update.inf settings to check .dll file versions instead of checking the registry. 2. Slipstreaming still does not work. Why? The problem here lies in the HFSLIP itself. This is the reason: IF EXIST HFCABS\_IE6_HFSLIP.CAB SET VERSIONIE=2KIE6&SET IE6SLIP=PASS IF EXIST FDVFILES\WIN2K SET VERSIONIE=FDV IF "!VERSIONIE!"=="2KIE6" ( (...) IF EXIST TEMP\xpsp2_binarydrop MOVE/Y TEMP\xpsp2_binarydrop\*.* TEMP >NUL HFSLIP changes IE version to FDV and this is why files placed in xpsp2_binarydrop folder do not get copied. They get copied only when IE version says 2KIE6. I can fix is easily but it would require to edit the HFSLIP .cmd file itself... It also means that the IE6 version shlwapi.dll from KB900725 is not copied when using FDV fileset. I believe there is a way to have it done but the problem needs to be approached from a totally different perspective :< I have something in mind but I'm not sure whether it will work. I want to avoid editing the HFSLIP source. What I can do now is to upload the updated version which can be installed (but not slipstreamed) in a system where FDV fileset was used.

Well, theoretically they should be installed only when you experience the issue mentioned in the KB article of the hotfix as according to Microsoft they were not as thoroughly tested as normal updates. However, I've been slipstreaming them for a long time in my system and have not experienced any problems connected with them. They address a variety of issues, from system errors up to HD audio support. Personally I think it's useful to have them installed/slipstreamed

I know what ought to be done to get it to work with FDV fileset. But I need to do some tests myself before uploading the fixed version

Could you also check what happens when you use FDV fileset and slipstream KB900725 and check which version of shlwapi.dll is copied? It should be 6.0.2800.1740 in case of IE6 and 5.0.3900.7068 when IE5 is present. The mechanism of copying these dlls is exactly the same as I used in 2479628.

Strange because I don't have these problems with icons: Are you using the newest version (v6a) of 2479628? As for IE6, update.inf identifies IE version basing on this HKLM, "SOFTWARE\Microsoft\Internet Explorer", "Version", "REG_SZ", "6.0.2800.1106" Could you check your version?

I tried to run IE7 without installing some time ago and see what system files are needed in order to do it. As far as I remember, the first one it asks for it's urlmon.dll and it seems that it's possible to replace the native W2k one with the newer IE7 version. However, the next dll file made the system unable to boot. It was 1-2 months ago so I don't remember which one was that. Still I think it would be much more useful and fruitful to try doing IE8 and just skip IE7. It doesn't really bring anything special as its engine is the same as IE6. Porting it to W2k will surely be a hard and painful work but the gain is going to be very little.

WildBill, Do you think it might be possible to port IE8 to Windows 2000? It would probably require to modify a lot of system files and add all the required functions from XP in order to get it work but still a working IE8 would give a new life to the old Win2k The structure of IE8 installer package is almost the same as normal update. Windows Internet Explorer 8 for Windows XP I'm intentionally not saying anything about IE7 as its engine is basically the same as IE6 so it doesn't give us any real benefits over IE6.

As WildBill uploaded the corrected version, I removed mine from the server As for the HBR Rollup, I started a separate topic related to it

Here are the links Windows2000-KB654654-Prf-v3-x86-ENU.exe (18.72 MB) Windows2000-KB654654-Srv-v3-x86-ENU.exe (20.13 MB)

This project has been discontinued. Please check the Unofficial SP 5.2 for Windows 2000 thread for more information.

Great but... you put browseui.dll twice there should be only one left in the xpsp2_binarydrop folder @edit I suspected something because size of the new file was about 500 kb larger than v5 Actually it shouldn't matter as update.inf contains only links to xpsp2_binarydrop\browseui.dll but I'm not so sure about how HFSLIP would react to the second browseui.dll, especially concerning IE5/6 compatibility. Just in case I quickly made a v6a version without the second unnecessary browseui.dll Windows2000-KB2479628-v6a-x86-ENU.exe @edit Just to prove that everything is OK now: Great job WildBill B)

1. KB957280 is not a hotfix (by request). 2. ntdsa.dll version 5.0.2195.7313 is already included in one of the other updates (I don't remember which one now but it's not a hotfix (by request)) 3. My Rollup is not intended to include the newest versions. HBR Mini Rollup contains files which originally belong to hotfixes (by request). 49 hotfixes (by request) are listed on bristols' page. 43 of them are combined into one in this rollup.

1. There will be a server version 2. I'm basing all my updates on bristols' updates list. KB957280 is listed there as obsolete and the other two are not present at all. I can't tell now if they were also replaced by other hotfixes or they are missing from the list. Let's wait for bristols himself to say something about it. Please keep in mind that this is HBR Update Rollup so I'm not going to include any other, i.e. non- hotfix (by request) updates.

I think I misunderstood what you meant by "showing thumbnails" Still, if you'd like to check PotPlayer, this version for sure works in a W2k system: PotPlayer1.5.27313.EXE

I prepared something special for today HBR Mini Rollup for Windows 2000 Professional 1. What is it? HBR Mini Rollup is a roll-up style package which contains almost all so called hotfixes (by request) available for Windows 2000 Professional. Server version hotfixes are not included in this package. HBR stands for "hotfix (by request)". 2. The following updates are included: 3. Which hotfixes (by request) are not included? KB822834 - Server hotfix KB823658 - Server hotfix KB838018 - Front Page Extensions; Server only but if you use it on a W2k Pro system then you should install it separately KB906952 - Server hotfix KB896414 - problematic hotfix (uses HFSVCPACK_SW1 instead of HF folder) KB925783 - Server hotfix 4. What is the purpose of this Rollup? The main reason for making this HBR Rollup is to simplify the process of slipstreaming hotfixes by using HFSLIP. This Rollup can be put directly into the HF folder. You do not have to and should not slipstream any of the hotfixes listed in point 2 because they are already included in this Rollup. The other reason is that in order to download a hotfix (by request) you have to input your e-mail address, rewrite a random code, download the hotfix from an URL sent on your e-mail address and use a password to unpack the file with the hotfix so it takes a lot of time to download all of them. 5. Technical information The filename of HBR Rollup is Windows2000-KB932590-v2-x86-ENU.exe. KB932590 is the last hotfix (by request) released by Microsoft. HBR Rollup uses its filename and its catalog file too. Catalog files from the rest of the integrated hotfixes are also registered when installing this Rollup. KB915985-v2 is made by BlackWingCat and contains a modified ntdll.dll file. The rest of the integrated updates are the official ones from Microsoft. 6. Screenshots 7. Download Windows2000-KB932590-v2-x86-ENU.exe (18.73 MB) @edit The URL temporary removed as the new version is coming soon @edit

I see but the result is that the file is replaced on reboot instead of being replaced instantly. That's what I'm trying to say Is there any particular reason to set an 8 flag when installing a hotfix? Is it just to avoid system instability when replacing the files on a running system?

Now I get it If the 8 flag is present, the file will be replaced on reboot. If there is no flag and the file is not in use, then it'll be replaced immediately. If the file is in use the 8 flag does not make any difference. Is it right?

So basically speaking if I just want to have the hotfix install only files whose version is higher than those present in the system, is the best way to just remove all these ",,,8" flags?

I checked the explanation given in http://www.sokoolz.com/addons/r64/ADVANCED_INF.pdf but I'm still not sure... What exactly will be the difference between the two strings [CopyAlways.Cache.Files] sp3res.dll,,,8 and [CopyAlways.Cache.Files] sp3res.dll when installing a hotfix on a Windows 2000 system? Let's say that an older version of sp3res.dll is already present in system32 directory.

Thank you very much for all the information I'll check all of them. How about the other question? Sometimes the same file is listed twice: sp3res.dll sp3res.dll Does it also have a specific function?