tommyp

Other than nvidia drivers, it works as I have mentioned a few times in this thread. Please refer to post #68. I used a driver program, like drivermax or driver genious or other similar program to get my post windows drivers. They are named oem1, oem2, etc. Those files are the ones needed to slipstream drivers. You may need to edit INF files if you run into probs during installation. Another option is to use the same program and set up a typical OEM structure as stated on the unattended website.

I had some probs with the latest version of nlite, setup stalled at t-9. Perhaps the latest nlite 1.4 is a bit too buggy (which kind of surprises me because nlite always worked fine in the past for me).

I have a dumb question, how do you know that the runonce key is not being run? How do you know that the codecs are not being registered? Can you zip and post your sysoc.in_ file?

I would recommend to include the IE7 rollup in your list of hotfixes in the HF folder. The IE7 installer had some issues that affected the runonce key during setup. The latest rollup fixes the runonce issue. BTW, codecs are registered by the runonce key.

I'm a little unsure of the problem. Are you saying that the files that reside in the HFEXPERT\CODECS folder are not copied to the windows\system32 folder after installing via an installation cd? BTW, the reason I mentioned nlite before was because your zipped file you attached before had nlite comments on it.

It may be worthwhile to rename your root directory from "F:\ƒRƒs[ ` hfslip_xp\" to simply "F:\hfslip_xp\". Also, are you using a clean source? Or an NLITE'd source? (HFSLIP works with a clean, non-NLITE'd source.)

You can look at hfcleanup, details are on hfslip.org. I'll have to forewarn you, hfcleanup is buggy with xp. The easier approach is run HFSLIP and then use NLITE on the sourcess folder.

I had some probs with windows media at one time, and I think I narrowed it down to some obscure sound card driver. Nothing looks out of place with that above file. One thing to try out is to take a registry snapshot before and and after installing wmfdist.exe on a fresh install. Typically I use a nice free bee program called regshot, available on www.softpedia.com. Attach the "compared" registries log to this thread.

You can do an hfslip run in less than 13 minutes when selecting a, b or c? You must have some fast machine there. By chance, how large is your installation ISO? Are you running nlite afterwards? Would you mind zipping and posting HFSLIPWU.INF?

RBCC - Please read my post #63 above.

hfslip.log?

hfslip.log?

There's plenty of info on hfslip.org. I suppose you can visit windows update to confirm installation of all the updates instead of hfnetchk. Or you can use the microsoft baseline analyzer as well. As far as the installer issure, you'll have to post your hfslip.log file, but I must say that you should double check your file list against tomcat76's list, it's up to you to be sure that you included all required updates (see TC's page) and not use ones that you aren't supposed to.

The answers are in the hfcleanup readme file on how to craft your own reducers. You can delete files by filename only and there is a quasi wildcard feature, but there is no keep capability (unless you modify a reducer to not delete it). BTW, it's admirable to keep your installation nice and small, but be careful. If you reduce too much, you can't do too much with your machine. I was on that kick for a while, but I soon realized I had to use the thing, which meant I could not be too aggressive. My 2k installation source is around 100 meg with dx9, ie6 core, reg files and codecs and some appreplacements. It installs totally unattended without user intervention in about 15 minutes (OS and applications).

I would suggest to either use nlite to reduce or use hfslip/hfcleanup to reduce. Don't use both.

I think we'll need a little more description of what you did. For your case 1, you should include IE5 updates as specified on Tomcat76's dynamic hotfix list. If you are running NLITE on the sourcess folder, be sure to use the files to keep as specified on www.vorck.com. Be careful with bugs' icon pack, it could be buggy with FDV's set (I experienced this at one time so I had to manually recraft some setup files so the icon pack would work). You should take one step at a time, the first goal should be to get a functional 2k source. Once that's done, you can run NLITE on the sourcess folder. Your second attempt is interesting, it shows that your source is modified somehow (there's exta files and there isn't a ident file in the root of the source folder), and HFSLIP may not function correctly with an adulterated source. You should remedy that before moving trying again. Also, if setup is complaining that some driver is missing, you probably reduced a little too much (read the readme file in the cleanup zip file you used).

The only non-problem problem about using NLITE on the sourcess file depends on what you are reducing with NLITE; there is a list of files to keep that is listed on www.vorck.com. One of these days I should update the hfslip.org site to include the same information. But there are no problems with replacing the two files you mention, but I haven't tested it with a dual boot system.

It's been tested and working for quite some time.

I just tried directx_aug2007_redist.exe with winrar and all extracts fine here too.

I just downloaded it too, all is OK here. This is a rather large file, you may want to increase the size of your cache/temporary internet files so IE can download it properly. I found that I used to get corrupted files if I had the cache set too small.

Destickied.

Destickied.

If there aren't any updates to this thread in a week, it's time to de-sticky it.

If there aren't any updates to this thread in a week, it's time to de-sticky it.

http://www.hfslip.org/advanced.html