Tomcat76

@the_guy... The HfNetChk message for dxtmsft.dll on Win2K appears to be gone with the QFE files. Acknowledge. Over.

Done. Thanks...

You can't wait for a new final, do you? I'll give it another day or two. If no problems arise with the new hotfixes, you'll get the final...

I already updated my lists (web pages) with the three new security hotfixes (KB896422 is replaced on XP and 2003) after checking them out. I don't see any problem with them. I still need to check KB921181, though. Does that appear on Windows Update? Is it labeled an optional hotfix?

And lookin' better than ever... As far as I know, it's because HFSLIP takes over SVCPACK.INF and because HFSLIP doesn't know what you removed with nLite. HFSLIP assumes you're providing a standard source so it only adds stuff into TXTSETUP.SIF for new things, meaning that if nLite stripped the references from TXTSETUP.SIF for specific files that normally reside in the source, they are not copied over during setup. If I'm wrong or this is incomplete, TommyP should be able to jump in.

@TommyP... I don't think that's what TAiN meant... TAiN... That's impossible, I'm afraid, because the file types are different. These are the "laptop" files involved: Driver_Smartcard.rdv HardSupport_Battery.rem HardSupport_PCMCIA.rdv HardSupport_PCMCIA.rin At best, you can merge Driver_Smartcard.rdv with HardSupport_PCMCIA.rdv. Personally, I'm favor of the opposite. I'd for example like for "ZZZ_ENGLISH_ONLY" to be split up since it contains fonts too. When an updated fileset arrives and I don't have much time, I'd keep the font remover but ditch the keyboard layout remover.

The way it looks now, the next final should arrive faster. I don't have as much to do as in the previous months. I could release one this weekend already after testing KB916281 on Win2K and Win2K3 but I'd rather hold off until after Patch Tuesday.

dziubek... I don't know anything about WINNT.SIF. I experimented with it a couple of years ago but it's completely out of my memory now. Does everything work fine if you don't use that WINNT.SIF file? If so, I hope someone will be able to help you with that file.

passivity-- Which version of HFSLIP were you using? Can you also show me the links to the download pages of MDAC_TYP.EXE and the hotfix that you picked?

Strange. Try these: 1) Make sure you're running HFSLIP from the Administrator account 2) Remove the underscore from the HFSLIP folder 3) Disable any "protection" programs that could interfere (anti-virus, script blockers, etc.)

Awesome... It can be considered "a release candidate" as far as WinXP is concerned. It still needs to be checked if everything's fine with KB916281 on Win2K and Win2K3. BTW... Did you slipstream those Quicktime codecs in the last build?

I'm having the same problem with Windows 2003 and gave up after more than 10 attempts. I hope the documentation will be updated soon. Snippet from the README included in the hfcleanup.zip, relating to the reducer files:If you are *not* using FDV's fileset (2k only), place the above mentioned files in the FIX folder. I can't see the point of putting the reducer files in the FIX folder. They'd just get copied over into SOURCESS which isn't the point. Also, the readme says you need SFC.DLL for Win2K and SFC_OS.DLL for XP/2K3 but it's nowhere to be found on FDV's HFEXPERT page. I find this all too confusing....

Support for this was dropped a long time ago because it's too difficult to implement. The installation INF for the hotfix that contains this binary needs tons of modifications, not to mention the fact that it's in Unicode (at least the non-English versions are). You can use RVM's Update Pack which includes that hotfix.

The empty SFCFILES.DL_ from FDV just needs to be renamed. It's not a compressed file.

OK. 60703c fixes the "not a valid Windows <whatever> system image" errors... and a few others.

@Kiki... TAiN mentioned at some point that there could be copy problems related to CLVSXD.ax. I'll have to check that out when I have some time. The problem with the other three files is a question of running MODIFYPE on them. I'll get on it...

OK... It's there.

I'm downloading it now, but I don't think it's that. Your new DOSNET.INF and TXTSETUP.SIF do not contain WMPreg.inf. I found the problem. I'll post an updated version soon.

The syntax error in DOSNET.INF is in the line referencing WMPreg.inf. Where can I get this WMP11 addon? AC.cab and AC.inf (ZacamAddon_AttributeChanger) are also not properly added into DOSNET.INF. I'll try to find why this is happening.

Sorry for not getting back sooner on this.The line "Slipstreaming XPize completed" is displayed after the processing of XPize. The "File not found" message comes from somewhere else. You said also that you are no longer getting shortcuts for XPize after installation and that your HFSLIP run time went up. I suppose that, because of the variables you have set (or not set) in HFANSWER.INI, HFSLIP decided to do a slipstream of XPize instead of an SVCPACK integration. That would explain everything. You can try the latest test release which simplifies the XPize handling. The XPIZESW variable is enough to make HFSLIP do an SVCPACK integration like before. I noticed a problem in the DOSNET.INF file you posted, more specifically the reference to WMPreg.inf. Do you know which addon is adding this file?

Whoops... That one slid right past me... Updated.

WinRAR can extract 7-zip files and I suppose some other major compression programs can too. The offer is nice but the frequency at which some versions are released wouldn't make it worth the hassle. I'll use ZIP for the test releases for a while and see how things go.

This thread isn't about circumventing WGA so as far as I'm concerned it's safe. But admins have access to this subforum too and they might have a different understanding of it.

Just for the record... HFSLIP is TommyP's. He wants it in a ZIP so I'm keeping it a ZIP. The test versions are in 7z format to keep the file size down (and ultimately the bandwidth on my server). The test versions of other files used to be in 7-zip format too until I realized that ZIP does better for ultra small files, so they're now distributed as ZIPs.

My take? Once the OS has been found to be "legit", MS should butt out and stop all polling/calling home. Like this, the rightful user wouldn't have so much to complain about anymore (at least as far as WGA is concerned). My guess is that the next step would be that MS assign a unique GUID to every single WGA download. If these files are found on someone else's computer, the original downloader will be put on a black list and the OS of the other person will be invalidated (if it hasn't been already). Smells like Palladium World Domination to me...