https://bugs.winehq.org/show_bug.cgi?id=51058
Bug ID: 51058 Summary: Buddy Launcher: fails to install/run, "failed to create driver" Product: Wine Version: 6.7 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: ntoskrnl Assignee: wine-bugs@winehq.org Reporter: pernegger@gmail.com Distribution: ---
Created attachment 69919 --> https://bugs.winehq.org/attachment.cgi?id=69919 terminal output [wine 6.7]
BuddyLauncher is a Japanese online activation DRM "solution" required for some commercial games, the client is available from https://www.drmbuddy.com/mypage/dl_launcher.php [the big grey button to the right that says "無料ダウンロード", you want BuddySetup3201.exe]. It may need LANG=ja_JP.UTF-8 or similar set to run.
I know DRM is tricky, and I'm not holding my breath, but considering the last update was in 2011 and it supports everything back to 98SE(!) I thought it might be simple enough to at least report it.
The installation completes without a GUI error message, but it's obviously not installed correctly, and the terminal output has this at the end:
0118:fixme:ntoskrnl:IoAllocateDriverObjectExtension stub: 00426DD8, 003B5000, 76, 00D9FA1C 0118:err:ntoskrnl:ZwLoadDriver failed to create driver L"\Registry\Machine\System\CurrentControlSet\Services\{1B5AFF9E-65D4-4392-9CD0-DF0DB39A6AD4}": c0000002
[Ubuntu 18.04.5, official packages from winehq.org]
https://bugs.winehq.org/show_bug.cgi?id=51058
Etaash Mathamsetty etaash.mathamsetty@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |etaash.mathamsetty@gmail.co | |m
--- Comment #1 from Etaash Mathamsetty etaash.mathamsetty@gmail.com --- Created attachment 73573 --> https://bugs.winehq.org/attachment.cgi?id=73573 patch that implements Driver Object Extensions
https://bugs.winehq.org/show_bug.cgi?id=51058
--- Comment #2 from Etaash Mathamsetty etaash.mathamsetty@gmail.com --- could you test that patch and see if the DRM works now?
https://bugs.winehq.org/show_bug.cgi?id=51058
--- Comment #3 from pernegger@gmail.com --- (In reply to Etaash Mathamsetty from comment #2)
could you test that patch and see if the DRM works now?
To be honest, the idea of building WINE, patched or otherwise, is rather too daunting. The minute this lands in an official build (devel/staging), I'll be happy to!
https://bugs.winehq.org/show_bug.cgi?id=51058
--- Comment #4 from Etaash Mathamsetty etaash.mathamsetty@gmail.com --- here's the thing, I don't want to submit it until I am sure that we are allowed to look at the ReactOS NDK headers (do those violate clean room?, where do we draw the line?)
Compiling wine is also not that difficult the wine documentation has a guide for it
https://bugs.winehq.org/show_bug.cgi?id=51058
--- Comment #5 from Etaash Mathamsetty etaash.mathamsetty@gmail.com --- (In reply to Etaash Mathamsetty from comment #4)
here's the thing, I don't want to submit it until I am sure that we are allowed to look at the ReactOS NDK headers (do those violate clean room?, where do we draw the line?)
Compiling wine is also not that difficult the wine documentation has a guide for it
You would also want to compile a WOW64 build, since the driver is probably 32 bit
https://bugs.winehq.org/show_bug.cgi?id=51058
--- Comment #6 from pernegger@gmail.com --- (In reply to Etaash Mathamsetty from comment #2)
could you test that patch and see if the DRM works now?
Should the patch still work with current master as-is? If not, would you mind updating it? (I'm finally willing and able to build WINE locally.)
https://bugs.winehq.org/show_bug.cgi?id=51058
--- Comment #7 from Etaash Mathamsetty etaash.mathamsetty@gmail.com --- I think it should, nothing much has changed in ntoskrnl it's definitely not getting upstreamed though (without a rewrite), because react os headers are off limits as well.
-
WineHQ Bugzilla