contiunas reboot after applying wim xp image

[amoss24]

I have made an image of a xp machine using win_pe and imageX, all works ok applying the image on the orignal test machine that i created the image on, but on other machines i apply the image and i get a constant reboot at the xp loading screen, no error messages are give just loops over and over.

Please help any idea, im thinking its a hal / mass storge driver issue, but i thought that using imagex wim files got around the driver issues of imaging.

Edited September 28, 2009 by amoss24

[Tripredacus]

When the client is booting up, use F8 to get to the boot menu. Select the "Disable automatic restart on system failure" and see what error you are getting.

[amoss24]

i do not get ths menu option with F8???

all i get is

safe mode

safe mode command promt

safe mode with network

boot with last known good config

boot windows xp normal

Any safe mode hangs at Mup.sys

others just give the usual reboot prob

I have managed to get the xp image working provided i use windows xp sp1a as my image, if i use service pack 2 i get blue screen then reboots but the reboot is to fast to see the error message, service pack 3 just continues reboot no blue screen if there is one its blood fast.

using the images on the orignal machine all if fine its only when i test on different machines i get into problems

the way i do image is

1) install pc with windows xp

2) apply service pack/s and updates etc

3) sysprep the pc

4) boot using winpe

5) imagex the c: to network share

apply image

1) boot pc using winpe

2) use diskpart to ready harddisk

3) apply image to c:

4) boot windows xp <<< at the initial xp logo loading screen this is where it reboots

its ok on the original machine i image on, but not on other machines.

Edited November 3, 2009 by amoss24

[amoss24]

think i sorted it out i have to delete

c:\windows\system32\drivers\intelppm.sys

after the image has finished.

[cluberti]

Are you perchance creating images on Intel CPU hardware and then trying to apply it to non-Intel CPU machines? If so, this is a no-no and would behave as you describe.