13 Dec
2011
13 Dec
'11
2:39 p.m.
On 13 Dec 2011 at 14:20, Fred Cisin wrote:
Since we are talking about the ACTUAL filenames, as
present in the
disk DIRectory and as used in the File Control Blocks in memory, as
opposed to the REPRESENTATIONS used in communication with the user by
the CLI (which resulted in some well-intentioned person thinking that
I had gotten the structure wrong), it is certainly easy to break many
of the "rules" of the DOS filenames, at the risk of "undefined" (but
FUN) results.
Some people are surprised to find that creating a DOS file name using
hex E5 characters is perfectly legit (DOS changes them to 05 hex).
In the bad old CP/M days, characters in filenames were pretty much
policed only by the CLI/CCP. A program could create a file named
with almost anything in it, including control characters (backspace
is fun).
But even today, I'm surprised by some Windows utilities that will
choke on a filename made up of Cyrillic characters, for example--or
not know how to display it.
--Chuck