isolation of 2 installations

  • Thread starter Thread starter kostas
  • Start date Start date
K

kostas

Hello there

Is there a way to isolate 2 windows 2000 partitions?

For example, I have 2 disks with 1 installation each and I want the
first installation not able to see the second one but the second must
see the first. ? must do it with a program not physically by
disconnecting each disk at a time

Thanks
 
boot commander will resolve your issues.
although as soon as you boot one os, it will see the
second disk. no matter which one is booted.
 
kostas said:
Is there a way to isolate 2 windows 2000 partitions?

For example, I have 2 disks with 1 installation each and I
want the first installation not able to see the second one but
the second must see the first. ? must do it with a program
not physically by disconnecting each disk at a time
Click to expand...

Any decent boot manager (which doesn't include Microsoft's NT/2K/XP boot
loader) can handle that easily. How invisible do you want the alternate
partition to be?

Routine third-party boot managers like XOSL, GAG, and BootMagic can mark
alternate partitions hidden/unhidden depending on which partition is
booted -- W2Ka can boot with W2Kb accessible, while W2Kb boots with W2Ka
hidden. However, "hidden" doesn't mean it's totally invisible -- W2K
will know the other partition is there, but won't give it a drive letter
and can't read any files on it. Normally, this should be enough.

BootIt NG, Ranish Partition Manager, and System Commander can do that,
too, but also have an optional proprietary mode with which they can even
make the inaccessible partition appear to be unallocated, unpartitioned
space, hiding its contents even deeper. The downside, however, is that
the proprietary handling means you have to swear off using other
partition management tools (for example, you can't subsequently use
PartitionMagic, fdisk, or W2K's native disk management tools because
they'll think the hidden space really is unallocated). Normally, you
shouldn't need to hide a partition this deeply unless you're hiding from
a technician the fact that you have a dormant partition there.
 
Very nice writeup! Thanks -

I'm Dan said:
Any decent boot manager (which doesn't include Microsoft's NT/2K/XP boot
loader) can handle that easily. How invisible do you want the alternate
partition to be?

Routine third-party boot managers like XOSL, GAG, and BootMagic can mark
alternate partitions hidden/unhidden depending on which partition is
booted -- W2Ka can boot with W2Kb accessible, while W2Kb boots with W2Ka
hidden. However, "hidden" doesn't mean it's totally invisible -- W2K
will know the other partition is there, but won't give it a drive letter
and can't read any files on it. Normally, this should be enough.

BootIt NG, Ranish Partition Manager, and System Commander can do that,
too, but also have an optional proprietary mode with which they can even
make the inaccessible partition appear to be unallocated, unpartitioned
space, hiding its contents even deeper. The downside, however, is that
the proprietary handling means you have to swear off using other
partition management tools (for example, you can't subsequently use
PartitionMagic, fdisk, or W2K's native disk management tools because
they'll think the hidden space really is unallocated). Normally, you
shouldn't need to hide a partition this deeply unless you're hiding from
a technician the fact that you have a dormant partition there.
Click to expand...
 
Back
Top