Signed-off-by: Nikolay Sivov nsivov@codeweavers.com --- .../api-ms-win-core-libraryloader-l1-2-1.spec | 1 + 1 file changed, 1 insertion(+)
diff --git a/dlls/api-ms-win-core-libraryloader-l1-2-1/api-ms-win-core-libraryloader-l1-2-1.spec b/dlls/api-ms-win-core-libraryloader-l1-2-1/api-ms-win-core-libraryloader-l1-2-1.spec index 4cc3358eed..5e2842196f 100644 --- a/dlls/api-ms-win-core-libraryloader-l1-2-1/api-ms-win-core-libraryloader-l1-2-1.spec +++ b/dlls/api-ms-win-core-libraryloader-l1-2-1/api-ms-win-core-libraryloader-l1-2-1.spec @@ -7,6 +7,7 @@ @ stub EnumResourceTypesExA @ stub EnumResourceTypesExW @ stdcall FindResourceExW(long wstr wstr long) kernel32.FindResourceExW +@ stdcall FindResourceW(long wstr wstr) kernel32.FindResourceW @ stdcall FindStringOrdinal(long wstr long wstr long long) kernel32.FindStringOrdinal @ stdcall FreeLibrary(long) kernel32.FreeLibrary @ stdcall FreeLibraryAndExitThread(long long) kernel32.FreeLibraryAndExitThread
Hello Nikolay,
isn't it better to regenerate the spec from a newer api-ms-win- core-libraryloader-l1-2-1 dll? This way we'll have the version info, too.
Regards, Fabian Maurer
On 1/23/19 10:07 PM, Fabian Maurer wrote:
Hello Nikolay,
isn't it better to regenerate the spec from a newer api-ms-win-core-libraryloader-l1-2-1 dll? This way we'll have the version info, too.
What should I regenerate it from? What do you mean by version info?
Regards,
Fabian Maurer
Hello Nikolay,
You can use winedump on both 32bit and 64bit api-ms-win-core- libraryloader-l1-2-1 to get their exports. Just install the latest Win10 with the latest SDK to get the most recent version of these DLLs. Then you can also add the Windows10/SDK version that you used to generated the specs into the patch.
Regards, Fabian Maurer
On 1/23/19 11:47 PM, Fabian Maurer wrote:
Hello Nikolay,
You can use winedump on both 32bit and 64bit api-ms-win-core-libraryloader-l1-2-1 to get their exports. Just install the latest Win10 with the latest SDK to get the most recent version of these DLLs.
Then you can also add the Windows10/SDK version that you used to generated the specs into the patch.
I don't have this file in 10.0.17763.0.
Regards,
Fabian Maurer
January 23, 2019 4:09 PM, "Nikolay Sivov" nsivov@codeweavers.com wrote:
On 1/23/19 11:47 PM, Fabian Maurer wrote:
Hello Nikolay,
You can use winedump on both 32bit and 64bit api-ms-win-core-libraryloader-l1-2-1 to get their exports. Just install the latest Win10 with the latest SDK to get the most recent version of these DLLs.
Then you can also add the Windows10/SDK version that you used to generated the specs into the patch.
I don't have this file in 10.0.17763.0.
That's because it's not a real file. On real Windows, it's a pseudo-DLL generated on demand by the loader, which keeps a big table of API sets and their mappings to the real DLLs that implement them.
Regards,
Fabian Maurer
Chip
On 1/24/19 1:13 AM, Chip Davis wrote:
January 23, 2019 4:09 PM, "Nikolay Sivov" nsivov@codeweavers.com wrote:
On 1/23/19 11:47 PM, Fabian Maurer wrote:
Hello Nikolay,
You can use winedump on both 32bit and 64bit api-ms-win-core-libraryloader-l1-2-1 to get their exports. Just install the latest Win10 with the latest SDK to get the most recent version of these DLLs.
Then you can also add the Windows10/SDK version that you used to generated the specs into the patch.
I don't have this file in 10.0.17763.0.
That's because it's not a real file. On real Windows, it's a pseudo-DLL generated on demand by the loader, which keeps a big table of API sets and their mappings to the real DLLs that implement them.
That's why I asked about how I am supposed to generate from it. I don't really want to dump memory sections after it was loaded hoping to find something there.
Regards,
Fabian Maurer
Chip
Hello guys,
@Nikolay I have some of the api set DLLs, but the one in question is missing. I thought all were actual DLLs up to now.
@Alisair I saw you updated this DLL to "File version 6.3.9600.16384". How'd you get that file?
@Chip Interesting, how do you know that? Do you have a link for more information? I'd like to learn more.
Regards, Fabian Maurer