Cloned Additonal Hard Drive Not Recognized

"ColTom2" wrote in message
...
Hi Anna:

I received the new HDD and proceeded as carefully as I could in following
the correct procedures.

1. When I connected the new HDD in the Primary Slave position it indicated
finding new hardware etc; however, the HDD did not appear with a drive
letter assigned. I used Disk Management and finally initialized the disk,
but sill no drive letter. I noticed that it said "Unallocated" so I right
clicked and had very few options, but one was "New Partition". I finally
clicked on it and it did assign the next drive letter "F" and immediately
started Formatting the disk.

2. It took a good awhile to finally Format and it got to 100% and
indicated
the disk was "Healthy. Original Disk was "O" Local Drive "C" and new Disk
was "1" something.

3. I then clicked on Acronis and ran it's Clone procedures and everything
went as normal. Took about 15 minutes to clone the new HDD and said to hit
any key to shut down which I did. At this point I thought everything was
fine.

4. I reconnected the new HDD and changed the Jumper pin to 1 & 2,
disconnected the old HDD, and thought that I was set to go.

5. Low and behold I now apparently have a cloned HDD that is NOT bootable,
as it would not boot and I got the message to insert disk or whatever.

At this point I am just about fed up with HDD's and have no idea what to
do
next to get the cloned HDD to boot.

If you can tell me where I am and what I need to do next I will be most
appreciative. I still can't believe the new HDD will not boot.

Thanks,

Tom


Tom:
With respect to 1, 2, & 3 above...
When a brand-new unpartitioned/unformatted HDD is installed in the machine
as a secondary HDD the XP OS requires that the disk be "initialized" before
it can be integrated into the system and be partitioned & formatted. This
"initialization" process as I'm sure you discovered is quite simple & quick.
Ordinarily the OS will generate a message to this effect, i.e., the need for
initialization when the system boots to the user's boot drive and the user
accesses the Disk Management snap-in utility. But not always in our
experience. In any event there is that need to initialize the disk before
proceeding with the partitioning/formatting process so that one or more
drive letters will be assigned to the disk.

Actually there was probably no need for you to undertake the preceding
process since you were intending to clone the contents of your "source"
(boot) HDD to the new "destination" HDD using your Acronis disk-cloning
program. As long as you were making a disk-to-disk copy, the disk-cloning
process in & of itself would carry out the partitioning/formatting process
without user intervention and an appropriate drive letter (or letters) would
have been assigned by the OS to the cloned destination disk following
completion of the disk-cloning process. Under those circumstances there
really wasn't any need for you to invoke the Disk Management utility in
connection with that process. Ordinarily the only time there *would* be a
need for the DM process would be when you wanted to manipulate the number &
size of partitions on the destination HDD so that they would be different
from the number/size of the partitions on your source HDD. (And even over
that latter circumstance you could achieve this manipulation using Casper's
disk-cloning process; I'm unsure whether you could do the same with the
Acronis program although I believe you could).

It's been some time since I've worked with the Acronis program so I hope I'm
correct re the preceding info. If I'm not I trust you or someone coming upon
this thread will correct me.

With respect to 4...
I'm not clear as to why there was a need for you to change the jumper
configuration on your newly-cloned HDD. You're indicating at this point,
i.e., immediately following the disk-cloning process, you now jumpered the
disk Cable Select? Do I have this right? But wasn't it jumpered CS from the
time you first installed the disk?

In any event, are you absolutely sure the disk was jumpered CS at this point
after you disconnected your source HDD?

The potential problem here is that if you didn't correctly jumper the disk
CS and that Western Digital disk is the *only* HDD connected in the system,
then it must be jumpered what WD terms "Single". Failure to do so will
usually (but not always) result in a failure-to-boot situation.

(I'm assuming in all this is that following the disk-cloning operation with
both your source & destination HDDs connected you took a peek at the new HDD
via Windows Explorer or some such and as best you could determine it
appeared all the files/folders seemed to have been correctly copied).

All-in-all it sounds like a simple misconfiguration of one sort or another
is at the root of the problem (assuming the disk-cloning operation was
successful). It's hard to imagine you're dealing with another defective HDD.

Assuming you're unable to resolve the problem at this point, would you
consider doing the following?...

Download & install the trial version of Casper 6 from
http://www.fssdev.com/products/free/
Give it a whirl and see how it goes.
Note that this trial edition is slightly crippled in that it will create a
partition on the destination HDD only sufficient in size to hold the
contents of your source HDD. So that (in your case) where your source HDD is
a 250 GB HDD and the total data contents on that drive total, for example,
55 GB, the 250 GB HDD that you're using as the destination HDD will contain
a partition of 55 GB to hold those contents. The remaining disk space on the
destination HDD will be unpartitioned/unallocated. (Naturally you could
later use Disk Management to create & format whatever other partitions you
desired on that destination HDD). Of course there is no similar limitation
in the licensed version of Casper 6.

In any event there's no harm or permanent situation in using the trial
edition of Casper 6, so give it a shot just in case it's the Acronis
disk-cloning operation that's somehow involved in this problem you've
related.
Anna

"Anna" wrote in message
...

Tom:
(SNIP)
I'm not clear as to why there was a need for you to change the jumper
configuration on your newly-cloned HDD. You're indicating at this point,
i.e., immediately following the disk-cloning process, you now jumpered the
disk Cable Select? Do I have this right? But wasn't it jumpered CS from
the
time you first installed the disk?

In any event, are you absolutely sure the disk was jumpered CS at this
point
after you disconnected your source HDD?

The potential problem here is that if you didn't correctly jumper the disk
CS and that Western Digital disk is the *only* HDD connected in the
system,
then it must be jumpered what WD terms "Single". Failure to do so will
usually (but not always) result in a failure-to-boot situation.

(I'm assuming in all this is that following the disk-cloning operation
with
both your source & destination HDDs connected you took a peek at the new
HDD
via Windows Explorer or some such and as best you could determine it
appeared all the files/folders seemed to have been correctly copied).

All-in-all it sounds like a simple misconfiguration of one sort or another
is at the root of the problem (assuming the disk-cloning operation was
successful). It's hard to imagine you're dealing with another defective
HDD.
(SNIP)
Anna


"ColTom2" wrote in message
...
Hi Anna:

Well good news finally!

I reconnected the new cloned HDD this morning and tried to boot and it
failed, as I mentioned in my prior posting last night. I rebooted to see
what the BIOS indicated and no disk was found in either the Primary Master
or Primary Slave.

I had made a bootable CD with Acronis as they recommended, but of course
it would not work because of the disk not being found.

For some reason I thought of the Jumper pin which was in positions 1 & 2
(the same position as my old HDD), but anyway I removed the Jumper
entirely.

Guess what....with the Jumper pin removed the disk showed up in the BIOS
as Primary Master! Got a Windows screen shortly that said I should reboot
to
I suppose get the disk squared away (I forget exactly what it said and why
the reboot).

But when it rebooted everything on the new HDD works as should be.

Now I have two HDD's that work; however, with both connected to the end
IDE cable the old works with the Jumper pin in 1&2 and the new will only
work with the Jumper pin totally removed.

If you have any idea as to why I would love to hear it.

Anyway I just want to thank you immensely for all your time and effort in
helping me resolve this issue and I really do appreciate all that you have
done.

Tom

P.S. You helped me learn a lot more about HDD's than I ever knew, but I
now
know there is a lot more that I can learn.


Tom:
As I'm sure you're aware my previous post above was sent before I saw your
latest post above.

It would appear that it was the absence of the "Single" jumpered
configuration of your cloned WD HDD that caused the problem you related.
While it is not uncommon for PATA WD drives to exhibit the failure-to-boot
problem when the drive is the only HDD connected on the IDE data cable
because the BIOS (in many, if not most cases) will not detect the disk
unless it is jumpered as Single - in effect, unjumpered, usually there's not
a problem when the WD disk is jumpered Cable Select. In most instances -
even if the disk is the only HDD connected on the IDE data cable - there
will be no problem with disk detection by the motherboard's BIOS when the CS
configuration is used. But, as I believe I may have previously mentioned,
occasionally some motherboards *will* balk at a CS setting. It's rather
uncommon (except for older motherboards) but it does happen.

Of course, you're certain the WD HDD was correctly jumpered as CS yes?

Anyway, glad to hear you're back-in-business with a bootable cloned HDD.
Anna

"Anna" wrote in message
...

Tom:
(SNIP)
I'm not clear as to why there was a need for you to change the jumper
configuration on your newly-cloned HDD. You're indicating at this point,
i.e., immediately following the disk-cloning process, you now jumpered the
disk Cable Select? Do I have this right? But wasn't it jumpered CS from
the
time you first installed the disk?

In any event, are you absolutely sure the disk was jumpered CS at this
point
after you disconnected your source HDD?

The potential problem here is that if you didn't correctly jumper the disk
CS and that Western Digital disk is the *only* HDD connected in the
system,
then it must be jumpered what WD terms "Single". Failure to do so will
usually (but not always) result in a failure-to-boot situation.

(I'm assuming in all this is that following the disk-cloning operation
with
both your source & destination HDDs connected you took a peek at the new
HDD
via Windows Explorer or some such and as best you could determine it
appeared all the files/folders seemed to have been correctly copied).

All-in-all it sounds like a simple misconfiguration of one sort or another
is at the root of the problem (assuming the disk-cloning operation was
successful). It's hard to imagine you're dealing with another defective
HDD.
(SNIP)
Anna


"ColTom2" wrote in message
...
Hi Anna:

Well good news finally!

I reconnected the new cloned HDD this morning and tried to boot and it
failed, as I mentioned in my prior posting last night. I rebooted to see
what the BIOS indicated and no disk was found in either the Primary Master
or Primary Slave.

I had made a bootable CD with Acronis as they recommended, but of course
it would not work because of the disk not being found.

For some reason I thought of the Jumper pin which was in positions 1 & 2
(the same position as my old HDD), but anyway I removed the Jumper
entirely.

Guess what....with the Jumper pin removed the disk showed up in the BIOS
as Primary Master! Got a Windows screen shortly that said I should reboot
to
I suppose get the disk squared away (I forget exactly what it said and why
the reboot).

But when it rebooted everything on the new HDD works as should be.

Now I have two HDD's that work; however, with both connected to the end
IDE cable the old works with the Jumper pin in 1&2 and the new will only
work with the Jumper pin totally removed.

If you have any idea as to why I would love to hear it.

Anyway I just want to thank you immensely for all your time and effort in
helping me resolve this issue and I really do appreciate all that you have
done.

Tom

P.S. You helped me learn a lot more about HDD's than I ever knew, but I
now
know there is a lot more that I can learn.


Tom:
As I'm sure you're aware my previous post above was sent before I saw your
latest post above.

It would appear that it was the absence of the "Single" jumpered
configuration of your cloned WD HDD that caused the problem you related.
While it is not uncommon for PATA WD drives to exhibit the failure-to-boot
problem when the drive is the only HDD connected on the IDE data cable
because the BIOS (in many, if not most cases) will not detect the disk
unless it is jumpered as Single - in effect, unjumpered, usually there's not
a problem when the WD disk is jumpered Cable Select. In most instances -
even if the disk is the only HDD connected on the IDE data cable - there
will be no problem with disk detection by the motherboard's BIOS when the CS
configuration is used. But, as I believe I may have previously mentioned,
occasionally some motherboards *will* balk at a CS setting. It's rather
uncommon (except for older motherboards) but it does happen.

Of course, you're certain the WD HDD was correctly jumpered as CS yes?

Anyway, glad to hear you're back-in-business with a bootable cloned HDD.
Anna

Hi Anna:

Apparently we were both writing replies at the same time and you did not
see my prior posting where everything was resolved prior to you sending this
posting. Anyway please read my 1/9/2010 12:25 PM posting.

First let me say something that I should have said in my 1/9/2010 12:41AM
posting earlier. I did not use the CS method in my cloning due to all the
other postings in relation to IDE cable positions etc, as I was apprehensive
in doing so. My last successful clone prior to this I used the Pri Master
(5&6) and Pri Slave (3&4) and that is what I did this time.

I do have some additional comments related to what you have indicated.

The last HDD that I cloned (the one that failed) I initially used WD
Digital/Data Lifeguard Tools to do the original clone. Using it for some
reason versus Acronis I never knew about Initializing the new disk etc. With
this recent new disk I never got an OS generated msg indicating that I
needed to initialize it. The only way that I found it was when the new disk
did not appear as a new drive letter in My Computer and I went to Disk
Management in an effort to see what was going on.

When I opened Disk Mgmt and saw the new Disk listed as "1" with a red mark
of some sort by Initialize is when I first knew anything about having to
initialize a disk. I initialized it not really knowing what I was doing.
Afterwards the disk drive still did not appear in My Computer. Whereas the
Primary Disk "0" indicated status "Healthy" the new disk after initializing
still indicated "Unallotted". When I right clicked on it I got very few
options one of which was "New Partition". Again I did not really know what I
was doing, but was only trying to get the new disk assigned a drive letter
where I could see it. Finally I clicked on New Partition and it launched the
Partition Wizard and I was able to get the next drive letter "F" assigned to
this disk. Immediately afterwards it auto started "Formatting" which took
well over an hour. I was plowing "New Ground" with all this and not knowing
really what I was doing. I tried reading all the Help files related to this
process, but to me they were totally inept with my limited experience.

So now I know a heck of a lot more about HDD's than I ever knew thanks to
you.

Again I want to thank you for your perseverance with a HDD novice. I
cannot really tell you how much that I appreciate all that you did for me in
this matter.

Kindest regards,

Tom

P.S. "All's well that end "well"....sorta like a aircraft landing in that
any you walk away from is a great one!


"Anna" wrote in message
...

"ColTom2" wrote in message
...
Hi Anna:

I received the new HDD and proceeded as carefully as I could in following
the correct procedures.

1. When I connected the new HDD in the Primary Slave position it indicated
finding new hardware etc; however, the HDD did not appear with a drive
letter assigned. I used Disk Management and finally initialized the disk,
but sill no drive letter. I noticed that it said "Unallocated" so I right
clicked and had very few options, but one was "New Partition". I finally
clicked on it and it did assign the next drive letter "F" and immediately
started Formatting the disk.

2. It took a good awhile to finally Format and it got to 100% and
indicated
the disk was "Healthy. Original Disk was "O" Local Drive "C" and new Disk
was "1" something.

3. I then clicked on Acronis and ran it's Clone procedures and everything
went as normal. Took about 15 minutes to clone the new HDD and said to hit
any key to shut down which I did. At this point I thought everything was
fine.

4. I reconnected the new HDD and changed the Jumper pin to 1 & 2,
disconnected the old HDD, and thought that I was set to go.

5. Low and behold I now apparently have a cloned HDD that is NOT bootable,
as it would not boot and I got the message to insert disk or whatever.

At this point I am just about fed up with HDD's and have no idea what to
do
next to get the cloned HDD to boot.

If you can tell me where I am and what I need to do next I will be most
appreciative. I still can't believe the new HDD will not boot.

Thanks,

Tom


Tom:
With respect to 1, 2, & 3 above...
When a brand-new unpartitioned/unformatted HDD is installed in the machine
as a secondary HDD the XP OS requires that the disk be "initialized" before
it can be integrated into the system and be partitioned & formatted. This
"initialization" process as I'm sure you discovered is quite simple & quick.
Ordinarily the OS will generate a message to this effect, i.e., the need for
initialization when the system boots to the user's boot drive and the user
accesses the Disk Management snap-in utility. But not always in our
experience. In any event there is that need to initialize the disk before
proceeding with the partitioning/formatting process so that one or more
drive letters will be assigned to the disk.

Actually there was probably no need for you to undertake the preceding
process since you were intending to clone the contents of your "source"
(boot) HDD to the new "destination" HDD using your Acronis disk-cloning
program. As long as you were making a disk-to-disk copy, the disk-cloning
process in & of itself would carry out the partitioning/formatting process
without user intervention and an appropriate drive letter (or letters) would
have been assigned by the OS to the cloned destination disk following
completion of the disk-cloning process. Under those circumstances there
really wasn't any need for you to invoke the Disk Management utility in
connection with that process. Ordinarily the only time there *would* be a
need for the DM process would be when you wanted to manipulate the number &
size of partitions on the destination HDD so that they would be different
from the number/size of the partitions on your source HDD. (And even over
that latter circumstance you could achieve this manipulation using Casper's
disk-cloning process; I'm unsure whether you could do the same with the
Acronis program although I believe you could).

It's been some time since I've worked with the Acronis program so I hope I'm
correct re the preceding info. If I'm not I trust you or someone coming upon
this thread will correct me.

With respect to 4...
I'm not clear as to why there was a need for you to change the jumper
configuration on your newly-cloned HDD. You're indicating at this point,
i.e., immediately following the disk-cloning process, you now jumpered the
disk Cable Select? Do I have this right? But wasn't it jumpered CS from the
time you first installed the disk?

In any event, are you absolutely sure the disk was jumpered CS at this point
after you disconnected your source HDD?

The potential problem here is that if you didn't correctly jumper the disk
CS and that Western Digital disk is the *only* HDD connected in the system,
then it must be jumpered what WD terms "Single". Failure to do so will
usually (but not always) result in a failure-to-boot situation.

(I'm assuming in all this is that following the disk-cloning operation with
both your source & destination HDDs connected you took a peek at the new HDD
via Windows Explorer or some such and as best you could determine it
appeared all the files/folders seemed to have been correctly copied).

All-in-all it sounds like a simple misconfiguration of one sort or another
is at the root of the problem (assuming the disk-cloning operation was
successful). It's hard to imagine you're dealing with another defective HDD.

Assuming you're unable to resolve the problem at this point, would you
consider doing the following?...

Download & install the trial version of Casper 6 from
http://www.fssdev.com/products/free/
Give it a whirl and see how it goes.
Note that this trial edition is slightly crippled in that it will create a
partition on the destination HDD only sufficient in size to hold the
contents of your source HDD. So that (in your case) where your source HDD is
a 250 GB HDD and the total data contents on that drive total, for example,
55 GB, the 250 GB HDD that you're using as the destination HDD will contain
a partition of 55 GB to hold those contents. The remaining disk space on the
destination HDD will be unpartitioned/unallocated. (Naturally you could
later use Disk Management to create & format whatever other partitions you
desired on that destination HDD). Of course there is no similar limitation
in the licensed version of Casper 6.

In any event there's no harm or permanent situation in using the trial
edition of Casper 6, so give it a shot just in case it's the Acronis
disk-cloning operation that's somehow involved in this problem you've
related.
Anna

Hi Anna:

Apparently we were both writing replies at the same time and you did not
see my prior posting where everything was resolved prior to you sending this
posting. Anyway please read my 1/9/2010 12:25 PM posting.

First let me say something that I should have said in my 1/9/2010 12:41AM
posting earlier. I did not use the CS method in my cloning due to all the
other postings in relation to IDE cable positions etc, as I was apprehensive
in doing so. My last successful clone prior to this I used the Pri Master
(5&6) and Pri Slave (3&4) and that is what I did this time.

I do have some additional comments related to what you have indicated.

The last HDD that I cloned (the one that failed) I initially used WD
Digital/Data Lifeguard Tools to do the original clone. Using it for some
reason versus Acronis I never knew about Initializing the new disk etc. With
this recent new disk I never got an OS generated msg indicating that I
needed to initialize it. The only way that I found it was when the new disk
did not appear as a new drive letter in My Computer and I went to Disk
Management in an effort to see what was going on.

When I opened Disk Mgmt and saw the new Disk listed as "1" with a red mark
of some sort by Initialize is when I first knew anything about having to
initialize a disk. I initialized it not really knowing what I was doing.
Afterwards the disk drive still did not appear in My Computer. Whereas the
Primary Disk "0" indicated status "Healthy" the new disk after initializing
still indicated "Unallotted". When I right clicked on it I got very few
options one of which was "New Partition". Again I did not really know what I
was doing, but was only trying to get the new disk assigned a drive letter
where I could see it. Finally I clicked on New Partition and it launched the
Partition Wizard and I was able to get the next drive letter "F" assigned to
this disk. Immediately afterwards it auto started "Formatting" which took
well over an hour. I was plowing "New Ground" with all this and not knowing
really what I was doing. I tried reading all the Help files related to this
process, but to me they were totally inept with my limited experience.

So now I know a heck of a lot more about HDD's than I ever knew thanks to
you.

Again I want to thank you for your perseverance with a HDD novice. I
cannot really tell you how much that I appreciate all that you did for me in
this matter.

Kindest regards,

Tom

P.S. "All's well that end "well"....sorta like a aircraft landing in that
any you walk away from is a great one!


"Anna" wrote in message
...

"ColTom2" wrote in message
...
Hi Anna:

I received the new HDD and proceeded as carefully as I could in following
the correct procedures.

1. When I connected the new HDD in the Primary Slave position it indicated
finding new hardware etc; however, the HDD did not appear with a drive
letter assigned. I used Disk Management and finally initialized the disk,
but sill no drive letter. I noticed that it said "Unallocated" so I right
clicked and had very few options, but one was "New Partition". I finally
clicked on it and it did assign the next drive letter "F" and immediately
started Formatting the disk.

2. It took a good awhile to finally Format and it got to 100% and
indicated
the disk was "Healthy. Original Disk was "O" Local Drive "C" and new Disk
was "1" something.

3. I then clicked on Acronis and ran it's Clone procedures and everything
went as normal. Took about 15 minutes to clone the new HDD and said to hit
any key to shut down which I did. At this point I thought everything was
fine.

4. I reconnected the new HDD and changed the Jumper pin to 1 & 2,
disconnected the old HDD, and thought that I was set to go.

5. Low and behold I now apparently have a cloned HDD that is NOT bootable,
as it would not boot and I got the message to insert disk or whatever.

At this point I am just about fed up with HDD's and have no idea what to
do
next to get the cloned HDD to boot.

If you can tell me where I am and what I need to do next I will be most
appreciative. I still can't believe the new HDD will not boot.

Thanks,

Tom


Tom:
With respect to 1, 2, & 3 above...
When a brand-new unpartitioned/unformatted HDD is installed in the machine
as a secondary HDD the XP OS requires that the disk be "initialized" before
it can be integrated into the system and be partitioned & formatted. This
"initialization" process as I'm sure you discovered is quite simple & quick.
Ordinarily the OS will generate a message to this effect, i.e., the need for
initialization when the system boots to the user's boot drive and the user
accesses the Disk Management snap-in utility. But not always in our
experience. In any event there is that need to initialize the disk before
proceeding with the partitioning/formatting process so that one or more
drive letters will be assigned to the disk.

Actually there was probably no need for you to undertake the preceding
process since you were intending to clone the contents of your "source"
(boot) HDD to the new "destination" HDD using your Acronis disk-cloning
program. As long as you were making a disk-to-disk copy, the disk-cloning
process in & of itself would carry out the partitioning/formatting process
without user intervention and an appropriate drive letter (or letters) would
have been assigned by the OS to the cloned destination disk following
completion of the disk-cloning process. Under those circumstances there
really wasn't any need for you to invoke the Disk Management utility in
connection with that process. Ordinarily the only time there *would* be a
need for the DM process would be when you wanted to manipulate the number &
size of partitions on the destination HDD so that they would be different
from the number/size of the partitions on your source HDD. (And even over
that latter circumstance you could achieve this manipulation using Casper's
disk-cloning process; I'm unsure whether you could do the same with the
Acronis program although I believe you could).

It's been some time since I've worked with the Acronis program so I hope I'm
correct re the preceding info. If I'm not I trust you or someone coming upon
this thread will correct me.

With respect to 4...
I'm not clear as to why there was a need for you to change the jumper
configuration on your newly-cloned HDD. You're indicating at this point,
i.e., immediately following the disk-cloning process, you now jumpered the
disk Cable Select? Do I have this right? But wasn't it jumpered CS from the
time you first installed the disk?

In any event, are you absolutely sure the disk was jumpered CS at this point
after you disconnected your source HDD?

The potential problem here is that if you didn't correctly jumper the disk
CS and that Western Digital disk is the *only* HDD connected in the system,
then it must be jumpered what WD terms "Single". Failure to do so will
usually (but not always) result in a failure-to-boot situation.

(I'm assuming in all this is that following the disk-cloning operation with
both your source & destination HDDs connected you took a peek at the new HDD
via Windows Explorer or some such and as best you could determine it
appeared all the files/folders seemed to have been correctly copied).

All-in-all it sounds like a simple misconfiguration of one sort or another
is at the root of the problem (assuming the disk-cloning operation was
successful). It's hard to imagine you're dealing with another defective HDD.

Assuming you're unable to resolve the problem at this point, would you
consider doing the following?...

Download & install the trial version of Casper 6 from
http://www.fssdev.com/products/free/
Give it a whirl and see how it goes.
Note that this trial edition is slightly crippled in that it will create a
partition on the destination HDD only sufficient in size to hold the
contents of your source HDD. So that (in your case) where your source HDD is
a 250 GB HDD and the total data contents on that drive total, for example,
55 GB, the 250 GB HDD that you're using as the destination HDD will contain
a partition of 55 GB to hold those contents. The remaining disk space on the
destination HDD will be unpartitioned/unallocated. (Naturally you could
later use Disk Management to create & format whatever other partitions you
desired on that destination HDD). Of course there is no similar limitation
in the licensed version of Casper 6.

In any event there's no harm or permanent situation in using the trial
edition of Casper 6, so give it a shot just in case it's the Acronis
disk-cloning operation that's somehow involved in this problem you've
related.
Anna

Hi Anna:

CS was always jumpered in 1 & 2 on both HDD's. However, with all that I have
been through I am not certain about anything....

Thanks again,

Tom


"Anna" wrote in message
...

"Anna" wrote in message
...

Tom:
(SNIP)
I'm not clear as to why there was a need for you to change the jumper
configuration on your newly-cloned HDD. You're indicating at this point,
i.e., immediately following the disk-cloning process, you now jumpered the
disk Cable Select? Do I have this right? But wasn't it jumpered CS from
the
time you first installed the disk?

In any event, are you absolutely sure the disk was jumpered CS at this
point
after you disconnected your source HDD?

The potential problem here is that if you didn't correctly jumper the disk
CS and that Western Digital disk is the *only* HDD connected in the
system,
then it must be jumpered what WD terms "Single". Failure to do so will
usually (but not always) result in a failure-to-boot situation.

(I'm assuming in all this is that following the disk-cloning operation
with
both your source & destination HDDs connected you took a peek at the new
HDD
via Windows Explorer or some such and as best you could determine it
appeared all the files/folders seemed to have been correctly copied).

All-in-all it sounds like a simple misconfiguration of one sort or another
is at the root of the problem (assuming the disk-cloning operation was
successful). It's hard to imagine you're dealing with another defective
HDD.
(SNIP)
Anna


"ColTom2" wrote in message
...
Hi Anna:

Well good news finally!

I reconnected the new cloned HDD this morning and tried to boot and it
failed, as I mentioned in my prior posting last night. I rebooted to see
what the BIOS indicated and no disk was found in either the Primary Master
or Primary Slave.

I had made a bootable CD with Acronis as they recommended, but of course
it would not work because of the disk not being found.

For some reason I thought of the Jumper pin which was in positions 1 & 2
(the same position as my old HDD), but anyway I removed the Jumper
entirely.

Guess what....with the Jumper pin removed the disk showed up in the BIOS
as Primary Master! Got a Windows screen shortly that said I should reboot
to
I suppose get the disk squared away (I forget exactly what it said and why
the reboot).

But when it rebooted everything on the new HDD works as should be.

Now I have two HDD's that work; however, with both connected to the end
IDE cable the old works with the Jumper pin in 1&2 and the new will only
work with the Jumper pin totally removed.

If you have any idea as to why I would love to hear it.

Anyway I just want to thank you immensely for all your time and effort in
helping me resolve this issue and I really do appreciate all that you have
done.

Tom

P.S. You helped me learn a lot more about HDD's than I ever knew, but I
now
know there is a lot more that I can learn.


Tom:
As I'm sure you're aware my previous post above was sent before I saw your
latest post above.

It would appear that it was the absence of the "Single" jumpered
configuration of your cloned WD HDD that caused the problem you related.
While it is not uncommon for PATA WD drives to exhibit the failure-to-boot
problem when the drive is the only HDD connected on the IDE data cable
because the BIOS (in many, if not most cases) will not detect the disk
unless it is jumpered as Single - in effect, unjumpered, usually there's not
a problem when the WD disk is jumpered Cable Select. In most instances -
even if the disk is the only HDD connected on the IDE data cable - there
will be no problem with disk detection by the motherboard's BIOS when the CS
configuration is used. But, as I believe I may have previously mentioned,
occasionally some motherboards *will* balk at a CS setting. It's rather
uncommon (except for older motherboards) but it does happen.

Of course, you're certain the WD HDD was correctly jumpered as CS yes?

Anyway, glad to hear you're back-in-business with a bootable cloned HDD.
Anna

Hi Anna:

CS was always jumpered in 1 & 2 on both HDD's. However, with all that I have
been through I am not certain about anything....

Thanks again,

Tom


"Anna" wrote in message
...

"Anna" wrote in message
...

Tom:
(SNIP)
I'm not clear as to why there was a need for you to change the jumper
configuration on your newly-cloned HDD. You're indicating at this point,
i.e., immediately following the disk-cloning process, you now jumpered the
disk Cable Select? Do I have this right? But wasn't it jumpered CS from
the
time you first installed the disk?

In any event, are you absolutely sure the disk was jumpered CS at this
point
after you disconnected your source HDD?

The potential problem here is that if you didn't correctly jumper the disk
CS and that Western Digital disk is the *only* HDD connected in the
system,
then it must be jumpered what WD terms "Single". Failure to do so will
usually (but not always) result in a failure-to-boot situation.

(I'm assuming in all this is that following the disk-cloning operation
with
both your source & destination HDDs connected you took a peek at the new
HDD
via Windows Explorer or some such and as best you could determine it
appeared all the files/folders seemed to have been correctly copied).

All-in-all it sounds like a simple misconfiguration of one sort or another
is at the root of the problem (assuming the disk-cloning operation was
successful). It's hard to imagine you're dealing with another defective
HDD.
(SNIP)
Anna


"ColTom2" wrote in message
...
Hi Anna:

Well good news finally!

I reconnected the new cloned HDD this morning and tried to boot and it
failed, as I mentioned in my prior posting last night. I rebooted to see
what the BIOS indicated and no disk was found in either the Primary Master
or Primary Slave.

I had made a bootable CD with Acronis as they recommended, but of course
it would not work because of the disk not being found.

For some reason I thought of the Jumper pin which was in positions 1 & 2
(the same position as my old HDD), but anyway I removed the Jumper
entirely.

Guess what....with the Jumper pin removed the disk showed up in the BIOS
as Primary Master! Got a Windows screen shortly that said I should reboot
to
I suppose get the disk squared away (I forget exactly what it said and why
the reboot).

But when it rebooted everything on the new HDD works as should be.

Now I have two HDD's that work; however, with both connected to the end
IDE cable the old works with the Jumper pin in 1&2 and the new will only
work with the Jumper pin totally removed.

If you have any idea as to why I would love to hear it.

Anyway I just want to thank you immensely for all your time and effort in
helping me resolve this issue and I really do appreciate all that you have
done.

Tom

P.S. You helped me learn a lot more about HDD's than I ever knew, but I
now
know there is a lot more that I can learn.


Tom:
As I'm sure you're aware my previous post above was sent before I saw your
latest post above.

It would appear that it was the absence of the "Single" jumpered
configuration of your cloned WD HDD that caused the problem you related.
While it is not uncommon for PATA WD drives to exhibit the failure-to-boot
problem when the drive is the only HDD connected on the IDE data cable
because the BIOS (in many, if not most cases) will not detect the disk
unless it is jumpered as Single - in effect, unjumpered, usually there's not
a problem when the WD disk is jumpered Cable Select. In most instances -
even if the disk is the only HDD connected on the IDE data cable - there
will be no problem with disk detection by the motherboard's BIOS when the CS
configuration is used. But, as I believe I may have previously mentioned,
occasionally some motherboards *will* balk at a CS setting. It's rather
uncommon (except for older motherboards) but it does happen.

Of course, you're certain the WD HDD was correctly jumpered as CS yes?

Anyway, glad to hear you're back-in-business with a bootable cloned HDD.
Anna