Tomcat76

Those switches are not for extracting the hotfixes. They are used for regular installation which is not HFSLIP's purpose. Either way, I checked them out and I can't see a problem. I am currently testing Win2K.

I don't know... Do you have enough hard disk space? Did you fully disable your anti-virus program?

This is weird because HFSLIP doesn't delete files from DRIVER.CAB. Is that file present in your original DRIVER.CAB?

Is it inside the new DRIVER.CAB?

No, I need to open them up and see if everything is OK. An installation switch doesn't say anything.

Please install KB933360 first. I can still see this is KB931836.

OK... Move IE7_INST.EXE into SVCPACK. Delete HFSLPGUI.CMD and HFSLPGUI.INF. Open SVCPACK.INF and add IE7_INST.EXE right below the first occurance of HFSLIP.CMD in the [setupHotfixesToRun] section. Open TXTSETUP.SIF and DOSNET.INF, and remove every reference to HFSLPGUI.CMD, HFSLPGUI.INF and IE7_INST.EXE. Open SVCPACK\HFSLIP.CMD and remove the entire line that refers to HFSLPGUI.INF.

What's inside HFSLPGUI.CMD?

The core files are identical. The only real difference lies in the [Version] header in the INF file that installs everything but that's of no importance because HFSLIP gives configuration INF files a new [Version] header which is OS-version independent. The update.ver file is also different but that file is completely ignored. BTW... No luck so far getting this slipstreamed properly. A delayed file replace at T-13 causes Windows setup to complain, resulting in the files with version 5.1 to not be replaced at all. So it looks like placing the new hotfix in the HFSVCPACK_SW1 folder is the only option for now. This DOES require the correct version of scripten.exe, though.

It would be faster if you just ran HFSLIP again because it's too complicated to explain. Can you compress these files together? SOURCESS\I386\DOSNET.INF SOURCESS\I386\HFSLPGUI.CMD SOURCESS\I386\SVCPACK.INF SOURCESS\I386\TXTSETUP.SIF

No, but you can help. Here's what I need... 1) On a Chinese Windows XP or 2003 system, install the original KB933360 from Microsoft in the correct language (CHS or CHT) 2) Go to Start > Run, type regedit and press Enter 3) Navigate to "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Time Zones" 4) Right-click on the "Time Zones" key in the left pane and select "Export" 5) Compress the .reg file and attach it to your next post Thanks. And do mention if this is CHS or CHT.

Oy... 10 of the 11 WSH 5.7 files are just borked. Tested with Win2K+IE6 and WinXP (without IE7). Additionally, they aren't copied into DLLCACHE as a consequence. The next test release will work around this issue but I do hope MS will fix this themselves. BTW... The three package versions (2K/XP/2K3) are identical as far as HFSLIP is concerned.

I just need to test how it goes with IE6. If no errors come up, it's OK to go -- will just have to alert that it's for IE6 only. In the other case, I'll have to update HFSLIP to make a "delayed file replace".

It is supported with test release hfslip-70812a.cmd. That might explain the errors I had in setuperr.log; I slipstreamed IE7 at the same time.

That's more or less right. The SOURCESS folder will be overwritten so if you want to keep the previous SOURCESS folder you need to back it up or rename it first. I see that I forgot to update the instructions page when HFSLIP was updated to use HFSVCPACK_SW1 and HFSVCPACK_SW2 instead of HFSVCPACK_SW. You need to change that in the alternate location as well.

The first digit is not for the destination folder; it only denotes the CD the file is on and/or if the file came with a Service Pack. 1 = original file on CD1 2 = SP file on CD1 (Win2K) or TABLETPC file on CD2 (WinXP) 3 = MEDIACTR file on CD2 (WinXP) 4 = NETFX file on CD2 (WinXP) 100 = SP file on CD1 (WinXP/2K3) The destination folder is further on: WINDOWS/WINNT: filename.exe = 1,,,,,,,1,0,0 system32: filename.exe = 1,,,,,,,2,0,0 system32\drivers: filename.sys = 1,,,,,,,4,0,0 Or from your example: si3112.sys = 1,,,,,,4_,4,1,,,1,4 The folders in [WinntDirectories] are relative to the WINDOWS/WINNT folder, so "1" ("\") is the WINDOWS/WINNT folder itself.

What do you mean "junctioned"? The SOURCE folder should and can only contain the original CD source. Can you please give more info? I don't even know what you are doing or what you're trying to achieve...

It's from MDAC 2.8 SP1. The best way to avoid those problems is to take a look at the new TXTSETUP.SIF. Way down at the bottom there's a list of new files slipstreamed by HFSLIP with a [sourceDisksFiles] header; use that for the nLite ignore list.

WMP 6.4 is always present on your system even when you install WMP9, so the updates for WMP 6.4 are still needed. Did you know Windows 2000, XP and 2003 even install WMP5? (Start > Run > mplay32) The different versions of MSXML don't overwrite themselves and they work independently from each other. If you install MSXML 2, 3, 4 and 6 then you get MSXML 2, 3, 4 and 6, and not only MSXML6.

The title post shows everything you need to know. The statement "everything goes in HF\NOREG except..." is accurate. I'm even listing updates that don't appear on Windows Update, on the_guy's list and on my dynamic list. That's right. Only those two need to be placed in that folder if you want to keep Windows Update happy.

In C:\WINDOWS\WindowsUpdate.log after installing it through Windows Update or Microsoft Update.

Added WindowsXP-KB912817-v2 (COM+ Rollup Package 13) to the list. I am using Rollup 14 so forgot about this one...

the_guy already mentioned this before. You have these in your HF folder: Windows2000-KB904706-DX9-x86-ENU.exe Windows2000-KB904706-v2-x86-ENU.exe The first is a hotfix for DirectX 9 and the second is a hotfix for DirectX 7. You should only have one or the other. Since you're slipstreaming DX9, you need to remove the hotfix for DX7. Also, I don't like this too much: It might be safer if you just pressed Enter when HFSLIP asks if you are going to place the new source in a subfolder on the CD. The statement "You need to type in the \" applies to the multi boot path only. I'll update the text in the HFSLIP window to make that clearer.

I started working on it twice but it ended up nowhere because of time problems. I wanna do it but I can't promise it'll be any time soon.

The newest Flash installer is from June. I installed it on an English Windows 2000 with IE6 and it's working fine. I don't know what could be the problem on your computer.