Slipstreaming Windows XP
Linc
OwnerDetroit Icrontian
Thrax shows us the easiest way to slipstream Windows XP.
When Windows XP was released in 2001, it was not foreseen that specialized hard drive controllers for a new generation of hard drives would become the norm. As IDE died its slow death, the rise of SATA prevented the venerable floppy drive from going with it. While Vista accepts CDs and flash drives containing SATA drivers, XP recognizes only the dreaded floppy. Adding insult to injury, those lucky few who have a drive and the appropriate disk are met with scores of updates once Windows is installed. Pleasantly, there is a solution to these common irritations known as "slipstreaming."
0
Comments
Well done, Rob- and thanks.
Rob (Thrax) has done a great job walking us through the process and, much to my chagrin, made my way of slipstreaming obsolete.
You have outdone yourself. That's slick. Shall be following that in the week when I reinstall my desktop (finally!). Cool read
The only problem I had was getting the article printed out without all of the ads & comments. Not finding a print option on the web page I used print preview, paged through until I found "about the author" and used that to print out the pages up to that for each web page of the article.
I am asuming that you play Tabula Rasa since your forum name is Thrax. Zarlon is my toon name when I play.
Thank You
Zarlon
I'm very glad I could help you with one of my articles, Zarlon! Thanks for commenting.
Nice suggestion.
cheers
You indicate that we can add programs by downloading them into the Addons directory. Do they just go into that directory or subdirectories?
I am building two versions, one an OEM (for me at home) and other is a VLK for work. Knowing how they go into the Addons directory will save me valuable time both at work and with my family/friends.
Thank You
Zarlon
PS. I am in the process of looking at all of your articles. Man you are a fountain of information & procedures. You are
after a very long sleepless weekend, hours of foul language and one big pile of newly burnt useless winxp installation cds - I am left to discover that all hope is lost and despite my heroic efforts to manually (and later with nlite) slipstream blooming windows xp - so it could acknowledge the existence of my very real (just ask Fedora) WD80 SATA drive on my crappy ASUS P4S800D MOBO - the forces of money grabbing evil (i.e SIS hatred, Micro[on global scale]Soft Evil and the rest of the lot) have once more prevailed! for it seems a "txtmode" version of the SIS 180 or 180OB - which according to section 5 of the slipstreaming article is needed for the rest of the just battle - is no where to be found on the World Wide Web - so it seems the only solution will be to write this weird forum S.O.S!
guys where's that driver in txtmode anyone anyone at all!?!?!
p.s
thanks for the article btw if I didn't stumble upon in it (round 4 am or so but still) I would keep burning copies of winxp containing cursed PNP drivers for ever!
m.
http://www.microsoft.com/downloads/Browse.aspx?displaylang=en&categoryid=4
and can you help me with the 2nd and most critical problem ?? why do all the exe s prompt as if i have to install them ?? and when i cancel them, nlite says that the addon is not the expected type...
Cheers...
Cheers...
I appreciate the help that even the tech at the computer store could not give me. I will tell everyone I know that may be interested in this article all about it, and I look forward to reading more of your work.
You are a life saver. Keep it up.:bigggrin::bigggrin::bigggrin:
No problem, Bandrik! Thanks for commenting!
it is the first i m integrating components and drivers into a winxp cd
thanx a lot
I pretty much follow the recommended slimming of the XP install, adding SP3, firefox, AVG, a few small hardware drivers, etc. Nothing radical. However my install is lagging out when it starts to install network devices. I do have a blown LAN port on my motherboard, replaced with a PCI lan. Other than that it's fairly straightforward. Any ideas where I went wrong to be lagging out here?
Thanks in advance,
-V
Can you take a camera picture of that screen?
Welcome to Icrontic!
During the windows install, after it's installed all the system devices, I hang up at "Installing network components". The blue progress bar gets to about 30% then it will hang there forever. I let it run overnight just to be sure. My normal XPsp2 install cd works fine, and that's the one I used as a source with nlite.
I tried another slipstream version this morning with the same results. That's odd, considering the very first time I tried this as a test on my test laptop everything worked great.
A few other notes:
-my first test showed the modern XP install screens, not the classic. No matter which option I chose last night and today I'm getting the classic install prompts.
-possibly related? My blown onboard LAN started working after a fresh install, but when I installed SP3, it went dead again. Maybe SP3 has an issue with this particular lan?
Thanks for the response and I look forward to browsing your forum daily!
-V
Did you slipstream your network drivers when making an SP3 disc?
If the slipstreamed XPsp3 disk doesn't support a driver will it hang like that? I always thought it just skipped over unknown devices and left the lovely "?" in device manger.
Either way I took the long route and did a Sp2 install and spent the day installing updates and obscure drivers :P. I'm definitely going to make a custom Xpsp3 disk again for this machine as well as my others but without testing it further I get the feeling that tracking down this particular issue might be tricky.
I'm thinking of starting fresh with another slipstream, this time only taking out a few things (not drivers this time) and adding the essential drivers I need (m.b., audio, video etc). Hopefully I won't need it anytime soon, but my data backup is current and I can always take the long route again if needed.
An alternate idea is to troubleshoot this on my older machine. I don't use it for anything other than studio recording so it's super easy to test on. Maybe I'll try another custom install and see if I can replicate the network issue. If not I'm guessing it's the driver conflict with sp3.
-V