What's New:
We improved the handling of file paths containing non-ANSI characters.
In the example below, COMMAND.COM is launched in a directory with a Kannada name, and
files with Lao and Tamil names are accessed.
Japanese filenames are recognized as long filenames, while
Lao and Tamil filenames are recognized as short filenames.
File and folder names containing non-ANSI characters
can now be accessed correctly by replacing them with short 8.3-character names.
(Previously, non-ANSI characters were replaced with "?" characters, making them inaccessible.)
However, this does not apply to storage devices that do not support short filenames.
Also, non-ANSI characters in environment variables are not supported.
Please specify ANSI-compatible paths for PATH, TEMP, etc. In
MBCS builds, non-ANSI characters are already replaced with "?" characters in the value returned by _wgetenv().
This appears to occur when the environment variable table for the msdos.exe process is initialized.
If you build it in UNICODE, you can get non-ANSI values with _wgetenv(), but I
don't think it's necessary to go to that extent to support it...