G
Guest
Guest
Archived from groups: microsoft.public.windowsxp.hardware (More info?)
I've always run a second drive as a slave - to add extra partitions
for needed space.
I'm adding drive 01 now (80 Gig) -- but I'm a bit confused as I don't
plan on 'intgegrating' it with drive 0 (40 Gig) as I have in the past..
First? I have a bunch of partitions on drive 0: .. C:\ through P:\ not
counting the ROM. (Don't get hung up on that...)
The plan was to 'duplicate' the drive letters for backup (not a mirror)
on the new drive.
However? While I won't be booting to drive 1, I will have a conflict
with the parttions/duplicat drive letters -- No?. I know when I
intitially format/copy the contents over to 1, I can "hide' the
partitions...
But -- how will I be able copy the contents over to drive 1 in the
future (If the partitions are hidden upon setup?) as I with to use it as
backup/storage of drive 0.
Second?
I don't plan on using 'all' of drive 1 as a clone. I'd like to enlarge
the partitions on 2, but leave space for mass storage for media.
So, how do I have a second drive that is a 'clone' (don't the partitions
have to be hidden if they share letters with drive 0? -- meaning I can't
copy 0 over to the second drive)?
So, when I install/format drive 1? How will I force the same
configuration (with larger partitions) without hiding them which will
disallow future use to copy to?
I recall either Drive Copy or PM allows that - I hide the drive letters
of drive 1upon format/copy (which will prevent me from copying to drive 1?!)
This can't be a unique situation -- I just can't wrap my pea brain
around it.
How does run a 'slave' that is a' partial' clone (for backup/storage for
driv 0) and the remainder as 'new' partitions that will interact with
the boot drive?
!!! BTW -- I've always set up the 'slave' as a 'master' on the second
IDE. I currently have a Dell 2400 and the Rom is the master on the
second master -- I believe I have to patch the new drive to the old one
(two IDE ports, one for the HD/One for the ROM. I recall my old box as
having 4 slots for each IDE device?)
Michael
I've always run a second drive as a slave - to add extra partitions
for needed space.
I'm adding drive 01 now (80 Gig) -- but I'm a bit confused as I don't
plan on 'intgegrating' it with drive 0 (40 Gig) as I have in the past..
First? I have a bunch of partitions on drive 0: .. C:\ through P:\ not
counting the ROM. (Don't get hung up on that...)
The plan was to 'duplicate' the drive letters for backup (not a mirror)
on the new drive.
However? While I won't be booting to drive 1, I will have a conflict
with the parttions/duplicat drive letters -- No?. I know when I
intitially format/copy the contents over to 1, I can "hide' the
partitions...
But -- how will I be able copy the contents over to drive 1 in the
future (If the partitions are hidden upon setup?) as I with to use it as
backup/storage of drive 0.
Second?
I don't plan on using 'all' of drive 1 as a clone. I'd like to enlarge
the partitions on 2, but leave space for mass storage for media.
So, how do I have a second drive that is a 'clone' (don't the partitions
have to be hidden if they share letters with drive 0? -- meaning I can't
copy 0 over to the second drive)?
So, when I install/format drive 1? How will I force the same
configuration (with larger partitions) without hiding them which will
disallow future use to copy to?
I recall either Drive Copy or PM allows that - I hide the drive letters
of drive 1upon format/copy (which will prevent me from copying to drive 1?!)
This can't be a unique situation -- I just can't wrap my pea brain
around it.
How does run a 'slave' that is a' partial' clone (for backup/storage for
driv 0) and the remainder as 'new' partitions that will interact with
the boot drive?
!!! BTW -- I've always set up the 'slave' as a 'master' on the second
IDE. I currently have a Dell 2400 and the Rom is the master on the
second master -- I believe I have to patch the new drive to the old one
(two IDE ports, one for the HD/One for the ROM. I recall my old box as
having 4 slots for each IDE device?)
Michael