search for: tahx6k

...but all of the names are shown in the 8.3 format and are almost unreadable. I discovered that the filenames in question have full colons (:) in them, and this is illegal for Windows clients. Windows itself won't let you create a file with an invalid filename. I have listings like: T7UFO1~9 --TAHX6K~4.txt --TAHX6K~B.ods etc. I was browsing around in smb.conf's man page looking for a way for these files to at least be readable. Is there a way to map all of the invalid characters in Windows that linux can use so they simply appear as a hyphen (or another character?) It would be so much eas...