[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]

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

--- Comment #5 from Jacek Caban <jacek at codeweavers.com> ---
(In reply to Zebediah Figura from comment #4)
> (In reply to Zebediah Figura from comment #3)
> > 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.
> 
> Well, maybe. The application attached to bug 33908 uses
> ExReleaseResourceForThreadLite().

FWIW, MRAC seems happy with just ExInitializeResourceLite().

> And presumably we'll need a KTHREAD implementation eventually anyway. I did
> ask for feedback on how to add one [1], but got no response.
> 
> [1] https://www.winehq.org/pipermail/wine-devel/2019-January/138609.html

Sure, ideally we'd have it implemented. I replied to wine-devel.

-- 
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.