PRB: OpenFile Does Not Work Well with SetFileAPIsToOEM

Last reviewed: September 25, 1995
Article ID: Q137201

The information in this article applies to:

Microsoft Win32 Application Programming Interface (API) included with:
```
    - Microsoft Windows 95 version 4.0
```

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 reference words: 4.00 Windows 95
KBCategory: kbprg kbprb
KBSubcategory: BseFileio

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: September 25, 1995
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.