From: BillW50 on
In news:kei464l251ljticff1b3gagqp2vdqg1apr(a)4ax.com,
Chris Hill typed on Wed, 25 Jun 2008 08:37:42 -0500:
> 11 hours. Sounds to me like your original drive is on death's door.
> If it has a manufacturer's diagnostic available get it. Next, be very
> careful when you do the copy. do not boot xp with the copy attached
> via usb once the copy is complete, this usually causes disaster.

I am trying to do the same thing. although I have tried a number of
different ways. Seagate's Ontrack, Partition Manager 2005, etc. And I
clone about 10GB per hour speed wise. So far I can't clone a bootable
disk. And Gateway has two partitions, one a recovery. Plus I have
EAZ-Fix (go back like utility) which makes this far harder. As both
modify the MBR. What usually works for me (which I might have to do now)
is to use the restore disc to get a bootable HD and then clone it.

--
Bill
Gateway Celeron M 370 (1.5GHZ)
MX6124 (laptop) w/1GB
Windows XP Home SP2 (60GB HD)
Intel(r) 910GML (64MB shared)

From: BillW50 on
In news:cb50b$48608e1d$16412(a)news.teranews.com,
Barry Watzman typed on Tue, 24 Jun 2008 02:03:06 -0400:
> This often happens with Windows. Windows knows what drive it's
> installed on and if you "copy" or "clone" it to a new drive (Ghost,
> Drive Image, Acronis, etc.) the new drive may not work (won't boot).
> But it doesn't always happen, only sometimes. And I don't know why
> sometimes but not always.
>
> Pdigmking wrote:
>> Hello,
>>
>> I have a toshiba A105 with an 80gig HD. I have a new Wester Digital
>> HD that I'm trying to swap in there. I used Acronis Migrate easy to
>> copy the drive, and I used this USB connection kit. The copy
>> appeared to go well although it took 11 hours. When I plugged the
>> new drive and fired up the computer I get: "Unable To Run Operating
>> System" or something like that. The jumper setting is on default (no
>> jumpers) which is master drive. In setup the drive is recognized,
>> it just won't boot up. Connections are good. Any ideas?

Barry, under the Recovery Console command (Windows XP install disc). The
following two commands should fix that problem.

FIXMBR C:
FIXBOOT C:

If you have a HD larger than 130GB and you don't have a Windows XP with
any Service Packs install CD, don't try the above. As it probably will
corrupt the HD. It can be fixed, but what a PIA.

BOOTCFG /rebuild

I am not sure what the BOOTCFG command all does. but that might help
too.

--
Bill
Gateway Celeron M 370 (1.5GHZ)
MX6124 (laptop) w/1GB
Windows XP Home SP2 (60GB HD)
Intel(r) 910GML (64MB shared)

From: Barry Watzman on
Sometimes.

Not always.

I'm fully aware of 48-bit LBA and all of it's implications.

In the cases I have seen [ALL of the cases I have seen, and that's a lot
.... I'm a college instructor in IT], Windows starts to boot and you get
the first two screens (the black screen and then the almost solid blue
screen) and it hangs forever there. Fixmbr and Fixboot won't fix that
problem ... it's gotten past anything that those will fix. It has to do
with the system security descriptors, I think, and the fact that the
drive you are booting from is not the same drive that Windows WAS
installed on. However I have not figured out why it only happens SOMETIMES.



BillW50 wrote:
> In news:cb50b$48608e1d$16412(a)news.teranews.com,
> Barry Watzman typed on Tue, 24 Jun 2008 02:03:06 -0400:
>> This often happens with Windows. Windows knows what drive it's
>> installed on and if you "copy" or "clone" it to a new drive (Ghost,
>> Drive Image, Acronis, etc.) the new drive may not work (won't boot).
>> But it doesn't always happen, only sometimes. And I don't know why
>> sometimes but not always.
>>
>> Pdigmking wrote:
>>> Hello,
>>>
>>> I have a toshiba A105 with an 80gig HD. I have a new Wester Digital
>>> HD that I'm trying to swap in there. I used Acronis Migrate easy to
>>> copy the drive, and I used this USB connection kit. The copy
>>> appeared to go well although it took 11 hours. When I plugged the
>>> new drive and fired up the computer I get: "Unable To Run Operating
>>> System" or something like that. The jumper setting is on default (no
>>> jumpers) which is master drive. In setup the drive is recognized,
>>> it just won't boot up. Connections are good. Any ideas?
>
> Barry, under the Recovery Console command (Windows XP install disc). The
> following two commands should fix that problem.
>
> FIXMBR C:
> FIXBOOT C:
>
> If you have a HD larger than 130GB and you don't have a Windows XP with
> any Service Packs install CD, don't try the above. As it probably will
> corrupt the HD. It can be fixed, but what a PIA.
>
> BOOTCFG /rebuild
>
> I am not sure what the BOOTCFG command all does. but that might help too.
>
** Posted from http://www.teranews.com **
From: BillW50 on
In news:15f75$4866c56c$6051(a)news.teranews.com,
Barry Watzman typed on Sat, 28 Jun 2008 19:12:31 -0400:
> Sometimes.
>
> Not always.
>
> I'm fully aware of 48-bit LBA and all of it's implications.

Oh good! But others may not be.

> In the cases I have seen [ALL of the cases I have seen, and that's a
> lot ... I'm a college instructor in IT],

And I'm an electronic engineer. That doesn't mean I know everything
though. ;-)

> Windows starts to boot and you get the first two screens (the black
> screen and then the almost solid blue screen) and it hangs forever
> there. Fixmbr and Fixboot won't fix that problem ... it's gotten past
> anything that those will fix. It has to do with the system security
> descriptors, I think, and the fact that the drive you are booting from
> is not the same drive that Windows WAS installed on. However I have
> not figured out why it only happens SOMETIMES.

Sad! I have seen this too. But only on OEM Windows copies so far. You
too?

> BillW50 wrote:
>> In news:cb50b$48608e1d$16412(a)news.teranews.com,
>> Barry Watzman typed on Tue, 24 Jun 2008 02:03:06 -0400:
>>> This often happens with Windows. Windows knows what drive it's
>>> installed on and if you "copy" or "clone" it to a new drive (Ghost,
>>> Drive Image, Acronis, etc.) the new drive may not work (won't boot).
>>> But it doesn't always happen, only sometimes. And I don't know why
>>> sometimes but not always.
>>>
>>> Pdigmking wrote:
>>>> Hello,
>>>>
>>>> I have a toshiba A105 with an 80gig HD. I have a new Wester
>>>> Digital HD that I'm trying to swap in there. I used Acronis
>>>> Migrate easy to copy the drive, and I used this USB connection
>>>> kit. The copy appeared to go well although it took 11 hours. When
>>>> I plugged the new drive and fired up the computer I get: "Unable To
>>>> Run Operating System" or something like that. The
>>>> jumper setting is on default (no jumpers) which is master drive. In
>>>> setup the drive is recognized, it just won't boot up. Connections
>>>> are good. Any ideas?
>>
>> Barry, under the Recovery Console command (Windows XP install disc).
>> The following two commands should fix that problem.
>>
>> FIXMBR C:
>> FIXBOOT C:
>>
>> If you have a HD larger than 130GB and you don't have a Windows XP
>> with any Service Packs install CD, don't try the above. As it
>> probably will corrupt the HD. It can be fixed, but what a PIA.
>>
>> BOOTCFG /rebuild
>>
>> I am not sure what the BOOTCFG command all does. but that might help
>> too.

--
Bill
Gateway Celeron M 370 (1.5GHZ)
MX6124 (laptop) w/1GB
Windows XP Home SP2 (60GB HD)
Intel(r) 910GML (64MB shared)

From: BillW50 on
In news:15f75$4866c56c$6051(a)news.teranews.com,
Barry Watzman typed on Sat, 28 Jun 2008 19:12:31 -0400:
> Sometimes.
>
> Not always.
>
> I'm fully aware of 48-bit LBA and all of it's implications.
>
> In the cases I have seen [ALL of the cases I have seen, and that's a lot
> ... I'm a college instructor in IT], Windows starts to boot and you get
> the first two screens (the black screen and then the almost solid blue
> screen) and it hangs forever there. Fixmbr and Fixboot won't fix that
> problem ... it's gotten past anything that those will fix. It has to do
> with the system security descriptors, I think, and the fact that the drive
> you are booting from is not the same drive that Windows WAS installed on.
> However I have not figured out why it only happens SOMETIMES.

I believe I now know why. Check this out. Apparently once Windows sees the
original partition and the cloned partition at the same time, you are now
screwed.

http://www.goodells.net/multiboot/partsigs.htm#method3

Although what is also interesting is if you planned on having the botched
cloned partition to be drive C, using Win9x FDISK /MBR will fix this
problem. While Windows 2000/XP FIXMBR will not.

--
Bill
Gateway Celeron M 370 (1.5GHZ)
MX6124 (laptop) w/2GB
Windows XP Home SP2 120GB HD)
Intel(r) 910GML (64MB shared)