tommyp

Ummm, you say you didn't use HFSLIP, but you are making a totally false statement here. HFSLIP does NOT use the $OEM$ folder. It slipstreams your files into the i386 folder, just as RyanVMs does. As a side note, HFSLIP does more OSs and all languages. With HFSLIP, you could also slipstream one hotfix or you can slipstream a hundred. The best part is that each patchday festival (2nd tues of each month) you download the update(s) from M$FT, run HFSLIP, run NLITE and you're done. HFSLIP was written to be NLITE friendly (and it always worked fine for me and others). Codejunkie, why not give HFLSIP a test run?

Super - If you place the WMP10 installer and any updates for WMP10 into the HF folder, HFSLIP will slipstream WMP10 with all updates. However, if you place the WMP10 installer in the HFSVPK_SW directory instead, then you'll need to install any WMP10 updates after you installed via your sourcess folder.

HFSLIP can parse INF files automatically. To install this inf to your installation source using HFSLIP, you could place this INF file in the HFSVPK folder. HFSLIP will install the HFSVPK INFs at T-13. BTW, HFSLIP will install HFSVPK REGs at T-13 too (this means that the inf & reg files will affect all users).

saugatak - Yes there is a way to remove AU with HFSLIP. Please give me a few days to verify something with HFCLEANUP.

At present, the current HFSLIP release does not slipstream this. If this is indeed an update, I'll incorporate it. Please advise if this is an update.... I don't use WU so I can't tell.

I just tested current release of HFSLIP and it unpacks it fine. Are you sure you got these two files from microsoft?

One option to see what file in your HF folder has WMP.DLL is to search HFSLP*.INF files in the sourcess\i386 folder for INF files that contain the string wmp.dll. You can do this by the search window. Open the INF file up and read it with notepad and get your KB article for it.

Sorry I posted some incorrect info. I updated & corrected my post. Thanks super magician.

If that file is an "extra" meaning that there no muweb.dll (or muweb.dl_) in your source\i386 folder, then you can place it in a folder that you need to create alongside your hfslipxxxx.cmd file: HFEXPERT\CODECS. Any files you place here are copied to the system32 folder and registered. Please refer to the HFSLIP info site about codecs (step number 15). You need to download some tools for your HFTOOLS folder when you do this (modifpe). All this info is on FDV's instructional site. If that file is part of the source\i386, then rename your muweb.dll to muweb.dl_ and place it into the fix folder.

clintb - Your best bet would be to look in the unattended forums for a switchless installer that installs via svcpack. If you cannot find one, just install it later on in the process.

teotwawki - please post back after testing with the current version. Very few of us do the multiboot cd's.

Are you running any crazy winnt.sif and/or regedits and/or cmd files during your installation? I do not have the initial sign in problem that you are talking about.

If you want cdimage to work automagically, just put your BOOT.IMG file into your HFTOOLS directory and move your BOOT.BIN somewhere else. HFSLIP works like this (and in this order)... 1 If it detects BOOT.BIN, it creates the image using MKISOFS and exits. 2 If it detects BOOT.IMG, it creates the image using CDIMAGE and exits. 3 If it detects neither, it exits.

I have a stupid question. Did you download your wmp installer from microsoft? The reason I ask is because it works fine for me.

New version released. Mainly bugfixes, but the implementaiton of some key parts of the script were improved by Tomcat76.

I know these are dumb questions, but I have seen bad copies from a cd to hard drive. Are you sure that your original source driver.cab and your sp4.cab are ok? Have you tested your source folder to ensure that your source is OK prior to slipstreaming? Any luck on attaching your error_report file? Can't do much more without it.

I meant the LegitCheckControl.cab file. What files are there when you manually open the cab file up?

Can you open your wga cab file with your favorite decompression program and see if the legitcheckcontrol.dll is inside it? If it isn't, make sure you get the proper cab file.

Super-Magician - Try it now. Your prayers for WMP10 are implemented. hehe

Strange how I can't edit the first post on this thread. I haven't time to figure out how to do it today. The new version is up, HFSLIP_60206 (see link on first post of this thread). Brief changes.... WMP10 svcpack'd (for those who want it) DX9C slipstream section revamped. Now works with 2ksp4, xpsp1 and 2003 gold and as usual some odds and ends.

Sounds to me like you're trying to slipstream the incorrect fixes (like putting an xpsp1 hotfix in your xpsp2 source). You may want to revisit the stickied links on the top of this board to put the right files in the right place. After reviewing your error_report, it's quite evident that there's some unneeded files there.

@Squeeto - PM me your email addy and I'll get some add'l reducer files for you to test out (if you like testing).

Strange. Are you sure that your wmp10 installer is fine? You test it by running wmp10 in your VM. I got the commandline switches from googling. Perhaps they changed the syntax around because I've seen numerous varations all over the msfn board. I haven't time to test xp installations today. If you want to help out the script project, it would be great if you can come up with a commandline switch that works. Test various commandline iterations on a non-wmp10 installation. Any help is appreciated.

There's more than one way to reduce windows . There is a hidden option in HFSLIP called HFCLEANUP. It's an alternative to reducing if you don't mind doing some legwork. The fileset I'm working on reduces far more than NLITE does. If you do this, you'll kill IIS. To summarize on eliminating IIS and using NLITE, do this: 1. Create a folder alongside your hfslip cmd file called HFCLEANUP. 2. Download Oleg2's mini002.zip file from here and extract the IIS.REM file to the HFCLEANUP folder. 3. Run HFSLIP and choose the A, B or C merged driver option. 4. Nlite your sourcess folder.

When using HFSLIP, how do you answer when prompted on how to repack the driver cab? I would recommend to make a merged driver.cab because I'm not 100% confident that NLITE reduces driver.cab, sp4.cab and spx.cab. If you chose the merged cab option with HFSLIP, NLITE works pretty good.