Tomcat76

If you want a per-folder listing you can use my dynamic update list. The link is in my signature.

For Windows 2000, Windows Defender requires gdiplus.dll. Put gdiplus_dnld.exe in HF and 7za.exe from the "7-Zip Command Line Version" package in HFTOOLS. This used to be covered through an external file (HFSPLUG1.CMD) but was merged into HFSLIP 1.0. I removed the HFSPLUG1.CMD info from the site but apparantly forgot to provide info on GDI+ elsewhere. I'll rectify this.

De-stickied at the request of Bilou_Gateux

I never checked how other tools handle it, but it can't be done from DOS if there are exotic characters in the original Unicode file; they'll get replaced by gibberish.ëàèùµéçõůšœûø

Yes; the space is the reason. I'll see if I can add support for REG, CMD and INF files with spaces in their name in the next version.

nothing. It's just a string. That's the datatype of the registry entry. Those FirstEntry LastEntry values have different datatype than the ones which store the customizations. This leaves in First/LastEntries.Oh, OK. Didn't see that, heheh. I'll put it in Gimme a bit more time to try to figure out what it is... What about this? IF EXIST WORK\I386E\ASMS ( IF EXIST SOURCESS\I386\ASMS ECHO Processing ASMS&XCOPY/EHY WORK\I386E\ASMS SOURCESS\I386\ASMS >NUL RD/Q/S WORK\I386E\ASMS ) Talk about efficiency...

@kenlau That log is from HFSLIP 1.2.2 which doesn't support IE7 hotfixes so it's pretty useless in trying to solve your problem @whitehorses What does "0x1" do? You mean that other compression cycle? What do you mean about "existant"?There was a typo in the accompanying (REMmed out) text. I corrected it. Search for "EXISTENT" in the current test release. Haha. You're not a top grader, eh? It's based on code by Yzöwl so you should ask him...

I did vote for her, but she looks 20 on that picture.

I was gonna quote you on "Yes, but I want to wait for SP1" but as I read on I realized there were other items I also barely recovered from. Great poll, but add in an older woman next time, will ya?

Right. I could have HFSLIP parse that INF section line by line (like it's done with the addons) but that would take too long on your Sempron I could be wrong, but isn't that extra work? You're creating an extra temporary file. Yeah. I didn't update that small bit yet. I'll change it to this: FOR /F %%I IN ('DIR/B/A-D/ON WORK\I386E') DO ( ECHO Processing %%I IF EXIST SOURCESS\I386\%%I (COPY/Y WORK\I386E\%%I SOURCESS\I386 >NUL) ELSE ( MAKECAB /D CompressionMemory=%COMPMEM% /D CompressionType=LZX WORK\I386E\%%I /L SOURCESS\I386 >NUL ) )Less lines... I also updated the text a few lines lower (EXISTANT instead of EXISTENT) which I corrected in the 64-bit version draft but not here...

From experience, I can only speak for HFSLIP. With that program it goes in the HFGUIRUNONCE folder (supported in the current test release).

Nowhere. HFSLIP only copies into WINDOWS/WINNT and Program Files...

It can't be slipstreamed. I think they told you that in the other thread

@whitehorses I added your proposed changes except the /R switch. Is it really necessary? A dot is a wildcard and it's working fine without that switch for me.

@Kiki 1) I only have HFSLIP do what the information files in Siginet's addons tell it to do. As far as I can see, the result should be that a CMD is executed during Windows setup that takes care of everything. 2) WMP11 is slipstreamed. You don't get WMP11 when clicking on "Windows Media Player"? 3) KB911564 is not related to any version of WMP in particular so you still need it when slipstreaming WMP11. 4) There's something fishy about the Sidebar addon. When I include it (RAR will be supported in next version), I get an error message at every login saying that Sidebar couldn't start because some file could not be found. The strange thing is: this file is not part of Windows, it's not included with the addon, and the forum post you linked to doesn't say anything about it either. Crazy stuff. I also tested the other two addons you mentioned and they are OK as far as I can see. 5) Do a proper run with the version I'll upload later and then see if you still get that error message. 6) Do they require a specific version of .NET? I see in your log that you are installing .NET 1.1 and .NET 2.0 in one go; this will cause other programs to think .NET 2.0 isn't installed yet before rebooting. If that's the case, either put those MSIs in HFGUIRUNONCE, or remove .NET 1.1 (or put .NET 1.1 in HFGUIRUNONCE). 7) Same as 5). Removing "Dynamic.DST...2" from the search string will cause those lines which contain "FirstEntry" and "LastEntry" to be stripped as well. They should not be stripped. You can put them in HFSVCPACK directory... the results is the same.Not really. "HKEY_CURRENT_USER" doesn't exist at T-13; any such entries will be converted to "HKEY_USERS" by Windows setup. And if you add entries at T-13 they may get overwritten again by applications that are installed later on.New version underway.

@whitehorses It's intentional. The "FirstEntry" and "LastEntry" lines are supposed to be included in HFSLPHIV.INF. @Kiki 1) HFSLIP supports the OEMBIOS addons -- at least, if I interpret them correctly. I personally doubt it you can use these on a self-assembled PC. 3) Important things to know 4) I'll check out those three addons 5) EXEs in HFSVCPACK_SW are installed with the /Q:A /R:N switches

Done. Yes. It does for me. No; the normal Windows Update site.

It's optional, just like the one for Win2K.

Is it possible that the original was in Unicode?

The one for 2K (with the GUID number) is working on Win2K. I updated the dynamic Win2K list.

OK. The one for XP/2K3 doesn't work on Win2K. But there's apparantly another link; this is what Windows Update downloads on Win2K: rootsupd_fe44934fd80dd11fec2f0f9b24431658a4f6d589.exe This one can be extracted from DOS, thankfully. Testing now....

The binaries from the hotfixes are slipstreamed into the IE7 installer. That's why the changelog says that only hotfixes that replace IE7 binaries are supported, by the way.

Yeah, that's what I said. But the new file in the "old link" can't be extracted from DOS so it can't be used. I tested the one with the GUID number on XPSP2 and it's working. I'm now going to test Win2K...

If you use the latest test release, you just need to dump the IE7 hotfixes in the HF folder. If your version of Windows requires activation, you need to have it installed at first logon (don't specify IE7SVCPACK in HFANSWER.INI) and you must activate before IE7 is installed.

I don't get 4 extra entries without the /R. I'll check out the Italian version of the timezone update -- maybe I'm missing something. I don't understand what do you mean by that. It works for me on w2k, both during HFSLIP process, and if I just run this command from commandline.That's nice, but the TXTSETUP.SIF of my XPSP2 has a tab right after the three file names I mentioned (between the file name and the = sign). Your code does not remove that extra tab so I also get it in FULLSRC.TXT. A list of the new and updated files is made after that, and then existing file names are stripped out (so they don't get referenced again in TXTSETUP.SIF and DOSNET.INF) by comparing the two lists. If a hotfix updates those three files, those extra tabs in FULLSRC.TXT will cause DOS to think those files are completely new and as a consequence add duplicate entries into TXTSETUP.SIF and DOSNET.INF. Sorry I mistyped it:FINDSTR /I /B /R "[^=]*\." SOURCE\I386\DRVINDEX.INF>>WORK\FULLSRC.TXT (red is the color) Alright. I'll test this in a bit. The msxml*r.dll files aren't supposed to be registered to my knowledge. At least, they produce errors when registered.