嗨，我想让我们的82357B GPIB-USB适配器在虚拟机中工作。
我在ubuntu 12.04主机（3.11内核）上使用VirtualBox 4.2.16（带扩展包，但问题是否相同）。
在vm中，我使用的是win7-x64并安装了连接专家16.3.17914.4。
就设备管理器而言，设备工作正常：我在vbox中创建了所谓的过滤器，允许从vm内访问两个USB设备。
“Both both”，因为设备在由驱动程序配置时更改了u*** ID。
配置完成后，设备管理器会显示健康的“Agilent Technologies 82357B”。
但是连接专家显然有这个配置的问题......它确实在其树中显示“USB / GPIB（GPIB0）”设备但是带有红色x。
当我右键单击它并选择“刷新此设备”然后它会尝试，但在详细信息中显示“
通信失败”和“错误：ResourceNotFound”。
它还会将一些内容记录到Windows的事件查看器中，从“IocAgent.ReadAndValidateInterfaceEntry：INTF4的验证失败：计算机上不存在串行接口编号3”，以“VOC”作为源。
第二个错误看起来也很有趣：“ag357i [Pid /
tid = 2088/1616]：错误，OpenU***IntfDevice（）：CreateFile（1）失败w / err = [5] on [\？ u***＃vid_0957＆amp; pid_0718＃my52433349
＃{a5dcbf10-6530-11d2-901f-00c04fb951ed}]”。
错误5是“访问被拒绝”。
AFAICT路径是正确的，根据设备管理器和Windows注册表，至少所有元素都是正确的。
我已经将完整的日志附加为.txt和.evtx（windows的本机事件查看器格式）。
通过在刷新接口的同时监视主机上的相应总线，我确实没有向设备发送u***数据包。
该设备在具有原生窗口7的另一台机器上工作正常。任何想法？
refresh.txt11.0 KB
以上来自于谷歌翻译
以下为原文
Hi,
I am trying to get our 82357B GPIB-USB adapter to work in a virtual machine.
I am using VirtualBox 4.2.16 (with the expansion pack but the problems w/o it are the same) on a ubuntu 12.04 host (3.11 kernel).
In the vm I am using win7-x64 and have connection expert 16.3.17914.4 installed.
As far as the device manager is concerned, the device works fine:
I have created so-called filters in vbox that allow both u*** devices to be accessed from within a vm.
"Both" because the device changes u*** ids while being configured by the driver.
After configuration the device manager shows a healthy "Agilent Technologies 82357B".
But connection expert obviously has problems with this configuration...
It does show a "USB/GPIB (GPIB0)" device in its tree but with a red x.
When I right-click on it and select "Refresh This Device" then it tries to, but shows "There was a communication failure" and "Error:
ResourceNotFound" in the details.
It does also log some stuff into windows' event viewer, starting with
"IocAgent.ReadAndValidateInterfaceEntry: Validate of INTF4 failed: Serial interface number 3 is not present on the computer" with "VOC" as source.
The second error also looks interesting: "ag357i[Pid/Tid=2088/1616]: Error, OpenU***IntfDevice():CreateFile(1) failed w/err=[5] on [\?u***#vid_0957&pid_0718#my52433349#{a5dcbf10-6530-11d2-901f-00c04fb951ed}]".
Error 5 is "access denied".
AFAICT the path is correct, at least all elements are correct according to the device manager and the windows registry.
I've attached the complete log as .txt and .evtx (windows' native event viewer format).
I did verify that no u*** packet is sent to the device by monitoring the respective bus on the host while refreshing the interface.
The device works fine on another machine with native windows 7.
Any ideas?
附件
举报
