Complicated question about new HD

[chris h]

I'm buying a new HD and this is what I want to do (in summary, explanations
below):

1) Install new HD in current computer running windows 2000, call it "C:"

2) Old "C:" should be called "D:" but it will remain as the drive with the
operating system

3) Copy everything from old drive to new drive except operating system; work
for one month with this configuration

4) On a new computer, operating system unknow but probably XP, install the
new hard drive as "C:" and install the operating system on it *without
losing its files*!

Can I do that and how? Basically I'm moving out in about 2 months and I want
to take everything with me. I have some programs that are 'device
dependent', that's why I want to keep 'C:' for the new hard drive.

And while we're at it, what is the best (fast/reliable) 250GB+ harde drive
under $300?

Thanks!

 

[Rod Speed]

I'm buying a new HD and this is what I want
to do (in summary, explanations below):

1) Install new HD in current computer
running windows 2000, call it "C:"

2) Old "C:" should be called "D:" but it will
remain as the drive with the operating system

3) Copy everything from old drive to new drive except
operating system; work for one month with this configuration

4) On a new computer, operating system unknow but
probably XP, install the new hard drive as "C:" and install
the operating system on it *without losing its files*!

Can I do that

Sort of, but you're going about it the wrong way.

and how? Basically I'm moving out in about 2 months and I want
to take everything with me. I have some programs that are 'device
dependent', that's why I want to keep 'C:' for the new hard drive.

Your approach basically wont work, particularly the initial
use of the new drive in the old system as the C drive.
Those programs that are drive letter dependant wont work
from the C drive with the OS now on the D drive if they are
modern programs which have entrys in the registry.

It would be better to not bother with using the new drive
in the old system for the last 2 months. When you are
about to move out, just clone the current C drive to the
new drive and temporarily leave the old C drive unplugged.
Install whatever OS you decide to use over the current
Win2K install, in the old system. Now take the new drive
out of the old system and put it in the new system. You
can now connect the original C drive again in the old system.

You'll likely find that you do have to do a repair of the
installation on the new drive in the new system, if the
hardware is significantly different to the old system.

And while we're at it, what is the best
(fast/reliable) 250GB+ harde drive under $300?

I like the WD drives for that size. I prefer the Samsungs
now but currently they dont have a 250GB drive.

 

[J.Clarke]

I'm buying a new HD and this is what I want to do (in summary,
explanations below):

1) Install new HD in current computer running windows 2000, call it
"C:"

2) Old "C:" should be called "D:" but it will remain as the drive with
the operating system

3) Copy everything from old drive to new drive except operating
system; work for one month with this configuration

4) On a new computer, operating system unknow but probably XP, install
the new hard drive as "C:" and install the operating system on it
*without losing its files*!

Can I do that and how? Basically I'm moving out in about 2 months and
I want to take everything with me. I have some programs that are
'device dependent', that's why I want to keep 'C:' for the new hard
drive.

And while we're at it, what is the best (fast/reliable) 250GB+ harde
drive under $300?

Trying to run an operating system that was installed on drive C off of
Drive D, while it can be made to work with much effort, is going to
waste far more time than it saves over making an image copy or
doing a ground-up reinstall unless there's some special circumstance you
haven't told us about. If you want to do it to learn how you'll find it
a fascinating and frustrating exercise. If you actually need to use the
machine to get work done then it's a Bad Idea.

There aren't that many 250 gig drives, and any of them should be decent
if they have adequate cooling and clean power.

 

[Lil' Dave]

There's more to program installations that just the files themselves. Some
of these files are application specific system files interdispersed with
windows system files in the windows directory and some subdirectories.
There are application specific "ini" files, and application specific
registry entries. Device dependent applications may also supply device
drivers as well.... So what is it you're going to keep as far as files?
Dave

 

[chris h]

There's more to program installations that just the files themselves. Some
of these files are application specific system files interdispersed with
windows system files in the windows directory and some subdirectories.
There are application specific "ini" files, and application specific
registry entries. Device dependent applications may also supply device
drivers as well.... So what is it you're going to keep as far as files?
Dave

They are my own C++ projects, I was just lazy enough to use the actual path
and now I regret it
I have tons of projects and several versions. I could change them all, and I
may even do it if necessary,
but still...

 

[J.Clarke]

They are my own C++ projects, I was just lazy enough to use the actual
path and now I regret it
I have tons of projects and several versions. I could change them all,
and I may even do it if necessary,
but still...

If you go through the registry you'll find that a lot of commercial
applications also use the actual path--it may not be hard-wired in the
code but you'll still have to find and change every registry entry. If
that was all you had to do then life would be good, but there are also
links, configuration files, and so on that have to be found and changed
manually.