>I wouldn't necessarily say inconsistent use of case as a fault of the OS, but rather a symptom of leniency offered by case-insenstive filesystem. True, you probably won't run into this sort of "quirkiness" from Unix-based software -- mainly because you're *forced* to keep consistent with case because the filesystem is case-sensitive. The case-senstiive nature of Unix filesystem has also been a source of frustration for many folks -- especially if they had gotten used to systems where filenames were not case-sensitive. On the other hand, folks who had gotten used to case-sensitve filenames aren't so irritated (save for the fact that you can't have both an upper and lower-case versions of the filename simultaneously -- though this is only a minor issue as having name that only differ in case is considered bad form anyway).

I've never had to work enough on a Unix system for this to be an issue, but anyone that considers a change in case on a filename to be a different file is running on the ragged edge of sanity... and why should I have to use the same letter casing logic as the file creator to be able to access the content or even find the dang thing in the directory system?

Do I mix case my filenames in Windows when I create them? Yes I do, I think it makes them more readable. Do I expect to have to type the exact same case every time I want the file? No, I don't.

>Of course there's the question if the feelings of any letters are being hurt by Windows because it is being insensitive to them...

It's not insensitive... it just simply doesn't discriminate one case over the other. *g*