> I think you will find that the space probably became chr$(255) if I
> remember correctly. I believe some of the OS/2 rule breaking files are
> also char 255. (Maybe it was 128... I cant even remember what space is
> off hand, but I do remember that these tended to be something NOT
No, you really don't need that. DOS itself (and now I mean the interrupt
routines that handle file requests, on int 0x21), allows spaces in filenames.
Not dots, and some other characters, though, as someone was trying to suggest
in some preceding mails. It also translates some accented charatcers to their
unaccented versions, but not all - probably only those present in the IBM
charset. It also translates the 'sigma' sign into something else, so that
you can have a filename starting with 'sigma', even though the 'sigma' would
normally mark a deleted file. And so on ...
However, a space is just a normal character for these functions. They
can operate with it without problems.
Not command.com, though - it uses space as an argument delimiter. And, about the
character 255 trick - yes, that could be done as well, but it's a different
story, though.
Vojtech
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/