Hello All, I've was directed here from another site.
I'm attempting to create a restore cd by slipstreaming XP with Sp2, both are each on their respective cds. I've copied the files from each to folders on my HD. The process seem to require files from the XP cd, and the downloaded service pack files into their respective folders.
PROBLEM: I need to integrate files from both folders of the XP CD and the SP2 CD. I've copied the files they are already there how do I merge them together.
Using nLite seem to involve the downloaded form of the XP SP2 files, but my files are on the SP2 CD, and I don't see how to integrate. them.
How am I going wrong!
Click to view attachment
regards,
Asamp
Full Version: Slipstreaming XP with Sp2 CD files
Your source folder will be F:\XP (and F:\ must be writable, i.e. hard drive). That's what you point nLite to as source.
You slipstream that source with XPSP2.EXE located in F:\XP-SP2 on your pic (doesn't matter if it's writable or not). That file is the only one needed, assumming it's the real thing (272 MB, downloaded from here, original name WindowsXP-KB835935-SP2-ENU.exe).
GL
You slipstream that source with XPSP2.EXE located in F:\XP-SP2 on your pic (doesn't matter if it's writable or not). That file is the only one needed, assumming it's the real thing (272 MB, downloaded from here, original name WindowsXP-KB835935-SP2-ENU.exe).
GL
Hello GrofLuigi,
thanks for the reply managed the .iso and burned it to cd using Roxio Media Creator. I will attempt the installation on my F: drive tomorrow to see how it works. From what I've read, no one has attempted to slipstreamed a restore cd with a sp. Will report the results.
Regards,
Alsamp
thanks for the reply managed the .iso and burned it to cd using Roxio Media Creator. I will attempt the installation on my F: drive tomorrow to see how it works. From what I've read, no one has attempted to slipstreamed a restore cd with a sp. Will report the results.
Regards,
Alsamp
Hello All, reporting back as promised. I attempted to install the XPP SP2 cd, and the installation would not accept my product key. Its the product key for my original XP also I configured n-Lite to slipstream with the key preinstalled perhaps this was the problem. 
Anyone have any ideas or have had this problem?
Regards,
Asamp
Anyone have any ideas or have had this problem?
Regards,
Asamp
QUOTE (Asamp @ Jul 21 2008, 02:27 AM) 
From what I've read, no one has attempted to slipstreamed a restore cd with a sp.
I think they have attempted, but failed.
QUOTE (Asamp @ Jul 21 2008, 10:37 PM)
Hello All, reporting back as promised. I attempted to install the XPP SP2 cd, and the installation would not accept my product key. Its the product key for my original XP also I configured n-Lite to slipstream with the key preinstalled perhaps this was the problem.
Anyone have any ideas or have had this problem?
Regards,
Asamp
Anyone have any ideas or have had this problem?
Regards,
Asamp
Depends on what operating system you were doing the slipstreaming. There were reports of various cases of either nLite or Vista not properly slipstreaming (interfering with) some product keys. Latest revisions of nLite addressed these issues. Have you tried them (the last came out yesterday)? And searching/browsing the nlite forum wouldn't hurt... I bet you'll stuble onto your issue.
GL
* Edit: But those issues were mostly with XP SP3 (and BTW why don't you integrate that? It's not much different from SP2.) Maybe try playing with unattended mode or do full slipstream (either manually or don't do anything else with nLite and then check if it will accept your key).
Final Report. Let me start by noting that my above comments involved using nLite 1.4.6 because I’d read that the recent release 1.4.7 didn’t burn the .ISO to cd.
I’m using nLite 1.4.8 as suggested here in this forum. The slipstreaming when well, but when I attempted to burn the disc the app needed to format the cd then froze in the middle of the process. I did a force quit via task manager, formatted the cd in windows and started up again.
Once in, I started up using the last session then attempted to burn the cd, the application claimed it did just that, but there wasn’t a file on cd, in fact I could not find the file in the place that I saved it. I reasoned that the .iso was lost, or not created, quit the app, rebooted my machine then tried again. I deleted the last session saved and started fresh. Fast slipstreaming, but the file was not saved in my folder then I open a window and notice the .iso file was in C:\. I then began to burn the file to cd, but the app indicated that it needed to format it which I’d done thru windows, so I used a different cd, which it accepted. The app claimed it burned the .iso to the cd but it did not, so using Roxio Media Creator 7.5, I burned the .iso to cd and, finally had a WinLite XPP SP2 cd.
I proceeded to reboot then attempt to install the O/S only to be faced with the same problem. My product key number was already coded in the boxes and the prompt box “Invalid product key” appeared very prominently.
Your experience my vary, but this did not work to my satisfaction.
Regards,
Asamp
I’m using nLite 1.4.8 as suggested here in this forum. The slipstreaming when well, but when I attempted to burn the disc the app needed to format the cd then froze in the middle of the process. I did a force quit via task manager, formatted the cd in windows and started up again.
Once in, I started up using the last session then attempted to burn the cd, the application claimed it did just that, but there wasn’t a file on cd, in fact I could not find the file in the place that I saved it. I reasoned that the .iso was lost, or not created, quit the app, rebooted my machine then tried again. I deleted the last session saved and started fresh. Fast slipstreaming, but the file was not saved in my folder then I open a window and notice the .iso file was in C:\. I then began to burn the file to cd, but the app indicated that it needed to format it which I’d done thru windows, so I used a different cd, which it accepted. The app claimed it burned the .iso to the cd but it did not, so using Roxio Media Creator 7.5, I burned the .iso to cd and, finally had a WinLite XPP SP2 cd.
I proceeded to reboot then attempt to install the O/S only to be faced with the same problem. My product key number was already coded in the boxes and the prompt box “Invalid product key” appeared very prominently.
Your experience my vary, but this did not work to my satisfaction.
Regards,
Asamp
Sorry if it didn't work out well. If you are not giving up, I have some suggestions for you:
Since you have problems, don't burn from nLite. Just use the "Make ISO" button on the Bootable ISO screen of nLite, it will ask you for a filename and you can burn that with your favorite app.
If you use Last Session, you must start from scratch and recreate the steps you did before (point to the original source files and do all integration/removal again). Or, you could just load your session and deselect the pages you don't need (for example, if you made it to the end but didn't succeed in burning, select just the Bootable ISO page and use your processed directory as source).
If you're using RW discs, try erasing them before you start, either in nLite or in your app. BTW, Roxio is not seen as a top notch burning app any more, why don't you try ImgBurn for a change. It's specialized in burning ISO files, it's lightweight and can do many other things (and also try erasing with it).
About the not accepting CD key problem: There can be many reasons for that, not easily discovered. First, Microsoft changes (blacklists) their accepted keys with every Service Pack. Then there is (was) the issue I wrote about in my previous post. That's why I suggested you try slipstreaming manually to see if nLite is the culprit (which I seriously doubt). Then, there are different settings of Unattended Mode (maybe in combination with Skip OOBE and/or Remove OOBE) that can influence accepting the key. Try taking out every variable that may influence the result (unatended, addons, removals, tweaks etc.)
Could youpost attach your Last Session.ini?
GL
Since you have problems, don't burn from nLite. Just use the "Make ISO" button on the Bootable ISO screen of nLite, it will ask you for a filename and you can burn that with your favorite app.
If you use Last Session, you must start from scratch and recreate the steps you did before (point to the original source files and do all integration/removal again). Or, you could just load your session and deselect the pages you don't need (for example, if you made it to the end but didn't succeed in burning, select just the Bootable ISO page and use your processed directory as source).
If you're using RW discs, try erasing them before you start, either in nLite or in your app. BTW, Roxio is not seen as a top notch burning app any more, why don't you try ImgBurn for a change. It's specialized in burning ISO files, it's lightweight and can do many other things (and also try erasing with it).
About the not accepting CD key problem: There can be many reasons for that, not easily discovered. First, Microsoft changes (blacklists) their accepted keys with every Service Pack. Then there is (was) the issue I wrote about in my previous post. That's why I suggested you try slipstreaming manually to see if nLite is the culprit (which I seriously doubt). Then, there are different settings of Unattended Mode (maybe in combination with Skip OOBE and/or Remove OOBE) that can influence accepting the key. Try taking out every variable that may influence the result (unatended, addons, removals, tweaks etc.)
Could you
GL
QUOTE (GrofLuigi @ Jul 22 2008, 06:18 PM)
Sorry if it didn't work out well. If you are not giving up, I have some suggestions for you:
Since you have problems, don't burn from nLite. Just use the "Make ISO" button on the Bootable ISO screen of nLite, it will ask you for a filename and you can burn that with your favorite app.
If you use Last Session, you must start from scratch and recreate the steps you did before (point to the original source files and do all integration/removal again). Or, you could just load your session and deselect the pages you don't need (for example, if you made it to the end but didn't succeed in burning, select just the Bootable ISO page and use your processed directory as source).
If you're using RW discs, try erasing them before you start, either in nLite or in your app. BTW, Roxio is not seen as a top notch burning app any more, why don't you try ImgBurn for a change. It's specialized in burning ISO files, it's lightweight and can do many other things (and also try erasing with it).
About the not accepting CD key problem: There can be many reasons for that, not easily discovered. First, Microsoft changes (blacklists) their accepted keys with every Service Pack. Then there is (was) the issue I wrote about in my previous post. That's why I suggested you try slipstreaming manually to see if nLite is the culprit (which I seriously doubt). Then, there are different settings of Unattended Mode (maybe in combination with Skip OOBE and/or Remove OOBE) that can influence accepting the key. Try taking out every variable that may influence the result (unatended, addons, removals, tweaks etc.)
Could youpost attach your Last Session.ini?
GL
Since you have problems, don't burn from nLite. Just use the "Make ISO" button on the Bootable ISO screen of nLite, it will ask you for a filename and you can burn that with your favorite app.
If you use Last Session, you must start from scratch and recreate the steps you did before (point to the original source files and do all integration/removal again). Or, you could just load your session and deselect the pages you don't need (for example, if you made it to the end but didn't succeed in burning, select just the Bootable ISO page and use your processed directory as source).
If you're using RW discs, try erasing them before you start, either in nLite or in your app. BTW, Roxio is not seen as a top notch burning app any more, why don't you try ImgBurn for a change. It's specialized in burning ISO files, it's lightweight and can do many other things (and also try erasing with it).
About the not accepting CD key problem: There can be many reasons for that, not easily discovered. First, Microsoft changes (blacklists) their accepted keys with every Service Pack. Then there is (was) the issue I wrote about in my previous post. That's why I suggested you try slipstreaming manually to see if nLite is the culprit (which I seriously doubt). Then, there are different settings of Unattended Mode (maybe in combination with Skip OOBE and/or Remove OOBE) that can influence accepting the key. Try taking out every variable that may influence the result (unatended, addons, removals, tweaks etc.)
Could you
GL
Hello Luigi, if you combine my previous post with my last you'll see a pattern which is this app is faulty.
1. I've already explained that I used both versions of nLite to make the iso bootable disc with both of the .iso files displaying the same behavior.
I version of nLite burned the file to disc, the other could not despite indicating that it had.
2. I don't know what version of the app you're using, but in the versions I used; to use the Last Session means to use a preset configuration with save settings from your last session in the app. (your last session is automatically saved).
3. Roxio did its job which was to burn the iso file to cd, and nLite 1.4.6 did the very same however both producing the same final results.
4. As I indicated in my previous post, initially I configured the app to include my product key but after the failure, I only took the defaults. This means no addons, unattended mode, tweaks etc.
Finally, you seem to be making comment about MS etc, I don't see what this has to do with the key problem. If you read my post my SP2 was on a separate cd not a dl, also a fresh install from the original XP disc accepts the product key with no problem, then I install SP2 over it.
The point is that it did not work. I also can not post the session.ini since I've dumped the app. However, I can recommend that if you going to use nLite use version 1.4.6, at least it will slipstream, create the iso, and burn it to cd feats the current version "1.4.8" failed to do.
regards,
Asamp
OK, have fun. I just tried to help. 
nLite has always worked for me.
GL
nLite has always worked for me.
GL
Hi again GL, I think what would help in this forum is, if users post their spec in their signature. This way people have an idea if their project has a chance or not. You say that it worked for you, but what was your project. What was it that you slipstreamed using which version of the app etc.
regards,
Asamp
regards,
Asamp
QUOTE (Asamp @ Jul 23 2008, 04:26 PM)
Hi again GL, I think what would help in this forum is, if users post their spec in their signature. This way people have an idea if their project has a chance or not. You say that it worked for you, but what was your project. What was it that you slipstreamed using which version of the app etc.
regards,
Asamp
regards,
Asamp
I don't think the computer specs are important. Only that it works well in general - no RAM/HDD problems, no crashes. I've used many versions of nLite on several computers without problems. As for my usage, I always start fresh (copy files from a source CD).
The source is the most important aspect of nLite. Recovery CDs from computer manufacturers are (nearly) always a no-no, as well as 'customized' in any way. It's even worse if they were customized by someone else.
I use retail XP Pro disc and slipstream the latest service pack. I utilize nearly all nLite's features (pages) and integrate hotfixes, but rarely (nearly never) addons - I don't see the need for them. Maybe my usage pattern is different from what most other people do - I don't work with unattended integration of programs because I don't do mass install on many computers - and I take my time with installing programs afterwards.
Oh, and another aspect very important aspect for nLite is that your .Net framework installation works well. I had zero problems (with nLite & other programs) using .Net 2.0 Service Pack 1.
GL
Hello GL,
if more users posted their spec i.e., "I use retail XP Pro disc and slipstream the latest service pack" then this would have saved me resources e.g., time, headaches, etc. However, as it stands now a user is flying blind, and the FAQ doesn't address the issue either.
So my spec are: restore disc: XPP with SP2 both on disc is a no go. configuration: all defaults. App will slipstream but O/S would not accept product key.
regards,
Asamp
note: I did not mention "computer specs"
if more users posted their spec i.e., "I use retail XP Pro disc and slipstream the latest service pack" then this would have saved me resources e.g., time, headaches, etc. However, as it stands now a user is flying blind, and the FAQ doesn't address the issue either.
So my spec are: restore disc: XPP with SP2 both on disc is a no go. configuration: all defaults. App will slipstream but O/S would not accept product key.
regards,
Asamp
note: I did not mention "computer specs"
QUOTE (Asamp @ Jul 24 2008, 12:25 AM)
So my spec are: restore disc: XPP with SP2 both on disc is a no go. configuration: all defaults.
What is XPP? XP Pro?
What do you mean by restore disc? I meant recovery CDs as received together with a new computer from OEM manufacturer.
GL
Yes! Restore or Recovery is the same thing. I purchased my computer from Alienware and the cd was included, so I can do a fresh install of the O/S. However, that was 02' and its time to move on, I don't know if I can install this on a completely new computer because this one is history.
regards,
Asamp
regards,
Asamp
QUOTE (Asamp @ Jul 24 2008, 03:17 AM)
Yes! Restore or Recovery is the same thing. I purchased my computer from Alienware and the cd was included, so I can do a fresh install of the O/S. However, that was 02' and its time to move on, I don't know if I can install this on a completely new computer because this one is history.
regards,
Asamp
regards,
Asamp
Someone who has experience with Alienware can correct me if I'm wrong, but I'm pretty sure you can't use this CD on a new computer and/or you can't properly slipstream it (the installation CD) with a Service Pack. This is windows XP OEM version, tied with the computer, probably customized by Alienware, already activated with Microsoft (WGA).
If Alienware gives uncustomized CD, then I'm wrong.
GL
Hello GL,
what do you mean by "tied with the computer" because I've completed a fresh install on another HD. I had to install the driver for the board activate the O/S etc. My impression was that you could move the O/S to another computer, but could not have the O/S on more than one computer at any one time.
regards,
Asamp
what do you mean by "tied with the computer" because I've completed a fresh install on another HD. I had to install the driver for the board activate the O/S etc. My impression was that you could move the O/S to another computer, but could not have the O/S on more than one computer at any one time.
regards,
Asamp
QUOTE (Asamp @ Jul 25 2008, 03:48 AM)
Hello GL,
what do you mean by "tied with the computer" because I've completed a fresh install on another HD. I had to install the driver for the board activate the O/S etc. My impression was that you could move the O/S to another computer, but could not have the O/S on more than one computer at any one time.
regards,
Asamp
what do you mean by "tied with the computer" because I've completed a fresh install on another HD. I had to install the driver for the board activate the O/S etc. My impression was that you could move the O/S to another computer, but could not have the O/S on more than one computer at any one time.
regards,
Asamp
Windows Product Activation.
Some versions of XP can be moved to another computer, some cannot. Since this looks like an OEM version, I think it couldn't. But depends how Alienware has implemented it.
GL
Well, its a Recovery cd where I can do a fresh install, repair the O/S, etc, but i still have to activate the O/S with the product key. I did a fresh install on another HD, and of course activated the product. Now, I'm building a new pc, and want to move the O/S to a new computer then dump the other computer. The O/S will be on one computer.
Regards,
Asamp
Regards,
Asamp
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.