Attachment uploads are currently disabled. This is a temporary situation and will resume as normal in the coming days.
UNSOLVED
Migration
Ok, this is my strategy as I await my new machine..A Dell 2400, P-4.
I currently have a failed machine...though I assume it is not a drive problem. (trust me).
Thus I will need to migrate the following setup to a single 40 gig drive.
HD0
c:\ 200 meg Dos FAT16 Primary partition
D:\2 Gig Applications
E:\ 2 Gig W2k will not migrate (WXP will fill that "new" partition)
Hidden partition---2 gig---old NT Server---nuttin' of value
Hd1
F:\Primary 2 gig W2k
G:\ 2 gig applications
H:\ 2 gig---nearly empty
I:\ CD rom
J:\ 2 gig applications
L:\ 2 gig application
M:\ 2 gig application
N:\ 2 gig applications
O:\ 2 gig applications
P:\ 2 gig empty
All but C:\ are FAT32
Whew!
The plan is to boot up the new system (40 gig) and look around. See whats what, but I will soon turn the lights out and make my move
My first move is to re-format and repartition. That is, I will need to create a small C:\ for Dos.
I would like to\must? duplicate the above partition sequence that is spread between a 6 gig and 20 gig drives on my new 40 gig drive. Of course the partitions will be larger---(I could easily combine O:\ and P:\ into one.)
Here is where I have a choice
Plan A: Using drive copy, from dos, and each of the "old" drives attqched as the secondary drive...copy the partitions into the new partitions I've created (again, in DOS).
As I will not be moving the W2k install from hd0---I will have XP there. Both as a place holder to keep the drive sequence intact but I have always had two installs of Windows.
Yes, I realize migrating W2k to a new system, new drive (not hd1, not a primary) will test the ability of W2k to repair and adjust to it's new home. I am aware it may not boot, may require a clean install....
However, I have scores of apps associated with it and do not relish the idea of re-installing them and also reconfiguring them. I have to try the move/repair and give it a shot.
So, my eyes are open...If it doesn't adapt...well, I have a job after the clean install.
Am I missing anything?
Plan B: I considered an (sort of) inplace fix of the OS---that is, rather than using Drive Copy in Dos with each drive as a slave--(moving data to the new drive and *then* running repair on the new drive after the media has moved)?
I could hook up each "old" drive directly to the new box, and run repair on them BEFORE I move the data---(and if they boot)--then hide them, replace my new drive and do the Drive Copy.
Is there any difference between the two plans other (than that which I will get to?)
That is, does it matter whether I "repair" Win2k after I move it (and the contents of the drives) to the new drive---versus, running "repair" on each drive (with the new drive out)---then moving the "repaired" (we hope) media to the new drive?
Plan B, upgrading\repair of W2k *before* moving to the new drive didn't occur to me--I figured it was at best not necessary...Plus, since W2k is on hd1--even if I am able to run repair so that it adapts to the new system --- well, I'll be looking to do the same thing again---as after it moves, it will longer be on hd1--I will have to run repair again.
So, while I thought plan B would require duplication of effort (repair of W2k before and after it moves)---is there any advantage to upgrading the drives "before" I copy the contents to the new drive.
Other than a clean install---which I may end up doing...is there a better plan to get two drives worth of data into one drive--- with a dead OS?
Michael
I currently have a failed machine...though I assume it is not a drive problem. (trust me).
Thus I will need to migrate the following setup to a single 40 gig drive.
HD0
c:\ 200 meg Dos FAT16 Primary partition
D:\2 Gig Applications
E:\ 2 Gig W2k will not migrate (WXP will fill that "new" partition)
Hidden partition---2 gig---old NT Server---nuttin' of value
Hd1
F:\Primary 2 gig W2k
G:\ 2 gig applications
H:\ 2 gig---nearly empty
I:\ CD rom
J:\ 2 gig applications
L:\ 2 gig application
M:\ 2 gig application
N:\ 2 gig applications
O:\ 2 gig applications
P:\ 2 gig empty
All but C:\ are FAT32
Whew!
The plan is to boot up the new system (40 gig) and look around. See whats what, but I will soon turn the lights out and make my move
My first move is to re-format and repartition. That is, I will need to create a small C:\ for Dos.
I would like to\must? duplicate the above partition sequence that is spread between a 6 gig and 20 gig drives on my new 40 gig drive. Of course the partitions will be larger---(I could easily combine O:\ and P:\ into one.)
Here is where I have a choice
Plan A: Using drive copy, from dos, and each of the "old" drives attqched as the secondary drive...copy the partitions into the new partitions I've created (again, in DOS).
As I will not be moving the W2k install from hd0---I will have XP there. Both as a place holder to keep the drive sequence intact but I have always had two installs of Windows.
Yes, I realize migrating W2k to a new system, new drive (not hd1, not a primary) will test the ability of W2k to repair and adjust to it's new home. I am aware it may not boot, may require a clean install....
However, I have scores of apps associated with it and do not relish the idea of re-installing them and also reconfiguring them. I have to try the move/repair and give it a shot.
So, my eyes are open...If it doesn't adapt...well, I have a job after the clean install.
Am I missing anything?
Plan B: I considered an (sort of) inplace fix of the OS---that is, rather than using Drive Copy in Dos with each drive as a slave--(moving data to the new drive and *then* running repair on the new drive after the media has moved)?
I could hook up each "old" drive directly to the new box, and run repair on them BEFORE I move the data---(and if they boot)--then hide them, replace my new drive and do the Drive Copy.
Is there any difference between the two plans other (than that which I will get to?)
That is, does it matter whether I "repair" Win2k after I move it (and the contents of the drives) to the new drive---versus, running "repair" on each drive (with the new drive out)---then moving the "repaired" (we hope) media to the new drive?
Plan B, upgrading\repair of W2k *before* moving to the new drive didn't occur to me--I figured it was at best not necessary...Plus, since W2k is on hd1--even if I am able to run repair so that it adapts to the new system --- well, I'll be looking to do the same thing again---as after it moves, it will longer be on hd1--I will have to run repair again.
So, while I thought plan B would require duplication of effort (repair of W2k before and after it moves)---is there any advantage to upgrading the drives "before" I copy the contents to the new drive.
Other than a clean install---which I may end up doing...is there a better plan to get two drives worth of data into one drive--- with a dead OS?
Michael
- (I use the term "repair" as MS defines it...It is probably necessary for one to understand that, first?)
Sorry, my post was rather complicated--then so is my system.
But I believe my description was comprehensive?
Line four said "...I will need to migrate the following setup to a single 40 gig drive." No, the setup is not standard.
Yes, I currently have a DOS partition and run W2k.
(Two specific MS Knowledge Base articles, 249694 and 824125, deal with the repair of W2k as concerns the migration and/or a change of system.)
No, not only do I not believe Dos is dead---it is very useful and I will have a primary, FAT16 partiton in my new drive...
It is possible for W2k (and associated applications) to be "repaired" and thus "cloned" to a new drive/partition (done that) and yes, a new system.
Yes, I will boot to multiple OS's...not relevent...boot.ini is quite managable...
My only remaining issue?
1. Should I preform the "repair" on each "old" drive, in the new environment (directly conntected to the new OS. Then move the data to the new drive)
OR
2. Should I (simply) copy (via Drive Copy in DOS) the data (as is) to the new drives---THEN preform the repair.
Again, a new machine (or drive or hardware) does not in anyway infer, imply let alone require one abandon one's operating system or applications. (or require the re-installation of either or both)
Yes, the repair of W2k is complex (been there--done it) and it isn't guaranteed to work. SP-4 and IE6 will probably need to be reinstalled (in my experience).
However, compared to re-installing The OS and scores of applications and reconfiguring each of them after a reinstall? The Knowledge Base (plan) is well worth the effort to avoid that.
Again--simple question?
Repair current setup (in new environment) before copy to new drive or, copy to new drive and then perform repair.
I outlined advantages/disadvantages for both in my first post---am I missing anything?
osprey4
6 Operator
•
34230 Posts
139
0
Posted September 13th, 2004 21:00
In theory, it should be possible to move a drive from an old machine into a new 2400 running XP, and the drive will be properly read. Then you can copy data to your new computer. However, you cannot copy applications. They must be reinstalled. Utilizing NTFS, there is no need for all of these partitions, although some people like to maintain a separate data partition for ease of data backup. Windows XP does not have DOS, as such, so running anything in DOS will not be possible.
If this does not address your issues, please post back and explain your objective. Are you trying to dual boot the new machine?