Boot problem, copied Master

"Michael Solomon (MS-MVP Windows Shell/User)" wrote in
message ...
Thanks for the information.

--
Michael Solomon MS-MVP
Windows Shell/User
Backup is a PC User's Best Friend
DTS-L.Org: http://www.dts-l.org/


I've found that copying drives, most of the time, is a flawless operation.
But sometimes, for no good reason, it goes wrong. Sometimes I suspect it's
bad data or bad sectors on the original drive. Running a scandisk and defrag
first is a good idea, as is getting rid of temporary files.

I've found that sometime Ghost works better, sometimes Drive Image works
better, and sometimes the Hard Drive Mfg. software is a better choice.

Since I do thins for a living, I have a few extra tricks up my sleeve that a
normal person wouldn't have available to them. For instance, sometimes it
works better when I put both the old and new drives into another working
machine, booting from neither, and run the copy that way.

Fortunately, most of the time it just works the first time and I don't have
to think much about it, just wait for the copy to finish and plug in the new
drive.

Personally, once cloning (imaging) became available as a relatively
inexpensive option for the purposes of copying a drive, I've found it much
preferable to the copy function for reasons you previously cited.

Now that we have activation to consider, it's all the more important the
system sees such a drive as an exact duplicate, something simply copying the
files doesn't always create. Since the option is there for Bill because he
has an application that supports it, there's no reason for him to use copy
over imaging at least for reasons that he wanted in the first place which
was an exact duplicate.

As you've pointed out to him and I have done the same in a previous thread,
he may have to do a repair install on the cloned drive, at least if he
insists on continuing from where he is and not attempting the image.

I can't speak to his other issue in that regard as it appears to be some
glitch he's having with the Powerquest software and I've not seen that
glitch before.

--
Michael Solomon MS-MVP
Windows Shell/User
Backup is a PC User's Best Friend
DTS-L.Org: http://www.dts-l.org/

"D.Currie" wrote in message
...

"Michael Solomon (MS-MVP Windows Shell/User)" wrote in
message ...
Thanks for the information.

--
Michael Solomon MS-MVP
Windows Shell/User
Backup is a PC User's Best Friend
DTS-L.Org: http://www.dts-l.org/


I've found that copying drives, most of the time, is a flawless operation.
But sometimes, for no good reason, it goes wrong. Sometimes I suspect it's
bad data or bad sectors on the original drive. Running a scandisk and
defrag
first is a good idea, as is getting rid of temporary files.

I've found that sometime Ghost works better, sometimes Drive Image works
better, and sometimes the Hard Drive Mfg. software is a better choice.

Since I do thins for a living, I have a few extra tricks up my sleeve that
a
normal person wouldn't have available to them. For instance, sometimes it
works better when I put both the old and new drives into another working
machine, booting from neither, and run the copy that way.

Fortunately, most of the time it just works the first time and I don't
have
to think much about it, just wait for the copy to finish and plug in the
new
drive.

Michael Solomon (MS-MVP Windows Shell/User) wrote:

Personally, once cloning (imaging) became available as a relatively
inexpensive option for the purposes of copying a drive, I've found it much
preferable to the copy function for reasons you previously cited.

Now that we have activation to consider, it's all the more important the
system sees such a drive as an exact duplicate, something simply copying the
files doesn't always create. Since the option is there for Bill because he
has an application that supports it, there's no reason for him to use copy
over imaging at least for reasons that he wanted in the first place which
was an exact duplicate.

As you've pointed out to him and I have done the same in a previous thread,
he may have to do a repair install on the cloned drive, at least if he
insists on continuing from where he is and not attempting the image.

I can't speak to his other issue in that regard as it appears to be some
glitch he's having with the Powerquest software and I've not seen that
glitch before.

You have me pretty well convinced and converted for the future,
Michael. I will stop trying to "copy" and will use "drive image"
just as soon as PowerQuest gives me a way to recreate the drive
from its image. Right now I can make images, but I can't recreate.
Now about the cloned drive I have now....I have nothing to lose by
doing as you say, a repair install on the cloned drive. Could you
lead me to a procedure for it? I believe I have Recovery Console
on that drive already. I believe I can install the cloned drive
as "Master or Single" and boot to Recovery Console. So please give
me instructions. And thank you both.
Bill L.

Xref: kermit microsoft.public.windowsxp.basics:205275

Just open Drive Image on the drive where you have the application installed,
choose restore, select the image, select the destination, note, you will
have to use the option to first delete the partition to which you wish to
restore the image as it will be restoring a partition. The option is a part
of the drive image application and a step in the restore process.

If everything works as planned, you shouldn't need to use Recovery Console
though, as "D" stated, since the clone will have the boot information from
the drive that is first in line, you may need to rebuild the boot config on
the new drive as follows:
NOTE: The instructions below explain getting to the Recovery Console from
the XP CD, I've never accessed the RC from the hard drive, I assume you do
it from within Windows and it then reboots the system to the RC. If you
can't for some reason, just follow the instructions below and then type the
command:

Place the XP CD in the drive, save your settings and exit. The system will
reboot and should boot from the CD. If you see a message to hit any key in
order to boot from the CD, do so, otherwise, assuming your system supports
it, the system should boot from the CD on its own as it can't find
an OS on the hard drive.

XP Setup will begin by examining your system, don't worry, just let it run,
it's just copying some files to a temp folder. Ultimately, you'll be
brought to a menu. Choose, "Repair a Windows XP installation using the
Recovery Console, press R.

You will be asked for an administrators password. This is not any of the
accounts you've created for XP. It's a hidden system account for which
users are asked only to create a password during setup. Most leave this
blank. If you left it blank, when asked for a password, just leave blank
and press enter.

At the prompt type bootcfg /rebuild and press enter.



--
Michael Solomon MS-MVP
Windows Shell/User
Backup is a PC User's Best Friend
DTS-L.Org: http://www.dts-l.org/

"William B. Lurie" wrote in message
...
Michael Solomon (MS-MVP Windows Shell/User) wrote:

Personally, once cloning (imaging) became available as a relatively
inexpensive option for the purposes of copying a drive, I've found it
much preferable to the copy function for reasons you previously cited.

Now that we have activation to consider, it's all the more important the
system sees such a drive as an exact duplicate, something simply copying
the files doesn't always create. Since the option is there for Bill
because he has an application that supports it, there's no reason for him
to use copy over imaging at least for reasons that he wanted in the first
place which was an exact duplicate.

As you've pointed out to him and I have done the same in a previous
thread, he may have to do a repair install on the cloned drive, at least
if he insists on continuing from where he is and not attempting the
image.

I can't speak to his other issue in that regard as it appears to be some
glitch he's having with the Powerquest software and I've not seen that
glitch before.

You have me pretty well convinced and converted for the future,
Michael. I will stop trying to "copy" and will use "drive image"
just as soon as PowerQuest gives me a way to recreate the drive
from its image. Right now I can make images, but I can't recreate.
Now about the cloned drive I have now....I have nothing to lose by
doing as you say, a repair install on the cloned drive. Could you
lead me to a procedure for it? I believe I have Recovery Console
on that drive already. I believe I can install the cloned drive
as "Master or Single" and boot to Recovery Console. So please give
me instructions. And thank you both.
Bill L.

In-Reply-To:
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Message-ID:
Newsgroups: microsoft.public.windowsxp.basics
NNTP-Posting-Host: adsl-215-67-174.bct.bellsouth.net 68.215.67.174
Lines: 1
Path: kermit!newsfeed-east.nntpserver.com!nntpserver.com!priapus.visi.co m!orange.octanews.net!news.octanews.net!green.octa news.net!news-out.octanews.net!news.moat.net!border1.nntp.sjc.gi ganews.com!border2.nntp.sjc.giganews.com!nntp.giga news.com!cyclone-sf.
pbi.net!216.218.192.242!news.he.net!news-hog.berkeley.edu!ucberkeley!enews.sgi.com!msrnewsc 1!TK2MSFTNGP08.phx.gbl!tk2msftngp13.phx.gbl
Xref: kermit microsoft.public.windowsxp.basics:205347

Michael Solomon (MS-MVP Windows Shell/User) wrote:
Just open Drive Image on the drive where you have the application installed,
choose restore, select the image, select the destination, note, you will
have to use the option to first delete the partition to which you wish to
restore the image as it will be restoring a partition. The option is a part
of the drive image application and a step in the restore process.

If everything works as planned, you shouldn't need to use Recovery Console
though, as "D" stated, since the clone will have the boot information from
the drive that is first in line, you may need to rebuild the boot config on
the new drive as follows:
NOTE: The instructions below explain getting to the Recovery Console from
the XP CD, I've never accessed the RC from the hard drive, I assume you do
it from within Windows and it then reboots the system to the RC. If you
can't for some reason, just follow the instructions below and then type the
command:

Place the XP CD in the drive, save your settings and exit. The system will
reboot and should boot from the CD. If you see a message to hit any key in
order to boot from the CD, do so, otherwise, assuming your system supports
it, the system should boot from the CD on its own as it can't find
an OS on the hard drive.

XP Setup will begin by examining your system, don't worry, just let it run,
it's just copying some files to a temp folder. Ultimately, you'll be
brought to a menu. Choose, "Repair a Windows XP installation using the
Recovery Console, press R.

You will be asked for an administrators password. This is not any of the
accounts you've created for XP. It's a hidden system account for which
users are asked only to create a password during setup. Most leave this
blank. If you left it blank, when asked for a password, just leave blank
and press enter.

At the prompt type bootcfg /rebuild and press enter.



Okay, Michael. Good news and bad news. I put the clone in as
Master/Single, and got to RC. I chose "R". Got to the prompt and
entered bootcfg /rebuild. It mumbled a bit and then asked:
Add installation to boot list? I said Yes.
It then asked me to Enter Load Identifier..... I just hit Enter.
It then asked me to enter OS Load Options..... I just hit Enter.
It took me back to the c:\windows prompt.
Bottom line is, I didn't know what to enter, and when I
restarted the system, the Slave drive is in exactly the same
condition I described....it boots past the black Windows Logo
screen, to the blue Windows XP logo screen, and then switches to
the Activation error message I reported before. Was I supposed to
enter something at thos eprompts? If so, what would you suggest?
I'd be happy to try again, before I go for the reformat and new
Drive Image run.
Bill L.

It should have listed what was on the drive thus giving you the necessary
information. Try this, go back to the RC, at the prompt type bootcfg /scan,
that should tell you and the RC what is there, make note of it, then type
bootcfg /rebuild.

If you still can't get it going, try doing a repair install as that may
rebuild the MBR:
Repair install as follows:
Boot from the CD. If your system is set to be able to boot from the CD, it
should detect the disk and give a brief message, during the boot up, if you
wish to boot from the CD press any key.

Once you have pressed a key, setup should begin. You will see a reference
asking if you need to load special drivers and another notice that if you
wish to begin the ASR (Automatic Recovery Console) depress F2. Just let
setup run past all of that. It will continue to load files and drivers.

Then it will bring you to a screen. Eventually, you will come to a screen
with the option to (1) setup Windows or (2) Repair Windows Installation
using the Recovery console.

The first option, to setup Windows is the one you want and requires you to
press enter. When asked, press F8 to accept the end user agreement. Setup
will then search for previous versions of Windows. Upon finding your
version, it will ask if you wish to Repair your current installation or
install fresh. Press R, that will run a repair installation. From there
on, follow the screens.


--
Michael Solomon MS-MVP
Windows Shell/User
Backup is a PC User's Best Friend
DTS-L.Org: http://www.dts-l.org/

"William B. Lurie" wrote in message
...
Michael Solomon (MS-MVP Windows Shell/User) wrote:
Just open Drive Image on the drive where you have the application
installed, choose restore, select the image, select the destination,
note, you will have to use the option to first delete the partition to
which you wish to restore the image as it will be restoring a partition.
The option is a part of the drive image application and a step in the
restore process.

If everything works as planned, you shouldn't need to use Recovery
Console though, as "D" stated, since the clone will have the boot
information from the drive that is first in line, you may need to rebuild
the boot config on the new drive as follows:
NOTE: The instructions below explain getting to the Recovery Console from
the XP CD, I've never accessed the RC from the hard drive, I assume you
do it from within Windows and it then reboots the system to the RC. If
you can't for some reason, just follow the instructions below and then
type the command:

Place the XP CD in the drive, save your settings and exit. The system
will
reboot and should boot from the CD. If you see a message to hit any key
in
order to boot from the CD, do so, otherwise, assuming your system
supports
it, the system should boot from the CD on its own as it can't find
an OS on the hard drive.

XP Setup will begin by examining your system, don't worry, just let it
run,
it's just copying some files to a temp folder. Ultimately, you'll be
brought to a menu. Choose, "Repair a Windows XP installation using the
Recovery Console, press R.

You will be asked for an administrators password. This is not any of the
accounts you've created for XP. It's a hidden system account for which
users are asked only to create a password during setup. Most leave this
blank. If you left it blank, when asked for a password, just leave blank
and press enter.

At the prompt type bootcfg /rebuild and press enter.



Okay, Michael. Good news and bad news. I put the clone in as
Master/Single, and got to RC. I chose "R". Got to the prompt and
entered bootcfg /rebuild. It mumbled a bit and then asked:
Add installation to boot list? I said Yes.
It then asked me to Enter Load Identifier..... I just hit Enter.
It then asked me to enter OS Load Options..... I just hit Enter.
It took me back to the c:\windows prompt.
Bottom line is, I didn't know what to enter, and when I
restarted the system, the Slave drive is in exactly the same
condition I described....it boots past the black Windows Logo
screen, to the blue Windows XP logo screen, and then switches to
the Activation error message I reported before. Was I supposed to
enter something at thos eprompts? If so, what would you suggest?
I'd be happy to try again, before I go for the reformat and new
Drive Image run.
Bill L.

Michael Solomon (MS-MVP Windows Shell/User) wrote:
It should have listed what was on the drive thus giving you the necessary
information. Try this, go back to the RC, at the prompt type bootcfg /scan,
that should tell you and the RC what is there, make note of it, then type
bootcfg /rebuild.

If you still can't get it going, try doing a repair install as that may
rebuild the MBR:
Repair install as follows:
Boot from the CD. If your system is set to be able to boot from the CD, it
should detect the disk and give a brief message, during the boot up, if you
wish to boot from the CD press any key.

Once you have pressed a key, setup should begin. You will see a reference
asking if you need to load special drivers and another notice that if you
wish to begin the ASR (Automatic Recovery Console) depress F2. Just let
setup run past all of that. It will continue to load files and drivers.

Then it will bring you to a screen. Eventually, you will come to a screen
with the option to (1) setup Windows or (2) Repair Windows Installation
using the Recovery console.

The first option, to setup Windows is the one you want and requires you to
press enter. When asked, press F8 to accept the end user agreement. Setup
will then search for previous versions of Windows. Upon finding your
version, it will ask if you wish to Repair your current installation or
install fresh. Press R, that will run a repair installation. From there
on, follow the screens.


Okay, Michael, more progress each time. Using one of the processes
you suggested, I got to the (1) Setup Windows option on the
Recovery Console. It proceeded to Setup Windows, and this time it
started with 39 minutes to go, and actually proceeded to load from
there, because the countdown actually proceeded. It got to about
33 minutes to go, and started asking the usual questions, and when
it got to entering my product key, I tried three different product
key. I was hoping that it would accept the Product Key of the XP
installation of which I had made a copy.......no, it wouldn't. I
then tried the Product Key of the XP Corporate CD that I borrowed
in order to get it to "boot to CD".......no, it wouldn't. I tried
the Product Key of the XP Home Edition I have lying around not
being used...again, no acceptance.

I'd have thought it would accept either the Master's PK, or that
of the CD that's in the reader......but no such luck.

Your advice and information have been very good. Can I impose
on you for the next bit?

Bill Lurie

All you should need is the key for the setup that is on that disk. If this
is a clone of the first disk, then whatever product key was used to set that
up should work here.

--
Michael Solomon MS-MVP
Windows Shell/User
Backup is a PC User's Best Friend
DTS-L.Org: http://www.dts-l.org/

"William B. Lurie" wrote in message
...
Michael Solomon (MS-MVP Windows Shell/User) wrote:
It should have listed what was on the drive thus giving you the necessary
information. Try this, go back to the RC, at the prompt type bootcfg
/scan, that should tell you and the RC what is there, make note of it,
then type bootcfg /rebuild.

If you still can't get it going, try doing a repair install as that may
rebuild the MBR:
Repair install as follows:
Boot from the CD. If your system is set to be able to boot from the CD,
it
should detect the disk and give a brief message, during the boot up, if
you
wish to boot from the CD press any key.

Once you have pressed a key, setup should begin. You will see a
reference
asking if you need to load special drivers and another notice that if you
wish to begin the ASR (Automatic Recovery Console) depress F2. Just let
setup run past all of that. It will continue to load files and drivers.

Then it will bring you to a screen. Eventually, you will come to a
screen
with the option to (1) setup Windows or (2) Repair Windows Installation
using the Recovery console.

The first option, to setup Windows is the one you want and requires you
to
press enter. When asked, press F8 to accept the end user agreement.
Setup
will then search for previous versions of Windows. Upon finding your
version, it will ask if you wish to Repair your current installation or
install fresh. Press R, that will run a repair installation. From there
on, follow the screens.


Okay, Michael, more progress each time. Using one of the processes
you suggested, I got to the (1) Setup Windows option on the
Recovery Console. It proceeded to Setup Windows, and this time it
started with 39 minutes to go, and actually proceeded to load from
there, because the countdown actually proceeded. It got to about
33 minutes to go, and started asking the usual questions, and when
it got to entering my product key, I tried three different product
key. I was hoping that it would accept the Product Key of the XP
installation of which I had made a copy.......no, it wouldn't. I
then tried the Product Key of the XP Corporate CD that I borrowed
in order to get it to "boot to CD".......no, it wouldn't. I tried
the Product Key of the XP Home Edition I have lying around not
being used...again, no acceptance.

I'd have thought it would accept either the Master's PK, or that
of the CD that's in the reader......but no such luck.

Your advice and information have been very good. Can I impose
on you for the next bit?

Bill Lurie

Michael Solomon (MS-MVP Windows Shell/User) wrote:
All you should need is the key for the setup that is on that disk. If this
is a clone of the first disk, then whatever product key was used to set that
up should work here.

Right, Michael. That's what I figured. But I checked with AIDA as
to what key is on the Master right now, and used that when
asked, and I got the error message. Well....I will try it again.
It's frustrating to have gotten over the next hurdle, the one
that is really the last one, and it won't accept it.
Bill L.

Hey Bill, got a quick suggestion for you: When you enter that code, be VERY
careful of similar letter/number characters. Been there done that! I
finally learned to NEVER write the key down in normal longhand; only block
print it in all caps. or better yet, print it out from something like AIDA.
When I first got my machine, I scanned the label to get the number copied
for convenience, but then I hand copied it to a business card and guess
what? Yup, 0 and O problem and C and G problems, PLUS I managed to screw a
1 vs and l at one point. Hmm, believe it or not, that's a (one) and a
(lower case l (ell)) back there! Holy crap Martha!! :-)~[ Why I thought
there would be a lower case L is still beyond me, but, ... .

You've sure had an interesting time of it. I'd call that patience and
perseverence! Hope this one's the winner fer ya!
Me? Doing pretty good - almost figured it out!! More news soon.

PopRivet


"William B. Lurie" wrote in message
...
Michael Solomon (MS-MVP Windows Shell/User) wrote:
All you should need is the key for the setup that is on that disk. If
this
is a clone of the first disk, then whatever product key was used to set
that
up should work here.

Right, Michael. That's what I figured. But I checked with AIDA as
to what key is on the Master right now, and used that when
asked, and I got the error message. Well....I will try it again.
It's frustrating to have gotten over the next hurdle, the one
that is really the last one, and it won't accept it.
Bill L.

Excellent suggestion, a major cause of key code issues and I was just about
to suggest it to him when I saw your post.

--
Michael Solomon MS-MVP
Windows Shell/User
Backup is a PC User's Best Friend
DTS-L.Org: http://www.dts-l.org/

"Pop Rivet" wrote in message
...
Hey Bill, got a quick suggestion for you: When you enter that code, be
VERY
careful of similar letter/number characters. Been there done that! I
finally learned to NEVER write the key down in normal longhand; only block
print it in all caps. or better yet, print it out from something like
AIDA.
When I first got my machine, I scanned the label to get the number copied
for convenience, but then I hand copied it to a business card and guess
what? Yup, 0 and O problem and C and G problems, PLUS I managed to screw
a
1 vs and l at one point. Hmm, believe it or not, that's a (one) and a
(lower case l (ell)) back there! Holy crap Martha!! :-)~[ Why I
thought
there would be a lower case L is still beyond me, but, ... .

You've sure had an interesting time of it. I'd call that patience and
perseverence! Hope this one's the winner fer ya!
Me? Doing pretty good - almost figured it out!! More news soon.

PopRivet


"William B. Lurie" wrote in message
...
Michael Solomon (MS-MVP Windows Shell/User) wrote:
All you should need is the key for the setup that is on that disk. If
this
is a clone of the first disk, then whatever product key was used to set
that
up should work here.

Right, Michael. That's what I figured. But I checked with AIDA as
to what key is on the Master right now, and used that when
asked, and I got the error message. Well....I will try it again.
It's frustrating to have gotten over the next hurdle, the one
that is really the last one, and it won't accept it.
Bill L.

Michael Solomon (MS-MVP Windows Shell/User) wrote:
Excellent suggestion, a major cause of key code issues and I was just about
to suggest it to him when I saw your post.

Yes, thank you and Pop both, Michael, but I have been extremely
careful about that. Let me point out something to you about
Microsoft's choice of letters and numbers in those ProdKeys.
Look 'em over very carefully. I have five sets right here in
front of me. I see no 0 or O ... I see no 1 .....
I am certain that that is not my problem. Fellows, I have
decided that I am going to put aside this Drive-Image-Generated
"COPY" of my Master Drive, and this afternoon I made a
Drive Image 7.0.3 "IMAge", which you, Michael, have been
telling me is what I should have been doing all along.

I imaged Master to a separate partition on my Slave Hard Drive.
It is nowhere near the same size in Bytes as what it is supposed
to be an image of. It is maybe 80% as large. It's late to be
doing anything with it tonight, but tomorrow I'm going to study
it, and the Manual, and I'm going to ask for specific instructions
on how to recreate a duplicate of my Master which I can boot and
run. You know, that has been my goal all along.
--
William B. Lurie

William B. Lurie wrote:
Michael Solomon (MS-MVP Windows Shell/User) wrote:

Excellent suggestion, a major cause of key code issues and I was just
about to suggest it to him when I saw your post.

Yes, thank you and Pop both, Michael, but I have been extremely
careful about that. Let me point out something to you about
Microsoft's choice of letters and numbers in those ProdKeys.
Look 'em over very carefully. I have five sets right here in
front of me. I see no 0 or O ... I see no 1 .....
I am certain that that is not my problem. Fellows, I have
decided that I am going to put aside this Drive-Image-Generated
"COPY" of my Master Drive, and this afternoon I made a
Drive Image 7.0.3 "IMAge", which you, Michael, have been
telling me is what I should have been doing all along.

I imaged Master to a separate partition on my Slave Hard Drive.
It is nowhere near the same size in Bytes as what it is supposed
to be an image of. It is maybe 80% as large. It's late to be
doing anything with it tonight, but tomorrow I'm going to study
it, and the Manual, and I'm going to ask for specific instructions
on how to recreate a duplicate of my Master which I can boot and
run. You know, that has been my goal all along.
And now continuing next morning, I hate this thread being so long,
but it is continuing logically, I guess.

When I started this morning, my Master had C: as 5306 MB, Active/Primary.
My Slave had G: as the new Drive Image, 4128.7 MB, only logical.
Slave also had I: old D-I 'Copy', 4188 MB, Active/Primary
I deleted the partion containing the 'Copy' which I have been
unable to make operational all this time.
I then used Partition Magic to set the newly-created Drive Image
as Active and Primary. It is now the only partition on that
drive, except for what is unused ('extended') space.
If need be, I will delete that, too, and format that whole drive,
and make a new Drive Image of the Master on that hard drive.
Notice that I finally got around to doing what you've been telling
me I should have done in the first place.

I am, of course, on my Master drive, and looking at the partition
on the Slave with Windows Explorer, all that is there other than
a few SysInfo files and the like, is one file....4192 MB,
and it is the PowerQuest Image file. You told me that is the clone
of my Master Hard Drive XP. So now what do I do with that drive,
that partition, that file, to make it so that I can use it as a
clone of my Master Drive, and substitute it in place of my
Master Drive (literally and operationally)?

--
William B. Lurie

William B. Lurie wrote:
William B. Lurie wrote:

Michael Solomon (MS-MVP Windows Shell/User) wrote:

Excellent suggestion, a major cause of key code issues and I was just
about to suggest it to him when I saw your post.

Yes, thank you and Pop both, Michael, but I have been extremely
careful about that. Let me point out something to you about
Microsoft's choice of letters and numbers in those ProdKeys.
Look 'em over very carefully. I have five sets right here in
front of me. I see no 0 or O ... I see no 1 .....
I am certain that that is not my problem. Fellows, I have
decided that I am going to put aside this Drive-Image-Generated
"COPY" of my Master Drive, and this afternoon I made a
Drive Image 7.0.3 "IMAge", which you, Michael, have been
telling me is what I should have been doing all along.

I imaged Master to a separate partition on my Slave Hard Drive.
It is nowhere near the same size in Bytes as what it is supposed
to be an image of. It is maybe 80% as large. It's late to be
doing anything with it tonight, but tomorrow I'm going to study
it, and the Manual, and I'm going to ask for specific instructions
on how to recreate a duplicate of my Master which I can boot and
run. You know, that has been my goal all along.

And now continuing next morning, I hate this thread being so long,
but it is continuing logically, I guess.

When I started this morning, my Master had C: as 5306 MB, Active/Primary.
My Slave had G: as the new Drive Image, 4128.7 MB, only logical.
Slave also had I: old D-I 'Copy', 4188 MB, Active/Primary
I deleted the partion containing the 'Copy' which I have been
unable to make operational all this time.
I then used Partition Magic to set the newly-created Drive Image
as Active and Primary. It is now the only partition on that
drive, except for what is unused ('extended') space.
If need be, I will delete that, too, and format that whole drive,
and make a new Drive Image of the Master on that hard drive.
Notice that I finally got around to doing what you've been telling
me I should have done in the first place.

I am, of course, on my Master drive, and looking at the partition
on the Slave with Windows Explorer, all that is there other than
a few SysInfo files and the like, is one file....4192 MB,
and it is the PowerQuest Image file. You told me that is the clone
of my Master Hard Drive XP. So now what do I do with that drive,
that partition, that file, to make it so that I can use it as a
clone of my Master Drive, and substitute it in place of my
Master Drive (literally and operationally)?

Just to continue this thread, and get some practice, and make
sure I did what I was supposed to, I reformatted my Slave dive,
took everything off it in the process, created one new full
sized partition, and then did a Drive Image image/backup creation
on that drive. I did not do a 'Drive Copy' but a Drive Image Backup.
I hope that's what I was supposed to do, Michael and Pop.

The size of the XP partition on the Master, which I imaged, is
16000 MB with 5373 in use, 'active---primary'..... 'C:'.
The size of the Slave is 38154 MB partition (G with now 4207 MB
in use. I hope I did it right, and I hope somebody will tell me
now how to make the Slave Drive bootable and a true clone of the
XP partition of the Master Drive.

--
William B. Lurie

Drive Image compresses the image file so there might be a size differential.

It certainly should be operational on the master drive and all you should
have to do is use Drive Image to restore it to that drive.

As far as the restoration process is concerned, the same holds true for the
secondary drive. That said, I don't know if that will make it bootable as
I've never done this operation to a separate hard drive on the same system.
I would think if you are replacing one drive with the other there should be
no problem but if you have both drives installed, there might be an issue.

One thought occurred to me, as oppose to setting the second drive as slave,
have you considered making it a secondary master; this is only for the
purpose of having both drives installed at the same time as your previous
configuration seemed to be. If it is simply replacing the master, then I
would think setting it as the master drive would be the way to go.

--
Michael Solomon MS-MVP
Windows Shell/User
Backup is a PC User's Best Friend
DTS-L.Org: http://www.dts-l.org/

"William B. Lurie" wrote in message
...
William B. Lurie wrote:
Michael Solomon (MS-MVP Windows Shell/User) wrote:

Excellent suggestion, a major cause of key code issues and I was just
about to suggest it to him when I saw your post.

Yes, thank you and Pop both, Michael, but I have been extremely
careful about that. Let me point out something to you about
Microsoft's choice of letters and numbers in those ProdKeys.
Look 'em over very carefully. I have five sets right here in
front of me. I see no 0 or O ... I see no 1 .....
I am certain that that is not my problem. Fellows, I have
decided that I am going to put aside this Drive-Image-Generated
"COPY" of my Master Drive, and this afternoon I made a
Drive Image 7.0.3 "IMAge", which you, Michael, have been
telling me is what I should have been doing all along.

I imaged Master to a separate partition on my Slave Hard Drive.
It is nowhere near the same size in Bytes as what it is supposed
to be an image of. It is maybe 80% as large. It's late to be
doing anything with it tonight, but tomorrow I'm going to study
it, and the Manual, and I'm going to ask for specific instructions
on how to recreate a duplicate of my Master which I can boot and
run. You know, that has been my goal all along.
And now continuing next morning, I hate this thread being so long,
but it is continuing logically, I guess.

When I started this morning, my Master had C: as 5306 MB, Active/Primary.
My Slave had G: as the new Drive Image, 4128.7 MB, only logical.
Slave also had I: old D-I 'Copy', 4188 MB, Active/Primary
I deleted the partion containing the 'Copy' which I have been
unable to make operational all this time.
I then used Partition Magic to set the newly-created Drive Image
as Active and Primary. It is now the only partition on that
drive, except for what is unused ('extended') space.
If need be, I will delete that, too, and format that whole drive,
and make a new Drive Image of the Master on that hard drive.
Notice that I finally got around to doing what you've been telling
me I should have done in the first place.

I am, of course, on my Master drive, and looking at the partition
on the Slave with Windows Explorer, all that is there other than
a few SysInfo files and the like, is one file....4192 MB,
and it is the PowerQuest Image file. You told me that is the clone
of my Master Hard Drive XP. So now what do I do with that drive,
that partition, that file, to make it so that I can use it as a
clone of my Master Drive, and substitute it in place of my
Master Drive (literally and operationally)?

--
William B. Lurie