changing harddisk without a re-install of XP and programs

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Can you please tell me if I can copy my current disk to a new one and then
startup from the new one without having tot reinstall windows and al the
programs? It's just a new harddisk without any other changes.
 
You may wish to visit the support website of the manufacturer of your
new hard drive and see if they have a free utility program that you can use to
accomplish this task. For example, if you have a new Western Digital drive,
you can download their free Data Lifeguard Tools which includes "drive-to-drive
copy capability" (Ref: http://support.wdc.com/download/).

Fujitsu
http://www.fcpa.fujitsu.com/download/hard-drives/#diagnostic

IBM and Hitachi
http://www.hgst.com/hdd/support/download.htm#DFT

Maxtor
http://www.maxtor.com/en/support/products/index.htm

Seagate
http://www.seagate.com/support/seatools/index.html

Western Digital
http://support.wdc.com/download/
www.westerndigital.com

Or you can purchase Norton Ghost and create an "image"
of your old hard drive:

Norton Ghost 2003
http://www.symantec.com/sabu/ghost/ghost_personal/

--
Carey Frisch
Microsoft MVP
Windows XP - Shell/User

Be Smart! Protect Your PC!
http://www.microsoft.com/athome/security/protect/default.aspx

----------------------------------------------------------------------------

:

| Can you please tell me if I can copy my current disk to a new one and then
| startup from the new one without having tot reinstall windows and al the
| programs? It's just a new harddisk without any other changes.
 
averbunt said:
Can you please tell me if I can copy my current disk to a new one and then
startup from the new one without having tot reinstall windows and al the
programs? It's just a new harddisk without any other changes.

Be sure to copy the two files in system32 to a floppy: wpa.dbl and wpa.bak

After rebooting (into safe mode) copy them back into system32. The usually,
but not always, avoids re-registering.

The free software listed by Carey will work fine but you might consider
investing in Acronis True Image. While it will not immediately make a copy
to another disk, you can create a backup on the primary drive, then swap
drives (new drive as primary master, old boot drive on secondary controller)
then boot the True Image recovery disk and tell it to build the new boot
drive from the old drive's backup. While is two steps, the Acronis True
Image can be used as a really good backup tool, especially if you got a DVD
burner. If you don't have enough space on the original boot drive then you
can backup across the network to another system that has enough space.

I have never used Norton Ghost, maybe it does the same thing???
 
Beemer Biker said:
Be sure to copy the two files in system32 to a floppy:
wpa.dbl and wpa.bak

After rebooting (into safe mode) copy them back into system32.
The usually, but not always, avoids re-registering.

The free software listed by Carey will work fine but you might
consider investing in Acronis True Image. While it will not
immediately make a copy to another disk, you can create a
backup on the primary drive, then swap drives (new drive as
primary master, old boot drive on secondary controller) then
boot the True Image recovery disk and tell it to build the new
boot drive from the old drive's backup. While is two steps,
the Acronis True Image can be used as a really good backup
tool, especially if you got a DVD burner. If you don't have
enough space on the original boot drive then you can backup
across the network to another system that has enough space.

I have never used Norton Ghost, maybe it does the same
thing???


I use Drive Image 7 which became Norton Ghost 9.0 when
Symantec bought out PowerQuest last year. Drive Image,
Ghost, True Image, and many other cloning utilities allow
one to copy a partition (i.e. a "Local Disk") from one HD to
another HD byte-for-byte so that programs installed on an
OS remain installed. In Drive Image, this is called a "Drive
Copy" operation. If the copy is to be bootable, you tell the
utility to make the new partition a "primary" one, and if it will
be the partition that has the boot manager and loader to be
used on the new HD, to mark the partition "active". If the HD
doesn't have a Master Boot Record (needed if any partition
on the HD is to be booted), you tell the utility to copy over
the "MBR" as well from the source HD. What you get is a
HD with a copy of the original OS and its files that don't
even know they reside on a different HD.

In doing this, you should be careful not to boot up the new
OS for the 1st time with the old copy of the OS visible to it.
Otherwise, the "child" OS will set pointers within itself that
point to files in its "parent" OS and the "child" will thereafter
be dependent on the continued presence of its "parent".
The easiest way to accomplish the transition is to jumper
the new HD as Slave and the old HD as Master (assuming
they are on the same IDE cable) to keep the old HD at the
head of the BIOS's boot sequence. After the copy, remove
the old HD, putting the new HD in the old HD's position.
(Jumpers don't matter unless you're using Cable Select
and/or you intend to use a 2nd HD on the same cable.)
The new HD will automatically go to the head of the boot
sequence, so it will be selected for booting when the PC starts
up. Once the new HD's OS has been started for the 1st time,
you can shut it down and put in the 2nd HD for use as extra
storage. If you do so, you'll want the BIOS to use the new HD
as the boot drive, so jumper it as Master and the old HD as
Slave so that the BIOS will by default set its boot sequence
with the new HD ahead of the old HD. You might also have
to check in the BIOS to see that this is indeed the case, and
you may have to adjust the boot sequence yourself if it is not
set correctly.

So the answer to the question of "can I transfer the old HD's
OS and files to a new HD without re-installing anything" is
"Yes". This can be done with various free utilities, but the
utilities that include various file archiving capabilities and
making compressed OS images (non-bootable files containing
an OS image) - such as Ghost, or True Image, or several others -
cost some money.

*TimDan*
 
Timothy Daniels said:
: SNIP


I use Drive Image 7 which became Norton Ghost 9.0 when
Symantec bought out PowerQuest last year. Drive Image,
Ghost, True Image, and many other cloning utilities allow
one to copy a partition (i.e. a "Local Disk") from one HD to
another HD byte-for-byte so that programs installed on an
OS remain installed. In Drive Image, this is called a "Drive
Copy" operation. If the copy is to be bootable, you tell the
utility to make the new partition a "primary" one, and if it will
be the partition that has the boot manager and loader to be
used on the new HD, to mark the partition "active". If the HD
doesn't have a Master Boot Record (needed if any partition
on the HD is to be booted), you tell the utility to copy over
the "MBR" as well from the source HD. What you get is a
HD with a copy of the original OS and its files that don't
even know they reside on a different HD.

In doing this, you should be careful not to boot up the new
OS for the 1st time with the old copy of the OS visible to it.
Otherwise, the "child" OS will set pointers within itself that
point to files in its "parent" OS and the "child" will thereafter
be dependent on the continued presence of its "parent".
The easiest way to accomplish the transition is to jumper
the new HD as Slave and the old HD as Master (assuming
they are on the same IDE cable) to keep the old HD at the
head of the BIOS's boot sequence. After the copy, remove
the old HD, putting the new HD in the old HD's position.
(Jumpers don't matter unless you're using Cable Select
and/or you intend to use a 2nd HD on the same cable.)
The new HD will automatically go to the head of the boot
sequence, so it will be selected for booting when the PC starts
up. Once the new HD's OS has been started for the 1st time,
you can shut it down and put in the 2nd HD for use as extra
storage. If you do so, you'll want the BIOS to use the new HD
as the boot drive, so jumper it as Master and the old HD as
Slave so that the BIOS will by default set its boot sequence
with the new HD ahead of the old HD. You might also have
to check in the BIOS to see that this is indeed the case, and
you may have to adjust the boot sequence yourself if it is not
set correctly.

Thanks, I was wondering were it came from. There are a few companies like
Roxio and Norton that buy other peoples products rather than develop
inhouse. Sometimes, like Roxio, they screw up a good package by having
their programmers take over other's work.

There is one problem with Acronis True Image I have run into when using it
migrate to another disk drive. If the new disk is in the system when the
back is created there is a possibility the swap file will be remembered as
being on the new drive. Then, when the new disk is booted, the swap file is
missing and you cant boot the os. It is solved by booting a dos floppy or
win98 cd and doing the fdisk/mbr number on the boot drive. Gets rid of the
"missing" swap file somehow. Took me a while to dig that info out.
 
Beemer Biker said:
There is one problem with Acronis True Image I have run
into when using it migrate to another disk drive. If the new
disk is in the system when the back is created there is a
possibility the swap file will be remembered as being on
the new drive.

Hmmm.... "new disk is in the system when the back is created".
Well, I assume there is some kind of mis-type there, but it
sounds like the problem wouldn't occur if the newly created
clone is booted for the 1st time with its "parent" out of sight.

*TimDan*
 
Timothy Daniels said:
Hmmm.... "new disk is in the system when the back is created".
Well, I assume there is some kind of mis-type there, but it
sounds like the problem wouldn't occur if the newly created
clone is booted for the 1st time with its "parent" out of sight.

*TimDan*

If the new disk was previously formatted and you boot, windows can assign
the swap file to the new disk. Then, when you make a backup of the OS, the
backup is aware that the 2nd disk is used for the swap file. Later, when
you swap drives and install the OS on the new drive, there is no swap file
any more. The very first time you boot windows on your new disk, it cannot
find the swap file and complains it is missing or corrupt. It will not boot.
You can avoid this by not haveing the new disk drive on the controller when
making the original backup. Re-writing the MBR also fixes the problem. I
dont think this is just an acronis problem. IANE on this but it has
happened 3 times to me using acronis and you cannot boot into safe mode
when it happens. An easy fix is fdisk/mbr from any dos or win98 boot disk.
 
Beemer Biker said:
If the new disk was previously formatted and you boot, windows
can assign the swap file to the new disk. Then, when you make
a backup of the OS, the backup is aware that the 2nd disk is
used for the swap file. Later, when you swap drives and install
the OS on the new drive, there is no swap file any more. The very
first time you boot windows on your new disk, it cannot find the
swap file and complains it is missing or corrupt. It will not boot.
You can avoid this by not haveing the new disk drive on the
controller when making the original backup. Re-writing the MBR
also fixes the problem. I dont think this is just an acronis problem.
IANE on this but it has happened 3 times to me using acronis and
you cannot boot into safe mode when it happens. An easy fix is
fdisk/mbr from any dos or win98 boot disk.


I agree that it isn't an Acronis problem, and why the swap file gets
assigned to the 2nd HD is something I've never heard of. Maybe
the partition on the 1st HD is so full that the OS needs more space
than is available on the 1st HD to provide a swap file of the size
that you have defined for it. If you boot up the OS on the 1st HD
without the 2nd HD connected, does the OS complain about lack
of space for a swap file?

*TimDan*
 
Roxio is a subdivision of Sonic Solutions now, Norton is a part of Symantec;
what other people products they buy? It was Adaptec which has sold some raw
software rights to Roxio initially and it has been RAW software for another
5-6 years or so. Norton products were trusted ones until Symatec purchased
them.

Back to the point: no cloning software includes either swap file (pagefile)
or hibernate file in an image by default. If the cloned disk won't boot it
means the software was used improperly. MBR issue isn't relevant to
pagefile.
 
strapping on his Jets said:
Roxio is a subdivision of Sonic Solutions now, Norton is a part of Symantec;
what other people products they buy? It was Adaptec which has sold some raw
software rights to Roxio initially and it has been RAW software for another
5-6 years or so. Norton products were trusted ones until Symatec purchased
them.

I used the very first CD-R package that adaptec came out with. The
developers parted company and tried to start up their own. They got sued for
property rights by Adaptec who tried to put their much better product of of
business. Easy CD Creater was and has been trash compared to Nero.
Back to the point: no cloning software includes either swap file (pagefile)
or hibernate file in an image by default. If the cloned disk won't boot it
means the software was used improperly. MBR issue isn't relevant to
pagefile.

suggest you google "pagefile mbr" before makeing a claim they are not
relevant
http://tinyurl.com/3r97b
 
I got used to read and understand written text long time before the
Internet. I don't claim, I just inform you that MBR isn't related to any
file unless some pedant would insist that partition table, boot loader code,
and boot sector of active partition are files.
 
Back
Top