fenyo

Yes, it's OK! You don't have to re-run HFSLIP just for this. But don't forget to edit this file in HFSVCPACK folder also, if you don't want to edit it again after every run of HFSLIP.

Yeah, but i think most of the people just download the files and run HFSLIP, especially if they're just updating. And next time they wonder why HFSLIP does not slipstream updates... Just as i did. You could save many research-hours for people by setting the file on your page to dword:00000002.

Hi! Regarding this: Mim0! May i suggest you to change WindowsXP-KB2264107-x86.reg to this? : --------- Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager] "CWDIllegalInDllSearch"=dword:00000002 --------- I have three reasons for this! 1) M$ Groove 2007 (its installed with Office 2007 typical-install) gets mad with "CWDIllegalInDllSearch"=dword:FFFFFFFF Every time i start IE8, it starts with "Error loading C:\Program Files\Microsoft Office\Office 12\GrooveUtil.DLL"! But when "CWDIllegalInDllSearch"=dword:00000002, there is no problem! 2) TYPE1 hotfixes can not extract itself when "CWDIllegalInDllSearch"=dword:FFFFFFFF, error message is "file is corrupt", and HFSLIP can not slipstream MANY hotfixes this way! (as CEoCEo said also) (this whole problem took me many-many hours to discover, that "CWDIllegalInDllSearch"=dword:FFFFFFFF is the reason HFSLIP can't slipstream!!! -Yes, i've read JUST NOW the hint on your page regarding this) But again, when "CWDIllegalInDllSearch"=dword:00000002, there is no problem! 3) "CWDIllegalInDllSearch"=dword:00000002 is enough protection for hijacking DLLs with remote locations! If hijacking with local files, its too late anyways... Regards, Fenyo