Problem when slipstreaming SP to Windows XP

I'd appreciate anyone's assistance in this matter as I've encountered a situation that's been quite vexing for me...

My situation involves attempting to apply either Service Pack SP1a or SP2 to Windows XP. While I'm able to successfully extract the contents of either SP to a local directory, I generate the following error when attempting to apply the SP to my Windows XP source files:

"Failed to copy some or all to the files necessary for integrated install.

"Please check that: a) No network or copy errors occurred during the integration process; b) The format of the destination directory is correct.

"The files to be integrated must reside in an i386 and/or ia64 or nec98 directory (i.e. for an i386 share, if you typed 'update /s:c:\cdshare', the files must be in the c:\cdshare\i386 directory). "

A few things of potential interest:

1) I have successfully applied SP4 to my Windows 2000 source files without encountering this issue.

2) I'm currently using Windows 2000 while attempting to apply the SP to the Windows XP source files. (Would this make a difference? Many of the tutorials that I've read seem to be using Windows XP to apply the SP to the source files.)

3) The aforementioned directory, I386, does exist at the same level of the directory structure hierarchy as the Windows XP installation file (setup.exe). According to all of the tutorials that I've read, the I386 directory is located in the appropriate place.

I'm really stumped and I've found a few other bulleting boards on which others have posted this same issue. I'd appreciate some help so that I can hopefully help these other people, too.

Matt

 

You update XP with XP updates. You update W2k with W2k updates.

 

I misread your original post. Go to the another thread. It explains the process a bit more simply.

http://www.windowsbbs.com/showthread.php?t=33946

 

Are you sure your typing the correct path in the integrate command? If you're copying and pasting the command in and you have the files located on a different drive than they used in the guide, make sure you change the drive letters in the command accordingly.

 

Zander:

I am absolutely, positively certain that I'm entering the correct command. I understand that much of what people post online may be generic but, as I'm not a novice with computers, I understand what the command means in "plain speak." The path which I enter to specify the location of the update.exe file is correct; the path to the I386 directory is also correct. The only two things of which I can think that could be causing problems are:

1) My downloaded files (specifically, the SP's update.exe file) is somehow corrupted or...

2) A computer running Windows 2000 has difficulty slipstreaming Windows XP SP's to Windows XP source files.

The latter doesn't make any sense to me as the SP should be a self-contained package. So long as one applies the SP to the appropriate O/S, then I don't see why a problem would occur.

I've downloaded and redownloaded the SP's until I'm blue in the face. I'm using a high-speed connection at work, so I doubt that I'm having bandwidth problems that could be affecting my SP files.

Again, I'm stumped... =(

 

Did you try the FOLDER 1, FOLDER 2, FOLDER 3 method of the other thread?

 

You bet'cha

RayH:

I did attempt the "Folder 1, Folder 2, Folder 3" method. The files appear to extract without a hitch. However, I generate the following error:

"The procedure entry point CreateActCtxW could not be located in the dynamic link library KERNEL32.dll. "

The title of the error message's window is "update.exe - Entry Point Not Found." I assume that, when attempting to run the update.exe file in order to apply the SP to the O/S, I'm encountering problems again.

Matt

 

Are you guys trying to use manufactured computer OEM disks or a RETAIL Windows disk?

 

Oem

My Windows XP is a manufactured computer OEM.

Matt