I thought that the
kIOHIDOptionsTypeSeizeDevice was supposed to be able to grab control
from
everyone else...?
If you think about it, letting any software grab control of the device
at any time would be a bad thing. For instance, you don't want some
other app coming along and Seizing the device after you seized it.
(Particularly if you are in the middle of an important read.)
I would venture to guess that the Griffin driver is already opening the
device for exclusive use. If that's the case, all you can do is either
not install the Griffin driver, or write your own kext that matches at
a lower level and can selectively route the data to your app or back up
the normal IO chain to the griffin driver.
You should, however, be getting either a kIOReturnExclusiveAccess, or
kIOReturnNotPrivileged errors. Do you get back a different error if you
try to open the device normally?
-raleigh
-----------------------------------------------
Raleigh Ledet, <email@hidden>
Wacom Technology Corp.
Mac Software Engineer
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Usb mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/usb/email@hidden
