Super-Magician

Yes, they are mostly useless for end users. Apparently, Microsoft updates DirectX every two months. The only people that really benefit are gamers who must use those updated modules/files.

HFSLIP extracts the files in Type 1 and Type 2 hotfixes to a folder in the directory called "TEMP". It then deletes the tons of junk files and copies the necessary files to its WORK directory. Later on, when HFSLIP says "Total Slipstreaming" in the title, each file is compressed using MAKECAB and copied to SOURCESS. If you open the WORK directory while HFSLIP is in its early stages (extracting hotfixes, slipstreaming, etc.), you'll see many folders. Although in most cases most of the folders are empty, in (I think) I386E you will find the new files (from the hotfixes). If you choose compression options A-C, after HFSLIP copies the files from the SP*.CAB file, and before it CABs the DRIVER.CAB file, you'll see HFSLIP copy certain binary files to the DRIVER directory. Just a brief, technical description . For a more basic description, see TommyP's post below.

OK, thanks for all of your hard work, Siginet ! I like the idea of a beta release...but take your time .

Camarade_Tux: Look at the script ! Can't really elaborate on exactly what it does. Ask TommyP !

Updated June 9, 2006 A new redistributable containing the June 2006 DirectX for Managed Code Update was released June 8th. Microsoft DirectX End-User Runtimes (June 2006) Full Download Direct Redist Download Link (from Microsoft) Download DX Package from FileHippo.com Edit: Whoops, false alarm! There is no new d3dx9 CAB file this time. Only a(n) XACT update.

Yes, I have it too on my W2K w/SP4.

Siginet, when do you plan on releasing RC8? Great tool, by the way! Since you are making a lot of changes in this release, do you recommend repacking the whole DVD? I've made a lot of cosmetic changes to my boot menu, but I know you're implementing BCDW install of CDShell. How are you getting rid of the .dat files?

Why do you want to remove the catalog files? They are required for Windows Update to think that the hotfixes are installed. KB905474 cannot be integrated/slipstreamed because there is nothing to download. The KB article is just a informational page describing the Windows Genuine Advantage Notifications application. The application is installed/executed when Windows Genuine Advantage fails to validate a copy of Windows.Although according to the KB article you can uninstall KB905474, I do not think you can slipstream it. Also, why would you slipstream it in the first place? Does Windows Update/Automatic Updates ask you to install it? Isn't the application just a nuisance if it keeps popping up to say your Windows isn't genuine?

I believe it is mplayer2, but you should get Tomcat's confirmation.

A sidenote - how come your start menu button came out capitalized? On XP English, it isn't.

Kiki, with your SP1 CD, I'm assuming you manually slipstreamed SP2, right? Also, you need to get rid of all your extra stuff and try it once. I mean, get rid of SFCFILES.DL_ and winnt.sif, get rid of all the MSI files Tomcat mentioned, and ONLY use the hotfixes mentioned on Tomcat's page (please use this link). Tomcat - does the ERROR_REPORT.TXT (or HFSLIP.TXT in the test releases) mention if you're using HFSLIP to slipstream an SP?

To get all of those errors in a file, run HFSLIP from the command prompt as such: HFSLIP_XXXXX.CMD 2>ERROR.TXT I agree that HFSLIP_LOG.txt would be more descriptive. In the current test release, it is HFSLIP.txt in SOURCESS. There is a diagnostic mode in HFSLIP, but I don't the exact specifics for it. I believed it is/was used by tommyp/the authors.

The Tomcat addition for HFTOOLS? It's so that people who normally use a different expand.exe (in %windir%\SYSTEM32) will be able to use Microsoft's expand.exe while running HFSLIP.

I would rather put it in HFEXPERT\APPREPLACEMENT, but as I have never tested that feature, I don't know if it would be the best option.

I do understand the purpose of the error report. Personally, I just thought that the extra copy was useless. However, I see now that some people like to have that in SOURCESS also. I think renaming the error report would be OK. This would clarify the purpose of the file a bit since it's created every time HFSLIP is run. My batch file is simply to just automate the ISO creation process. It has a bit of extra stuff packed into it, but I'm not sure including it in HFSLIP would add any additional functionality.[attachment removed]

Actually, that post was intended toward Tomcat76. As he has not incorporated it yet into the script, doing so would not work.

@Tomcat76, why not have expand.exe placed into HFTOOLS instead of the root HFSLIP directory?

Some possible changes/additions to HFSLIP: 1. Remove second copy of ERROR_REPORT.TXT in SOURCESS - To me, there really is no point for this second copy. I always end up deleting it before creating my ISO file (I use my own personalized batch file). I'd like to see this removed. If you disagree, please tell me why. 2. Compress ERROR_REPORT using MAKECAB - I believe TAiN floated the idea to make HFSLIP automatically compress the ERROR_REPORT after it is created. I think this would a great addition as often people simply post the TXT file on this forum without putting it in a ZIP file first. In Internet Explorer, since there is no "word wrap" setting, clicking on the file just opens up the error report with continuous text and no line breaks, and it's hard to read. 3. Automatically run a custom batch file after HFSLIP is completed - Have the capability for HFSLIP to call up a custom batch file (i.e. custom.cmd) after the slipstreaming process. As I mentioned in the first item, I use my own CMD file to automate the ISO creation process, and I would like this to run automatically after HFSLIP is completed. Maybe something like this would work: IF EXIST custom.cmd call custom.cmd IF EXIST custom.bat call custom.bat

This thread used to be 18 pages long. What happened to all of the original posts? A little off topic: Just wondering - can a moderator edit a post but prevent the system from showing that the post was ever edited? Most edited posts will show something like this:

Just realized the following: The name of Microsoft's module in Windows XP (and 2003) is EXPAND.EXE, not EXTRACT.EXE. I believe this is also true on 2000, but I could be wrong. @einpoklum, can you check to see whether 2000 uses extract or expand? --------------------------------------------------------------------------------------------------------------------------------------------------- @TAiN: AFAIK, there is no way to check and verify the size of a file at the command prompt. Although you can produce it using DIR, it might take some time to integrate it into the script. Maybe doing this would work: 1. DIR %windir%\system32\EXPAND.EXE>TEMP.TXT 2. Find the string "15,872 bytes" (for XP's module) in TEMP.TXT (not sure of the exact command that should be used; I'm not familiar with FINDSTR) 3. If the string is found, use that EXPAND.EXE. 4. If the string cannot be found, report an error or search for EXPAND.EXE (don't think this is possible).

It is not possible for HFSLIP to distinguish between "valid" and "invalid" extract modules. However, Tomcat76/tommyp could probably add the exact path of EXTRACT.EXE into the script.

Johnny Walker, please attach your ERROR_REPORT file as outlined in the directions for posting here. Compress it into a ZIP file first.

Can you attach your ERROR_REPORT? Please compress it into a ZIP file before attaching.

Same here!