November 11, 2003

DevCon:Improving the Device Driver Experience

Wow. Couldn't blog during the session because it was so full it was leaking out into the hallway! Way to many people for the session. They are going to run the session again tomorrow in a larger room, but I decided to stick it out and ended up sitting in the front instead of at a table.

Device driver installation is getting cleaner in Longhorn. Most of the compatibility and roll back issues that currently exist in Windows are going to be solved in Longhorn, and they have new tools to assist in the driver installation experience.

Longhorn is also going to have a new level of trust required during the installation experience. All drivers must be signed, but there are ways to sign a driver manually as administrator for a single machine. Can't discuss much more on that right now, but if you have access to some of Microsoft's people you can talk to them directly. (Assuming you have an NDA)

Well, gotta run to the next session. I am sitting stealing some power from some nice ladies in the hallway here and need to get to the next room.

Posted by SilverStr at November 11, 2003 03:00 PM | TrackBack
Comments

So if all drivers must be signed does that mean that 3rd party drivers (ie: the hacked to not suck voodoo drivers (for now-unsupported hardware) and things like the vmware svga/mouse drivers) are not going to be usable?

Posted by: Arcterex at November 12, 2003 11:47 AM

In Longhorn you can self-sign a driver through Authenticode if you wish to trust a driver not signed on behalf of Microsoft. A vendor like VMWare could also get a Class 3 cert and sign the driver themselves, it just won't be trusted as a WHQL approved driver. The dialog will show this different in its text when prompted to the admin installing it. The nice thing about this approach is that its flexible enough while still giving a level of assurance who the owner of the driver is, allowing you to apply the appropriate trust.

Posted by: SilverStr at November 14, 2003 09:17 PM