Tomcat76

Are you installing the abandoned Microsoft Java runtime?

1) The DRIVERCAB feature handles subfolders, but everything is merged together into the "root" of DRIVER.CAB.

And all cabs are in HFCABS?

Well... HFSLIP doesn't give special care to your $OEM$ folder, but it has a partial alternative. HFEXPERT\WIN = files that go in the Windows folder and subfolders (copied to destination during text-mode copy) HFEXPERT\PROGRAMFILES = files for Program Files and subfolders (copied to destination when SYSOC.INF is parsed; long filenames and spaces supported) > Advanced features

@Kiki Better now? You may have to reload just to be sure...

Those aren't Type 2 hotfixes. HFSLIP happens to "support" those two by having them installed silently at T-13. They aren't slipstreamed.

There is nothing wrong with those files, so the only thing I can think of is that the RunOnce(Ex) programs are being blocked. This can only be caused by an error in HFSLIPWU.INF, by something you include in WINNT.SIF or by one or more of the files you include in the HFSVCPACK folder.

Type 2 hotfixes go in the HF folder, but they may not all be supported. Can you post a list of the ones you want to include?

Kiki--- The only page which has frames (iframes, actually) is the download pop-up; all others are "regular." I will add a print stylesheet one of these days which will hopefully fix your problem too. daddydave--- Thanks for the comments. I was looking at it from the "beginner to advanced user" perspective when I made the site, and I think using more than one "index" is a little too much. Also, the difference between "Advanced" and "Special" is that the former is for advanced users while the latter is about harmless extras meant for everyone. The idea is that an expert user only needs to go by the changelog. I was usually very careful about adding links to other pages on the site if a certain HFSLIP update needed more explanation, though this was a problem lately because of the lack of the "Important things to know" page. The site needs updated, and I'll see if I can improve the structure somehow too.

That's a very strange issue. I have these in SOURCESS\I386 after using HFSLIP 1.2.1: D3D8.DL_ (part of XP) d3d9.dl_ (part of XP) d3dx10.dl_ d3dx9_24.dl_ d3dx9_25.dl_ d3dx9_26.dl_ d3dx9_27.dl_ d3dx9_28.dl_ d3dx9_29.dl_ d3dx9_30.dl_ d3dx9_31.dl_ d3dx9_32.dl_ They're also in TXTSETUP.SIF. Do you mind checking again in both locations?

I disagree with that. What's the point of instructions if they are to be ignored? I could block the handling of opuc.dll if modifype.exe isn't present, but HFSLIP would have to be updated again if Microsoft fix it and I'd be ignoring users who fix it themselves.

ctpoon--- 1) Check on the fresh install (if you still have it) if there's still a folder named HFSLPGUI inside the Windows folder. 2) Are HFSLPGUI.CMD, HFSLPGUI.INF and IE7_INST.EX_ present in SOURCESS\I386? 3) Can you give me your new HFSLPGUI.CMD, HFSLPGUI.INF and TXTSETUP.SIF?

Many features involving the HFEXPERT folder require modifyPE.exe, which is why HFSLIP looks for it if it detects the HFEXPERT folder. Download modpe081.zip and extract modifyPE.exe into the HFTOOLS folder. I'll ask Oleg to make a special note of this in his instructions.

The site was updated with a new page titled "Important things to know -- please read!" with additional info on IE7, WMP11 and OPUC4 slipstreaming.

Thanks

Still calm...

Because it might break the installation of several programs that are installed at "GuiRunOnce". What's a good time frame? We don't know. It depends on the speed of the computer and the amount of programs to be installed. If you know the command, you can experiment with it yourself in SOURCESS\I386\HFSLPGUI.CMD.

@Super-Magician I suppose it should. If it contains 2.0... @the_guy I meant for the dynamic list. WMP11 needs to be extracted into HF\WMP11. Having another section "Files that go in the HF\WMP11 folder" seems a bit too much.

No. As I said in my previous post, HFSPLUG2.CMD is called when the new source is ready. So HFSLIP.CMD already has the word "EXIT" at the end. If you add anything below "EXIT", it will be ignored when it's run (at T-13).Try this: FINDSTR/VI "EXIT" SOURCESS\I386\SVCPACK\HFSLIP.CMD>>HFSLIP.CMD ECHO>>HFSLIP.CMD net user "Proprietario" /DELETE ECHO>>HFSLIP.CMD net user "MYUSERNAME" "" /ADD ECHO>>HFSLIP.CMD net localgroup Administrators "MYUSERNAME" /ADD ECHO>>HFSLIP.CMD net accounts /maxpwage:unlimited ECHO>>HFSLIP.CMD EXIT MOVE/Y HFSLIP.CMD SOURCESS\I386\SVCPACK

The patcher is coming. To the majority of the latest posters here: can you please start your own thread? Thanks.

HFSPLUG2.CMD is called almost at the end of an HFSLIP run. After that, the log file is created and then the ISO is made and burned (if applicable). So its purpose was (and apparantly still is ) to make last-minute modifications to a new source that's already slipstreamed.

The dynamic list for XPSP2 was updated roughly three hours ago. The only thing that's missing is WMP11. I'm not sure how I should incorporate that into the list yet...

I'm using the English version on a Dutch WinXP Pro. Don't see a problem there

jvidal--- With 7-zip, WinRAR, or another advanced decompressor installed, right-click on the installer file and select Extract to "wmp11-windowsxp-x86-ES-ES\". Then rename the folder to WMP11 or wmp11 (or whatever case variations you like). The reason for this ugly method is because the installer can't be extracted from DOS (gives an error). I don't know if KB898543 is needed for a Spanish Windows XP, but I'm willing to bet it is. You can always test without it if you like. You'll know you need it if you get an error message after you let Windows setup adjust the screen resolution and the post-setup wizard is bypassed. IE7 goes in HF. Everything goes in HF unless stated otherwise.

IE7 is now installed at GUI logon, meaning: when the Welcome screen appears. If you disabled the Welcome screen through a registry edit you can see it install. Since IE7 requires a reboot, you need to reboot manually after Windows has loaded the first time.