Iwas dumb enough to get a GFWL-encumbered game (and GFWL is down). I found some project called XLiveLess that aims to re-implement XLive.dll as a stub that does only minimal job that's necessary to run the game.
When I've placed pre-built DLL all I've got is "The ordinal 29 could not be located in the dynamic link library" error. So I've ran a debugger to find the call to that export, deduced the signature, added appropriate code to .cpp and .def files and built the library. Now, after updating the DLL, I'm still getting the same error, but dumpbin /exports xlive.dll clearly shows me that #29 is exported - there's a line 29 000024A0 [NONAME] in the output.
I'm also certain my self-built library is the exact xlive.dll game's accessing - if I remove the binary it starts complaining that DLL's missing. If that matters, I'm currently running this under Windows 8.0 x86_64.
Now I'm lost and confused, and I'm not experienced with Windows programming (did some 15 years ago but forgot almost everything since then). What could be possible causes loader still not finding the exported function, even though it's right there? Am I missing something?
Fallout 4 is an old game but it still has many followers. But lots of Fallout 3 players into an ordinal 43 error. Why does this issue appear? How to get rid of the error? In this post, MiniTool explains the reasons and displays 4 feasible solutions.
The DLL file is missing or corrupted: the error message suggests that the xlive.dll file is missing or corrupted. If that is in the case, you can download the file and place it in the game installation folder.
Fallout 3 is cannot work fine with the new versions of Windows: Fallout 3 was released in 2008. 12 years have passed by and the game is too old to work well on the new operating system.
If the above solution fails to help you get rid of Fallout 3 ordinal 43 error, you should replace the DLL file. Please note that it is not recommended that you get the DLL file from any third-party source. You can ask help from your friends who do not encounter the error and get the file from their PCs.
Step 4: Look at the Compatibility mode section. Check the box next to Run this game in compatibility mode for and then select Windows XP SP3 from the drag-down menu. Finally, do not forget to check the box next to Run this program as an administrator.
As we know, Fallout 3 is a bit old and it only supports older versions of the drivers. In other words, the game cannot work well with some new versions of drivers. How to witch the new graphics drivers to old ones? Refer to the following tutorial.
Step 5: Select an older entry from the list of all drivers and download it. When the download process completes, save it to your computer, open it, and follow the on-screen instructions to install the old drivers.
At Fixya.com, our trusted experts are meticulously vetted and possess extensive experience in their respective fields. Backed by a community of knowledgeable professionals, our platform ensures that the solutions provided are thoroughly researched and validated.
Hello,
Well this usually means that the version of the library that the application you are running needs is different than the version of the library the application is finding.
This is an important distinction. For example you may have the correct version of the library on your computer but the application may be finding the wrong version first. In that case you will get a message like this.
Rather than give you a long technical description of the problem I suggest you try this:
Try placing a copy of xlive.dll that came with your application in the application folder.
Or try placing the latest version you can acquire of xlive.dll in your applications folder.
Being as your are getting the 'ordinal' message it is possible that your application will only run wtih the exact version of xlive.dll it was compiled for.
Hope this helps.
3a8082e126