Tomcat76

Just an FYI... RC4 no longer blocks KB926121. Put it in HF if you want it, exclude it if you don't want it. I don't want to enforce it.

Dawid... In general, the answer is that HFSLIP was made primarily to "satisfy" Windows Update as far as components are concerned that are part of Windows (with a few exceptions such as WMP9 for Win2K). Adding other hotfixes and programs MAY work, but there's no guarantee; HFSLIP assumes certain standards with regard to the internal composition of hotfixes and the destination of files that aren't present in the Windows source, so if there are any that need special treatment (renaming of files, non-standard locations, etc.) they won't be slipstreamed correctly. 1) If you're using the roots update from 12/13/2007, either the file you have is corrupt or something went wrong during its installation at T-13. See my hotfix list for Windows XP and remove anything that isn't listed. If this works, you can start to experiment with other hotfixes. 2) KB925877 contains many files that need special treatment. This hotfix isn't covered by HFSLIP because it doesn't show up on Windows Update. I could create an HFSLIP plugin for it if I have some time to spare, but why aren't you just using WINDOWSXP-KB925876-X86-RUS.EXE? 3) MSN/Live Messenger isn't part of Windows. If you want this handled by HFSLIP, you can extract MsnMsgs.msi from the exe and place it in HFSVCPACK_SW1.

Updated plugin and created "addon maker".

No problem. Glad it works

Can you test with the latest test release (1.7.4rc3)? This bug should be fixed. Thanks for reporting it.

See if the new test release does what you want

I found it. For some reason, I let HFSLIP add this line into HFSLPHIV.INF: HKLM,"SOFTWARE\Microsoft\Windows\CurrentVersion\Setup\OC Manager\Subcomponents","reminst",0x10001,1 This enables installation of RIS. I suppose I mistakenly saw it for a new registry entry even though the only public hotfix that contains it (KB926121) only checks for its presence (to see if RIS is installed or not). This could explain why Windows Update wants to install KB926121 on Windows 2000 Professional, which doesn't come with RIS at all. I need to see what the best solution is because KB926121 does add a registry value.

I'll check it out.

I did some comparisons and found out that HFSLIP (no matter how minimal the setup) enables installation of Remote Installation Services. Now I need to figure out why it does that. In the mean time, you can get around this by unchecking "Remote Installation Services" in the list of optional components that you're presented with during Windows setup (it normally is unchecked).

It isn't a Type 2 hotfix. It's just that it installs automatically if you pass it a switch it doesn't understand. So it would behave in the same way if you placed it in HFSVCPACK_SW1. This is the reason this script uses 7za.exe to extract it. So far, I haven't found another method. New version coming up shortly with changed description and a meaningful estimated size (3.1MB) showing for the Add/Remove Windows Components entry.

I noticed that myself when I tested 2000 Advanced Server a little while ago, but didn't pay much attention to it because I'm not too familiar with the Server editions (it could've been intentional seeing what "extras" MS are putting in with Service Packs for Server 2003). If I remember well, I also got a pop-up message asking to configure RIS after logging on. The first thing that comes to mind is that this behavior is caused by one of the newer hotfixes, which wasn't supported properly by HFSLIP 1.5.0 yet. Since I don't know which files make up RIS, this could take a while to figure out (if that's even the problem). But the hotfixes intended for 2K Server are the most likely candidates.

Here are two different scripts that handle Silverlight.exe. One is a standalone script to create an addon that is compatible with nLite and HFSLIP; the other is an HFSLIP plugin. Info: - full slipstream into source - integration into Add/Remove Windows Components - can be uninstalled and reinstalled from Add/Remove Windows Components Current limitations: - if Microsoft releases a new version of Silverlight 1.0 and you want to slipstream it into a new source, the script needs to be updated first; this is because the exact version number needs to be known and there is no usable text file inside the Silverlight.exe package that shows it - 7za.exe is needed to extract Silverlight.exe To do: - fix the limitations (if possible) Instructions to create the nLite/HFSLIP compatible addon: See the readme.txt in Addon_Maker_Silverlight10_v4.zip Instructions to use the HFSLIP plugin: 1) Create a subfolder inside the HFSLIP working folder named _EXTERNAL (if it doesn't yet exist) 2) Download Silverlight.exe from this page and place it in _EXTERNAL 3) Place 7za.exe in HFTOOLS; you can get it from 7za457.zip (7-Zip Command Line Version) from this page 4) Download HFSLIP_PRE_Silverlight10_v4.zip and extract HFSLIP_PRE_Silverlight10.cmd into HFTOOLS 5) Run HFSLIP General notes: 1) The current version of this script was made to work with MS Silverlight version 1.0.30109.0 (timestamp: 9-Jan-2008). 2) Reinstallation requires the Windows CD to be in the CD drive so the files can be copied again. 3) Installation during Windows setup and uninstallation/reinstallation is taken care of by MSSLOC.INF. You can find this file uncompressed in the new I386 folder and in Windows\inf (after installation). Changelog: v4: removed obsolete reference from MSSLOC.INF v3: uninstallation/reinstallation from Add/Remove Windows Components no longer requires a reboot (or log off and back on) v2: updated description and added estimated size (3.1MB) for the entry in Add/Remove Windows Components

SNM is not "unsupported" or "not maintained". I just posted a reply to the SNM thread that will hopefully clear things up.

HFSLIP looks for IE7 updates in this way: IF EXIST HF\IE7*-KB*.exe . . . This is mainly done to exclude IE7-WindowsXP-x86-enu.exe and IE7-WindowsServer2003-x86-enu.exe in a simple and safe way. Different methods were used in the past but they were either overcomplicated or caused trouble (such as non-IE7 hotfixes being detected on Dutch sources due to a strange bug in DOS).

Just to answer the question that's being asked over and over again.... I didn't abandon this script. It's just that I didn't find a way to silently install .NET 2.0 SP1 and .NET 3.0 SP1 aside from just repacking it. Silent .NET Maker is about creating an administrative install, patching the updates into that, and creating a new install package. This has failed until now and I haven't been able to figure out why. I recently followed someone's advise to extract the .NET 2.0 SP1 executable and to patch the contained MSI with the contained MSP files, but that share always fails to install (can't install from Netfx20a_x86.msi, can't install from vs_setup.msi and can't install from setup.exe), and I've tried many switches. Note that I didn't even try to install at T-13; my attempts only included installs on a real system so the problem is not installation at T-13 but installation in general. I've been trying that for two days straight with no meaningful result apart from the fact that I made a new 7zS.sfx file but I won't release a new version of Silent .NET Maker just for that. If there's any guide that would explain how to make an administrative install of .NET 2.0 SP1 and .NET 3.0 SP1 so that they can be easily patched with future updates *and* can be installed, please share it. @Tomalak: NDP1.1sp1-KB867460-X86.exe = SP1 for .NET 1.1 NDP1.1sp1-KB928366-X86.exe = latest cumulative post-SP1 update for .NET 1.1 NDP20-KB928365-X86.exe = latest cumulative update for .NET 2.0 SP0 So the list is complete as far as .NET 1.1 SP1 and .NET 2.0 SP0 are concerned.

Disregard the comment on windowsxp-kb905474-enu-x86.exe; it's incorrect.

jbm... There are a couple of issues. Problems: WindowsXP-KB917344-x86-ENU.exe [JScript update for IE6 with WSH 5.6] WindowsXP-KB938127-x86-ENU.exe [VGX update for IE6] Can't verify / remove to be safe: WindowsXP-KB895961-x86.exe [???] WindowsXP-KB899510-x86.exe [???] WindowsXP-KB902841-x86.exe [???] WindowsXP-KB888795-x86.exe [for MCE 2005] Updates replaced by newer updates already present in your list: WindowsXP-KB884020-x86-enu.exe [replaced by KB941644] WindowsXP-KB890046-x86-ENU.exe [replaced by KB932168] WindowsXP-KB929338-x86-ENU.exe [replaced by KB931784] Info: WindowsXP-KB899337-v2-x86.exe [replaced by KB917021-v3] windowsxp-kb905474-enu-x86.exe [could be unsupported - use "WindowsXP-KB905474-ENU-x86-Standalone.exe"] WindowsXP-KB928843-x86-ENU.exe [replaced by KB935448] WindowsXP-KB942763-x86-ENU.exe [blocked by HFSLIP - you already have HFSLIP_PRE_TZ4 in HFTOOLS] wmfdist11.exe [ignored - you can remove this] Edit: removed comment about KB905474

Just did two test installs and all is fine here. I'm even test-running two new HFSLIP addons (AMD processor update and MS Silverlight) and it seems to work. Can you ZIP your HFSLIP.LOG file?

the_guy only posts critical updates...

Not really. You could check for hard disk errors with chkdsk c: /r (replacing "c:" with the drive your HFSLIP working folder is located on) and using different media.

Just put BRANDING.CAB in the HFCABS folder. IEAK6 stores the custom settings in extra INF files in that package, and these are handled by HFSLIP if existent.

Your TXTSETUP.SIF seems fine. Have you tried removing programs from the HFSVCPACK/_SW1/2 folders?

From what I can see in your log file, you are letting HFSLIP merge DRIVER.CAB with SP2.CAB (HFSLIP default), so SP2.CAB won't exist in the new source anymore. This is reflected in the TXTSETUP.SIF that HFSLIP creates so that Windows setup doesn't look for SP2.CAB anymore. But you placed a custom TXTSETUP.SIF in the REPLACE\I386 folder. This overwrites the TXTSETUP.SIF that HFSLIP created. You should remove the custom TXTSETUP.SIF, run HFSLIP again, and then manually edit the TXTSETUP.SIF that HFSLIP created. Also, don't reuse this new TXTSETUP.SIF; HFSLIP also edits TXTSETUP.SIF for other changes (eg, copying of new files) so it is safer to always edit it manually afterwards.

Do the HFSLP***.INF files exist in the I386 folder on the new CD (or ISO)? If so, can you ZIP the new TXTSETUP.SIF and attach it here?

No, I don't have a problem with that. Go ahead.