tommyp

Whew! I'm trying to see what the 974112 hotfix does and what files WU wants to see and how to get the right files in the right place. The prob is that the extracted hotfix has only the wstrmdll.dll & not the strmdll.dll, but WU seems to want 2 files. a) Please post your svcpack\hfslip.cmd file... and while I dissect it, try B, C and D. B) In the sources folder, look for the wstrmdll.dll and strmdll.dll files. You may need to extract them. See if they are version 4.1.0.3938. They probably aren't. Rename the sourcess to sourcess1 (we'll use this later). c) Remove this line.. MOVE WORK\CDROOT\%FLD64%\strmdll.dll WORK\CDROOT\I386\wstrmdll.dll >NUL save and run the script. Extract the wstrmdll.dll and strmdll.dll and see if they are version 4.1.3938. If they are the same, then install the image. If not, rename this sourcess to sourcess2. d) Go back to sourcess1, rename it to sourcess. Extract the KB974112 hotfix (I use a cmd prompt with a /x switch). Navigate to the sp2qfe folder and rename the file there from wstrmdll.dll to wstrmdll.dl_. Make a copy of the wstrmdll.dl_ and call it strmdll.dl_. Place both files into the sourcess. Run the script and type in MAKEISO (instead of i have read...) to make an iso to install onto a VM. e) If you are testing a VM iso image, prior to making an ISO, open txtsetup.sif. Locate line ie8props.propdesc = 1,,,,,,,2,0,0, and delete it. Run the script, but type makeiso instread of i have read... to make an ISO. See if IE8 works properly on the VM. I'm not sure what the file does.

No need to test I. It's the same as H but the ::'s were replaced with REMs. And yes, you'll have errors with the triedit and the ieprops. I'll tackle that next. I know what to do, but it's tricky to test.

I think I see what's doing now. For some reason, the ::'s don't always act as a remark in a cmd file. REMs work though. Try this...

I think I found a workaround to test the script, witout an x64 disk. Well, sort of anyway. Can I get a copy of your source\amd64\sysoc.inf & source\amd64\drvindex.inf? Sorry to put you through this, I think I was making too many changes at once...

Our text editors are different, so our line counts are off. Search thru the script for ieprops.propdesc. There's two lines under ::tp_f. Delete those two echo lines after that. FWIW, all the changes I did this time have a :: tp_f there.

Was it closing at the same point as before (just as the WMP updates were getting parsed)? Let me get back to the drawing board here.

Try this new beta out. Hopefully it remedies the malware tool and the bluetooth stack hotfix. You'll probably see the triedit.dll copy error still. When visiting WU, you'll more than likely just see that KB974112 is still not applied. Let's test this out before going further. If you see that the malware tool isn't installed, please post your svcpack/hfslip.cmd file.

Yes, this helps alot. I can't quite figure out the triedit thing yet, but I have a few other Qs. If you still have that VM where everything is almost happy, please compare the strmdll.dll & wstrmdll.dll files. See if they are exactly the same file version (or in other words just the filenames are different). Maybe do a checksum on them. On a fresh installation, is the bthport.sys file located anywhere on the harddrive? Can you give me a copy of your hfslip.cmd file that is inside the svcpack folder? Is there a triedit.dll file anywhere on the harddrive?

Which works, the modded E or the virgin B?

Modify the E one. If it fails, then test the B.

Not sure what happened. To make E, I went back to B and modded it. Go to line 1364... :: TP MOVE WORK\CDROOT\%FLD64%\strmdll.dll WORK\CDROOT\I386\wstrmdll.dll >NUL remove the :: TP Also, test out B again to see if you get the same error.

Hope this one works....

How about this?

5am? Are you nuts? No need to re-run w/beta B and that last question. You can delete beta B. I released a new beta C, please use this version for testing. I seem to recollect that TC disappeared before IE8 went final, so the IE8 slipstream code was for the beta. So in other words, there was extra files. I commented those extras out, so most of the copy errors will be gone. The triedit.dll is a bit confusing. Earlier you said that triedit was in sourcess then the post above you said it's not. Please confirm. The bluetooth stack hotfix, aka the 951376 is a bit tricky. The right file is there, even though there is one too many sys files. See how far you get with the 3 different steps below. Step 1 - Before visiting WU, see if this part of the registry exists. No need to create it, just see if it's there. HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\Windows XP Version 2003\SP3\KB951376\Filelist. Revisit and see if it's applied. Step 2 - Visit WU and don't install any hotfixes. If WU reports that the 951376 update isn't applied, See if bthport.sys exists anywhere in the windows folder. It should be in the system32\drivers folder. if it's not there, then extract it off the soucess and place it there. Revisit WU and see if it's applied. Step 3 - If it's still not applied, manually create the above key and then revisit WU to see if it still complains. Basically what we are doing here is this: http://www.microsoft.com/technet/security/...n/ms08-030.mspx security update deployment, Windows XP (all editions), and going through the last few things in that table. 974112 - If WU is still reporting this one as not being applied, manually apply the hotfix from the EXE file. Please post the KB974112.log file. It's probably in the windows folder. We're coming down the homestretch.... I think/hope!

I think we're getting closer. Let's try to address these 3 missing updates first. * 951376 - In sourceSS, can you check your driver.cab file to see if bthport.sys is version 5.2.3790.4274? It probably isn't. If it isn't in the cab, please continue reading this bullet. Can you also check the source folder to see if bthport.sys located outside of a CAB file. If it is located outside a cab file, please advise whether or not it is compressed. Also, please advise whether or not you see bthport.sy* or bthport.sys or both. If you see two, you found the prob. * 974112 - Do me a favor... Let's dissect this one a bit. The file that is a prob is wstrmdll.dll or strmdll.dll. The one inside the hotfix is wstrmdll.dll, but I think it may get renamed on a traditional hotfix installation. On a clean installation of your sourcess folder, please check your windows folder and all subfolders for file wstrmdll.dll or strmdll.dll. Make note of what exact filename you see and version. Next, manually install 974112. After installing the hotfix manually, recheck the files again. Whatever the case is, the version should be 4.1.0.3938. What I need to know is what filename (wstrmdll.dll or strmdll.dll) is listed with a version of 4.1.0.3938, and I need to know the location of the file too. * 890830 - I found an error with processing of the 890830. This will be fixed in the next iteration. Last Q for now. Is triedit.dll or triedit.dl_ in the sourcess folder? You mentioned there was a copy error for that, and I'm trying to see where that file came from. Maybe it came from a hotfix? Boy, it's tough going through someone elses code. Tomcat wrote this and I'm trying to figure it all out. Thanks for bearing with me. My coding is quite a bit rusty.

Hmmm, reposting the program without regard of the creative commons legal code and without notification of who the author is. Sounds lik a violation to me. Above zip file deleted.

Was it causing a problem? No. However, V1.7.9 includes the same killbits as v1.7.8. It's ridiculous to continually update the hfslip for activex killbits that are released every month. There was a lot of back and forth killbit discussion on the past few pages. The conclusion that evolved is that hfslip processes msft killbits hotfixes without error.

Looking at the txtsetup.sif file you attached before, it appears that WindowsServer2003.WindowsXP-KB925148-v4-x64-ENU.exe may not be handled correctly. I'd suggest to remove the non-critical update from your list. It's one of those multilingual bugfixes, which you probably don't need anyway. If you really really need it, I'm sure we can work something out. I'm not sure why you had those copy errors though, the code seems to be there and the txtsetup.sif is created right for the IE8 hotfixes, the files are present in the sourcess. It's almost as if there is a bad image or something. Very weird. Report your findings with the beta B I posted earlier (remove the above hotfix too).

Try this... re-download your ie8 installer. FWIW, mine is 33176 kb in size (for eng version). Next, try this one for size.

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

1062 didn't jive on this side. Can you zip up your post-hfslip txtsetup.sif?

jvidal - Thanks for being patient, the log file helped me out. I hope you don't mind being the king of beta testing. It's easier to tackle this piecemeal, so lets try to iron out the WM hotfixes first. Try this out. Open the script and locate line 1035. Line 1035 is the blank line between these two lines: SET HFNOREG= MOVE/Y WORK\WMP\UPDATE\*.CAT WORK\SVCPACK >NUL on the blank line # 1035, add this: MOVE WORK\WMP\wm11x64\*.* WORK\WMP\amd64 >NUL Save it, re-run the script, install on a VM and report back your findings. As far as the KB890830 malicious software, can you do this? I can't extract it on my 2000 box. For the x32 version, the /x is a hidden option, but it lets you extract. I cannot confirm for x64. Open a command window in the HF folder. Run this command and see if it lets you extract it. Let me know if it prompts you for a directory for where to extact it or if it just runs/installs the program instead. windows-kb890830-x64-v3.1.exe /x Lastly, are the files that you list for the txtmode, do those files exist in the sourcess? Pay attention to the filenames... Are you installing via boot CD? Please LMK what you discover with the above Q's, so I can automate things and start tackling the other probs. Thanks!

Gluon - Please re-read my previous post AND the hfslip site again AND the readme of the zip file you downloaded. They all say the same thing. You need SYSSETUP.DL_ and SFC_OS.DL_. Place those two files into replace\i386. Well, the cleanups worked without errors for SP2, maybe SP3's setup routines use something else. Who knows... I guess you can test the waters and let me know what files are needed. But what I can tell you is that when I ran ran syssetup and sfc_os back in the SP2 days, things worked pretty good and I did not get setup errors. As far as the driver signing stuff goes, this may work - place this into your winnt.sif: [unattended] DriverSigningPolicy=Ignore

The MRT is typically installed at the svcpack level (i.e. not slipstreamed). You don't need that MRT software, unless your goal is have a bloated OS. Those other files have to get processed differently via hfslip, they are all WMP and WM codec related. MSFT changes their mind on their packing scheme on those types of files all the time, thus the reason for so many betas on the x32. I'll see if I can start a quicky patch.... Edit - try out this beta. Maybe I'll start up a 64 beta thread if I feel ambitious. Please post errors you have, please don't be vague with the errors, I'll need as much info as possible (like what files are missing). Remember I don't have a xp64 so I can't test this out.

Wow! That was fast. FDV, looks like we got a taker, and we have German precision to make it perfect too. Thanks for stepping up to the plate Mimo! FDV, can you link to this list? Or host it for Mimo? Either way is fine with me. I'll update the hfslip site so that it points to the right place for XP lists once it's all settled. Sorry muppet , but a one time update of a list doesn't cut it.