Tomcat76

Works fine here (Win2K). Did you put WindowsInstaller-KB893803-v2-x86.exe in the HF folder and not HF\NOREG or HF\BASIC?

The FIX folder is intended for files which exist in SOURCE\I386. So winntbbu.dl_ and syssetup.dl_ are in the right place.

I meant: do both of those files exist in the new source after running HFSLIP?

I have a couple of questions and remarks... 1) I'm not sure if these two files are copied over fine into the new source. Are they? Active Directory Cookbook For Windows Server 2003 & Windows 2000.ch_ Mastering Active Directory For Windows Server 2003, 3rd Edition.ch_ 2) Please remove all the duplicates from the HF folder. 3) Please remove all *x64* DX9 "gaming" cabs from the HFCABS folder, at least those for *D3DX* since HFSLIP does not ignore these. 4) When slipstreaming the DX9c core (BDAXP.cab and dxnt.cab) into Server 2K3 SP2, you should use the latest test release of HFSLIP. The current final is not optimized for DX9 slipstreaming into 2K3 SP2 (only 2K3 Gold and SP1). 5) Rename the .NET executables in the HFSVCPACK folder to something that doesn't have a combination of a numerical character and an underscore at the beginning. This seems to confuse Windows setup. You may try experimenting with quotes in TXTSETUP.SIF after running HFSLIP but this is untested. 6) What's the purpose of flash.exe if you're slipstreaming swflash.cab? 7) Is there a difference between Java.exe and JRE6.exe?

Can you ZIP your HFSLIP.LOG?

Honestly... I don't know. I never tried it

What's with the thumbs up? Can you compress HFSLIP.LOG and attach it here? Have you tried NOT modifying your OS? Maybe files which are modded are replaced by HFSLIP again as you slipstream hotfixes.

If the OS is Hebrew I'm afraid changing the Localization string is the only option you got. Norwegian versions of Windows are also labeled "English" but they contain extra text in Norwegian so HFSLIP can base itself on that. But your PRODSPEC.INI can't be discerned from an English PRODSPEC.INI.

SNM does not remove the CSetupMM directory and I don't plan to do so. But I'll look into updating it with the latest files.

CaNgO-- xpsepsclangpack-x86-tr-tr-langpack_c98aae608a413fb0e3a916a5d49dad7d9a4f327f.exe (may be renamed to xpsepsclangpack-x86-tr-tr-langpack.exe but doesn't have to be) is slipstreamed provided you include the Turkish language pack. This action is not shown in the DOS box. If Windows Update doesn't offer it after installing DNF30.exe, it was slipstreamed correctly. grunz-- SNM already does that. The "ErrorReporting" key is even restored when installation has finished. As far as the rest of your post is concerned... Can we please keep it on topic? Thanks.

Can you ZIP PRODSPEC.INI and post it here? Thanks.

LegitCheckControl.cab is to be placed in HFCABS. WUA is multilingual. HFSLIP will slipstream the proper files if your source contains the expected information in PRODSPEC.INI (Localization=Hebrew).

You shouldn't have this problem if you follow the guide lines in the two pages I linked to before. You can place silent .NET installers in HFSVCPACK or in HFGUIRUNONCE.

Please remove .NET Framework from the HF folder; it doesn't belong in there. HFSLIP - Basic how-to Dynamic hotfix list for Windows 2000 SP4 (make your changes under "Update your Windows 2000 configuration" and THEN look at the lists at the bottom)

Changed in test release 70721a. The main WMP INF file is now copied over with its original name.

Your "CD Install Path" is a space. You may want to fix that.

You may want to double-check that the source files you copied from CD are not read-only.

Can you compress (zip) TXTSETUP.SIF from SOURCESS\I386 and attach it to your next post? Thanks.

Could be because of the change in the handling of WMP in test release 70720b. Did you use that version? Test release 70721a should fix that.

I thought it was the same problem but I see the difference now. I don't have experience with patching .NET before making an administrative installation so I can't comment on why it doesn't work.

It's compressed, as 450 said. I will look out for another version but I won't use one that's as large as 122KB. The bigger the SFX file, the bigger the outputted installers. But this is really a lost battle. If I find one which isn't flagged as a trojan, it may so in a few months. A lot of anti-virus software manufacturers are just lazy and flag all files compressed with a certain method as a trojan if one virus maker happened to use the same compression method for his virus, instead of checking what's inside of it.

ponghy The uninstallation issue is worked around if you use Silent .NET Maker (even its first version) via a registry hack: [HKEY_CLASSES_ROOT\Installer\Products\D6461317C3DC4F04799BDCE9E42626FE] "PackageCode"="FE8E5CFB041CA454B974EE7CA3A4BAF3"

OK... Thanks.

Parallels (like MS Virtual PC) probably uses a generic audio driver which isn't affected by the problem that's corrected in KB935448. I can't explain it otherwise. I'd say place the hotfix in HFSVCPACK_SW1, unless you don't mind fooling around with InstallRite (or similar program). If you're including IE7 I wouldn't worry about KB933566. The XML file that's downloaded from the MS server doesn't have info for IE7 (yet) so it assumes you have IE6. The file "browseui.dll" was updated in KB933566 for IE6 but it does not exist in KB933566 for IE7 so the warning you see is to be ignored.

Try test release 70720b. It strips out any reference to wmp11.inf from the WMP INF files.