I've been lucky; if you look in TXTSETUP in my 2k set you'll see my strings for my controllers and my dual core mobo, Asus I think, too lazy to look, had a 2k driver for the controllers.
The real reason was that I have to run Adobe CS4 in my office, and it won't run on 2k. Although I am sure I could probably get away with being the one guy permitted to run HFSLIP in a corporate environment, with 2k, as noted in the other thread, I used to slipstream 2k by hand because I need to know exactly WTF is going on with hotfixes. It's going to be the same way with XP... I have a permanent directory on my server that has XPSP3 unmodified and one in parallel that gets hotfixes (QFE) and the registry data is extracted from the INFs and put into the HIVE files. As newer hotfixes replace older ones, they get dropped right in. I stay on top of things this way and it's not terribly hard. For totally new files, I enter that data permanently into TXTSETUP and LAYOUT, but leave that out of the fileset so things go normally for HFSLIP users. I keep my FDVFILES separate like any other user in a third directory. When it's time to make an install CD, I do it by hand. Which is no great chore since I literally do this once a year. So far I have not rolled out XP except on my machine, and it is full, bloated install. Like everyone else right now, I am testing and isosizing for VMWare to test my own fileset to make sure it is bulletproof.
One thing that really bothers me is that XP has sooooo many networking dependencies. You could slash stuff out of 2k all day long and still connect to a LAN. In XP, this is not the case. Some files from the oddest places had to be left in... Internet Connection Wizard for example has a few files that XP needs. There are others from other INFs.
The only way this was getting done in a timely manner was due to both Tom and I working simultaneously (for the record, he switched to XP in order to run a piece of software too. His home machine runs 2k with no issue as far as hardware goes). We discussed nLite and both agreed that it didn't remove a consistent baseline automatically (i.e. you can make a settings file, but since we're running HFSLIP it's one less step to have our own). It's a fantastic program but we figured we both had dealt with 2k and might as well do the same for XP. Following INFs made it pretty easy. I also wanted an opportunity to better understand XP; this is reflected in such things as HIVEACX.INF.
There was a gentleman once way back who had, well, let's just say a misguided notion that removing components from XP before install was a bad idea, and that deletion after install was the way to go. History has not been kind to him, but to address his complaint -- namely, that some DLLs need registering before they can be deleted -- I added the FINAL1 and FINAL2 files to Win2k so that prior to install, files could be copied, registered, and then deleted at the user's option. All invisibly. I am adding this to XP as well so that a user can register and delete a DLL without ever having to both with it post-install. This fellow made claims about some DLLs, like JSCRIPT.DLL (saying it is needed to display the services tab) that might be true after installation, but don't apply if the file is deleted prior to installation. I picked that DLL because I actually tried it, and the services display tab worked 100%. There might be others; maybe I picked a random DLL that just happens to contradict a claim, I don't know. (For a guy who claims to slim down XP he sure does keep an awful lot of stuff... Outlook? IE7? Media Player? Anyway...)
Getting back to the work of those I actually respect, I should also add a note about Blackviper
. I recommend his information on Services highly; I relied on this info when removing several services. He's still the go-to source for this information.
I am, I would say, done with Windows 2000. If someone finds a bug of major import in fileset 9, then I'll recommend fileset 8j (IIRC) which I kept and link to on my site. It has its own readme and keeps just a small few things that set 9 got rid of. It seems to address the few problems reported with set 9. It is sad that support for 2000 ends this summer; at that point the OS will become a curiosity that will be great for old PCs and perhaps MAME cabinets. It's a HUGE chore to run it from USB, and an even bigger hassle to run it from CD (yes, it can be done; no, I am NOT going into it, no matter how much I am begged*). I did note elsewhere that I am also making a fileset for vehicles to run from USB right at install time -- run HFSLIP with my car set, get an ISO, burn to CD, install from CD right onto USB drive directly. It's not a huge priority because so many hobbyists have their own ways of doing it, but it's in the pipeline.
We will all continue with hotfix updates -- Tom with 2k and me with 2k3 though these are waning in popularity. (Which kind of surprises me, considering it is a free trial download. Although I don't do it myself, I know one can make a perfectly good PE disk using the trial of 2k3. I did it once myself to test that).
We expect XP to pretty much be the future here and with Muppet Hunter keeping hotfixes up to date and so many users, it's going to pretty much be our focus from here on. Tom and I will continue to address user needs for 2000 of course. I doubt HFSLIP will ever support IE8 slipstreaming in 2003 though, for example, and although WMP 11 codecs might work in 2k, don't hold your breath for official support. If someone addresses these, TommyP does accept code contributions, but there are configurations neither of us concern ourselves with.
*I was pestered enough about NT 4 SP7, and several of us addressed that and finished it. I looked into booting 2000 from CD. Two products were made and are now entirely scrubbed from the Internet (trust me. TRUST me. They're gone). As for USB, one can search around. If someone wants to make a 2000 specific tutorial I'll host it gladly.