Also, does the Beo5 show up in the Device Manager in the VM? Does it show whether the driver has installed properly.
Stoobie
Devon,
UK
Also, does the Beo5 show up in the Device Manager in the VM? Does it show whether the driver has installed properly.
Stoobie
I moved the VM image from a Windows 10 to a Windows 7 machine and that worked. There must be something with the VirtualBox settings/driver on the Win 10 machine.
Anyhow - now that the setup i working - should I upgrade to latest CT version (6.84?) or stick to 5.12?
I would say that if it is all working and all the hardware you need to control is in the CT then I'd stick with CT5.12. However, if you find hardware is not available the newer CT would be advisable as more is added with each new version.
I would make a new virtual machine with the newer CT (I believe you can copy the VM you already have instead of going through all the steps) That way you can remove CT5.12 from the new VM and instal a newer CT and move from one to the other without having to uninstal/reinstal the CT each time.
Using a newer CTshould update the Software Version on the Beo5. If it does, it may no longer be compatible with CT5.12.
Stoobie
You must be logged in as a BeoWorld member to post replies to forum threads.
Register to access the forums, reference material, and exclusive member benefits — including our monthly prize draw.
Become a Member