Tomcat76

There's a new version out of the Roots Certificate Update (rootsupd.exe). The link I have in my Windows 2000 update list downloads a new file, but this one can't be extracted from DOS. So don't use it. I'm currently testing the one that Windows Update is downloading (with a GUID in the file name) on Windows XP. This one CAN be extracted from DOS. rootsupd_963ec3df48991128f4edd42c66f40f144720f759.exe Later, I'll test it on Windows 2000 and Windows 2003 as well.

WindowsUpdateAgent20-x86.exe Size: 4 601 824 bytes Timestamp: 15 June 2005 WindowsUpdateAgent20-x86.exe Size: 4 490 712 bytes Timestamp: 29/30 October 2006

That's right. I thanked you for the IDEAS in the changelog. It's intentional. I thought you wanted things to go quicker. I don't see the /R in your code sample. I only see a /VI and it's orange. The first line is useless because it doesn't strip the tabs. If I try your code on an XPSP2 source, the following files are considered "new" if they appear in a hotfix:wuau.chm noise.chs noise.cht The only thing I can (and will) do is merge the first two lines of the existing code. I normally even do that, but I was using the temporary file at some time and forgot to update the code when it was no longer necessary. The second line in your code is garbage: the resulting file is empty (0KB). I tried various alterations but nothing worked except the existing code. Also, I need the temporary file DRV.TXT for the processing of SPX.CAB and DRIVER.CAB.

Can you try without winnt.sif and sfcfiles.dl_? Your log seems to be OK at first glance except I don't know if the .REG file is OK. Try also removing all files from HFSVCPACK and HFSVCPACK_SW.

Yes, the source was already patched to SP1. I didn't install 2K3 with the new version of WUA20, but I checked the WUA20 files in SOURCESS\I386 and they were all updated (I unpacked them and checked the version numbers).

Sorry, guys. I didn't check the output in TXTSETUP.SIF when releasing the previous test release. Should be fixed now...

"Registering components" is correct. The installation of .NET 2.0 takes a while so don't give up too soon. If you already waited long enough, try a run without nLite.

The files are newer and some MUI DLLs were added, but nothing has changed place. I just tested it on 2K3 SVR and it's working fine. Try downloading the file again. Also, check that files such as wuapi.dl_ in your original source aren't newer than October 29, 2006.

Your PRODSPEC.INI is fine, but the WUA20 executable is newer. I just downloaded it and there's indeed a newer version. Lemme check if something was changed....

@whitehorses It depends on the tool if switches can be combined or not, or even "attached" to the program's name. FIND needs them separated and "detached" but FINDSTR doesn't. /R stands for Regular expression. It should only be used if there are regular expressions in your search string. Just to make something clear: there's nothing "wrong" with the time zone code that's there in the current final of HFSLIP; it's "working" and produces the same result as your code. But I admit that your sample is better; I reworked it a little and it's now used in version 70130b. Thanks

Are you slipstreaming rootsupd.exe? This is only intended for Win2K...

Thanks. Fixed in 70129b.

OK. This shows that WUA isn't slipstreamed at all. What's the size of WindowsUpdateAgent20-x86.exe? What's its timestamp? (right-click > Properties > Digital Signatures) Can you post a copy of the PRODSPEC.INI file you have in SOURCE\I386?

1) You can leave MPSetup.exe in HFSVCPACK_SW if you prefer but HFSLIP can slipstream it if you put it in the HF folder 2) KB885492 can be slipstreamed even if MPSetup.exe is in the HFSVCPACK_SW folder but it's rather pointless since it's superseded by KB917734 3) The SP5 with IE6 hasn't been tested yet for compatibility; things may go wrong with the IE hotfixes 4) USP5 isn't considered "outside the lines" if it was slipstreamed by HFSLIP 5) HFSLIP takes care of the Win2K 137GB barrier if REG.EXE is present in the HFTOOLS folder

OK... I have something that works. Just want to verify something extra with the SVCPACK install and then I'll release it.

This is odd. My source does not require activation (it's a volume-license), but when I install from SVCPACK, I encounter the three issues you listed on hfslip.org (or at least the one in User Accounts). I've started to install it from GUIRunOnce, and all those problems are gone. That is odd, yes. Everything's fine here with an SVCPACK install (IE7SVCPACK=1). I mentioned those three issues when HFSLIP slipstreamed IE7...

There are none, to my knowledge, except that you need a Windows distribution that doesn't rely on activation. I'm installing it from SVCPACK. Installing the IE7 updates after IE7 is exactly what I prepared and was about to test, but I was already afraid that problems like this would arise. A lot of the IE7 binaries are copied into a temporary location during installation and they only overwrite the old files upon a reboot. I suppose that's the reason why other sources say you can't install the updates right after IE7.

Working on it....

Actually, I just searched the entire script and can't find where that DIR/B/A-D error message could be coming from. To my knowledge it can only come from missing single quotes in a FOR loop and there aren't any of those... I'll go error message hunting again one of these days....

And if people want to create a complete installer they can use "normally"? This has been the case since .NET 3.0 is supported and it's intentional. You think it should be changed?

Yes. But don't include .NET 2.0 inside .NET 3.0 in that case (it would be pointless). The latest version of SNM excludes it by default.

.NET 3.0 installed for me. I used the same setup as you: DNF11.exe and DNF20.exe in HFSVCPACK and DNF30.exe (not including .NET 2.0) in HFGUIRUNONCE. Event Viewer shows the regular warnings about .NET 3.0 here...

@darafat .NET 3.0 breaks the WebClient service in Windows if installed at T-13 (from SVCPACK.INF). It must be installed at first GUI logon.

TommyP told me this a couple of months ago.