Microsoft KB Archive/137201

{|
 * width="100%"|

PRB: OpenFile Does Not Work Well with SetFileAPIsToOEM

 * }

Q137201

-

The information in this article applies to:


 * Microsoft Win32 Application Programming Interface (API), included with:
 * Microsoft Windows 4.0
 * Microsoft Windows 95

-

SYMPTOMS
After you call SetFileApisToOEM, OpenFile is supposed to accept OEM strings for file manipulation. However, giving OpenFile an extended character produces an unexpected filename. For example, with char 190, the filename contains a '+' instead of the expected character.

CAUSE
OpenFile converts the given OEM string internally to ANSI before manipulating the filename or passing it down to the filesystem. This conversion is not always successful, as not all OEM chars have equivalents in the ANSI set.

RESOLUTION
Use Createfile to open the file. CreateFile does not convert OEM to ANSI, so this problem does not occur.

STATUS
This behavior is by design.

Additional query words: 4.00 Windows win95fest

Keywords :

Issue type :

Technology : kbAudDeveloper kbWin32sSearch kbWin32API