Jump to content

Integrating SP's For Dummies


Recommended Posts

Posted (edited)

THIS GUIDE IS FOR PEOPLE WHO DON'T WANT TO USE NLITE AND/OR CAN'T WAIT TILL THE NEXT RELEASE OF NLITE (bugfix) comes out....ENJOY!

INTEGRATING A SERVICE PACK TO A WINXP CD

Create a directory on the hard drive and copy the entire contents of your WinXP CD to the directory as follows:

C:\XPCD

Download the Service Pack, rename it to XP-SP* and place it in the C:\. Using the RUN COMMAND, run the executable with a -x at the end as follows:

*represents the servicepack version like XP-SP1, or XP-SP2, or XP-SP3

RUN COMMAND: C:\XP-SP -x

After it's verified the integrity of the file, you will be prompted for a location to extract, just type in the following:

C:\SPCD

Click on OK when the extraction's complete, and then type the following using the RUN COMMAND:

C:\SPCD\i386\UPDATE\UPDATE.EXE -integrate:C:\XPCD < FOR SERVICE PACKS 2 and 3

for Service Pack 1, type the following using the RUN COMMAND:

C:\SPCD\UPDATE\UPDATE.EXE -s:C:\XPCD

When integration's finished, you'll see the message -The Integrated install has completed successfully -.

CONGRATULATIONS! YOUR DONE!

MAKING THE WINXP SP INTEGRATED ISO BOOTABLE USING NERO BURNING ROM

Put this boot image into a folder called: C:\XPBOOT

Start Nero Burning Rom.

Select File > New... from the menu.

1.) Select CD-ROM (Boot)

2.) Select Enable Expert Settings (for advanced users only!)

3.) Select Image file from Source of boot image data and browse to the folder

C:\XPBOOT. Change Files of Type to All Files (*.*) and locate XPBOOT.BIN

4.) Set Kind of emulation to: No Emulation

5.) Set Load segment of sectors (hex!): to 07C0 (If needed)

6.) Set Number of loaded sectors to: 4

7.) Press the Browse... button

Click ISO tab

Set File-/Directory length to ISO Level 1 (Max. of 11 = 8 + 3 chars)

Set Format to Mode 1

Set Character Set to ISO 9660

Check all Relax ISO Restrictions

Click Label Tab

Select ISO9660 from the drop down box.

Enter the Volume Label as WXPOEM_EN

Enter the System Identifier as WXPOEM_EN

Enter the Volume Set as WXPOEM_EN

Enter the Publisher as MICROSOFT CORPORATION

Enter the Data Preparer as MICROSOFT CORPORATION

Enter the Application as WXPOEM_EN

* For Windows XP Home OEM, substitute WXPOEM_EN with WXHOEM_EN

* WXPOEM_EN is the label for Windows XP Professional OEM release

Click Burn tab

Check Write

Check Finalize CD (No further writing possible!)

Set Write Method to Disk-At-Once

Press New button

Locate the folder C:\XPCD

Select everything in the folder and drag it to the ISO compilation panel.

Click the Write CD Dialog button.

Press Write and you're done!

BOOT_IMG.zip

Edited by XL-DJK

Posted

i tried this method and it doesn't allow me to slipstream because I am using winxpsp1 and it says that it cannot work with already integrated software.

Posted
i tried this method and it doesn't allow me to slipstream because I am using winxpsp1 and it says that it cannot work with already integrated software.

It worked for me with no problems :)

Posted

It could be because you've done other modifying of the source. Such as adding hotfixes or something.

Also, why do people feel the need to post a method and a "guide" for a method that has worked since Win2k SP1? By all means, keep sharing, but the process just doesn't change. I mean, if you want it even easier, open up nLite, tell it the XP source, tell it the service pack file you download, and it does it all for you. THen you make the ISO, and burn it.

Posted

Could someone post that deploy.cab from longhorn? Please? XL-DJK95355?

Please don't make me download 600MB for a 5KB file :)

Posted

Yes, I agree Alanoll, but that's not how it's been in the past. The deployment manager in 2003 server was way better than the one on XP. The documentation for unattend.txt files was way better too.

Posted
i tried this method and it doesn't allow me to slipstream because I am using winxpsp1 and it says that it cannot work with already integrated software.

okay, just delete SVCPACK.INI, then it´s not going to bug you any more :rolleyes:

Good luck :)

Posted

so I was right then...

It could be because you've done other modifying of the source. Such as adding hotfixes or something.

I jsut expected you to know what you did.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...