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

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

--- Comment #6 from Zebediah Figura  ---
(In reply to Jacek Caban from comment #5)
> (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().

Sure, I expect most applications are, but as with spinlocks, I'd rather
implement the whole suite properly so we don't run into annoying race
conditions down the road.