Tomcat76

You can put MDAC_TYP.EXE (version 2.8 SP1) in the HF folder but the hotfix for that version is not supported. The reason: MDAC 2.8 SP1 adds lots of new binaries which need to be copied into the Program Files folder which is too complex (for me) to handle through an INF file; I've tried to do it but I failed. The hotfix for version 2.8 SP1 also contains files to be placed in Program Files so it's the same problem there. I even tried integrating the hotfix into the installer at one point but that failed too (a dialog comes up during "silent" install informing the user that something is being installed to which the user needs to click "OK", and in the end some binaries are not installed). HFSLIP currently makes Windows setup install MDAC_TYP.EXE at first logon for both Windows 2000 and Windows XP. I'll think about having the hotfix for version 2.8 SP1 install at first logon too; it should work but it's ugly. The hotfix for version 2.5 SP3 is fully slipstreamed. This *can* be done because all it does is update already existing files. Just don't mix the two together...

Me thinks an admin would know how to craft a nice batch file to fulfill the task without extra effort...

60608a contains the recent suggestions. Thanks...

Sorry... Yes, I have.Sorry if this sound ironic... but I'm not kidding.

HFSLIP uses a shortened version since April 23: HKLM,"SYSTEM\CurrentControlSet\Control\HAL","14140000FFFFFFFF",0x10001,16 So a standalone INF can be this: [Version] Signature = $Windows NT$ AdvancedINF = 2.0 [DefaultInstall] AddReg = AddReg.Halt [AddReg.Halt] HKLM,"SYSTEM\CurrentControlSet\Control\HAL","14140000FFFFFFFF",0x10001,16 @the_guy: thanks for the info

@Squeeto... If you want the Windows files, you can just put them in the relevant HFEXPERT subfolder. It will work in most cases. This is the part I don't like. One of the first things I do after installing an OS is disabling the Indexing Service on all partitions. It's not so much the claimed speed increase that makes me do it, but rather that I don't want the OS to think for me or do things in the background too much. Likewise, I don't allow XP to auto-defrag my hard drives (I actually do that registry edit even though I'm installing Diskeeper -- you can never be too sure, hehe).

The only problem I see in the zipped files is one related to the WU Catalog engine (IUCTL.CAB) which will be rectified in the next test release. But "tshoot.dll" is present in both DOSNET.INF and TXTSETUP.SIF so the problem doesn't lie there. Is the file present in your I386 folder?

You're right. BTW... Support for Win2K SP4 was extended to July 13, 2010 because of this new policy...

Does anyone else have this problem that XP complains the product isn't genuine at first logon and then not anymore? I can't reproduce it myself; no message is showing here.

At this point, you can maybe manually edit HFSLIP.CMD though I don't know if it'll work that early. Insert the following: %HFSLIP%\winnt32.exe /cmdcons /unattend somewhere between the line with D E F... and the line with EXIT.

Good catch. Thanks!

The IE remover was made by FDV for English versions of Windows 2000 Professional, so basically you got two problems to overcome: convert from Pro to Server and then from English to Chinese... Hopefully there are people here who have some experience with this...

Welcome It doesn't need to be installed because its files are updated. HFSLIP used to have a registry hack in place to stop Windows Update from complaining about it but I removed it in HFSLIP version 60528 because Q832483 is replaced by KB911562 (according to the information here). Yesterday I noticed that Windows Update is *still* complaining so I put a reduced version of the reg hack back in place in test version 60603a.

Oh... Was *that* the question? I'm using XP for video editing only... so no.

They aren't harmful as far as I can see and HFSLIP supports them. KB917730 I could recommend... You should decide for yourself if KB918766 is useful. KB919071 is recommendable for English systems.

Apparantly there are still problems on WinXP/2K3. So here's 60603b... I'll test it myself tomorrow.

We could go on with this forever. I prefer not to go too far away from what's reported on WU/MU. That's nice, but it's only available in English. My list is intended for all users. Thanks. I'll remove it.

Uh, what? No... Not at all. The fix is intended for every OS version. All I said was that I only tested it on 2K.

An attempt at .NET 2.0 installation at T-13. It's working on Windows 2000 with RVM's silent installer. I still didn't test it with other Windows versions. Please read the foot note in the main post. Windows XP and Windows 2003 users should just place Aserone's silent installer in the HFSVCPACK folder but I didn't want to exclude these OS's from being able to use installers that don't contain the T-13 fix. The choice is yours.

Aserone's. It has the fix built-in that was mentioned on Stebner's blog site which relies on REG.EXE. That file doesn't come stock with Windows 2000. Anyway... Check the Test releases thread in a few secs...

Nothing, then. EDIT: Ah, wait a second. I dissected the EXE and it will only work on WinXP/2K3. I hate it when they fail to mention that. So you can expect a patch from HFSLIP anyway.

I made an INF file to replace the REG ADD and REG DELETE stuff to make it Win2K-compatible. At this point, I only need to know if INF files can be installed from SVCPACK.INF or not. If not, I'll have to do it from HFSLIP.CMD.

Maybe I should start reading my changelog too

Which expand.exe did you use? What's wrong is that you didn't read the changelog

I don't know if this is the right place to ask but it's with the intention to achieve an icon set. From what I gather, Neptune is supposed to look like Windows 2000. Does anyone know if it has *more* icons in the Windows 2000 style which would complement an icon library to make Windows XP/2003 look like Windows 2000?