I used Norton Save & Restore to clone my 80GB HD to a new Samsung 300GB
drive. All went OK until I tried to swap the drives. The system booted from
the old C-drive instead of the new one. So I powered down and removed the
old one. When I powered up, it hangs on the XP splash screen. I'm back to
my old drive. Any ideas how I can get my Dell Dimension 4700 to see the new
drive and boot from it?

Thx,

GDS

Geoff wrote:
> I used Norton Save & Restore to clone my 80GB HD to a new Samsung
> 300GB drive. All went OK until I tried to swap the drives. The
> system booted from the old C-drive instead of the new one. So I
> powered down and removed the old one. When I powered up, it hangs on
> the XP splash screen. I'm back to my old drive. Any ideas how I can
> get my Dell Dimension 4700 to see the new drive and boot from it?
>
> Thx,
>
> GDS

The idea is to clone old disk to new, COMPLETELY REMOVE/DISCONNECT old disk
from system and let it boot from the new disk (a couple of times, maybe?).
THEN you can connect the old disk as slave...

--
Tumppi
=================================
A lot learned from these newsgroups
Helsinki, FINLAND
(translations from/to FI not always accurate
=================================

You may have to edit the bot.ini file on the SATA drive so XP knows which
drive to load from. The boot.ini is pointing to the IDE drive.

Thomas Wendell is right as well. If you boot from the old drive before
booting from the new drive XP sometimes writes a new signature to the new
drive causing it to become unbootable. Either one could be the problem.

--
Kerry Brown
Microsoft MVP - Shell/User
http://www.vistahelp.ca


"Geoff" <(E-Mail Removed)> wrote in message
news1CEB842-2089-406D-B533-(E-Mail Removed)...
>I used Norton Save & Restore to clone my 80GB HD to a new Samsung 300GB
> drive. All went OK until I tried to swap the drives. The system booted
> from
> the old C-drive instead of the new one. So I powered down and removed the
> old one. When I powered up, it hangs on the XP splash screen. I'm back
> to
> my old drive. Any ideas how I can get my Dell Dimension 4700 to see the
> new
> drive and boot from it?
>
> Thx,
>
> GDS

"Kerry Brown" wrote:

> You may have to edit the bot.ini file on the SATA drive so XP knows which
> drive to load from. The boot.ini is pointing to the IDE drive.
>
> Thomas Wendell is right as well. If you boot from the old drive before
> booting from the new drive XP sometimes writes a new signature to the new
> drive causing it to become unbootable. Either one could be the problem.
>
> --
> Kerry Brown
> Microsoft MVP - Shell/User
> http://www.vistahelp.ca
>
>
> "Geoff" <(E-Mail Removed)> wrote in message
> news1CEB842-2089-406D-B533-(E-Mail Removed)...
> >I used Norton Save & Restore to clone my 80GB HD to a new Samsung 300GB
> > drive. All went OK until I tried to swap the drives. The system booted
> > from
> > the old C-drive instead of the new one. So I powered down and removed the
> > old one. When I powered up, it hangs on the XP splash screen. I'm back
> > to
> > my old drive. Any ideas how I can get my Dell Dimension 4700 to see the
> > new
> > drive and boot from it?
> >
> > Thx,
> >
> > GDS
>
>
Kerry and Thomas,

There is no BOOT.INI file on either drive to edit. Also, SATA jumpers are
only used for potential incompatibility with 1.5GB SATA adapters; there is no
ability to set Master/Slave. So neither of your posts helped me,
unfortunately. Removing the old drive resulted in the hang on the splash
screen.

>> "Geoff" <(E-Mail Removed)> wrote in message
>> news1CEB842-2089-406D-B533-(E-Mail Removed)...
>> >I used Norton Save & Restore to clone my 80GB HD to a new Samsung 300GB
>> > drive. All went OK until I tried to swap the drives. The system
>> > booted
>> > from
>> > the old C-drive instead of the new one. So I powered down and removed
>> > the
>> > old one. When I powered up, it hangs on the XP splash screen. I'm
>> > back
>> > to
>> > my old drive. Any ideas how I can get my Dell Dimension 4700 to see
>> > the
>> > new
>> > drive and boot from it?
>> >
>> > Thx,
>> >
>> > GDS


> "Kerry Brown" wrote:
>
>> You may have to edit the bot.ini file on the SATA drive so XP knows which
>> drive to load from. The boot.ini is pointing to the IDE drive.
>>
>> Thomas Wendell is right as well. If you boot from the old drive before
>> booting from the new drive XP sometimes writes a new signature to the new
>> drive causing it to become unbootable. Either one could be the problem.
>>
>> --
>> Kerry Brown
>> Microsoft MVP - Shell/User
>> http://www.vistahelp.ca


"Geoff" <(E-Mail Removed)> wrote in message
news:C52D7B1E-23A3-436B-B7DE-(E-Mail Removed)...
> Kerry and Thomas,
> There is no BOOT.INI file on either drive to edit. Also, SATA jumpers are
> only used for potential incompatibility with 1.5GB SATA adapters; there is
> no
> ability to set Master/Slave. So neither of your posts helped me,
> unfortunately. Removing the old drive resulted in the hang on the splash
> screen.


Geoff:
As Thomas Wendell ("Tumppi"?) pointed out...

After you perform the disk-to-disk cloning operation you should disconnect
your source HDD (the 80 GB one) and make the initial boot with ONLY the
destination HDD (the 300 GB SATA HDD) connected. Thereafter, assuming the
disk cloning operation was successful, you can re:connect the old HDD and
access your BIOS to ensure that the boot priority order indicates the SATA
HDD will be your boot drive. (I'm assuming that's what you want).

It's unclear from your last post if you followed Thomas' instructions.
Anna

"Geoff" <(E-Mail Removed)> wrote in message
news:C52D7B1E-23A3-436B-B7DE-(E-Mail Removed)...
>
>
> "Kerry Brown" wrote:
>
>> You may have to edit the bot.ini file on the SATA drive so XP knows which
>> drive to load from. The boot.ini is pointing to the IDE drive.
>>
>> Thomas Wendell is right as well. If you boot from the old drive before
>> booting from the new drive XP sometimes writes a new signature to the new
>> drive causing it to become unbootable. Either one could be the problem.
>>
>> --
>> Kerry Brown
>> Microsoft MVP - Shell/User
>> http://www.vistahelp.ca
>>
>>
>> "Geoff" <(E-Mail Removed)> wrote in message
>> news1CEB842-2089-406D-B533-(E-Mail Removed)...
>> >I used Norton Save & Restore to clone my 80GB HD to a new Samsung 300GB
>> > drive. All went OK until I tried to swap the drives. The system
>> > booted
>> > from
>> > the old C-drive instead of the new one. So I powered down and removed
>> > the
>> > old one. When I powered up, it hangs on the XP splash screen. I'm
>> > back
>> > to
>> > my old drive. Any ideas how I can get my Dell Dimension 4700 to see
>> > the
>> > new
>> > drive and boot from it?
>> >
>> > Thx,
>> >
>> > GDS
>>
>>
> Kerry and Thomas,
>
> There is no BOOT.INI file on either drive to edit. Also, SATA jumpers are
> only used for potential incompatibility with 1.5GB SATA adapters; there is
> no
> ability to set Master/Slave. So neither of your posts helped me,
> unfortunately. Removing the old drive resulted in the hang on the splash
> screen.
>


More info is needed about the drives. Are they both SATA?

--
Kerry Brown
Microsoft MVP - Shell/User
http://www.vistahelp.ca

http://www.acronis.com/
Try the 15 day trialware ver of ATI 10, may help, your call..
Cheers
j;-j

"Geoff" wrote:

> I used Norton Save & Restore to clone my 80GB HD to a new Samsung 300GB
> drive. All went OK until I tried to swap the drives. The system booted from
> the old C-drive instead of the new one. So I powered down and removed the
> old one. When I powered up, it hangs on the XP splash screen. I'm back to
> my old drive. Any ideas how I can get my Dell Dimension 4700 to see the new
> drive and boot from it?
>
> Thx,
>
> GDS

"Anna" wrote:

>
> Geoff:
> As Thomas Wendell ("Tumppi"?) pointed out...
>
> After you perform the disk-to-disk cloning operation you should disconnect
> your source HDD (the 80 GB one) and make the initial boot with ONLY the
> destination HDD (the 300 GB SATA HDD) connected. Thereafter, assuming the
> disk cloning operation was successful, you can re:connect the old HDD and
> access your BIOS to ensure that the boot priority order indicates the SATA
> HDD will be your boot drive. (I'm assuming that's what you want).
>
> It's unclear from your last post if you followed Thomas' instructions.
> Anna
>
>
Anna,

I did exactly what he recommended. The new SATA drive (300GB) is in an
external enclosure, so I don't have to keep swapping drives into/out of the
bays.
After the copy completed, I shutdown, disconnected the old drive from the
primary SATA port, moved the new drive's SATA cable from the secondary to the
primary port, and restarted.

After several restarts, the freezes continued, so I hooked up the old drive
to the SECONDARY SATA port, hoping the machine would boot from the new drive
and view the old drive as just a data drive. However, the old drive was
still the C-drive, XP found it and booted up from it. There's my second
question: how do I switch the new drive to become the C-drive? XP with the
SATA setup seems to look for C, not for the drive that's physically on the
primary SATA port.

"Kerry Brown" wrote:


>
> More info is needed about the drives. Are they both SATA?
>
> --
> Kerry Brown
> Microsoft MVP - Shell/User
> http://www.vistahelp.ca
>
Yes, see my reply to Anna for more details.

BTW, Symantec's tech support rep just emailed me and recommended using
fdisk/mbr on the new drive. She thinks the MBR is corrupted. Not knowing
what's in an MBR (is it volume-specific info?), I can't evaluate this piece
of advice. The MBR was successfully copied from the old drive by Norton Save
& Restore. Does the MBR for the new drive have to be different from the old
drive, or exactly the same?

Plus, FDISK.EXE is not part of WinXP, so even if I could find a copy, I'm
reluctant to run it.

"Jaymon" wrote:

> http://www.acronis.com/
> Try the 15 day trialware ver of ATI 10, may help, your call..
> Cheers
> j;-j
>
I've seen this product on several forums and am going to give this approach
about 3 more days before I give up and try that route. I also have Partition
Magic 8.0, but sadly, it's not owned by Symantec so any vestiges of quality
support have vanished.