N
nusrat
i'm running w2k-pro on a corporate win-server network, in a company where
it's not unusual for your desktop system to be down or crippled for days
because of some software change which was forcibly "pushed" to your machine
remotely by the Network/PC Support department.
i'd like to know a procedure to:
(a) re-partition my 256gig IDE HD -- in-place -- into 2 equal parts
(b) be able to use the second partition as a bootable hot-backup,
on which i *manually* control which changes on the "normal"
boot-part get replicated to the backup -- not just by date/time range,
but also by specifying specific folders/files to be omitted/included
(c) be able to boot and run from the second part,
with ALL code thinking that the booted partition
is addressed as "c:\" -- including the Support department's
network logon scripts which run at boot-time.
(d) still be able to access both partitions,
no matter which one i've booted from.
-- opening the PC's case isn't an option.
-- the drive currently has only one partition, a full-drive primary,
i.e. with no "extended"/"logical" partitions.
-- i'm not concerned about my non-system win .lnk files
being made "stale" due to drive-letter changes
-- i don't mind if the solution involves creating a third partition
which must be booted briefly to "fix"/hack something on the
other partition(s) before switching between backup & "normal" mode.
-- the bios set-up screen on this machine (a late-model dell)
allows switching the order of devices used to attempt booting.
i'd also like to ask how the solution would be different
if i were using two separate IDE drives.
tia,
kate
it's not unusual for your desktop system to be down or crippled for days
because of some software change which was forcibly "pushed" to your machine
remotely by the Network/PC Support department.
i'd like to know a procedure to:
(a) re-partition my 256gig IDE HD -- in-place -- into 2 equal parts
(b) be able to use the second partition as a bootable hot-backup,
on which i *manually* control which changes on the "normal"
boot-part get replicated to the backup -- not just by date/time range,
but also by specifying specific folders/files to be omitted/included
(c) be able to boot and run from the second part,
with ALL code thinking that the booted partition
is addressed as "c:\" -- including the Support department's
network logon scripts which run at boot-time.
(d) still be able to access both partitions,
no matter which one i've booted from.
-- opening the PC's case isn't an option.
-- the drive currently has only one partition, a full-drive primary,
i.e. with no "extended"/"logical" partitions.
-- i'm not concerned about my non-system win .lnk files
being made "stale" due to drive-letter changes
-- i don't mind if the solution involves creating a third partition
which must be booted briefly to "fix"/hack something on the
other partition(s) before switching between backup & "normal" mode.
-- the bios set-up screen on this machine (a late-model dell)
allows switching the order of devices used to attempt booting.
i'd also like to ask how the solution would be different
if i were using two separate IDE drives.
tia,
kate