tommyp

mim0/Muppet Hunter - Just a heads up. HFSLIP can slipstream WM11 codecs and not the player for XP. This could wreak havok if one were not using hfcleanup (I got my hfcleanup'd install down to 160 meg with all my codecs and drivers!!!). I'll come up with a list of what's needed codecwise for this.

New beta is up for some miscellaneous changes/enhancements for XP. If you are like me and do not want WMP11 but you need the codecs, here's what you do. Create a folder called WMP11. Inside it, place the wmfdist11.exe file (you gotta extract it from the WMP11 installer). There you go, WM11 codecs. So you can remove WMPlayer in its entirety and use a real media player.

Here's a little tutorial that was based off of a few other HFSLIP contributors. There are other ways to do it, but this method works for me (and it's the easiest). I'll try to keep this post updated if need be. Install a program called DriverMax (it's a freebee program). Run DriverMax and export all your drivers to a convenient folder. Locate all your post-windows drivers files as follows. Go through each of the folders and subfolders. Look for OEM#.INF files. The OEM signifies post windows installation driver files. Open the OEM#.INF file and look for the [sourceDisksNames] section. Put a semicolon(s) in the lines just after it. Right after the [sourceDisksNames] line, add this line: 1 = "Windows CD",driver.cab,,"\I386" Please note that the 1 could be different, but just use the same number that was just semicoloned. Save the file. Rename that INF file to something descriptive, e.g. Video_Nvidia.INF or whatever you want. Don't use spaces in the filename. Create a folder called HFEXPERT alongside the HFSLIP.cmd. Inside HFEXPERT, create a folder called DRIVERCAB. Create another folder inside DRIVERCAB, e.g. Video_Nvidia. Don't use spaces. Copy the contents of the extracted driver folder from step 3 (i.e. renamed OEM#.inf file and all the other files except for that xml file) to the last created folder (e.g. HFEXPERT\DRIVERCAB\Video_Nvidia folder). When running HFSLIP, you'll need to select driver compression A, B or C. See list below for some oddball errors I found, with working solutions. If you experience GUI setup of windows that complains that some files are missing, you need to populate the hfexpert/drivercab/insertnamehere folder with the missing files. I have found that the driver extraction programs aren't perfect. If you are using HFCLEANUP to remove windows drivers, you can also add them back in with HFEXPERT\DRIVERCAB\InsertNameHere. When doing this, you'll need to look for INF files that aren't called OEM#.INF. You have to be a little careful in reading the hfreducer title and the driver description for what to put back in. I am using hfcleanup and adding things back in. My drivers.cab file is 15 meg I have not verified this procedure for all scenerios so there could be errors. If there are errors, post here and I'll try to help. If need be, I'll updated this post to capture the important items.

Merry Christmas y'all.

Looks like you got the source in two places. You only need it source. You should probably leave the path as default when prompted on the screen too, unless you are trying to install via a network (unsupported). Last but not least, double check your hotfixes against Mimo's or muppet hunter's list. I see two foreign updates there.

Try running mim0's hotfix checker to clean up your hotfixes (if any). It's probably worthwhile to remove the "extras" to verify that your basic hotfix install is smooth before running additional items. One final note, let's concentrate on getting hfslip to work for you correctly, before you start nliting it. There's and old adage, we must learn to walk before we can run.

mim0 - the wmfdist95 is only for wmp9. It's not needed if you use wmp11. Actually, to be safe, you probably should not include it if you are using wmp11.

Here's a monkey wrench for XP. If you use wm9, you can upgrade to the v9.5 codecs using wmfdist95.exe in HF. These codecs don't have as many DRM as WMP11 does. HFSLIP already takes care of necessary hotfix updates if you use wmfdist95.exe.

Relax everyone. There's two maintainers of XP hotfix lists (mimo and muppet hunter). FDV is hosting muppet hunter's list, mimo is hosting his own. On a sidenote, I get a kick out of the unattended MSFN board that has a stickied windows update list where the last post was sometime in March. I'm not sure why an outdated thread is stickied, but what do I know.

gluon - if there's new binaries (i.e. dll's or ax's), they are registered via hfslipwu.inf. So, if there's a new binary there, it's gotta be removed. If a dll/ax or whatever you are removing is called out in another inf and it's not present, setup will not parse that particular inf file. This is a little tricky. To answer your Q regarding the commented out sections, I had a hard time editting those files with the script. If those hive's aren't editted correctly, you'll get a bsod right after txtmode filecopy. I suppose you can tread the waters, but the waters could get quite rough. Oh, dosnet isn't parsed because iirc it's not needed for cd installs. It was a time saver.

mimo - This is an excellent tool! Thanks for helping the cause. Can you do me a favor? I've been running with some hotfixes that I intentionally prefix (e.x., optional updates are named opt_, ie6 hotfixes are ie6-, etc). Prefixing the hotfixes readily identifies ie6 hotfixes, which aren't typically named like ie8 ones. Can you change your script a bit to put a wildcard before the actual filename when doing the commands? Using a wildcard will not be a prob for those who do not rename them. This isn't a critical change request, it's one of those if you feel like it type of changes.

The extra dx9 stuff is all the DLLs you posted up in the first message of this thread. HFSLIP detected it and put it into txtsetup.sif (which is what is used to copy the files over). The final result is that the dll's are placed in system32 (via txtsetup.sif) and are registered (via hfslipwu.inf).

gluon - you'd need a REM for that, not an RDV. The RDV is to remove stuff from cabs. The REM filters stuff out of the i386 and some inf files. You'll also need a RIN that looks like this: mmdriver.inf;x You'll need to find out what other INFs call out the other ax's. You'll need to filter those INFs out with the right RIN callout. Sorry, I don't have a list of that stuff. If you want to start a hfcleanup thread, please do so. This is a WU thread.

Whenver I somehow get logged off, the only way I can get back is if I clear the cookies out and relaunch my browser. This prob only seems to happen after using the google search window on top of this page (or any other google search that yields an MSFN thread). 95 times out of 100, when I see a text only thread (as opposed to linear/standard/outline) I get logged out. I have to shut my browser off/clear cookies and relog back in. It's more of a pain... sometimes I just use two different browsers, one to post threads and another one to search threads.

new service pack = new modded dll's. Cheers!

There was no change in code for dx "extras" processing, and there wasn't any change in HFAAO processing either. I'd suggest to remove your hfaao cab files and rerun so you can locate and remove the offending cab file. To me it sounds like you are slipstreaming it (via hf) and hfaao'ing it (via hfaao). Select one method you like. The activex killbits stuff is still sort of there, but it not the latest and greatest. It's easier to keep the killbit hotfix in the HF folder instead of updating the code every month. If there are zero copy issues, then it could be two things. Either it's not supported by hfslip (i.e. not a critical update) or it's just processing an INF file (such as killbits). For now, I'll assume that you have checked your list against the stickied xp hotfix lists and removed the nonessentials.

Kiki - If the extracted exe file has one of the hfslip supported switches, then all you need is the exe. I would rename the exe file so it's not a long filename though.

Kiki - MBSASetup is a program like MS Office, Nero or any other program. It is not a windows component.

This board isn't dll swapping central. Look elsewhere for your files.

M2 - can you do me a favor? Can you see what file versions of wmvcore.dll you have on your system? Also, can you post your KB952069.log file too? Thanks!

This is more of a tutorial of how to do unattended installs and isn't really hfslip releated. Three options come to my head. First - Why not extract/run the program and then use the hfexpert/codecs folder. Or in other words, make your own codec package out of that. This method is true slipstreaming. Second - If that's not what you want to use, why not make a self extracting sfx with a built in commandline that automatically installs it without any switches? There's lots of tutorials for that on the unattended site. Third - Place the file in svcpack, but rename the file with a different extension. Then create a cmd file inside svcpack where it first renames the file back to normal and then runs the switch that shark provided. This is similar to #2.

Yes, it was replaced some time ago. The hfslip site has this info.

kiki - I'm sure m2gd's fix will work fine. If it works on 2k, then 99% of the time, it will work on xp. For your 2nd q, if the installer switches are known and you place it in the right svcpack folder, it should get processed. To be safe, use 8.3 file name format. m2gd - i see that you put the 958470 in sw1. Can I ask you if you are slipstreaming wmp9? Or just the codecs?

969084 is very far from a critical update. If you read it, it allows someone else to remotely control your machine. If that is really what you want, and you want your OS to be open to intruders, you should put it into hfsvcpack_sw1. I can't wait for msft to dig themselves out of this gaping hole that they started digging.

The code for the old hfslip is quite larger, so I would expect more trouble. So far, there aren't many requests for ie8 in 2k3 server. As FDV would say - a server OS should be just that, a server. Why should it have a unsercure browswer on it? Let it rest for a bit, I have some real life tasks to take care of besides this. LMK if all installs fine on a real machine. I'll post a new final.