Tomcat76

If the OS is running fine you must be very lucky. It's been a while since I've seen such a mess. > MDAC253-KB911562-x86-ENU.exe > MDAC253-KB927779-x86-ENU.exe > MDAC271-KB911562-x86-ENU.exe > MDAC271-KB927779-x86-ENU.exe > MDAC281-KB911562-x86-ENU.exe > MDAC281-KB927779-x86-ENU.exe <--- use this one only > MDAC28-KB911562-x86-ENU.exe > MDAC28-KB927779-x86-ENU.exe If you're slipstreaming MDAC 2.8 SP1 (I hope the MDAC_TYP.EXE file is MDAC 2.8 SP1 and not an earlier version because they have the same file name), you only need the hotfixes for MDAC 2.8 SP1. KB927779 replaces KB911562 so you only need KB927779. > OE5.5sp2-KB911567-Windows2000sp4-x86-ENU.exe > OE5.5sp2-KB923694-Windows2000-x86-ENU.exe > OE5.5sp2-KB941202-Windows2000-x86-ENU.exe > oe6.0sp1-KB897715-Windows-2000-XP-x86-ENU.exe > OE6.0sp1-KB911567-Windows-2000-XP-x86-ENU.exe > OE6.0sp1-KB923694-Windows2000-x86-ENU.exe > OE6.0sp1-KB941202-Windows2000-x86-ENU.exe <--- use this one only When slipstreaming IE6, you are also slipstreaming OE6. Do not include hotfixes for OE 5.5 SP2. KB941202 is the latest cumulative update so there's no need for the other OE6 SP1 updates. > msxml6-KB933579-enu-amd64.exe I didn't know you have a 64-bit version of Windows 2000. I suggest you remove this. > StepByStepInteractiveTraining-KB923723-x86-ENU.exe Not supported to my knowledge. > WindowsMedia7-KB917734-x86-ENU.exe > WindowsMedia7-KB936782-x86-ENU.exe Not supported. HFSLIP doesn't support slipstreaming of WMP 7.1 so these hotfixes are useless. I'm not surprised Windows Update asked you to install the KB936782 hotfix for WMP9.

When IE7 is installed at first GUI logon, you need to reboot manually afterwards before you can use IE. Did you reboot?

HFSLIP 1.7.1rc4 introduces a new folder named REPLACE. Files and folders in REPLACE are copied into the SOURCESS folder near the end of the HFSLIP run, replacing any existing files. REPLACE replaces the FIX folder. You can put the updated Remote Desktop Connection Client installer in REPLACE\SUPPORT\TOOLS. For the Windows XP SP2 Support Tools, you can use the WinXP SP2 Support Tools plugin for HFSLIP I wrote some time ago, but you can now also extract the update yourself and copy the content of the update's i386 subfolder into REPLACE\SUPPORT\TOOLS so this hotfix doesn't need to be extracted each time HFSLIP is run. For the Windows 2000 SP4 Support Tools, you are advised to use the Win2K SP4 Support Tools plugin for HFSLIP if you're slipstreaming the KB911280 hotfix. This hotfix contains an updated version of the netdiag.exe binary that exists in SUPPORT.CAB, so HFSLIP would update SUPPORT.CAB with the newer netdiag.exe. But if you place SUPPORT.CAB from the Windows 2000 SP4 Support Tools update in REPLACE\SUPPORT\TOOLS, the SUPPORT.CAB which HFSLIP has created will be overwritten again. This won't happen when using the plugin.

For the Windows 2000 SP4 Support Tools: The plugin for the handling of the Windows 2000 SP4 Support Tools can be downloaded here. 1) Extract HFSLIP_PRE_2KSP4-SupportTools.cmd into the HFTOOLS folder. 2) Create a new folder named _EXTERNAL in the main HFSLIP folder. 3) Place sp4supporttools.exe in _EXTERNAL. 4) Run HFSLIP as usual. Note that this plugin is only compatible with HFSLIP 1.7.1rc4 or newer.

In Easter Egg mode, TXTSETUP.SIF from SOURCESS\I386 is appended to. If FDVFILES\IE.IN_ exists, TXTSETUP.SIF from FDVFILES is used as a base. Otherwise, HFSLIP takes it from SOURCE\I386. The content of your FIX folder is copied over near the end of the HFSLIP run, regardless of your setup.

That looks like the post install wizard didn't run (the one where you set the firewall, register with MS, etc). As TommyP suggested, do a test without nLite. Create an ISO from the SOURCESS folder and install that. If the problem remains, remove all updates which do not appear on either they_guy's or my Windows XP SP2 hotfix list and try again (without nLite).

Here it is. I hope the other languages will be supported soon...

I think that the problem is just that the file doesn't like to be renamed. I suppose nLite doesn't rename it.

I can't help much without an HFSLIP.LOG file. You are clearly doing things wrong there because most hotfixes you mention come in two versions and you need the right ones. KB939653 When slipstreaming IE6, you only need IE6.0sp1-KB939653-Windows2000-x86-ENU.exe. When not slipstreaming IE6, you only need IE5.01sp4-KB939653-Windows2000sp4-x86-ENU.exe. KB936782 When slipstreaming WMP9, you only need WindowsMedia9-KB936782-x86-ENU.exe. When not slipstreaming WMP9, you don't include any KB936782 hotfix. KB938127 When slipstreaming IE6, you only need IE6.0sp1-KB938127-Windows2000-x86-ENU.exe. When not slipstreaming IE6, you only need IE5.01sp4-KB938127-Windows2000sp4-x86-ENU.exe. KB918439 When slipstreaming aolsupp.exe AND IE6, you only need IE6.0sp1-KB918439-Windows-2000-XP-x86-ENU.exe. When slipstreaming aolsupp.exe and NOT IE6, you only need IE5.01sp4-KB918439-Windows2000sp4-x86-ENU.exe. When not slipstreaming aolsupp.exe, you don't include any KB918439 hotfix. KB904706 When slipstreaming the DirectX9 core, you only need Windows2000-KB904706-DX9-x86-ENU.exe. When not slipstreaming the DirectX9 core, you only need Windows2000-KB904706-v2-x86-ENU.EXE. This is all on my hotfix list, btw. If you mark the checkboxes for the components you wish to add (like IE6, AOL ART support, DX9 and WMP9), then the list at the bottom shows only those hotfixes you need and hides those you don't need.

@ctpooon-- Sorry, but I couldn't duplicate it yet. Everything is fine with WinXP Dutch. I will check the binaries of the CHT IE7 package and cumulative hotfix next. @geese howard-- That wizard shows "DirectX Runtime Optional Components" so I suspect it's installing the Managed DirectX stuff which HFSLIP doesn't support. See if you get an extra folder named "DirectX for Managed Code" (the name can be slightly different) in your %WINDIR%\Microsoft.NET folder after installation has completed.

Are you running nLite or a similar tool after HFSLIP? I see several problems with your log, though they shouldn't cause this to happen. You have no less than 5 cumulative security updates for IE7 and 2 "cumulative" updates for the vulnerability with VML. Many files in your HFCABS folder aren't supported either.

Well, there you go. Either the file got corrupt (try downloading it again) or you need to run modifyPE.exe on it before running HFSLIP: modifype.exe VCPack.exe -c

Is there a reason why you're letting HFSLIP slipstream Windows Installer 3.1 and then install it again in your .NET 3.5 silent installer? Remove Windows Installer from your .NET 3.5 package and try again. I can't say anything on the switches for .NET 3.5 because I haven't tested it yet.

Just as I thought. I will do some tests in my VM to see if I can somehow duplicate the problem when slipstreaming IE7. I could come up with a few test releases but that's taking things too far; I don't like to work in the dark. Can you tell me if everything is fine if you set IE7GUILOGON=1 in HFANSWER.INI? It's not so important, but it would help knowing whether it's the same problem or not. Thanks for the help

OK. Everything looks fine so at this point I can only ask to remove some files from STORAGE: DriverLanguageMap.xml hraidsk1 license.txt raidisk1 readme.txt Version.txt If that doesn't help, do a run without STORAGE.

Not feasible, because the filename differs in every language and the name of the Application Data folders is different in several languages. You want to return to English-only? Also, the "Microsoft\Internet Explorer\Quick Launch" folder path is defined as a variable in SHELL.INF, so it may differ as well.

That's correct. HFSLIP can only work with a clean source (you may patch it with Service Pack 4 beforehand if you like). Not to my knowledge. I think people have asked for this for years. If you're a gamer you're still better off with Windows XP. The 3D acceleration was greatly improved with SP4 but it's still lacking compared to Windows XP. Which ones?

I'd like to have a look at your updated TXTSETUP.SIF, HFSLIPWU.INF, HFSLPGUI.CMD, SVCPACK.INF (SOURCESS\I386) and HFSLIP.CMD (SOURCESS\I386\SVCPACK) files. Can you ZIP them in one and post the package here?

That's strange, because HFSLIP doesn't alter or even touches SUPPORT.CAB from Windows XP. Are you using my plugin for the Windows XP SP2 Support Tools update? As far as Windows 2000 is concerned, I have just finished a similar HFSLIP plugin for the Windows 2000 SP4 Support Tools update and will post it later.

That copy command must come from somewhere. Do you still have an entry for SP4.CAB in TXTSETUP.SIF or in DOSNET.INF? Have you tried removing the Read Only attribute for each file after copying them from CD? Wait... That didn't come out too well... Have you tried selecting all files in the SOURCE folder, right-clicking somewhere inside the selection, choosing Properties, unchecking the Read-only checkbox, clicking Apply, marking the radio button to "apply the changes to the selected items, subfolders and files", clicking OK, and clicking OK again? Whatever... You know what I mean...

HFSLIP hasn't changed the handling of ieframe.dll when it's slipstreamed into the source. The current test release does something special with that file, but only if the GUILOGON method is used (only then, because I haven't observed any issues myself with ieframe.dll when slipstreamed, or with the SVCPACK method). This is beginning to smell like a serious issue with the newest cumulative update. Can you please do me a favor and retest with HFSLIP 1.7.0? Don't reuse the source that HFSLIP 1.7.0 made in the past; let HFSLIP 1.7.0 make a new source again, using your current list of hotfixes. If you used SNM to create a silent installer for .NET 1.1 you should see two entries in Administrative Tools. If they aren't there, installation has failed. I can't speak for .NET 3.5 yet because I haven't been able to try it thus far. Check the RunOnce key in HKEY_LOCAL_MACHINE for anything suspicious.

Have you tried 1.6.5 again (actually ran it) to see if the problem is with HFSLIP 1.7.0+?

No, there's nothing wrong with that. TommyP only said that it's not a requirement. That's up to you. I include a silent installer for .NET 1.1 in the HFSVCPACK folder in my builds because it's the minimum required for the latest releases of SoundForge. You only need SP4; it's cumulative. HFSLIP doesn't support it, but I recently made an HFSLIP "plug-in" for the Windows XP support tools so I'll make one for this too. It is advised, yes, because nLite (or another slipstreaming tool) may remove binaries slipstreamed by HFSLIP.

Nice... Not so nice. My hotfix list shows you what is needed to keep Windows Update happy (apart from .NET Framework). Any other hotfixes you include MAY be supported, but they are usually superseded by the ones that are displayed on my list. General rule: if you come across an older security hotfix that doesn't appear on my list, it's been replaced by one or more of those that do appear. My suggestion (to anyone) is to use only the hotfixes on my list and test with that. If everything works properly, you can try to experiment with non-security updates that Microsoft doesn't show on Windows Update.Also important is that some hotfixes require special handling. This is then hardcoded into HFSLIP but it's gradually removed as hotfixes become replaced by newer ones. For example, the non-English versions of the KB896358 update contain two binaries (itss.dll and itircl.dll) which have an older creation date than those in the Rollup Update, yet they are newer; when HFSLIP is processing that hotfix and the source language is not English, itss.dll and itircl.dll from the Rollup (which was processed a little earlier) are removed. Now, if ever a hotfix is released that replaces KB896358, the special workaround that was needed for KB896358 will be removed over time. That is correct. My hotfix list doesn't show the IE5 updates anymore when you mark the checkbox for IE6. Likewise, the update for DirectX 7 is removed when you mark the checkbox for DirectX 9. As noted on that web page, you are supposed to mark/unmark checkboxes, and THEN look at the lists below. You only HAVE to have SP4. Whether your source was patched with a previous Service Pack beforehand won't make a difference (except maybe more clutter). I don't know where you got that information from but it's inaccurate. Each Windows Service Pack is cumulative.

You can put MP10Setup.exe in HF. Then you won't have to worry about that anymore