does this give us the freedom to rename files to set the order of installation? thanks!

Kiki--

Yes; that's the reason behind it.


S3pHiroTh--

In that case, I can only suggest not to use the prep tool. I'll write up a warning message in that thread.

By the way... Do you still have the problem if you use merging option D, E or F with HFSLIP after using the prep tool?

I don't know... if you want I'll do the tests, because, now, I have deleted the previous SOURCE directory (made by prep tool) because for me isn't useful, driver.cab is always recompressed. I'll do that test after I have solved (or discovered) why, if I run Windows Update, shows me 2 hotfix KB890830.

It isn't urgent. I just wanted to know as much as possible.

For those people having the DRIVER.CAB problems...

Here's a special version I'd like you to try out. It isn't supposed to shed more light on the situation; it's actually attempting to work around the problem. It force-copies new driver binaries instead of only copying those which are newer.

See that you don't get "0 files copied" while new driver binaries are processed (using merging option A, B or C). You should only get several occurances of "1 files copied", along with the names of the files.

It worked perfectly . Just a question, what do you recommend now? To continue with this source or that in my case I do not use the prep tool and start over? Would there be any problems?

This post has been edited by Neo2x: Feb 15 2007, 11:00 PM

?

Now that a more sensible workaround has been found, for the IE7 and RunOnceEx problems; are you going to revert to the previous methods used prior to the discovery of the problems?

I don't know if RunOnceEx problems were fixed because I never had them, but I can confirm the Quick Launch problem was fixed. The other issues, however, still remain:

* broken icons in Control Panel > User Accounts
* broken thumbnail view in folders

It looks like the non-public hotfix didn't make it into the new shell32 update...

For example:
Oops maybe I got it wrong then and no changes at all were made to HFSLIP due to RunOnceEx and IE7!

Not that I can remember. IE7 slipstreaming was simply dropped since HFSLIP 1.2.0 (December 7) because of all the problems. With that release and those that came afterwards, the IE7 executable is copied into the source and installed at T-13 or at GUIRunOnce (depending on what the user specifies in HFANSWER.INI), and the latest final adds support for IE7 hotfixes by slipstreaming them into the IE7 executable.

When slipstreaming IE7 into the Windows source, the missing entry in iesetup.dll is still causing an error message to pop up during Windows setup, yes; I noticed that too yesterday during the test (I made a new version of HFSLIP based on the current final that slipstreams IE7 again).

I will continue testing but I don't intend to unleash an HFSLIP version that slipstreams IE7 until at least the thumbnail issue can be fixed.

Sorry; I keep forgetting to reply to this.

It has been dropped a while ago as you noticed. I'll work on it some more but the first versions will only install the MCE hotfixes at T-13 or at GUIRunOnce.

@Yzöwl

It looks like it's possible after all. Looking at setuperr.log, I noticed 5 IE7 files (and later another one) had caused problems. I decided to use the same technique on them as on iesetup.dll and that seems to fix every problem I experienced, ie: thumbnails and User Accounts graphics.

Enjoy this release

This post has been edited by Tomcat76: Feb 18 2007, 11:50 AM

removed from the stickied topics?

hi TC! that was fast ... a new test release already (for ie7) ? ... btw, has support for TimeZoneSetup.msi & UFDSetupWizard.msi been added, as well as Windows Defender? thanks!

Uh... They should all be supported with HFSLIP 1.3.0. If the only requirement is .NET 1.1 then place them in HFSVCPACK_SW (along with a silent .NET 1.1 installer in HFSVCPACK). Otherwise, place them in HFGUIRUNONCE (with a silent .NET 1.1 installer in HFSVCPACK or in HFGUIRUNONCE; if in HFGUIRUNONCE, rename the files if necessary so that .NET 1.1 is installed before your MSIs -- they are handled alphabetically).

@Kiki, like I've been saying, WindowsDefender.msi must be placed in HFGUIRUNONCE in order to work.

i know that S-M ... i merely tried to validate because i was thinking there could some new changes too ...

Hi Tomcat I've tested this build, I have see another error in setuperr.log, the error is this:
Impossible to register OLE control C:\Windows\System32\pngfilt.dll. Error: GetProcAddress has return error 127 (impossible to find specified procedure).

Tomcat, since this is no longer sticky, can you please add an icon for this thread so it would be easier to locate? -thanks!