tommyp

The prob see is probably because the system needs a reboot. Why not slipstream it instead? You can place the installer into the HF directory.

hfslip doesn't support vbscripts. You're best bet is to ask on the unattended forum.

This issue hasn't arose in over a year. Please do what tomcat76 said, and fwiw, it may be worthwhile to rename your files to 8.3 format without any strange symbols. Also, how are you installing the image? Did you set up your vm to boot from the iso? Did you select the default multiboot options when you ran hfslip? Are you trying some sort of network installation?

Holy thread resurrection! When you ran hfslip, did you select the default values for the multiboot path? When installing the ISO, did you set up your VM to boot from the iso image? Are you trying to do something funky like some network install?

If you are using the ISO to do clean installs, you can remove all the folders except for i386 and $oem$. The other folders are used for upgrades and whatnot. If you have your application addons and silent installers folders all filled up, then obviously you'll have a bloated iso too. HFSLIP isn't smart enough to delete things like that for you

Nope, that's not the final solution. Maybe by the weekend, I'll post a new beta up that addresses this.

You can put them in either or. I keep that sort of reducer stuff all in hfcleanup. But again, the choice is yours.

Gluon - can you rename that same inf file you located before and place it into the HFSVCPACK folder? Rerun the script and test out. Is anyone else beside gluon having probs with KB973525 on XP?

gluon - One more q for you. Sorry to piece meal you to death. On a clean installed machine and doing nothing else, does "973525" (no quotation marks) exist anywhere in the registry? I'm just trying to see if that INF file is actually installed at all.

gluon - Another favor... can you search through your sourcess\i386 folders for hf*.inf files that contain the text "973525"? If you find it, please zip it and attach it. Thanks! Also, have you tried running the script with the nokillbits set as default in the hfslip.ini file? Or in other words, delete the nokillbits line.

Pardon my ignorance, but you asked how to manually integrate dx9. By manual I thought you meant binary by binary by hand. Manually is tedious. There is more than just registering a few DLLs. There's some driver files to be added and there's a host of INF files that need to be installed too. If you want to use HFSLIP to automatically (i.e. not manually) slipstream DX9 into an XPSP1 source, you can do one of two things. You can either place the directx 9 distributution in the HF folder, OR you can place the same cabs you mentioned before into the HFCABS folder. Either will do the same. Keep in mind that nobody is maintaining an SP1 hotfix list, so it will be up to you to see if it works. I think that portions of HFSLIP were trimmed to kill off the SP1 hotfixes. Keep that in mind. The code that was removed will not be added back in. However, if you decide to be all up to date, just slipstream SP3, you do not need to worry about this because SP3 has DX9. If you choose not to use HFSLIP to add in DX9, please ask in the appropriate forum.

The prob with the kill bits is that the initial killbits is set, various hotfixes overwrite things, and then in the end, one or two more still need to be set. HFSLIP just sets the appropriate killbits as late as possible during installation. If you can, please do me a favor because I don't want to test out XP. Run hfslip with your current setup, install it on a VM. Obtain and install the freeware regshot program (google for it). Do a regshot, install the KB973525 hotfix, do another snapshot and compare the results. There will be some sort of HKLM,"SOFTWARE\Microsoft\Internet Explorer\ActiveX Compatibility\{...nonsense...}","Compatibility Flags",0x00010001,0x00000400 ADDED to the registry. I just need the line or lines added or modified to the registry and I'll add it to the program. Actually, all I really need is the nonsense part of the changes. lol. Once that is done, then all will be cool.

Beta S provided. Added dx9 code provided by gluon. No other code changes. Thanks dude! Please provide feedback. I'd like to get this thing out of beta. It's been over a year of betas so far.

That's odd. Without WMP9, I was able to slipstream the 969878 and 975025 and directx9 and the rest of the hotfixes using beta R. In fact, the only missing update I got was the Malicious Software Removal Tool because I didn't include it. Weird. Maybe I'm doing something wrong? edit. With WMP9, WU reports that I missed the sofware removal tool and 973540, which ironically I forgot to include. Others installed fine. I must be doing something wrong then. Oh well. Let's keep this thread back on topic - windows updates. If you are running into a particular problem, please either report it in the beta thread or in a new thread. This is not a blog. Thanks in advance for understanding.

Sure doesn't sounds like an hfslip related issue at first glance. Question for you - did you/can you test your dvd extracted source by itself to see if it installs? Remember, hfslip creates bootable cd images. If you do something else with it, you're on your own. Sorry. Perhaps you should ask on that forum instead? I did see a similar prob once, it was an XP home upgrade cd. For it to work, you needed to have an old OS installed on it prior to installing.

Those _*.cabs are created to speed things up if slipstreaming ie6 on a 2k source. The files inside them won't update because the ie6 cabs weren't updated. There's no need to clear them, unless you want to (hfslip will just recreate them). There's no need to delete anything in hfcabs, hf, hfsvcpack* or any other folders. However, you should delete obsolete files obviously. You do not need to clear the source folder either. The script will clear and recreate the sourcess folder on each run. One little pet peeve I have with 2k vs xp is that when copying files from a cd to a hard drive, on a 2k box the files have a read only file attribute. This does not happen with xp. It would be beneficial to clear the read only attribute to the 2k source files. It sounds like you using a pre-sp4 source. If you are, just include the SP4 and hfslip will slipstream the source directly with sp4. This is OK. There's no need to delete source after slipstreaming sp4. This will save time too. As far as the svcpack.log and mp\dosnet.inf files go, it could be an artifact of microsoft's sp4 slipstreaming routine. I can't say exactly though. I haven't slipstreamed a pre-sp4 source in many years.

Tomalak - did you have the same issues with a VM? Or just the real install? Are those files missing inside the sourcess\i386 folder? If the files are in the sourcess, chances are it's a bad burn. I typically test the CDs out on a VM prior to a real install to verify the burn is ok.

Sorry, but I'm not too sure of svcpack.log. Is that file on the installed OS or in some folder on the install disk? I'll assume for now that you installed windows and the E drive is your CD. Looking at E:\OSKITWin2KReinstallKit\HFSLIP\SP\i386\mp\dosnet.inf doesn't quite make sense. Typically there isn't an "MP" folder, or at least I've never seen an MP folder. Dosnet.inf should be in the i386 folder. The files I have in my hftools follow. If I rename zcdimage.exe to cdimage.exe, then cdimage is used to create the image. Both methods make the same file, so I always have an option to use either. cdimage take precedence for making ISOs, but if it's not there, it uses mkisofs. bbie.exe bbie.lic boot.bin boot.img cmdow.exe EXTRACT.EXE HFANSWER.INI mkisofs.exe mkisofs.txt modifype.exe MSICabExtract.exe MSICabExtract.txt Reg.exe ZCDIMAGE.EXE FWIW, my hfanswer.ini has this: FORCECDIMAGE= CDIMGSW=-h -j1 -m MKISSW=-relaxed-filenames -d -D -N -J -no-emul-boot -no-iso-translate -boot-load-size 4

New beta R is up that addresses some 2k WMP and WM hotfixes. The changes do not affect XP.

I'm coming down the home stretch with W2K WMP hotfixes and a new beta that addresses them. Turns out that most of the media type updates are codec related. Give me a little bit more and I should have things resolved. Today I've run the script and tested the resultant iso 10 times and my PC is tired, and so am I. On a sidenote, the current rootsupdate can be downloaded from here: http://www.microsoft.com/downloads/details...49-a00e01e22f17 I think the next round of roots updates should be here: http://support.microsoft.com/kb/931125 I'm not 100% sure, but I think that running this inf file will kill 958470 from showing up with WU in W2k. [Version] signature="$Windows NT$" ClassGUID={00000000-0000-0000-0000-000000000000} SetupClass=Base LayoutFile=layout.inf [DestinationDirs] [DefaultInstall] AddReg = add.reg DelReg = delreg [Add.reg] HKLM,"SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\%SP_SHORT_TITLE%","DisplayIcon",0x00020000, "%windir%\System32\msiexec.exe" HKLM,"SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon","BufferPolicyReads",0x10001,1 HKLM,"Software\Microsoft\Internet Explorer\ActiveX Compatibility\{7584c670-2274-4efb-b00b-d6aaba6d3850}" HKLM,"Software\Microsoft\Internet Explorer\ActiveX Compatibility\{7584c670-2274-4efb-b00b-d6aaba6d3850}","Compatibility Flags",0x00010001,0x400 HKLM,"SOFTWARE\Microsoft\Internet Explorer\ActiveX Compatibility\{7584c670-2274-4efb-b00b-d6aaba6d3850}","AlternateCLSID",0x00000002,"{6A6F4B83-45C5-4ca9-BDD9-0D81C12295E4}" HKLM,"Software\Microsoft\Internet Explorer\ActiveX Compatibility\{9059f30f-4eb1-4bd2-9fdc-36f43a218f4a}" HKLM,"Software\Microsoft\Internet Explorer\ActiveX Compatibility\{9059f30f-4eb1-4bd2-9fdc-36f43a218f4a}","Compatibility Flags",0x00010001,0x400 HKLM,"SOFTWARE\Microsoft\Internet Explorer\ActiveX Compatibility\{9059f30f-4eb1-4bd2-9fdc-36f43a218f4a}","AlternateCLSID",0x00000002,"{971127BB-259F-48c2-BD75-5F97A3331551}" HKLM,"Software\Microsoft\Internet Explorer\ActiveX Compatibility\{4EDCB26C-D24C-4e72-AF07-B576699AC0DE}" HKLM,"Software\Microsoft\Internet Explorer\ActiveX Compatibility\{4EDCB26C-D24C-4e72-AF07-B576699AC0DE}","Compatibility Flags",0x00010001,0x400 HKLM,"SOFTWARE\Microsoft\Internet Explorer\ActiveX Compatibility\{4EDCB26C-D24C-4e72-AF07-B576699AC0DE}","AlternateCLSID",0x00000002,"{54CE37E0-9834-41ae-9896-4DAB69DC022B}" [Strings] ServicePackSourceFiles = "Windows 2000 Hotfix Source Files" SP_SHORT_TITLE ="KB958470" SP_TITLE = "Windows 2000 Hotfix - KB958470" SERVICE_PACK_NUMBER =5 SP_TITLE_NEW = "Security Update for Windows 2000 (KB958470)" I'm not sure why the lines have line breaks, anyone know how to turn off the line wraps?

The easiest way is to DL the dx9c installer and install it. Manually installing it with binaries is a big pita. There's many files to rename, swap and register. There's also some INF files that need to get modded and installed too. If you need directions on how to do it, look outside the hfslip forum.

I didn't forget to address the 891122. Look 4 or 5 posts up. Please keep in mind that I was running some beta tests on the MSI installer and wanted that resolved before I started addressing WMP probs ane WMP codec probs. I did mention a test you can run to help troubleshoot and provide a list of what should be replaced that isn't replaced. Once I know that, I can automate things. If not, when I get some free time, I'll have to run various cases of WMP and VMs to see what's happening for myself.

Holy run on sentences! lol!! If you feel like troubleshooting windows malware player hotfixes, here what you can do. Install a program called installrite on a clean install. Check things with WU (do the custom) to see what hotfixes are not applied correctly. Do not let WU install the fixes. Next, exit out of WU. Run installrite, do a snapshot, install the problem hotfix and then compare what files/registry has changed. Sometimes a binary may be swapped or addes somewhere else. Sometimes, WU wants to see the same file in multiple locations, esp with windows malware player binaries. The locations would be sys32 and PF\WMP. Personally, I don't particularly care for WMP. All you really need is codecs and any media player. WMP is garbage. There's plent of others that a far superior. Both winxp and w2k come with wmp6. 2k has wmp7 which would only be installed if said so on your winnt.sif file. xpsp3 has wmp9 (?) that is only installed if said so on the winnt.sif file. By SS WMP9 on 2k, the winnt.sif file will install wmp9 instead of 7. I'm not too sure how to answer your install this and uninstall that and what is left over. I guess you can try it out and see what happens. As far as the DX9 hotfix goes, make sure you are using the DX9 hotfix. The file is named Windows2000-DirectX9-KB971633-x86-ENU.exe. Note that it says directx9 in the filename. If you have the wrong file there, then obviously WU will report an error.

hotfix 099 - http://www.microsoft.com/technet/security/current.aspx

Please learn how to zip your log files next time. Thanks. Do you have the same prob with M?