U2701A IVI驱动程序不起作用

你好，我发现U2701A IVI驱动程序有一种非常奇怪的行为。
我正在使用两台机器，都运行Windows XP sp3。
其中之一是生产机器，其范围插入其中。
另一个是我自己的开发PC。
我正在使用Windows的远程桌面协议连接到生产计算机。
我运行范围的最新驱动程序：1.3.5.0根据我如何打开Windows会话，我得到一个不同的行为：案例1：在本地打开一个会话（在插入范围的机器上）=>一切正常案例2
：在本地打开会话，然后通过RDP连接到该会话=>一切正常案例3：通过RDP打开会话=> IVI驱动程序不起作用（见下文）案例4：通过RDP打开会话，然后连接到该会话
session local => IVI驱动程序不起作用对于案例3和4，这里是对正在发生的事情的描述。
这是有效的： - 查询* IDN？
使用Agilent Interactive IO或NI等效 - 将示波器与Agilent Measurement Manager一起使用 - 在仿真模式下与IVI驱动程序通信但这不起作用： - 通过IVI驱动程序与labview或C通信到物理设备。
为了初始化设备，C程序只给我一个错误0. Labview产生一个“（Hex 0x80004003）无效指针。”
错误。
-----最后这个问题并不重要，因为我现在该如何避免它。
我在这里写的主要是为了记录。
但这种行为可能是由于驱动程序本身造成的吗？
我连接了很多其他仪器，没有一个给我带来这样的困难！编辑：Bap2703于2013年8月6日上午9:43



     以下为原文

  Hello,

I found an extremely weird behavior with the U2701A IVI driver.

I am working with two machines, both running windows XP sp3. One of them is the production machine with the scope plugged to it. The other one is my own dev PC. I am using Remote Desktop Protocol from Windows to connect to the production machine.
I run the latest driver for the scope: 1.3.5.0

Depending on how I open the windows session, I get a different behaviour:

Case 1: opening a session locally (on the machine where the scope is plugged) => everything works
Case 2: opening a session locally, then connecting to that session through RDP => everything works
Case 3: opening a session through RDP => IVI driver doesn't work (see below)
Case 4: opening a session through RDP, then connecting to that session locally => IVI driver doesn't work



For case 3 and 4 here is a description of what's happening.

This is working:
- Querying *IDN? with Agilent Interactive IO or NI's equivalent
- Using the scope with Agilent Measurement Manager
- Communicating with the IVI driver in simulation mode

But this is not working:
- Communicating to the physical device through the IVI driver, either with Labview or in C.

I fail to initialize the device, a C program just give me an error 0.  
Labview produces a "(Hex 0x80004003) Invalid pointer." error.

-----

At the end this issue is not critical since I now how to avoid it. I am writing here mainly for the record.
But can this behavior be due to the driver itself? I have many other instruments connected, none of them caused me this kind of difficulties!

Edited by: Bap2703 on Aug 6, 2013 9:43 AM