Tomalak

It is, of course.I do not have the log file anymore which lists all the patches used, but if the problem still exists after my next try (maybe next week, maybe later - may take some time) I'll report it here. Note that I have used one of the test versions (latest installation is from mid of the previous week), the problem may have gone with one of the later versions or the new 1.2.2 final. Regards, Tomalak

Same here. WMP11 and all relevant hotfixes - at least one of them breaks miniplayer functionality. Kind regards, Tomalak

Yes, it does - at least on WinXP Pro. One of the many MS updates that are available in English only, but do work flawlessly on other versions also... Regards, Tomalak

Hello, according to the changelog (http://hfslip.org/changelog.html) Windows Powershell is supported starting from hfslip 1.2.0. But this package has the KB number 926139 only for the English version. For localized versions this is 926140. Is it possible to change that in the script so the non-English installers are supported too? Thanks! Regards, Tomalak

Sorry for being so dumb, but what do you mean here? Why not just call the executable and make it extract itself to a certain directory? Or are you searching for a pure DOS solution (without Windows running?) 7za only knows about 7z, zip, gzip, bzip2, Z and tar formats. You need 7z.exe to extract the installer (but this is not a standalone solution and requires other files). Regards, Tomalak

Hello all, just wanted to let you know: MS has updated the LegitCheckControl.cab again: http://go.microsoft.com/fwlink/?LinkID=39204 Kind regards, Tomalak

Hello, is it possible to keep the date and time stamps of downloaded files, i.e. have them have the same date and time as the files on the server have? Currently all files get the current (= download) date and time. This is useful to see when the last download happened, but I prefer to see the original date - it allows me for example to check for silently updated patches, or to sort them according to their provision date. If thinking about implementing this, it could be made an option, so the current behaviour can also be chosen. Thanks! Regards, Tomalak

It was not officially supported, but you showed how to do that here: http://www.msfn.org/board/index.php?s=&amp...st&p=537452 I always added that manually to the script, and it worked without problems. You can now compare that old suggestion with the new support you added to the upcoming version ;-) Regards, Tomalak

Too late :-) Reinstalled Windows today and used the way described in my first post and suggested by Tomcat76: putting the cab in the HFCABS and KB905474 in HF folder. It worked flawlessly - the newer dll was used, and I didn't have to update anything after installation was finished, i.e. WU was completely satisfied as version 1.5.0708 was present. Thanks, Tomalak

Hello all (sorry for disturbing the silence in this forum these days ;-)), in the past few weeks it was not necessary (or even counterproductive?) to put the LegitCheckControl.cab into the HFCABS folder as it was available only in version 1.5.0530, but the update KB905474 already contained version 1.5.0540. Everything went fine using just that update, not the cab file. Now a new version of the LegitCheckControll.dll is available for download (version 1.5.0708, http://go.microsoft.com/fwlink/?linkid=39204). Can somebody confirm - before I have to try it out myself in a few days - that from now on the correct way consists again of providing the update KB905474 in the HF directory _and_ the current LegitCheckControl.cab in the HFCABS directory? What will I end up with, can these two files go together? Thanks, Commander Tomalak

Hello all, I know it is a topic dealing with a piece of bloat, but anyway: will hfslip support integration of WMP11, as it does with WMP10 now? If so, when will this happen - the english beta 2 was released just a few days ago, and I think that content and format of the final version (announced for November) will not change much until then. The installer contains two files, "wmp11.exe" which is probably the player, and "wmfdist11.exe", which is the collection of the most recent codecs. If hfslip could support those soon it would be great! Thanks, Commander Tomalak

Oh, sorry, didn't know that... I obviously have to buy a new dictionary with a better description of the term "crack" - I was not aware yet that using an openly published command script to extract files out of an official MS download and registering them within the system is illegal. Ah, stop, now I see - hfslip is doing something completely different... Anyway, although I still do not understand it, I don't want to upset any one of you. You can close/delete/whatever this thread if it deems appropriate... Regards, Tomalak

Hello, may I ask why my first post has been removed? I can understand that you don't want to integrate this into hfslip to keep its original purpose, but the information I gave may be interesting for a lot of XP Home users. Absolutely nothing was illegal here, the script has even been openly published by a computer magazine. I can't see why this should be more problematic than discussing about, let's say, integrating ripped codecs without using the installer provided by the creator. Sorry, just wanted to help... Commander Tomalak

Hello all, -message deleted by mod- Commander Tomalak

Sorry, my fault - shouldn't have said "new", just meant "newer" (than the original that came with SP2). Yes, I was really referring to the one year old KB898461. Regards, Tomalak

Problem solved, see http://www.msfn.org/board/index.php?s=&amp...st&p=537288 For the future, to prevent other users from stumpling upon the same issue: is it possible to generate a warning at the beginning of a HFSLIP run if the user has no admin rights? I didn't see any error messages during the run that would've given me a hint on my mistake, even for the MSI files with the admin installs... Or they just went off screen too fast to recognize them. Thanks! Tomalak

Hello, did an install of my Win XP SP2 today, with test release 60722a. I noticed two little bugs: 1. KB898461 (new version of the package installer, 'update.exe') was not integrated successfully. IE complained about that missing update when trying to access WU. After I installed it manually, everything worked fine, and WU did not find any other missing updates - they were all slipstreamed without problems. 2. Not sure about that one, but I also tried to integrate the optional update KB914440 v6 (for diagnosing network problems). It seems to be a regular hotfix, but was not slipstreamed, too. Don't put too much effort into it, it's only a minor problem and not really an important update. Greets, Tomalak

My HFSLIP folder path does not contain any spaces, so this was not the problem. I did a reinstall today, this time with admin rights, and anything worked as expected: XPize was integrated successfully, and MSXML 3.0 SP7 also! Thanks for your great tool, I absolutely love it! Oh, by the way, this "run HFLSLIP with admin rights only, otherwise you'll have problems" thing should be documented somewhere... Regards, Tomalak

So what's the correct way then to ensure XPize is slipstreamed? Just putting the executable in the HF folder? This parameter is still documented on http://users.telenet.be/tc76/hfslip/special.html - I know it's not to be updated for every test release, but I thought it at least covers the latest stable release. I assumed the parameter is still valid... Will try to prepare a new installation CD in a few days, this time with admin rights ;-) Thanks for your help so far! Regards, Tomalak

No, didn't have the time to check it out that detailled by now. But I have to test something different first, got that idea from another thread where you answered: currently I'm not running hfslip as an administrator, only as a normal user. Maybe this has caused this problem too - I saw the messages on the screen but XPize was not able to fulfill its task... More on that later, Tomalak

Uh, no... Running it as a normal user - integration of an MSI can fail if you do not have administrator privileges? Just discovered that: MSXML 4.0 SP2 was installed correctly, MSXML6 not. User Profile Hive Cleanup Service was installed, MSXML3 was not. Okay, will do that - but not today, I'm too tired now and have to go to bed... I'll tell you about the results soon. Regards, Tomalak

Hello all, I had a strange experience with hfslip this weekend. After nLite had problems integrating XPize some time ago, I discovered that its integration is also supported by hfslip. My last install (mid of May so I used the stable version before 60528, can't remember which one it was exactly) went fine, the system came up after installation completely 'xpized' (version 4.3 oder 4.4x). This weekend I had to do a reinstall, and I did everything exactly as last time: put the executable "xpize.exe" (version 4.42 lite) into the 'HF' folder and set "FORCEXPIZESLIP=1" in the hfanswer.ini. During the hfslip run I saw some messages that indicated that the integration was indeed done ("Please wait while xpize ..." etc.), but after installation of Windows everything was just plan vanilla Windows XP SP2, without any change! Okay, I used nLite too (1.0.1, which also allows integration of IE7), but only to remove some components, and this was not different from last time when it had worked. I can't imagine how nLite would roll back the changes made by xpize and restore the original unpatched files... So I think it might be a problem of hfslip (or me, in combination with hfslip ). So what is going on here? Someone with similar experiences or an idea which magic happened here? Do you need more information? Thanks for your help, Commander Tomalak

Hello, sorry I have to come back to that old topic, just to report that slipstreaming MSXML3 SP7 did not work on my last install again (stable version 60712 of hfslip, MSI used from http://tinyurl.com/m2keb). After installation I still have the Windows default of MSXML SP5 (WinXP SP2, german edtion) - everything else (well, except XPize, see separate thread) worked absolutely flawless. It's not really that important, but something like this annoys me - is there something else I can do, or can something been further tweaked in the hfslip script? I'm willing to do some test installs in a virtual machine in the next time, if necessary. Thanks for your help! Regards, Commander Tomalak PS: Just had a look on my source - it's msxml3.dll with a date of 2004/08/04 and has version 8.50.2162.0. I have no clue what is different on my system :-(

In contrary to my opening question I'd now say: no! As I understood it's way too much effort to do, and the final version might have a completely different distribution format. The solution is - as I'm using it anyway - nLite: the newest version allows for integration of IE7 during creation of an installation CD. I was just not aware of the "integrate" option of the IE7 beta, it is not included in the official help you get with the '/?' option... Regards, Tomalak

Hello all, sorry if this has been asked before but the search does not work at the moment (at least for me) and I have not yet seen this topic here: is "hfslip" able to slipstream the new IE7 betas (final version will be similar so IMHO no extra effort is needed preparing this feature now) - or is this planned after the release of the final at the end of the year? I guess it will not be similar to the IE6 method described on fdvs website as there are no cab files, and I'm talking of WinXP (with SP2) instead of Win2000 - but the files in the installer could be extracted and given to hfslip. So how to do a manual integration? Thanks for your support, Commander Tomalak