When you have a FAT32 volume and if the power goes off, when the computer boots, check disk runs. But not if you have a NTFS Volume. Why is that? Does this mean that no problems might occur to NTFS when that happens?

Why is it bad to have two partitions in FAT32 and NTFS on a same drive?

Problems might occur, indeed. At least according to Murphy.

NTFS is a journalising (it keeps a log) file-system. If the log and it's current state doesn't match upon reboot the filesystem perform a check and undo any failed changes, thus bringing the filesystem back to last consistent state. This goes pretty fast and there is no need to check the whole MFT/partition/drive.

The second question beets me. Why should that be bad? I have always mixed different filesystems according to my needs. If you plan carefully there are no drawbacks. To avoid unpleasent surprises you have to do some thinking though. Not all os's accept filesystems placed by random, or you might get unpractical drive letters.

All my computers (well, in the house - used by my family) have their C:\ formatted in FAT16. Then there is a mix of different partitions formatted in FAT32, NTFS and ext2fs, swap-formats and also other temporary stuff. The main computer have three harddrives, a total of 12 partitions formatted in four different formats (for the moment).

Feel free to ask about opinions in this question - I'm sure you will get some different ideeas and opinions in return.... :)

Well like he said the main "bad" thing about having NTFS and FAT32 on the same drive is that not all OS's can read the same filling system. For example if you install WinXP with NTFS then windows 98 with FAT32 (Does not support NTFS) windows 98 wont be able to read the NTFS system. However, I have heard of ideas around this so its not really all that "bad".

cya,
Will

PS: Thats just the basics. Newbie style. :)

Exactly what I was wondering :huh: :o
Don't have clue...Windows 2000/XP does NOT scan the hard disk under NTFS for an invalid shut down, but does for a FAT32 :o

.uncorn answered well: NTFS is a journalising (it keeps a log) file-system. If the log and it's current state doesn't match upon reboot the filesystem perform a check and undo any failed changes, thus bringing the filesystem back to last consistent state. This goes pretty fast and there is no need to check the whole MFT/partition/drive. :) Thanks!!

For the second question:
Different file systems can coexist on the same computer or even the same hard drive. When this is the case it is important to remember that the two disks, or partitions, do not "access" each other or communicate with each other in any way. There is no such thing as one file system being "compatible" with another file system. All reading and writing operations are handled by the operating system, NOT the file system. All a file system does is organize the data on the disk. In some cases, such as with NTFS, the file system may offer security, encryption, or other features. However the operating system is still responsible for interpreting the information stored on the partition or disk no matter what file system is used. :)

A friend of mine told me that if you have FAT32 and NTFS in two partitions in the same hard drive. if the system restarts due to a fault (let's say a power failure), the chance of getting bad sectors on the hard drive is high. I don't know how this happens and even he doesn't know. He had heard if from someone else.

Is this theoritical or just a myth? If anyone knows, let me know.

And thanks for your help, guys.

I "know" only from personal experience.
I have run computers with mixed filesystems (and always had different partitions with different filesystems as drive no 1) for years. Or at least since I laid my hands on NT 3.5.
The number of faulty shutdowns due to my mistakes, blue screens, games (my sons played a lot for some years), and maybe even a rare power failure is high. But I haven't noticed any exceptional losses. Neither have I noticed problems with bad sectors.

To conclude: *To me* this seems as a myth or maybe some other problem with drivers/cables/drives that has been taken for filesystem problems.