On Sat, 2012-10-27 at 04:46 +0200, Peter Stuge wrote:
> therau2000 wrote:
> > > > 2-More intensive testing showed
> > >
> > > What testing?
> >
> > My own testing; who else's?
>
> Of course, but how did you do it?
1-started a large file copy (over 100 MB) to Device's removable drive;
2-using "
On Sat, Oct 27, 2012 at 1:02 AM, Tim Roberts wrote:
> I don't believe any of the libusbx back-ends operate as a filter driver.
> However, I thought that the libusb-win32 COULD act as a filter.
> Am I wrong?
Yes libusb0.sys (libusb-win32 kernel driver) can act as a upper
filter and it works with l
Alan Stern wrote:
> > I still think the storage subsystem has your answer.
>
> Speaking as someone who knows practically nothing about the various
> APIs in Windows, the impression I get is that the "competing program"
> is using a "raw SCSI" interface.
Right, I think so too.
> Does Windows pro
On Sat, Oct 27, 2012 at 11:07 AM, Alan Stern wrote:
> Speaking as someone who knows practically nothing about the various
> APIs in Windows, the impression I get is that the "competing program"
> is using a "raw SCSI" interface. The analogous facility in Linux is
> provided by the sg (SCSI generi
On Sat, 27 Oct 2012, Peter Stuge wrote:
> > The sniffer output is from the "competing program" using default OS
> > driver USBSTOR. It contains BOTH types of communication and the
> > switch over is quite visible.
>
> Where would you say that it happens in the log?
>
> Also, do I understand corr
therau2000 wrote:
> > > 2-More intensive testing showed
> >
> > What testing?
>
> My own testing; who else's?
Of course, but how did you do it?
> > Let's try another approach: Tell us everything you know about the
> > device, and show some kind of capture of the non-storage communication.
>
>
On Sat, 2012-10-27 at 03:28 +0200, Peter Stuge wrote:
> > 2-More intensive testing showed
>
> What testing?
My own testing; who else's?
> Unless you see the "New device" bubble above the system tray I don't
> think there is any driver action going on.
I never said there was a device driver d
therau2000 wrote:
> > > There is visibly something similar to Linux's "detach_kernel_driver"
> >
> > How did you determine that?
>
> 2-More intensive testing showed
What testing?
> > > 1-how can we detach/re-attach the default USBSTOR driver under Windows?
> > > 2-how can we load and attach li
On Sat, 2012-10-27 at 02:57 +0200, Peter Stuge wrote:
> therau2000 wrote:
> > There is visibly something similar to Linux's "detach_kernel_driver"
> > followed by "claim_interface" followed by lets-do-business followed by a
> > "release_interface" followed by a "re-attach_kernel_driver" which t
therau2000 wrote:
> There is visibly something similar to Linux's "detach_kernel_driver"
> followed by "claim_interface" followed by lets-do-business followed by a
> "release_interface" followed by a "re-attach_kernel_driver" which then
> resumes normal removable drive operations.
How did you dete
The "competing program" definitely does not install anything. I double
checked that by dumping the full registry before and after it ran.
More intensive testing showed that while there is any transfer in
progress to/from the Device's removable drive, there is no possible
communication with the Dev
therau2000 wrote:
>
> 2-my Java Program is currently being used by well over 1600 people
> world-wide. Installing libusb-win32 driver is not an option because:
> a-it disables the default Windows removable-drive driver USBSTOR,
> therefore making it impossible to access recorded Videos/Photos;
Here the debug log what I actived before I call
libusb_get_string_descriptor_ascii()
[timestamp] [threadID] facility level [function call]
[ 0.953095] [0b1c] libusbx: debug [composite_submit_control_transfer] us
On Fri, Oct 26, 2012 at 6:21 PM, Stefano Di Martino wrote:
> Hi,
> I have the strange problem, that when I'm using pyUSB with libusbx as backend
> I get the error "Insufficient memory".
> I tried to use then libusbx directly and it end up in an similar error:
>
> "ERROR in retrieving string descr
Hi,
I have the strange problem, that when I'm using pyUSB with libusbx as backend I
get the error "Insufficient memory".
I tried to use then libusbx directly and it end up in an similar error:
"ERROR in retrieving string descriptor: LIBUSB_ERROR_NO_MEM"
I have extended listdev.c:
// ...
char da
2012/10/25 Sean McBride :
> On Fri, 12 Oct 2012 23:40:46 +0200, Ludovic Rousseau said:
>
>>To make Xcode happy I had to use #include "libusb.h" instead of
>>#include for local headers.
>
> As I said, I had to do the same. Now, for my own development & testing, I'm
> now trying something else...
16 matches
Mail list logo
