I tried also to reverse the scenario installing the TV server on the virtualized client, it was too slow That's all, and it's the short version of the story, I tried a lot of variations before having a satisfactory result, including Hyperview setups (completely useless because the lack of a good VGA support and the need of an external SW to route the USB devices ), virtualbox 4.x, working but degrading the video quality, virtual box 5.x I had just a black screen on client on my setup, but could be working on different HW. Step 6 can be completely avoided if you're going to use a network based remote (say an android phone+ a remote control sw), or if you use a wireless mouse.
1) Started from my working configuration SSE2008r2/VHS2011 with dvblink (4.1.1 ) installed, it was already working and sharing TV to other WMC/Kodi/Emby/web clientsĢ) installed Vmware 10 on server (I tested it also on W10, no problem at all, I still have to test if VMware 11 makes any difference).ģ) Installed ThinPC + the needed components (MUIs and WMC)Ĥ) configured the Unity mode (the way VMware calls its version of XPmode)ĥ) installed the dvblink network client on the virtual ThinPC and configured it's own WMC to use it)Ħ) the most boring part was to configure the IR remote to talk with the client ( I used eventghost+ the network sender plugin on server and eventghost+ network receiver+MCE plugins on the virtual machine.
0 kommentar(er)
