SP3 Slipstream Causes Install to Fail

[Ben]

Hi,

I've just tried to slipstream SP3 into a clean Win XP source CD,
however, no matter which method I use, I get an error when running the
DOS part of the install. The error is:

"The file ohci1394.sys could not be found. Press any key to continue."

The method's used so far are: Copy original Windows XP SP1 from retail
CD, into a folder called c:\temp\WinXP. Then download SP3, and either:
1) extract SP3 using /c:temp\sp3 command line, then run update/
update.exe -s:c:\temp\winxp
or
2) upgrade directly from the SP3.exe using /integrate:c:\temp\winxp

Both methods report that the upgrade was successful. I then write the
new CD using CDBurnerXP, creating a bootable CD.

The CD boots, and setup starts to load, some drivers are loaded, and
it gets past the press F6 to load 3rd party drivers, and press F2 to
run ASR. But then it fails loading ohci1394.sys.

Anyone know why this is happening, or how to get around it?

Thanks

Ben

 

[JS]

ohci1394.sys is most likely your firewire driver.

Better way to Slipstream (assuming your using
either a SATA or PATA hard drive to install XP
is as follows. You can install the firewire driver later
if needed.

Create a "Slipstreamed" version of XP that incorporates SP3
AutoStreamer, it's easy to use and for the most part self explanatory.
After you create the CD then do a "Clean Install", see the last part
of my reply.

Auto Streamer Guide and Download Sites:
http://www.simplyguides.net/guides/using_autostreamer/using_autostreamer.shtml
http://fileforum.betanews.com/detail/1092632287/1

Where to download SP3
(This file will be used in created the slipstreamed CD)
http://www.microsoft.com/downloads/...a8-5e76-401f-be08-1e1555d4f3d4&DisplayLang=en

Create a Slip Stream version of Windows XP using SP3
http://www.webtree.ca/windowsxp/slipstream.htm (Using AutoStreamer)
http://www.theeldergeek.com/slipstreamed_xpsp3_cd_final.htm
http://www.winsupersite.com/showcase/xpsp3_slipstream.asp

The slipstreamed CD you create will not include any specific drivers
for your motherboard, audio, video, network, etc. Those you will
need to download from your PC manufacture's or motherboard's
web site.

How to do a Clean Install of Windows XP
Start by changing the BIOS setting to Boot from CD drive first.
Then see below:

From Michael Steven's: http://www.michaelstevenstech.com/cleanxpinstall.html
more info: http://windowsxp.mvps.org/XPClean.htm
and: http://www.theeldergeek.com/clean_installation_of_windows_xp.htm
also: http://www.bootdisk.com/

How to optimize your chances of installing Windows XP SP3 successfully:
http://www.pagestart.com/windowsxpsp3p3pg8.html

 

[Ben]

I thought it should work too, but just to test I've just used Auto
Streamer to go from SP1 > SP2 > SP3, and still received the same error
"The file ohci1394.sys could not be found."

The original Win XP SP1 cd runs through the setup without any errors,
so something during the slipstream process causes ohci1394.sys to go
missing, or get corrupted. The file still seems to exist, under i386
there is a file called ohci1394.sy_ & in driver.cab & sp1.cab there is
a ohci1394.sys in each.

Just testing a SP2 boot disk to see if the error is in the SP3
slipstream process. I'll use nLite rather than Autostreamer next.

Ben

 

[frustratedxpsp3installer]

I am having the same problem. I am using nLite.

I thought it should work too, but just to test I've just used Auto
Streamer to go from SP1 > SP2 > SP3, and still received the same error
"The file ohci1394.sys could not be found."

The original Win XP SP1 cd runs through the setup without any errors,
so something during the slipstream process causes ohci1394.sys to go
missing, or get corrupted. The file still seems to exist, under i386
there is a file called ohci1394.sy_ & in driver.cab & sp1.cab there is
a ohci1394.sys in each.

Just testing a SP2 boot disk to see if the error is in the SP3
slipstream process. I'll use nLite rather than Autostreamer next.

Ben

 

[Twayne]

"frustratedxpsp3installer"

I am having the same problem. I am using nLite.

Why bother to slipstream SP2 and/or 3? All it does is prevent having to
insert the SP2 and/or the SP3 disk and remove same if/when they're asked
for. That's a hell of a lot faster than fiddling with unreliable, hard
to test/prove out slipstreams. Most of the time they aren't known to
fail until the time comes that they're needed. IMO It's a waste of time
for what it accomplishes even when it does work right.


HTH,

Twayne`

 

[Shenan Stanley]

<snip>

Why bother to slipstream SP2 and/or 3? All it does is prevent
having to insert the SP2 and/or the SP3 disk and remove same
if/when they're asked for. That's a hell of a lot faster than
fiddling with unreliable, hard to test/prove out slipstreams. Most
of the time they aren't known to fail until the time comes that
they're needed. IMO It's a waste of time for what it accomplishes
even when it does work right.

I assure you, it is not a waste of time if you do many installs. The amount
of time it saves is quite large. I slipstream SP3 and as many of the
post-SP3 updates as I can into the media I install with (network and CD) and
in the end the time it saves greatly outweighs the hour or so it takes when
I do it from scratch (20 minutes or so if I start from where I left off the
last time I did it.)

At this point my Windows XP installation CD only has 11 or so
critical/security updates after the CD installation of Windows XP is done.
If I wanted, I could automate those (and do on the network installations)
but they are relatively small and I will probably see how many of those can
be integrated as well.

For the normal home user who might install a syste 0-1 in their lifetime,
slipstreaming is probably not the thing to do. For anyone who does tech
support and might install 1+ times a day/week/month - probably worth a
little effort to save them time. Time is money. ;-)

 

[frustratedSP3installer]

I fixed the problem by starting the slipstream process from scratch, i. e,
erasing ALL files from the previous slipstream integration directory on the
hard drive, then copying the files from the original XP installation CD, and
then using nLite to integrate SP3, drivers and hotfixes. That included NOT
loading an nLite session file.

 

[Twayne]

<snip>


I assure you, it is not a waste of time if you do many installs. The
amount of time it saves is quite large. I slipstream SP3 and as many
of the post-SP3 updates as I can into the media I install with
(network and CD) and in the end the time it saves greatly outweighs
the hour or so it takes when I do it from scratch (20 minutes or so
if I start from where I left off the last time I did it.)

I'm curious; having seen you around enough to know you're no dummy about
computers, why do you prefer slitpstreaming over simply imaging the
drives?
Images allow you to go right back to the time of the last backup
(which for me is last night or anything was installed/uninstalled, or
data on the drive changes by more than 750k. In the case of a
catastrophic failure, I can toss the boot CD into the drive and the boot
drive be back up and running in 19 minutes (last time I stop-watch
clocked it). My laptop (used as a sandbox) can regenerate the boot
drive in about 12 minutes, or 5, depending on which image I want to use.
I particularly like having historical backups stashed away too. In case
it occurs to you, my C drive is OS only; none of my own data storage is
on C; for backup purposes.

I think slipstreams may have their place occasionally but I'm trying to
imagine why/where they may be better for boot drive installation over
other methods.

At this point my Windows XP installation CD only has 11 or so
critical/security updates after the CD installation of Windows XP is
done. If I wanted, I could automate those (and do on the network
installations) but they are relatively small and I will probably see
how many of those can be integrated as well.

For the normal home user who might install a syste 0-1 in their
lifetime, slipstreaming is probably not the thing to do. For anyone
who does tech support and might install 1+ times a day/week/month -
probably worth a little effort to save them time. Time is money. ;-)

No arguement about time is money, for sure! I think that's what makes
me so curious to see what you think of my comments on imaging et al,
neglecting the regular data backups etc. that also need to be done; I'm
happy just discussing the boot drive here.

Regards,

Twayne`




I understand where you're coming from, but only SPx was mentioned, not
updates. Which means one must periodically keep collecting updates and
adding them. I think most newbies will spend a lot more time on
creating slipstreams than you do, they'll not do the updates or if they
do they may not be complete, and I always feel sorry for the poor slobs
who come in because their slipstream didn't work when they needed it.
Normally I'd rather try to talk to them about doing imaging as
opposed to slipstreams for the advantages I'm sure you aware of, mainly
that it's always up to date and if you've kept a historical record you
can do a lot of things a lot easier and quicker.

Regards,

Twayne`