« Close

Datasheets and User Guides

App Notes

Software & Driver

 

64-bit LabJackUD.dll (Outdated)

This is an old version of the driver that is no longer necessary. The current LabJack Installer includes both 32-bit and 64-bit versions of everything needed for both 32-bit and 64-bit applications. That installer can be found at this link

This is a beta of a 64-bit version of the LabJackUD.dll and can be used with 64-bit applications running on 64-bit versions of Windows. However, it is not required for 64-bit versions of Windows since those will run 32-bit applications. All 64-bit applications using the LabJackUD driver will require this version. This includes the 64-bit versions of MATLAB and LabVIEW as well as applications you write.

To install, simply unzip and place the LabJackud.dll and LabJackWUSB.dll files into the C:\windows\system32 folder, which is where Windows stores 64-bit DLLs.

Currently, there are some limitations with how pointers and arrays are handled. These will be cleared up in a future version. For now this version should work fine on systems with less than 4 GB of memory.

Since this is still strongly in development, if you run into any issues with it please let us know so they can be addressed.
File Attachment: 

23 comments

What is the expected date for a release version of the 64-bit DLL?

We had to push this back a bit due to some other projects so we don't have a firm date set at this time.  However, it is something we are still working on. 

If there is a problem you are having with the current version above, send us an email to [email protected] and it's likely something we can fix/add and post within a few days.

I'm running the 64-bit version of Matlab under Win7 on a machine that has 8GB of RAM.

Will this beta version of the driver work:

    1. Never

    2. Sometimes

    3. Always

?

 

We currently have several people who are using this version without problems.  It should work under most circumstances.

There is a theoretical point where it won't work, but from a practical standpoint very few people have run into that.

Hi,

I am trying out the C# U3_SPI example code with a U3.  My PC is running Windows 7 64 bit.  My compiler is Visual Studio 2010 Pro.

I installed the driver exactly as shown in this page and in the preceding page for 64 bit Windows UD driver.

Testing with LJControlPanel shows the PC can talk to the U3.

In debug mode in Visual Studio, I set the platform target to x64.

When I step through the code and come to this line:

u3 = new U3(LJUD.CONNECTION.USB, "0", true); // Connection through USB

I always get this error message:

System.DllNotFoundException was unhandled
  Message=Unable to load DLL 'labjackud.dll': The application has failed to start because its side-by-side configuration is incorrect. Please see the application event log or use the command-line sxstrace.exe tool for more detail. (Exception from HRESULT: 0x800736B1)
  Source=LJUDDotNet
  TypeName=""
  StackTrace:
       at LabJack.LabJackUD.LJUD.UDOpenLabJack(DEVICE deviceType, CONNECTION connectionType, String address, Boolean firstFound, Int32& handle)
       at LabJack.LabJackUD.LJUD.OpenLabJack(DEVICE deviceType, CONNECTION connectionType, String address, Boolean firstFound, Int32& handle)
       at LabJack.LabJackUD.U3..ctor(CONNECTION connectionType, String address, Boolean firstFound)
       at SPI.SPI.performActions() in C:\LabJack\C#\U3_SPI\U3_SPI.cs:line 72
       at SPI.SPI.Main(String[] args) in C:\LabJack\C#\U3_SPI\U3_SPI.cs:line 42
       at System.AppDomain._nExecuteAssembly(RuntimeAssembly assembly, String[] args)
       at Microsoft.VisualStudio.HostingProcess.HostProc.RunUsersAssembly()
       at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean ignoreSyncCtx)
       at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
       at System.Threading.ThreadHelper.ThreadStart()
  InnerException:

Please help.  Thank you.

It looks like that could be one of two issues.  The first would be to double check that the 64-bit versions of the LabJackUD.dll and the LabJackWUSB.dll are found in the system32 folder (which needs to be done separately).  It looks like other people with a similar error were able to fix it by installing the Visual C++ runtime packages.  One of the following might fix this:

 

http://www.microsoft.com/downloads/en/details.aspx?FamilyID=BD512D9E-43C...

http://www.microsoft.com/downloads/en/details.aspx?displaylang=en&Family...

 

Thank you for your prompt reply.

I double-checked and, yes, LabJackUD.dll and LabJackWUSB.dll are both in c:\windows\system32.  Both of these 2 files were extracted from LJUD64bitv315.zip.

I also renamed LabJackUD.dll and LabJackWUSB.dll in C:\Windows\SysWOW64 so that they are not available anymore.  I believe they were put into SysWOW64 by LabJackUDSetupV315_64bit.exe, because I did not put them there.  (It did not make any difference whether they have the right name or not.)

I also installed Visual C++ runtime from http://www.microsoft.com/downloads/en/details.aspx?FamilyID=BD512D9E-43C8-4655-81BF-9350143D5867.  Actually it was an reinstall, because it only offered two options: repair or uninstall.  I chose repair.

I then tried stepping through the U3_SPI again and ran into the same error.

The error message suggested using sxstrace.exe to get more details on the side-by-side configuration error.

This is the output of the sxstrace tracing:

=================
Begin Activation Context Generation.
Input Parameter:
 Flags = 0
 ProcessorArchitecture = AMD64
 CultureFallBacks = en-US;en
 ManifestPath = C:\Windows\system32\labjackud.dll
 AssemblyDirectory = C:\Windows\system32\
 Application Config File =
-----------------
INFO: Parsing Manifest File C:\Windows\system32\labjackud.dll.
 INFO: Manifest Definition Identity is (null).
 INFO: Reference: Microsoft.VC90.CRT,processorArchitecture="amd64",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="9.0.21022.8"
 INFO: Reference: Microsoft.VC90.MFC,processorArchitecture="amd64",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="9.0.21022.8"
INFO: Resolving reference Microsoft.VC90.CRT,processorArchitecture="amd64",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="9.0.21022.8".
 INFO: Resolving reference for ProcessorArchitecture amd64.
  INFO: Resolving reference for culture Neutral.
   INFO: Applying Binding Policy.
    INFO: Find publisher policy at C:\Windows\WinSxS\manifests\amd64_policy.9.0.microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.4926_none_accf10dbe1dc8ba2.manifest
    INFO: Publisher Policy redirected assembly version.
    INFO: Post policy assembly identity is Microsoft.VC90.CRT,processorArchitecture="amd64",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="9.0.30729.4926".
   INFO: Begin assembly probing.
    INFO: Attempt to probe manifest at C:\Windows\WinSxS\manifests\amd64_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.4926_none_08e1a05ba83fe554.manifest.
    INFO: Manifest found at C:\Windows\WinSxS\manifests\amd64_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.4926_none_08e1a05ba83fe554.manifest.
   INFO: End assembly probing.
INFO: Resolving reference Microsoft.VC90.CRT.mui,language="*",processorArchitecture="amd64",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="9.0.30729.4926".
 INFO: Resolving reference for ProcessorArchitecture amd64.
  INFO: Resolving reference for culture en-US.
   INFO: Applying Binding Policy.
    INFO: No publisher policy found.
    INFO: No binding policy redirect found.
   INFO: Begin assembly probing.
    INFO: Did not find the assembly in WinSxS.
    INFO: Attempt to probe manifest at C:\Windows\assembly\GAC_64\Microsoft.VC90.CRT.mui\9.0.30729.4926_en-US_1fc8b3b9a1e18e3b\Microsoft.VC90.CRT.mui.DLL.
    INFO: Attempt to probe manifest at C:\Windows\system32\en-US\Microsoft.VC90.CRT.mui.DLL.
    INFO: Attempt to probe manifest at C:\Windows\system32\en-US\Microsoft.VC90.CRT.mui.MANIFEST.
    INFO: Attempt to probe manifest at C:\Windows\system32\en-US\Microsoft.VC90.CRT.mui\Microsoft.VC90.CRT.mui.DLL.
    INFO: Attempt to probe manifest at C:\Windows\system32\en-US\Microsoft.VC90.CRT.mui\Microsoft.VC90.CRT.mui.MANIFEST.
    INFO: Did not find manifest for culture en-US.
   INFO: End assembly probing.
  INFO: Resolving reference for culture en.
   INFO: Applying Binding Policy.
    INFO: No publisher policy found.
    INFO: No binding policy redirect found.
   INFO: Begin assembly probing.
    INFO: Did not find the assembly in WinSxS.
    INFO: Attempt to probe manifest at C:\Windows\assembly\GAC_64\Microsoft.VC90.CRT.mui\9.0.30729.4926_en_1fc8b3b9a1e18e3b\Microsoft.VC90.CRT.mui.DLL.
    INFO: Attempt to probe manifest at C:\Windows\system32\en\Microsoft.VC90.CRT.mui.DLL.
    INFO: Attempt to probe manifest at C:\Windows\system32\en\Microsoft.VC90.CRT.mui.MANIFEST.
    INFO: Attempt to probe manifest at C:\Windows\system32\en\Microsoft.VC90.CRT.mui\Microsoft.VC90.CRT.mui.DLL.
    INFO: Attempt to probe manifest at C:\Windows\system32\en\Microsoft.VC90.CRT.mui\Microsoft.VC90.CRT.mui.MANIFEST.
    INFO: Did not find manifest for culture en.
   INFO: End assembly probing.
INFO: Resolving reference Microsoft.VC90.MFC,processorArchitecture="amd64",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="9.0.21022.8".
 INFO: Resolving reference for ProcessorArchitecture amd64.
  INFO: Resolving reference for culture Neutral.
   INFO: Applying Binding Policy.
    INFO: No publisher policy found.
    INFO: No binding policy redirect found.
   INFO: Begin assembly probing.
    INFO: Did not find the assembly in WinSxS.
    INFO: Attempt to probe manifest at C:\Windows\assembly\GAC_64\Microsoft.VC90.MFC\9.0.21022.8__1fc8b3b9a1e18e3b\Microsoft.VC90.MFC.DLL.
    INFO: Attempt to probe manifest at C:\Windows\system32\Microsoft.VC90.MFC.DLL.
    INFO: Attempt to probe manifest at C:\Windows\system32\Microsoft.VC90.MFC.MANIFEST.
    INFO: Attempt to probe manifest at C:\Windows\system32\Microsoft.VC90.MFC\Microsoft.VC90.MFC.DLL.
    INFO: Attempt to probe manifest at C:\Windows\system32\Microsoft.VC90.MFC\Microsoft.VC90.MFC.MANIFEST.
    INFO: Did not find manifest for culture Neutral.
   INFO: End assembly probing.
 ERROR: Cannot resolve reference Microsoft.VC90.MFC,processorArchitecture="amd64",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="9.0.21022.8".
ERROR: Activation Context generation failed.
End Activation Context Generation.

=================
Begin Activation Context Generation.
Input Parameter:
 Flags = 0
 ProcessorArchitecture = AMD64
 CultureFallBacks = en-US;en
 ManifestPath = C:\Windows\system32\WerFault.exe
 AssemblyDirectory = C:\Windows\system32\
 Application Config File =
-----------------
INFO: Parsing Manifest File C:\Windows\system32\WerFault.exe.
 INFO: Manifest Definition Identity is Microsoft.Windows.Feedback.Watson,processorArchitecture="amd64",type="win32",version="1.0.0.0".
 INFO: Reference: Microsoft.Windows.Common-Controls,language="*",processorArchitecture="amd64",publicKeyToken="6595b64144ccf1df",type="win32",version="6.0.0.0"
INFO: Resolving reference Microsoft.Windows.Common-Controls,language="*",processorArchitecture="amd64",publicKeyToken="6595b64144ccf1df",type="win32",version="6.0.0.0".
 INFO: Resolving reference for ProcessorArchitecture amd64.
  INFO: Resolving reference for culture en-US.
   INFO: Applying Binding Policy.
    INFO: No publisher policy found.
    INFO: No binding policy redirect found.
   INFO: Begin assembly probing.
    INFO: Did not find the assembly in WinSxS.
    INFO: Attempt to probe manifest at C:\Windows\assembly\GAC_64\Microsoft.Windows.Common-Controls\6.0.0.0_en-US_6595b64144ccf1df\Microsoft.Windows.Common-Controls.DLL.
    INFO: Attempt to probe manifest at C:\Windows\system32\en-US\Microsoft.Windows.Common-Controls.DLL.
    INFO: Attempt to probe manifest at C:\Windows\system32\en-US\Microsoft.Windows.Common-Controls.MANIFEST.
    INFO: Attempt to probe manifest at C:\Windows\system32\en-US\Microsoft.Windows.Common-Controls\Microsoft.Windows.Common-Controls.DLL.
    INFO: Attempt to probe manifest at C:\Windows\system32\en-US\Microsoft.Windows.Common-Controls\Microsoft.Windows.Common-Controls.MANIFEST.
    INFO: Did not find manifest for culture en-US.
   INFO: End assembly probing.
  INFO: Resolving reference for culture en.
   INFO: Applying Binding Policy.
    INFO: No publisher policy found.
    INFO: No binding policy redirect found.
   INFO: Begin assembly probing.
    INFO: Did not find the assembly in WinSxS.
    INFO: Attempt to probe manifest at C:\Windows\assembly\GAC_64\Microsoft.Windows.Common-Controls\6.0.0.0_en_6595b64144ccf1df\Microsoft.Windows.Common-Controls.DLL.
    INFO: Attempt to probe manifest at C:\Windows\system32\en\Microsoft.Windows.Common-Controls.DLL.
    INFO: Attempt to probe manifest at C:\Windows\system32\en\Microsoft.Windows.Common-Controls.MANIFEST.
    INFO: Attempt to probe manifest at C:\Windows\system32\en\Microsoft.Windows.Common-Controls\Microsoft.Windows.Common-Controls.DLL.
    INFO: Attempt to probe manifest at C:\Windows\system32\en\Microsoft.Windows.Common-Controls\Microsoft.Windows.Common-Controls.MANIFEST.
    INFO: Did not find manifest for culture en.
   INFO: End assembly probing.
  INFO: Resolving reference for culture Neutral.
   INFO: Applying Binding Policy.
    INFO: Auto Servicing Policy redirected assembly version.
    INFO: Post policy assembly identity is Microsoft.Windows.Common-Controls,processorArchitecture="amd64",publicKeyToken="6595b64144ccf1df",type="win32",version="6.0.7600.16661".
   INFO: Begin assembly probing.
    INFO: Attempt to probe manifest at C:\Windows\WinSxS\manifests\amd64_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7600.16661_none_fa62ad231704eab7.manifest.
    INFO: Manifest found at C:\Windows\WinSxS\manifests\amd64_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7600.16661_none_fa62ad231704eab7.manifest.
   INFO: End assembly probing.
INFO: Resolving reference Microsoft.Windows.Common-Controls.mui,language="*",processorArchitecture="amd64",publicKeyToken="6595b64144ccf1df",type="win32",version="6.0.7600.16661".
 INFO: Resolving reference for ProcessorArchitecture amd64.
  INFO: Resolving reference for culture en-US.
   INFO: Applying Binding Policy.
    INFO: No publisher policy found.
    INFO: No binding policy redirect found.
   INFO: Begin assembly probing.
    INFO: Did not find the assembly in WinSxS.
    INFO: Attempt to probe manifest at C:\Windows\assembly\GAC_64\Microsoft.Windows.Common-Controls.mui\6.0.7600.16661_en-US_6595b64144ccf1df\Microsoft.Windows.Common-Controls.mui.DLL.
    INFO: Attempt to probe manifest at C:\Windows\system32\en-US\Microsoft.Windows.Common-Controls.mui.DLL.
    INFO: Attempt to probe manifest at C:\Windows\system32\en-US\Microsoft.Windows.Common-Controls.mui.MANIFEST.
    INFO: Attempt to probe manifest at C:\Windows\system32\en-US\Microsoft.Windows.Common-Controls.mui\Microsoft.Windows.Common-Controls.mui.DLL.
    INFO: Attempt to probe manifest at C:\Windows\system32\en-US\Microsoft.Windows.Common-Controls.mui\Microsoft.Windows.Common-Controls.mui.MANIFEST.
    INFO: Did not find manifest for culture en-US.
   INFO: End assembly probing.
  INFO: Resolving reference for culture en.
   INFO: Applying Binding Policy.
    INFO: No publisher policy found.
    INFO: No binding policy redirect found.
   INFO: Begin assembly probing.
    INFO: Did not find the assembly in WinSxS.
    INFO: Attempt to probe manifest at C:\Windows\assembly\GAC_64\Microsoft.Windows.Common-Controls.mui\6.0.7600.16661_en_6595b64144ccf1df\Microsoft.Windows.Common-Controls.mui.DLL.
    INFO: Attempt to probe manifest at C:\Windows\system32\en\Microsoft.Windows.Common-Controls.mui.DLL.
    INFO: Attempt to probe manifest at C:\Windows\system32\en\Microsoft.Windows.Common-Controls.mui.MANIFEST.
    INFO: Attempt to probe manifest at C:\Windows\system32\en\Microsoft.Windows.Common-Controls.mui\Microsoft.Windows.Common-Controls.mui.DLL.
    INFO: Attempt to probe manifest at C:\Windows\system32\en\Microsoft.Windows.Common-Controls.mui\Microsoft.Windows.Common-Controls.mui.MANIFEST.
    INFO: Did not find manifest for culture en.
   INFO: End assembly probing.
INFO: Parsing Manifest File C:\Windows\WinSxS\manifests\amd64_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7600.16661_none_fa62ad231704eab7.manifest.
 INFO: Manifest Definition Identity is Microsoft.Windows.Common-Controls,processorArchitecture="amd64",publicKeyToken="6595b64144ccf1df",type="win32",version="6.0.7600.16661".
 INFO: Reference: Microsoft.Windows.Common-Controls.Resources,language="*",processorArchitecture="amd64",publicKeyToken="6595b64144ccf1df",type="win32",version="6.0.0.0"
INFO: Resolving reference Microsoft.Windows.Common-Controls.Resources,language="*",processorArchitecture="amd64",publicKeyToken="6595b64144ccf1df",type="win32",version="6.0.0.0".
 INFO: Resolving reference for ProcessorArchitecture amd64.
  INFO: Resolving reference for culture en-US.
   INFO: Applying Binding Policy.
    INFO: Auto Servicing Policy redirected assembly version.
    INFO: Post policy assembly identity is Microsoft.Windows.Common-Controls.Resources,language="en-US",processorArchitecture="amd64",publicKeyToken="6595b64144ccf1df",type="win32",version="6.0.7600.16385".
   INFO: Begin assembly probing.
    INFO: Attempt to probe manifest at C:\Windows\WinSxS\manifests\amd64_microsoft.windows.c..-controls.resources_6595b64144ccf1df_6.0.7600.16385_en-us_106f9be843a9b4e3.manifest.
    INFO: Manifest found at C:\Windows\WinSxS\manifests\amd64_microsoft.windows.c..-controls.resources_6595b64144ccf1df_6.0.7600.16385_en-us_106f9be843a9b4e3.manifest.
   INFO: End assembly probing.
INFO: Parsing Manifest File C:\Windows\WinSxS\manifests\amd64_microsoft.windows.c..-controls.resources_6595b64144ccf1df_6.0.7600.16385_en-us_106f9be843a9b4e3.manifest.
 INFO: Manifest Definition Identity is Microsoft.Windows.Common-Controls.Resources,language="en-us",processorArchitecture="amd64",publicKeyToken="6595b64144ccf1df",type="win32",version="6.0.7600.16385".
INFO: Activation Context generation succeeded.
End Activation Context Generation.

=================
Begin Activation Context Generation.
Input Parameter:
 Flags = 0
 ProcessorArchitecture = AMD64
 CultureFallBacks = en-US;en
 ManifestPath = C:\Windows\system32\werui.dll
 AssemblyDirectory = C:\Windows\system32\
 Application Config File =
-----------------
INFO: Parsing Manifest File C:\Windows\system32\werui.dll.
 INFO: Manifest Definition Identity is Microsoft.Windows.Feedback.Watson,processorArchitecture="amd64",type="win32",version="1.0.0.0".
 INFO: Reference: Microsoft.Windows.Common-Controls,language="*",processorArchitecture="amd64",publicKeyToken="6595b64144ccf1df",type="win32",version="6.0.0.0"
INFO: Resolving reference Microsoft.Windows.Common-Controls,language="*",processorArchitecture="amd64",publicKeyToken="6595b64144ccf1df",type="win32",version="6.0.0.0".
 INFO: Resolving reference for ProcessorArchitecture amd64.
  INFO: Resolving reference for culture en-US.
   INFO: Applying Binding Policy.
    INFO: No publisher policy found.
    INFO: No binding policy redirect found.
   INFO: Begin assembly probing.
    INFO: Did not find the assembly in WinSxS.
    INFO: Attempt to probe manifest at C:\Windows\assembly\GAC_64\Microsoft.Windows.Common-Controls\6.0.0.0_en-US_6595b64144ccf1df\Microsoft.Windows.Common-Controls.DLL.
    INFO: Attempt to probe manifest at C:\Windows\system32\en-US\Microsoft.Windows.Common-Controls.DLL.
    INFO: Attempt to probe manifest at C:\Windows\system32\en-US\Microsoft.Windows.Common-Controls.MANIFEST.
    INFO: Attempt to probe manifest at C:\Windows\system32\en-US\Microsoft.Windows.Common-Controls\Microsoft.Windows.Common-Controls.DLL.
    INFO: Attempt to probe manifest at C:\Windows\system32\en-US\Microsoft.Windows.Common-Controls\Microsoft.Windows.Common-Controls.MANIFEST.
    INFO: Did not find manifest for culture en-US.
   INFO: End assembly probing.
  INFO: Resolving reference for culture en.
   INFO: Applying Binding Policy.
    INFO: No publisher policy found.
    INFO: No binding policy redirect found.
   INFO: Begin assembly probing.
    INFO: Did not find the assembly in WinSxS.
    INFO: Attempt to probe manifest at C:\Windows\assembly\GAC_64\Microsoft.Windows.Common-Controls\6.0.0.0_en_6595b64144ccf1df\Microsoft.Windows.Common-Controls.DLL.
    INFO: Attempt to probe manifest at C:\Windows\system32\en\Microsoft.Windows.Common-Controls.DLL.
    INFO: Attempt to probe manifest at C:\Windows\system32\en\Microsoft.Windows.Common-Controls.MANIFEST.
    INFO: Attempt to probe manifest at C:\Windows\system32\en\Microsoft.Windows.Common-Controls\Microsoft.Windows.Common-Controls.DLL.
    INFO: Attempt to probe manifest at C:\Windows\system32\en\Microsoft.Windows.Common-Controls\Microsoft.Windows.Common-Controls.MANIFEST.
    INFO: Did not find manifest for culture en.
   INFO: End assembly probing.
  INFO: Resolving reference for culture Neutral.
   INFO: Applying Binding Policy.
    INFO: Auto Servicing Policy redirected assembly version.
    INFO: Post policy assembly identity is Microsoft.Windows.Common-Controls,processorArchitecture="amd64",publicKeyToken="6595b64144ccf1df",type="win32",version="6.0.7600.16661".
   INFO: Begin assembly probing.
    INFO: Attempt to probe manifest at C:\Windows\WinSxS\manifests\amd64_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7600.16661_none_fa62ad231704eab7.manifest.
    INFO: Manifest found at C:\Windows\WinSxS\manifests\amd64_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7600.16661_none_fa62ad231704eab7.manifest.
   INFO: End assembly probing.
INFO: Resolving reference Microsoft.Windows.Common-Controls.mui,language="*",processorArchitecture="amd64",publicKeyToken="6595b64144ccf1df",type="win32",version="6.0.7600.16661".
 INFO: Resolving reference for ProcessorArchitecture amd64.
  INFO: Resolving reference for culture en-US.
   INFO: Applying Binding Policy.
    INFO: No publisher policy found.
    INFO: No binding policy redirect found.
   INFO: Begin assembly probing.
    INFO: Did not find the assembly in WinSxS.
    INFO: Attempt to probe manifest at C:\Windows\assembly\GAC_64\Microsoft.Windows.Common-Controls.mui\6.0.7600.16661_en-US_6595b64144ccf1df\Microsoft.Windows.Common-Controls.mui.DLL.
    INFO: Attempt to probe manifest at C:\Windows\system32\en-US\Microsoft.Windows.Common-Controls.mui.DLL.
    INFO: Attempt to probe manifest at C:\Windows\system32\en-US\Microsoft.Windows.Common-Controls.mui.MANIFEST.
    INFO: Attempt to probe manifest at C:\Windows\system32\en-US\Microsoft.Windows.Common-Controls.mui\Microsoft.Windows.Common-Controls.mui.DLL.
    INFO: Attempt to probe manifest at C:\Windows\system32\en-US\Microsoft.Windows.Common-Controls.mui\Microsoft.Windows.Common-Controls.mui.MANIFEST.
    INFO: Did not find manifest for culture en-US.
   INFO: End assembly probing.
  INFO: Resolving reference for culture en.
   INFO: Applying Binding Policy.
    INFO: No publisher policy found.
    INFO: No binding policy redirect found.
   INFO: Begin assembly probing.
    INFO: Did not find the assembly in WinSxS.
    INFO: Attempt to probe manifest at C:\Windows\assembly\GAC_64\Microsoft.Windows.Common-Controls.mui\6.0.7600.16661_en_6595b64144ccf1df\Microsoft.Windows.Common-Controls.mui.DLL.
    INFO: Attempt to probe manifest at C:\Windows\system32\en\Microsoft.Windows.Common-Controls.mui.DLL.
    INFO: Attempt to probe manifest at C:\Windows\system32\en\Microsoft.Windows.Common-Controls.mui.MANIFEST.
    INFO: Attempt to probe manifest at C:\Windows\system32\en\Microsoft.Windows.Common-Controls.mui\Microsoft.Windows.Common-Controls.mui.DLL.
    INFO: Attempt to probe manifest at C:\Windows\system32\en\Microsoft.Windows.Common-Controls.mui\Microsoft.Windows.Common-Controls.mui.MANIFEST.
    INFO: Did not find manifest for culture en.
   INFO: End assembly probing.
INFO: Parsing Manifest File C:\Windows\WinSxS\manifests\amd64_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7600.16661_none_fa62ad231704eab7.manifest.
 INFO: Manifest Definition Identity is Microsoft.Windows.Common-Controls,processorArchitecture="amd64",publicKeyToken="6595b64144ccf1df",type="win32",version="6.0.7600.16661".
 INFO: Reference: Microsoft.Windows.Common-Controls.Resources,language="*",processorArchitecture="amd64",publicKeyToken="6595b64144ccf1df",type="win32",version="6.0.0.0"
INFO: Resolving reference Microsoft.Windows.Common-Controls.Resources,language="*",processorArchitecture="amd64",publicKeyToken="6595b64144ccf1df",type="win32",version="6.0.0.0".
 INFO: Resolving reference for ProcessorArchitecture amd64.
  INFO: Resolving reference for culture en-US.
   INFO: Applying Binding Policy.
    INFO: Auto Servicing Policy redirected assembly version.
    INFO: Post policy assembly identity is Microsoft.Windows.Common-Controls.Resources,language="en-US",processorArchitecture="amd64",publicKeyToken="6595b64144ccf1df",type="win32",version="6.0.7600.16385".
   INFO: Begin assembly probing.
    INFO: Attempt to probe manifest at C:\Windows\WinSxS\manifests\amd64_microsoft.windows.c..-controls.resources_6595b64144ccf1df_6.0.7600.16385_en-us_106f9be843a9b4e3.manifest.
    INFO: Manifest found at C:\Windows\WinSxS\manifests\amd64_microsoft.windows.c..-controls.resources_6595b64144ccf1df_6.0.7600.16385_en-us_106f9be843a9b4e3.manifest.
   INFO: End assembly probing.
INFO: Parsing Manifest File C:\Windows\WinSxS\manifests\amd64_microsoft.windows.c..-controls.resources_6595b64144ccf1df_6.0.7600.16385_en-us_106f9be843a9b4e3.manifest.
 INFO: Manifest Definition Identity is Microsoft.Windows.Common-Controls.Resources,language="en-us",processorArchitecture="amd64",publicKeyToken="6595b64144ccf1df",type="win32",version="6.0.7600.16385".
INFO: Activation Context generation succeeded.
End Activation Context Generation.

 

I installed the VC++ 2008 SP1 runtime for x64 and it works now.  Thank you very much!

Hello,

I am compiling a 64 bit dotnet test application on Win XP 64 system.  64 bit is required as I must integrate into a much larger 64 bit application.

I downloaded the LJUD64bitv315.zip file and placed the labjackud.dll in the C:\windows\system32 folder folder as mentioned above.  Also I have used the local property setting for LJUDDotNet as suggested.  Nevertheless I still get the error:

{"Unable to load DLL 'labjackud.dll': This application has failed to start because the application configuration is incorrect. Reinstalling the application may fix this problem. (Exception from HRESULT: 0x800736B1)"}

I am curious about the date stamp on the labjackud.dll in the LJUD64bitv315.zip file as it is dated 9/15/2009.  I thought this was a new release of the 64 bit dll?

Any suggestions?  Is there a way to check/verify the version of the dll?

Thanks

Jim

Finally Found the fix:

Installed the Package:

Microsoft Visual C++ 2008 Redistributable Package (x64)

I had already installed the 2010 version which did not fix the problem.

Perhaps you developed the dlls using 2008 and it requires this package.

 

Recommended correction to the instructions:

The statement, 

"To install, simply unzip and place the LabJackud.dll into the C:\windows\system32 folder, which is where Windows stores 64-bit .dlls. "

Should be changed to,

"To install, simply unzip and place both LabJackud.dll and LabJackWUSB.dll into the C:\windows\system32 folder, which is where Windows stores 64-bit .dlls. "

At least that correction is what was necessary for my configuration.  Labview 2012 64-bit running on Win 7 Pro 64 bit running under VMWare Fusion on a Macbook Air.  

Thanks for the correction.  The instructions were written before the newer version of LabJackWUSB.dll was needed.  I will add that to the instructions.

Hi,

 

I'm using NetBeans 7 for develop AllIO for U3. I placed relevant dlls in system32 folder too.

But I get the following error.

Exception in thread "main" java.lang.UnsatisfiedLinkError: com.labjack.labjackud.LJUDJavaJNI.OpenLabJack(IILjava/lang/String;I[I)I

at com.labjack.labjackud.LJUDJavaJNI.OpenLabJack(Native Method)
at com.labjack.labjackud.LJUD.OpenLabJack(LJUD.java:21)
at labjack.U3_AllIO.runExample(U3_AllIO.java:75)
at labjack.U3_AllIO.main(U3_AllIO.java:243)
Java Result: 1

Please give me a soluiton for this.

Thanks

Currently our Java wrapper only supports 32-bits, so you will need to build a 32-bit Java application that will use the 32-bit UD driver from the installer.

Hello LabJack Support Staff,

I am having issues running the m-file ljud_LoadDriver. I am running Win7 on a x64 system (so much fun, I know) with Matlab R2010a.

Anyways, I have two scenarios producing errors and it both has to do with the dynamic library. Firstly, I will tell you what I have done:

1. I have downloaded and installed Microsoft Visual Studio 2008 Express Edition from vcsetup.exe

2. I downloaded and installed the Microsoft Windows SDK for Windows Server 2008 and .NET Framerwork 3.5

3. I have downloaded and extracted the 64-bit .dlls that you posted into the Windows\System32 folder and replaced the .lib file in the folder that I draw the .h from

4. The mex example works correctly as indicated too

Now, the m-file. I have renamed the header path to the header file location. When I run the file from script, the output is:

 

?? Error using ==> loadlibrary at 368

Failed to preprocess the input file.

 Output from preprocessor is:The command "cl" is misspelled or could not be found.

Error in ==> ljud_LoadDriver at 10

    loadlibrary('labjackud',header);

 

cl.exe is definitely in the folder it should be in (as indicated on the MatLab website): C:\Program Files (x86)\Microsoft Visual Studio 9.0\VC\bin

 

I cannot get past this error. If you have any suggestions, I would greatly appreciate it.

Thanks,

Katalyst

The cl.exe error typically implies an error with how the compiler is set up.  We had another user with the same version of Matlab recently have the same issue.  Please see this response.  Matlab can be tricky to get working but this should give you a starting place. 

I am running LabJack on Win7 64 ultimate.

My PC has 48 GB of RAM due to the memory requirements of my application.

Your original comments state something about everything being okay with 4GB of RAM.

Do I need a special version of labjackud.dll to run on systems with more that 4 GB of RAM.

Also is labjackud a compiled as a debug build or release?

Typically, anything *ud.dll is Debug, is this the case here?

How do I get a Release version?

Thanks

David

 

That version should work for you, but as usual, let us know if you run into any problems and we can help you address them.

Pretty much everything we put up on the website is a release build, even our "beta" .dlls.  UD is just the name we use to refer to that series of products.  There are some cases where we give people debug versions but they are typically sent directly via email to try and resolve a particular issue someone is having.

Good evening,

I am running Matlab R2012b 64-bit on a Windows 7 64-bit system.  When running 'ljud_LoadDriver', I receive the following errors:

 

Error using loadlibrary>lFullPath (line 587)

Could not find file C:\progra~1\LabJack\drivers\labjackud.h.


Error in loadlibrary (line 220)

        header=lFullPath(header);


Error in ljud_LoadDriver (line 10)

    loadlibrary('labjackud',header);

 

I have added labjackud.dll & labjackWUSB.dll to the Windows\System32 folder as well as ran 'mex -setup' in MATLAB, yet I am still receiving the errors.

 

Any help would be greatly appreciated.

 

 

Find where labjackud.h is located on your machine, and try changing the "c:\progra~1\..." line in loadlibrary to exactly match the location of the header file on your machine.

 

Thank you, but now MATLAB is trying to find LCC and cannot do so.  When I run 'ljud_LoadDriver' the error I receive now is:

 

Warning: Shared libraries are not supported on this platform.

Functions that do not have a mexFunction signature may have

unpredictable results. 

> In loadlibrary at 54

  In ljud_LoadDriver at 10 

Error using loadlibrary (line 209)

LCC was not found at C:\Program

Files\MATLAB\R2012b\sys\lcc\bin\lcc.exe.


Error in ljud_LoadDriver (line 10)

    loadlibrary('labjackud',header);

 

As previously stated, I ran 'mex -setup' for Microsoft SDK 7.1

 

 

It looks like MATLAB is still trying to use lcc instead of the Microsoft tools.  Can you provide us with the output you get from mex -setup when selecting the Microsoft SDK.  If it is easier you can email it to us at [email protected].