Yeah, pretty much what R.a.B.B.i.T said.
Also, that's not *exactly* true, I've had the command prompt window bitch at me for not having "Documents and Settings" capitalized like that, for some reason.
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\>cd docuMENTS and SeTTinGS
C:\Documents and Settings>cd ../DOCUMENTS AND SETTINGS
C:\Documents and Settings>
I suspect you were using a command that had more than one parameter, like copy:
C:\>echo "" > "Documents and Settings\test.txt"
C:\>dir Documents
Volume in drive C has no label.
Volume Serial Number is D424-0774
Directory of C:\
01/27/2006 07:31 PM 28 Documents
1 File(s) 28 bytes
0 Dir(s) 12,835,221,504 bytes free
C:\>echo "" > "Documents and Settings\test.txt"
C:\>dir Documents and Settings\test.txt
The system cannot find the file specified.
C:\>dir "Documents and Settings\test.txt"
Volume in drive C has no label.
Volume Serial Number is D424-0774
Directory of C:\Documents and Settings
01/27/2006 07:32 PM 5 test.txt
1 File(s) 5 bytes
0 Dir(s) 12,835,221,504 bytes free
As you can see, unless you enclose a directory that contains spaces in quotes, it is truncated after the first space. I highly suspect that's the reason you were having issues with 'casing.'
By default, NTFS is totally non-case sensitive. It was weird seeing files with the same file and different casing when I first set up samba on my server.