Slipstreaming Windows XP Service Pack 2 & Boot CD!


Recommended Posts

  • 3 weeks later...

It's funny because nlite (install) worked fine on my and a friend of mine's computer. but another friend it just blew up :)

Anyway, I wanted to ask if the sp1 serial number would work with the slip streamed sp2. I believe that when I was using windows2000 and trying to do the exact them thing years ago (slipstream service pack x), w2k wouldn't except the serial...or maybe I'm crazy being up this late at night/early morning and imagining things :) It was the OEM version.

I tried this german program (spend many hours with babelfish translating words into a text file) but could never get it to work... Winfuture xp iso builder

Congratulations, Peter, on a really well-thought-out manual.

I haven't needed to slipstream anymore since I finished the SP2 slipstream.

This was successful but before I saw your guidelines (too bad for me, eh?!)

I am, however, very intetrested in the additions that you are planning for your manual -the how-to 'stream other programs, not just service packs.

I am also into image backups at the moment. These seem to reduce (but not remove) the need for slipstreaming.

Great to communicate with another (Adelaidean) Aussie!

Regards & all the best for the continuance of your project.

Malcolm

  • 4 weeks later...

Hi ptiliffe!

You have a great guide! :D I was wondering if you were still endeavoring to add more to this guide? If so, I have alot of information about attempting to slipstream sp2 onto a Dell XP home sp1 OEM cd. I keep getting the error about usbehci.sys is corrupted everytime I boot off of the CDs I make.

I have tried it using nlite just to slipstream, same error (usbehci.sys is corrupted).

I have tried it using nlite to slipstream and create the iso image, same error (usbehci.sys is corrupted).

I have tried doing it all manually, following this guide:

http://vbdotnet.home.comcast.net/XP_SP2.htm

then using the instructions at this link, as joliet format is recommended for this process using Roxio Easy CD Creator version 5.x (which is the version I have):

http://www.tacktech.com/display.cfm?ttid=298

and I still get the same error (usbehci.sys is corrupted).

I have tried using Autostreamer, but next is always grayed out and it won't let me continue.

I made 3 cds with the same problem so far, and I am sure of a few things. I don't think the dell cd has the problem because when I boot off of it I do not get the usbehci.sys is corrupted error. I also know the problem is not due to the machine or cd drive I boot off of because I have tried them in multiple machines and cd drives.

I am endeavoring to accomplish two goals with this post, one is to document what hasn't worked for me so far to the benefit of others and two to see if anyone has any suggestions about the problem I face here? Thanks again and I hope my information proves beneficial to others.

  • 5 weeks later...

http://www.supanode.com/guides/slipstream_winxp_and_sp2/

THE GUIDE HAS BEEN UPDATED

The above link is the new guide home. It has been down for some time now but should be fully accessible now.

Please note that I am no longer supporting this guide and am no longer writing any further guides. I have done one last update on this guide to make sure that all the links work, the information is still relevant and transfer it to the new domain/hosting.

Please do not ask me to help you with understanding this guide as I have tried my hardest to make it as simple as possible for all people to understand.

Good luck with it and take care.

Kind regards,

Peter Iliffe.

  • 3 months later...

Okay this guide is way over a year old now! But I thought I would still give it a bit of a kick to the top for those of you who may be still interested and have not seen this guide. The good old manual way of doing things! :D Enjoy...

  • 2 months later...

Hi All!

This is my 1st time to join this forum. My apologies if I would not be posting in the correct one.

You my main concern is slipstreaming official & request-only hotfixes. Again, my apologies.

If I may, this how my dilemma goes:

I have been trying to slipstream lots of Hotfixes (official & unofficial) but some always end up needing to be reinstalled. I have tried changing the sequence (by file name, by build date, by date created) with different combinations --- & all seem well until XP finishes it installation. I have also tried using the qchain.exe tool still with the same result. However when I ran qfecheck to verify I encounter reports like the one below.

I suppose there must be a hotfix or some hotfixes that prompt this to happen!

Please look at this log (from the many logs that have already been generated):

Windows XP Hotfix Validation Report for \\BURGH

Report Date: 3/14/2006 5:03am

Current Service Pack Level: Service Pack 2

Hotfixes Identified:

iscsi200: Current on system.

KB307154: Current on system.

KB319740: This hotfix should be reinstalled.

KB816045: Current on system.

KB822686: Current on system.

KB842520: Current on system.

KB843518: Current on system.

KB843541: Current on system.

KB867282: Current on system.

KB867795: Current on system.

KB870975: Current on system.

KB870979: Current on system.

KB870981: Current on system.

KB870997: Current on system.

KB872789: Current on system.

KB872966: Current on system.

KB873333: Current on system.

KB873339: Current on system.

KB873392: Current on system.

KB873396: Current on system.

KB873397: Current on system.

KB873407: Current on system.

KB883483: Current on system.

KB883517: Current on system.

KB883523: This hotfix should be reinstalled.

KB883529: Current on system.

KB883667: Current on system.

KB883939: Current on system.

KB884018: Current on system.

KB884020: Current on system.

KB884038: Current on system.

KB884047: Current on system.

KB884538: This hotfix should be reinstalled.

KB884539: Current on system.

KB884558: Current on system.

KB884562: Current on system.

KB884568: Current on system.

KB884575: This hotfix should be reinstalled.

KB884862: Current on system.

KB884868: This hotfix should be reinstalled.

KB884883: This hotfix should be reinstalled.

KB884897: Current on system.

KB885222: Current on system.

KB885250: Current on system.

KB885293: Current on system.

KB885295: Current on system.

KB885423: Current on system.

KB885443: Current on system.

KB885453: Current on system.

KB885464: Current on system.

KB885523: Current on system.

KB885626: This hotfix should be reinstalled.

KB885835: This hotfix should be reinstalled.

KB885836: Current on system.

KB885843: Current on system.

KB885863: Current on system.

KB885865: Current on system.

KB885887: Current on system.

KB885894: This hotfix should be reinstalled.

KB885898: Current on system.

KB885932: Current on system.

KB886185: Current on system.

KB886199: Current on system.

KB886540: Current on system.

KB886659: Current on system.

KB886677: This hotfix should be reinstalled.

KB886716: This hotfix should be reinstalled.

KB886809: Current on system.

KB887170: This hotfix should be reinstalled.

KB887173: This hotfix should be reinstalled.

KB887186: Current on system.

KB887472: Current on system.

KB887535: Current on system.

KB887569: Current on system.

KB887589: Current on system.

KB887742: This hotfix should be reinstalled.

KB887797: This hotfix should be reinstalled.

KB887816: Current on system.

KB887820: Current on system.

KB887823: Current on system.

KB888083: Current on system.

KB888111: Current on system.

KB888113: This hotfix should be reinstalled.

KB888239: Current on system.

KB888240: Current on system.

KB888254: Current on system.

KB888302: This hotfix should be reinstalled.

KB888321: This hotfix should be reinstalled.

KB888402: Current on system.

KB888413: Current on system.

KB888432: Current on system.

KB888603: Current on system.

KB888622: Current on system.

KB889016: This hotfix should be reinstalled.

KB889073: Current on system.

KB889085: Current on system.

KB889315: This hotfix should be reinstalled.

KB889320: Current on system.

KB889321: Current on system.

KB889334: Current on system.

KB889407: Current on system.

KB889527: Current on system.

KB889673: Current on system.

KB890042: Current on system.

KB890046: This hotfix should be reinstalled.

KB890047: Current on system.

KB890048: Current on system.

KB890175: Current on system.

KB890463: This hotfix should be reinstalled.

KB890546: Current on system.

KB890552: Current on system.

KB890558: Current on system.

KB890582: Current on system.

KB890644: This hotfix should be reinstalled.

KB890733: Current on system.

KB890737: Current on system.

KB890831: This hotfix should be reinstalled.

KB890837: Current on system.

KB890859: This hotfix should be reinstalled.

KB890864: Current on system.

KB890923: Current on system.

KB890927: This hotfix should be reinstalled.

KB890937: Current on system.

KB890946: Current on system.

KB890951: Current on system.

KB890953: Current on system.

KB891019: Current on system.

KB891070: Current on system.

KB891117: Current on system.

KB891220: Current on system.

KB891570: Current on system.

KB891630: Current on system.

KB891781: This hotfix should be reinstalled.

KB891849: Current on system.

KB892050: Current on system.

KB892056: Current on system.

KB892099: Current on system.

KB892227: Current on system.

KB892233: Current on system.

KB892346: Current on system.

KB892489: This hotfix should be reinstalled.

KB892559: Current on system.

KB892627: Current on system.

KB893008: Current on system.

KB893056: Current on system.

KB893066: Current on system.

KB893086: Current on system.

KB893089: Current on system.

KB893226: Current on system.

KB893317: Current on system.

KB893357: Current on system.

KB893376: Current on system.

KB893476: Current on system.

KB893605: Current on system.

KB893609: Current on system.

KB893756: This hotfix should be reinstalled.

KB893803: This hotfix should be reinstalled.

KB893803v2: Current on system.

KB894069: Current on system.

KB894075: Current on system.

KB894083: Current on system.

KB894179: Current on system.

KB894391: Current on system.

KB894395: This hotfix should be reinstalled.

KB894463: Current on system.

KB894472: Current on system.

KB894794: Current on system.

KB894871: Current on system.

KB895246: Current on system.

KB895406: Current on system.

KB895536: Current on system.

KB895900: Current on system.

KB895961: This hotfix should be reinstalled.

KB896166: Current on system.

KB896178: Current on system.

KB896256: This hotfix should be reinstalled.

KB896269: This hotfix should be reinstalled.

KB896336: Current on system.

KB896344: This hotfix should be reinstalled.

KB896358: This hotfix should be reinstalled.

KB896360: This hotfix should be reinstalled.

KB896422: This hotfix should be reinstalled.

KB896423: This hotfix should be reinstalled.

KB896424: This hotfix should be reinstalled.

KB896427: This hotfix should be reinstalled.

KB896428: This hotfix should be reinstalled.

KB896613: Current on system.

KB896626: Current on system.

KB896684: Current on system.

KB896688: Current on system.

KB896725: Current on system.

KB896727: Current on system.

KB896896: Current on system.

KB897327: Current on system.

KB897338: This hotfix should be reinstalled.

KB897574: This hotfix should be reinstalled.

KB897649: Current on system.

KB897663: This hotfix should be reinstalled.

KB897696: Current on system.

KB898068: Current on system.

KB898108: Current on system.

KB898439: This hotfix should be reinstalled.

KB898444: Current on system.

KB898461: Current on system.

KB898543: Current on system.

KB898713: This hotfix should be reinstalled.

KB898781: Current on system.

KB898900: This hotfix should be reinstalled.

KB899271: Current on system.

KB899337: This hotfix should be reinstalled.

KB899344: Current on system.

KB899418: This hotfix should be reinstalled.

KB899510: Current on system.

KB899527: This hotfix should be reinstalled.

KB899587: Current on system.

KB899588: Current on system.

KB899589: This hotfix should be reinstalled.

KB899591: This hotfix should be reinstalled.

KB900411: Current on system.

KB900485: Current on system.

KB900624: Current on system.

KB900725: This hotfix should be reinstalled.

KB900730: This hotfix should be reinstalled.

KB900732: Current on system.

KB900808: This hotfix should be reinstalled.

KB900930: This hotfix should be reinstalled.

KB901017: This hotfix should be reinstalled.

KB901026: Current on system.

KB901122: Current on system.

KB901190: Current on system.

KB901214: This hotfix should be reinstalled.

KB902149: This hotfix should be reinstalled.

KB902400: Current on system.

KB902841: Current on system.

KB902845: Current on system.

KB902853: This hotfix should be reinstalled.

KB903234: This hotfix should be reinstalled.

KB903235: Current on system.

KB903250: Current on system.

KB903737: Current on system.

KB904412: This hotfix should be reinstalled.

KB904636: Current on system.

KB904706: Current on system.

KB905213: Current on system.

KB905299: Current on system.

KB905414: This hotfix should be reinstalled.

KB905519: This hotfix should be reinstalled.

KB905749: This hotfix should be reinstalled.

KB905816: This hotfix should be reinstalled.

KB905915: This hotfix should be reinstalled.

KB906232: Current on system.

KB906472: This hotfix should be reinstalled.

KB906569: This hotfix should be reinstalled.

KB906650: This hotfix should be reinstalled.

KB906681: This hotfix should be reinstalled.

KB906688: Current on system.

KB906693: Current on system.

KB906866: This hotfix should be reinstalled.

KB907265: Current on system.

KB907405: This hotfix should be reinstalled.

KB907572: Current on system.

KB907865: This hotfix should be reinstalled.

KB908519: This hotfix should be reinstalled.

KB908521: Current on system.

KB908673: This hotfix should be reinstalled.

KB909441: This hotfix should be reinstalled.

KB909520: Current on system.

KB909667: This hotfix should be reinstalled.

KB910437: This hotfix should be reinstalled.

KB911262: This hotfix should be reinstalled.

KB911904: This hotfix should be reinstalled.

KB911927: This hotfix should be reinstalled.

KB912024: Current on system.

KB912475: Current on system.

KB912784: This hotfix should be reinstalled.

KB912919: This hotfix should be reinstalled.

KB913296: This hotfix should be reinstalled.

KB913446: This hotfix should be reinstalled.

KB913538: Current on system.

By the way, the files that should be reinstalled or those that are current on the system change for every report that is generated when I finish my patient attempts to reinstall again (& again).

Any help would certainly be appreciated!

Please advise.

Thanks much!

-KIKI-

Mike,

You could create a very basic un-attended install disk (floppy)

;SetupMgrTag

[Data]

AutoPartition=1

MsDosInitiated="0"

UnattendedInstall="Yes"

[unattended]

UnattendMode=FullUnattended

OemSkipEula=Yes

OemPreinstall=No

UnattendSwitch="Yes"

Repartition=Yes

FileSystem=ConvertNTFS

TargetPath=\WINDOWS

[GuiUnattended]

AdminPassword=*

EncryptedAdminPassword=NO

OEMSkipRegional=1

TimeZone=85

OemSkipWelcome=1

[userData]

ProductKey=PRODUCT-KEY-HERE

FullName="Mike Milburn?"

OrgName="."

ComputerName=HOME_PC

[Display]

BitsPerPel=16

Xresolution=1024

YResolution=768

Vrefresh=65

Flags=0

AutoConfirm=1

[TapiLocation]

CountryCode=44

Dialing=Tone

AreaCode=CHANGE AS NESS.

[RegionalSettings]

LanguageGroup=1

SystemLocale=00000809

UserLocale=00000809

InputLocale=0809:00000809

[identification]

JoinWorkgroup=WORKGROUP

[Networking]

InstallDefaultComponents=Yes

[branding]

BrandIEUsingUnattended=Yes

[Proxy]

Proxy_Enable=0

Use_Same_Proxy=0

Save this as winnt.sif (I know some parts may be out of date etc, or not to your preference, but Microsoft has some good guides for changing the options etc).

put it on a floppy, boot to CD and leave the floppy in, it'll read it as soon as setup starts and thats it, you dont need to press anymore keys until Windows is installed.

Also, this currently, takes your primary hard drive and puts a full NTFS partition on it, again this might not be everyone's preference.

I hope thats of some help.

Tom

I use nLite. Just use that, its quick, easy and above all realiable.

My apologizes if noted already, didnt feel like reading through the whole thread.

It has been stated before - however the method written in this guide is for people who want to completely manually slipstream their CD. This tutorial could be easily expanded to cover a lot of other areas including integrating the serial key. Manually I personally beleive can give you much more control if you know what you are doing.

It has been stated before - however the method written in this guide is for people who want to completely manually slipstream their CD. This tutorial could be easily expanded to cover a lot of other areas including integrating the serial key. Manually I personally beleive can give you much more control if you know what you are doing.

Plus no one mention that they do have problems using Nlite, it has it own forum for the problems.

I prefer the manual way of doing, a UA install.

Still very useful.

Was just talking to someone other day who was about to reinstall and was complaining about installing SP2 after he installed Windows, I said just slipstream an install cd, what is that, I searched for this thread for him, hes very happy.

Thanks guys for all your support and nice feedback.

Just a heads up also - Any new posts from me will be under the username Nexoni from now on. Figured I better write that under this username as some may not beleive 'nexoni' he/I am the original thread starter unless I mention it here first. Figured some may flame 'nexoni' that he/I am taking credit for this guide. :)

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Are you going to do performance benchmarks comparing all states? I'd be interested in seeing that in the next "part".
    • My father still uses a programme written in dbase3. Still manages to work with a little help from dosbox. 
    • Microsoft hides these secret Windows 11 performance boost settings available on every PC by Sayan Sen Windows enthusiasts often look for ways to extract as much performance out of their systems as possible, and it's often the case that they try and do so while trying to minimize the heat and power consumption. This is especially relevant in the case of mobile Windows PCs since laptops and notebooks tend to get hot and management of that heat and power is harder in such a form factor. As such users often turn to techniques like under-volting which can be used to squeeze out the maximum capabilities of a chip while also maintaining lowered power levels. There are official apps from AMD and Intel with the likes of Ryzen Master and XTU (Extreme Tuning Utility). While these are quite handy, most enthusiasts probably prefer to dig into the BIOS and play around with settings there like Curve Optimizer on Ryzen, which lets users set various frequency-voltage scaling values. These are essentially called P-States. If you are not familiar with them, Processor Power Management is done through Advanced Configuration and Power Interface (ACPI) P-states and C-states. While P-states or performance pwoer states handle CPU voltage-frequency scaling, C-states deal with CPU sleep states so that some of the CPU functions, which are not necessary at that moment, can be disabled. The P-states and C-states work together to make the processor run more efficiently. It helps the OS and apps determine which cores can be parked and which should be boosted. Of course not every user is an enthusiast or knows the technicalities and integrities of how things like overclocking or undervolting work. Thankfully for them Windows itself offers something pretty cool, though it is hidden by default on all systems. By default, Windows only has two P-States, "Minimum Processor State" and "Maximum Processor State." However, this can be changed with a Registry trick to expand the options under a secret "Processor performance boost mode" dropdown. This essentially enables the HWP or hardware P-States available on a device, and these are not controlled just by the OS itself as the underlying hardware gets involved too. In total there are five Processor Performance Boost Mode profiles that control how Windows requests and allows CPU turbo/boost behavior under the different power policies. They are: Disabled: In this mode, processor boosting is effectively turned off. The CPU will avoid entering turbo or boost frequencies and instead operate closer to its base frequency ceiling. This can significantly reduce power consumption and heat output, but at the cost of reduced burst performance and responsiveness in short workloads. Enabled: This is the standard behavior where boost functionality is allowed under normal conditions. The processor can opportunistically increase frequency when workload demands it, balancing performance gains with power and thermal constraints as managed by the system. Aggressive: Aggressive mode favors performance more heavily, allowing the CPU to enter higher boost states more readily and sustain them longer. This should in theory improve responsiveness under bursty or heavy workloads but increases power draw and thermal output compared to the default enabled behavior. Efficient Enabled: This mode still allows boosting, but with a stronger bias toward energy efficiency. The system attempts to use boost more selectively, avoiding unnecessary frequency spikes when the performance gain is marginal. Efficient Aggressive: This is a hybrid approach where boost is still performance-responsive, but the system continuously weighs efficiency more heavily than in Aggressive mode. It aims to deliver noticeable performance improvements while reducing wasted power in less demanding scenarios. Here's how to enable the Processor performance boost mode: Open Registry Editor: Press Win+R, type regedit, and click OK. Go to: HKLM\SYSTEM\CurrentControlSet\Control\Power\PowerSettings\54533251-82be-4824-96c1-47b60b740d00\be337238-0d82-4146-a960-4f3749d470c7 (where HKLM stands for HKEY_LOCAL_MACHINE_) Modify the value of Attributes from 1 to 2 (you can find modify option by right-clicking) After that, exit Registry, you should now be able to see the new "Processor performance boost mode" dropdown menu: As you can see there are now five new P-States or CPPC states or power profile available that help define the boost mode processor setting on your PC. Wrapping it up here's a quick run-down of the settings as defined by Microsoft itself. Setting Description Disabled The corresponding P-state-based behaviour is disabled. Collaborative Processor Performance Control (CPPC) behaviour is disabled. Enabled The corresponding P-state-based behaviour is enabled. CPPC behaviour is Efficient Enabled. Aggressive The corresponding P-state-based behaviour is enabled. CPPC behaviour is Aggressive. Efficient Enabled The corresponding P-state-based behaviour is Efficient. CPPC behaviour is Efficient Enabled. Efficient Aggressive The corresponding P-state-based behaviour is Efficient. CPPC behaviour is Aggressive. Aggressive At Guaranteed Windows calculates the desired extra performance above the guaranteed performance level, and asks the processor to deliver that specific performance level. Efficient Aggressive At Guaranteed Windows always asks the processor to deliver the highest possible performance above the guaranteed performance level. In the next part we shall be comparing these settings to explore how much of a benefit or regression they can provide in terms of performance and power efficiency. If you decide to change the values on your system and are experiencing problems like crashes or an overheating PC, make sure to revert the steps back to the original state.
  • Recent Achievements

    • Week One Done
      rolfus earned a badge
      Week One Done
    • One Month Later
      Leroy Jethro Gibbs earned a badge
      One Month Later
    • Conversation Starter
      flexorcist earned a badge
      Conversation Starter
    • One Month Later
      AndreaB earned a badge
      One Month Later
    • One Month Later
      agatameier earned a badge
      One Month Later
  • Popular Contributors

    1. 1
      +primortal
      518
    2. 2
      +Edouard
      198
    3. 3
      PsYcHoKiLLa
      147
    4. 4
      ATLien_0
      93
    5. 5
      Steven P.
      78
  • Tell a friend

    Love Neowin? Tell a friend!