I don't have classic/OS 9 installed on this computer. It's pure OS X
and I get the exclusive error when calling USBInterfaceOpenSeize(). The
C++ code is built with Project Builder so there's no chance of a rogue
library.
Any other ideas?
John
On Thursday, October 2, 2003, at 11:16 AM, Steve Sisak wrote:
At 8:08 -0700 10/2/03, Kris Daniel wrote:
This happened to me as well. I noticed that if I called
USBDeviceOpen(), or USBInterfaceOpen(), I'd usually get an error on
the first call. Just to be stubborn, I tried calling the open
command again after it failed, and it opened successfully.
I don't have an explanation for it (possibly uninitialized
variable?), it works, so I moved on. At the very least, it's an idea
to try.
It sounds like Classic has control of the device -- retrying
USBDeviceOpen()/USBInterfaceOpen() is part of the procedure for
getting Classic to release a device it has open.
-Steve
_______________________________________________
usb mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/usb
Do not post admin requests to the list. They will be ignored.
