Anybody here ever slipstream install disks?

[Ar-Pharazon]

I've seen this referenced as a way to make a new XP install disk (for example) and include service packs and all the security updates so as not to have to go through all those updates if/when you have to reinstall.

Googled this, and keep finding instructions that talk about slipstreaming the SP's, but not much about all the other updates.

Any thoughts?

 

[Alpha_Geek]

No help from me, I always update by hand and then create a recovery image file with Ghost.

If you're looking to deploy the same load on multiple machines, you can use an image if you run sysprep prior to shutting down the model system and then image that drive for duplication. All nice and legal that way as the customer has to enter their COA number.

Not exactly the data you wanted, but hopefully useful in some way.

AG

 

[SalvorHardin]

Yes, I've done this in the past to incorporate the XP SP2 and to incorporate the Vista SP1 and various drivers for my hardware or other updates.

Both attempts were successful and save a lot of time when I have to format and reinstall for some reason.
But don't ask me to tell you how. I used google and guides found there and don't really remember the process.

 

[farmkid]

The best way I've found to do it is with a program called nLite. With nLite, you can customize your installation however you want. You can add or remove any Windows components you want, slipstream service packs, integrate any programs or drivers you want, automatically enter the COA number, etc. I haven't tried, but I'm sure you can include any updates as well.

The last time I used it was to create a custom Windows install disk for my home computer. I wanted to install Windows on a SATA disk, but I don't have a floppy drive for installation of the SATA drivers during the install process. I was able to use nLite to integrate the SATA drivers so that they were loaded during the install process.

 

[SalvorHardin]

The best way I've found to do it is with a program called nLite. With nLite, you can customize your installation however you want. You can add or remove any Windows components you want, slipstream service packs, integrate any programs or drivers you want, automatically enter the COA number, etc. I haven't tried, but I'm sure you can include any updates as well.

The last time I used it was to create a custom Windows install disk for my home computer. I wanted to install Windows on a SATA disk, but I don't have a floppy drive for installation of the SATA drivers during the install process. I was able to use nLite to integrate the SATA drivers so that they were loaded during the install process.

Ah, yes. that's the one I've used to do it too.
nLite.

 

[Ar-Pharazon]

Thanks for the replies. I'd seen nLite mentioned, I'll have to give it a try.

 

[Robert Maxwell]

I, too, use nLite. I had zero experience slipstreaming, and I had to work a special RAID driver into an XP install disc. nLite made it incredibly painless and simple.

 

[Mr. B]

A did this procedure a while back. With the instructions in hand it's pretty easy. What do you mean by "other updates?" Service Pack 3 is rather comprehensive.

 

[PurpleBuddha]

Navigating the slipstream can be difficult. Do not let your computer attempt to do it for you.

 

[Ar-Pharazon]

A did this procedure a while back. With the instructions in hand it's pretty easy. What do you mean by "other updates?" Service Pack 3 is rather comprehensive.

"other" being the 100 or so security updates for the OS, IE and WMP. I have XPx64, so there is an SP2 for it, but it still has many, many updates even after SP2 is installed.

Initially I wanted to do an AHCI driver with my old motherboard, because I thought it might be the only way to utilize more than 4 of the 8 SATA connectors on that board. But it turned out that board had other problems, so I have a new mobo in now.

I still want to do this so if (when) I have to reinstall, it's a quicker & easier process. I may try this over the weekend.

 

[Mr. B]

In that case you'd be better off with an image of the completed installation.

 

[Ar-Pharazon]

3 tries, 3 FAILS. Technically 1 near fail and 2 fails.

1st try - Installed XP, but some of the settings I chose were ignored. No drivers were integrated, but I found that was my fault for not copying the drivers folders to the local drive.

2nd try - Learned from the 1st try to delete the hotfixes prior to SP2 so time wasn't wasted hitting "OK" when it said they weren't "for this version of Windows". They were x64 updates, but I think they were superseded by SP2, which was slipstreamed earlier in the process. After another full format and install, got BSOD when Windows tried to start. Tried to restart a couple times, same result.

3rd try - Did the slipstream process from scratch so no bad info got repeated. Same result as 2nd try, BSOD upon completion and first Windows start.

On top of all that, a second app was needed to slipstream Windows Media Player 11, nLite couldn't deal with it on it's own. That's a little lame, but the overall crapfest it turned out to be is really pissing me off. I've wasted almost 12 hours and 3 CD-R's. Could there be a problem in the burning process?

Luckily, I am doing this with an extra internal HDD, so no loss of a working OS.

 

[farmkid]

When I used nLite, I found that I had carefully follow the instructions. I also had several failures before I got my SATA drivers integrated, but it finally worked. Look around for a tutorial, and follow it carefully. Also, as I remember, you might need to go find a different boot sector image, or something like that. To avoid making coasters, I used a CD-RW with each tweak I made until I got an image that worked.

 

[Ar-Pharazon]

I'll have to find a good tutorial then. The 3 pages of instructions from the nLite website were very basic, but I followed those to the letter.
But aside from the first go, where I didn't sort the hotfixes and had to keep hitting "yes" when it wanted to know whether to keep the newer version of .dll's or not and the "hotfix not for this version of Windows" nonsense, there weren't really any problems with that aspect.

The later attempts were even quicker once I got rid of the redundant hotfixes and sorted them properly. Only 2 or 3 "not for this version" messages. I even tried a couple more times and did away with the integrated drivers, like the first attempt, no dice. BSOD again.

I wonder if this is more x64 quirkiness.

 

[farmkid]

I wonder if this is more x64 quirkiness.

It could be. I've never used x64, so I have heard that it's a little more temperamental than its 32-bit sibling. I never had BSODs with nLite; the problems I had was that it either wouldn't boot, or it wouldn't load the drivers I was trying to integrate. It might be worth your time to spend a few minutes of quality time with Google to see if anyone else has successfully used nLite with x64.

 

[Ar-Pharazon]

As far as your drivers, did you copy the drivers folders to your HDD?

That's what I did wrong the first time around. It seemed like it was "integrating" the drivers from their respective CDs early in the process, but when it got down to creating the finished product, it had a "device not ready" message. I realized on the second try it was looking for the drivers on the DVD drive I originally had the disks in earlier on.

 

[farmkid]

In my case, it seems I had to create a new folder in the directory where the Windows install stuff was. It didn't make a lot of sense, but it worked.

...I just found the directions I used. Here they are. I know this isn't the issue you are having, but you might learn something that will point you in the right direction.

 

[Meredith]

I have, nLite looks intriging

 

[Robert Maxwell]

Here are the instructions I used to slipstream RAID drivers. Worked the first time. I hope it helps.

 

[Ar-Pharazon]

^ Mostly these are the same as other instructions I've seen, but with RAID related stuff added. I'm not doing any RAID stuff, but these also talk about finding the Windows install directory on your C:, which I can't seem to find (at least nothing nLite considers acceptable). So I use the original XP disk like it also suggests.

Tried it one more time, did ONLY XP, SP2, WMP11, a few drivers and a few tweaks at the end. Left out all hotfixes and updates, just to see.

Same result, BSOD on first actual Windows start.

Pretty much giving up on this POS. It doesn't seem like I'm meant to be able to make it work.

But thanks for the replies and glad to hear some of you have gotten it to do something other than waste your time.