Help replacing my C: Drive!

T

Troy Bruder

Hello,

I have a Windows XP machine installed on my 9GB SCSI "C:" drive... This
drive has reached its capacity, and I would like to swap it out with a much
larger 120GB EIDE drive.

Is there any easy way to do this without having to reload everything from
scratch??? I'm afraid if I do a full backup/restore, the restored registry
is going to contain all of the SCSI drivers for booting when I would have an
EIDE at that point...what would happen??

Any advice for me?

Thanks,
Troy
 
C

Colin Barnhorst

If you buy a boxed hard drive, as opposed to OEM (bare) drive, you should
get a cd that runs the manufacturer's software, which includes a utility for
transferring your old hard drives contents onto the new one. It is not just
a file copy program. The new drive will boot your system the same way as
the old one.
 
T

Troy Bruder

But how is that possible? The drivers in the registry won't match.?


Colin Barnhorst said:
If you buy a boxed hard drive, as opposed to OEM (bare) drive, you should
get a cd that runs the manufacturer's software, which includes a utility
for transferring your old hard drives contents onto the new one. It is
not just a file copy program. The new drive will boot your system the
same way as the old one.

--
Colin Barnhorst [MVP Windows - Virtual Machine]
(Reply to the group only unless otherwise requested)
Troy Bruder said:
Hello,

I have a Windows XP machine installed on my 9GB SCSI "C:" drive... This
drive has reached its capacity, and I would like to swap it out with a
much larger 120GB EIDE drive.

Is there any easy way to do this without having to reload everything from
scratch??? I'm afraid if I do a full backup/restore, the restored
registry is going to contain all of the SCSI drivers for booting when I
would have an EIDE at that point...what would happen??

Any advice for me?

Thanks,
Troy
 
C

Colin Barnhorst

It is not a simple copy program. The manufacturer's software knows that you
are transferring the system from your old hard drive to a new one. It
rewrites the hardware abstraction layer along the way. The registry is not
a factor.

--
Colin Barnhorst [MVP Windows - Virtual Machine]
(Reply to the group only unless otherwise requested)
Troy Bruder said:
But how is that possible? The drivers in the registry won't match.?


Colin Barnhorst said:
If you buy a boxed hard drive, as opposed to OEM (bare) drive, you should
get a cd that runs the manufacturer's software, which includes a utility
for transferring your old hard drives contents onto the new one. It is
not just a file copy program. The new drive will boot your system the
same way as the old one.

--
Colin Barnhorst [MVP Windows - Virtual Machine]
(Reply to the group only unless otherwise requested)
Troy Bruder said:
Hello,

I have a Windows XP machine installed on my 9GB SCSI "C:" drive... This
drive has reached its capacity, and I would like to swap it out with a
much larger 120GB EIDE drive.

Is there any easy way to do this without having to reload everything
from scratch??? I'm afraid if I do a full backup/restore, the restored
registry is going to contain all of the SCSI drivers for booting when I
would have an EIDE at that point...what would happen??

Any advice for me?

Thanks,
Troy
 
A

Admiral Q

The "off the shelf disk drive cloning" software, included with the
harddrive, is "not" or "almost guaranteed" not to have drivers needed to
load/recognize a "full blown" SCSI controller and drive - normally the
software provided by manufacturer to clone a drive to their drive is using a
MS-DOS or PC-DOS environment with a NTFS/FAT32 drive file system driver (as
DOS before 7.0 did know about FAT32, and never new about NTFS), which have
"bare bones" IDE controller drivers.
Then assuming the cloning software does recognize the SCSI and IDE
controllers, and the OP can boot and copy - your statement about rewriting
the HAL (Hardware Abstraction Layer) is a completely "false" or untrue
statement. Only a "repair" installation and/or "upgrade" in place will
"rebuild" the HAL to contain the correct drivers for the IDE controller, and
that's assuming WinXP doesn't make the new IDE drive another drive
designator, such as D or E or you get the picture - when that happens there
are literally thousands upon thousands of registry entries pointing to C:,
and now should be D or E or ... A repair and/or upgrade in place install
will fix all the "windows" paths, but not all the other "application
software" with their shortcuts.
The OP should if possible clone the drive, then remove the SCSI drive
along with disabling the SCSI controller, at least temporarily so XP doesn't
see it and hopefully the repair and/or upgrade install will make the IDE
drive C: - then add the SCSI back, enabling the controller and loading the
proper XP drivers, which then the OP can use for data storage or whatever
he/she chooses.

--
Star Fleet Admiral Q @ your service!
"Google is your Friend!"
www.google.com

***********************************************

Colin Barnhorst said:
It is not a simple copy program. The manufacturer's software knows that you
are transferring the system from your old hard drive to a new one. It
rewrites the hardware abstraction layer along the way. The registry is not
a factor.

--
Colin Barnhorst [MVP Windows - Virtual Machine]
(Reply to the group only unless otherwise requested)
Troy Bruder said:
But how is that possible? The drivers in the registry won't match.?


Colin Barnhorst said:
If you buy a boxed hard drive, as opposed to OEM (bare) drive, you should
get a cd that runs the manufacturer's software, which includes a utility
for transferring your old hard drives contents onto the new one. It is
not just a file copy program. The new drive will boot your system the
same way as the old one.

--
Colin Barnhorst [MVP Windows - Virtual Machine]
(Reply to the group only unless otherwise requested)
Hello,

I have a Windows XP machine installed on my 9GB SCSI "C:" drive... This
drive has reached its capacity, and I would like to swap it out with a
much larger 120GB EIDE drive.

Is there any easy way to do this without having to reload everything
from scratch??? I'm afraid if I do a full backup/restore, the restored
registry is going to contain all of the SCSI drivers for booting when I
would have an EIDE at that point...what would happen??

Any advice for me?

Thanks,
Troy
 
A

Admiral Q

This statement:
(as DOS before 7.0 did know about FAT32, and never new about NTFS)

should say:
(as DOS before 7.0 did NOT know about FAT32, and never new about NTFS)

--
Star Fleet Admiral Q @ your service!
"Google is your Friend!"
www.google.com

***********************************************

Admiral Q said:
The "off the shelf disk drive cloning" software, included with the
harddrive, is "not" or "almost guaranteed" not to have drivers needed to
load/recognize a "full blown" SCSI controller and drive - normally the
software provided by manufacturer to clone a drive to their drive is using a
MS-DOS or PC-DOS environment with a NTFS/FAT32 drive file system driver (as
DOS before 7.0 did know about FAT32, and never new about NTFS), which have
"bare bones" IDE controller drivers.
Then assuming the cloning software does recognize the SCSI and IDE
controllers, and the OP can boot and copy - your statement about rewriting
the HAL (Hardware Abstraction Layer) is a completely "false" or untrue
statement. Only a "repair" installation and/or "upgrade" in place will
"rebuild" the HAL to contain the correct drivers for the IDE controller, and
that's assuming WinXP doesn't make the new IDE drive another drive
designator, such as D or E or you get the picture - when that happens there
are literally thousands upon thousands of registry entries pointing to C:,
and now should be D or E or ... A repair and/or upgrade in place install
will fix all the "windows" paths, but not all the other "application
software" with their shortcuts.
The OP should if possible clone the drive, then remove the SCSI drive
along with disabling the SCSI controller, at least temporarily so XP doesn't
see it and hopefully the repair and/or upgrade install will make the IDE
drive C: - then add the SCSI back, enabling the controller and loading the
proper XP drivers, which then the OP can use for data storage or whatever
he/she chooses.

--
Star Fleet Admiral Q @ your service!
"Google is your Friend!"
www.google.com

***********************************************

Colin Barnhorst said:
It is not a simple copy program. The manufacturer's software knows that you
are transferring the system from your old hard drive to a new one. It
rewrites the hardware abstraction layer along the way. The registry is not
a factor.

--
Colin Barnhorst [MVP Windows - Virtual Machine]
(Reply to the group only unless otherwise requested)
Troy Bruder said:
But how is that possible? The drivers in the registry won't match.?


If you buy a boxed hard drive, as opposed to OEM (bare) drive, you should
get a cd that runs the manufacturer's software, which includes a utility
for transferring your old hard drives contents onto the new one. It is
not just a file copy program. The new drive will boot your system the
same way as the old one.

--
Colin Barnhorst [MVP Windows - Virtual Machine]
(Reply to the group only unless otherwise requested)
Hello,

I have a Windows XP machine installed on my 9GB SCSI "C:" drive... This
drive has reached its capacity, and I would like to swap it out with a
much larger 120GB EIDE drive.

Is there any easy way to do this without having to reload everything
from scratch??? I'm afraid if I do a full backup/restore, the restored
registry is going to contain all of the SCSI drivers for booting
when
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top