64

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Just list Devices
2.
3.
output:
##
jusbpmp.dll: Can't load IA 32-bit .dll on a AMD 64-bit platform
    at java.lang.ClassLoader$NativeLibrary.load(Native Method)
    at java.lang.ClassLoader.loadLibrary1(Unknown Source)
    at java.lang.ClassLoader.loadLibrary0(Unknown Source)
    at java.lang.ClassLoader.loadLibrary(Unknown Source)
    at java.lang.Runtime.load0(Unknown Source)
    at java.lang.System.load(Unknown Source)
    at jpmp.manager.DeviceManager.loadPmpLib(Unknown Source)
    at jpmp.manager.DeviceManager.<init>(Unknown Source)
    at jpmp.manager.DeviceManager.getInstance(Unknown Source)
##

Version 1.4 Win7 64 bit.
I think the only problem here is that the dll has been compiled for 32 bit 
system.

There's any way i could recompile it for 64 bit instead?
After that, could check wich architecture is present and therefore load the 
proper dll at app startup.

greetings

Original issue reported on code.google.com by rs...@iscte-iul.pt on 9 Nov 2012 at 10:56

[GoogleCodeExporter]

Compiled for Win32, check sources to recompile for 64 bit.

Original comment by netcm...@gmail.com on 19 Feb 2013 at 4:41

[GoogleCodeExporter]

sources are not available! why? It keeps saying "could not resolve hostname 
'jusbpmp.googlecode.com'

What to do about it?!

Original comment by lbru...@gmail.com on 14 Oct 2013 at 11:00

[GoogleCodeExporter]

Hi!

I've tried to find a downloadable 64 bit DLL, but after spending a few hours 
searching and not finding anything, I set out to compile it myself.

So I
- downloaded and installed Visual Studio
- configured the required JNI
- spent another few hours looking for a certain mssachlp.lib that was being 
missed by the system
- waded through the circular references over at msdn looking for a download for 
WMDM
- ended up downloading a possibly random mssachlp.lib from a code.google 
project that happened to host a file with this name
- found out the hard way that despite being on an x64 machine I still have to 
configure VS if I'd like to have a 64-bit binary built
- and in the crowning moment of awesome, I encounter these lines:

1>  Generating Code...
1>     Creating library D:\work\......\jusbpmp\x64\Debug\jusbpmp.lib and object 
D:\work\......\jusbpmp\x64\Debug\jusbpmp.exp
1>devicemanager.obj : error LNK2019: unresolved external symbol "public: 
__cdecl CSecureChannelClient::CSecureChannelClient(void)" 
(??0CSecureChannelClient@@QEAA@XZ) referenced in function "public: virtual void 
__cdecl devicemanager::setup_mtp(void)" (?setup_mtp@devicemanager@@UEAAXXZ)
1>devicemanager.obj : error LNK2019: unresolved external symbol "public: 
__cdecl CSecureChannelClient::~CSecureChannelClient(void)" 
(??1CSecureChannelClient@@QEAA@XZ) referenced in function "public: void * 
__cdecl CSecureChannelClient::`scalar deleting destructor'(unsigned int)" 
(??_GCSecureChannelClient@@QEAAPEAXI@Z)
1>devicemanager.obj : error LNK2019: unresolved external symbol "public: long 
__cdecl CSecureChannelClient::SetCertificate(unsigned long,unsigned char 
*,unsigned long,unsigned char *,unsigned long)" 
(?SetCertificate@CSecureChannelClient@@QEAAJKPEAEK0K@Z) referenced in function 
"public: virtual void __cdecl devicemanager::setup_mtp(void)" 
(?setup_mtp@devicemanager@@UEAAXXZ)
1>devicemanager.obj : error LNK2019: unresolved external symbol "public: void 
__cdecl CSecureChannelClient::SetInterface(struct IComponentAuthenticate *)" 
(?SetInterface@CSecureChannelClient@@QEAAXPEAUIComponentAuthenticate@@@Z) 
referenced in function "public: virtual void __cdecl 
devicemanager::setup_mtp(void)" (?setup_mtp@devicemanager@@UEAAXXZ)
1>devicemanager.obj : error LNK2019: unresolved external symbol "public: long 
__cdecl CSecureChannelClient::Authenticate(unsigned long)" 
(?Authenticate@CSecureChannelClient@@QEAAJK@Z) referenced in function "public: 
virtual void __cdecl devicemanager::setup_mtp(void)" 
(?setup_mtp@devicemanager@@UEAAXXZ)
1>D:\work\......\jusbpmp\x64\Debug\jusbpmp.dll : fatal error LNK1120: 5 
unresolved externals

Could you please help me with this matter, or maybe compile and upload a 64-bit 
version of the dll itself?

Original comment by zov...@gmail.com on 18 Jul 2014 at 2:46