[bristols]

I found that changing the IE version number to 6.0.2800.1106, in the registry locations above, allowed 2479628 to install correctly. Browseui.dll installed as expected. However, the icon glitches I mentioned above remain.

tomasz86, on 23 May 2011 - 12:49 PM, said:

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

That's great. But I guess my ongoing problems with 2479628, as a user of FDV's Fileset, should be posted in the HFSLIP forum. Why the fileset sets IE's version number as 6.0.2900.5512 I have no idea. At the moment I'm thinking that there is at least some problem with the fileset (or with my use of it), because I found that even my IE5-based HFSLIPped system has IE's version number in the registry as 6.0.2900.5512 (rather than 5.00.3700.1000 or 5.0.3862.1500).

This post has been edited by bristols: 23 May 2011 - 06:24 PM

[tomasz86]

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.

This post has been edited by tomasz86: 24 May 2011 - 01:18 AM

[tomasz86]

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.

[tomasz86]

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

This post has been edited by tomasz86: 24 May 2011 - 07:02 AM

[tomasz86]

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.

This post has been edited by tomasz86: 24 May 2011 - 08:57 AM

[WildBill]

tomasz86, on 24 May 2011 - 06:28 AM, said:

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

Sure, I can put them in separate folders. I include those to help anyone else who wants to patch those files.

[tomasz86]

WildBill,

I have one suggestion for you It's just a cosmetic thing but still

In strings section there is something like this (example taken from 2479628).

HelpLink = "http://support.microsoft.com?kbid=2479628"
  URLInfoAbout = http://support.microsoft.com

How about changing the URLInfoAbout from MS to "http://www.msfn.org/board/topic/146529-pe-tool-for-creating-patches"?

I did it for my HBR Mini Rollup:

HelpLink = "http://www.msfn.org/board/topic/151551-hbr-mini-rollup/"
  URLInfoAbout = http://www.msfn.org/board/topic/151551-hbr-mini-rollup/

This post has been edited by tomasz86: 26 May 2011 - 12:47 AM

[tomasz86]

I added a string to HFSLIP which solves the issue with FDV files and updates which use the xpsp2_binarydrop folder.

I'll make it it public after having done some more tests

[dencorso]

You all shouldn't use the so called "friendly names" for links expected to survive all IPB updates. Use instead the base form of the links:

http://www.msfn.org/board/index.php?showtopic=146529 
and 
http://www.msfn.org/board/index.php?showtopic=151551

which work no matter what.

[tomasz86]

Thanks for the tip I'll change the URL in the next version of the HBR Rollup.

[tomasz86]

I made a 2a version of KB981852. The changes I made are only cosmetic - the catalog file from 979683 was added so WU won't ask for it when 981852 is installed, and I also fixed the name to make it clear which version it is.

Actually the catalog from 979683 is present also in v2 but its name was changed to KB981852.cat. Now there are two catalogs inside - the original one from 981852 (XP version) and the one from 979683

Windows2000-KB981852-v2a-x86-ENU.exe





@edit

I did the same thing to 2079403. The catalog file from 955069 was added.

Windows2000-KB2079403-v1a-x86-ENU.exe


@edit 2

And 982214. The catalog from 971468 added.

Windows2000-KB982214-v1a-x86-ENU.exe

This post has been edited by tomasz86: 02 June 2011 - 08:19 AM

[tomasz86]

I did the same thing to these updates:

2124261 - added the catalog from 917537

2387149 - added the catalog from 924667

2360937 - added the catalog from 970238

2476687 - added the catalog from 978037 and moved WildBill's *.asm files to a different folder (so they won't be slipstreamed by HFSLIP)

2507618 - added the catalog from 980218 and moved WildBill's *.asm & *.map files to a different folder

Windows2000-KB2124261-v1a-x86-ENU.exe

Windows2000-KB2360937-v1a-x86-ENU.exe

Windows2000-KB2387149-v1a-x86-ENU.exe

Windows2000-KB2476687-v2a-x86-ENU.exe

Windows2000-KB2507618-v1a-x86-ENU.exe

I also got a new (well, used but still) monitor so comparing two update.infs in WinMerge is much easier now than before on an old 17' CRT 1024x768 The current one is still a CRT but a 22' one with a diamontron tube

This post has been edited by tomasz86: 03 June 2011 - 01:27 AM

[tomasz86]

v8 of 2479628 is ready:

Windows2000-KB2479628-v8-x86-ENU.exe

Changelog:
- added the catalog from 923191 (as 2479628 replaces 2296011 which supersedes 923191)
- suitable for both IE5- and IE6-based systems*
- fixed compatibility with FDV fileset**

* requires the newest beta (J v5) of HFSLIP (available to download at Mim0's site) when using with FDV fileset (thanks Mim0 for applying the fixes)
** IE6 files are slipstreamed correctly when using FDV & IE6 and also can be installed manually in a system which used FDV fileset (thanks BlackWingCat because I learnt how to do it by analising your KB989898)

This post has been edited by tomasz86: 04 June 2011 - 04:31 AM

[tomasz86]

I made a complete update of Web Folders. It combines 892211, 907306 and 956790 together. 907306 & 956790 normally are not available for Windows 2000.

Webfldrs-KB892211-v2-ENU.exe

Install only if you use Web Folders.

This post has been edited by tomasz86: 07 June 2011 - 06:21 AM

[WildBill]

Wow, you've been really busy. Sorry I haven't updated the master list -- would an admin mind doing it if I can't get to it? I've been trying to port MS11-020, and every time I think I have it I have to pull something else in from XP -- first it was srv.sys, then i found I needed matching security features from srvsvc.dll (from KB2345886), but those require CancelIPChangeNotify() which means upgrading iphlpapi.dll, and *that* means upgrading tcpip.sys to add support for the function (and then there's more stuff to add that srvsvc.dll needs). By the time I'm done this will wind up being a micro service pack.

This post has been edited by WildBill: 07 June 2011 - 09:35 PM

[tomasz86]

I think I've become addicted to this

By the way, some time ago I found some interesting things and possible issues concerning the unofficial updates and the superseded official ones.

I've attached some parts of a conversation I had with bristols about it:

Spoiler

Quote

While editing update.inf files I found out that there are big differences between the unofficial ones and the superseded official updates. I still need to check them carefully but here is an example of what I found:

955069 is superseded by 2079403 (unofficial). If you compare the update.inf files of these two updates you can see that 955069 includes this string:

Quote

[ProcessesToRun]

"%systemroot%\system32\Regsvr32.exe /s %systemroot%\system32\msxml3.dll"

while 2079403 doesn't. I don't know if it makes any difference but it is kind of suspicious. There are also many other differences between those update.infs.

An another example:

955069

Quote

[Save.Reg.For.Uninstall]

HKLM,SOFTWARE\Microsoft\Internet Explorer\ActiveX Compatibility\{f5078f22-c551-11d3-89b9-0000f81fe221}
HKLM,SOFTWARE\Microsoft\Internet Explorer\ActiveX Compatibility\{f5078f1b-c551-11d3-89b9-0000f81fe221}
HKLM,SOFTWARE\Microsoft\Internet Explorer\ActiveX Compatibility\{f5078f1c-c551-11d3-89b9-0000f81fe221}
HKLM,SOFTWARE\Microsoft\Internet Explorer\ActiveX Compatibility\{f5078f1d-c551-11d3-89b9-0000f81fe221}
HKLM,SOFTWARE\Microsoft\Internet Explorer\ActiveX Compatibility\{f5078f1e-c551-11d3-89b9-0000f81fe221}
HKLM,SOFTWARE\Microsoft\Internet Explorer\ActiveX Compatibility\{f5078f21-c551-11d3-89b9-0000f81fe221}
HKLM,SOFTWARE\Microsoft\Internet Explorer\ActiveX Compatibility\{f5078f1f-c551-11d3-89b9-0000f81fe221}
HKLM,SOFTWARE\Microsoft\Internet Explorer\ActiveX Compatibility\{f5078f20-c551-11d3-89b9-0000f81fe221}
HKLM,SOFTWARE\Microsoft\Internet Explorer\ActiveX Compatibility\{f5078f28-c551-11d3-89b9-0000f81fe221}
HKLM,SOFTWARE\Microsoft\Internet Explorer\ActiveX Compatibility\{f5078f29-c551-11d3-89b9-0000f81fe221}
HKLM,SOFTWARE\Microsoft\Internet Explorer\ActiveX Compatibility\{f5078f26-c551-11d3-89b9-0000f81fe221}

Quote

[Product.Add.Reg]

HKLM,SOFTWARE\Microsoft\Internet Explorer\ActiveX Compatibility\{f5078f22-c551-11d3-89b9-0000f81fe221},"Compatibility Flags",0x00010001,0x400
HKLM,SOFTWARE\Microsoft\Internet Explorer\ActiveX Compatibility\{f5078f1b-c551-11d3-89b9-0000f81fe221},"Compatibility Flags",0x00010001,0x400
HKLM,SOFTWARE\Microsoft\Internet Explorer\ActiveX Compatibility\{f5078f1c-c551-11d3-89b9-0000f81fe221},"Compatibility Flags",0x00010001,0x400
HKLM,SOFTWARE\Microsoft\Internet Explorer\ActiveX Compatibility\{f5078f1d-c551-11d3-89b9-0000f81fe221},"Compatibility Flags",0x00010001,0x400
HKLM,SOFTWARE\Microsoft\Internet Explorer\ActiveX Compatibility\{f5078f1e-c551-11d3-89b9-0000f81fe221},"Compatibility Flags",0x00010001,0x400
HKLM,SOFTWARE\Microsoft\Internet Explorer\ActiveX Compatibility\{f5078f21-c551-11d3-89b9-0000f81fe221},"Compatibility Flags",0x00010001,0x400
HKLM,SOFTWARE\Microsoft\Internet Explorer\ActiveX Compatibility\{f5078f1f-c551-11d3-89b9-0000f81fe221},"Compatibility Flags",0x00010001,0x400
HKLM,SOFTWARE\Microsoft\Internet Explorer\ActiveX Compatibility\{f5078f20-c551-11d3-89b9-0000f81fe221},"Compatibility Flags",0x00010001,0x400
HKLM,SOFTWARE\Microsoft\Internet Explorer\ActiveX Compatibility\{f5078f28-c551-11d3-89b9-0000f81fe221},"Compatibility Flags",0x00010001,0x400
HKLM,SOFTWARE\Microsoft\Internet Explorer\ActiveX Compatibility\{f5078f29-c551-11d3-89b9-0000f81fe221},"Compatibility Flags",0x00010001,0x400
HKLM,SOFTWARE\Microsoft\Internet Explorer\ActiveX Compatibility\{f5078f26-c551-11d3-89b9-0000f81fe221},"Compatibility Flags",0x00010001,0x400

2079403 does not contain these strings.

Quote

I'm just wondering whether there is any difference between the way these files work under w2k and XP. I think the safest way would be to just take the old official superseded update and replace the file inside with the new version. By doing so we could just use the old update.inf with all these strings.

This is also the reason why I decided not to include any unofficial updates in the UR2. I'm going to make a separate Rollup which will be updated regularly. UR2 will contain only the official updates and won't be updated once it's finished

The problem here is that after seeing all these differences I'm not really sure that they supersede the official ones... This is also why I included all official updates in UR2, including those superseded by the unofficial ones. If you install an unofficial update which contains a newer version of the file, the strings added by the original one will still be there, only the file will be replaced.

This post has been edited by tomasz86: 07 June 2011 - 09:50 PM

[tomasz86]

Basing on this post by Inki I managed to "correct" the DirectX update and I'm working on getting the Wordpad one to work too. The point is to be able to slipstream them using HF folder.

975560 - I corrected the header so it can be slipstreamed from HF now (no problems during text setup when copying files).

Windows2000-DirectX9-KB975560-v2-x86-ENU.exe

Tested in HFSLIP and tested in text setup - no problems occur when copying files.

This post has been edited by tomasz86: 14 June 2011 - 11:25 AM

[tomasz86]

June updates are up and I wonder if this update (2518295) affects Windows 2000 Server too.

[tomasz86]

I prepared a corrected version of the Wordpad update 973904 which includes the corrected wordpad.inf. It can be slipstreamed from HF folder and no changes have to be made further.

Windows2000-KB973904-v2-x86-ENU.EXE

Please check this topic for details.

[tomasz86]

I think that 2416400 should have different filename. It's an IE6 Cumulative Update and Windows 2000 IE6 Cumulative Updates used to follow this scheme:

IE6.0sp1-KBXXXXXX-Windows2000-x86-ENU in opposite to IE5's IE5.01sp4-KBXXXXXX-Windows2000sp4-x86-ENU.

2416400's current filename is Windows2000-KB2416400-x86-ENU. Wouldn't it be better to change it to IE6.0sp1-KB2416400-Windows2000-x86-ENU? What's your opinion on this, WildBill?

This post has been edited by tomasz86: 16 June 2011 - 08:21 AM