10-27-2008 01:41 PM
loadlibrary 193 seems to indicate that the 32-bit DLL is bad. Anyone have any solutions?
10-27-2008 04:55 PM
The better way is to call the automation object (see the examples directory) to send a message - the entire opcapi.dll is implemented as a com object.
10-27-2008 09:24 PM
Thanks for the thought, but my code is compiled w/ the x86 CPU option (for 32-bit), and it installs into file path "C:\Program Files (x86)\...". I'm merely trying to port to a Win64 system. The HP BTP software supports both a 32-bit & 64-bit versions of opcapi.dll on win64.
When I compile with the "AnyCpu" (64-bit on win64) option, I can link to the 64-bit opcapi.dll, but other parts of our product require that we stay in 32-bit mode.
So, the big question is "Why can't I load the 32-bit version of opcapi.dll?". The error 193 implies HP shipped a bad library. Am I missing something? The same code works on a 32-bit windows w/ BTO software. Any other ideas?
10-29-2008 01:51 PM
The problem/solution is simple. There is no reference in the PATH variable to the 32-bit libraries... so my 32-bit app always tries to bind to the 64 bit versions. Duh. Sometimes its the simple things.