Slipstreaming and Bootable Disc

Slipstreaming and Bootable Disc FAQ's

by "Tachtech"

What is slipstreaming?

Newer version of Microsoft Windows Operating Systems (2000,XP,2003) have the ability to integrate Service Packs and HotFixes into the initial installation of the operating system. You can use this method to replace the original source files with updated Pack files before installing Windows. When the operating system is installed, the Service Pack and Hotfixes are installed automatically.

Newer Corporate versions of Microsoft Office Products also support slipstreaming.

Why use the Load Segment of 0000 instead of 07C0 ?

As of 11.27.2003 we recommended using:
Load segment of sectors (hex!): 0000

It was determined that most original discs from Microsoft have been using 0000. Early Windows 2000 CD's used 07C0. Many Dell Discs created using Nero Burning ROM had the Load Segment set to 07C0. We have not encountered any problems with the Discs created with it set to 0000.

Does SP1 have to be applied prior to applying SP2

No. SP2 can be applied without applying SP1 or SP1a.

Error: This Service Pack Cannot be intergrated into a destination that also has intergrated Software Updates.

While applying a Service Pack the following error message is displayed.

Error: This Service Pack Cannot be intergrated into a destination that also has intergrated Software Updates. Consult the Service Pack documentation for more details about supported intergration scenerarios.

This is a common error message that occurs when using a disc from a large manufacturer such as Dell or HP.

You will need to remove some files and folders from the compelation prior to applying a service pack.

Remove the following file:

I386\SVCPACK.INF

Removing the following folders will avoid older patches from being applied:

$OEM$
I386\SVCPACK

You may need to remove or edit the following file:

I386\WINNT.SIF

Product Key doesn't work.

If your product key starts with FCKGW you have the "Devil's Own" release of Windows XP. This key is blacklisted.

SP1 will disable Windows Update and certain features of XP running the Product ID codes:

XXXXX-640-0000356-23XXX
XXXXX-640-2001765-23XXX

- View Volume License Product Keys: Changes with Windows XP Service Pack 1 (Microsoft Link)
- View Unable to install Windows XP SP2 (Microsoft Link)
- View Microsoft Knowledge Base Article - 302878
- View Product Key Validation: Frequently Asked Questions (Microsoft Link)
- View What is Licensing (Microsoft Link)

Can Dell Windows XP CD's be used to load other brand PC's?

Some Large OEM's such as Dell create their Discs to check the BIOS. If the BIOS type does not match the required System, a message will be displayed stating that the System Type is incorrect.

Slipstreaming a disc will not remove this message. Some files on these Discs are different from standard OEM Discs from Microsoft. Slipstreaming these Discs will update the files but will not remove the BIOS check.

Why the newer creating bootable disc articles using 'Easy CD Creator 5' and 'Easy CD and DVD Creator 6' use Joliet.

Nero supports dual File Table support, allowing Long File Names and characters like dollar signs. Roxio products do not. We now recommend using Joliet when writing disc when using Roxio products due to the inability to create unattended discs with the ISO9660.

NTLDR Error with Boot discs created with some versions of Nero.

- View Article TTID#: 177

The Disc is not booting?

Verify the original disc boots.
Verify the CD-ROM is set as the first boot device in the BIOS/CMOS/System Setup.
Verify the loaded sectors was set to 4.
When booting from a SCSI or Serial ATA controller, additional drivers may need to be added to the disc.
Nero may not have retained the Boot information. Verify the setting on the Boot tab prior to writing the disc.
Try using ISO Level 2.

If the disc still doesn't boot, include any error messages and your hardware configuration when contacting us.

Nero problems recording Discs with ISA SCSI Controllers.

- View Article TTID#: 238

When executing C:\OS\SP.EXE /U /X:C:\OS\SP it fails.

-or-

An error message is displayed when executing:
C:\OS\SP\UPDATE\UPDATE.EXE /S:C:\OS\ROOT
C:\OS\SP\I386\UPDATE\UPDATE.EXE /S:C:\OS\ROOT

To better debug the problem, launch the Service Pack in Manual-Extraction-Mode using the following command from the Run Dialog:
C:\OS\SP.EXE /X

When the Service Pack is extracting the Service Pack folder(directory) disappears and no prompt of completion is displayed.

The Service Pack file may be corrupt or incomplete. Remove the /U from the extraction command. If the following error is displayed download the Service Pack, again.

The following error message is displayed when the Service Pack is being applied.

Service Packs can only be applied from Windows 2000, XP, or higher. They cannot be applied from older versions of Windows such as Windows 98.

When trying to run the Service Pack an error message reporting the file cannot be found appears.

Verify the Service Pack is in the correct location. Check the spelling of the file name.

If the original file did not have an extension then you most likely have Hide file extensions for known file types enabled.

See article TTID#193 for Windows XP and article TTID#191 for Windows 2000 for additional information.

Service Pack reports that it is not a valid Win32 Application.

Verify the original file had the extension EXE before you renamed it. If it had a different extension such as ZIP or RAR you will need to extract the Service Pack from this archive first. Then rename the extracted file.

If the original file did not have an extension then you most likely have Hide file extensions for known file types enabled.

See article TTID#193 for Windows XP and article TTID#191 for Windows 2000 for additional information.

An error is reported during the extraction or file verification process.

The Service Pack is probably corrupt. Try downloading the Service Pack again.

Extraction of Service Pack is not working.

Try a manual extraction.
Click Start > Run...

Type in the path and file name to the Service Pack.
(example: C:\OS\SP.EXE)

Click the OK button.

In the Choose Directory For Extracted Files text box type where you would like to extract the Service Pack to.
(example: C:\OS\SP)

Click the Ok button.

Wait while the files are extracted.

Click the OK button.

UPDATE.EXE can not be found when you attempt to apply the Service Pack.

Verify that UPDATE.EXE is at the location specified in the Run command.

An error has occurred copying files from the Service Pack share to the distribution share.

The hard drive may be full. Check to see how much free space the drive has.

When running the UPDATE.EXE command the following error is displayed: Failed to copy some or all to the files necessary for integrated install.

- Verify the target folder(directory) contains a sub-folder(sub-directory) named i386.

- Check to see how much hard drive space you have available.

How big should the Service Pack files be that I download from Microsoft?

	Language	File Name	Size
SP1	English	xpsp1_en_x86.exe	133 MB (140,440,152 bytes)
SP1a	English	xpsp1a_en_x86.exe	125 MB (131,170,400 bytes)
SP2	English	WindowsXP-KB835935-SP2-ENU.exe	266 MB (278,927,592 bytes)
SP1 64-Bit	English	xpsp1_en_ia64.exe	199 MB (209,265,752 bytes)

When running the UPDATE.EXE command the following error is displayed: The Procedure entry point _wcstoui64 could not be located in the dynamic link library msvcrt.dll.

Occurs when running SP2 RC1 for Windows XP on a computer running Windows 2000 Server SP4 (msvcrt.dll 6.1.9844.0). We are still researching problem. Other people have experienced problems while trying to slipstream/intergrate SP2 for Windows XP using a computer running Windows 2000 Professional.

After slipstreaming, the disc media is not large enough.

Some of the folder can be removed from the disc compellation.

The following folders are only required for upgrades:

I386\WIN9XMIG (32.7MB)
I386\WIN9XUPG (3.89MB)
I386\WINNTUPG (1.03MB)

The following folder is only required if you are using a language other than the default:

I386\LANG (99MB)

The following folder is only required if the information found in VALUEADD\VALUEADD.HTM pertains to the installation:

VALUEADD (9.87MB)