tommyp

@vci - I meant to say that the download links for the MS 888111 weren't there. I saw the one MSFT link you posted. I guess it was poor penmanship on my part. What does this particular 888111 do? Any benefits? Thanks for posting the DL... I'll digest it for slipstreamibility and let you know. Also, with FDV's fileset. Your best bet would be to either make manual changes to the INF files and either pack them into the FIX folder or in the FDVFILES folder. I'm sure FDV will chime in when he reads this.

All links are dead except for the sound driver one (which seems to be sound card specific). See if you can get the microsoft executable hotfix and I'll investigate. The rsaenh seems to be one not to be worried about. Following the procedure that will be in the upcoming hfslip release will have the 5.0.2195.6611 revision. At least the revision on my machine has 5.0.2195.6611 anyway. Hope this helps. TP

VCI, welcome to the board. It was a good thing you didn't read through the 39 pages because you are the first to ask. Do you have links for these? Is encpack only for IESP5?

@saugatak: I'm not sure why you would want to use NLITE using FDV's fileset. His fileset produces a nice & tidy OS, free from bloat. I don't see a need to run NLITE on his source. @Tomcat76: MSXML4 is optional. If you really need it for an application, you'll get prompted by the application. With non-English applications like Adobe and such, I do not slipstream foreign applications like that. Your best bet would be to visit unattended.msfn.org and read up there. The intent of HFSLIP isn't to support all of your unattended installation needs. As far as the rootsupdate goes, if you visit WU and it says you are missing the rootsupdate file, then you'll have the correct download for your localized source. Since you are using a dutch source, I would recommend waiting until the new release comes out. It will save you a lot of heartburn.

@gzduke5 - I'll look into that issue you had. It may just go away at the next release of HFSLIP. @saugatak - The intent of HFSLIP isn't to remove components of windows. HFSLIP is used to integrate hotfixes and such. If you need to remove components, please take a look into NLITE. It's a dynamite program. @Tomcat76 - I'll digest the macromedia stuff. A future release is planned in a day or two. You're all going to love it (I know I do hehehe).

Cool, we're a sticky now. Guess it's getting good now. @tomcat76 - If you want to install those office programs (or any other program), please visit Link2 Link1 @saugatak - You probably knew this already, but it's worth mentioning. If you are modifying your installed source, do not modify the SOURCE folder. Modify the files in the SOURCESS instead.

@Tomcat76 - A bad drive will kill you every time. As I said in my post last nite, once the updated HFSLIP is released, the hotfix you mention will be taken care with WU (it's only a registry tweak BTW). Give a few days for me to finish up some tests before it's released.

Thanks Lupo. @Tomcat76 - Why not just install the windows update agent AFTER the hfslip? As far as that last IE update not be installed (which is all but a registry change), you will see it installed when the next version of hfslip comes out (should be a few days). Are you installing anything else after installation? Weird reg tweaks maybe? Are you using a winnt.sif file? Are you testing on VMWARE's program that was suggested on the previous page?

@Tomcat76. There isn't any issues of note with your scripten hotfix versionwise(which is really the version of jscript). I may suggest to run the microsoft baseline analyzer and see what that reports. Why are you so insistent on installing the 5.1 script? It just won't work with IE6, so don't waste your time with it. That was discussed on another thread, which has absolutely no bearing on this one. By the way, can you read your source\i386\prodspec.ini file and see if it says "Localization=English" in it? Can you post the filenames of the files in your hf folder?

Tomcat76: Try adding DriverSigningPolicy=Ignore to your [unattended] section of your winnt.sif file. Perhaps that will do the trick.

@eatkus - Please post your original prodspec.ini file from your source folder. @Tomcat76 - Do you have enough hard drive space when you run hfslip? It needs a few gig of space to run correctly. Also, I'm not sure what you're saying with the rebooting. The sourcess doesn't have an installation with an automatic reboot. BTW, the nature of the iexplore.ext program is a hidden file. You'll have to view it through windows explorer if you are viewing hidden and system files. If in doubt, click start/run and type in "iexplore.exe" and IE should start up. Last point with IE, the script has the IE desktop icon hidden. If you want to show it, there are instructions in the zip file.

@Tomcat76: First Q, Are you using an english version of windows? Or a dutch verion? The IESRC is just a series of CAB files. That's it. Don't bother putting exe files in there. In the HF folder, place your script__.exe file. The __ is the language you are using. As Lupo pointed out, IT=Italian, EN=English, and NL=your language (if you are using Dutch). So, google for SCRIPTNL.EXE and place that into your HF folder. In fact, your other exe's in the HF folder should have an NLD in it (the english guys should have ENU). The JSCRIPT update is only a portion of an update, so I kind of consider it a worthless file. Also, please read the instructions if you are reporting windowsupdate issues.

@Tomcat - A few things: 1 - I'm not sure where you read about using a jscript 5.1. 5.1 is for IE5. If you want IE6, you need 5.6. Lupo from Italy localized the IE scripten scripting stuff a few versions back. Place the script__.exe hotfix back into the HF folder and eliminate the 5.1 script fix. 2 - Place the w2k rollup package into the HF folder (hfslip corrects MSFT's mistakes) 3 - Be sure that you place the HFSLIP cmd file onto your harddrive like this: d:\hfslip\hfslip___.cmd Any spaces or punctuation marks will render the script useless.

@Bilou. Long time no see. Thanks for the inputs. I do not have any issues with LFN and CAT files. Everything installs like a charm on my side (and others too). I re-reviewed an inf from an IE update as a case in point. It has an LFN cat file. The inf says to register this: HKLM,SOFTWARE\Microsoft\Windows NT\CurrentVersion\Hotfix\%SP_SHORT_TITLE%,"Installed",0x10001,1 and install this catalog: %SP_SHORT_TITLE%.cat, update\%SP_SHORT_TITLE%.cat Let's not forget the strings section: SP_SHORT_TITLE ="KB883939-IE6SP1-20050428.125228" Which also happens to be part of the WUHF that is generated (if you had that hotfix in your HF folder). Perhaps I missed something with the 8.3 comment, but I just don't see what you're talking about. In any event, thanks for pointing out that there are errors with your installation before you even tried it.

@FDV, You said it better than I could.

@dziubek: I know English isn't your primary language. I would STRONGLY recommend to read the instructions that came with the zip file. I didn't write the instrutions for my health. The msxml copy errors are a known issue (just as the directions say). Also, it appears that you were trying to be fancy in creating your folder structure. The instuctions give an example on folder structure. KEEP IT SIMPLE! For example, place the file in a folder called hfslip. D:\hfslip\hfslip_0809.cmd. If you put characters in there, it won't work (this is also stated in the instruction file). Also, if you have windowsupdate questions, please follow the instructions on how to report them (the instructions have directions for that too). Please do yourself a favor, and translate the english directions to your native language and read them. All the answers you need to fix this is there.

New file posted this morning. What's new: 1) Additional fixes to for non-English slipstreaming (English still works fine) 2) Add reg files, cmd files, inf files to get processed at T-13 minutes. Say goodbye to importing REG entries using an $OEM$ and CMDLINES method. BTW, CMDLINES happens at T-12 minutes. 3) Added in more information to the non-English users and how to report any WindowsUpdate issues they have. Don't forget the read the instructions.... Enjoy!

@dziubek. Thanks for beta testing with a different language. FYI, you do not have to change the language in the beginning. But I have an issue with this. It really does seem that you are using a modified and non-virgin source. If your newest file in your source\i386 folder is newer than Sep 30, 2004, then it's not virgin and the script won't work. Can you tell me the file dates of each of these files in your source\i386 folder? agentdpv.dl_ (mine is 8/4/04) authz.dl_ (mine is 8/4/04) dhtmled.oc_ (mine is 8/3/04) hh.ex_ (mine is 8/4/04) hlink.dl_ (mine is 8/29/02) hypertrm.dl_ (mine is 8/4/04) icm32.dl_ (mine is 8/4/04) lsasrv.dl_ (mine is 8/4/04) mrxsmb.sy_ (mine is 8/3/04) ole32.dl_ (mine is 8/4/04) shell32.dl_ (mine is 8/4/04) srv.sy_ (mine is 8/3/04) srvsvc.dl_ (mine is 8/4/04) tcpip.sy_ (mine is 8/3/04) telnet.ex_ (mine is 8/4/04) Are you using an NLITEd slipstreamed source? Are you using something that XPCreated? The script works as advertised with English, and this is the first issue I see with people running the script.

@dziubek - Are you using a virgin XPSP2 source?

@Oleg: I understand what you are saying. It's far easier re-running the script to get it done correctly. 10-15 mintes is all it takes running the script, and of that, 80% is the cabbing function. If you wanted to slipstream updated binaries afterward, you would have to do the recabbing once again (which is 10 minutes or so). So in all, you would save about 3 minutes. Personally I don't think it's worth it. @samogon. Here's a 3rd request for you to read the instructions that came with the zip. The first time was when you ran the file, 2nd time was in my post an hour ago, and here's the third time. I pasted the instructions below for you to make it easier for you. Without this info, I CANNOT help you. Q. I am getting messages saying WU isn't happy. How can I report this? A1. Please re-read the "Known [non-issue] Issues" section of this file to see if it's a known issue already. A2. Please download the HFNETCHK program, and run it with the commandline HTNETCHK -V -F C:\WU.TXT A3. Please post your language and the WU.TXT file on the http://www.msfn.org/board/index.php?showtopic=32125 board

@samogon: I can help you out with your problem. I'm afraid I'll have to ask you to read the directions on how to post about errors on non-English versions. Without that, I really can't help. @Oleg_II: I can do that request you asked about, but I'll have to ask you to find a commandline program that is a makecab equivalent. The problem with makecab is that when it makes a compressed binary, it assigns the current date. If you can find a commandline compression program that when it makes a compressed file, it doesn't change the date of the file. I suppose I could just rename the files with a "_" extension, but people will complain that their i386 folder is too big. So, if you find a utility, I can do that request. I have to question why this may be an issue. The script takes about 15 minutes to run. If you are going to be making an installation CD, why not just run the batch, go outside and breathe fresh air and when you get back its done and you're ready to make your boot cd.

@os2fan2: DefectX.... HAHAHA. Both versions of defectx install, it's your choice on which way to do it. I like the slipstream one better. @Oleg_II: I don't plan on mixing OS's via the script. So I'll leave that up to you. Sorry dude. You may want to see which DLLs and INFs are required to install that wireless service. If you add some files into the fix folder, the xp wireless service may start. I haven't tried it. Files you would need are sfc.dll, syssetup.dll and some other ones.

If using the OEM folder, don't you need an extra line in your WINNT.SIF file? Is it oempreinstall=yes or something like that? Or am I thinking of something different? @gzduke5: I'll review that INF file later today when I get a chance. Thanks for posting. @Oleg_II: What is the 2k to xp wireless control you talk about? If you're talking about the wireless service (802.11), it's already there. @FDV: Thanks for adding in nice utilities for the SVPK folders. I guess those folders come in handy for some cool stuff.

FDV, I was thinking the same thing with the kill bits. BTW, you'd be amazed how sloppy microsot was with the rollup package. There are some files with newer file dates, but older versions (non-english only). Go figure. I guess they never heard of configuration managment. @gzduke5: can you open up IEW2K_1.CAB and extract the ieexcep.inf file and post it here?

Never say "you can't do it" to me. HAHAHA. Is there anything else worthwhile slipstreaming into the source? If not, I'll consider the efforts on this project as just a maintenance type of thing. Any feedback appreciated. FDV, thanks for posting about this thread on the forums. . I think the title of this thread scares off the XP guys, even though it works with XP too. I guess it will be one of those hidden gems you stumble on.