Products Support > GSX Support FSX/P3D
Couatl64_P3D.exe - Entry Point Not Found **WINDOWS 7 is no longer supported**
achmedfsx:
Just what I did the last hours:
I updated the Visual C++ Redist x86 and x64 to 2015-2022 redist according to website https://docs.microsoft.com/en-us/cpp/windows/latest-supported-vc-redist?view=msvc-170 (support from Vista onwards !).
After the first update (x64), the desktop icons disappeared, so I started the task manager by Ctrl-Alt-Del, started "cmd" from there and rebooted by shutdown /r, all icons were back.
Then I renamed the FSDT folder from yesterday's update and run the FSDT Live Update again.
Now, the error message appears again, but P3D (4.5 HF2) starts, XPOI shows it's arrows and I can order a GSX ground vehicle.
I'm not sure if the Visual C++ Redist update was necessary...
BTW: I have no knowledge of MS Visual, but I checked the library "api-ms-win-downlevel-ole32...dll" with dependency walker.
This dll never had an entry point "GetErrorInfo.". In Win 10, I couldn't find this dll by searching at all, so I think this dll isn't the reason for the error message but just some kind of last resort while searching for the entry point.
I found this entry in the MS documentation for oleauto.h that points to library OleAut32.dll (and other libraries, but the library mentioned in the error message is also related to OLE).
Now OleAut32.dll offers this entry point (Win 7 + 10). OleAut32.dll is further related to Ole32.dll, in tis lib I found the same entry point "GetErrorInfo". So the problem of the missing entry point must go deeper (as the official Win 7 OLE lib offers this entrypoint, assuming GSX is using this one).
Then I found information about similar error messages related to program linkage modes.
https://docs.microsoft.com/en-us/cpp/build/linking-an-executable-to-a-dll?view=msvc-170
I found hints that "entry point not found" could result from a wrong linkage mode.
So just a thougt that one of the GSX updates of the last two weeks brought such a wrong linkage,
maybe with a fixed dll name of Win 10 that is not the same as in Win 7 ?
Just an assumption...
virtuali:
--- Quote from: achmedfsx on February 17, 2022, 10:07:30 pm ---BTW: I have no knowledge of MS Visual, but I checked the library "api-ms-win-downlevel-ole32...dll" with dependency walker. This dll never had an entry point "GetErrorInfo.".
--- End quote ---
I made some research too and, it's entirely normal YOUR version of that dll won't include it. All of your with that error have the api-ms-win-downlevel-ole32-l1-1-0.dll listed of missing that function but, according to this Microsoft page, which specifically discusses Legacy Desktop OS, indicates the GetErrorInfo is supposed to be included in the api-ms-win-downlevel-ole32-l1-1-1.dll
https://docs.microsoft.com/en-us/previous-versions/windows/desktop/legacy/mt588480(v=vs.85)#api-ms-win-downlevel-ole32-l1-1-1dll
As you can see, GetErrorInfo is there. I don't know when this updated version came out and how to obtain it but, as you did, I also checked my whole \Windows folder in Windows 10, and while there is a "Downlevel" subfolder ( both 32 and 64 versions of it ), which contains several .dlls with similar names, THAT specific one isn't there, in any version so, it seems that .DLL is specific to OS older than Windows 10.
Now, it's possible it might belong to Windows 8 or perhaps 8.1, but since when these came out, Windows 7 was STILL fully supported, I would guess it should have been available for Windows 7 as well, during one of the Windows updates, when they were still up.
Today, I can't see how you could possibly get it, other than with a redistributable runtime, which you did and seemed to have improved the situation.
olseric:
--- Quote from: virtuali on February 17, 2022, 12:32:47 pm ---As I've said already, if you run an older installer with the network disconnected, it will work with that version, just you won't be able to UPDATE again so, you would be exactly in the same situation MICROSOFT has already put you 2 years ago: no more Windows Updates for Windows 7 and no more support.
--- End quote ---
Where would we find these older installers cached on our machine? I have the original from when I purchased it, but having a "live update" software pretty much negates the ability for me to go out to your website to download it. Nice feature, don't get me wrong, but eliminates the ability to "roll back" when something goes wrong.
I tried the trick presented by achmedfsx. I still get the error on startup and the GSX application is not loading (no jetways at any "default" airport either which I presume is a function of GSX).
virtuali:
--- Quote from: olseric on February 18, 2022, 05:35:08 pm ---Where would we find these older installers cached on our machine?
--- End quote ---
When you download the installer, at the end of the installation it will ASK YOU if you want to KEEP the installer you just downloaded in the Documents\GSX_Installer folder. The Document folder has been chosen under the assumption ANY user SHOULD do REGULAR Backups of his own Documents folder.
In never had a regular backup strategy, not even for your own Documents folder, that's even more reckless than still using Window 7 in 2022.
--- Quote ---I tried the trick presented by achmedfsx. I still get the error on startup and the GSX application is not loading (no jetways at any "default" airport either which I presume is a function of GSX).
--- End quote ---
You must fix the startup error and, as far as I know, the only way to fix it is getting hold of the updated api-ms-win-downlevel-ole32-l1-1-1.dll, because the function we use must have been moved there, so it's not present anymore in the api-ms-win-downlevel-ole32-l1-1-0.dll you have. This .dll is NOT present in Windows 10, so it must have appeared somewhere as an update to Windows 7.
achmedfsx:
--- Quote from: virtuali on February 17, 2022, 11:53:58 pm ---I made some research too and, it's entirely normal YOUR version of that dll won't include it. All of your with that error have the api-ms-win-downlevel-ole32-l1-1-0.dll
--- End quote ---
Sorry, I don't have much knowledge of the MS Visual environment. But I ask myself if the call has to be done to ms-win-downlevel-ole32 directly. What I understand: you want to get the error object from COM, so you call GetErrorInfo.
But shouldn't this call be done through ole32.dll (this dll contains an entry GetErrorInfo in Win 7: http://www.win7dll.info/oleaut32_dll.html) ? Isn't this the function we talk about: https://docs.microsoft.com/de-de/windows/win32/api/oleauto/nf-oleauto-geterrorinfo?redirectedfrom=MSDN ?
--- Quote from: virtuali on February 17, 2022, 11:53:58 pm ---Now, it's possible it might belong to Windows 8 or perhaps 8.1, but since when these came out, Windows 7 was STILL fully supported, I would guess it should have been available for Windows 7 as well, during one of the Windows updates, when they were still up.
--- End quote ---
If I understand it right (excuse my dumbness), according to https://www.nirsoft.net/dll_information/windows8/combase_dll.html, in Windows 8 the oleaut32.dll exposes GetErrorInfo (too), and imports CoGetErrorInfo from combase.dll.
In my understanding, one has to call oleaut32.dll, from there it goes to combase.dll (Win8).
Is my assumption total nonsense ?
If no, I ask myself why the resolution doesn't find the entry in oleaut32.dll after the update(s) of the last two weeks in Win 7.
Maybe I have to set some kind of a LIBPATH (as in UNIX) ?
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version