Windows implements CreateFileA as a wrapper around CreateFileW.In effect, it calls CreateFileA instead of CreateFileW. Unfortunately, when trying to create the HAXM VM device node, emulator stores the path name ( \\.\hax_vm00) in an ANSI string, and passes it to CreateFile. CreateFileW, which only accepts Unicode strings ( wchar_t * or LPWSTR). Instead, it should always use the Unicode variant of that API, e.g. CreateFileA or even CreateFile, which maps to CreateFileA when the string parameter is of type char *. If a Windows application is fully Unicode-aware, it should never call a Windows API function that takes an ANSI string ( char * or LPSTR), e.g. In short, this could be due to a flaw in emulator.exe's support for Unicode.
Mac emulator: failed to initialize hax: invalid argument driver#
OK, it looks increasingly likely that this is an Android Emulator/QEMU bug, not a HAXM driver bug.
0 kommentar(er)
