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