Jim wrote:
> Oh, didn't realize that it was the Windows XP Repair Install that was
> hanging too, I thought you simply had restored the Ghost image and it was
> hanging on boot-up

Both hang, actually (unfortunately). ;-(

>>The 7Y250(1) developed bad sectors. I removed 7Y250(1) and ran on the
>>7Y250(2). In prepping the drives to send back Maxtor, I accidentally
>>formatted the good drive rather than the bad drive.
> Ugh.

Ugh is right.

>>I first took the 250G 7Y250(1) (bad) and did a chkdsk /f /r to get
>>around the bad sectors. Then, I ghosted from the 7Y250(1) (bad) to the
>>new 6Y250 drive.
> Ok, so then did the original Maxtor that now has marked bad sectors, are you
> sure this boots?

Yes, absolutely. It still boots, and in fact I'm running with it right
now (not from where I'm posting, however).

> IOW, you're Ghosting it from the bad sector drive to the
> new drive, but we don't know at this point if the bad sector drive is a good
> source for Ghosting, correct?

Fortunately, we do know that it's good, because it boots/runs perfectly.

> bad sector'd drive. It's important only to the extent that I'm trying to
> determine if this is a problem w/ Ghost, OR, the source (i.e., bad sector
> drive).

I'm almost thinking this is a problem with Ghost. Or else it's a Windows
security "feature".

> drive, even boots! If it doesn't, Ghosting isn't the issue. (btw, by
> Ghosting I assume you mean copy/clone from one HD to the other).

Yes, specifically in this case using Norton Ghost V10.

> On the
> other hand, if the source HD does boot, then sure, this would point to the
> Ghosting process. It may simply be that the copy/clone process was in
> error. If so, I can suggest a work around using another tool.

That would be WONDERFUL if you know of such a utility. If it does a
sector by sector copy, it'll probably be OK, but I can't find anything
that'll do a sector copy and simply ignore bad sectors.

Thanks again Jim!

-->Neil