tommyp

Yea, I've been over my head lately and no time (or desire) to code hfslip more. If you have Q's for the reduction files and/or syntax, drop me a line. Once you get the reduction files all set, can you post a general thread with all of the files? I kind of like one stop shopping.

In the previous thread you started, I suggested that you verify your hotfix list. I'll have to ask you again since you didn't do anything. You have a few outdated and replaced ones. Check here: http://www.msfn.org/board/index.php?showtopic=62177 (My favorite) http://www.msfn.org/board/index.php?showtopic=58747 http://www.msfn.org/board/index.php?showtopic=31886 The reason why you may not see some hotfixes not listed is because (it's technical so bear with me) the update infs that are part of the hotfix delete the replaced/outdated hotfix registry entries. This is why you aren't seeing some of the hotfixes. The nirsoft program only displays entries in the registry (just like wu4). IMO you are far better off with using an alternate hotfix checker as described on the "how to use hfslip" webpages as opposed to registry-only checkers. Implementation of WMP10 isn't the greatest, but it's a shot on my part. If the "check for updates" bugs you that much, put the wmp installer in the HFSVPK_SW folder instead. FYI, there are FAR better media players than WMP. If it's missing a reg key, report back with the key so I can check it out and fix. The nlite Q... Once you get all your hotfixes figured out, give nlite a try again and post back with your error_report file. I really can't help without it. Also, give NLITE some time too. Have you tried NLITE on a barebones XPSP2? Last point, a recommended fix doesn't mean mandatory fix.

FDV explained it better than I could. HAHA. The beta posted in the first posting has Bilou's ideas implemented. The beta also works for whatever SP you are running. Just a side note, the changes really only affect XP and 2003, W2K is left unchanged for now (read you need sp4 for w2k). Please give it a try and report back.

Thanks for the pointers Bilou. I found a solution. Within the next day or so, grab the new HFSLIP and give it a test ride with xpsp1. I also adapted the script for what I think 2003 server should be.

Yep, it's the RVM integrator. The problem with his integrators is that it overwrites what you have (thus obliterating what HFSLIP did). HFSLIP modifies what you already have. That is the big difference between the two. If you really need things slipstreamed, you may want to read up on the HFEXPERT folder. You can slipstream lots of goodies with it, and you can slipstream only what you want.

Can I take a look at your sysoc.inf or sysoc.in_ file? Also, are you sure you need all those hotfixes? Were any of those updated since the initial release?

OlegII. Glad to see you back from your trip. We sort of missed you and your modding that you help us out with. Who wants to be the keeper and maintance person for the reduction files?

@Wela - I updated the first post for where the file needs to go. Put it in the FIX folder and you're good to go. If you are using FDV's fileset, you do not need to add a setupapi.dl_ file.

I don't mean to rain on parades, but where exactly is the "How To" part of this thread?

Sorry dude. I have no plans on making hfslip work with xpsp1. As mentioned in my first post, life calls and HFSLIP isn't on the top of my priorities. One thing you can *try* is to edit hfslip so that BANDAIDXP routine is same as BANDAID2K3. In other words, delete the XP part and replace it with the 2k3 part. No guarantees if it will patch everything correctly, but I guess it's worth a shot.

HFSLIP holiday party? Count me in.

Don't forget that you could always have HFSLIP automatically parse files for you during installation. Right now, it can parse cmd, reg and inf files at t-13. You just need to craft up the files and put them into the HFSVPK folder.

Have you tried the latest revision? It's not in the svcpack.inf file?

Throw the wmcsetup file into the HF folder and it will be integrated via svcpack. Sorry, I don't plan on slipstreaming this one. If someone wants to write up the code to slipstream it and test it, I'll be more than happy to add it to the script.

@x-pert - Can you attach your error_report file and your winnt.sif files?

I don't mean to beat a dead horse, but my hfslip'd 2k does not have msi issues. Are you sure it's an HFSLIP issue? Or is it an NLITE issue? The reason I ask is that HFSLIP does not tinker with the policies via inf files. Also, I'd like to make hfslip more universal and error-free. Thanks!

FDV, be careful on your runonce lines, you had a bit too many runonce's lined up. Sort of like you were studdering. HAHA. The 11,nameofdll.dll has one too little commas. If you are looking for various ways to register things, open up hfslipwu.inf and take a look. I already had issues with registering dlls a while back and incorporated the fixes. BTW, dumb Q, but I just tested an old version of fdv's fileset (the one with the updates that I mentioned a few days back), and I am not getting the es.dll, txfaux.dll, msiprov.dll and slayerui.dll errors that x-pert is getting. How can I join the party and get those errors too? What am I doing wrong or right?

Oleg and others, HFSLIP was reposted to fix the above. It works great with the FDVs beta. Glad it all works. Now we can concentrate on ripping more stuff out!

Assorted notes & summary for the Desktop Icon and QL issue: 1. Desktop icon: The W2K rollup forces more down our throats for IE than I previously thought. The "standard" installation makes IE-related changes whether or not you have IE installed. As a favor M$FT did for us, part of this rollup is to force the IE icon on your desktop (amongst other cr@p). When HFSLIP is run, an inf is made from the rollup and is named hfslip10.inf. When the sourcess folder is installed, the hfslip10.inf is parsed, which forces to show the IE shortcut on the desktop. The workaround for now is to remove the "Product.Add.Reg.Professional," from the 5th line from the top. It was my err, and I have redid the script to correct this. FDV, can you check the hfslip10.inf to see if anything needs to get ripped out from it? 2. QL: The trick here is to rip the file copy stuff out of axant5.inf and put it back into ie.inf where it belongs. This comes with a catch because setup files need to be tweaked so no setup missing file complaints occur during installation. Here's what to do... a. mod the txtsetup.sif --->add/correct this iexplore.lnk = 1,,,,,,,,3,3 iexplore.exe = 1,,,,,,,,3,3 ;1 b. mod the layout.inf ----->add/correct this (FDV, this answers my question I had for you a few months back) iexplore.lnk = 1,,,,,,,,3,3 iexplore.exe = 1,,,,,,,,3,3 c. mod the axant5.inf ----->Remove the stuff related to placing the QL shortcut and the iexplore.exe files. The lines remove are these: DestID's section: file.copy.ql = 16419,"Microsoft\Internet Explorer\Quick Launch" file.copy.ie = 16422,"Internet Explorer" file.copy.ql section: iexplore.exe.lnk file.copy.ie section: iexplore.exe There's lots of other junk that can be removed too. BTW, keeping this INF squeeky clean is good because nlite removes it. d. ie.inf.... Some tweaks as follows so ie.inf copies the files over. ----> add new FDVPATCH section [FDVPATCH] AddReg = interface,iepatch,addreg DelReg = delreg ----> Add new destinationdirs section [DestinationDirs] file.copy.ql = 53,"Application Data\Microsoft\Internet Explorer\Quick Launch" file.copy.ie = 16422,"Internet Explorer" ----> Add to the defaultinstall sections (last line is new) [DefaultInstall] AddReg = interface,iepatch,addreg DelReg = delreg CopyFiles = file.copy.ql,file.copy.ie [DefaultInstall.NT] AddReg = interface,iepatch,addreg DelReg = delreg CopyFiles = file.copy.ql,file.copy.ie ----> Add file copy section [file.copy.ql] iexplore.lnk [file.copy.ie] iexplore.exe e. hfslipwu.inf --> replace the FDV section with this: HKLM,"Software\Microsoft\Windows\CurrentVersion\RunOnceEx\ZZZ",990,0,"RunDll32.exe %11%\AdvPack.Dll,LaunchINFSection %10%\inf\ie.inf,FDVPATCH" ....note to FDV, the FDVPATCH section is run last to fix the registry bloat from hotfixes. The above results in a w2k less IE, no IE desktop shortcut, with an IE QL shortcut to the fake iexplore.exe redirector. Steps a thru d are updates to FDV's fileset; step e is an hfslip fix. I mailed FDV the updates to his beta and the new hfslip. If anyone needs advance copies for their enjoyment, PM me with your email addy and I'll send them to you. FDV, Now that I got this working, do you think you can refine the windows explorer so it doesn't do the stupid large file icons? The large icons remind me of fisher price.... I'm a big boy that doesn't like bloat cartoons for files.

Can you repost the above in English? My German is a bit rusty.

If you need msxml4 for XP, follow the same directions for 2000 (I'll send some updates to FDV for updating). I'm not sure of the jscript update for xp though. A quicky check from a SP2 source has jscript at 5.6.0.8820, the jscript version inside the scripten.exe hotfix (the same as the one for IE6/2K) is 5.6.0.8825. Is this a recommended or critical update at this time? I haven't slipstreamed it with XP to verify functionality. Do you have a link for the 5.6 jscript update? Remember, with the jscript updates, it's language and version dependant, so you'll have to get the one for your language and OS and version of IE. Be careful if slipstreaming the jscript update if it isn't for your OS and IE version. Applying the incorrect one will cause some problems with your source.

Tomkat, For w2k, put the WM Codec (wmfdist.exe) file in HF and you are good to go. You can't slipstream wm player 9 or 10 into W2K. If you are doing XP, you need the codecs (wmfdist95.exe) and the player (mp10setup.exe) in the HF folder (remember, it's optional). Hope this helps.

You don't need a repacked installer for WMP10. You use the one directly from M$FT. If you're running English and you want WMP10, put this file (MP10Setup.exe) into the HF folder. It will be slipstreamed when running HFSLIP. Remember, this is OPTIONAL. Here's the link. http://download.microsoft.com/download/1/2...7/MP10Setup.exe

Try running an HFSLIPed sourcess without using NLITE to isolate if it's HFSLIP or NLITE related. There were lots of issues lately with the latest NLITE and sfc. Also, are you slipstreaming something else? HFCLEANUP? FIX? HFEXPERT? OS? Language? Your error_report has all that info, perhaps you can attach post it so we can see what's happening.

The file MP10Setup should be placed into the HF folder. I don't have a link readily handy. FDV can you fix/remove the link?