Tomcat76

With the edit, I moved the general HFSLIP instructions to the top and put the "All updates are optional" line in bold and "New DX9 gaming binaries" should be pretty clear too. I don't know what more I can change. Put the word "optional" at the end of every single update? Should I change every instance of "Required files:" into "Required files if you want to include this component:"? I can't change it into "Optional files:" because *that* would be incorrect....

Your script didn't work for the most part but I've kept some of the changes that I thought were nice. Thanks.

You apparantly don't understand what I'm trying to do. I'm first checking for the existence of msxmlcab.exe. It has preference because it doesn't need an admin install (ie, it just needs to be extracted which works faster). ==> if exist msxmlcab.exe If msxmlcab.exe doesn't exist, the msi will be processed. Now here's the tricky part. In order to do an admin install, I need to know the exact file name of the msi. The English version is simply called "msxml.msi" but the localized versions are called "msxmlfra.msi", "msxmlger.msi", etc. I've opted to copy the localized versions to the working folder and rename them to "msxml.msi", and then run the general command to perform the administrative installation. "msxml*.msi" = all msi files "msxml.msi" = just the English msi file "if exist msxml*.msi if not exist msxmlcab.exe" = exclude the exe, but include ALL msi's in this section (English, French, German, etc.) "if not exist msxml.msi" = exclude the English version from the renaming routine

Yes. I'm just doing that to rename msxmlfra.msi and the other non-English files to msxml.msi. I have to have the exact file name to do an admin install and I can't know which file somebody is going to use. No. That hotfix has an older version of msxml4.dll.msxml4.dll KB887606 = 4.20.9828.0 (03-Aug-2004) msxml4.dll KB832414 = 4.20.9821.0 (20-Jan-2004)

The new DX9 files are optional. What I mean with "required" and "optional" on my pages is that, if you WANT to include a specific update, these files HAVE to be used.For WinXP SP2, which comes with the basic DX9 files, the updates are optional. But if you WANT to include the updates, the "[date]_d3dx9_[number]_x86.cab" files MUST be in the HFCABS folder. See the nuance? Win2K contains neither the basic DX9 files nor the updates. If people WANT to integrate DX9, BDANT.cab and dxnt.cab are REQUIRED but the 5 new files are OPTIONAL. It's a completely different meaning. I'll update the Win2K page to separate the basic DX9 files from the 5 new files to make things clearer. EDIT: Done. Is it any clearer now?

There's another method too. Copy the CD source into (for example) D:\WINXPSRC Copy the SP2 installer into (for example) D:\ Then run this command: D:\WindowsXP-KB835935-SP2-ENU.exe -s:D:\WINXPSRC\

Try this video: http://www.ebaumsworld.com/ballmerwindows.html... When including the WM9/10 codecs but not WMP9, only the audio plays with Windows Media Player 6.4. That video uses "Windows Media Video v7" for the video portion which is not included in the WM9/10 codecs but is included in the WM6 codecs. WMP9 has standard support for it. I don't know about Media Player Classic. Try the video. If it doesn't play, you need to include the WM6 codecs.

Which command are you using to integrate SP2 and are you doing it before running HFSLIP?

[Attachment removed] Msxml4.dll, which is part of MSXML 4.0 SP2, has been renewed at least twice. The script attached to this post updates that file to the latest version and creates a new executable, msxml4.exe, which is supposed to be used as a replacement for msxmlcab.exe. When running this script from the HFSLIP folder, the updated executable is placed directly in the HF folder; otherwise, it will be located in the same folder you run this script from. This should benefit: - users who wish to have the most recent version of MS XML 4.0 - international users, as msxmlcab.exe is only available in English Procedure: 1) Download the attached file. HFSLIP users can place it in the HFSLIP folder. 2) Create a folder alongside xml4-maker.cmd called HFXTC 3) Go to this page and download either msxmlcab.exe (English only), msxml.msi (English only) or msxml***.msi (other languages) and place it in HFXTC 4) Download KB887606 for the same language into HFXTC 5) Run xml4-maker.cmd That's it. If you did this from the HFSLIP folder, you can run HFSLIP now. Note #1: The final executable, msxml4.exe, can be used as a standalone installer too; to install it silently, use the default /q switch. Note #2: Since msxml4.exe replaces msxmlcab.exe, the latter is no longer needed. When using HFSLIP, you are advised to remove msxmlcab.exe from the HF folder; HFSLIP processes files alphabetically which will leave you with the older version of msxml4.dll again as msxmlcab.exe is processed after msxml4.exe. And why would you keep two versions anyway? Note #3: This script should only be run once. Just reuse msxml4.exe for every project. Note #4: msxmlcab.exe contains only the two most essential files to support MSXML 4.0 SP2, while msxml.msi contains an SDK on top (hence its much larger size). You can regard the former as a plugin to view MSXML 4.0 content. The script attached to this post makes an updated version of msxmlcab.exe, even when using the MSI file as a starting point. This means that people who need the SDK functionality from the MSI should not use this script. Updates: 2006-01-21: Un-bloated the script a little. No functionality changes. 2006-01-21: Un-bloated the script a little more. Thanks Yzöwl for the leads. No functionality changes. 2006-01-22: Updated the description. No functionality changes. 2006-01-23: Msxml4.exe can be used as a standalone installer. No functionality changes as far as HFSLIP is concerned.

HFSLIP\HFEXPERT\WIN\SYSTEM32\

Exactly. MS have released update rollups for security fixes in the past during extended support phases. I see no reason why they'd stop doing that now...

I finally had the chance to test this one out. It's working so I'll update my list as soon as possible. Thanks.

The source of the problems I had with DX9 and WUA20 has been localized and a new version is in the making Are you still having problems, Tommy?

Whoopsie... An error in the script. I mixed up two updates (Q322011 and Q814995) at the file copy stage, which would cause an unsuccessful install if only one of those two was included. The script's been improved a little too. It's now 0.5kb less, haha.

[Attachment removed] There was 51218 and 51224 in between (maybe even more). Try the attached...

Yeah, that's what I meant. I had it in the non-slipstreamable list but realized today it shouldn't have been in there. Problem solved...

Updated Qs.cmd to support the last of the Q's. My list of SP1 updates has just been updated to include WindowsMedia8-KB817787-x86-ENU.exe in the "slipstreamable list". I had it in the non-slip list by mistake. That leaves us with KB327405 (Windows XP documentation update) and WindowsMedia-Q828026-x86-ENU.exe. It's probably better to create silent installers for both of them.

HFSLIP doesn't support some of the updates for WinXP SP1 (they're "optional" for a reason) so here's a script that handles four of these. Supported updates: Q322011_WXP_SP2_x86_ENU.exe (You cannot preview a fax in the Fax Console) Q327979_WXP_SP2_x86_ENU.exe (Game stops responding or quits unexpectedly) Q810243_WXP_SP2_x86_ENU.exe (Watch TV shows recorded by Media Center PCs) Q814995_WXP_SP2_x86_ENU.exe (Some fixes stop working after you install KB328310) 1) Create a folder called "HFXTC" in the root of your HFSLIP folder 2) Place one or more of the above updates in HFXTC 3) Download the attached Qs.zip and extract Qs.cmd into the root of your HFSLIP folder 4) Run HFSLIP_xxxxx.CMD 5) Run Qs.cmd Qs.zip

Don't know if I correctly understand what you're trying to do, but APPREPLACEMENT is meant to replace existing applications. Is the "real" mplayerc.exe present in your source (or going to be while running HFSLIP)? If not, it cannot be replaced either.

expand -r SFCFILES.DL_

Thanks. HFSLIP handles it fine with Win2K SP4 so I updated the lists.

I don't use a modified setupapi.dll and never had Win2K SP4 nor WinXP SP2 complain about a missing SPx.cab (WinXP SP1 doesn't complain about SP1.cab either).

You should use Memtest86+. It uses the core of Memtest86 but clears some of the bugs. http://www.memtest.org/ Clockgen was nice when I had the 3500. It doesn't work with X2. I'm doing everything in the BIOS now anyway so it's not a loss.

Are there people who're interested in seeing HFSLIP capable of handling Windows XP with SP1? So far, only TommyP and I have been testing betas of HFSLIP with XPSP1, and we're both having our own problems with it. TommyP (uses VMWare): IE shortcut doesn't work and Quick Launch is broken My problems (I'm doing an old-fashioned CD install): 1) wuaucpl.cpl (from Windows Update Agent 2.0) is copied over to the hard drive during txtmode setup, but is deleted and replaced by wuaucpl.cpl.manifest during GUI mode setup. This causes Windows Update to ask to install the Windows Update Agent at the first visit, making the integration useless. 2) Around T-19, I get a popup saying something to the extent of "Setup was unable to find 'glmda.ini' in (Unknown)". Glmda.ini is part of DirectX 9. Three things could happen, depending on what I do: * If I point it to a local folder which holds the extracted content of dxnt.cab, setup continues and everything is fine * If I press Cancel, the following problems arise: - the background music doesn't play during the post-setup wizard (username/activation/etc.) but the xylophone noises (or whatever they are) DO play - DirectX 9 is not installed - IE shortcut doesn't work - Quick Launch is broken - the "System Restore" tab is missing under System Properties - some menu items are missing (such as IE > Tools > Synchronize) * If I point it to the I386 directory on the CDROM (where GLMDA.IN_ is located), setup continues but asks for the location of "glmda_g.ini" later on, which is NOT on the CD. If I press Cancel there, the same problems described above occur. I've tested both SP1 as well as SP1a, modded the HFSLIP CMD, but nothing changes it. If I use BDANT.cab (intended for Win2K) instead of BDAXP.cab, DirectX 9 does get installed but I still get the prompt for the location of "glmda.ini" and the other problems are also there. Any volunteers? Anybody have an idea of what might be going wrong?