Sorry for previous message: link was not sent properly.
Since you are indeed very knowledgeable on the subject and seem to be a
great Mac Fan, tell me:
is technically feasible to implement what is described here
https://developer.apple.com/library/mac/#documentation/DeviceDrivers/Conceptual/Clas
Since you are indeed very knowledgeable on the subject and seem to be a
great Mac Fan, tell me:
is technically feasible to implement what is described here on the Mac
as the Linux equivalent
libusb_detach_kernel_driver/libusb_attach_kernel_driver?
I know all about the kext approach but it is NOT
On Thu, 2012-11-15 at 05:28 +0100, Peter Stuge wrote:
> therau2000 wrote:
> > > > libusb-1.0.dll is getting loaded by the interface class with the
> > > > following command:
> > > > MyLib libUSB = (MyLib) Native.loadLibrary("usb-1.0", MyLib.class)
On Thu, 2012-11-15 at 04:32 +0100, Peter Stuge wrote:
> therau2000 wrote:
> > libusb-1.0.dll is getting loaded by the interface class with the
> > following command:
> > MyLib libUSB = (MyLib) Native.loadLibrary("usb-1.0", MyLib.class);
>
> I don't e
libusb-1.0.dll is getting loaded by the interface class with the
following command:
MyLib libUSB = (MyLib) Native.loadLibrary("usb-1.0", MyLib.class);
I need to unload libusb-1.0.dll to load another one.
Question: How can I unload libusb-1.0.dll while keeping my program
running?
On Tue, 2012-11-13 at 10:16 -0800, Tim Roberts wrote:
> therau2000 wrote:
>
> >
> >
> > In my case, it is always a one-to-one match; all USB devices have
> > only one partition formatted as FAT32.
>
>
> Today, maybe. Will your software never be used on
:
> therau2000 wrote:
>
> >
> >
> > Several USB devices [all with different vendor/product-id, all
> > removable drives with different Volume names, all formatted FAT32]
> > are already connected when program starts. Windows does NOT display
> > Volume names; it dis
Here is the situation:
Several USB devices [all with different vendor/product-id, all removable
drives with different Volume names, all formatted FAT32] are already
connected when program starts. Windows does NOT display Volume names; it
displays only "removable drive" and the Drive letter for eac
ything besides Java 6 or above to run my program.
Thank you all for your help,
therau2000
--
The Windows 8 Center - In partnership with Sourceforge
Your idea - your app - 30 days.
Get started!
http://windows8center.sourcef
IoControl" 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
On Sun, 2012-10-28 at 16:57 -0400, Alan Stern wrote:
> On Sun, 28 Oct 2012, therau2000 wrote:
> > When program xusb fails to claim interface 0, it would seem possible to
> > "activate SCSI Pass Through". Further calls to libusb_bulk_transfer
> > could then be
On Sun, 2012-10-28 at 20:57 +0100, Peter Stuge wrote:
> therau2000 wrote:
> > In that case, will you please add "SCSI Pass Through" capability
> > to libusbx?
>
> I won't, but maybe someone else will.
Sorry, I thought you were making all decisions regardin
don't
> see why mass storage would be less worthy.
In that case, will you please add "SCSI Pass Through" capability to
libusbx?
>
>
> therau2000 wrote:
> > Before I tried to use libusbx, I investigated (and many times
> > unsuccessfully tried) just about every
On Sun, 2012-10-28 at 21:12 +0800, Xiaofan Chen wrote:
> On Sun, Oct 28, 2012 at 8:09 PM, therau2000 wrote:
> > On Sun, 2012-10-28 at 11:51 +0800, Xiaofan Chen wrote:
> >
> > Given this scenario:
> > 1-uninstall any driver installed by zadig.exe;
> > 2-use exam
4-when failing to "claim interface", libusbx automatically falls back to
"SCSI Pass Trough" for all synchronous transfers.
Could it be THE solution for all USB devices that show up as a removable
drive?
therau2000
---
On Sun, 2012-10-28 at 08:58 +0800, Xiaofan Chen wrote:
> On Sat, Oct 27, 2012 at 11:41 AM, therau2000 wrote:
> > libusbx is required because my Java Program is used on Linux and Mac OS X as
> > well. My prototype program does work without any modification under 64-bit
> > Li
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
the switch
over is quite visible.
The xusb output was done while using libusb0 driver.
therau2000
Using libusbx v1.0.14.10576
Opening device 0546:3304...
Reading device descriptor:
length: 18
device class: 0
S/N: 3
VID:PID: 0546:3304
bcdDevi
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_inter
ver under Windows?
2-how can we load and attach libusb0 (.dll and/or .sys) WITHOUT doing an
install?
This CAN be done; the proof is that the "competing program" is doing it.
There a some very smart people out there; I am sure someone has figured
this out already ... or is about to
) does not require User
to install anything to work correctly.
Question: how can libusbx piggy-back its communication to USB
devices over driver USBSTOR ?
Thank you for your help,
therau2000
--
Everyone hates slow
21 matches
Mail list logo
