Eugene Lin and Jason Cobb - Windows Plug and Play
- Posted: Jan 18, 2006 at 11:56 AM
- 122,435 Views
- 36 Comments
Download
How do I download the videos?
- To download, right click the file type you would like and pick “Save target as…” or “Save link as…”
Why should I download videos from Channel9?
- It's an easy way to save the videos you like locally.
- You can save the videos in order to watch them offline.
- If all you want is to hear the audio, you can download the MP3!
Which version should I choose?
- If you want to view the video on your PC, Xbox or Media Center, download the High Quality WMV file (this is the highest quality version we have available).
- If you'd like a lower bitrate version, to reduce the download time or cost, then choose the Medium Quality WMV file.
- If you have a Zune, WP7, iPhone, iPad, or iPod device, choose the low or medium MP4 file.
- If you just want to hear the audio of the video, choose the MP3 file.
Right click “Save as…”
- Mid Quality WMV (Lo-band, Mobile)
- WMV (WMV Video)
Ever wonder what's really going on when you attach a peripheral device to your computer (running Windows XP or Vista)? Well, we wanted to find out the low level truths about Plug and Play in Windows. Who else better to talk to than Eugene Lin and Jason
Cobb, the Plug and Play Guys ( Eugene is a Program Manager and Jason is a dev lead, both are on the Device Management and Installation team ). Join us ( Charles Torre and special guest Channel 9 correspondent/Technical Evangelist Jeremy Mazner ) as we discuss
how PnP works and what's new for Vista in this most interesting and oft overlooked killer feature of Windows.
Comments Closed
Comments have been closed since this content was published more than 30 days ago, but if you'd like to continue the conversation,
please create a new thread in our Forums,
or
Contact Us and let us know.
Follow the Discussion
Only thing I'm noticing in this video is that the sound volume is really really low....and my speakers have to be all the way up...maybe you could boost the volume on the videos during the encoding process?
Since this interview, I've gotten a new camera and this sound issue will not happen again (at least not this bad).
Again, Dr. Lehman saved this for us. (We almost didn't release it and were going to start over, but this is a great discussion and we didn't want to lose it)
C
It's a great video!
Good to know that you realized the issued but that it won't be a common issue with future C9 videos!
Thanks again for another awesome going deep video.
Great video. Thanks.
I'm in the minimalist camp. Don't replace my legs!
Yes. I edited it out because we discussed stuff that is not ready for public consumption at this point in time. Nothing Earth shattering, mind you, but we had to cut it just the same.
C
That got me to thinking....you know what would be cool. On the day that Vista launches Channel9 should launch a series called, "Secret Stuff" where all of the videos of Vista stuff that couldn't be shown on C9 during the development cycle(or that had to be edited out). By that time(the Day Vista launches) most everything will be public and it would be just be a cool "publicity" stunt to drive traffic to the site.
I don't know....the idea just seems really cool....because we'll be able to see everything that you guys were dying to show us but couldn't for various reasons. Just a thought.
It's unfortunate that sometimes we have to cut out stuff from our content (we really dislike editing not just because all of us are as lazy as Scoble(his words, not mine! He's not lazy...)
I like the idea of after ship "bloopers", if you will. Good thinking, Zeo!
C
http://channel9.msdn.com/ShowPost.aspx?PostID=148176
If so, I would really like an explanation also.
Scoble or Charles, is there anyway you can forward the above mentioned discussion thread to one of these guys for a response? I know I am not the only one with the issue.
Thanks and keep up the great work, all of you guys.
I hope this happens much more frequently in the future.
Unfortunately these drivers where just bare bones gamepad drivers with no way to set controller deadzone (making it useless in certain racing games), custom button mappings or rumble but at least it worked.
I love the idea of having a device not find a driver generating an error report so that hardware manufacturers can find out what kind of problems users are having and help them find drivers online more easily.
I HATE the junk (shovelware) certain companies trick users into installing when all they need is a simple driver. It's even more despicable than file type hijacking in my opinion.
No, we haven't found a solution for this. Raymond sums up some of the problems well in his blog. While there are better ways that Windows can address this stuff, we only have so much time to get Vista solid enough for people to stake their livelihoods on it.
Some of the features we're adding to Vista PnP will make this less of a problem.
For example, you'll never get prompted for source media during a reinstall or rollback any more, because we squirrel away all the required driver files in the Driver Store before we do an installation. This means that while your mouse may still reinstall when you switch USB ports, Vista will have all the files it needs, guaranteed.
The performance of the reinstall will also be faster due to the Driver Store anti-tampering features. Because we "trust" the drivers in the store to be unmodified, we don't have to re-verify file signatures when we install. Instead, we do the signing checks up-front when the drivers are imported into the store to make sure they haven't been corrupted or (eek) tampered. We were surprised by how much time the crypto calls were taking. Something like 70% of our install time if I recall correctly.
To the thread about external USB drives not working, I've seen some similar problems when USB-powered drives couldn't get enough juice to function properly. There isn't much Windows can do if the drive stops working. From Windows' perspective, the drive was there one minute, gone the next. Whether it was due to lack of power or a wormhole opening up next to the PC is totally impossible for Windows to determine. The suggested solution of changing permissions on the enum keys in the registry and deleting them is creepy. However, we have also seen a few badly behaved installers (I believe there was a Korean light-pen or something like that) that actually modify PnP's permissions on these critical keys and break device installs. In those cases, we'll follow up with the vendors but we can't seal off these risks without breaking a lot of stuff. Back in the sunnier more optimistic days of early Longhorn planning we fantasized about doing stuff like this, but reality set in and time, unfortunately, continued to pass.
That's all for now, kids. Hope that made sense.
-Euge
I laugh because when I plugged in the XBOX360 controller for the first time, I wasn't sure what had happened. I went to the setupapi.log to confirm that we actually found something on Windows Update. I was happy to see someone finally using this feature. For Vista we've made the experience even better for WU, and there are folks evangelizing the message to partners. And I'm pretty sure this internet thing is here to stay.
Yes, the shovelware problem is frustrating. Luckily for us, there is a way out. If I don't like the stuff that ships with a device, then I simply return the device. Call me an optimistic capitalist...
Here's hoping for a cleaner ecosystem with Vista. Less crapware. More "it just works." Shiny glass for everyone.
-Euge
Might I suggest that you speak with the folks who made the device? If nothing's wrong with your PC, then this is probably happening for a lot of other owners as well. They may have an answer.
-Euge
Hi,
When I watched your show, you did mention about the "Heart Monitor". I knew that there is a device from Microlife called Blood Pressure Monitor. It can link with the PC by USB connection. How can I use the Microsoft Visual Studio 2005 to control it, please.
Thanks,
/CharlieChau.
-Euge
thank you very much, that answeres my question! the driver store seems a good idea finally for managing all those drivers. good job guys!!!
This is one of the best videos ive watched on channel 9 and ive watched a few
Keep up the excellent work.
1) Make generic driver that can talk to any USB printer that supports P1 spec. Call it "Windows Ready To Print" logo.
2) Any device that supports P1, also supports P1+ which is a driver that is installed *on the device. The driver can be downloaded from the device using the P1 driver. The P1+ driver will contain the URL for the Model (not the home page) with updated drivers or app software. P1 and P1+ are drivers *only* and run in user mode only and must be certified if they want the Ready-To-Print logo. I'd pay extra if they did not install all that crud in the tray or my desktop!!
3) People could also install the CD or from exe or inf as today if needed.
--
William
Are you considering any way that manufacturers can add custom functionality without having apps that run all the time? Something like an applet that hosts all the custom interfaces so you can configure non-standard features, without having to have all these processes running and no easy way to remove them.
Also, it would be nice to have an easy way to list all the installed drivers and uninstall old drivers or move between different installed versions in a standard way, and move everything away from custom install wizards.
Anyway, good job
One of the stipulations of submitting a driver for WHQL could be that the manufacturer signs a contract asserting that they are making a good-faith effort to fairly test their driver. If there are serious customer reports of malfunction (it would only matter for high-volume devices), Microsoft could reserve the right to sue the manufacturers if they passed the tests only due to cheating.
-NKS
CYA:)
Great video!
I was wondering out of curiosity if there will be an easy way to add and remove drivers from the driver store to make, for example, a custom installation CD with all the drivers already installed or to manage the existing store.
Yes there will be easy ways to manage drivers in the Driver Store. We'll have a command-line utility that allows administrators to add, enumerate and delete drivers from the Driver Store. We've also plumbed the existing SetupCopyOemInf and SetupUninstallOemInf APIs to add and delete drivers from the Driver Store, respectively. And we're adding a new API to enumerate the drivers in the store. You'll reference drivers in the store via the INFs that we publish to %windir%\inf. That way we're safe to move the Driver Store location or even modify the storage format in future revisions.
-Euge
We actually already support ways that manufacturers can add custom pages to device property dialogs (many display vendors do this with the display cpl); many choose to do something else. It all comes down to what device manufacturers believe the user experience should be like. The Windows ecosystem is wide and varied, so you're getting a lot of choices. And with choice, comes good and bad options.
As I mentioned to freney, we will offer ways that users can enumerate the drivers they have in the Driver Store. We didn't have time to implement a GUI interface to this (that would have been great), but we will be able to satisfy the needs of the IT crowd with command-line and API interfaces.
From Device Manager (yeah, I know, blech) you can roll back to a previously installed driver from any device. And the Update Driver Software Wizard will let you manually select from a list of compatible drivers. I hope that most people won't have to do this, since our inbox support is improved over XP and we're pushing hard to get partners to support their newer devices seamlessly via Windows Update.
-Euge
Did this change in Vista? Or I still need another computer to download the driver?
Hi Karnokd
I have a small tip for you that may work. If I was about to reinstall Windows XP or Vista from scratch, before I did, while I was still online, I would go to the Web site of the manufacturer of my built-in Broadcom Gigabit network hardware, and download the drivers to my hard drive. Then, from there, I would copy the driver files to either a USB Flash memory key or just burn them onto a recordable CD or DVD. This is exactly what I have done, prior to reinstalling Windows Vista Home Premium. The network drivers for my Dell XPS 720 home tower PC (and a whole load of other drivers besides) have been copied onto a DVD+RW. This means I have all drivers to hand!
In your case, you are setting up the network hardware from a brand new PC (after you have installed Windows.) I take it the machine has Windows XP Home or Pro on it at the moment? You could be in a Catch-22 situation here! However, Vista may have the drivers for your network hardware already inside the operating system (I know Vista has a lot more built-in drivers than XP had.) Failing that, then the only way would be to use a second PC that is already online to the Web to download the drivers that way. Then put them on a USB Flash memory key or DVD+RW (if you have the correct DVD drive on the other PC) and then try to install them on the laptop.
If you could tell me the exact make and model of your network hardware (you should find this information in your laptop PC manual somewhere), I could try to find it on the Web for you, if you like.
Sorry I could not be of any more help, but I am very new to Vista and have never even installed it before, so I don't know what to expect when I do come to reinstall it!
Please let me know if you found this advice helpful!
Alastair C Parker.
ES bello
Remove this comment
Remove this thread
close