I have found many sites that give directions for doing a trimmed-down custom install of XP Pro, but nowhere is ever mentioned whether a custom install of SP 2 & 3 can be done. Is there any way to install only specific components of these Service Packs and discard the unneeded?
It's all or nothing for the SP so far as I understand it, should one thing fail, the entire process likely will. What I do (did) was integrate the SP using my original install disc. After this I used NLite (http://www.nliteos.com/) to trim it down for my specific scenario. I currently only use this XP disc (actually variations of it) on two VM's but both are based off of the original 'integrated' disc I created many years ago. My original disc was SP2 so I only had to add SP3 (+all updates to my current base image) before removing what I didn't need/want for each install afterward. I currently use NTLite (https://www.ntlite.com/) for my actual Win 7 installs and a few Win 10 test builds (though Win 10 is a bit more problematic so far in my experience I expect it'll quickly become better once the OS is finalized for RTM). It's been many years and there is no doubt (in my mind at least) that Nuhi knows what he's doing with these programs! That's not to say you can't mess it up yourself by removing things you need but don't recognize. A VM for testing is suggested and is certainly a requirement in my experience.
@Uitlander Its been a while since I last compiled any trimmed down down version of windows. The best place to start looking is an nlite user guide as syrinx mentioned. You will need and an install disk and an .iso program such as daemon tools or power iso, that can mount/compile and extract these images. http://www.nliteos.com/guide/part1.html http://www.nliteos.com/guide/part2.html http://www.nliteos.com/guide/part3.html Albeit, im sure if you know where to look on the web, you can already find pre-compiled images of activated XP3 that are around 320MB. Be sure to read the notes to make sure it still has the features you need.
Do you know where I can find all the security updates and patches for XP64? So I can slipstream them into a iso.
Iv been using "WindowsUpdateDownloader" http://www.windowsupdatesdownloader.com/ there is also http://www.majorgeeks.com/files/details/windows_hotfix_downloader.htmlyou could try should the other not work. Select from the list, ie XP64, it downloads selected KB's and service packs so you can slipstream them via nlite or similar tools. regards.
I have been combing through SP3, and already identified over 150 components in SP2 that I'd call bloatware. As example, 'fixes' for Telnet, WMP, Outlook, IRC, and other junk that will not be installed (or will be uninstalled). I am eager to find a way to get rid of these space-wasters, either pre-installation via nLite, or post-installation using XPlite. I have already hit a snag in my plan to use nLite. Its site says it requires an OS, along with .NET Framework be present on the rig prior to use. My starting point will be a custom-build, which means a total blank slate (no operating system or software at all). Not sure how this will work out, or where to start. I suppose I could install the whole thing, which is "Windows XP Professional - FULL RETAIL+SP3 (XP PRO) (E85-01011/E85-00086)", then rip away everything I can with XPlite Pro, then follow the instructions given in the links by TS4H to use nLite? Not sure how to proceed. Advice?
Many thanks for the links. I have printed their contents out, and will study them at home. I am always keen to find such info on nLite or XPlite. As mentioned in my answer to syrinx, I have an install disc but nothing else. I'm not familiar with PowerIso, but will look into it. Daemon Tools is now infamous as a purveyor of crapware (aka PUPs) hidden in their installer. I have heard there is an older version sans the malware, but unable to determine its version number.
You'll likely only want to use one program or the other. nLite helps trim the ISO down so that when windows is installed, it's already removed the things you selected and this is the cleanest approach in my opinion. XPLite can only be used on a 'live' or active system so far as I remember but I always prefer to test the changes in a VM even with nLite or its newer sibling NTLite so that I can make adjustments without having to restore my actual system over and over and over...until I get it right. In addition, once you have finished an nLited build that satisfies you the rules can be saved and adjusted in the future using the original/same ISO. With nLite you essentially re-build the Windows XP install disc. Obviously nLite itself requires a computer w an OS in order for you to work on the ISO. Once that ISO revision is completed (tested and burned to a CD/DVD) you do not need nLite to be installed, nor the .NET framework for the target system. The biggest issues may be in identifying the required drivers to keep.
Wow I have forgotten about this thread. As syrinx mention your biggest issue is removing non essential drivers. Compatibility may also be an issue if you wish to install the image on brand new hardware, so keep that in mind. Maybe install XP on the hardware you plan to install it on then check for incompatible drivers if everything is functioning as normal then compile your nlite on that hardware. nlite should be able to import the drivers list from the PC you are on. You can then trim it back using nlite and reinstall. Let us know you go. regards.
As mentioned, the first hurdle to overcome is the fact this will is a custom-build with no software. As such, nLite is useless until an OS and .NET is installed, and according to TS4H, an iso program is also required. Since I do not have access to a secondary computer, other than public computers that do not allow any sort of downloads, this seems to eliminate use of nLite. The only thing I can think of is to install the full XP Pro SP3 disc, use XPlite to rip out as much bloat as possible, then install what is needed to use the nLite, and proceed from there. I cannot think of any other way to meet the requirements of nLite, other then to buy a second PC and work from it, which I don't see happening. As for virtual stuff, I plan on tinkering with VirtualBox eventually, but that is likely years off.
