tommyp

Cool thread, thanks for starting saugatak. FWIW, I did a task on seeing what services W2K actually needs. Here's what I have running. Event Log Plug and Play Remove Procedure Call (RPC) Workstation Network Connections Protected Storage Remove Access Connection Manager Telephony Windows Management Instrumentation Driver Extensions I'm sure some of the above services can be eliminated too, but the above list works fine for me. Maybe this will help slim down the source a bit more?

Of course it didn't work. The solution is really easy. You didn't follow the directions , especially the part on "which file goes where". There is a subtopic in this forum. http://www.msfn.org/board/index.php?showtopic=57603 and it appears you are using HFSLIP for XP so you may want to look here: http://www.vorck.com/hfslip.html#11 Bottom line, you have to rename the files back to the way you downloaded them from Microsoft. Once you rename them correctly, then HFSLIP will work. Post back if you run into probs.

@Bilou_Gateux - Would it be better to somehow modify the Drivers.au3 file so it looks for the i386\prodspec.ini file instead of the XP cd root files? That prodspec.ini file is on w2k and newer OS's. If changed correctly, won't the driver method work for all OS's? I don't know the syntax of the Drivers.au3 file, so I don't know how to modify it. Any tips?

Have you tried HFSLIP? It slipstreams hotfixes, the WGA, the WUA and a lot more. http://www.msfn.org/board/index.php?showforum=129

@TAiN: I was looking at these same two threads this morning. I think I like this one better: http://www.msfn.org/board/index.php?showtopic=51406 only because it seems easier, but I haven't tried it, so YMMV. My $.02. When doing his 3 steps, create your OEM subfolders alongside your SOURCE\i386 folder. Once all 3 steps are complete, run HFSLIP and you're good to go.

@pr0nstar - Thanks... the link is corrected.

@Oleg_II - The files get copied over during the copy mode portion of setup (like right after formatting). If you need a dll registered, then place it in the CODECS folder. Easy huh? @Yzöwl - I'll incorporate your ideas in the script (won't release it yet though).

If you use the HFEXPERT folders, you do NOT need to edit anything. HFSLIP does it for you. CODECS folder: Contents will end up in the system32 folder, if it's registerable (via regsvr32) then it's registered. SYSTEM folder: Contents gets copied to the SYSTEM folder. No other processing. It only copies files over. SYSTEM32 folder: Contents gets copied to the SYSTEM32 folder. No other processing. Only copies. WIN folder: Contents gets copied to the %windir% folder (ie Windows or WINNT). No other processing. Just a word of caution, you may see some error messages if you use this. This is why I have made it a hidden item to prevent any probs. BTW, you can almost use it as a replacement for your OEM folder. Hope this helps. If you can think of other worthwhile folders other than anything in the program files folder, I'm sure I can incorporate it.

HFSLIP, the 2K/XP/2K3 slipstreamer HFSLIP is a small CMD script made to slipstream hotfixes into a Windows 2000/XP/2003 source without the need for an SVCPACK folder full of unextracted hotfix executables. Home Page *************************************************** LATEST VERSION - HFSLIP 1.7.9 Download Mini changelog HFSLIP 1.7.9: - [XP] added support for IE8, OS recognition, MS Installer 4.5 plus lots of MS related bugs Complete changelog Basic how-to guide Important notes on Windows XP Service Pack 3 Handling of Windows Internet Explorer 7 Important things to know Advanced Features Related links on Fred Vorck's site... HFSLIP FAQ by TommyP and Fred Vorck HFEXPERT and HFCLEANUP folders *************************************************** HFSLIP... * slipstreams Service Packs as well as Type 1, Type 2, and MSXML hotfixes. * slipstreams Windows Genuine Advantage and Windows Update Agent. * integrates the Malicious Software tool for people who can't live life seeing it as a Windows Update. * integrates silent, switchless installers such as .NET. * has Windows setup run your custom REG, CMD and INF files at T-13. * force feeds hotfix registry information and the security catalog files (taken from the hotfixes you want to slipstream). * maintains existing digital signature data on all files used for installation. * doesn't rely on any modified DLLs for installation. * doesn't require you to disable system file protection. * doesn't need a winnt.sif file or require you to edit any source file. * runs on Windows 2000 and higher. * supports all languages. * generates a log file which can be used to report errors. * repacks cab files in a compression ratio of your choice. * supports an optional answer file to automate the HFSLIP process. * supports application addons and XPize. * optionally slipstreams alternate applications, codecs, WINDOWS/WINNT files, Program Files files, custom drivers and AutoIt installs. * optionally supports reduction file sets aimed at reducing your installation. * optionally slipstreams a ramdrive for nice security. * optionally slipstreams alternate icons. * optionally creates bootable ISO images for testing/burning/etc. * optionally extracts boot sectors from the Windows CD into a file called BOOT.BIN required to generate a bootable ISO image. * optionally creates a new SPX.CAB driver package with updated driver binaries for a speedy HFSLIP process. Windows 2000 specific features: * it slipstreams Internet Explorer 6. * it slipstreams DX9c (without the bloat -- no pictures of joysticks, etc.) * the Microsoft Post-SP4 Rollup error with Hardware Abstraction Layer is resolved. * it slipstreams WMP9. * it slipstreams the latest WMP 9/10 codecs (does not require WMP9). Windows XP specific features: * it supports XP SP1, SP1a, SP2 and SP3. * it slipstreams DX9c into Windows XP SP1 (without the bloat). * it slipstreams WMP11 for Windows XP Pro (more info). * it slipstreams WMP10. * it slipstreams the latest WMP10 codecs (does not require WMP10; not intended for WMP11). Windows Server 2003 specific features: * it slipstreams DX9c into Windows 2003 Gold (less the bloat). * it slipstreams the latest WMP10 codecs. The first time HFSLIP is run, a series of subfolders are created in the HFSLIP working folder which you can then populate. Subsequent runs will create a fully slipstreamed source in a folder called SOURCESS. HFSLIP is to be used for installations from CD. You may have issues with other installation types. You use hotfixes downloaded from the Microsoft servers and not from someone else. Caution is advised if you run nLite on the SOURCESS folder (see this link for more information). What is needed: a drive with a few gigs of free space and the ability to read. Error Reporting. See http://hfslip.org/support.html Please report any issues with languages too and include the output from HFNETCHK if applicable. ------------------------------------------------------------------------------------------ Thanks to everyone for helping out with the script!!!

As promised, here's how to SLIPSTREAM codecs into your source. DO THIS AT YOUR OWN RISK! version 3, dated May 22, 2006 & works with HFSLIP_51030.cmd and newer. This is a manual process and if it scares you, don't do it. What does this do? a. Slipstreams codecs into your source. b. Fixes icons for various media types in Windows Explorer. Does this require system file protection or any dll replacements? a. No. What do I need? a. For W2K, you need to slipstream DX9 (Refer to FDV's instruction set for details). b. The KLITE Mega Codec Pack. You may be able to do this with the other packs too, but I haven't verified it. c. W2K: Download WindowsMedia9-KB891122-x86-Global-ENU.exe, extract it and put wmfdist.exe into HF folder. d. WXP/2K3: Download WindowsMedia-KB891122-x86-ENU.exe, extract it and put wmfdist95.exe into HF folder. e. The HFSLIPCD.INF file, download link at bottom of the message. f. The modifype.exe program in the HFTOOLS folder. What if I NLITE my source? a. Do NOT remove the SOUND DRIVERS otherwise most codecs WILL NOT work. Refer to step 12, unless you know what you are doing. What if I NLITE my source to eliminate WMP totally? There's a 5+ page NLITE thread on how to do this, but this can be done very easily as follows: a. See the write up at the bottom of this. Known issues: a. None at this time, installs like a charm. There are two methods to HFSLIP your codecs. Option A The first and easier method is to use TAiN's prepacked plugin. Here is a new version of the pack. Unattended installation: Manually create HFSLIP\HFEXPERT\CODECS directory Dump contents of pack into CODECS Option B TommyP's old fashioned manual way Instructions Step 1. Download the modifype.exe program and place it alongside the HFSLIP___.CMD file. Step 2. Download the KLITE Mega Codec Pack. Step 3. Manually create a folder alongside the HFSLIP___.CMD file called HFEXPERT. Step 4. Manually create a folder inside HFEXPERT called CODECS. Step 5. On a junker PC or a VM, install the KLITE MEGA CODEC PACK. You can install everything, we'll pick and choose what files we want. Step 6. Copy the following files from the junker PC or VM to your HFEXPERT\CODECS folder. These files reside in a combination of the %windir%\system32 and the Program Files\K Lite Codec Pack folders and Google. 3ivx.dll 3ivxConfig.exe 3ivxDSAudioDecoder.ax 3ivxDSDecoder.ax 3ivxDSMediaSplitter.ax 3ivxVfWCodec.dll ac3acm.acm ac3filter.ax ac3filter.cpl CLVSD.ax CoreAAC.ax CoreFLACDecoder.ax CoreVorbis.ax cpuinf32.dll DirectVobSub.cpl divx.dll divxa32.acm DivXc32.dll DivXc32f.dll divxdec.ax huffyuv.dll I263_32.drv IMC32.acm Ir41_qcx.dll Ir50_32.dll ir50_lcs.dll l3codecp.acm l3codecx.ax MACDec.dll MatroskaSplitter.ax mkx.dll MonkeySource.ax mp4.dll MPCDec.ax mpeg2dmx.ax mpg4c32.dll msaud32.acm msvcr70.dll ogg.dll OggDS.dll OpenQuicktimeLib.dll splitter.ax vorbis.dll vorbisenc.dll vorbisfile.dll vp31vfw.dll vp6dec.ax vp6vfw.dll vp7dec.ax vp7vfw.dll VSFilter.dll WavPackDSDecoder.ax WavPackDSSplitter.ax WMV9VCM.dll xvid.ax xvidcore.dll xvidvfw.dll Step 7a. Quicktime: Place these into the HFEXPERT\CODECS folder. qtmlClient.dll QuickTime.qts QuickTimeEssentials.qtx QuickTimeInternetExtras.qtx Step 7b. Google for QuickTime.ax and place that into the HFEXPERT\CODECS folder. Step 8a. Realplayer: Place these into the HFEXPERT\CODECS folder. FYI, one of the files could be from an older version - that's all right): atrc3260.dll cook3260.dll drv13260.dll drv23260.dll drv33260.dll drv43260.dll pncrt.dll sipr3260.dll tokr3260.dll Step 8b. Google for RealMediaSplitter.ax and place that into the HFEXPERT\CODECS folder. Step 9. Download and place HFSLIPCD.INF into the HFEXPERT\CODECS folder. Refer to bottom of message for download link. Step 10. If you want to remove Windows Media Player and go with Windows Media Classic: a. Put my OPTIONALLY place my modified mplayer2.in_ file into your FIX folder (see end of message for download). You need to rename the file for your OS. b. Create a folder inside HFEXPERT called APPREPLACEMENT. Place mplayerc.exe (Media Player Classic executable) inside it. Rename it to mplayer2.exe. Step 11. Run HFSLIP and install using the SOURCESS folder. Step 12. If you want to run NLITE: a. Add in a files to keep and files to remove section in your NLITE settings. Refer to the end of this posting for what to keep and what not to keep. b. Do NOT remove the "SOUND DRIVERS" or "Windows Media Player 6.4" when running NLITE. c. Here's the NLITE KeepFiles and RemoveFiles: [KeepFiles] bdaplgin.ax kstvtune.ax ksxbar.ax kswdmcap.ax l3codecx.ax msdvbnp.ax msyuv.dll psisrndr.ax vbisurf.ax wstdecod.dll psisdecd.dll dxntunp.inf dxver.inf diactfrm.inf dpvoice.inf dmusic.inf dsound.inf dinput.inf ksreg.inf dplay.inf dxdllreg.inf dxbda.inf bda.inf kscaptur.inf mpe.inf ndisip.inf nabtsfec.inf slip.inf streamip.inf ccdecode.inf wstcodec.inf bdasup.sys ccdecode.sys ks.sys ksolay.sys ksproxy.sys kstvtune.sys ksuser.sys kswdmcap.ax ksxbar.ax mpe.sys msdv.sys mskssrv.sys msyuv.dll nabtsfec.sys pid.dll slip.sys stream.sys swenum.sys wmasf.dll wmpasf.dll wmidx.dll msaud32.acm drmv2clt.dll wmadmoe.dll wmsdmod.dll wmsdmoe2.dll wmspdmod.dll wmspdmoe.dll wmadmod.dll dxmasf.dll msdxm.dll sl_anet.acm strmdll.dll drmclien.dll wmpdxm.dll wmploc.dll wmpsrcwp.dll wmnetmgr.dll wmp.dll qasf.dll wmvcore.dll wmvdmod.dll wmvadvd.dll l3codecp.acm mp43dmod.dll mp4sdmod.dll mpg4dmod.dll [RemoveFiles] npds.zip Any questions, comments or suggestions appreciated. Thanks to TAiN for his codec pack. hfslipcd.inf 2kmplayer2.zip

To clarify, if you have an MSI type hotfix, you place the update into the HF folder and you need to fill the MSIEXT folder with the msi-extractor tool. The tool is a relatively small, and is totally harmless even if you don't have any MSI type hotfixes. Personally, I just leave that tool in that folder and leave it. If HFSLIP needs it, then it's used. But, if HFSLIP calls it and you decided to not have it there, don't cry to me saying HFSLIP doesn't work. @FDV, "didn't know you gots the xp" That's f-n funny! You made it sound like a disease! @Oleg_II - Thanks for your help. Greatly appreciate it. @TAin - In the event that we get our own forum, I'll post directions on how to slipstream lots of codecs into the source.

Lots of stuff can be removed, but the functionality part depends on what you want to run. For starters, ICW, some MDAC stuff, disk tools, Imagevue are some things for starters. Nlite doens't remove that anymore. BTW, my 2k has 10 services running and is fine. Yea yea yea, I know there is more to take out, but I have no time to figure out what else to remove.

@TAiN - Are you running HFSLIP on a modified OS? It seems that fundamental DOS commands aren't functioning with your system, which in turn cause HFSLIP not to work. See if you have EXPAND.EXE in your system32 folder as HFSLIP calls out that one. If you have another PC laying around, try HFSLIP on that instead. Also with your HFEXPERT files, you are putting old WMP codecs in there, and these will overwrite the WM10 codecs you slipstreamed. So be careful on what you do there. If a mod creates our own forum, I'll post directions on how to do the codec slipstreaming properly (which will be at your own risk obviously).

Or on the flip side, adding more components. I just slipstreamed a ton of codecs! It would be cool if the mods created a new forum for this. It's nice having a wmp free system and be able to play all types of files (excluding quicktime and real media because I hate them). @TAiN - Can you please post your "error_report.txt" file. All the info I need to troubleshoot your problems is in that. All I can say for starters is to be sure that you have your source folder properly placed and named. Please post the error report and I'll get back to you. Also, there are two methods of installing DX9. One is slipstreamed and the other is svcpack'd. Instructions for both are on the top of this thread. The choice is yours on which way to go, both methods work great. I cannot say if Gurglemeyer's dx9 package works because I haven't tried it.

@pene - Sorry for not answering earlier, I wanted to leave that malicious tool there because the file generates a regkey when it's run. A workaround is for the user of HFSLIP to generate a REG file and run it during installation. I wanted to make it as easy as possible for people. Personally I don't care if my system has that tool installed because if I install windows, I should not have malicous software on it. To each their own though.

Try my sig for slipstreaming your hotfixes instead of patching after installation. It supports localized settings (ie you can do languages other than English). Hope this helps.

@Oleg_II - If you want to slipstream wm9 and wm10 codecs (NOT the player, only the codecs), then put wmfdist.exe in the HF folder. I install the remainder of my codecs using the HFEXPERT folder. It works great with a full-up hfslip version, but when I run NLITE on the source (very heavily I may add), some codecs don't work properly. When I get free time (not very often) I'll have to troubleshoot it. You can learn more about the HFEXPERT folder on FDVs instructional site. If you're not a novice user of unattended installations, then HFEXPERT isn't for you. BTW, after I run NLITE, I rip out an additional 8 meg or so of extra bloat. Nuhi didn't want any w2k inputs, so I did it myself.

Thanks to Pene for his inputs with the WGA link, which required a little change in HFSLIP. So the Pene version is now up along with FDV's new instruction set (minor change) and first post updated. Remember, please follow the error reporting technique spelled out in the first post so we can help with errors/issues.

Pene to the rescue!!! Thanks for the link. I'll update the script.

@os2fan2 - FYI, the goal of HFSLIP was to create a fully updated source and then rip the hell out of it. Sometimes I use FDV's fileset and other times I heavily reduce using NLITE. However, for my functional w2k setup, I typically run with 10 windows services running and 3 other non-windows services. Everything works fine. The blackviper site does has great info on that sort of stuff though. @pene - Those two files you mention are required for the Windows Genuine Advantage. If you didn't HFSLIP it, then you will get prompted to download when visiting the WU website. You do NOT need it if not visiting WU. You also do not need the WUA if not you don't visit WU either. I honestly don't follow the latest and greatest WGA revisions, but if you have a link for the latest version, please post it or send FDV a PM with the latest link. Also, the extra cabs I have in my HFCABS folder are harmless. I just left them in the folder after I extracted my IE6 installer. Those extra ones don't get processed, so no harm is done. You can put them there if you wish, but those files aren't used anyway. As mentioned in yesterday's posting here, the KB903235 isn't required. After reading what the_guy wrote, I deleted my 903235 hotfix from my HF folder as it's part of the IE update rollup. If it was in the HF folder, no harm is done. @x-pert - This thread isn't really to discuss what hotfixes you need. I would suggest you use hfnetchk as specified in the instructions on the top part of this thread, and on the screens you should have read when you run HFSLIP.

@saugatak - A1) WindowsMedia9-KB885492-x86-ENU.exe isn't really needed, but I put it there anyway. It doesn't hurt to have it there, even if NOT using WMP. A2)I requested FDV to update his instruction set for slipstreaming the codecs, there was an err on the instructions. The user of HFSLIP is required to do manual processing of WindowsMedia9-KB891122-x86-Global-ENU.exe for HFSLIP to slipstream the wm9/wm10 codecs. My list has the fileset listed to slipstream the codecs correctly. BTW, HFSLIP is a hidden gem because it is capable of slipstreaming lots of other things now (I call it HFEXPERT), but you'll have to read the instruction set. I do not entertain questions on HFEXPERT stuff as all the information is there. @pene - Please refer to step 20 of http://www.vorck.com/2ksp5.html for what to do with the delfiles file. @all - Perhaps it's a good idea to include the error_report files on FDV's site. My concern is that someone with a non-english source will try to slisptream English hotfixes which will result in a failed installation. Also, I know I'll get the dreaded question on someone asking why they should slipstream codecs or WUA (or whatever else) when they don't want it.

@kreative19 - Please see the attached file for what to hfslip. Besides have non-essential stuff, you are trying to slipstream IE5 files in there. You can't do that. Please see the attached and you should be good. Also, please do NOT edit the top portion of the error_report.txt file, unless you don't need our help. @Oleg_II - I didn't really check the file names you have listed, but if you visit WU and it says it needs it, then put the file in the HF folder. Also, please see the attached file for a good start of what's needed. @all - If you are unsure or do not trust someone's recommended hotfix list, install a barebones non-hfslipped windows, visit WU and see what's needed. Once you get the hotfixes required, put them into the HF folder and run HFSLIP.

@tripleX - You need to extract FDV's fileset and place the contents into the FDVFILES folder. Once done, run HFSLIP.

@Helios666 - As a friendly reminder of what FDV stated above, please see the proper error reporting technique as stated in the first post of this thread. Without your error_report.txt file, we CANNOT help you. @Electrician - No harm made with my comment the other day. . I thought you had said that you didn't have the sysoc file at all. I would advise to run a makecab command on the sysoc.inf file in your source\i386 folder to bring it up to snuff with a standard source folder. Once you do that, you can remove the the .inf, leaving the .in_ in its place. My point being that others have successfully done XP and had no issues with that file and it seems that your source is different from others. @all - I send FDV the fix for the mshtml and the double command in svcpack.inf. I guess we'll call it the Oleg_II version for this edition.

@tripleX - Thanks for the clarification. Your folders are set up correctly. I think I was just getting a bit confused whether the issue was a FDV or HFSLIP induced error. Perhaps it's time to have another thread for FDV issues and another for HFSLIP issues. @Oleg_II - Glad the directx9 issue went away. It took me forever to figure that one out (which is why it took a while between releases). Thansk for comment about the CMD files in svcpack.inf. I'll check it out. To answer your last Q, yes it is possible to add things into svcpack. In fact, if you create a CMD file, and place it into the HFSVPK folder, HFSLIP will integrate it into the source and do the magic. It's up to you to create the CMD file though. BTW, if you want to override some of FDV's settings for explorer, I would strongly suggest to download the regtweak program in the unattended forum and generate a reg file. Place that file into the HFSVPK folder and those settings will be part of the source. I know about the MSHTML issue. I'll fix it up and get the change implemented.