fdv

ricktendo64 - I grabbed the data from an MS hotfix, then later, from the equivalently named HIVE file from one of the ReactOS releases. It is not up to date, only Jan 2009 I think, so you are correct, it does miss some. I will have a look at ReactOS again to grab that string at some point. jaclaz - That's a pretty small XP; maybe I shouldn't bother re-inventing the wheel.... can you send me the latest XPcli_build.zip? It's a 404 on that site now. PVU - thanks for the kind words, man. Even now TP and I have some new ideas and we are stirring them around in the Great Cauldron.

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.

I have been using it in a HIVE file for, oh, 8 years or so. I recommend modifying HIVE files wherever possible because they are used to populate the registry first. You can also fix the time zone data permanently this way. See the HIVE files in my Win2k set for more detail.

Someone else add to this since I gotta do other stuff. When 2k/XP/2k3 install, they throw INF files into the INF folder and later parse that for device INF installers. So, the first thing we have to do is rename your INF driver files to something unique. Let's say mysnd.inf. let's also say that your soundcard driver is h48a2ns9.sys. Then, open TXTSETUP and add mysnd.inf = 1,,,,,,,20,0,0 h48a2ns9.sys = 1,,,,,,,4,0,0 The install will find the device, speed through INF looking for an installer file, will find the one you added, and install the card. Now you can use nlite (because digsig and file checking need disabling). Someone add to this, I gott go

Hey man! I would agree with this -- that it is not a good idea. MS has already released TCP/IP patches for XP and above and not for 2k because, according to them, the protocol stack is different in 2k (and of course being closed source there is no way for us to know). After summer 2010, I'd say 2k will be good for, say, running MAME in a custom cabinet not connected to the 'net. With a good hardware firewall there probably won't be any real risk, but you never know; we all thought that since NT4 was so mature after SP6a+Rollup that it would remain a good multipurpose OS, but sure enough, many of the 2k exploits affected NT4 as well. Haha! Well, okay, if you must know, I have to run the Adobe Creative Suite version 4, and only version 2 worked on win2k; after that it was XP only. My office environment demands it also*. The best I can do for you is to direct you to the WINE project; they might have some documentation on what might be in it since they had to duplicate its functionality. I'll think about it but I don't see too much demand; one only needs to take the file list from TXTSETUP, paste it into Word, replace the = 1,,,,,,,^t^t^t^t with nothing, then replace ^p with ^pd1, Just make sure nothing is after the filename, and d1, is before each filename. That's pretty easy actually. *I'm sure people will catch that. I actually don't use HFSLIP anywhere but home; at the office I need to know exactly what's being replaced, so for many years I have been creating a manually slipstreamed Win2k. I'd get the hotfixes, extract with /x, and see just what files were at work, and extract the registry data and manually put it into the HIVE files.

Not a huge deal, I only spent ~30 mins looking for an answer on the 2k thing so no biggie As far as IE goes, honestly, you'd need access to source code. The fact that Windows will work without it is very telling, and you might be right -- there would be calls, but would they be plastered everywhere? Hard to tell. Could they be commented out and the DLLs recompiled and there be no loss of functionality? On that question, I am very sure the answer would be "yes."

We worked in friendly "coop-etiton" for reducing XP And really, we produced in a record short amount of time considering our other hobbies. We exchanged ideas but more times than not, TommyP would email me a question and then email me the answer to the same question before I could even respond

Late to the thread, but I like this defragger, and it works on 64 bit

@Martin - can you run DXDIAG and see if there are missing files? Do you know if this worked in set8k? I have to ask because I do not have a fileset9 install in use right now, I am running XP at home. Yeah, yeah, I know, silly me @Kiki - I forgot, sorry! I will address that I promise!

I suppose if Tom and I had been forced to use XP in 2002 you'd have seen all of this much earlier Even with Tomcat's actual identity it's been very hard to track him down, he's a ninja I guess I am also making a fileset for Car MP3 computers, just so everyone knows. It would boot XP from USB by default. I can't decide whether to include networking. I am tempted not to. (? is that the right decision?) This car fileset will in fact be dramatically small and only intended to run media software. Most software would not work.

Yes, I know it took me 9 years. I hated XP for a really long time. Still kinda do. Events happened in 2009 that caused me to have to start using it. So, I made myself a fileset to use and might as well share it. For now, it DOES include IE. I will be optionalizing IE, but I needed to get rid of the other junk in XP first before I started to work on that. I have not fully determined all of the differences between this and what nLite delivers. Your registry will be smaller with my fileset, but because of the way XP handles the registry now (which is different than Win2k), a smaller registry doesn't necessarily matter, since it's not loaded all at once anymore. See below for what I remove. Remember that this is the first set. My SYSTEM32 is 270meg at the moment. Yes, it can go smaller, but I need to keep a lot of functionality. This is not intended for use in your MP3 car computer, there are other projects for that. This is compatible with TommyP's reducers; there were some errors but I think I have addressed them. Without further delay: FDV fileset for Windows XP. Requires HFSLIP Dec 27 Beta A or higher. Put the files in FDVFILES and you're ready to go. BTW if you want, you can save more space by commenting out OOBE.INF in SYSSETUP. I understand some people have enterprise editions of XP or whatever. I have made an OOBE that calls OEMBIOS, since logically, if you need OEMBIOS, you need to call OOBE, but if you do not need OOBE, you do not need OEMBIOS. This large OEMBIOS file is really only for OEM XP editions and is not necessary to install. Removed This fileset prevents the installation of the following MAJOR components: COM, DTC, WBEM, DotNET 2 This fileset prevents the installation of the following MINOR components: Optional Net Components, Autoupdates, BITS, Autoupdates for Root Certs, Accessories, Message Queueing, Multimedia themes (cursors, sound effects, that kind of thing), KOC, Communications apps, Optional utils, but calc and paint -are- installed by default, Games (all, including offline ones, online ones, and pinball), Wordpad, Fax, Tablet PC, NT backup, Media Center, IIS, Frontpage and its extensions, Media player (including obsolete remnants from v6 and 7), Add-on DRM, WMP skins, MSN messenger and explorer, Application compatability (Myst? lol), MS Info, Network Plug and Play autodiscovery, PC Health, graphical multiuser logon selection (i.e. click on a picture to log on), Net Meeting, Task scheduler, Firewall (you bought a hardware firewall, right?), blaster cleaner, SAPI (the voices and characters), Macrovision disc driver, Troubleshooter, MS Outlook and address book, Movie maker, Pictures of controllers, VGX and obsolete Flash for IE, Search dog (he is not switched off, he is removed and cannot be switched on), Obsolete Bluetooth devices, MS proprietary photo crap, Quality of Service, conferencing, new account wizard, shared folder wizard, web printing, help files, and more. The registry HIVE files have been gutted. The timezone information has been reapaired in HIVESFT.INF. (Correct as of January 2009).

Heh, you guys are quite welcome! Performance counters could go, too, I guess. I'm going to have a look and see what else might. Meanwhile I am about to introduce XP fileset 1. It is very preliminary and leaves IE in for now.

Oh, it's going to take me forever to find this, I just know it, but I had this issue a month ago. There is a security setting (secpol.msc etc etc) that applies ownership of files to either all administrators or to specific users/administrators and will not allow deletion even by an admin if it's not the original admin. This is the default setting in XP and it CAN be changed. I am hoping I jogged someone's memory because although I have the registry setting in an INF file somewhere it will take me a while to dig it up. I'll try to find it.

I see your comment about tip top shape, Prob, and I have to ask, what role will your server play? Because honestly there are a lot of unpatched vulns.

All I can really say is that I have used some of their recommendations for 2k in my own IE removal fileset. Never had a problem.

Bearwindows made a slipstreamer. Referenced here or in the HFSLIP subforum, I forget which. Wendy was working on an unofficial SP7 too. Somewhere in the HFSLIP subforum is a slipstreamer that Tomcat76 made... we don't support it and don't encourage questions about it but if you do a search on nt4 sp7 it will probably come up. I forget the exact file but sp6a replaces an NT4 system file with a driver. This was an error on MSFT's part and simply requires care if not using Tomcat's slipstreamer. We did it as a curiosity mainly and did not intend to merge it with HFSLIP.

Hey, nice work! Is the source available?

Just letting everyone know about HFSLIP 64. I am posting this because until now there was no reason for 64 users to visit that subforum.

Yes. Someone has played a trick on you. The reason no one is answering this Q is because they ran a program that we're not allowed to mention here. It is possible to switch it back, but technically, I believe I am not permitted to tell you how.

Slipstream hotfixes using HFSLIP 64. If you want the technical nitty gritty on driver slipstreaming, I explain it here. nLite is fine for driver integration but this process lets you know how it works.

Zeus, the TCP/IP files are replaced with hotfix versions. You want the absolute BEST way to do this? 1. Run HFSLIP with the HF directory full and accurate 2. Go into SOURCESS and find the binaries you want to modify 3. Hex edit them 4. MAKECAB them 5. Put them in REPLACE You might as well have the very latest files from hotfixes. Using someone else's add-on is taking a chance with using an outdated file. Edit: I see the patch for TCP is September 2008. So, there ya go. Don't bother with it. There are more current methods all over the 'net.

I currently have an NT4 domain with domain name 'mydomain'. I have also installed SBS 2003 R2 with a different domain name 'newdoain.local'. The SBS server is not configured as a DC and AD iis not active. I access an mission critical databes, running on SQL on the SBS server via the IP address. I also have a 2003 Standard Edition server (NOT a DC and No AD), purely running as a webserver. I would now like to install a second Windows 2003 server as a DC with AD and migrate the NT4 users. Would I still be able to access the SBS server and the SQL DB. So, before NT4 Server = mydomain (presumably a domain controller) SBS 2003 = newdomain.local, not a DC, AD not running, runs databases Standard 2003#1 = unspecified domain, not a DC, AD not running, runs IIS After NT4 Server = mydomain, taken offline (new) Standard 2003#2 = mydomain.local, domain controller, AD running (unchanged) SBS 2003 = newdomain.local, not a DC, AD not running, runs databases (unchanged) Standard 2003#1 = unspecified domain, not a DC, AD not running, runs IIS I do not, on the face of it, see a problem with the (new) mydomain.local accessing any kind of data on newdomain.local, not a DC and running databases, via its IP address.

sure, see my post in this thread

Add the tweaks to your HIVE files. See my fileset for examples. Tweaks happen at install time when they're supposed to happen that way. My HIVE files have notes in them (search for semicolons to find and read them)

Correct No, the fileset has to be translated to the new language Yes, it yields less satisfactory results but try with txtsetup, layout, sysoc, and syssetup and see, but see note below on keyboard. nLite works okay but it's up to the user to decide what is right for them. IMO my fileset reduces more than nLite, esp. the registry. And in win2k, the size of the registry matters (it doesn't matter so much in xp and 2003 because the entire thing is not loaded at once in those OS's) unfortunately win2k has no drivers for the ahci 7, 8, 9 unless you use (i forget who's) files. To best slipstream, I would suggest manual within txtsetup for the most common controllers such as intel. Look in sysoc and the list of infs.always in syssetup and you will see the components. There are not many win2k resources since my tutorial was all there was for a long time. At the time, many people did not understand the fundamental problem of IE's security flaws. For many, many years, people insisted that having IE but not using it was safe. Heck, there are STILL people who think this who have obviously never read a complete Microsoft security bulletin and who do not understand zones. By the time XP came around, people had started to believe and started to read more, and suddenly cared about eliminating bloat since 2000 was so streamlined. So, bottom line, my list is -the- list. I think that would be GREAT, a lot of people would welcome it You will have to mainly open the french equivalent files and make sure that the strings contain french not english, and make sure to edit txtsetup and layout so that the correct keyboard is selected and not 409 (409 is EN). That is actually a lot more work than you might think. There are a LOT of places to change 409 to your own keyboard.