tommyp

DEU_Q832483_MDAC_x86.EXE isn't needed & tweakui.exe can probably go into one of the HFSVCPK folders. Tweakui doesn't belong in the HF folder. I haven't verified the other updates, but if the baseline analyzer says it's ok, then you're golden.

@kreative19 - Have you read the instructions on how to use HFSLIP? FDV has clear instructions on what goes where. The instructions are posted on the first post of the thread, in the zip file, and when you run the program. I strongly recommend you read them.

Run HFSLIP as mentioned above, and then run NLITE to yank OE off your installation. It works for me.

I'll ask one more time. Run a directory of your HF folder (YES that means ALL files in the HF folder), ZIP it and post it. FYI, a 7z is not a ZIP.

I meant to type out the filenames of the files in the HF folder, and zip up the txtfile.

On my home machine, I run a heavily reduced source. I typically run NLITE to reduce the source, then I run custom crafted cmd files to reduce the source even more. My i386 folder is about 115 meg (with the latest NLITE release), but with older NLITEs I was able to get 108meg, and that's with IE6/DX9C HFSLIP'd. It's lightning fast and puts XP to shame. I love it. The bad part is exactly what you mention with framework, but NLITE has a separate DL for just the select binaries that NLITE needs. Usually once I run NLITE, I do a reinstall a few hours after that. Installation time for me is 15 minutes with all my programs, all unattended and click free. Just remember, each NLITE setting depends on what you plan on running on the machine. So each person needs a different setting. On a sidenote, if I were to run an alternate method for installing without HFSLIPping the source, my SVCPACK folder would be larger than all the binaries in the I386 folder. I prefer a smaller and more compact source, thus the reason why HFSLIP was created.

@Outatouch - The current version slipstreams all of WMP10 (codecs too) with the exception of the WDF components. The first posting this thread says this too. . I wasn't planning on integrating drivers. I typically run NLITE on my slipstreamed source, and NLITE can integrate drivers. @Oleg_II - You can see if hotfixes are installed by (1) visiting windowsupdate or equivalent (2) using HFNETCHK or (3) the Microsoft Baseline Security Analyzer. Personally I like HFNETCHK because it checks file versions. The FAQ sheet has this information. Please read it. Also, for tips on CMD files and whatnot, please review a CMD file that resides in the sourcess\i386\svcpack folder for tips to get the working directories correct. That should help you out. One last thing, FWIW HFSLIP assumes that there isn't any SVCPACK folder in your source folder, and when HFSLIP is run, it creates it's own SVCPACK folder and svcpack.inf file, obliterating any svcpack folder & svcpack.inf file in your source. @kreative19 - Can you please run a directory listing of the HF folder, zip the file and post it here?

Updated download. Includes the corrected typo's and the French fix. Also, don't bother expanding RyanVM's package into the fix folder. You'll have the latest binaries, but you'll be missing a slew of registry entries.

Ok, the new file is up. WMP10 is slipstreamed for XP. WindowsUpdateAgent is slisptreamed (with localization), Empty.txt file corrected, Tomcat's webvw.dll issue is resolved. Enjoy. Comments appreciated. Please remember that if you have issues with your specific language, please say which language you are having trouble with, and please post your HFNETCHK output if applicable. If you are working with W2K, please post your HF folder directory listing as a ZIP file on your post and whether or not you are integrating FDV's files. There is too many options for slipstreaming W2K.

@Outtatouch - I noticed the same thing with WMP10 earlier this week. If you do that installation, you'll be missing a slew of codecs and other junk. So, the next iteration will be out in a bit that includes the "improved" method of slipstreaming WMP10. Yes, the next version corrects the empty.txt issue. @Tomcat76 - The next revision will have the swimp (software improvement). HAHA

@Tomcat76 - Please tell me which webvw.dll works. SP4? Rollup? The kb894320 update? I could have sworn you said the rollup version worked for you. @Pene - Can you tell me the dll or sys file that has the ! in front of it? Do you get this error when using FDV's files? Or do you get it without using FDV's files? @kreative19 - Someone posted a like for flash, I forgot the link, but the filename is flashplayer7_winax.exe. Place that file into the HFSVPK_SW and you'll have your flash installed.

@jpascal - I can't believe you read all 48 pages. That's a ton of reading dude. @Tomcat76 - I have the 828026 update in my HF folder. When you slipstream this, all the script does is slipstream wmp.dll and do some registry changes. If you install WMP9 afterward, the latest wmp.dll (the one from the 828026) remains. @Outtatouch - WMP10 will be slipstreamed at the next release. It won't be a "full blown" version though. You'll have two options for doing WMP10 for XP. The sleek/streamlined version that is truly slipstreamed, or you can just install it via svcpack for a full blown version. The difference will be needless features such as USB stuff and a few skins. You'll need to do your own codecs afterward. If need be, I can put in codecs with hfslip at a later time. @OS2fan - For reg tweaks for XP, you should take a look at the regtweakage program here. It may work with 2k as well, but I haven't verified it for both. I generate my own reg tweaks so I don't use the program. @murvun - Have you tried installing your "source" to see if it's corrupt? Are you using a slipstreamed SP4 of W2K? @mudpit - I'm sorry, but can you remind me of what language you are using? I can't be of much help without knowing what language you have.

@Pene - Thanks for the suggestions. Very nice and thanks for finding that troublesome error. Will update at next release. @Tomcat76 - For English versions, the updates are all listed at FDV's site. If in doubt PM me and I can furnish a list that I use. I'm not sure you did it or not, but you need the scripten.exe hotfix in the HF folder. The scripten fix has newer binaries than the vbs56nen one. Also, with all versions of the rollup, the scsi and hal binaries are NOT slipstreamed (the original sp4 ones are used).

@triplex - Thanks for the empty.txt issue. Will be corrected at the next revision. @FDV - For listening pleasure, I recommend a Black Label Society album called Hangover Music. I liked it so much while crafting HFSLIP, I added Zakk Wylde's name in the script. HAHA.

The dx9 file (mpeg2data.ax) is a file extracted form one of the DX cabs. The prob I believe is that it doesn't have the conventional 8.3 filename. I had to make it an 8.3 filename during the copy stage, but is supposed to bring it back the "normal" way after. Perhaps someone knows how to fix it? For the XP lovers, I tried emailing a few people that slipstreamed WMP10 and asked if I could use their script. Well, it was a few weeks and I heard nothing back. So I'll just generate my own. Now the question I have for this is this: how much of WMP10 do you want slipstreamed? All of it? Or just the barebones stuff? Preliminary tests are good so far, but I want to know how far to go. (DRM, removeable media, etc).

You can't hfslip an hfslipped source. You need a virgin source. Why? Because the script generates additional INF files for which hotfixes are installed, and the script is expecting to have an unadulterated source. If time is too critical, you can remove the "CALL :SPCABS" from the file. The downside to that would be that you'll have a mix of new and old files in your installation.

New version is up. Slight changes, none affecting english users. Fixed the webvw.dll (will eliminate the kb894320 webvw.dll file). Attempted some fixes for the MSOE6 lovers. Have fun. TP

@kukris - There some tests to do to verify IE6. For starters, you can open up each of the files required for IE6 and verify that they say 6 instead of 5. For DX9, there is too many files to verify. It's far easier installing the source onto a VM type of program and do the verification there. Takes far less time. As far as slipstreaming an additional update. Sorry dude, you have to re-run the entire batch. Someone else asked this a few weeks ago, and honestly, I have no time to figure out how to do it. I figure a week of my personal time to save someone else 15 minutes isn't worth it IMHO. Sorry to be blunt. MSOE integration is a PITA. I'm not sure how people tolerate such a program. I did one last try for MSOE, and wil be submitting to FDV for uploading. If people find too much heartburn seeing a non-essential, non-critical windowsupdate for MSOE6, then they should not use the program. Period. If anyone has issues with their install and WU, I'll have to remind them to re-read the instructions, especially the part about reporting issues with hfnetchk results.

@Bilou - Thanks for the tip with the WUA. I won't be true-slipstreaming that as you mention. Perhaps in the future I'll include it. The problem I have is that the installer for that has all the languages in it, and to decipher all the languages is tricky in the script. I'm sure you read the code for hfslip, and if you noticed on the last round, I removed an entire large section for automatic language selection. It just didn't work well. So for now, I won't slipstream it, unless someone else can craft a script that will select languages and output a two letter language (for example English=EN, Français=FR, etc) for ALL languages. I cannot readily find a short and sweet solution to this issue. Anyone feeling like stepping up to the plate? Once that's done, slipstreaming that fix is a piece of cake. BTW, can you confirm Tomcat76's issue with the webvw.dll file with your French version? @Tomcat76 - It seems that you have many language windows at your disposal. Pending Bilou's webvw.dll diagnosis of webvw.dll, I'll change HFSLIP such that the old version of webvw.dll is kept. That way WU will be happy with an older file. This change will not affect English users because this seems to be a non-English issue. For your WMP9 fix, you may want to put your change in the OEM cmdlines or just run a post-install regchange. Perhaps an alternate way to take care of this would be to del that wmp7 branch and add in a reg line like this (can you tell that I love WMP?): Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\WMP9] "DisplayName"="Windows Mierda Player 9 Series" "UninstallString"="" @Ikky_Phoenix - I worked a bit on the OE issue, I think it's fixed up nicely now. Once I hear back from Tomcat76 and Bilou on the webvw.dll issue, I'll forward the new hfslip to FDV for everyone's enjoyment.

@Outtatouch - Welcome to the thread. Ask as many questions as you like, well, as long as they aren't about the meaning of life. HAHA. The last iteration of HFSLIP was really to help out the international folks mainly, but now it also automatically generates some key things during the slipstreaming process that no other slipstreaming utilities do. A side benefit of the latest change is less folders, easier instructions and less things for the user to do. If you are running English versions of Windows, your installation will go smoothly. Most of the info on the thread lately is troubleshooting of non-english issues (which I cannot do). @Tomcat76 - Thanks for doing your troubleshooting. An idea if you feel up to it, if webview.dll is giving you trouble, remove the 894320 hotfix from the HF folder and you should be OK. The only thing the 894320 fix has is the webvw.dll anyway. But if you *really* need to make WU happy, extract webvw.dll from the rollup and place webvw.dll (renamed to webvw.dl_ into the FIX folder), just as FDV suggests. Honestly, I prefer a working system instead of a machine that makes WU happy. There IS a difference between the two as evidenced from what you discovered. Anyway, here's some info for your reg files, it's for W2K only. WMP9: Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\WMP7] "RequiresIESysFile"="4.70.0.1155" "UninstallString"="C:\\PROGRA~1\\WINDOW~2\\setup_wm.exe /Uninstall" "DisplayName"="Windows Media Player system update (9 Series)" "DisplayIcon"="C:\\PROGRA~1\\WINDOW~2\\wmplayer.exe" Yesterday you asked about MDAC. WU is looking for this key to see if it's installed (running a source with HFSLIP automagically makes these changes into the registry): Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\DataAccess\Q832483] @="" "Type"="Update" "Installed By"="" "Description"="" "IsInstalled"=dword:00000001 "InstalledDate"= "InstalledBy"="System" "ServicePack"=dword:00000001 "ProductVersion"="2.53.6200.1" @Pene - HFSLIP was set up to just get barebones files to make a smaller installation source. The msxmlcab.exe file has all you need for MSXML4, no other files are needed for msxml4. As far as the msi extractor goes, I sent FDV an email clarifying that issue. The MSI extractor is ONLY needed if you want to slipstream the new version of windowsupdate.

Tomcat76 - Can you narrow down what the problem is with the "computers by me issue?" This issue doesn't come up with English, so I'll have to ask you for some help. Can you access your network without going to the "computers by me" icon (without any error windows)? Does this issue happen with your non-hfslipped sources? Are you using your localized version of IE? BTW, as Bilou pointed out a few days back, in reference to the MDAC update, it is included with the rollup. You can verify this by extracting that mdac update that microsoft recommends and checking file versions/dates. All is the same. The only thing WU wants is a simple regedit that says that it is installed. You can always use HFNETCHK or the microsoft baseline analyzer to confirm.

@Tomcat76 - Thanks for the feedback. I found the error and sent the new hfslip to FDV for reposting. He'll post here once it's uploaded. Thanks again and sorry for inconvenience. TP

Updated to a new version that supports Windows 2003, new folder structure is implemented, less folders required, WGA added, assorted fixes implemented, and now all installations are now localized. As usual, thanks for the feedback and have fun. TommyP

@vci - I looked into the 888111 fix, and it's not slipstreamable. I guess it's a major change for windows because it adds a bunch of files that aren't part of the original installation. I installed it on my machine here and see no difference with anything. Having said that (or should I say having wrote that?), is it really worth having this file? I see no advantages and see no other improvements. Unless I'm looking in the wrong place? @Outatouch - The included directions say to place the WMP10 installer in a folder other than the HF folder. An example listing for w2k is included in the help file. For starters, and on first glance at your HF list, WMP10, dxsdk, dxwebsetup, hmtcdwizard_enu.exe are all NOT supposed to be there. I attached a filelist of what I have in my HF folder for XP. This makes hfnetchk and the MS baseline analyzer happy. Hope this helps you out. I'll be out of town for work related business for a couple of days (and I'm not in the computer business either). Please hold on to your shorts for a new and improved version of HFSLIP once I get back. It may look the same on the cover, but the inner workings were vastly improved to include hidden features that nobody else has.

CD installation?