On Mon, 2012-10-29 at 01:15 +0100, Peter Stuge wrote:
> Find out exactly how those commands get sent, and find a method to
> send them which is outside the USB domain if possible, since that
> will be both simpler for you to implement *and* will provide a
> significantly better user experience.
The "competing program" uses a .dll to communicate with the Device's
Firmware. By examining that .dll file, I just discovered that it is
calling "DeviceIoControl" in kernel32.dll. MS documentation about
"DeviceIoControl" states "An application can use the DeviceIoControl
function to perform direct input and output operations on, or retrieve
information about, a floppy disk drive, hard disk drive, tape drive, or
CD-ROM drive.". Somewhere else I read that "SCSI Pass Through" is
implemented using "DeviceIoControl" direct (meaning un-buffered).
So I imagine this is how the "competing program's" .dll communicates
with the Device's Firmware.
Writing Java and C code using the libusbx API is doable for me; I have
done it and it does work nicely. But I am afraid that writing code for
"DeviceIoControl" is beyond my capabilities. So unless someone helps in
one way or another I am afraid I will have to... give up.
Regards,
therau2000
------------------------------------------------------------------------------
The Windows 8 Center - In partnership with Sourceforge
Your idea - your app - 30 days.
Get started!
http://windows8center.sourceforge.net/
what-html-developers-need-to-know-about-coding-windows-8-metro-style-apps/
_______________________________________________
libusbx-devel mailing list
libusbx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libusbx-devel
