tommyp

@pain, thanks for the great feedback. I'll see what I can do to incorporate your ideas. I know it's all possible, even with the incrementing/decrementing. I just have to think things out to make the hfexpert folder a little easier to use and create. However, I will keep HFSLIP from automatically generating HFEXPERT. I want this to be a hidden gem. And before you ask, there are other hidden gems in there already that remain undocumented.

Use the latest version, HFSLIP_51027.cmd.

Here's my nlite ini file. I install my drivers aftwards, so I rip it out of the sourcess folder. edit: ini file removed.

You can run nlite on a FDV/HFSLIP source. As ironic as it sounds, do not remove IE in the selections. I'm sure that you can get an sourcess\I386 folder down to less than 120 meg (130 meg if you slipstream your codecs) and not lose functionality for all your applications. I found out that using Nlite, you need time an patience, but the payoff is great.

Can you give me a link? I don't use international languages, so these installers are foreign to me.

@saugatak - The beta hfslip automatically renames your MSIEXC folder to HFTOOLS. It's up to you to fill it up. Depending on what you want to slipstream, HFSLIP will prompt you that you need a tool. Yes, the cmdow link you talk about is correct. Place the exe file into your HFEXPERT\SYSTEM32 folder (you need to create the HFEXPERT folder). The hfslip file talked about in this thread is on the first post of this thread. The file posted has Yzowl's ASPI update too (along with some other things).

Text mode copy was fixed. Please see this link.

@ratba_tardly - I'm guessing the update.exe question is for slipstreaming a service pack into your source. I'm guessing it depends on what OS you are running and what you are slipstreaming. Here is a link that may help you out.

I just checked that hotfix, looks like HFSLIP can't do it. I regret to say that I don't plan on slipstreaming that one either. Sorry dude.

HFSLIP doesn't currently support /q installers. I don't think any of my applications need it, can you point me to an application that needs it? (just for my curiosity). I'll see what I can do about implementing it in the next release.

I have a dumb question. I'm not a computer weenie or anything like that. But what is ASPI anyway? I don't remember needing it for anything, unless I'm too much of a dunce.

@dziubek - Thanks for your help with the non-English versions. I appreciate your time and feedback! @ALL - I uploaded the last of the betas... It has the HFEXPERT\DRIVER folder addition, as well as selectable driver.cab packing. Thanks to Oleg for finding me the right info for this!!! Txtmode copy for XP went from 8 minutes to 3 using option B for packing. Your mileage may vary. Pleae post any last minute items before I send this to FDV for hosting. Thanks TP

@Yzöwl - Thanks for the additional code to help out with ASPI drivers. I'll incorporate that into the next version. BTW, hfslip now comes with your msxml extractor. So far so good. Thanks!

The two versions are exactly the same EXCEPT one version makecab's the new binaries using the regular makecab function. The other version makecab's the new binaries with the makecab and the CompressionType=LZX and other switches. People continually tell me that the CompressionType=LZX type is supposed to make the file copy stage faster, but I can't confirm and don't have time to test it out. So, I'll let the community judge which is better and I'll use the better method in future HFSLIPs. As far as execution time of HFSLIP, one may be faster, but I can't confirm that either. I don't plan on having an unpacked hotfix folder, it will add too many other files to maintain if re-running HFSLIP. Typically what I do when running hfslip is to fire it up and come back 15 minutes later. If you want a significant speed improvement, disable your virus software. I have also tried out xxcopy. It's a great program. However, from what I remember, if you save the executable somewhere else, reload your system, and then launch the executable again, it complains that you ran out of time using the program. I don't want to deal with that. It's hard enough to get people to read the directions This is why I went with what utilities are already available on someone's PC.

Any link for the hotfix? If in doubt, try it out (As Johnnie Cochrin would say).

@NtegrA - About the LegitCheckControl files. You are the first to report errors on this. You need to download the proper legitcheckcontrol.cab file. Please refer to FDV's site for a download link. Please place the correct legitcheckcontrol.cab file in HFCABS and report back. Also, just as the hfslip.zip file contents say, HFSLIP is designed for people who install using a CD. Using it not the way it was designed for will cause some problems. Lastly, be sure that you have WindowsXP-KB887472-x86-enu.exe in your HF folder and not WindowsXP-KB887472-x86-SP1-ENU.exe. You only need the SP1 version if you are running XPSP1. I did some homework and cleaned up a few things. a. There shouldn't be any CAT files in the sourcess\i386. b. Fixed the SP# cabs missing during file copy stage. c. Fixed another XP related hotfix (a non-English issue). d. Addressed NtegrA's concern for file copying. e. Please don't say that HFSLIP didn't cab everything in your sourcess\i386 folder. The files that are un-cabbed in the source remain un-cabbed in the sourcess. For example, with XP, there is exactly 111 DLL files in my source\i386. My sourcess\i386 folder also has 111 DLL files. f. Also, please no comments about small txt files in the sourcess. Using the same case as above, there are 5 txt files in my source\i386 and 5 txt files in my sourcess\i386. I tried deleting them many versions ago with HFSLIP and people complained about copy errors. I'm not going that route again. g. It is not HFSLIP's intent to strip files away. h. LegitCheckControl may appear to not be slipstreamed if you don't apply the registry "correction" during installation or after installation. YOU need to apply the reg tweak to make it happen, I don't do it for you (yet). I NEED YOUR HELP if you want me to slipstream and fix things correctly. I don't have time to test all the variations of installations. There are two versions of HFSLIP. Each version packs binaries differently, but the slipstreaming process is exactly the same. I need to know if "Version A" copies faster or if "Version B" copies faster. This will settle something people have nagged me about for a while. I'll let you guys decide which is better and I'll go with the version that copies faster.

@NtegrA - If you want the ISO created, you need both cdimage.exe and the boot.img files. It won't work with one of them missing. I had a typo in the first thread, it should have been boot.img and not boot.bin. @zerospeed - You said you are missing KB887472. In your HF listing, you have WindowsXP-KB887742-x86-ESN.exe listed but not 887472. Thanks for reporting KB890046. I'll update the script later today. Also about the add/remove software in the control panel. That was done intentionally. @Crash&Burn - HFSLIP intentionally does not create the HFEXPERT folder. It was made to discover by those who visit FDV's site. The HFEXPERT folders listed are the only ones supported by HFSLIP. In fact, there will be some other *surprises* for those who read the instructions in a few weeks. The other surprises will require some reading by the user. Please keep the results coming...

Can you send/post some screen shots of this?

Here's the latest. Slipstreaming: This version slipstreams and applies update INFs a bit differently than the past. It should help out the network installation people a bit more. It also corrects some XP related hotfix issues that came up. Driver repacking: I took some advice from Oleg & FDV about driver repacking. This version repacks drivers and leaves no remnant SP#.cab folders in the slipstreamed source. MORE driver repacking. Oleg sent me some great reading material. File copying during text mode should be faster now. File repacking: Files are makecab'd a bit differently now. I'm not sure if it saves time making the cabs or saves time copying files during installation. Final installation: HFSLIP only leaves one residual file on your drive after installing the slipstreamed source. For the people who cannot live life with a pop-up window during the installation of windows, create a folder alongside HFSLIP called HFEXPERT. Inside the HFEXPERT folder, create a folder called SYSTEM32. Inside that folder, place cmdow.exe. Additions: HFTOOLS: This is the new placeholder for HFSLIP related tools. 1) MSI Extractor tool 2) modifype.exe 3) cdimage.exe and boot.img (OPTIONAL! Put these files here if you want HFSLIP to generate an ISO image for you.) 4) For those running an old version of HFSLIP, there is no need to rename your MSIEXT folder. HFSLIP renames it for you. 5) Future iterations of HFSLIP will use HFTOOLS for any additions/tools needed by HFSLIP. Users should also keep in mind that other items can be slipstreamed/replaced during the HFSLIP process using the HFEXPERT folder. Other items include slipstreamed codecs, alternate applications, additional system32 files, additional system files and additional %windir% files. Any tips/corrections/comments appreciated. Thanks for testing guys... beta is out, see first post.

@dziubek - a) 898461: I found something to correct with HFSLIP. I'm testing it now. B) Activex issue: Can you please check the versions of the windows\system32\GWFSPIDGen.dll and windows\system32\LegitCheckControl.dll and compare them to the revisions of the LegitCheckControl.cab (you need to expand the cab file with winzip or equivalent). If your CAB file versions are older, you need to redownload the latest LegitCheckControl.cab file. c) Please PM me with your email address if you would like to test my latest version that I'm working on. It has a ton of changes, and maybe the issue with 898461 will be resolved. The new version is a bit different, but is improved to make the sourcess a bit smaller.

@dziubek - Good news and bad news. HFSLIP works and MSFT doesn't. HFSLIP found another the MSFT error. I think you may want to revisit microsoft and download the new hotfix for MS05-050. There was lots of troubles with this one (LINK). I took a look at the hotfix I had downloaded the other week, and compared it to the one I just re-downloaded. They silently RE-RELEASED THE HOTFIX, the original one had the wrong binaries!!!! HAHAHAHAHA Hats off to Microsoft on that one. They create their own problems. Anyway, the new file from microsoft will fix the issue you have. Delete the incorrect WindowsXP-KB904706-DX9-x86-PLK.exe and download the new one.

Check the guts of MULTIMED.INF. This is the INF that installs the sndvol.exe (the speaker icon) proggie.

try this: copy SOURCESS\I386\FILENAME1.111/A SOURCESS\I386\FILENAME2.111/B

@Oleg, Have you been playing with that cmd reducing set?

@nite0859 - Thanks for pointing out the hotfix issue. You would be surprised that people would rather have unstable systems and happy WindowsUpdate results. Strange and sad but true. Also, the point you mention about making your own updated installation source: this is exactly the reason why I came up with HFSLIP.