BASICCOLOR DISPLAY SOFTWARE SERIAL
Maybe drivers at the host level do the USB-Serial conversion, taking control of the serial bus, then pass the USB device to the VM, which tries to do the USB-Serial conversion, but the serial bus is already under the host control. I feel it's related to the way the hypervisor is presenting the device to the VM guest OS, and the USB/COM ports thing, but I can't find much more infos about that. I'm quite running out of ideas to try at this point, apart from setting up a dual-boot on my MacBook, but I would prefer to make it work in a VM. I tried with USB 3.0 enabled and disabled.
BASICCOLOR DISPLAY SOFTWARE INSTALL
I made a clean Win 10 install in Parallels on my MacBook to rule out specific VirtualBox issue, the probe is seen correctly by the Devices Manager but still not discovered in LightSpace. I pasted the VM to my workstation and ran the VM with my workstation as the VirtualBox host to rule out MacBook or USB port specific issue, still no luck. I wiped the VM and made a clean Win 8.1 installation, then installed the up-to-date generic FTDI drivers that Ted Aspiotis refered to on LiftGammaGain, to clean the mess and rule out driver version or conflict issue, but still no luck. I uninstalled basICColor display software to make sure it isn't preventing the probe to connect to LightSpace, asked basICColor to send the drivers without the software, and re-installed the drivers. The DISCUS is connecting without issue within basICColor display software, but still not discovered in LightSpace.
In the VM (VirtualBox Win 8.1 guest running in High Sierra host, USB set to 2.0) the device is seen as "other device" named "DISCUS" and missing drivers, so I assumed FTDI drivers were needed.īasICColor recommends to install the probe drivers through their basICColor display software, so I did that. The device is seen in the Windows Devices Manager as "USB Serial Converter" with FTDI drivers. The DISCUS probe is working flawlessly within native Win 8.1 on my workstation, no need to install any driver. Networking was also taken care of, Resolve connexion is successfully set up. My other probe, an i1 Pro 2, is working well in the VM. The usual suspects (DISCUS checked in the Discoverable Probes, license allows to use a DISCUS, DISCUS rotated to first I've been trying to make my DISCUS work within a VM to be able to perform calibration using my MacBook, but unfortunately it didn't go so well. I'm wondering if there are any users around here who would use a DISCUS in a Virtual Machine on a MacBook Pro?
0 kommentar(er)
