Dropped clone to new pc buts gets stuck rebooting

[Guest]

We got in some brand new computers and are dropping our ghost image clone to
these computers. (We've used these clones hundreds of times.) However, on
the new computers, after the clone drops and we reboot the pc, the computer
gets stuck in a "rebooting loop" and never comes up. It reboots before you
see any Windows XP startup info like the logo screen, etc. There is also no
blue screen message either. It simply reboots during the 'black' screen when
starting up.

We're guessing something is different in hardware on the new pc and are
hopeful there is something we can do to our ghost image clone to "update" it
so it will work on the new computers. Does anyone have any ideas on what we
might try?

 

[Sooper]

We got in some brand new computers and are dropping our ghost
image clone to these computers. (We've used these clones
hundreds of times.) However, on the new computers, after the
clone drops and we reboot the pc, the computer gets stuck in a
"rebooting loop" and never comes up. It reboots before you see
any Windows XP startup info like the logo screen, etc. There is
also no blue screen message either. It simply reboots during
the 'black' screen when starting up.

We're guessing something is different in hardware on the new pc
and are hopeful there is something we can do to our ghost image
clone to "update" it so it will work on the new computers. Does
anyone have any ideas on what we might try?

Why does your FROM name appear all munged up?

"=?Utf-8?B?S0hlbW1lbG1hbg==?="

The munging almost looks deliberate.

With all the many very recent postings you have made it almost seems
as if the groups is being spammed by a bot!

 

[Guest]

I guess I don't know why my display name is messed up. It should say
"KHemmelman".

I just thought of some additional info. The new computers came with SATA
hard drives. Perhaps there is something we need to add into the registry of
our old computers or clones so this new controller is detected?

 

[Yves Leclerc]

SATA drivers, if not an Intel controller, are not automatcially in XP. You
may have to do a re-install of XP to fix this.

 

[RA]

Putting an old clone on new and different hardware isn't really a good idea
and can sometimes be difficult to impossible. The components are different,
the drivers are different etc. You should build a new image using one of
your new machines. It doesn't take that long to do and then your image will
work perfectly with all your new machines.

 

[Guest]

Actually it does take a long time to do this. We have many versions of
clones for many different entities within our organization and with many
different models of computers in each entity we would end up with an enormous
number of clones we would have to maintain.

We had previously ran into an issue referencing a similiar situation in MS
KB Article 314082. The fix recommended in that article took care of that
issue and we've cloned old pc's to new hardware a large number of times using
this fix. The drivers get redetected and reloaded when the new pc starts up,
so I don't know that it's a problem. It may not be ideal, but the
alternative of designing new clones for each hardware revision is just not a
workable situation.

After playing around a bit more, we have gotten it to give the BSOD instead
of just rebooting. The code on the BSOD is:

STOP 0X0000007B (0XF78AE640, 0XC00000034, 0X00000000, 0X00000000)

I'm searching MS KB articles in the hopes that I can find some helpful info.

 

[Guest]

I thought I would post a followup message for others to reference in the
event they run into the same thing.

We had run into a similiar problem in the past and there is a MS KB Article
that provided a solution to that problem. That article is:
http://support.microsoft.com/default.aspx?scid=kb;en-us;314082

This article references moving XP to a new system and getting the following
stop code when starting up the new pc:

STOP: 0x0000007B (0xF741B84C,0xC0000034,0x00000000,0x00000000)

There is a mergeide.reg file at this KB article that you can run on the old
pc before cloning/moving it to the new pc. The reg file adds info about
hardware back into the registry and when the new pc starts up, it 'knows'
about this hardware and doesn't bomb when it sees those devices.

However, this time around, we got a slightly different stop code on the
BSOD, but it was pretty much an identical situation.

STOP 0X0000007B (0XF78AE640, 0XC00000034, 0X00000000, 0X00000000)

We've believe we have fixed our problem by adding additional hardware info
into the reg file from the KB article. The new computer we were having
problems with uses an Intel 82801 FB/FW ICH6/ICH6W SATA Controller. We added
the device id for this controller (and additional Intel controllers) into the
reg file following the same syntax in the reg file for the Intel devices and
then our disk to disk clone from an old pc to this new pc worked fine.
Obviously if others try this do it at your own risk, but since MS had
previously released a KB article with a fix, I'm guessing we are on the right
track with the solution. As an FYI, the Intel devices in this reg file from
Microsoft are Vendor 8086.

 

[NoneOfBusiness]

Putting an old clone on new and different hardware isn't really a good idea
and can sometimes be difficult to impossible. The components are different,
the drivers are different etc. You should build a new image using one of
your new machines. It doesn't take that long to do and then your image will
work perfectly with all your new machines.

or you can add your drivers to the old install and reimage. Dell
inlcudes all sorts of drivers installed in their images which are not
necessarily installed on the pc.. (Optiplex GX260 with SCSI raid
drivers? )