WG> Actually I prefer NT not being able to screw up my OS/2 HPFS
WG> partitions. :)  
Then take note of a sad, sad tale.  I had to install NT 3.51 to work
out some problems a client was having. No sweat, says I; I keep a DOS
partition (small) as the primary and 2 logical partitions < 504 meg
for OS diddling.  Clever, no? Well, I installed NT to D:, a logical
partition.  Went on just fine, no real problems.  It DID kill the Boot
Manager as expected, so I figured that all I had to do was make it
bootable again.  Went to the NT disk manager and did so.  WRONG!  DOS
and NT still booted fine, NT could see all the HPFS partitions out to
2.1 gig.  OS/2 would NOT boot.
OK, I was prepared for that.  Tried to restore the backup.  No go:
OS/2 barfed with partition table errors.  OK, boot OS/2 from disk and
reset the partitons.  Still no go.  I finally got the system restored
by using OS/2 (from floppy) to remove all except the primary
partition, re-defined all the partitions and formatted all the logical
partitons (didn't matter whether the D: NT partiton was FAT or HPFS).  I
then re-installed NT - but immediately declared physical drive 0 as OFF
LIMITS to NT's disk manager.  Booted from OS/2 floppies to re-enable
Boot Manager, then installed OS/2.  Everything worked, so I booted the
PSNS (backup recovery disks) and restored the rest of the system from
the network drive it was backed up to.
Long story, but the point is that MS can screw up a disk in a blink. 
KEEP BACKUPS at all times when messing with it, even if it can't SEE
you're logical drives.  Not sure how NT 4 reacts to this but it
couldn't be any better - MS seems to go from BAD to WORSE only.
--- Maximus/2 3.01
1:128/166)
---------------