Support

I'm testing, how my application behaves when there is a network problem between VirtualHere server and client. After connection is lost between VirtualHere server and client, client side remove the usb device, but it seems that onClientBeforeUnbind and onClientAfterUnbind events are not executed when connection is lost.

I purchased VirtualHere because I want to be able to use my Momo Racing wheel with my SteamLink. First off, I have to say the documentation for VirtualHere is terrible (non-existent?) After struggling to figure out how to even connect the damn thing to my SteamLink, I finally got it to show in the list of hubs while streaming. Now the problem is that the wheel and pedals are being detected incorrectly.

I've setup a VirtualHere server that's working fine with a Windows 10 machine. But when I try to use it on Windows 7, here is what I observe:

- The Server running on a RaspberryPi3 iLinux OS gets detected - AutoFindHubs is turned Off and I have specified the Server IP.
- 2 out of 3 devices connected to the RaspberryPi show up in the drop down in the Client running on Win7
-- Mouse - detected
--Keyboard - detected
-- USB-Serial FTDI device - Not Detected

- The Client running on Win7 also runs Symantec Anti-Virus and VPN software.

This seems to be an obvious windows issue and nothing to do with VirtualHere client itself.

I have two windows 10 machines (one desktop, one laptor) and one windows 7 machine which is a laptop. On both laptops the client will auto find the server and display everything while the win10 desktop never finds it. I can specify the address of the hub and everything works fine.

Any ideas what could cause this? I assume its something to do with windows network settings but I can't seem to find anything different between the two win 10 machines.

Hello,

I was using vhusbdarm 3.4.7 since September on a dd-wrt router without problem. I have decided to upgrade the binary to the lastest version 3.5.5

For the same config or another clean, it doesn't work on the same machine. If I revert back to 3.4.7 it works again.

Here is the syslog:

Hi. QNAP TS-212 + printer CANON MG5140. I'm using the licensed version of V3.4.7. Only part of the image or text is printed. If I connect the printer to my computer directly, it prints normally. The driver reinstalled, NAS rebooted, the application itself also reinstalled (on NAS and PC) - nothing helps.

We're looking to potentially deploy a number of servers to embedded devices. If so, ideally we would be able to automate this via our build process.

Some questions:

1. Is there a floating license option?
2. Is there a way to activate the license from the command line?

It will be difficult to automate deployment to devices with a specific serial number; especially if we have to do this via a GUI-based client.

Thanks!

Hi,
I am looking to buy a license but first I need to know what happens if my embedded board dies, or I decide to change to another one because the specs aren't good enough, do I have to buy a new license or is it possible to reset the license?

Thanks
Oscar

Ubuntu GNOME 3.26.2

The client (vhuit64) runs as expected and shows the connected USB device (connected to a Synology NAS).

However the terminal window starts with a warning (that may not be serious):

(vhuit64:8640): IBUS-WARNING **: The owner of /home/dd/.config/ibus/bus is not root!

After "using" it with the menu, it fills the terminal every few seconds with something like:

*** WARNING: Received 6 packets; Accepted 1 packets; Rejected 5 packets because of interface mismatch

And there is no trace of any local USB device.

Hi There

our company is very pleased to find your product, if it works as described, we will require many licences

I have paid for a full licence

I have downloaded and installed

VIRTUALHERE SERER and installed on a Windows 10 Desktop
VIRTUALHERE Client on a MS Surface Pro 3

The USB device we wish to use with your software is recognized by server and appearsto connect with no errors ( Log)

On the client machine USB HUB is visible , as is the USB Device

PROBLEM