Slipstreamed/Sysprep'ed SP2 install fails



Matt Pooley
07-10-2005, 03:20 AM
Hi,

I wonder if someone here can help me.

I'm trying to build a Sysprep image of XP with SP2.

However, what I've found is that the first boot of XP SP2 will always
fail on my hardware (a custom built low-profile unit). This happens
regardless of whether it's the initial slipstreamed SP2 install or the
first boot after Sysprep.

Note that SP1 works with no issues.

The lock-up always happens at the same place, after checking my video
resolution, I see the XP logo and 'Please wait...' followed by no
activity (16 hours and counting)

When I'm installing SP2 from CD, I can reboot once and the system
recovers, when I'm booting a Sysprep'ed image, the image is dead, and I
have to wipe the disk before I can do anything else (repair installs
don't help)

At this point I've accepted that SP2 has some issues with my hardware,
I just need some help working out which piece of hardware it doesn't
like. Is there any way to get a log of the driver/module which is
causing the lockup so I can dig further ? (Or alternatively, has anyone
else reached the same point in the past and found a magic wand.)

Thanks for your help,

Matt.


--
Matt PooleyPosted from http://www.pcreview.co.uk/ newsgroup access

Netanel Ben-Shushan
07-10-2005, 03:20 AM
Hi,

First - Please understand me because my English is not the best...

Second - Now let's talk about your problem @ Sysprep imaging:

Try to install windows XP again (on FAT/FAT32 formatted partition) and to
install all your necessary applications and updates.
After you’ve installed your applications and updates, insert the WinXP CD
into your drive and go to D:\Support\Tools (when D:\ is your CD Drive letter).
Now extract the Deploy.cab file into your C: partition at new folder (for
example folder named deploy).
Now find the Setupmgr.exe file and create a new Sysprep setup answer file,
you find a new folder in drive C: named Sysprep, and there you find your
answer file that you've been created.
Now edit the answer file and add this section in the answer file's end:
[Sysprep]
BuildMassStorageSection=Yes
[SysprepMassStorage]
Now save it as Sysprep.inf there.

If you want to get more details why you need to add this section watch this
KB article: http://support.microsoft.com/?kbid=303786
Now go to c:\deploy and copy these files to c:\sysprep:
Sysprep.exe
Setupcl.exe

Now run Sysprep from c:\sysprep and check the "Use Mini-Setup" and "Detect
non-plug and play hardware" and click on the Reseal button.
This action takes between 20minutes to 45 minutes.

When the Sysprep tool done the reseal process and the PC turn off create
with 3rd disk imaging software the image (I recommended you to use Norton
Ghost).

Good Luck!
And Best Regards,
Netanel Ben-Shushan
Visit my website (Hebrew website): http://www.netanel.pctip.co.il
Feel free to send me mails to netanel@pctip.co.il

"Matt Pooley" wrote:

>
> Hi,
>
> I wonder if someone here can help me.
>
> I'm trying to build a Sysprep image of XP with SP2.
>
> However, what I've found is that the first boot of XP SP2 will always
> fail on my hardware (a custom built low-profile unit). This happens
> regardless of whether it's the initial slipstreamed SP2 install or the
> first boot after Sysprep.
>
> Note that SP1 works with no issues.
>
> The lock-up always happens at the same place, after checking my video
> resolution, I see the XP logo and 'Please wait...' followed by no
> activity (16 hours and counting)
>
> When I'm installing SP2 from CD, I can reboot once and the system
> recovers, when I'm booting a Sysprep'ed image, the image is dead, and I
> have to wipe the disk before I can do anything else (repair installs
> don't help)
>
> At this point I've accepted that SP2 has some issues with my hardware,
> I just need some help working out which piece of hardware it doesn't
> like. Is there any way to get a log of the driver/module which is
> causing the lockup so I can dig further ? (Or alternatively, has anyone
> else reached the same point in the past and found a magic wand.)
>
> Thanks for your help,
>
> Matt.
>
>
> --
> Matt PooleyPosted from http://www.pcreview.co.uk/ newsgroup access
>
>

Matt Pooley
07-10-2005, 03:20 AM
Hi,

Thank you for the suggestion, I am creating a new image to try this out
on right now..

Matt.


--
Matt PooleyPosted from http://www.pcreview.co.uk/ newsgroup access

Netanel Ben-Shushan
07-10-2005, 03:20 AM
Fine, Good Luck Sir.

Best Regards,
Netanel Ben-Shushan


"Matt Pooley" wrote:

>
> Hi,
>
> Thank you for the suggestion, I am creating a new image to try this out
> on right now..
>
> Matt.
>
>
> --
> Matt PooleyPosted from http://www.pcreview.co.uk/ newsgroup access
>
>

brianb
07-10-2005, 03:20 AM
If you want to locate any errors after a failed install, you can usually find
them in C:\WINDOWS\setuperr.log (assuming c:\windows is your root system
folder)
You may have to install drive as a slave into another system to view the log
file.

"Matt Pooley" wrote:

>
> Hi,
>
> I wonder if someone here can help me.
>
> I'm trying to build a Sysprep image of XP with SP2.
>
> However, what I've found is that the first boot of XP SP2 will always
> fail on my hardware (a custom built low-profile unit). This happens
> regardless of whether it's the initial slipstreamed SP2 install or the
> first boot after Sysprep.
>
> Note that SP1 works with no issues.
>
> The lock-up always happens at the same place, after checking my video
> resolution, I see the XP logo and 'Please wait...' followed by no
> activity (16 hours and counting)
>
> When I'm installing SP2 from CD, I can reboot once and the system
> recovers, when I'm booting a Sysprep'ed image, the image is dead, and I
> have to wipe the disk before I can do anything else (repair installs
> don't help)
>
> At this point I've accepted that SP2 has some issues with my hardware,
> I just need some help working out which piece of hardware it doesn't
> like. Is there any way to get a log of the driver/module which is
> causing the lockup so I can dig further ? (Or alternatively, has anyone
> else reached the same point in the past and found a magic wand.)
>
> Thanks for your help,
>
> Matt.
>
>
> --
> Matt PooleyPosted from http://www.pcreview.co.uk/ newsgroup access
>
>


Slipstreamed/Sysprep'ed SP2 install fails