On Mon, May 31, 2010 at 4:53 PM, juerg maier <juerg.ma...@jmid.ch> wrote:
> Hi
> downloaded pyusb-0.4.3.win32-py2.6.exe and ran it (W7/64).
> It found my Python 2.6 installation and extracted it
> into F:\Python26\Lib\site-packages
> Created a new Exclipse Pyton26 project and tried to follow the example code
>   import usb.core
> this throws an ImportError: DLL load failed: The specified module could ot
> be found
> What do I need to do in addition to make the module accessible in my
> project?
> Will it not work on my 64 bit windows?

Win7 64 bit (or Vista 64bit), that is a bit problematic. I think you have to
use test signing right now if you want to use libusb-win32.
http://www.microsoft.com/whdc/driver/install/drvsign/kmcs-walkthrough.mspx

The latest svn version has the option to use test signing. We (admins
for the libusb-win32 project) will probably get the money to get a digital
signature in the future so that libusb-win32 can work under 64bit Vista/Win7.
http://libusb-win32.svn.sourceforge.net/viewvc/libusb-win32/trunk/libusb/

I have not tried to use pyusb with Win 7 64bit yet. 32bit/64bit
DLLs are provided by the libusb-win32 package. Probably
32bit Python can work with the 32bit DLL libusb0.dll is
under C:\windows\syswow64. The 64bit DLL libusb0.dll
is under c:\windows\system32. Sounds confusing, right?
But that is because Microsoft wants to keep the compatibility
between 32bit and 64bit Windows. The 64bit drivers
(you can not use 32bit driver for 64bit Windows) libusb0.sys
will reside in c:\windows\system32\drivers.

Or maybe you want to move to pyusb-1.0 and use libusb-1.0 Windows
backend. In that case, you can use winusb.sys as the driver and
it works under 64bit Vista/Win7.
http://www.libusb.org/wiki/windows_backend

-- 
Xiaofan http://mcuee.blogspot.com

------------------------------------------------------------------------------

_______________________________________________
pyusb-users mailing list
pyusb-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/pyusb-users

Reply via email to