Tomcat76

You're welcome

It isn't supported, yes. I've outlined this in the other thread. Basically, if you want it slipstreamed, I'll have to find a way to hack webfldrs.msi out of Windows setup...

This isn't something we can help you with. HFSLIP, when using the default method for IE7 handling or when using the installation from SVCPACK (IE7SVCPACK=1) slipstreams the IE7 hotfixes into the main IE7 installer, or better: the main installer is expanded, the hotfixes are expanded, then the old binaries are overwritten and a new installer is created. That's why it works and why your installer doesn't.

Circumventing WGA should not be discussed here, as outlined in the forum guide lines.

The INF file inside the original executable contains garbled characters too; that's because it's encoded in ANSI. I did a quick test with the Russian timezone update for Win2K3 on a Win2K3 SP2 source and HFSLIP copied everything exactly as in the original INF file. I believe further testing with that update to see what could be wrong is pointless because an English version of Windows probably hasn't support for Russian characters. Can you zip HFSLPHIV.INF from SOURCESS\I386 and attach it here?

As far as the font DPI goes... I found font.inf, but that file -- as far as I understand it -- is some sort of "info database" which is called whenever you change the DPI and/or the codepage. What I (or you) need to find out is how the system should be set to 120dpi so that Windows setup executes the correct section from font.inf.

A note aside... When reg editing from SVCPACK, you should know there is no "HKEY_CURRENT_USER"; anything you code for that will be translated for "HKEY_USERS". So you're basically doing the same thing twice. If a reg key doesn't take it can only be because it's being overwritten by something else during Windows setup. I'll check out some files in a Windows source to see which might be responsible for breaking your tweaks.

This smells like the registration problem that was fixed in HFSLIP 1.4.3. You are using version 1.4.1. Can you please use a recent version of HFSLIP?

It's supported. I added it to my list.

I don't know if you should know... browsewm.dll, csseqchk.dll, dw15.exe, ieshared.chm, msratelc.dll and setupwbv.dll. These are all new binaries (they don't exist in a vanilla Win2K SP4 source). But since HFSLIP has a special automatic filter for new binaries now they are no longer deleted after extraction from the CABs. However, I doubt these files are really important. HFSLIP removed them since the beginning (January 2005) and nobody has ever noted any problems. The main purpose of the test release is to see if there are any problems when those files are slipstreamed. I couldn't notice any during Windows setup, starting up IE and going to Windows Update. I'm not exactly sure, but the browsewm.dll file could be responsible/needed for the Media side bar in Internet Explorer. I need to check that on an installation that doesn't have browsewm.dll.

All versions of script*.cab are ignored if either script*.exe or *Script56*.exe are found in HF. I updated the changelog of the test release to make that clearer. You shouldn't have a problem with a network-based installation because the one file which goes in Program Files\Internet Explorer (dw15.exe, one of the 6 extra files) is copied into a temporary folder on your hard disk during txtmode setup. The differences from before are explained in the changelog: - 6 extra files are slipstreamed (5 if you also slipstream WMP9 because dw15.exe exists in both packages) - 3 new cab files are created in HFCABS to speed up consecutive HFSLIP runs

I suspect one of the hotfixes that precedes KB873339. The only new one you have is windowsmedia11-kb929399-v2-x86-intl.exe. Remove it and see if the error still appears. The two updates you mention are supported; I haven't updated my lists for the May updates yet. KB931768 replaces KB928090.

The problem lies with your list of hotfixes; it's way out of date. A few comments: 1) Support for msxmlcab.exe has been dropped many months ago; this was documented for an extended period of time in different locations 2) Please include only one KB890830 3) Please remove wmcsetup.exe, wmfdist95.exe and hotfixes for WMP8 and WMP9 when slipstreaming WMP11 When in doubt, check either the_guy's list at the top of this forum or my dynamic list (linked from my signature).

Yes, I'm aware of that. I just never got around to updating HFSLIP to remove the error messages that fly by when you exclude the cab. I'm currently discussing a thorough facelift of the IE6 slipstreaming code with TommyP. I'll mix this in with it.

@Bugs Bunny Lots of problems with the media hotfixes. Check out the main post.

v1 = March 2006 v3 = August 2006

SOURCE\I386\PRODSPEC.INI Write here: "Localization=...."

New final for make benefit user base...

Handling of Windows Internet Explorer 7

IE7? Default handling? Is it still the classic interface after a reboot?

I'll need more info, I'm afraid...

I don't count that as a positive report...

Should be fixed with test release 70511a. Will become a final after positive reports.

Found the prob. There are two, actually. 1) HFSLIP doesn't slipstream IE7 hotfixes with the new naming standard (they are ignored) 2) HFSLIP takes the newest ADVPACK.DLL. The one in the IE7 cumulative updates is newer than the one in the Roots Update, but since the latest cumulative is ignored you end up with version 6 from the Roots Update. Will fix asap...

It's possible that a network install can't find winnt32.exe. It isn't copied to the hard disk. Add this to TXTSETUP.SIF: [sourceDisksFiles] WINNT32.EXE = 1,,,,,,,,3,3 And this to DOSNET.INF: [Files] d1,WINNT32.EXE If that doesn't fix the problem I'm not really sure how to do it. I'll search around...