tommyp

Oopps, I meant to say [type] hfcleanup.

Silverlight = not critical update = not supported. Sorry Kiki.

Thanks for the inputs M2GD. Yes, the item you bring up in #4 should probably go into sw1. I haven't tested all scenerios with item #3. It depends on what WMP version you're slipstreaming and what winnt.sif switch you have. It seems to make a difference. Are you saying that if 952069 is in HF that it does not slipstream properly? What version of WMP are you using? Also, according to my findings, 937894 was replaced by 951071 which was further replaced by 971032. All the KB articles say that anyway. Is this a msft error?

Hi Kiki. HFEXPERT is manually created, it's intended for the folks who read about it from the website. At the current time, there isn't any XPSP3EXT.zip files. Most people who use sp3 do not even bother with that aspect. I suppose if you really wanted one, you'll need to go through txtsetup, drvindex.inf and spx.inf and locate every file. Whatever file you didn't find is extra and that would be part of the xpsp3ext fileset. I do not think it's worth the effort though.

It's probably easiest to just place mrt.exe into the HF folder. Personally I do not think that MRT does anything to the system other than take up filespace. The OS does not call MRT or run MRT. The only thing MRT.exe is used for is to keep WU happy. This is why I classify it as a worthless junk update. If the same issue was for a critical update, then updating the script would be needed. For now though, I think all is fine. The intent of slipstreaming critical hotfixes is done. I think we should be good to go at this point.

IIRC, the patched sysssetup.dll was there so that empty folders aren't created in the windows directory. It all depends on how much you are reducing for requiring the need for it. I do not believe that anything in "replace" is modifype'd.

Yes, you're right. Right after the driver cab generation the script process the post-cmd files. It just so happens that your post-cmd file deletes triedit and a mess of other files too. Remove that cmd file and you'll be fine. A couple of extra files in the sourcess won't kill you. Oh, you need mrt in HF. Nothing else needs to be done. HFSLIP can't decompress it, unless you can find a switch for it.

I was able to borrow an x64 disk and tested hfslip64 with it but didn't install it. I have triedit.dl_ in sourcess\amd64 at the end. Very strange. True I do not have all the hotfixes you list, but the file is there. I'm not sure how to address the copy issue you are having. Maybe as a workaround, and as a rather poor bandaid, create a folder called replace\amd64 and put a cabbed version of triedit.dl_ there. Or maybe perhaps your HFSLIP64_POST_DelObsBin.cmd in hftools is trying to delete it for you? I don't know dude. In any event, please double check that HFSLIP64_POST_DelObsBin.cmd file, or maybe delete it all together. If things work nicely, your WU should be satisfied. Hope she works....

Well, hfslip can be configured to to automatically do the drivers, if set up properly. If there is accompanying software, then you can do that separately. Most of the time, you do not need to use software provided by the hardware manufacturer. There is a slick program called installrite that I have used. If you get the hang of it, you can really do cool things, like install the software, configure it and then make the installer. Works like a champ. And it can work in svcpack. Personally, I install my programs at the first logon. My silent installers are on my D partition where each installer is called via a cmd file. Total windows install time for me w/all programs is about 15 minutes. The only thing I have to click is which partition I want to install windows on. After that, the next time I touch it, all software is installed.

Another option... check out step 9 of hfslip advanced. When running a post-cmd, you can run a command that is parsed just before the ISO is created. So, if your iso takes 40 seconds to create, then when doing a shutdown cmd, make sure you allow enough countdown time for the iso to create before the system shuts down. There ya go. It's already there. I guess you can config it to make your PC text message your cell so you know when the iso is ready too. The options are endless.

HFSLIP supports various switched and switchless installers vis the HFsvcpack folders. Remember, the intent of hfslip isn't to install programs, it's to install windows. To create silent installers, or to make automated installers, you should visit the msfn's unattended forum. There should be lots of info there on how to generate them. As far as driverpacks goes, I haven't used them. I've been using oleg's method (drivercab) for quite some time and it works great. I had some tips on how to generate the appropriate hfexpert\drivers & inf files in that thread. Basically I created separate folders inside drivercab (video, sound, etc) and inside each of those folders I had the apprioriate INF and other driver binaries. Hint - when creating your fileset, look for oem1, oem2, oem3....oemx. The oem's list the files and such what you need. I suppose most of that info was from that thread, but if you want to do it manually, load your OS on your target machine, and go through the INF directory. Then pick and place all the binaries into hfexpert\drivercab\....

You're a computer tech who doesn't know how to make a script to turn off a computer after a program is executed? Tell me, are you using hfslip for personal use?

I suppose you could extract each relevant hotfix, compile the appropriate INF files for each hotfix, boot via a bartcd, copy the binaries to their home, reboot to the real machine, apply the INF files and you'll be good to go. Too much work. It's easier double clicking each hotfix. When done, go to your windows folder and delete all the hidden hotfix uninstaller folder. Visit the hfslip.org website for a tool called hfnetchk. It's a small batch file that will tell you what hotfixes need to be applied. It's easier doing that than using WU.

One last question, and pardon if I have I asked this before. Does triedit.dl_ exist anywhere in the sourcess directory? At one point I thought you said it did and another time I thought you said it didn't.

I'll try to tackle this stuff, but I'm not a msft expert. These aren't really HFSLIP questions btw. 1. If installing manually, there is no order. Newer binaries will overwrite old ones. However, if you install IE6 after the fact, you'll have all the IE6 hotfixes to install. 2. There is not prob with installing hotfixes twice. No change to your OS will happen. 3. You're on your own with msxml. There's several types of msxml. For hfslip to work, you need the msxml hotfixes listed. I suppose you can just install them manually, but no guarantees. 4. If you are installing wmp codecs, you need the codec hotfixes that are listed on the hotfix page. 5. It does not matter. You can install everything and then reboot when done. 6. It will be easier to burn a new image than installing all the hotfixes manually. 7. You are on your own with how to install windows. Ask that one in the right forum.

I have a dumb question for you. Did you install the hfslip generated image to verify that the language is english? Or are you just going by the hfslip generated folder names? The hfslip generated foldernames have no bearing on what language you are running.

Can you manually move mrt.ex_ from i386 folder to the amd64 folder and then open txtsetup.sif (its in amd64). Change the mrt.exe = blahblahblah to mrt.exe = 1,,,,,,,2,0,0 Make the iso and retest. If you see any errors other than triedit.dll, let me know. All the folders for x64 is a bit confusing and I'm trying to figure the nitty gritty with x64's txtsetup.sif. It's a little different than x86 machines.

Ok, I figured it out, sort of. MSFT changed their language naming scheme. Boy, they sure like changing file and folder names. Nothing like being consistent. Way to go microsoft! Here's a fix you can do while I figure out how to automate things. FZ500 - Open the script. Find REN TEMP\sp3qfe\msimsg.dll.%LG%-*.mui msimsg.mui and replace with REN TEMP\sp3qfe\msimsg.dll.zh-tw.mui msimsg.mui AJARBAS Locate the same line of code as above and replace with: REN TEMP\sp3qfe\msimsg.dll.pt-br.mui msimsg.mui LF I'm not sure what "traditional" Chinese is, but maybe one of these two makes sense: Chinese (China) - Change line of code to REN TEMP\sp3qfe\msimsg.dll.zh-cn.mui msimsg.mui Chinese (Hong Kong) - Change line of code to REN TEMP\sp3qfe\msimsg.dll.zh-tw.mui msimsg.mui Save, re-run the program and you should be OK. Good luck!

jvidal - Can you do me a favor? Can copy the triedit.dl_ from source and place it into your latest and greatest sourcess folder. Make the iso and see if you get the triedit.dll copy error. No need to install, just do the txt mode copy portion. After that, extract the MRT hotfix and place the MRT into HF. Run the new beta I (attached). Hope this does the trick and doesn't fart out this time. If all is cool, you'll just see a triedit.dll copy error. WU should report all is installed. Just a little FYI, I'm not too familiar with x64, so the folder structure is strange to me. I guess with anything new it would be strange. So I had to take a stab at what I thought was right. Namely, placement of the mrt.exe file via txtsetup.sif. I had the option of one of two places. Hopefully I chose the right one.

fz500 - I'll assume that you are having the same prob as L-F. He hasn't chimed in so I don't know how to answer him. Whatever the case, I'm not sure what Windows-zh-TW-KB943729.exe is, the filename format doesn't look like a normal microsoft release. I do not recall if it is a supported hotfix or not. It's probably safer to delete it. I'm not too sure what the prob is, it seems that the txtsetup.sif is correct. Is the file missed in text copy mode in the sourcess folder? Are you doing a clean install from a boot CD? AJARBAS - Your txtsetup.sif looks fine too. Is the file missed in text copy mode in the sourcess folder? Are you doing a clean install from a boot CD? The bottom line is that languages that aren't english or don't use a standard qwerty keyboard are harder to digest in the script.

Sounds like an FDV question. FDV, can you chime in?

Thanks dude. I think I have the answers for everything except the triedit.dll. Let me figure out how to automate things.

Ok, I think we're getting there. Let's tackle automating the 974112 hotfix next. Try this.. using that modded H (the one with the line removed), run the script as-is and install the ISO. You'll see triedit and ie8props copy errors. See if WU reports that 9741112 is installed. Next, extract the 890830 and place the mrt.exe file into windows\system32. See what WU reports. Next, for something interesting, delete the system32\mrt.exe file and create a new text document in system32 called mrt.exe. See what WU reports. Save the VM if you can.... If WU says that 974112 isn't installed, then open the script up and locate this: TP_F special fix for KB951376. Just before that line, add this: REN WORK\CDROOT\%FLD64%\wstrmdll.dll strmdll.dll >NUL COPY\Y WORK\CDROOT\%FLD64%\strmdll.dll WORK\CDROOT\I386\wstrmdll.dll >NUL Save the script and run it. When run, you'll get the ie8props and triedit copy errors again. See what WU reports. Save the VM if you can... Let me know how far you get.

L-F - Please zip up and attach your hfslip.log and your SOURCE\I386\PRODSPEC.INI and sourceSS\i386\txtsetup.sif files. Thanks.

Are you using french hotfixes? If not, use the french one. Are you kiling IE with FDV's fileset? If yes, then FDV should chime in, his fileset may have some english in there.