Archived from groups: microsoft.public.windowsxp.general (
More info?)
<brianwolters@gmail.com> wrote:
> No..it was connected to the internet and anti-virus was on. Someone
> told me that it may be a problem with the boot partion drive letter.
> That is doesn't match the drive letter assigned to the initial install.
> Is there anything I can do in the copy portion of Ghost to make an
> EXACT copy? The new copy drive boots but as I said, I log in, and it
> will say "LOADING PERSONAL SETTINGS", then "SAVING YOUR
> SETTINGS" and goes back to login prompt. It only does this on the
> new drive. The old one still works just fine. Any other suggestions
> using Ghost would be appreciated. Thanks!
OK, back to square one. You wrote: "I've used Norton Ghost but
it will get to the login part, load settings and then say logging off
and go back to login prompt." But it appears that the *clone* is
getting to login, etc., not Ghost.
Do the copy again disconnected from the Internet and with the
anti-virus disabled. Make the new clone's partition a primary
partition and have it marked "active". After the copy operation,
don't let the clone boot up. Disconnect the source HD to make
the "parent" OS invisible, THEN start up the PC. (Since the
HD that used to be at the head of the BIOS's HD boot order is
now disconnected, the BIOS will go to the next HD in the HD
boot order to look for the "active" partition, where it expects to
find the boot files, e.g. ntldr, boot.ini, and ntdetect.com .)
Since the clone will be at the head of the HD boot order, the
"rdisk(0)" parameter in the boot.ini entry will still apply. On
subsequent boots, both HDs may be connected and visible to
each other. If you don't want to make changes to the boot.ini
file to enable dual-booting, just switch the HDs' positions in the
BIOS's HD boot order to determine which HD's OS gets loaded.
The OS that runs will call its own partition "Local Disk C:", and
it will choose other letters for the other partitions. That's OK
unless you have short cuts that contain paths to other partitions.
If you don't disconnect the source HD to make the "parent" OS
invisible to the new clone during its first startup, the new clone
will form links with various random files in the "parent's" file
structure, and you'll never know that until you remove the
"parent" and find that some of the clone's files are missing.
*TimDaniels*