D-Link Forums
Software => D-ViewCam => Topic started by: Natey2 on December 22, 2015, 02:12:20 PM
-
I got D-Link D-ViewCam v3.6.4 (DCS-100 with Device Pack Version 1.6.8 ) to run fine in a Hyper-V Virtual Machine:
The .vhd VM I created was a Windows 8.1 image, with 4GB RAM and 2 Virtual Processors.
I suspect it will work fine with less resources.
This means I can run D-ViewCam on my desktop PC (Intel Core i7, Windows 10 Pro, 16GB RAM) without turning off UAC for the main desktop PC.
(Turning off UAC will disable a number of things in Windows 10, and is generally not recommended by MS).
The VM instance has UAC turned off to facilitate the operation of D-ViewCam.
The Video Storage area is on a disk in the main desktop PC, accessible from the VM instance via a network-mapped drive letter.
ref: How to Create and Run Virtual Machines With Hyper-V: http://www.howtogeek.com/196158/how-to-create-and-run-virtual-machines-with-hyper-v/ (http://www.howtogeek.com/196158/how-to-create-and-run-virtual-machines-with-hyper-v/)
-
Awesome, thanks for posting about this. ;)
-
I built a Windows XP SP3 Virtual Machine (1GB total RAM, 2 virtual processors), and D-ViewCam 3.6.4 runs fine in it (under the control of Windows 10 Pro Hyper-V). It's great to be able to see/use the D-ViewCam main console monitor in a window'ed environment instead of Full-Screen
FYI.
-
Kewl. Glad it's working. Enjoy. ;)
-
MS broke the operation of the vEthernet switch (Hyper-V VM network adapter/switch for external connections) in their latest Windows 10 1709 update, that will prevent the VM from accessing the internet, or network resources on the host PC.
If you use DVC and want to continue using it in a VM (like I do), see the fix at http://social.technet.microsoft.com/Forums/windows/en-US/7cdd3227-4405-4e3a-933b-806b7f3f7c0d/hyperv-switch-issues-after-windows-10-1709-update?forum=win10itprovirt (http://social.technet.microsoft.com/Forums/windows/en-US/7cdd3227-4405-4e3a-933b-806b7f3f7c0d/hyperv-switch-issues-after-windows-10-1709-update?forum=win10itprovirt)
-
Thanks for sharing this. Hope this helps future users.
Enjoy. ;)
MS broke the operation of the vEthernet switch (Hyper-V VM network adapter/switch for external connections) in their latest Windows 10 1709 update, that will prevent the VM from accessing the internet, or network resources on the host PC.
If you use DVC and want to continue using it in a VM (like I do), see the fix at http://social.technet.microsoft.com/Forums/windows/en-US/7cdd3227-4405-4e3a-933b-806b7f3f7c0d/hyperv-switch-issues-after-windows-10-1709-update?forum=win10itprovirt (http://social.technet.microsoft.com/Forums/windows/en-US/7cdd3227-4405-4e3a-933b-806b7f3f7c0d/hyperv-switch-issues-after-windows-10-1709-update?forum=win10itprovirt)