tommyp

Do a poll FDV. I'd be interested in seeing if there really is a need.

Squeeto, For the community's info, can you tell us what your commit & thread usage is when using bblean? Close your browser before running this test. Thanks!

I have no idea on how to make it stick (see my post #36 of this thread). Maybe a cmdlines command? Cmdlines happens after svcpack.

Squeet. The reason you only had a screen with a mouse is because there was no shell (see next para). Remember, there are two things that explorer.exe does: the shell and the file manager. I tried various ways to delete msft's explorer.exe and found a few things. You give up all context menus in the "alternate" windows explorer. This is a big minus in my book. I routinely do a right mouse click and search. This feature is gone. Right mouse click on INF files is gone too. Also, I tried swapping the shell by altering the hives, running infs and running regedits, but the explorer.exe shell still wants to load up at the first boot. So if there is no explorer.exe that acts like a shell, then you'll get a blank screen. The reg setting for the shell is getting set somewhere else, perhaps it's hardcoded in some setup exe file? One thing that is important with slipstreaming BBLEAN is that you remove any files with spaces and removing files that have 4 character extensions. Otherwise, you'll have a bad txtsetup.sif file. I hardly think it's worth altering hfslip for this only because the shell swap doesn't seem to readily work properly. Perhaps an sfx file is better for this? I don't know. A crazy idea that may work is to place the contents of the bblean folder into HFEXPERT\WIN and rename the BBLEAN.EXE file to explorer.exe. In other words... HFEPERT\WIN\EXPLORER.EXE. I haven't tried this though and I'm not sure how bblean would act if it had a different exe filename. Anyone want to test it?

A few quick notes. ERROR_REPORT is used by the HFSLIP developers to see what the user is doing. It does not report any problems encountered during the hfslip process. IIRC, you may want to recheck your hotfixes and apply the ones that really apply to your machine. I'm sure that your machine does not have every problem that the hotfixes are addressing. Perhaps a good start is to slipstream the critical fixes (with the proper MSFT filenaming scheme) and test the ISO. Then add more and more hotfixes (with the MSFT filenaming scheme) and test the ISOs along the way. Personally, I have a funny feeling that your hotfixes don't have the proper filenames, but that's just me. On a sidenote, if you want to disable some optional things from being installed, you could use a winnt.sif file.

Edited the first post for the new 2k reduction fileset. Enjoy your fresh and lightweight 2k.

Are you sure you are using the latest test version that TC has posted? It appears you are using an older version. During installation when it is detecting hardware, press shift+F10. This brings up a command prompt. CD to the windows folder. Then cd to the hfslip folder. Tell us if the %windir%\hfslip folder exists. If it does exist, run a DIR command and see if there are a bunch of INF files there.

He needs the scriptDE.exe in the HF folder. By the selection boxes, I mean that the file is mandatory if you are slipstreaming IE6 and with that said, you should not be able to deselect it. If you aren't slipstreaming IE6, you do not need the scriptXX.exe hotfix. The scriptXX.exe has the dlls (and installation infs) specific to IE6.

Yes, those were cleverly named such that HFSLIP can support up to 800 hotfixes.

Amen! HAHAHA. Glad it all works out now. TC, thanks for fixing the empty HFEXPERT and other advanced folders.

You need the script version for your language. For english it's scriptEN.exe. For yours, I would presume it's scriptDE.exe. This file is a requirement for IE6 to slipstream. TC, on your hotfix site, the scripten.exe is needed if you are HFSLIPing IE6. If you aren't doing IE6, then you shouldn't slipstream it. In other words, it should not have a little checkbox by it if IE6 is selected.

I get a 100 meg without using nlite . I'm too lazy to slipstream my drivers, but they are only 10 meg anyway.

TC is correct, hfslip doesn't do anything with VGX. It is installed via syssetup.inf (a protected file that HFSLIP doesn't touch). I have a few applications that need VGX (and they won't install if it's not there), so i don't remove it with NLITE. Besides, now I use alternate methods to reduce my 2k sourcess . Can you say 100 meg ISO? He uses hacked setup files to disable SFC during setup too.

tjabocom - Do you have an empty folder called HFCLEANUP? Do you have an empty folder called HFEXPERT? If you do, delete them and try again. I had a boot.bin file in my hftools so I never really see that part of the script run. TC, can you take care of the above change? Thanks for the inputs Kramy. We always appreciate constructive criticism.

Probably a stupid question (I'm full of stupid questions), but are you doing a CD installation? Are you messing around with the dosnet.inf file after you run hfslip? I haven't seen TC's script he sent you, but if you are monitoring dosnet.inf during hfslip, you should not keep your dosnet.inf open in a text editor when hslip is running.

Stupid Q, but do you have a HFCABS\MAILNEWS.CAB file? If you do, is it corrupted? (There are 54 files in the cab). While your checking out that cab file, check the other required CAB files required for IE6. Use Tomcat76's signature as a guide for what cabs are required. Side Q, is your current operating system (the one you are sitting in front of now) reg tweaked to disable the 16 bit subsystem?

Yep, you're right. Sorry. Those MSOE updates used to drive me nuts. Perhaps it's the IEUPDATE or VGXUPDATE command?

TC - If there is an OE prob with windows update, the OEUPDATE.EXE KB######.INF command must be issued. This command was in HFSLIP a while back, but was removed. Perhaps it is a good idea to add it back in.

Extract the hotfix using winzip or eqivalent, and run a command... OEUPDATE.EXE KB#####.INF

Are you doing any registry changes to defeat 16 bit processing? Have you tried hfslip without any of the items in your hfsvpk folders? Are you running nlite on the sourcess?

Did you download your mp10setup.exe directly from microsoft?

TC - you have mail.

Both the 2k rollup update AND the windows update rollup have msxml3. Filedates are different between both files, but they both have the same revision. Go figure. Note to TC. If the rollup isn't in the HF folder and you aren't slipstreaming IE6, msxml3 needs to be added to the txtsetup and it needs to be registered.

The SOURCE folder should be the contents of your CD. So if your original CD has a folder called kiki alongside your i386 folder, then your source folder should have a folder called kiki folder alongside your i386 folder. The only folders you need for a barebones installation is the i386 folder AND you need the ident files from the CD too. The ident files as specified here http://www.msfn.org/board/index.php?showtopic=70109 There are other files and folders that you can delete too. Information for other files to be deleted are on the unattended.msfn.org site.

By no means is this version final. 2k/ie6/hfdrv and no driver merge and no cleanup. OK 2k/ie6/hfdrv/driver merge and no cleanup. Not OK. (txtsetup error).