tommyp

Let's not include microsoft office updates. It's way outside the scope of hfslip.

Sorry, it's not supported.

I tend to think that the likelihood is probably pretty high if your PC already has a virus. Topic moved to the "Malware Prevention and Security" forum, this is not an HFSLIP related question.

Another option if that doesn't work is to let hfslip run its course. After the ISO is made, you can run your xpize or whatever you want on the sourcess folder. Following that, if you want an ISO, you can type "makeiso" instead of "I have read the......" It will make a bootable iso using the sourcess folder.

Create a cmd file that says pause in the hftools directory.

I do not use MSBLA. The commandline hfnetchk is still usable for me and it suits my needs just nicely. It has been working flawless for me for the past 3 or 4 years. I not recall that the commandline hfnetck uses any other built in utilities/services other than the cab extractor, but I could be wrong. You should test it out on a fdv/2k and report your findings.

I see where you're coming from now. Have you tested it w/fdv's fileset? If it's a dependancy with the wu 3 engine, what files are the wu3 engine? Maybe you can keep those wu3 engine in the same directory as the hfnetchk? FWIW, the cmdline version works fine with my stripped to he!! (hfcleanup) 2k boxes. I use the ie6 core but no IE, I suppose there's lots of other stuff removed as well.

Hardly an HFSLIP topic, but I have no probs with hfnetchk on my 2k boxes. I think there are issues when using it for ie7 or ie8 on xp. Ymmv though. Perhaps it's better to ask on shavlik's website instead? You could always use the microsoft baseline analyzer instead (but it's not a cmd line program).

I'd say that it's mature enough to get out of beta. The prob is putting it onto the hfslip website. I'll have to take a time out and talk with FDV on how host it for keeps.

I'm not 100% sure if the hfnetchk utility is ie8 compatible, remember, the old hfnetck is out of support by shavlik (sp?). What does the regular WU say? Or what does the microsoft baseline security analyzer say? The bottom line is that if you are slipstreaming ie8, then the subject mshtml.dll you want is 8.x.x.x.x. mshtml ver 6.x.x.x is ie6. More than likely, you discovered a quirk with obsolete software.

I have no prob with muppet hunter doing the updates. In my opinion, it's probably easier having the list posted on a separate site but that's only my opinion. Muppet, PM me offline if you want me to send you that spreadsheet.

I can't say. I suppose you can try it in a test environment.

-x- thanks for the contribution, but like i said, there's other updates needed for the other flavors of wmp9. I'm sure that there's other things to test out. Acheron - you're doing a great job plugging the efforts at ryanvm's site. From the limited reading that forum, it appears that ryanvm lost motivation too. Irregardless of that, I'm sure that his file is fine, however his pack does not support all flavors of IE/WMP, etc. I honestly do not have time to support an OS that I don't even use. Maybe someone will devote some time to maintain them. Until then, you can consider my xp list an abandoned effort.

bfc - to see what's new and what to remove, go to the first message in this thread and open the msft link. If you open each MSxx-xxx article, you'll see what the old articles are replaced by the new update. Each MSxx-xxx article is associated with a KB article, and the KB article number is part of the exe filename. Sometimes they are new where nothing is replaced, but most of the time there is an update that is replaced. In my handy dandy WU tracker spreadsheet, I track all the MS numbers and KB articles so I can quickly see what's new and what's old and place each in the appropriate row. I use the spreadsheet to automatically generate the html code for fdv to host. The reason I find it particularly annoying when people post new updates is that I still need to complete the MS article info and its associated KB # so I can update the lists in the future. Posting links to what's new is only half of the info I need. Personally if I wasn't maintaining a WU list, I'd just visit the msft link every patch tuesday. I'd open each MS article, read it, see what's old and delete the appropriate exe from the HF folder. Then I'd put the new one in the HF folder. It probably takes 3 minutes to do tops. Then there's the various flavors of IE, WMP, and other non-essential bloatware that msft offers that somehow gets on the critical update listings. So, if you had to copy/paste/edit each hyperlink for each new hotfix and put it into the WU hotfix list spreadsheet, you can imagine the time it would take.

Try asking in the right forum.

I've seen the roots update not slipstreaming via WU on occasion. After running it manually, I could not isolate any changed files or registry changes, but WU is happy after that. I suppose you can place it into a folder other than HF. I think it goes in sw2.

Microsoft never makes mistakes. LOL! There have been many occasions where WU will look for and insist that an old file is required. Let it slide for a bit and check in a week or two.

Posting links like that doesn't help for me to maintain my lists. Besides, I refuse to maintain them. I pass over the reigns to someone else. -x- are you offering services?

Acheron - Don't mean to be mean or anything, but what's the point of posting what updates are new when you don't even use the lists on this site anyway? Why not tell ryanvm that his lists are outdated? I'm done with XP list maintenance. I don't use xp & don't plan on ever using xp. My time is better spent on other things than that. Sometimes real life gets in the way.

There is some component in mdac needed to correctly display the add/remove programs via control panel. There is lots of mdac is that is, well, pretty much useless. I've been using the same reducers for the past 2+ years without incident (and without mdac). So to answer your Q, if you running that ruducer, the add/remove programs will still work. If you go all out and remove all of the mdac, your add/remove programs won't work, unless you use a different program to do so. Hope this helps.

I nominate Acheron for doing XP update lists.

What's all this brouhaha about? HFSLIP supports two iso maker packages. mkisofs.exe is open source, nlite uses it too. Nobody is complaining to Nuhi that his software is old because it uses an old iso maker software. Cdimage.exe is not open source and IIRC, it was not supposed to have leaked out of msft. Like what Martin said, there is no need to update an iso maker program. It's up to the HFSLIP user to make an iso with either of two solutions. Alternatively, they can make their own iso using their own program after hfslip is run. At the end of the day, an iso file is an iso file.

In your HF folder, is your killbit hotfix installer OK or corrupted? The regshot you provided doesn't really help if you installed via WU. You'll need to do a clean install, do a regshot, install the activekillbit file exe file, do a second regshot and then compare. BTW, you're the only guy having an issue with this.... Did you bump your hotfix list against what is posted in the stickied section? Before you ask, I will not check for you.

Martin - No need to apologize. The out of band update was appreciated. Most of the time, I miss the oddball ones like that. Actually I don't mind doing the 2k lists because I use it. The XP and the various flavors of IE and WMP and other non-essentials are a pita.

Once in a while there is some noise about the killbit hotfix not slipstreaming. That is remedied by a few lines of code in the script. So far, I have not seen any complaints on this, well probably since earlier this year. If you still cannot get the kill bit to slipstream, install the hotfix manually BUT do a regshot before and after and post the results. The regshot will show which entry needs to be added into the registry to make WU happy.