Tomcat76

I think that Microsoft has integrated those hotfix in the latest pack of directx, so isn't necessary to install. I haven't them in my hf folder, and WU doesn't tell me to install them. KB836880 is superseded for sure:qdvd.dll - KB836880 - version 6.5.1.903 - date 20-Feb-2004 qdvd.dll - dxnt.cab - version 6.5.1.904 - date 8/9-Jul-2004 I'm not sure about KB872901: qdv.dll - KB872901 - version 6.5.1.904 - date 14-Jul-2004 - size 264 KB qdv.dll - dxnt.cab - version 6.5.1.904 - date 8/9-Jul-2004 - size 309 KB Don't you just love how Microsoft decides on version numbers? Edit... The answer lies in the KB articles... KB836880: APPLIES TO: Microsoft DirectX 9.0b, when used with Microsoft Windows 2000 Standard Edition (We all know what "Standard Edition" means ) KB872901: APPLIES TO: Microsoft DirectX 9.1 Software Development Kit Update Neither is for DirectX 9.0c.

That's strange. They exist (otherwise you wouldn't be able to give them). Can you check that they are still present on the new CD? Well, look... Those files are part of WMP11 which you are slipstreaming. I suppose the codecs package you use is not up-to-date. If any of the files you include in HFSVCPACK cause Windows setup to reboot internally, the GUI stuff will be installed at T-13 (which may fail).

@450 You can start by removing the following: IE7-KB928089-WindowsXP-x86-enu.exe (superseded by IE7-KB928090) StepByStepInteractiveTraining-KB923723-x86-JPN.exe (update for StepByStep program which is not part of Windows) WindowsXP-KB928090-x86-JPN.exe (for IE6 only; this breaks slipstreaming of IE7) WindowsXP-KB929969-x86-JPN.exe (for IE6 only; this breaks slipstreaming of IE7) WindowsXP-Windows2000-Script56-KB917344-x86-jpn.exe (not needed for IE7) wmpcdcs8.exe (not for XP SP2) wmp6cdcs.EXE (not for XP SP2) messenger.msi (not supported when in HF; should be in HFSVCPACK_SW or in HFGUIRUNONCE) Apr2006_MDX1_x86.cab (ignored) Apr2006_MDX1_x86_Archive.cab (ignored) BDA.cab (ignored / for Windows 98) BDANT.cab (ignored / for Windows 2000) BDAXP.cab (not for XP SP2 / can break DirectX9 on XP SP2) dxnt.cab (not for XP SP2 / can break DirectX9 on XP SP2) wusetup.cab (ignored) What is ZP81UPDW.EXE? You have a lot of other hotfixes in your HF folder. Chances are big there may be some that are not supported.

HFSLIP needs to be used first; a clean source is expected. What language files? The IEUI2xxx.EXE files? I don't even know what they are or where you got them from. They are treated by HFSLIP as Type 2 hotfixes based on their name and it depends on what's inside of these whether they are supported or not.

HFSLIP can burn the ISO since version 1.2.0.@Sgt_Strider To extract the boot image from a Windows CD, HFSLIP looks for a drive that has the I386 folder in its root. The last one encountered is used. It doesn't really matter which version of Windows is in the I386 folder; the extracted boot images are identical (and if not identical, they are at least interchangeable -- I'm using the same boot.bin for every version of Windows).

Comparing the old DRVINDEX.INF with the new one, it seems as though DRIVER.CAB could not be extracted completely. Do you have enough hard disk space? The Windows 2000 DRIVER.CAB package is almost 200MB large when extracted. If you have WinRAR or 7-zip, also try manually extracting DRIVER.CAB to see that it isn't corrupted (right-click > "Extract to DRIVER\").

It doesn't have to because it already does... You can even call it r.exe if it makes you feel better...

Did you provide the DOSNET.INF, DRVINDEX.INF and TXTSETUP.SIF files from SOURCESS\I386 or from SOURCE\I386? They seem like the original ones to me...

- HFSLIP.LOG- DOSNET.INF (SOURCESS\I386) - DRVINDEX.INF (SOURCESS\I386) - TXTSETUP.SIF (SOURCESS\I386) Thank you

Looking at that screenshot I'd say no. I'll have a look at it.

Can you post the current log file, please (in attachment)? Small correction to what Super-Magician wrote: msxml6_x86.msi (MSXML6 SP1) does NOT necessarily need to be renamed to msxml6.msi for HFSLIP; any msxml*.msi file is handled.

HFSLIP 1.3.1: - use info on "Important things to know" page for WinXP and Win2K3 Current test release and future final: - use info on "Important things to know" page for Win2K3 - for WinXP, IE7 is slipstreamed; the IE7SVCPACK variable is ignored

I haven't any more updates planned for the next final so it should be identical to the current test release. I'm just waiting for anyone to report any new, obscure bugs that I haven't come across during my testing.

For Windows Update and Microsoft Update, you need: WindowsUpdateAgent20-x86.exe (HF) LegitCheckControl.cab (HFCABS) For Microsoft Update, you'll also need: MUWEB_SITE.CAB (HFCABS)

Slipstreaming WMP11 into Windows XP Pro is possible since HFSLIP 1.2.0. Details are on the Important things to know page. The current test release slipstreams IE7 into Windows XP. It's stable as far as I'm concerned...

The line that copies ntkrpamp.exe isn't present in that TXTSETUP.SIF file. It's like FDV either stripped out multi-CPU/core support, or he used an old TXTSETUP.SIF as a base. You can add this at the bottom of the TXTSETUP.SIF file in your SOURCESS folder but I doubt there isn't more to it: ntkrpamp.exe = 2,,,,,,,,3,3

@Kiki I see no problem with HFSLIP.CMD. It has to be the hotfixes. The errors you see for Ricks_VistaRTMFonts_AddOn_v1.1 are due to it containing an [ExtraFileEdits] section, which is not supported by HFSLIP. I also don't intend to create support for it because it's too difficult, because there would be a limit to the amount of subitems to add, and because it would only work for English sources (in the case of this addon). You have three different options: 1) Ask someone in that forum to remake the addon by using a separate INF file instead of the [ExtraFileEdits] section in ENTRIES*.INI 2) Remake the addon yourself 3) Create an INF file in HFSVCPACK yourself and ignore the errors when HFSLIP parses the addon. Ricks_VistaRTMFonts_1.1.inf [Version] Signature="$WINDOWS NT$" [DefaultInstall] AddReg=Fonts.Add [Fonts.Add] HKLM,"SOFTWARE\Microsoft\Windows NT\CurrentVersion\Fonts","%calibri%",,"calibri.ttf" HKLM,"SOFTWARE\Microsoft\Windows NT\CurrentVersion\Fonts","%calibri_bold%",,"calibrib.ttf" HKLM,"SOFTWARE\Microsoft\Windows NT\CurrentVersion\Fonts","%calibri_italic%",,"calibrii.ttf" HKLM,"SOFTWARE\Microsoft\Windows NT\CurrentVersion\Fonts","%calibri_bold_italic%",,"calibriz.ttf" HKLM,"SOFTWARE\Microsoft\Windows NT\CurrentVersion\Fonts","%segoe_print%",0,"segoepr.ttf" HKLM,"SOFTWARE\Microsoft\Windows NT\CurrentVersion\Fonts","%segoe_print_bold%",,"segoeprb.ttf" HKLM,"SOFTWARE\Microsoft\Windows NT\CurrentVersion\Fonts","%segoe_script%",,"segoesc.ttf" HKLM,"SOFTWARE\Microsoft\Windows NT\CurrentVersion\Fonts","%segoe_script_bold%",,"segoescb.ttf" HKLM,"SOFTWARE\Microsoft\Windows NT\CurrentVersion\Fonts","%segoe_ui%",0,"segoeui.ttf" HKLM,"SOFTWARE\Microsoft\Windows NT\CurrentVersion\Fonts","%segoe_ui_bold%",,"segoeuib.ttf" HKLM,"SOFTWARE\Microsoft\Windows NT\CurrentVersion\Fonts","%segoe_ui_italic%",,"segoeuii.ttf" HKLM,"SOFTWARE\Microsoft\Windows NT\CurrentVersion\Fonts","%segoe_ui_bold_italic%",,"segoeuiz.ttf" HKLM,"SOFTWARE\Microsoft\Windows NT\CurrentVersion\Fonts","%simhei%",,"simhei.ttf" [Strings] calibri = "Calibri (TrueType)" calibri_bold = "Calibri Bold (TrueType)" calibri_italic = "Calibri Italic (TrueType)" calibri_bold_italic = "Calibri Bold Italic (TrueType)" segoe_ui = "Segoe UI (TrueType)" segoe_ui_bold = "Segoe UI Bold (TrueType)" segoe_ui_italic = "Segoe UI Italic (TrueType)" segoe_ui_bold_italic = "Segoe UI Bold Italic (TrueType)" segoe_print = "Segoe Print (TrueType)" segoe_print_bold = "Segoe Print Bold (TrueType)" segoe_script = "Segoe Script (TrueType)" segoe_script_bold = "Segoe Script Bold (TrueType)" simhei = "SimHei (TrueType)" I couldn't find VisualTooltip21.zip but I could find NR_VisualToolTip_Addon_v1.1.cab (Visual ToolTip 2.1 by MrNxDmX). There shouldn't be any problems with that.

Yes, as long as its name contains "888111".

Can you be more specific? Everything seems to be fine looking at the files in the package you attached, but I need to see HFSLIP.CMD from SOURCESS\I386\SVCPACK as well to be sure. I don't see anything related to WMP11 in the setup information files as if HFSLIP didn't detect it. Did you extract everything into HF\WMP11? HFSLIP didn't see WMP11 so the cause should be found elsewhere. Never mind that you don't need WindowsMedia9-KB917734-x86-ENU.exe.As far as IE7 is concerned... If you use such an extensive list of hotfixes you should keep track of what is what... From the Overview section on the download page of WDS 3.01:Windows Desktop Search (WDS) 3.01 is a minor update to Windows Desktop Search 3.0 I think that should answer your question... Certainly not the hotfixes that HFSLIP officially supports. I get this with a fully up to date source:Windows XP Professional Build 2600.xpsp.050301-1521 (Service Pack 2) I did lots of tests with version 2.1.1 of the Sidebar addon and never had a problem with it ever since including the VAIO addon as well. Nothing has changed structurally in version 2.2.1 so I wouldn't know why it would fail.

Wow! Just saw the other thread.... Is that the amount of bugs you had to fix with IPB 2.2.2? Hats off...

@Gedrean HKLM/RunOnce. @Sgt_Strider It isn't on my agenda. Application addons are fairly easy because most people abide the rules, but there are millions of INF compositions out there used in driver packages. If I start it now, I may be able to complete it 5 years later. iTwins posted similar thoughts in the SATA integration thread.

I think xper is aware of it. The only way I could reply to your post is by copy-pasting the "Add Reply" link from a browser with which I'm not logged in to the forums to a browser with which I am logged in.

MU/WU doesn't ask to install KB905474 here. Are you sure you also didn't include an old version of KB905474 in the HF folder? That's the only time I think MU/WU would ask to update it.Try this (if you have the time)... 1) Install Windows 2) Register those DLLs you mentioned 3) Run Microsoft Update If this works, I'll update HFSLIP so those DLLs are registered automatically when KB905474 is detected in the HF folder. I've tried but if I delete that string, IE7 doesn't start and some pieces of WMP11 doesn't install... You removed it post installation or before installation? HFSLIP uses the advpack.dll method at T-13 now. For you, that would be:rundll32.exe advpack.dll,LaunchINFSection %SystemDrive%\Custom\Cursori\Aero\Install.inf,DefaultInstall RunOnceEx didn't work for me either. I had to use RunOnce.

Yup... It's mentioned in the changelog

Technically, this isn't HFSLIP but the hotfixes that are being extracted. If HFSLIP wouldn't hide the extraction dialog messages you could see what's going on. The extraction dialogs (even when hidden) take the top window position by themselves and I don't know how to stop that from happening.