toggle quoted messageShow quoted text
But hyper-v on win10 require you to connect to rdp?
Skickades från E-post för Windows 10
While this topic is a bit old, I must respectfully disagree. I was able
to get an ISO image of 1703, boot it up, enable narrator, choose the
type of windows installation I wanted, and have windows fully booted. I
carried this out on a windows 8.1 samsung, with intel audio drivers,
using the latest, at the time, VMWARE player.
On 08/08/17 11:16 AM, J.G wrote:
> This weekend I played whith virtualisation programs and tested all 3
> major players (VB, VM ware and Hyper-v from Microsoft). My results are
> interesting but also I have expected some of them. As I saw some months
> ago, VB semms to be the least accessible program due to Qt GUI which it
> has and completely inaccessible window where you can manage your VMs.
> Hyper-V and VM ware are accessible, so it means, you can manage VM
> (start/stop it, add/remove removable devices etc)
> But the most important result is that: I found, that until W10 is not
> fully installed into VM, you cannot use Narrator or any other screen
> reader due to audio issues. it means that you can start setup, but when
> you are going to press ctrl + windows + enter, Narrator will probably be
> started but you would not hear anything. Does anybody know, why does
> this happen? I have one explanation but do not know if it was correct.
> It seems, that "slim Windows" - a package which is running during
> installation, does not have or does not recognise audio drivers of
> virtual software. Am I correct?
> Second question is for MS staff if they track this list. is it possible
> to include this feature into next update of a system? probably it will
> be rs4.
> Best regards, Jožef