tommyp

@tripleX - Please use the un-adulterated error_report.txt file when posting, it has all the information that is needed when HFSLIPping. BTW, HFSLIP automagically generates it when HFSLIP is run.

@triplex - You still are NOT setting up the folders correctly. Can you please post your error_report.txt file?

Does your source\i386 folder have a svcpack folder in it? If it does, then you will get that copy message. For best results, you must use a virgin source. Also, be careful about modifying the sysoc.inf file in your fix folder. HFSLIP uses that to patch all the proper regedits. If you must have an altered sysoc.inf, please modify the one in the sourcess\i386 folder instead.

@tripleX - Please read the first post on error reporting.

Sorry for the delay.... the new version is up. Things fixed... implemented fix for the new w2k rollup, rfliu2000's comment, wmp9/10 codec slipstreaming, improved dx9 slipstreaming, incorporated an HFExpert mode slipstream capability (be careful with this one), added the malicious software detection tool integration, fixed the KB898461, and some other things. I haven't touched the issue with the point that Electician brings up with sysoc.inf. If he's missing that file in his xp, there is something wrong with his cd. According to all that I have read, every installation source has it and I'm not sure why he said what he did. Strange. Have fun, good luck, and please use the new error reporting tool (if need be). TP

@amitri - Place the MP10Setup.exe file in the HF folder and run HFSLIP. It will be slipstreamed. Use the installer from the unattended.msfn.org website.

I didn't forget about hfslip, in fact I've been doing so many test runs, I'm getting sick of it. The next version is a drastic change from the past, but since it's only a command prompt program, it will the same to the user. I'm trying to make it easier to add things in the future (once I figure out some fancy scripting), but this change is necessary if I want to make it easier for me in the future. The issue I'm having now is directx and when some lines are processed during installation. This is kind of key for the next version. Today I have dissected the setup process, all along the way from T-X to T=0 seeing when is the best time to inject settings/inf files/etc. It's pretty cool watching stuff get added to registry and then processed. The issue I'm having is with DX9 and trying to fix problems posted a week or so ago. I thought I had the solution, but I'm not sure. Maybe I'm just trying to inject too much DX9 stuff. But give a little while before it's resolved. I'm working as fast as I can, Captain. @zottan - I'm sorry I can't help you with the problem you have. Please rephrase it so I know what's wrong. If you are slipstreaming 2003 server, you MUST slipstream SP1 manually first for HFSLIP to work. Also, please doublecheck the hotfixes to see if they post SP1 fixes. I don't have a list of hotfixes handy, and I don't use/have 2003 server either. @Electrian - The empty.txt fix was implemented about a month ago, and since then other changes also took place. My buddy Lupo from half way around the world mailed me some nice code to take care of the sysoc.inf file. That issue should be gone too. That's strange with the KB898461 though. I'll have to investigate. Can you do me a favor? Before you post that you have issues with HFSLIP, please verify that you have the latest version of HFSLIP as you are bringing up issues that were resolved a few weeks/months back. Thanks!

I've read the contents of your HF directory. You have way too much stuff in there. Please see the first thread in this thread on what fixes are supposed to go in there. For starters, all of these don't belong: MDAC_TYP.EXE StepByStepInteractiveTraining-KB898458-x8 WindowsMedia9-KB885492-x86-ENU.exe js51nen.exe js56nen.exe MSJavx86.exe msjav.exe Also, the hotfixes you are slipstreaming are for ENGLISH. So I'm not sure if you have an English CD or not. If you have a language other than english, you will have to use your localized hotfixes. @saugatak - Thanks for the heads up with the rollup. I'll check it out in a bit.

And the output also shows "0 file(s) copied" when the above updates are extracted (after the "file not found" message). I have tried to fix it myself but it's too complex and unfortunately I don't have much experience with this topic. By the way: I want to compliment you to your code. It must have been a great lot of work!! Respect! I would be very grateful if you help me. Many Thanks Berki <{POST_SNAPBACK}> Sorry I haven't responded earlier. You'll need to manually slipstream SP1 first for your W2K3. Read the first message of this thread on how to manaually do it. HFSLIP only slisptreams GDR fixes, this avoids issues that come with QFE types. Some of those fixes you have listed are not GDR types. Besides, I have read that QFE fixes aren't really for everyone. Good luck.

@Oleg_II - Thanks for spelling out the DX9 issues clearly. It really helped alot with getting the DX9 better slipstreamed. Hopefully I have it corrected for the next version, which BTW is under some serious testing. It has some nice new features.

@PeterGau - The issue you have with HFSLIP is because you renamed the files you downloaded from Microsoft. A typical type 1 HF has this name: WindowsXP-KB885836-x86-ENU.exe (for English anyway). I sent you a PM to help you rename your files. @rabidrodent - Obviously you didn't read the instructions on the first posting of this thread. * The following do NOT belong in your HF folder. dotnetfx.exe, js56nsv.exe, the two NDP files, Q818043, Q832843. In fact, you don't need any of those files. *The following files are named incorrectly and not processed correctly: WGA and the WUAgent20. Please refer to http://www.vorck.com/2ksp5.html on how to get the correct files and what to do with them. * http://www.vorck.com/2ksp5.html also tells you how to work with the dotnet installation. @dreaMMar - Thanks for the words of encouragement and thanks for posting. It's pretty cool that the program works halfway around the world.

@Electrician. You may want to read this: http://www.vorck.com/hfslip.html for what fixes are to be placed into the HF folder. At first glance, W2K hotfixes don't belong there (msxml3.msi, rootsupd.exe, scripten.exe). XP comes with msxml3, rootsupd isn't needed, and scripten is an IE6SP1, XP is IE6SP2. Also, be sure that your XP source is SP2.

@PeterGau - I'd love to help, but I'll have to ask you to read the first post on how to post errors. I'll need a file listing of your HF folder for starters. TP

@Electrician - You don't need to use Gurgelmyers URP to slipstream using HFSLIP. As long as all the hotfixes are in the HF folder, you're all set. To get a CMD window during windows setup, I think it's either shift+F10 or CTRL+F10.

@PeterGau - Welcome to the board. You do not need the setup.exe in the root of the CD. If in doubt, you can always copy it over. But it's really not needed. TP

@kukris - Please visit FDV's site on what KB#'s you should have in your folder. You have way too many in there. I didn't verify the list as FDV has it published already, but you do not need js56nde.exe (scriptde.exe supercedes it), MDAC_TYP.EXE (the rollup fixes this), msxmlcab.exe (isn't needed), Q832894.exe (a blast from the past IE hotfix). You need to tidy down your HF folder. Fix it up and report back. @FDV - thanks for posting. All - Grab the international fix.

@dziubek - HFSLIP will be updated shortly (FDV may post when it's up) that has the fix for the odd update. The MRT thing code you posted changes from month to month. I think I have an idea to get it done. You'll need to hold on for that fix as I'm working on some more things to slipstream. ...KB898461. I'll have to look into this one.

@hoonu - HFSLIP is a slipstreamer, so you can't uninstall it. It's all integrated together. For you unattended needs (other software, guest accounts, etc), I would suggest you visit unattended.msfn.org site.

@dziubek: Thanks for using the error report for the issues you have with HFSLIP. Hopefully these answers are OK for you. 1) The error messages you see when the script is running throught the msxml extacting are fine (the msxml ones). There's a ton of filtering happening there and I had to make the script as generic as possible. The alternative to not seeing that is to just have the dos window show a plain old black screen, which isn't too desireable. 2) KB887472 - It is missing from your list because you didn't slipstream it. 3) KB890046 - MSFT has an interesting installer with international versions. The change will be incorporated into the next HFSLIP. I hate how microsoft can't keep international versions the same as english. 4) KB890830 (Windows Malicious Software Removal Tool). It's a known issue that this fix isn't slipstreamed. Do you anticipate malicious software on a clean install? I'll look into slipstreaming it.

@triplex - Found the errors (actually Microsoft induced errors) with file versions and file dates. Hopefully you have set an example here on error reporting so I can quickly fix things. I fixed some other stuff while I was editting the file. @All - New version is up with HFSLIP fixing Microsoft errors. Please use the error_report.txt file to report any issues.

@blinkdt - Thanks for the compliment. Would you mind if I quoted your words for the first post of the thread? @pene - The last I heard from you about your usb issue was when you couldn't get the list the hfslip'd computer. Can you run this for me? Start/Run/DXDIAG. See where the errors are and report back. My system works fine here. @Oleg_II - Are you removing IE with FDV files and then installing IE6 after windows is installed? @triplex - I didn't forget about you, I'm evaluating your errorlog. Give me a bit to see what's happening. I think I found something interesting.....

@tripleX - You can slipstream your msxml sp7. Throw the msi installer into the HF folder. Regarding the issues you have with your installation, please follow the error reporting procedure in the first post of this so I can help you out. @all - New version is up. Some FDV tweaks, eliminated a needless re-cab operation (saves a minute or two) and some tidying.

@BeenThereB4 - I don't know if you are being sarcastic or not in this wonderful world of the internet, but can you verify that the files that bireland mentions are on the CD for 2000 server? I can't because I just don't have it. The script is set up for a cd installation, not a network install that bireland did. HFSLIP even says that it is intended for installing from a CD when you run the program. But it's nice to hear what happens when the script can be capable of. As far as capilization goes, I have never ever had any issues with upper/lowercase filenames on my installation cds. In fact, I'm not sure if you checked lately, but if you slipstream (not hflsip) SP4 onto W2K, and/or if you slipstream (not hfslip) SP2 onto XP, you'll see lowercase filenames on some of the files. Those sources seem to install fine for lots of people. So I'm not sure what you're getting at with the capitilization mandate. @bireland - Slipstreaming IE6 is more than fileswaps for it to work. I think the traditional method of slipstreaming IE6 isn't really slipstreaming at all. It's just running the IE6 installer at the SVCPACK.INF.

@tripleX - According to KB890046, it has no bearing on the line you quoted from HFSLIP. The line you quoted was due to a webvw.dll issue. If you have issues with your installation, please post the results from HFNETCHK otherwise I can't help. @bireland - I haven't tested hfslip with windows2000 server. Sorry I can't help too much for you. You may be able to get around this copy error by using a winnt.sif file. Also, HFSLIP was geared more for installing via a cd, just as the instructions say.

Can someone tell kreative19 where to go to read about how to use HFSLIP? I tried to do it nicely 3 times already. @kreative19 - Hopefully someone will guide you on where to go to get instructions on how to use HFSLIP. Unfortunately for you, you'll need to read it and follow it for the script to work. @murvun - In the instuctions is a commandline file-checker called hfnetchk. Please run it and report any issues. After running HFSLIP, the instructions are all there. There's probably instructions on FDV's site too.