tommyp

The version of HFSLIP posted yesterday (HFSLIP_60117.CMD) fixes up XPSP1 related issues. Please don't complain about "recommended" updates. After you read the article on them, you'll realize that they aren't needed.

Please use this thread for any HFCLEANUP items. Oleg2 is handling the HFCLEANUP. Thanks Oleg2!!!

I would still like to hear the results of you creating an ISO of your source folder (yes the one that is presently on your hard drive) and testing it in a VMware or equivalent. Before you said you tested your installation CD. That is different. There are lots of times that a cd doesn't copy properly. Sorry I can't much help unless I hear results of your VMware test. Speaking of copy, how much free hard drive space do you have? Have you tried your tests with vmware without using FDV's fileset?

Updated new revision. Some new features. As usual, post any issues you have. Don't forget to read FDVs site on how to use HFSLIP.

If your winnt.sif file isn't set up properly, your $OEM$ folder won't copy over during installation. Remember, FDV's fileset has a winnt.sif file and it will overwrite the one you have in your source. If you have a custom winnt.sif file, delete the winnt.sif from FDV's fileset. Also, I'm not how you have your folder structure set up, but it should be like this. d:\hfslip\source\i386 d:\hfslip\source\$oem$

The JET database is used for ms office. I'll send you the reduction file for that for completeness. Here's a tip.. .codecs are a pain. But this should help. Use process explorer and/or gspot to see what codecs are being used for the stream. I'm not sure what you are reducing set you are using, but be careful about removing the audio drivers. Even though it sounds innocent to remove them, a lot depends on them for audio/video. I ran into that problem a while back with Nlite.

A dumb comment, but if you happen to click on the cmd window (or any cmd window), HFSLIP will pause. Pressing enter will resume it. Dirtwarrior, on FDV's HFSLIP info page is a section devoted to HFSLIP and NLITE and also has info on how to add extra files. I urge you to read it.

Maybe a day late or a dollar short, but I believe the scripten.exe hotfix is needed only if you slipstream ie6. It's not needed when doing fdv's fileset. Can someone verify?

Can you test on a virtual machine? Can you try the script without FDV's fileset? Also, you may want to eliminate scripten.exe from your hotfix folder. IIRC, that fix may be only for IE6 slipstreaming.

Are you sure that your Windows2000-KB904706-DX9-x86-ENU.exe file is OK? In other words, if you are running an 2k machine now, what happens when you double click it? Does it say that it is corrupt?

I'll be a bit brave and try a helpful answer instead. IE has nothing to do with enabling the "big lba". Check out this http://www.48bitlba.com/tools.htm. All you really need to do is make a regedit file and you're ok. In the meantime, if you wrote anything to the drive, consider your old data corrupt.

Bilou, Hold off a few days for testing xpsp1. Tomcat and I ironed out numerous bugs and all is great, but I want to test a bit more before I release the next version. FYI, hfslip won't be able to do the msjava update. I believe msjava is installed by sysoc.inf. You can probably edit that line out and you'll be have no majava; sysoc.inf is not a protected file.

Thanks for the tips Bilou. I did some recrafting over the weekend to help out XPSP1 with the help from Tomcat, and I have a new feature for driver cab repacking (it's the SPx.cab). I'm still testing and hope to release it in a few days. I really like this version, instead of 20 minutes to repack the driver cab, it takes only a few minutes to repack only what's needed.

Oleg2, Do you mean your installed source is down to 100 meg? Out of curiousity, would you be able to compare your actuals with this table.

Try testing your source folder to see if that works. If your source isn't bootable & error free, then hfslip won't fix it.

Read step 6. and the beginner's last step.

Yes, scripten.exe should be in your HF folder and both lists have it listed. To any lurkers out there, the EN in scripten means ENglish.

I have isolated my Quick launch issue. In my winnt.sif I have IEACCESS=OFF because I hate IE icons. When doing this "switch", the C:\Documents and Settings\Administrator\Application Data\Microsoft\Internet Explorer\Quick Launch folder is not created. After installation, if you try enabling the qlaunch, it flags an error, however if you manually create the folder, then qlauch works. I just tried again with IEACCESS=ON and all is great (I do not have to create a qlaunch folder). I have no issues with XPSP1 (using my latest beta).

I don't mean to hijack the thread, but I'll need some technical info on driver cabs. This will help me script this. I'm not sure of the setup process and how setup determines what files it should select. I don't want to get bitten by the numerous things that dx9 adds to the driver cab when slipping it into w2k. Is this what needs to get done? Step 1. identify the files to recab and recab them as SPx.cab (this step is easy) Step 2. With a w2k sp4 as a case in point, should the drvindex.inf be changed like this: In the header section. CabFiles=sp4,driver ---> CabFiles=sp4,driver,spx In the footer section. After the line sp4=sp4.cab add in spx=spx.cab

Should I try making a SPx.cab, where X is the service pack number + 1?

I like how people make devoted webpages for how to convert 2003 server to a 2003 workstation. Using HFCLEANUP it is easily done. More details as I complete my testing.....

With W2K, have you did a start/run and type in THEMES?

HFSLIP doesn't modify winnt.sif and HFSLIP doesn't alter or create any files in the OEM folder. So you do not need to alter or move your winnt.sif file to the fix folder. I have a similar setup here with the OEM folders and it's running fine, so it looks like the prob is on your side. Are you sure that your unattended files and folders are functional? I mean, have you created an ISO from the SOURCE folder to verify if it works? I know that you have had a successful installation with your XPCD folder before, but please verify your SOURCE folder works. If it helps, please see step 13 of http://www.vorck.com/2ksp5.html to see how the OEM folder should be. Also, a stupid comment, you need to install by a CD if your OEM structure is like that, and your winnt.sif file needs the correct switches so the files get copied over during the file copy stage.

Did you place your $OEM$ folder alongside your SOURCE\i386 folder? Are you replacing your winnt.sif file in the FIX folder? Or is the correct winnt.sif file in your sourcess\i386 folder? After running hfslip, is your $oem$ folder alongside the sourcess\i386 folder? Just to verify functionality of your folder and file structure, have you made an ISO of your SOURCE folder to see if your unattend works? The reason I ask is because I have an installation that is totally silent and it's lauched via cmdlines and the $oem$ folder structure. For me, the SOURCE iso and the SOURCESS iso both install fine. FYI, hfslip doesn't alter any files in the OEM folder.

@Squeeto - Since I asked that question a few months back, HFSLIP was updated (thanks to Yzowl) for some great slipstreaming of additional folders, but the folders will only get copied to the %windir% folder. It's not possible to copy files to the Program Files at that stage of the game. Once I slipstreamed Firefox just to say I did.