In the DDK, you can get the HCL test suite for video drivers. If you pass this suite, you're sweet. Given enough perseverance and a few changes to the way WinVNC implements things, you can get the "Designed for Windows" logo.
http://www.microsoft.com/hwdev/driver/default.asp The driver verifier is the thing that does most of the work. Just beware that this *is not* meant for production systems. The driver verifier will blue screen you at the first opportunity after *any* driver has done something bad or drop you into a remote kernel debugger. Exercise the driver with devctl and watch the world turn blue, unless you've done a really excellent job on programming it. If only every device manufacturers was forced to do this step. Andrew -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of James ''Wez'' Weatherall Sent: Tuesday, 5 March 2002 2:25 AM To: [EMAIL PROTECTED] Cc: VNC-LIST Subject: Re: winvncdrv new version available [snip] Essentially, the display driver is the way WinVNC should have operated from the beginning, but since it works only on NT and could cause system instability, we opted for the hint route instead, which is more portable (to Win98, for example) and cannot crash the OS. (Note that Rudi's version uses a hook driver that I've never seen crash a system, so the instability point is probably moot). [snip] --------------------------------------------------------------------- To unsubscribe, mail [EMAIL PROTECTED] with the line: 'unsubscribe vnc-list' in the message BODY See also: http://www.uk.research.att.com/vnc/intouch.html ---------------------------------------------------------------------
