You're not thinking in USB terms. Physically unplugging the device or running out of batter power would obviously cause problems, and if you try to talk to a device that's gone you will get a UsbDisconnectedException (once the disconnection is detected by the USB Hub or Host Controller).
However there are a large number of other USB exceptions, PID, CRC, Babble, BitStuff, Stall, etc. Basically whenever you send/receieve data over the USB bus, any of the errors defined in the USB spec can happen. Additionally, the OS may encounter a non-specific error and throw a UsbPlatformException. On Fri, 30 Dec 2005, Elliotte Harold wrote: >Dan Streetman wrote: > >> To get a String Descriptor you have to talk to the device, and anytime you >> actually talk to a device you can get an exception (see the sync/async >> Submit methods). > >That makes sense. Thanks. Could you give me an example of the sort of >error that might occur? For instance, if the device were physically >unplugged or ran out of battery power and then I tried to talk to it >would I get this exception? But that would probably be a >UsbDisconnectedException. Maybe a misbehaving device elsewhere on the >chain? What causes these exceptions to occur in practice? > > > -- Dan Streetman [EMAIL PROTECTED] --------------------- 186,272 miles per second: It isn't just a good idea, it's the law! ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ javax-usb-devel mailing list javax-usb-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/javax-usb-devel
