Support

Have a funny one here...

We need to support some old WindowsXP specific Applications that need to use a MODEM to communicate with remote embedded hardware. We're running the VirtualHere Server on Ubuntu 64bit with a Prolific USB to Serial Adapter with a Serial MODEM attached to that. Ubuntu dmesg output lists the Prolific USB to Serial Adapter as a pl2303 device.

Opening the Prolific USB to Serial Device via the VirtualHere USB Hub results in an instant BlueScreenOfDeath on the WindowsXP PC.

Hey all,

the noAvahi-server is working as expected, but when i try to start the avahi version, the syslog comes up with following message:

Mar 29 11:32:27 carambola2 user.err vhusbdar7x9xa: Failed to create AVAHI client: Daemon not running


Hi,
i want to use a Carambola2 to connect my Dslr via VirtualHere and the Windows client. The Carambola2 is an "OpenWrt-Device".

If i run the Server Version with avahi-support (vhusbdar7x9xa) the following message appears:
can't load library 'libdbus-1.so.3'

Hi,
I installed VirtualHere USB Sharing on my Synology NAS (RS212) and so far everything went fine. However it can not start:

Tue Feb 4 22:44:10 CET 2014 Starting VirtualHere…
/volume1/@appstore/VirtualHere USB Sharing/vhusb: error while loading shard libraries: libavahi-client.so.3: cannot open shared object file: No such file or directory
Tue Feb 4 22:44:10 CET 2014 Failed to start

What can I do? Is there any package that includes libavahi-client.so.3. The core and common library is located in /lib/.

Thanks for your help.

<p>Hi,
</p>
<p>starting the OEM command line version of the server on a Ubuntu 13.10 server<br />
I get the command prompt again, and the following in /var/log/syslog:
</p>
<p>Feb 1 23:23:29 karl-heinz vhusbdox86: >>> Starting v1.7.8 (Built: Jan 29 2014, 09:29:37)<<<<br />
Feb 1 23:23:29 karl-heinz vhusbdox86: Using default configuration /home/hoe/config.ini<br />
Feb 1 23:23:29 karl-heinz vhusbdox86: Serial:d0278869afc9<br />

VirtualHere USB Server NAS License v1r4

VirtualHere USB Server (hereafter referred to as "Software") is licensed to share USB devices on a per server basis. Trial versions of this Software are limited to sharing 1 device. If you continue to use the Software after 10 days you must purchase a license.

You may:

- Install and use one instance of this Software on this NAS device. There is no limitation on the number of clients that can connect to the Software installed on this NAS.

You may not:

The VirtualHere client license can be displayed by right clicking on USB Hubs -> About -> License. It applies to the OSX and Windows editions of the Client. It will display the following text:

VIRTUALHERE USB CLIENT LICENSE v1
-------------------------------------

VirtualHere hereby gives you a worldwide non-exclusive license to use the software "VirtualHere USB Client" (Software)
according to the following conditions:

You may:
- Install and use the Software on an unlimited number of computers with no payment required.

This is the license for the VirtualHere USB Server. The NAS edition of the VirtualHere USB Server has a different license. The license can be displayed by passing the -l argument to the server. This will show the license below:

VirtualHere USB Server License v2
------------------------------------------

VirtualHere hereby gives you a worldwide non-exclusive license to use the software "VirtualHere USB Server" (Software) according to the following conditions:

You may:

Hi all,

<p>After messing around with the client exe file and extracting the included dpinst, I got stuck.<br />
My idea was to distribute the VirtualHere client (drivers) with WPKG. The execution of the client application (tray icon) works, but as soon as the user wants to connect to a certain USB device, administrator privileges are requested.
</p>
<p>Some ideas anyone? Maybe some "silent installation" switches have to be set?
</p>
<p>Thank you.</p>