search for: whql

...39;t matter? > > > > Let me explain how it works: > We don't make any difference between server or client platforms when > building our drivers. Initially, all the files, mentioned above (inf, > cat, sys, and pdb), are absolutely the same. Then the files go to QE for > WHQL testing. QE tests the same drivers on both, desktop and server > platforms, and creates two different submissions files for sending them > to WHQL dashboard togather with the original "cat" file. > As the result, we have two different cat files created from the same > original...

...guori <aliguori at amazon.com> >> >> See https://issues.oasis-open.org/browse/VIRTIO-16 although it >> was prematurely closed. > > The reason it was closed is described in the comments. and I quote: > " I think anyone can use a different subsystem vendor id and whql the > driver. virtio-102 will make this even easier, by making the subsystem > id flexible. Let's close this and re-open if someone tries to do this > and runs into a problem. " > > Look here for example: > https://github.com/YanVugenfirer/kvm-guest-drivers-windows/blob/m...

...guori <aliguori at amazon.com> >> >> See https://issues.oasis-open.org/browse/VIRTIO-16 although it >> was prematurely closed. > > The reason it was closed is described in the comments. and I quote: > " I think anyone can use a different subsystem vendor id and whql the > driver. virtio-102 will make this even easier, by making the subsystem > id flexible. Let's close this and re-open if someone tries to do this > and runs into a problem. " > > Look here for example: > https://github.com/YanVugenfirer/kvm-guest-drivers-windows/blob/m...

...gt; > > Let me explain how it works: > > We don't make any difference between server or client platforms when > > building our drivers. Initially, all the files, mentioned above (inf, > > cat, sys, and pdb), are absolutely the same. Then the files go to QE for > > WHQL testing. QE tests the same drivers on both, desktop and server > > platforms, and creates two different submissions files for sending them > > to WHQL dashboard togather with the original "cat" file. > > As the result, we have two different cat files created from the sam...

From: Anthony Liguori <aliguori at amazon.com> See https://issues.oasis-open.org/browse/VIRTIO-16 although it was prematurely closed. Red Hat has non-redistributable Windows drivers and Microsoft will not allow anyone else to WHQL certify drivers using that vendor ID. That makes it impossible to use virtio drivers with a Windows guest without changing the vendor ID. Cc: Matt Wilson <msw at amazon.com> Cc: Rusty Russell <rusty at rustcorp.com.au> Cc: Michael Tsirkin <mst at redhat.com> Signed-off-by: Antho...

From: Anthony Liguori <aliguori at amazon.com> See https://issues.oasis-open.org/browse/VIRTIO-16 although it was prematurely closed. Red Hat has non-redistributable Windows drivers and Microsoft will not allow anyone else to WHQL certify drivers using that vendor ID. That makes it impossible to use virtio drivers with a Windows guest without changing the vendor ID. Cc: Matt Wilson <msw at amazon.com> Cc: Rusty Russell <rusty at rustcorp.com.au> Cc: Michael Tsirkin <mst at redhat.com> Signed-off-by: Antho...

Hi, recently Ive installed Windows 2008 x64 HVM domain on Xen 4.0. On xen wiki is info: Support for Citrix WHQL-certified Windows PV drivers, included in XCP (Xen Cloud Platform). Xen Cloud Platform: So I installed them on Windows 2008 x64 domain and its not able to boot anymore: File: \windows\system32\Drivers\xevtchn.sys Status: 0xc0000428 Info: Windows cannot verify the digital signature for this fil...

Hi, recently Ive installed Windows 2008 x64 HVM domain on Xen 4.0. On xen wiki is info: Support for Citrix WHQL-certified Windows PV drivers, included in XCP (Xen Cloud Platform). Xen Cloud Platform: So I installed them on Windows 2008 x64 domain and its not able to boot anymore: File: \windows\system32\Drivers\xevtchn.sys Status: 0xc0000428 Info: Windows cannot verify the digital signature for this fil...

why is it so hard to get signed virtio drivers? is it politics? a license issue? can someone with involved with or knows of these decisions comment? dont want to start a thread of speculation. we all know all where that leads and i dont want it drowing out any answers.

...e explain how it works: > > > We don't make any difference between server or client platforms when > > > building our drivers. Initially, all the files, mentioned above (inf, > > > cat, sys, and pdb), are absolutely the same. Then the files go to QE for > > > WHQL testing. QE tests the same drivers on both, desktop and server > > > platforms, and creates two different submissions files for sending them > > > to WHQL dashboard togather with the original "cat" file. > > > As the result, we have two different cat files creat...

...om> > >> > >> See https://issues.oasis-open.org/browse/VIRTIO-16 although it > >> was prematurely closed. > > > > The reason it was closed is described in the comments. and I quote: > > " I think anyone can use a different subsystem vendor id and whql the > > driver. virtio-102 will make this even easier, by making the subsystem > > id flexible. Let's close this and re-open if someone tries to do this > > and runs into a problem. " > > > > Look here for example: > > https://github.com/YanVugenfirer/kv...

>>> On 2010/07/07 at 12:18, benco <benco@acid.sk> wrote: > No, I don''t like testsigning - this is the main reason why I want to use > Citrix driver. GPLPV driver works fine for me and if there would be a way > to use it without testsigning on, I would be happy with it. > Why don''t you like testsigning? -Nick -------- This e-mail may contain

...te: > From: Anthony Liguori <aliguori at amazon.com> > > See https://issues.oasis-open.org/browse/VIRTIO-16 although it > was prematurely closed. The reason it was closed is described in the comments. and I quote: " I think anyone can use a different subsystem vendor id and whql the driver. virtio-102 will make this even easier, by making the subsystem id flexible. Let's close this and re-open if someone tries to do this and runs into a problem. " Look here for example: https://github.com/YanVugenfirer/kvm-guest-drivers-windows/blob/master/NetKVM/NDIS5/wxp/netkvm...

Hi. I have the same problem, which described in: http://lists.xensource.com/archives/html/xen-users/2010-07/msg00241.html I''m using Debian Squeeze (2.6.32-5-xen-amd64) in Dom0, Xen 4.0.1-rc6, Windows 2008, 2003 x86_64 in domU After installing drivers from http://www.xen.org/files/XenCloud/Software/0.5/XCP-base-0.5.iso, system stops on progress bar in normal boot, but ok in safe mode. In

I think one - maybe final? - problem. How can I tell the difference between drivers for "client" versions of Windows (eg. Windows 7) and server versions of Windows (eg. Windows 2008 Server)? It seems in many or most cases the drivers are identical, eg: $ md5sum viostor/2k12/amd64/* viostor/w8/amd64/* bbe250c13bf891fd7292ccab9908a63a viostor/2k12/amd64/viostor.cat

...this. > > Maybe this doesn't matter? > Let me explain how it works: We don't make any difference between server or client platforms when building our drivers. Initially, all the files, mentioned above (inf, cat, sys, and pdb), are absolutely the same. Then the files go to QE for WHQL testing. QE tests the same drivers on both, desktop and server platforms, and creates two different submissions files for sending them to WHQL dashboard togather with the original "cat" file. As the result, we have two different cat files created from the same original one. As far as I r...

...#39;: quad buffer and active stereoscopy, synchronization ... The results, for all FirePro drivers (of this year); I can''t get the quad buffer/active stereoscopy feature. But they work on a native installation. The only driver that allows this feature is a Radeon HD driver (Catalyst 12.10 WHQL). But this driver becomes unstable when an application using active stereo and synchronization is closed: -The synchronization between two computers is lost. -The CCC can crash when the synchronization is made again. Someone have any clues about this? Thanks, Aurelien _______________________...

Hi, I have been using syslinux on my portable disk with success on many types of machines (both bios boot and EFI boot) I however hit a small issue recently If I use menu.c32, on some UEFI systems (HP) the menu does not appear after the vendor splash screen. The system however goes ahead and after the timeout configured in the menu system syslinux boots the kernel. I can then (after kernel

On Thu, Oct 29, 2015 at 10:33:57AM +0200, Yan Vugenfirer wrote: > > On 29 Oct 2015, at 10:28, Richard W.M. Jones <rjones@redhat.com> wrote: > > On Thu, Oct 29, 2015 at 11:05:42AM +1100, Vadim Rozenfeld wrote: > > > > Seems like looking at this field in the .inf file is better than our > > current approach of matching path names. > > You just need to

...g it. Their > input / comments might be helpful, not only for this particular case > but for others, and for improving both, the UEFI implementations in HP > machines and (vesa)menu.c32 under UEFI. > > Regards, > Ady. > > PS: MS requires 1024x768 32bpp as minimum GOP mode in WHQL. I would not > be surprised if some UEFI Class 3 systems end up not supporting > 640x480. > > >> _______________________________________________ >> Syslinux mailing list >> Submissions to Syslinux at zytor.com >> Unsubscribe or set options at: >> http://www...