[Bug 45819] Symantec Eraser Control Driver 'eeCtrl64.sys' (Norton 360) fails in driver entry point due to 'ntoskrnl.exe.ExInitializeResourceLite ' stub (needs STATUS_SUCCESS)

wine-bugs at winehq.org wine-bugs at winehq.org
Wed Feb 20 14:03:13 CST 2019


https://bugs.winehq.org/show_bug.cgi?id=45819

--- Comment #3 from Zebediah Figura <z.figura12 at gmail.com> ---
(In reply to Jacek Caban from comment #2)
> (In reply to Zebediah Figura from comment #1)
> > I have a working implementation of this which I've pushed to Staging.
> > However, it doesn't work in Wine yet, because it needs an implementation of
> > KeGetCurrentThread().
> 
> Unless I'm missing something, you don't need the actual structue, just an
> unique thread identifier. For that you could just use PsGetCurrentThreadId()
> which is already implemented.

Problem there is that programs can pass (their own or a different) thread to
ExReleaseResourceForThreadLite(), and that's supposed to be a KTHREAD pointer.

I guess we can skip that for now, though.

-- 
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.



More information about the wine-bugs mailing list