"Michael" == Michael Stefaniuc mstefani@redhat.de writes:
Michael> The change is for Win64 compatibility and it matches the DDK. -MMRESULT WINAPI acmDriverEnum(ACMDRIVERENUMCB fnCallback, DWORD dwInstance, DWORD fdwEnum) +MMRESULT WINAPI acmDriverEnum(ACMDRIVERENUMCB fnCallback, DWORD_PTR dwInstance, DWORD fdwEnum)
Is the spec aentry then still right?
./dlls/msacm32/msacm32.spec:@ stdcall acmDriverDetailsW(long ptr long)
Uwe Bonnes wrote:
"Michael" == Michael Stefaniuc mstefani@redhat.de writes:
Michael> The change is for Win64 compatibility and it matches the DDK.
-MMRESULT WINAPI acmDriverEnum(ACMDRIVERENUMCB fnCallback, DWORD dwInstance, DWORD fdwEnum) +MMRESULT WINAPI acmDriverEnum(ACMDRIVERENUMCB fnCallback, DWORD_PTR dwInstance, DWORD fdwEnum)
Is the spec aentry then still right?
./dlls/msacm32/msacm32.spec:@ stdcall acmDriverDetailsW(long ptr long)
For 32bit yes but if it will work for 64bit I have no clue. I don't remember to have seen any Win64 fix patch that touched the spec file too so I would have to defer the answer to this question to Alexandre.
bye michael
Michael Stefaniuc mstefani@redhat.com writes:
Uwe Bonnes wrote:
> "Michael" == Michael Stefaniuc mstefani@redhat.de writes:
Michael> The change is for Win64 compatibility and it matches the DDK.
-MMRESULT WINAPI acmDriverEnum(ACMDRIVERENUMCB fnCallback, DWORD dwInstance, DWORD fdwEnum) +MMRESULT WINAPI acmDriverEnum(ACMDRIVERENUMCB fnCallback, DWORD_PTR dwInstance, DWORD fdwEnum)
Is the spec aentry then still right?
./dlls/msacm32/msacm32.spec:@ stdcall acmDriverDetailsW(long ptr long)
For 32bit yes but if it will work for 64bit I have no clue. I don't remember to have seen any Win64 fix patch that touched the spec file too so I would have to defer the answer to this question to Alexandre.
It's fine for 64-bit too.