Emulator Issues #6805
closed
Entry Point Not Found crash on Windows Vista
0%
Description
What went wrong?
When launching Dolphin on a Windows Vista machine, Dolphin throws an error "Entry Point Not Found" with the message "The procedure entry point K32GetProcessMemoryInfo could not be located in the dynamic link library KERNEL32.dll.", and then crashes (Dolphin has stopped working, close program). The main window for Dolphin is not displayed before the crash.
What steps will reproduce the problem?
- Launch Dolphin on a Vista installation
Which versions of Dolphin did you test on?
The latest version as of writing, 4.0-330, has this issue.
The first version to experience this issue is 4.0-298.
Which version of Dolphin used to work?
4.0-291 does not have this issue.
What are your PC specifications?
The machine where this issue occurs is:
OS: Windows Vista Home Premium SP2 x86
CPU: Intel Core i7 860 @ 2.93 GHz (no overclocking) [first-generation Core i7, Lynnfield series]
GPU: EVGA NVidia GeForce GTX 560 - 1 GB (no overclocking)
64 or 32 bit Operating System?
32-bit
64 or 32 bit Dolphin?
32-bit
Any other relevant information (e.g. logs, screenshots, configuration
files)
I have tested this issue on a Windows 7 x64 machine on both x64 and x86 versions of Dolphin 4.0-330 and neither have this issue. That machine's specifications are:
OS: Windows 7 Home Premium SP1 x64
CPU: Intel Core i7 740QM @ 1.73 GHz (no overclocking) [first-generation Core i7, Clarksfield series]
GPU: Stock NVidia GeForce GT 330M - 1 GB (no overclocking)
This issue is probably due to the changes in the Visual Studio project files that occured between builds 291 and 298.
Thanks for all the work everyone contributes to Dolphin. Good luck with solving this issue.
Updated by MayImilae over 10 years ago
Issue 6817 has been merged into this issue.
Updated by maartenpeters over 10 years ago
I think that this commit fixes this issue?: https://code.google.com/p/dolphin-emu/source/detail?r=851200eb42f7d1cdc61a72193755bab64c001590&name=DX9-Final#
Updated by mushman5 over 10 years ago
I will be happy to test that revision on the DX9-Final branch, but I will need a build compiled. I don't know how compile it myself.
Updated by mushman5 over 10 years ago
I have tested the latest DX9-Final build (as of writing) posted on the forums (link below) and do not experience the crash.
https://forums.dolphin-emu.org/Thread-unofficial-testing-needed-dx9-final?pid=297809#pid297809
Please merge the appropriate changes into the Master branch. I will be happy to test again if required.
Updated by NeoBrainX over 10 years ago
- Status changed from New to Accepted
- Priority set to Urgent
- Milestone set to Current
- Operating system Windows added
PSAPI_VERSION needs to be defined as 1 in the project files as a compile flag. Defining it in a cpp file isn't good enough since then we'll run into the same issue again once we use PSAPI functions anywhere else.
Source: http://msdn.microsoft.com/en-us/library/windows/desktop/ms683219%28v=vs.85%29.aspx (msdn page for GetProcessMemoryInfo)
"If PSAPI_VERSION is 2 or greater, this function is defined as K32GetProcessMemoryInfo in Psapi.h and exported in Kernel32.lib and Kernel32.dll. If PSAPI_VERSION is 1, this function is defined as GetProcessMemoryInfo in Psapi.h and exported in Psapi.lib and Psapi.dll as a wrapper that calls K32GetProcessMemoryInfo.
Programs that must run on earlier versions of Windows as well as Windows 7 and later versions should always call this function as GetProcessMemoryInfo. To ensure correct resolution of symbols, add Psapi.lib to the TARGETLIBS macro and compile the program with -DPSAPI_VERSION=1. To use run-time dynamic linking, load Psapi.dll."
@ comex, parlane: Should be easy enough to fix.
Updated by maartenpeters over 10 years ago
And I think that the commit from comment 2 fixes this issue (with PSAPI_VERSION.)
Updated by Lioncash over 10 years ago
- Status changed from Accepted to Fixed
This issue was closed by revision 55e8be595ce3.