Tomcat76

Wondering... 1) XP Home or Pro? 2) Do the programs which you put in HFSVCPACK install correctly? 3) Do you see IE7.EXE in SOURCESS\I386\SVCPACK? 4) Do you see this line near the bottom of SVCPACK.INF in SOURCESS\I386? IE7.EXE /quiet /norestart /update-no /nobackup 5) If your answer is "yes" for questions 2,3 and 4... does IE7 install properly if you remove both WMP11 and KB898543-v3?

Right. The purpose of keeping it there is so WGET can check if the online version is newer before downloading it again.

This isn't your first time, eh? I'd like to have a look at your TXTSETUP.SIF, HFSLIPWU.INF and SYSOC.IN_ files.

@TommyP Is the code in the HFCLEANUP section capable of editing Unicode versions of SYSOC.INF?

@ctpoon I downloaded the CHT version and see nothing out of the ordinary with it. It should've worked. Can I take a look at SVCPACK.INF from SOURCESS\I386? BTW... If you use the latest test release, you can change KB926139 to KB926140 in your language. @grzesiek I couldn't find a Polish version to dissect. Could that be the reason it failed? The switches are universal; they work for every language in which IE7 is made available. I also tested this completely with XPSP2 English and XPSP2 Dutch.

No; they are merged. I meant: change %W2Kcd% to "WinCD"...1="WinCD",driver.cab,,"\I386"

That never occured to me before. What you see is "no support" for the zero-width no-break space. Its name should give you a clue about its purpose. If I can't find a usable alternative, I'll just remove them.

I probably confused it for the MUI version. Sorry. Supported in the current test release...

Script updated to support automatic downloading

You can include the IE6 cumulative if you want since IE7 is only installed afterwards. Do you get that below a header "INTERNET EXPLORER 7 GOLD"?

Here's something. Don't know if it's workable or not. (updated script to support automatic downloading) 1) Download HFNETCHK.zip and extract it into a folder of your choice 2) Download wgetwin-1_5_3_1-binary.zip from this site and extract wget.exe into the same folder as above. I realize this is an older version, but this one is smaller, doesn't require additional files and does the job. Use a newer version if you know what you're doing. 3) Run hfnetchk.cmd When run, hfnetchk.cmd first checks if wget.exe is present. If it is, it will determine the OS language and present WGET with the relevant download URL for the CAB file (any language not on the KB842432 article page gets the English version). If the CAB file is already present, WGET will first check if the online version is newer. The download won't take place unless the local version is older. The script will then check for the existence of the CAB file. If it can't find one, an error message is displayed; otherwise, the XML file is extracted from the CAB file, overwriting an existing XML file. Then, HfNetChk is run using the XML file as the data source. The output file is opened automatically. This script also numbers the output files so you can run it multiple times without overwriting the older ones.

Added to the current test release

It should be initiated by SYSOC.INF... somewhere after the mini-wizard in which you enter your product key, I think. I'm not the expert here when it comes to stripping down Windows. Hopefully TommyP or FDV will be able to tell what's wrong. Something may have gotten wrong in the lines that precede the one that calls HFSLIPWU.INF. I believe HFSLIP is stripping them out as needed when using HFCLEANUP.

The only difficulty is: that reg value would be inserted before IE7 is installed. If the IE7 installer overwrites it again, I'll have to switch the order around of the programs in SVCPACK.INF so I can embed a REG ADD in HFSLIP.CMD that's executed AFTER IE7 is installed.

Any luck?

That's an interesting find, antonio_king. It could be that the extension isn't activated by default in IE7.

And your first post edit... Nobody ever said anything about the duplicates so I suppose it's allright. But it's maybe safer to remove the old one if possible. Creating a second [sourceDisksNames] section would certainly confuse Windows. But now that we're on the subject... It's maybe better to change "I386" to "\I386". According to Yzöwl, that's the correct syntax. Also, something other than %w2kcd% could be used. I know it's just a name and that it doesn't make a difference; it just doesn't really reflect the fact that this procedure isn't limited to Windows 2000. HFSLIP uses "Windows CD" in one of the other INF files. You could make "WinCD" or something similar out of that to keep it short. Does your program already cover INF files which use a number other than 1? You'd have to update the [sourceDisksFiles] section in that case too.

I can confirm this. I think it's that authorization cab but I'm not sure. I still don't have mucltui.dll in system32 after running Microsoft Update, though; neither on Win2K (normal system) nor on WinXP (virtual machine). It could be as simple as this: Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Services] "DefaultService"="7971f918-a847-4430-9279-4a52d1efe18d" [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Services\7971f918-a847-4430-9279-4a52d1efe18d] "AuthorizationCab"="muauth.cab" I'll test this tomorrow when I'm more awake...

@TAiN Yes. You just include the hotfixes that you want to include. @ivans2605 Lack of time, I'm afraid. I got my hands full with HFSLIP already. It would make things easier for me if anyone can give me a full list of hotfixes for a particular Office distribution (the first Office CD is good enough) so I can put up an "alpha release". The difficulty lies in finding out which MSP files are to be ignored. The script in its current state is only useful if the Office source has already been patched recently.

To tell you the truth, I'm not sure. It's maybe better to remove it from the list of obsolete hotfixes in the site's changelog. The Highmat update doesn't appear on Windows Update when slipstreaming WMP11. I realize that the binaries contained in the Highmat update aren't part of the WMP11 package, but that doesn't really mean anything; MS may have integrated it in the WMP11 files. Does it still appear on Windows Update when slipstreaming WMP10? I don't remember this because it's been months since I didn't include it with an HFSLIP project with WMP9 or 10.

With or without the timezone update?

BTW... I see in your sig you're using Server 2003 x64. Is that the one you're trying to update? HFSLIP doesn't yet support 64-bit versions of Windows, I'm afraid. That could be the reason for your problem.

You can try in FIX. This will update the file but I don't know if Windows setup will accept it without the CAT file. I'd put WindowsServer2003-KB916048-x86-xxx.exe in HF and don't bother with extracting it.

mucltui? That's gotta be a new file. It isn't part of any update package I know of... I suppose it's the MU equivalent of wucltui.dll.