For the AIR shared runtime installers, it may be possible to do this if you unzip the AdobeAIR.exe file and then copy the dll into that root folder, then run the installer. So if you're packaging up an application using a "bundle" and the captive runtime, you can add this file afterwards alongside your generated. If you can put this where the application. okay yes this may work! See below for a zip containing a dummy "dsound.dll" which just has the two functions we need at the appropriate ordinals. Not 100% sure whether that would work, I'll see if we can try it. Not sure whether the Dependency Walker can give any information about it, I was wondering as a temporary workaround we could just create a new/dummy dsound.dll, which can be put into the same location as the executable. I'm curious as to why that DLL fails to load, it's not just that the symbols are changed but the library is failing when we call LoadLibrary on it. Reading up on the Windows 11 compatibility promise, all they say is that they'll work with the vendor to fix the issue, so I think this is one that we need to update. Sounds like this may be a known issue (or at least, there are others experiencing the same problem). See a picture of what we're looking for below. functions that it's trying to import from a DLL that are missing, then we have our culprit, and we can switch to dynamic loading/detection of the symbols for that library.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |