has anyone had any problem integrating that huge hotfix pack using hfslip ? the hot fix dot net ?

For those unfamiliar...

the site:
http://www.thehot...0;.net/sp3.html

the backstory:
http://www.pcworld.com/resource/article/0,...,RSS,RSS,00.asp

@ FDV, something wrong w/ s.p.a.m.net address...or its just offline perhaps?
[Edit] Doh! You already fixed it. heh. [/Edit]

Interesting I suppose, course that huge list of fixes looks like a headache in waiting to me
Recommended/Critical? nope just a huge list, and get them all just in case heh.

s.p.a.m net - what Crash&Burn is talking about is this: i typed the hotfix URL and the board software automatically changed it! i guess a filter for certain urls is in place because perhaps someone from that domain tried to do some spamming? i am not really sure but i fixed the url... (i'm not sayin' how!) it's only for reference and i'll be taking the link down in a little bit, because i am sure that even though the filter is a well-intentioned move against spammers, it's probably there for a reason to prevent any traffic to their site, and i don't want to mess with what the mods have decided is a good idea.

i suppose there are no issues between hfslip and that h-tfix pack then?

Uh why would you want to? If you look at what it is...
Or perhaps even read some of the user comments before downloading, or perhaps go to:
http://arstechnica.com/news.ars/post/20051015-5438.html
or: http://www.broadbandreports.com/shownews/68515
I'm sure there are others. Good luck w/ that.

Brannigan noted that while the hotfixes may be genuine, they're not for public consumption. (But this is beside the point.)

Here's the main point : http://www.ryanvm.net/forum/viewtopic.php?t=498 .

As you can probably infer, I'm interested whether or not hfslip can do this job. I know that this thread http://www.msfn.org/board/HFSLIP-2K-XP-2K3-slipst-t57659.html states that

All I'm doing is confirming that there are no issues when slipstreaming that massive hotfix pack.

Well tommyp or fdv (or even saugatak or olek II) might be better suited to answer (I'm much newer to this project), but I've not had any problems with hotfixes thus far, even ones that Nlite chokes on.
I'd just recommend not installing that hulking fix en-mass, choose ones from it selectively is all...

HFSlip isn't quite as automated as some of the other SLIPpipng options around here, when you want to differ from some of the presets some minimal editing of the inf's used is required, but really FDV's site and the files themselves are very well commented and they make it quite easy to use.
And FDV generally will add more inf's to add in if there are things removed from his defaults that you'd rather keep.

With a small amount of work HFSlip can take place of $OEM$ and even preinstall software, but as its main design isn't the latter, again it does require some end-user work.
Again from what I have seen from this project, most everyone is very helpful (unlike some others where posts just go unanswered). Maybe if the posts here got out of hand like some of the others that might change, but lets hope not

I try to help out on the boards, as I haven't been as helpful as olek or saug as far as testing goes yet, hopefully when I get my system setup properly for backups et al, I'll be able to participate more in that

nLite859, HFSLIP is designed to work with hotfixes following standard naming conventions being in certain folders.

Put the hotfixes you want (after making sure that they follow the KB-xxxxxxx naming format) in the HF folder and see if it works. It's an easy enough test. And read the instructions at FDV's site.

As far as I know it is not a good idea to get tthat so called SP. MS has specifically warned users not to get that update pack.

i have read also as suryad that ms has warned users against this binary.

BUT. if you REALLY want to try it... put it in the HF folder and give it a name of an XP hotfix. this will "trick" things. of course, this faux sp3 has to be in the form of an EXE file.

this is not recommended, and HFSLIP is set up to prevent people from going too wild -- which means that we don't really want to support questions having to do with things HFSLIP really isn't meant for (in other words, yeah, it CAN do this, but we are not saying you should, so if there are problems, we warned ya).

You guys are awesome. Thanks for the responses!

On a sidenote, I don't see what the big deal is. People have been using RyanVm's update pack for a long time now -- without much grumbling. What would happen if M$ issued a similar warning about RyanVm's update packs ? Like I said before, the main reason that I'm looking at that huge hotfix pack is because RyanVm is going to discontinue support for machine-specific hotfixes. However, RyanVm is not against the idea of some other person taking over the collection and the maintaining of the machine-specific hotfixes... it's just that HE himself is no longer going to do it.

Another reason for using hfslip is so that people do not have to wait for other people, such as RyanVm, to release updatepacks. It's far easier to slipstream hotfixes on-the-fly as hotfixes are released rather than wait. However, the disadvantage that micro$oft and others are pointing out are that there is NO pre-testing on how the hotfixes will interact with one another. However, if you read *cough*theh0tfix's*cough* forums, you'll get a general idea -- BUT since hotfixes are machine specific, there is no guarantee what will work for one person will in fact work for another -- since the machines that the hotfixes are being installed on are indeed very different.

Yet, it seems that even micro$oft itself cannot fully test how CRITICAL hotfixes will impact every single system in existence. A prime example is here : http://msfn.org/comments.php?shownews=14828 . This is why I take advice from micro$oft with a grain of salt. If THEY can't get it right, and THEY are the ones making the hotfixes, then who are THEY to advise ME ?

Anyhow, thanks for the great support on a great piece of software. Now if only your hfslip would integrate BTS's driver packs ...

@nite0859 - Thanks for pointing out the hotfix issue. You would be surprised that people would rather have unstable systems and happy WindowsUpdate results. Strange and sad but true. Also, the point you mention about making your own updated installation source: this is exactly the reason why I came up with HFSLIP.

Just for the heck of it, I did it.

Procedure: Started with Sp2. Integrating all of BTS's Driverpacks, method 3, then integrated that hulking hotfix pack, along with the codecs I posted earlier using hfslip. after it was done, i xpsized the entire thing (patched i386 files).

got somekind of error on first boot with medctrro.exe ... dunno what that is. prolly driverpack related.

@nite: Please review these instructions at step 11. You have hotfixes that are named incorrectly.

Whoops.

Ok, ok, ok. What I'll do is rename them with the structure of WINDOWSXP-KBXXXXX.EXE Sometimes, It'll even be WINDOWSXP-KBXXXXX-V2.EXE or even WINDOWSXP-KBXXXX-V5-X86.EXE.

P.S. On a side note, I came across some hotfixes that some guy extracted and re-packaged using 7-zip (I suppose because there is suppost to be a special way of installing them with special switches?) I know they aren't standard hotfixes, since they've been tampered with, but do you think HFSLIP can handle these "special exceptions?" If you want to keep HFSLIP "pure," then I'll understand. Just lettin' you know what I've seen. It's really no big deal if you don't decide to implement this, but it does give more options with those special switch circumstances.

I really don't know enough about all of this to be even making a request, so if you reply with just a then I'll understand.

If these packs are repacked switchless or switched installers, place them in the right svcpack folder for installation via svcpack. I will only work with microsoft downloaded binaries, so you won't see them slipstreamed by hfslip. Sorry dude.