I very much appreciate your response and I understand your argument about ntfs r/w but I'm like an old dog that got burnt from touching its nose to the stove. I've had to reinstall too many Windows OSs starting with WinNT3.5 because of file corruption, some of them caused by ntfs-3g back when it was classified as "experimental" ( which wasn't that long ago ). I realize that was then and this is now but I'm just stubborn
This is how I "fixed" my fstab entry in case anyone else wishes to wast some time in fstab and possibly ruin their system
Original: UUID=DA9056C19056A3B3 /media/WinXP ntfs defaults,nls=utf8,umask=0222 0 1
New: LABEL=WinXP /windows/C ntfs umask=0222,ro 0 0
(1) UUID's drive me crazy so I use "LABEL=" to id partitions in fstab
( Had to do it anyway since I have 2 partitions with the same UUID - that's a long story )
(2) The "ro" is probably redundant given my umask but I did it anyway.
(3) The very last number in the original entry dictates when and if a filesystem check and possible repair is done at boot time on that partition. If you had write access to the partition I suppose that would make sense but since I now only have read access I disabled it by setting it to 0. Don't care very much for one filesystem doing a check on another filesystem when one of them is Microsoft's.
I'm sure I left off a utf-8 parameter or something somewhere along the way but this is working so far and I'm ready to make adjustments if necessary.
I do apologize for what's basically turned into a rant but it just "threw" me a little that "ntfs" is now "ntfs-3g".