Why don’t u try again call ExCreateCallback with the Create parameter set as
False, indicating that it requires an existing callback object. If that is
success then probably ExUnregisterCallback is not doing its job … hope ur
calling ExUnregisterCallback at IRQL < DISPATCH_LEVEL. Else if
ExCreateCallback fails with Create False in ur case then perhaps WinObj
isn’t updating current callback sections … 
–Arup
-----Original Message-----
From: Daniel Simard [mailto:xxxxx@matrox.com]
Sent: Wednesday, April 24, 2002 6:01 PM
To: NT Developers Interest List
Subject: [ntdev] SOMEBODY HAS AN ANSWER –> Callbacks for driver
communication
Hi, I have implemented the callback method for driver communication (like
suggested into your NT Insider document volume 8 issue 4) i.e. with
ExRegisterCallback and ExNotifyCallback.
This is working really well, but event if I unregister and dereference my
callbacks they are still into the \callback\ folder (can see them with
WinObj.exe).
Is it normal or is it something I might doing wrong ?
thanks
You are currently subscribed to ntdev as: xxxxx@quark.co.in
To unsubscribe send a blank email to %%email.unsub%%