Benchlink Data Logger 3将无法运行

嗨Alex，1。请在安装软件时尝试以管理员身份登录.2。现在右键单击桌面上的图标并说“以管理员身份运行”而不是双击它。让我知道是否有效



     以下为原文

  Hi Alex,

1.Please try logging as an administrator while installing the software.
2.Now right click on the icon lying on the desktop and say “run as administrator” instead of double clicking on it.

Let me know if that works

工作得很完美！
谢谢！



     以下为原文

  Worked perfectly!  Thank you!

我有一台运行Windows 7 Pro 64位的新计算机。
我安装了Agilent IO库，然后从Agilent CD安装了Benchlink Logger 3程序。
安装没有错误。当我单击桌面上的Benchlink Data Logger图标时，程序将打开并显示一个窗口，其中显示以下错误消息：'Microsoft.Jet.OLEDB.4.0'未在本地计算机中注册.Is
这是Windows 7的问题？



     以下为原文

  I have a new computer running Windows 7 Pro 64 bits. I installed the Agilent IO libraries and then installed the Benchlink Logger 3 program from the Agilent CD. The installs did not have errors.

When I click on the Benchlink Data Logger icon on the desktop, the program opens and appears a windows with the following error message:
'Microsoft.Jet.OLEDB.4.0' is not registered in local machine.

Is it a problem with Windows 7?

我得到了相同的.net错误。
我正在运行Windows 7 Pro 64位。
我最近收到了Data Logger 3 Pro 3.0版和Data Logger 4.0版。
我根据具有管理员权限的说明安装但是在Data Logger 3 Pro中收到未处理的异常.net错误：问题事件名称：CLR20r3问题签名01：datalogger.exe问题签名02：3.0.0.0问题签名03：4b1f4d51问题签名04：
System.Windows.Forms问题签名05：2.0.0.0问题签名06：4f682206问题签名07：151f问题签名08:18问题签名09：System.InvalidOperationException操作系统版本：6.1.7601.2.1.0.256.48数据发生以下错误
Logger 3 vesion 4.0：“Microsoft.Jet.OLEDB.4.0”提供程序未在本地计算机上注册。
我在这个论坛中读到原因是64位对32位，但是没有单独的64位安装可执行文件。



     以下为原文

  I am getting the same .net error.  I am running Windows 7 Pro 64-bit.  I recently received the Data Logger 3 Pro version 3.0 and Data Logger Version 4.0.  I installed per the instructions with admin rights but receive a unhandled exception .net error with Data Logger 3 Pro:

  Problem Event Name:     CLR20r3
  Problem Signature 01:     datalogger.exe
  Problem Signature 02:     3.0.0.0
  Problem Signature 03:     4b1f4d51
  Problem Signature 04:     System.Windows.Forms
  Problem Signature 05:     2.0.0.0
  Problem Signature 06:     4f682206
  Problem Signature 07:     151f
  Problem Signature 08:     18
  Problem Signature 09:     System.InvalidOperationException
  OS Version:     6.1.7601.2.1.0.256.48

The following error occurs on Data Logger 3 vesion 4.0:
The 'Microsoft.Jet.OLEDB.4.0' provider is not registered on the local machine.

I read in this forum that the cause was 64bit vs 32bit, but there are no separate installation executables for 64bit which were provided.

这是旧版BLDL软件的已知问题。
请访问Agilent.com，搜索34830A并下载BLDL Pro 3.3版。
BLDL3的4.3版本可以在34825A下找到。
在34970A / 72A和34980A网页上也可以找到这两者的链接。



     以下为原文

  This is a known problem with older versions of the BLDL software.  Please go to Agilent.com, search for 34830A and download version 3.3 of BLDL Pro.  Version 4.3 of BLDL3 can be found under 34825A.  Links to both of these can also be found on the 34970A/72A and 34980A web pages.

嗨，我已经尝试了以上所有建议和BLDL版本，没有运气。
我仍然得到.NET错误，程序将无法运行。
我也试过修复.NET 4.5.1。
Windows 7 Pro SP1还有其他建议吗？



     以下为原文

  Hi, I've tried all the above suggestions and BLDL versions, and no luck. I still get .NET error and the program will not run.   I also tried repairing .NET 4.5.1.  

Windows 7 Pro SP1

Any other suggestions?

当人们尝试在64位计算机上运行32位安装程序时，通常会出现此错误。目前，我们必须将安装程序分开，一个用于32位操作系统，另一个用于64位操作系统。
很快就会有一个组合安装文件但是现在请下载64位安装文件。



     以下为原文

  People normally get this error when they try to run the 32 bit installer on a 64 bit machine.

Currently we have to separate installers, one for 32bit operating systems, and another for 64 bit operating systems.  Soon there will be just one combined installation file but for now please download the 64 bit installation file.

该软件可以在Windows 7启动器上运行吗？
我打算在上网本上安装。
请指教



     以下为原文

  Can the software run on Windows 7 starter?  I intend to install on a netbook.  Please advise

抱歉。
由于支持Benchlink Data Logger 3所需的所有其他底层.net和企业软件，它仅在Window 7 Pro，Enterprise和Ultimate版本上受支持。



     以下为原文

  Sorry.   Because of all the additional underlying .net and enterprise software required to support Benchlink Data Logger 3, it is only supported on Window 7 Pro, Enterprise, and Ultimate editions.

我有一台运行Windows 7 Home Premium的计算机，它运行Benchlink就好了，即使它似乎不支持该操作系统版本。
我们需要将该计算机用于其他用途，因此安装了I / O库，34970A驱动程序和Benchlink（所有都是最新版本）。
配置例程可以很好地找到数据记录器并与之通信。
Benchlink显然可以看到它，但不能与之沟通。
在尝试添加乐器时，我得到以下5。
与6.沟通时在与地址ASRL1 :: INSTR的工具交互过程中发生错误原因是（数据格式不支持）7。
搜索串行完整的1个仪器找到0个仪器我已经尝试了这个消息线程中给出的建议，包括一个完整的卸载，重新安装具有相同的结果。它只是一个侥幸它工作在
原机还是还有别的东西？



     以下为原文

  I have one computer running Windows 7 Home Premium and it's running Benchlink just fine, even though it does not appear to be supported for that operating system version.  We need to take that computer for another use so installed the I/O library, 34970A driver, and Benchlink (all are latest editions).  The configuration routine can find and communicate with the data logger just fine.  Benchlink apparently can see it, but not communicate with it.  When trying to add an instrument I get the following

5.  Communicating with
6.  Error occurred during interaction with instrument at address ASRL1::INSTR> reason is (Data format Not supported)
7.  Searching serial complete 1 instrument(s) found 0 instrument(s)

I have tried the suggestions given in this message thread, including a complete un-install, re-install with the same results.

Is it just a fluke that it worked on the original machine or is there something else going on?

首先要仔细检查一下，您的仪器rs-232设置和安捷伦I / O库中的PC设置是否匹配。
如果所有设置都匹配并且您仍然遇到问题，则可能与此有关：-------------------------------
--------------------------------------------------
--------------------------------------------------
--------------------------------------------------
------------------------------------使用安捷伦仪器上的RS-232与运行任何微软的笔记本电脑的问题
操作系统症状：上传数据时超时，数据损坏，数据丢失，错误消息原因：PC上使用的RS-232 I / O芯片（UART）只有16字节缓冲区。
如果没有实时流量控制，缓冲区溢出可能会发生，从而导致数据丢失。
如果丢失的字符恰好是换行符，则软件永远不会看到行尾终止符，从而导致超时。
其他缺少的字符可能导致返回的数据错误。
Microsoft串行驱动程序未实现真正的硬件流控制。
它实现了软件驱动程序中的所有流控制。
这使得它易受PCI总线锁定，更高优先级中断和中断禁用的影响。
基于软件的流量控制的原因是历史性的，因为早期的硬件设计非常不可靠：16550 UART有无数的克隆，其中大多数都有缺陷。
Microsoft的唯一解决方案是开发一个尽可能少使用功能的软件驱动程序，因此在驱动程序中完成了硬件流控制。
此时Microsoft无法更改驱动程序以解决此问题。
仅在笔记本电脑上观察到这个问题，可能是由于与电源管理和/或PCMCIA适配器相关的软件开销，但理论上它也可能发生在台式机上。
更快的处理器和更慢的RS-232波特率无法成为令人满意的解决方案。
解决方案：不要将RS-232用于关键任务应用程序。
相反（1）考虑使用内置USB和LAN连接的34972A，或者（2）利用34970A的GPIB端口。
1.82357A USB / GPIB转换器可以连接到便携式PC上的USB端口和34970A上的GPIB端口。
此选项适用于具有USB，Windows 2000,98 SE或XP的笔记本电脑。
Windows 3.1,95和NT不支持USB。
2.使用E5810A LAN到GPIB网关。
网关可以连接到34970A上的GPIB端口，然后连接到PC的LAN（或直接连接到PC的LAN端口）。
LAN网关与Windows®98（SE）/ Me / NT / 2000 / XP兼容。
3.安装PCMCIA GPIB卡。
一些供应商提供PCMCIA GPIB卡，通常支持Windows®98（SE）/ Me / NT / 2000 / XP。



     以下为原文

  First thing to double check is that your instrument rs-232 settings and your PC settings found in Agilent I/O libraries match.  If all of the settings match and you are still having problems it could be related to this:
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Problems Using RS-232 on Agilent Instruments with Laptop PCs running any Microsoft OS


Symptoms: Timeouts, corrupt data, missing data, error messages while uploading data

Cause: The RS-232 I/O chip (UART) used on PCs has only a 16-byte buffer. Without real-time flow control, it is possible for buffer overruns to occur, causing a loss of data. If the missing character happens to be a line feed, timeouts can result from the software never seeing the end-of-line terminator. Other missing characters can cause returned data to be wrong.


The Microsoft serial driver does not implement true hardware flow control. It implements all flow control in the software driver. This makes it susceptible to PCI-bus lockouts, higher priority interrupts and interrupt disables. The reason for the software-based flow control is historical, due to the very unreliable early hardware designs: there were a myriad of clones of the 16550 UART, most of them defective. The only solution for Microsoft was to develop a software driver that used as few features as possible, and hardware flow control was therefore done in the driver. Microsoft is unable to change the driver at this point to fix this problem.

The problem has been observed only on laptop PCs, perhaps due to software overhead associated with power management and/or PCMCIA adapters, but theoretically it could occur on desktop PCs too. Faster processors and slower RS-232 baud rates do not help enough to be a satisfactory workaround.

Resolution: Do not use RS-232 for mission critical applications. Instead (1) Consider using 34972A with USB and LAN connectivity built in OR (2) take advantage of the 34970A´s GPIB port.
1.The 82357A USB / GPIB converter can be connected to a USB port on the portable PC and to the GPIB port on the 34970A. This option will work with laptops that have USB, and Windows 2000, 98 SE, or XP. Windows 3.1, 95 and NT do not support USB.
2.Use an E5810A LAN to GPIB gateway. The gateway can be connected to the GPIB port on the 34970A then attached to the PC´s LAN (or directly to the PC´s LAN port). The LAN gateway is compatible with Windows® 98 (SE)/Me/NT/2000/XP.
3.Install a PCMCIA GPIB card. Several vendors supply PCMCIA GPIB cards and typically support Windows® 98 (SE)/Me/NT/2000/XP.