Can incorrect HD jumper settings cause corruption??

Nodsu.... I just tried that now... neither OS can mount the drive. But NT4 happily reads the drive as if it were an ordinary file system.

There must be a more direct way to know what the file system is. Isn't there a utility out there that can tell me this?

Or is there a command (or GUI action) in NT that will reveal the filesystem?

OK, Nodsu, I finally have a real explanation for this mystery....

What is true in fact is that the file format IS indeed NTFS, however the whole drive is an extension of a Volume started on the first physical disk. That first disk has two partitions, one FAT 16 (#1) and one NTFS (#2). The NTFS (#2) partition is the first part of logical drive D: and the whole second physical drive is the rest of drive D:.

The second physical drive is the one that could not be read outside of its home on the NT4 machine. I suppose that there is a reason that the "Partition Type" byte in the partition table is not 07 for NTFS (it is 05) and that the reason has something to do with the drive being part of an Extended Volume Set. But I'm not sure how it works/why it is that way. Maybe you can tell me.

But in any case, when the drive is married to it's mate on the NT4 system, the OS has enough info to be able to read everything fine. And when the drive is separated from that necessary info (almost certainly on the first drive) then the Format Type has no meaning to the OS that's trying to read it. So apparently the OS then declares the drive space "Unformatted".

Any thoughts/comments, anyone??