XP Home installation hangs @ 39 minutes

[Canary M. Burns]

Hey guys ive made a few unattended discs before. They mostly had sp2 integrated and some custom runonce to install additional software. They all worked great, but now i want to create a disc with the latest updates, ie7 etc... So ive taken a xphome disc and did all the stuff i did b4 for my other discs and I downloaded RVMUpdatepack 2.1.11 and the ie7addon from RyanVM. Ive read that u can use Nlite to integrate these. So anyways i integrated the update pack and ie7 and install hangs after the first reboot when it gets into gui mode @ 39 mins. So I tried just the rvmupdate by itself and then ie7 by itself and they still hang, but it doesnt hang if i leave out those updates and go with just sp2. Any ideas?

If you need additional info please let me know. Sorry im new to the forums so i dont know what info u all need.

Edited July 24, 2007 by Canary M. Burns

[Kelsenellenelvian]

xphome disc and did all the stuff i did b4 for my other discs and I downloaded RVMUpdatepack 2.1.11

Are you adding in other fixes? Because there is a limitation that XP reaches at @ 150 cat files in the svcpack folder. Once there is too many hotfixes and cat files the installation will hang sometimes for an hour or more...

[Canary M. Burns]

Nope the only thing that ive done to it is integrate SP2 and then the update pack and ie7 addon.

thanks for the response

*edit*

I tried copying a diff xp home source i had and starting from scratch and still didnt help, anyone have any thoughts for me

Edited July 25, 2007 by Canary M. Burns

[Canary M. Burns]

Anyone have any ideas for me? Or any ideas what I could be doing wrong? Have people succesfully slipstreamed IE7, WMP11, and RyanVM update pack into a installation disk before?

Little Help

[gosh]

The 39 min mark is at the start of setup, setup does the following in order:

1 - registers catalogs so it can check digital signature of files

2 - Installs core hardware such as cpu, hard disk, drivers

3 - starts step 1 of 3

So what you're looking at is either 1) corrupt core files, 2) digital signing broken, 3) hardware issues

Upload your setuplog.txt (which shows what setup did), and setupapi.log (which logs hardware detection), and setuperr.log (if you have it). I'll look at the files if you want and tell you what is wrong.

-gosh