Products Support > GSX Support FSX/P3D
Couatl64_P3D.exe - Entry Point Not Found **WINDOWS 7 is no longer supported**
virtuali:
--- Quote ---Windows 7 = Good and has about 100 million users.
--- End quote ---
Nobody denies Windows 7 WAS good, it's just way past due its time, and of the 100 millions users, I'm sure they are mostly running older PCs that are not really suited for high-performance "gaming", which is what P3D requires.
And, even if 100 millions users sounds like an high number, it's dwarfed by Windows 10 numbers right now:
https://gs.statcounter.com/os-version-market-share/windows/desktop/worldwide
So yes, Windows 7 WAS good, but all good things ends.
--- Quote from: Broeder Alarm on February 21, 2022, 03:56:23 am ---So far GSX is the only software that is useless for THIS operation systeem.
--- End quote ---
Of the ones YOU tried or YOU are interested in.
We are discussing about P3D right ? Well, you cannot update to P3D V5, for example, because it runs in Windows 10. That's just the first obvious example of something pretty major related to this topic you can't use because you are using a legacy OS.
jimr:
Have been reading this carefully as am also a Windows 7 user with FSX SP2 because i have it running so well i dont want to touch it for as long as i can. For me the most recent GSX update last week installed without issue and walkin gates is working perfectly but fully accept one day i will get caught out.
One advice at the beginning of the thread was to use a previous installer with internet off if i get the error response to a future update.
Excuse my ignorance on this but when i run live update does a copy of that installer remain on my PC and where would it be located? Is it that that i would use to install a previous version?
Thanks.
p.s. walkin gates is fab....been waiting for this for years....many thanks!
achmedfsx:
--- Quote from: virtuali on February 20, 2022, 01:00:02 am ---Of course it fails. You can't modify the exe, it will quit later because it detected it has been tampered with.
--- End quote ---
Seems not to quit here. Did a 2 hours flight yesterday, at P3D start, Couatl complains about being modified maybe by a virus,
I clicked OK on the button in the middle of the window (closing this popup by the X in the upper right disables GSX and XPOI).
Two hours later in LSGG, I called the little car that leads me to the gate.
There I found the marshaller, so it seems, no problem in my environment ?!?.
Or did I miss something ? I don't know much about moving jetways and these things as I fly GA
(my license is GSX, not GSX2, maybe that's the reasing it works in my case ?)
Even if I get the error of the missing GetErrorInfo, P3D comes up and GSX/XPOI work well.
My whole sim installation is outside C:\Program... , maybe that's the reason ?
Now I set all back to the original state.
Moving dll 1.1.1 to the Couatl64_P3D.exe folder and rename to 1.1.0 -> GetErrorInfo not found
Creating a Couatl64_P3D.exe.handle as https://docs.microsoft.com/en-gb/windows/win32/dlls/dynamic-link-library-redirection mentions -> GetErrorInfo not found.
cmd-Window: C:\Windows\System32\CompatTel as first in PATH, then calling Couatl64_P3D -> GetErrorInfo not found
Looking deeper in Couatl64_P3D.exe, I find LoadLibraryA after the lib names (offset ~0016C630):
According to https://docs.microsoft.com/en-us/windows/win32/api/libloaderapi/nf-libloaderapi-loadlibrarya
a lib can be loaded outside the specifications of https://docs.microsoft.com/en-gb/windows/win32/dlls/dynamic-link-library-search-order.
Some bytes before, in the library list, I find "python27.dll".
So it may be python that loads these libs outside of the normal search order ?
https://www.python.org/downloads/windows/ states "Python 3.9.10 cannot be used on Win 7 or earlier",
but python27.dll seems to belong to an older Python version ? Or just a compat lib in Python 3.9.10
BTW: these Api-ms-win-downlevel... libs are hard links (see "fsutil hardlink"), so copying them on the same drive doesn't create a separate instance but a new hardlink.
virtuali:
You are losing your time digging in Couatl.exe. As I've said in my previous post, I already check this and, WE DO NOT CALL GetErrorInfo!
It must be some of the libraries we link with, and it's not Python. We don't use the regular Python, we use Stackless, and it's not the normal interpreter, is our own version, but we haven't changed *ANYTHING* in our code, other than keeping Visual Studio regularly updated.
I also checked the Windows SDK we compiled the program with, and it's not a very new version, it's a version that should support Windows 7 and, again, it hasn't changed in the last version.
So, as I've said, several times by now, I'm fairly sure one of the normal Windows updates that are released, likely the VC++ redistributable runtimes, that caused the requirement of a newer version of the api-ms-win-downlevel-ole32.dll which, again, is NOT included in Windows 10, so there must be a way to install it properly in Windows 7, unless is something in between, maybe for Windows 8, I couldn't find a precise answer on when it came out.
olseric:
--- Quote from: jimr on February 22, 2022, 12:08:34 pm ---Have been reading this carefully as am also a Windows 7 user with FSX SP2
--- End quote ---
This shouldn't affect you. The runtimes being called were inside the 64bit environment (P3D4)...which your sim, FSX, is a 32bit application.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version