Tomcat76

Are you using nLite or some other tool after HFSLIP? Try HFSLIP 1.7.0rc1 (top of this forum). Nearly forgot: Yes, it's normal. HFSLIP.CMD is divided into two parts and they need to be executed at different times.

The plan is to have HFSLPGUI.CMD check whether Windows is still in setup or not. If it is, installation should be aborted and called again from the next RunOnce event. This may make it into the upcoming 1.7.0 but it will be there for sure in 1.7.1. Either way, HFSLPGUI.CMD is only called at T-13/T-12 if a serious error occured during Windows setup that caused it to reboot internally. For example, this could happen if you aren't careful with what you are adding into CMD files in HFSVCPACK.

The ID problems should be fixed in hfslip-1.7.0rc1. I hope that fixes all of them...

There is a bug in HFSLIP that prevents the IE level from being set properly with USP5. Actually, HFSLIP sets it to IE6 but it's reset to IE5 just a bit later. I'm currently working on HFSLIP 1.6.6 RC7 which will also fix this problem. I'll keep you posted.

HFSLIP takes the files in xpsp2_binarydrop if IE6 is being slipstreamed. Seeing that you also have issues with the IE6 cumulative update, I believe the problem is that HFSLIP doesn't recognize the IE6 cabs in HFCABS. Can you zip HFSLIP.LOG and attach it here?

I see the problem. I'll fix this asap. Edit: fixed

@Nanasi3 Thanks for reporting this. Can you verify that it's fixed in 1.6.6 RC5? @Glowy Do you have the same problem with RC5? Try rebooting your system and do a chkdsk too.

Those files are renamed to support long filenames. They are given their original name back during the copy process way in the beginning of Windows setup (txtmode setup). You should see something like this in TXTSETUP.SIF when you open it in Notepad: HFGUI1.EXE = 1,,,,,,,999,0,0,"Whateverfileinhfguirunonce.exe" I should note that executables and MSI files in HFGUIRUNONCE should not contain spaces; they are only allowed for REG files, CMD files and INF files.

WindowsMedia6-KB925398 is a security hotfix which applies to every OS that HFSLIP supports. Installing WMP9/10/11 does not remove or overwrite WMP 6.4 (mplayer2.exe) or WMP 5 (mplay32.exe). It's at version 2, though (WindowsMedia6-KB925398-v2-x86-PLK.exe). WM9Codecs.exe is not supported. Why would you want this anyway when you're slipstreaming WMP11? wmp6cdcs.exe is only for Windows 2000. I will have WM9Codecs.exe blocked for all OS's and wmp6cdcs.exe blocked for non-2000 systems in the next release. You are also missing an update which is crucial if you want to slipstream WMP11. This file is on my hotfix list and more info on it can be found on the Important things to know page of the HFSLIP site. I suggest you compare the content of your HF folder with my hotfix list (after checking IE7, WMP11, and such in the "Update your Windows XP configuration" section) and remove every hotfix that isn't listed -- including XPize47b2Lite.exe. Don't forget the special hotfix for WMP11.

pallemn... You say you're using Windows 2000. Unless that's Advanced Server Limited Edition or Datacenter Server Limited Edition, it's 32-bit. So you can remove the 64-bit driver references from your STORAGE.INI file. It looks fine otherwise. Why are you pressing "S"? You should just install Windows as if the controller is already supported...

Are you referring to the %ProductIdCode% variable? I don't know how to get this working in a slipstreaming context as it requires the iecustom.dll file and the ProductIdCode needs to be acquired from it like this: "CustomFunction,iecustom.dll,GetProductIDCode". The lack of the "ProductIdCode" doesn't prohibit IE7 from functioning properly, but the next version of HFSLIP will make it blank (no value).

I'm not suprised. Please see what I wrote above. If I begin with this I won't finish until the next patch Tuesday. You have multiple cumulative MSXML4 updates, multiple cumulative MSXML6 updates, multiple versions of the Malicious Software Removal Tool, updates for both Windows Media Player 10 and 11, and hotfixes for both IE6 and IE7. And that's just by taking a quick look at your list.Please use my hotfix list.

Windows XP SP2 already has DirectX 9.0c so slipstreaming the DX9 core is blocked if the SP level is 2 or higher. You can have HFSLIP slipstream the additional binaries that are included in the bi-monthly redists. See my list for info on which are supported. You will need the latest test release of HFSLIP if you want the x3daudio*.dll files properly supported.

If you include more hotfixes than those which appear on my list, you should do your homework. Start by checking the knowledge base article associated with each update. windowsxp-kb824151-x86-deu.exe -- not for XPSP2 windowsxp-kb841356-x86-deu.exe -- not for XPSP2 windowsxp-kb841533-x86-deu.exe -- not for XPSP2 windowsxp-kb867282-x86-deu.exe -- obsolete cumulative update for MSIE6 windowsxp-kb871250-x86-deu.exe -- not for XPSP2 windowsxp-kb873333-x86-deu.exe -- OK, but superseded by KB912817-v2 or KB922668 WindowsXP-KB873339-x86-DEU.exe -- OK (on my list) windowsxp-kb873376-x86-deu.exe -- not for XPSP2 windowsxp-kb883939-x86-deu.exe -- obsolete cumulative update for MSIE6 windowsxp-kb885250-x86-deu.exe -- superseded by KB914389 WindowsXP-KB885835-x86-DEU.exe -- superseded by KB914389 and KB924270 together WindowsXP-KB885836-x86-DEU.exe -- OK (on my list) WindowsXP-KB886185-x86-deu.exe -- OK (on my list) WindowsXP-KB887472-x86-deu.exe -- OK (on my list)

Alright. Keep us posted

Thanks. Greek should now be supported That file is now part of the package and will be slipstreamed if the OS is Windows XP or Windows Server 2003. There are two versions present (one for XP and another for 2K3); the correct one is selected automatically.

Yes, it updates 5 files that are already part of the Windows XP/2K3 source.

Try the latest test release (71103a). This should add support for your original PRODSPEC.INI. The 3rd time zone package for HFSLIP doesn't have Greek language files. Most likely, the wrong language was installed.

Hmm... This could be difficult. Do you mind putting PRODSPEC.INI in a ZIP and attaching it here? I need to do some testing which I can't do from the image. BTW... Would you be interested in having the 3rd cumulative time zone update supported for Greek systems? I posted instructions in the beginning of this thread.

Can you show me the complete content of your original PRODSPEC.INI?

Oh my God! You have truly SAVED my life! For all these years I have been updating the Windows CD by hand... file by file. And now there is a way to do this FASTER than installing Windows plus going to Windows Update... and with marginal user interaction! I vote for pinning this topic! I am confident it will help so many people like us.

There are things you can't do at T-13. For example, switching to "Windows classic" through a .REG file at T-13 will cause Themes to be broken. And if you disable System Restore in the same way, you won't be able to enable it again.

You should remove msxml2.msi; it is not intended for Windows XP. Can you ZIP and attach your HFSLIPWU.INF file?

That could happen if files failed to register at T-13. Do you have errors in C:\WINDOWS\setuperr.log after installing the new Windows source?

HFSLIP only works properly on a clean source so it needs to be run first.