Replies: 1 comment
-
I have heard about this issue before affecting some users. Basically the operating system seems to load only the real system dll file ignoring the local wrapper. Renaming the wrapper and hex editing the executable to point to it is probably the best solution in that case. But it is a curious thing and I do not know why some users have this issue. One could look at the MS documentation here: For dsound.dll there is talk about a similar issue here: EDIT: |
Beta Was this translation helpful? Give feedback.
-
Why do i have to rename winmm.dll to e.g. winmx.dll to make it work?
Beta Was this translation helpful? Give feedback.
All reactions