tommyp

I was a bit ambitious today and made a few improvements to include integrating critical updates to a slipstreamed XP service pack 2 source. See the first post.

@Bilou, You have lots of great ideas/suggestions, but I have no idea on how to incorporate them. Can you please add in some code so I can copy and paste it into that CMD file, or if you prefer I can pass the reigns to you as the keeper of the slipstreamer. Either way is cool with me. An idea on running that inf, perhaps it can be run using an OEM folder cmdline? If that is done, the winnt.sif file would need to get modded such that during the installation, the OEM folder is copied over and the cmdline is run.

Donjuan, Here's and example of how to install an inf via a commandline %systemroot%\System32\rundll32.exe advpack.dll,LaunchINFSection 1KB329115.inf ,DefaultInstall

Donjuan, Thanks for the positive feedback. I haven't figured out how to automate the INF entries. By automating, I mean extracting a portion of the inf file and integrating it with the hive files. I'm sure it's possible, but editing the infs isn't that tough. However, I would recommend that you run at least the ones for internet explorer (if you have slipstreamed them). The inf files makes some registry changes that deal with activex.

That's a ton of q's. Hopefully these answers will help out. I define a "standalone" installation as a "stock" sort of configuration, with no optional components removed by nlite. I define a "nlited" installation as an installation cd that you run NLITE to slim the source down even further. I have my I386 folder shrunk down to 128 meg suing NLITE. By saying scripten hf2, I mean it that it's a type 2 hotfix. If you built a repacked directx9c package that requries a different switch, you CAN edit the cmd file. In fact, I encourage anyone who uses it to edit it. I created my dx9c package such a long time ago, I forgot exactly how I did it. That's why I created that cmd file with the /Q:A /R:N switches. I cannot confirm, but if you are using an xpcreated source i386 folder, chances are that this cmd file isn't for you. Your best bet is to use a virgin source. On WMP stuff. I don't plan on integrating any WMP stuff. It's too bloated for me. However, if you read through the source of the cmd file, and you're a bit technical saavy, then you should be able to slipstream both WMP9 in there too. Hell, maybe you can slipstream WMP10 in there instead. Hope this helps

If you want a bloaded install cd and slow windows 2000 installation, then do the svcpack method. If you want a sleek, slim and speedy windows 2000 installation, do the tommyp method.

My method does ALL the hotfixes and integrates IE6, without using a svcpack folder.

@ Bilou: What components aren't updated in my method?

Have you checked out my method of integrated the hotfixes? All you have to do is drop the various hotfixes in a folder and run the cmd file. It will slipstream any hotfix you have. http://www.msfn.org/board/index.php?showtopic=32125

If you copy blackbox over via a CD, make sure you change the attributes so it's not read only. BB will not keep any settings if you don't change the attributes. Have you looked at BBLean? I like it better than BlackBox.

It's somewhere on the board. I repacked it a while back, you need the regular installation and some other file to repack it. Search for it

You're right, the msxml files aren't registered off the bat. I run a regsvr32 command to register the msxml files after the install. I guess an inf file can do the same thing too.

First post updated to include the infs.

BBLean is pretty cool, small, open source, stable and without eye candy. It uses like 5 meg of memory as opposed to explorer that uses 15.

This method sort of follows the same routine as a post I did a few weeks ago on slipsteaming IE6 into a W2K installation. link However, this batch file is more user friendly and doesn't need much user intervention. This program is geared as an alternate to XPCREATE, but more importantly, as a great companion to W2K NLITE'd installations. I'm not sure about others, but I had great difficulty creating a usable source using xpcreate. Once microsoft came out with the mid October hotfixes for IE, it pretty much deemed xpcreate unusable for me. This method fully slipstreams type 1 and type 2 HF's into the i386 folder, but does not include DX9C. It has optional switches if you want to slipstream IE6SP1 and MDAC updates into the I386 folder (but you have to have the correct hotfixes in the folders). There is nothing executed from the SVCPACK folder. To use it, open it up in notepad and change the DOIE and DOMDAC switches accordingly. Things you need 1. W2KPro with SP4 slipstreamed * 2. FDVs zip files (need sfc.dll and setupapi.dll) 3. An XPSP1 cd (not sp2). (need IE.IN_ IESETUP.DL_ MSOE50.IN_ AND WAB50.IN_) 4. The updates listed on one of the stickies in this forum. 5. IE6SP1 installer, uncompressed (it's a series of cab files) General instructions. 1. Place the attached file it into its own folder. 2. Open the cmd file with notepad and see the instructions in the top of the file. 3. After the program is run, you'll have a slipstreamed source. 4. If you run NLITE, run it after the slipstreaming cmd file is run. 5. Run a series of infs after installing with this source. The installed source needs some infs for settings changes that the hotfixes do and for windowsupdate report things correctly. I can post them in this thread if it's in demand. I'm sure that this code can be modded somewhat to accomodate for changes for xp too. My prelimary results seem to work. The program takes about 8 minutes to run. The only issues I see is that it does not put an internet explorer icon on the screen (which is just a regedit to put it there), but IE can be accessed by going start/run and type in IEXPLORE.EXE. Any test results or comments are appreciated.

@Bilou, I updated the IE6 slipstream with an altered but similar method. Link I'm sure if you try it out to build a package and then overwrite the w2k source, you can slipstreeam away using XPcreate. I verified the batch file last night and all works great. In any event, it sounds like you are in the same boat that I was in a few months ago with the october 12th hotfixes. However, for me it's nice have only one file in the svcpack folder now along with all the updated binaries in the i386 folder. Zero critical updates for me currently. It really speeds up my installation too.

Here's one to add the status bar on the bottom of the explorer window: [HKEY_CURRENT_USER\SOFTWARE\Microsoft\Internet Explorer\Main] "StatusBarOther"=dword:00000001

Reinstall MDAC and your problem will be solved. The control panel depends on about 3 dll files, which are part of the w2k mdac default installation.

@Bilou_Gateux, I have inf files to accomplish the registry fixes in W2K. To integrate the msxml, add the dll to the txtsetup.sif and the other 2 files to locate the file into the system32 folder. Once installation is complete, register the dll. Have you had success with integrating directx9? BTW, the update pack for w2k will be around 100meg. Let me know if I can help out too.

It is possible to slipstream all the post sp4 critical updates into w2k including ie6sp1 with the exception of dx9. I posted about it a few weeks ago.

It isn't that hard to do with command lines, but I don't think I'm really capable of doing it all in one big script (cmd) file (I'm not a computer guru when it comes to programming like that). Bilou Gates started doing some commandlines, but it appears that his efforts moved somewhere else. If anyone is going to step up to the plate, I can forward some of the scripts that I did come up with to at least do the IE6 stuff (as long as I get some sort of credit). When I did that posting a while back, I thought it would have received better fanfare from the community being a real way to slipstream IE6 as opposed to running an exe file at the end. Whatevs. I still think it's a great way to install windows. If any of you guys ran a w2k installation, take a look at the size of the i386+critical updates+dx9+ie6 files/folders. The method in my link is 80 meg less and it installs in 5-10 minutes less time than the traditional way. Like I said before, once the IE6 is integrated, the rest (critical updates) is a piece of cake. The only file in my svcpack folder is dx9c. The remainder of the ~28 critical updates is integrated without any commandline switches (because all the dlls and exes are already packed into the distribution folder). According to windowsupdate, hfnetcheck and baseline security analyzer, all patches/updates are installed. Once a new critical update comes around, all I have to do is expand the update and swap the required DLLs and EXEs into the i386 folder and apply an inf file. How easy is that? I got a little ambitious and integrated the new xml stuff too (without it the baseline analyzer was complaining that it needed some system update). I'm sure dx9c is integratable, but I think it's more regedits than anything else. Take a gander at the XP2 expanded installer and the expanded DX9 cabs and you'll see what I mean. On a sidenote, my nlited W2K i386 folder is 126meg which includes IE6 & hotfixes.

For 2k, do you mean this?

Bilou, Thanks for the commandline, it worked. Finally got the MDAC complete as well as that MSOE PITA update. Here's what you inf info needed for the OE update to say it's installed via windowsupdate. HKLM,"Software\Microsoft\Windows\CurrentVersion\Internet Settings","MinorVersion",0,";SP1;Q823353;" No more critical updates reported with my install.

Great work Bilou, You can delete that dummy.cab from your list. Thanks for the inf info, but I have all but one of the infs needed to make windowsupdate to think it's all patched/updated. Let me know if you want me to mail them to you. I'll test those commandlines out that you gave. I guess it's ok to have remedial questions once in a while. HAHA. It appears that windowsupdate only checks the registry. The commandline HFNETCHK utility checks file versions, and the Microsoft Baseline Analyzer checks both. Weird. Each is good in their own way I guess. The registry spot that windowsupdate generally checks is: HKLM\Software\Microsoft\Updates - there will be 4 "folders" there -DataAccess\ -Internet Explorer 6\SP1\ -Windows 2000\SP5\ -Windows Media Player Another spot the hotfixes write to is here: HKLM\Software\Microsoft\Windows NT\CurrentVersion\Hotfix\ I don't think that windowsupdate looks there, but there isn't too much more in the infs to insert it anyway. My remaining inf needed is for MSOE (KB823353). I tried a bunch of variations, but I seem to *think* that this hotfix is the only one that needs some reference in the HKLM\Software\Microsoft\Microsoft\Active Inf Setup\oeupdate. It's an oddball. I'll confirm it in a bit.

Click here for the current version. HFSLIP is a small CMD file to slipstream hotfixes into a Windows source without the need for a svcpack folder full of EXE files that would only be integrated. Windows 2000 Instructions Windows XP/2003 Instructions. HFSLIP is a hotfix slipstreaming program for Windows 2000 and Windows XP and Windows 2003. * It slipstreams and recabs Type 1, Type 2, and MSXML-MSI hotfix binaries into the Windows source (if it's a hotfix, HFSLIP can handle it!) * It integrates programs that use silent, switchless installers like WMP9 [2K only], WMP10 [XP and 2003 only] and DotNet. * You can import registry entries, run CMD files and run INF files at T-13 minutes. This makes your settings "stick". * It force feeds hotfix registry information during the installation, the registry information is taken right from the hotfix you want to slipstream. All hotfixes would be localized. * It force feeds the additional files required for your installation. * It force feeds the necessary catalog files into the registry. * It maintains digital signature data on all files used for installation. * It doesn't rely on any modified DLLs for installation. * There is no need to disable system file protection, SFC is maintained after installation. * A winnt.sif file is not required, and no editing of any source files is required. * It runs in a command box on Win2k and higher. * All languages supported * Fully localized installation for all OS's * File to report errors are automatically generated. Windows 2000 specific features: * It slipstreams Internet Explorer 6 into Windows 2000 (or, you can use IE 5). * It slipstreams DX9C into Windows 2000 (but does not have bloat -- no pictures of joysticks, etc.) * It slipstreams all Type 1 and Type 2 critical updates. * The Microsoft post rollup errors with Hardware Abstraction Layer and the SCSI driver are resolved with this issue. Note: With the rollup errors repaired, windows update will report that the rollup is not installed. Read the instruction set if you would rather have windowsupdate happy instead. * It slipstreams the Windows Genuine Advantage and slipstreams the new WindowsUpdateAgent. * It integrates the Malicious Software tool for the people who can't live life seeing it as a WU. * It slipstreams the WMP 9/10 codecs (not the player). * It slipstreams HFExpert items. Windows XP specific features: * It slipstreams all Type 1 critical updates. It can also slipstream type 2 updates as well, but there are no Type 2 at this time for XP. * It slipstreams the Windows Genuine Advantage and the new WindowsUpdateAgent. * It integrates the Malicious Software tool for the people who can't live life seeing it as a WU. * It slipstreams WMP10 (less the WDF components). If you need WDF, then don't slipstream it in the HF folder. Read links below for details. * It slipstreams WMP10 codecs (not the player) less DRM. * It slipstreams HFExpert items. Windows 2003 specific features: * It slipstreams all Type 1 critical updates. It can also slipstream type 2 updates as well, but there are no Type 2 at this time for 2003. * It slipstreams the Windows Genuine Advantage and the new WindowsUpdateAgent. * It integrates the Malicious Software tool for the people who can't live life seeing it as a WU. * It slipstreams WMP10 codecs (not the player) less DRM. * It slipstreams HFExpert items. Once the file is run, it will create a fully slipstreamed source in a folder called SOURCESS. Installation must be from a CD. Caution is advised for those who slipstream DX9C into W2K and run NLITE on the sourcess folder. What is needed: A drive with a few gig of free space and the abilty to read. Error Reporting. Please post these items so I can help troubleshoot if needed. I cannot help you without it. -- The ERROR_REPORT.TXT file, with the bottom part completed by you. -- Your hfnetchk log - this is HFNETCHK -V -F C:\WU.TXT - ZIP up the above and post the info. - (Hint a filename like ERRORZIP.RAR is not a ZIP file. ----------- I have tested this with English versions and works great. Additional language support was added, however, I cannot test with other languages. YMMV. Please report any issues with languages and include the output from HFNETCHK if applicable. Detailed directions are in the attached zip file. Slipstream Data File Download For Windows 2000, please visit FDV's site on this. For Windows XP and 2003, please visit FDV's site on this.