These versions are test builds. Use them at your own risk.

A new final was released on June 14. If you were referred to this thread prior to June 14, please get the final from the main thread.

HFSLIP home page

*********************************************************
I hope tomcat76 doesn't mind me [tommyp] editting this post to add in a beta test build. See attachment for beta testing in preparation for the next final. Bugfixes:
a FDV fileset fix to run an additional INF command
b ActiveX killbit fix
c FDV fileset detection file redefined
d Miscellaneous WMP hotfix fixes (several fixes actually!!!)
e Another activex killbit fix



*********************************************************

You can help by checking if the binary removal files (2000SP4.EXT, XPSP1.EXT and XPSP2.EXT) cover everything. Download dumpdupes.cmd and place it in the main HFSLIP folder (alongside the normal HFSLIP executable). Run this tool AFTER you ran HFSLIP (it namely requires a SOURCE and a SOURCESS folder to compare). If there are any duplicate binaries that can be removed, a file called EXCLUDE.TXT will be created. Let me know if it contains additional files to those that already exist in the current removal files. This program can be used to check Windows 2000, XP and 2003 sources.
Dumpdupes.cmd has one limitation: it only checks for duplicates in the current sources. This tool would have to be run again whenever new hotfixes arrive in order to ensure the list is up to date. I'll probably make another tool that outputs a full list of any driver binary that isn't supposed to be loose in I386 once I evaluated the pros and cons of both.

I used HFSLIP_60312-t1.CMD with WIN 2000 & XP

WINDOWS 2000:

1. KB 842773 (WinHTTP 5.1) doesn't integrate.

2. Failure of registration of chosen files: *cpl again (2000 & XP)
-> directx.cpl be active


WINDOWS XP:

3. KB 892130 Windows Genuine Advantage Validation Tool doesn't integrate.

4. KB 887472 (Windows Messenger) doesn't integrate.


----

5. How to download and integrate KB905474 ?

In general: when did these problems start? Which HFSLIP release is working fine?

For the *.cpl files...
60312-t1 doesn't touch *.cpl files anymore (as opposed to the last few builds) so the problem lies elsewhere. Do these come from application addons?

FYI, The .cpl issues that I mentioned in the main thread were not HFSLIP's fault.

@TAiN:
OK... Thanks. The new solution is still better, though. I'm letting HFSLIP compress *.cpl files again just like before. Only the *.cpi files are left uncompressed. There's no point in not compressing either.

@dziubek:
Just for testers... can you remove winhttp.dll from your HFEXPERT folder?

YES, no problem . I removed this file and I must create new sourcess, yes?

Also, can you rename LegitCheckControl.dll in your HFEXPERT folder to WGA1.DLL?
You do know there's a new version of LCC, right?

Yes... HFSLIP needs to be run again.

Yes I know, but I for safety downloaded this file again and renamed LegitCheckControl.dll in HFEXPERT folder.

* KB 892130 Windows Genuine Advantage Validation Tool doesn't integrate.

* KB 887472 (Windows Messenger) doesn't integrate.

* Failure of registration of chosen files: *cpl again

I used this files from addon pack:Control Panel Extensions
http://ryanvm.net/forum/viewtopic.php?t=511






dziubek

You can rename WGA1.DLL back to LegitCheckControl.dll. It was just for testers.

I believe that the *.cpl issue is actually a *.cpi issue. You should remove the ending "x" from the name of *.cpi files that have one because HFSLIP doesn't rename them. For example, "CDImagex.cpi" should be renamed to "CDImage.cpi".

As far as LegitCheckControl is concerned... If you remove the version that's in HFEXPERT, are you still being asked to download "Windows Genuine Advantage Tool"?

I'm looking into the Windows Messenger hotfix now.

Windows Messenger...

It would help if you actually included the hotfix in the HF folder. Please note the difference:

WindowsXP-KB887472-x86-plk.exe (Windows Messenger hotfix)
and
WindowsXP-KB887742-x86-PLK.exe (Stop error)

First test:
1. I used HFSLIP_60312.XX CMD (ERROR_REPORT_1.zip)

a. I added WindowsXP-KB887472-x86-plk.exe to HF folder and this hotfix was integrated.
This was my oversight, sorry :>

b. I deleted wga1.dll (LegitCheckControl.dll) in HFEXPERT,
but I still being asked to download "Windows Genuine Advantage Tool"
-->KB 892130 Windows Genuine Advantage Validation Tool doesn't integrate.
(http://download.microsoft.com/download/4/f/9/4f9730c0-2061-4028-bca9-3d6e652a5cc8/LegitCheckControl.cab)

c. I removed the ending "x" from the name of *.cpi files, but failure of registration of chosen files: *cpl it exists again.



Second test:

2. I used HFSLIP_60313a.CMD (ERROR_REPORT_2.zip)


a. KB 892130 Windows Genuine Advantage Validation Tool doesn't integrate.

b. I deleted all files from CODECS folder and i added this addons to HFAAO folder (instead of hand unpacking files and placing CODECS folder)

->>only one didn't register: CDImageGUI Control Panel Extension

Microsoft VirtualCD CPL
http://www.ryanvm.net/forum/viewtopic.php?...=asc&highlight=

Windows Update List CPL
http://www.ryanvm.net/forum/viewtopic.php?...=asc&highlight=

User Accounts2 CPL Enabler
http://www.ryanvm.net/forum/viewtopic.php?...=asc&highlight=

TweakUI Control Panel Extension
http://www.ryanvm.net/forum/viewtopic.php?...=asc&highlight=

Services and Devices CPL (Pserv)
http://www.ryanvm.net/forum/viewtopic.php?...=asc&highlight=

ResHack Control Panel Extension
http://www.ryanvm.net/forum/viewtopic.php?...=asc&highlight=

Registry Tweaker CPL
http://ryanvm.net/forum/viewtopic.php?t=15...=asc&highlight=

Bootvis Control Panel Extension
http://www.ryanvm.net/forum/viewtopic.php?...=asc&highlight=

Hoster CPL
http://www.ryanvm.net/forum/viewtopic.php?...=asc&highlight=

DirectX 9.0c CPL
http://www.ryanvm.net/forum/viewtopic.php?...=asc&highlight=

MemTest CPL
http://www.ryanvm.net/forum/viewtopic.php?...=asc&highlight=

CDImageGUI Control Panel Extension
http://www.ryanvm.net/forum/viewtopic.php?...=asc&highlight=

RVM Integrator 1.1 CPL
http://www.ryanvm.net/forum/viewtopic.php?...=asc&highlight=

Windows XP PowerPacker 1.0rc7.1 CPL
http://www.ryanvm.net/forum/viewtopic.php?...=asc&highlight=







-------
How to integrate KB905474. I found nowhere direct link to him. I in attachment send content of this hotfix downloaded from WU to: C:\WINDOWS\SoftwareDistribution\Download

KB905474.7z

dziubek

LegitCheckControl.dll...
For testing, open a Run box (in a freshly installed system), type the following and press Enter:



*.CPL files...
I see some of those need to be renamed. In that case, you should use the HFAAO method.

CDImageGUI...
I'll need to check that out. I don't see anything special about that package.

Testing HFSLIP_60313a

1. SVCPACK\HFSLIP.CMD seems to be in good order
2. On setup, there was a copy problem with HFSLP255.INF - It's not in the I386 folder

I have seen a few times lately that CPL files aren't registering. In my dealings with CPL files, if you place one in the sys32 folder, you see a control panel icon in the control panel. There wasn't any commands or anything to register it, it was just there. Am I missing something? Is there some sort of new CPL file looming out there?

An alternate way to see if the wga is slipstreamed is to open up regedit and search for LegitCheckControl.dll. Once you register this dll, it writes itself all over the registry.

usualy any .cpl file is diplayed in control panel - if not hidden by a special treatment (tweakui has a chapter to reveal them)

but you can also register an .exe file into control panel - silentdrive does so:

(the 115K .exe inside this cab copies a 40K .exe into system32 an shows it in control panel)

greetings

and dziubek: your missing file-problem: the .cpl and the .cpi MUST have the same name!!!

The cab file posted by murvun is an exe that creates something display an icon in control panel. dziubek is having this prob...
"c. I removed the ending "x" from the name of *.cpi files, but failure of registration of chosen files: *cpl it exists again."
Isn't a CPL file just a CPL file and it only gets displayed in the control panel? I never seen the need for a CPL file get registered. As a "for example" I have a directx9 CPL file in my 2k hfexpert\win\system32 folder. It gets copied over to system32, and after installation if I double click the directx9 CPL file, the directx9 properties appear. I don't register it. I think I'm missing something with this issue. [sorry if I'm hijacking this thread]

The *.cpl and *.cpi files should be placed in HFEXPERT\WIN\SYSTEM32, yes. I wrote that in my previous message but then I edited it.

@murvun:
I also thought they need to have the same name, but one of the packages is renaming CDImagex.cpi to CDImageGUI.cpi and leaves CDImage.cpl alone. The final names are not the same.

@dziubek:
Can you PM me your HFSLIPWU.INF and TXTSETUP.SIF file?

With which installation to add these files: first or second?


dziubek

The one with all the *.CPL files in their original addon packs (including CDImageGUI).

dziubek...
Forget the regsvr32 thing, but do this: start a system that you just made (one that has the LegitCheckControl problem), open up the Windows Registry and search for the following string:

17492023-C23A-453E-A040-C7C580BBF700

I just need to know if you get results or not (yes or no).

Was the latter also the case with 60310 or is that something you don't know given the path problems you were having before? Does it still happen if you only include hotfixes in the HF folder?

I sent these files to attachment.
I will send result regsvr32 in a more than ten minutes.


dziubek

Can I have links for "ConAtrib", "HashTab", "OUEngine", "OpenSub" and "SrtupMon"? There's something wrong with them.

1)

HashTab- Installed to System32\ShellExt

Open Subfolder

Office Update Engine

StartupMonitor - Installed to System32

Attributes Context Menu

According to me these addons run good.

2)I opened up the Windows Registry and searched for the following string:



inI found a few entries and also I exported two branches from Windows Registry






3)
I used following command

but it doesn't be active still in WU


dziubek

Download the attached file. When booted into the "faulty" system, right-click the file and select "Install". Then go to Windows Update.

It's a miracle HashTab, Open Subfolder, Office Update Engine, StartupMonitor and Attributes Context Menu even install right. A new test release that fixes the handling of these addons is ready to be posted but I'm waiting for the wga1.inf results first.

You do know that HFSLIP handles the original Office Update CAB, right? It's called opuc3.cab and can be placed in the HFCABS folder.

Just a quick note on my lunch break...I also had issues with the Attributes Context Menu addon, but I just removed it from my setup and worked on some other issues.

YES I know, but I on time of tests didn't place this file HFCABS folder.

After installation file inf ,all be active :-)
WU doesn't ask about renewed installation KB 892130 "Windows Genuine Advantage Validation Tool"

EDIT:

1. When I use Windows Update Agent 2.0 I have to use Windows Update v4(WU Catalog) also ?
(http://v4.windowsupdate.microsoft.com/CAB/x86/unicode/IUCTL.CAB)

2. How download and integrate hotfix: KB912945?
dziubek

OK. I'll release a new test version soon.

1) No; it's only needed for the Windows Update Catalog site

2) Try this link:
http://www.microsoft.com/downloads/details...50-ee01256aaa92
I suppose it needs to go in the HF folder.

do NOT put that in your hf folder. it WILL break your XP install. the 2003 update is the same. MS knows about this and will fix it for the next cumulative update for IE.

Maybe put it in the script to delete that file at the start?

the_guy

What file? Nobody's been talking about the FIX folder here...

I meant the HF folder. 912945 causes a lot of things to break, all because of the mshtml.dll file. You can install it fine in Windows, but do not integrate it.

the_guy

Oh, but HFSLIP has experience with that.

Try 60314b. If it's what I think it is, that version should work around the problem.

I ran 60313a yesterday and just got around to looking for any problems today. An odd problem has popped up that I never noticed before...

These are the files that I have in /WIN/SYSTEM32:
Almost all of them get copied into c:\winnt\system32...but these ones do NOT get copied over:

I have some other stuff in /WIN/CURSORS and /WIN/FONTS but they all get copied over fine.

Some of the apps in there, like notepad, may be better off in APPREPLACEMENT but I have them in there because they get removed by HFCLEANUP and I want to put them back. They are the stock files...it is just easier to have them in there while I am addressing HFCLEANUP issues than to keep deleting HFCLEANUP, re-adding the default pack, and re-deleting the files I want to keep. Does that make any sense?

Anyway, I found this interesting and thought you guys might like to see it. Cheers!

Grr... this is going to be a serious PITA.

Apparently, the boot folder needed for a multiboot has it's own TXTSETUP.SIF, which has a reference to HFSLP255.INF. I was using an old boot folder.

For my next test image, I guess I copy over the TXTSETUP.SIF to the boot folder and see how it goes.

There has got to be an easier way to build and maintain a multiboot disk. Maybe I'll try constructing my own boot folder without having to run setup, and see how it goes.

Tain, It looks like you are building your own OS using HFEXPERT. hehe. I really can't answer your Q, but I think you have to be careful that you don't overwrite an existing file using the hfexpert. What I am thinking is that after the text mode copy, the sub-installation infs are moving files from the temp location to their final spot. My advice would be to use appreplacement if the file already exists in the source. I'll have to update the hfexpert page to identify this issue.

Hi,



Does it have anything to do with the problem I mentionned with nLite ?

TAiN...
The solution depends on what the actual problem is.

1) The four files in question reside in the CD's I386 folder but they are not copied over into SYSTEM32

2) The four files in question do not reside in the CD's I386 folder or the version is wrong/different

I can figure that out myself if you send me your txtsetup.sif file...


@Camarade_Tux
No. When merging driver.cab with the SP cab, the reference to the SP cab was not removed from DOSNET.INF. It may have affected people who install from a floppy but I'm not sure of that. Either way, that's corrected now.

Ok. Thanks for the reply.

little OT:
@Camarade_Tux
What do you use theme in your OS?

dziubek

(Longhorn) inspirat from: http://crystalxp.net/galerie/en.cat.3.htm

Also check the Vista one.

And some bricopacks :
http://crystalxp.net/bricopack/en.htm

Scenario two is correct. The only file in the 'problem set' that ever exists natively is wordpad...but it gets removed by HFLCEANUP in my config. The other files are alien to stock windows.

Check the latest release, TAiN. This one allows the HFEXPERT\WIN folder (and its subfolders) to act as some kind of "backdoor" to slip in files that are removed with HFCLEANUP.

Consider this basic rule:
Do not place files in HFEXPERT\WIN that you are removing with HFCLEANUP. If you add them anyway, those files will not be removed.

This makes more sense to me and it makes HFSLIP more flexible. It's easier to add in a few files in HFEXPERT\WIN than it is to edit removal filesets. It can also help with debugging problematic filesets.

I don't mean to sound like an a$$hole here, but the name HFEXPERT was coined meaning that you need to know more than the average person about the windows installation process. If you don't know about it, then blindly using it will cause failed installs. This is why the instructional webpage is hidden in FDV's site.

Tomcat, do NOT take the liberty to change the hfcleanup/hfexpert routines. Period.

I don't really know what you mean by "routine", but if you think I switched them around then I have to say I didn't. Everything is still in order.

I always thought that the purpose of HFEXPERT\WIN was to add files, and the purpose of HFCLEANUP to remove files. This apparantly wasn't the case as TAiN found out.
IMHO, I think it's illogical that HFCLEANUP removes stuff you add through HFEXPERT\WIN. It defeats the purpose of HFEXPERT. All I did was fix this "collision"...

I'll undo it if you still want it...

TC, please undo. The way it worked before is far better. Let's say for instance you run a reducer for some file. The reducer also reduces some extra files too, in addition to installation infs (if there is one). There are too many cross-references and only asking for trouble. The only way around this would be to hardcode all the inter-relations like nlite. It's way too much work to implement and not worth the extra effort. Nlite is easier to use for reducing, and there is lots of support for it already.

Bottom line, it's a catch 22 situation. Delete first and then add -or- add first and then delete. I chose the latter, because of all the installation infs and the interdependancies. For example with Tain's case. He ran the wordpad reducer, meaning he didn't want it. He also had it in the hfexpert. So either he wants it or he doesn't want it. See what I mean? Catch 22.

Isn't the purpose of HFEXPERT\WIN to just add files to the source... no registration, no special stuff done to them?

Please note that I'm not talking about HFEXPERT\CODECS nor HFEXPERT\APPREPLACEMENT. These are "special". No installation INFs are created for files in HFEXPERT\WIN...

Did I get this wrong?

TC, I understand that it is only the hfexpert\win folder. I guess it's a matter of how the user interprets hfcleanup and hfexpert, and which came first the chicken or the egg.

I suppose you have a point though. However, it *may* break the special functionality of hfcleanup that I frequently use (maybe others too).

Perhaps you should set up a poll and ask the community which they prefer. Ask if they want to add then remove -or- remove then add. Or in other words, which takes priority, hfexpert or hfcleanup. Right now, hfcleanup has precedence. Perhaps I assumed incorrectly when I first coded in hfcleanup and hfexpert (and built reduction files that work with it).

I don't intend to break anything. Just let me know of potential issues and I'll see if they can be fixed.

I don't think that the question should be "which comes first". It's more a question of "which is allowed to undo changes of which".

In the previous releases of HFSLIP, HFCLEANUP (additionally) removes files that are added through HFEXPERT\WIN. Maybe I see it wrongly, but to me that totally nullifies the use of HFEXPERT\WIN. Why would one place files in HFEXPERT\WIN if they may be deleted?

I think that the only interaction between them which should/could be allowed is to force-add files that are deleted by one or more reduction filesets. This way, you don't need to edit filesets to try out different things.

The basic purposes are not changed: HFCLEANUP is used to remove stuff and HFEXPERT is used to add stuff.
I'm only changing a con into a pro:
Old con = HFCLEANUP removes files that are added through HFEXPERT
New pro = HFEXPERT\WIN can be used (misused) to override decisions of HFCLEANUP

How's KB912945 doing?


@dziubek
Is everything OK with CDImageGUI?