Well I have not used Vista yet (<rant>I mean 15GB disk space minimum required? Come on...</rant>), however I have read about the "enhanced security" and so on. If you do not have sufficient account privileges to disable UAC then (from what I have read) you may have to use WMI. Who knows, I have not seen your code, but it may be quicker to do a rewrite using WMI that it would be to try and figure out a way around this new "uber secure" version windows. Have you seen the DBD::WMI module?
I am not fully aware of the user account privileges setup for Vista. Perhaps there is some sort of exclusion (or trusted apps) list that your system administrators could include your application in.
Good luck,
Martin | [reply] |
Microsoft is indeed hitting limits on system requirements ;)
And if you want to use the new Windows skins and still want a lot of speed, 1GB of RAM is best (I found 512MB a bit slow)
I did check out the DBD::WMI module, and it realy is a great module!
Thumbs up for Corion.
I guess I do have to switch over to WMI.
I was also looking at the privilige list. And if I'm correct on the Vista architecture, it may be possible to run devcon if it's included into the group policy. (I didn't check that out so far).
Thus remaining an issue on the devcon tool itself, it is an unsigned software. Which means, if I'm not mistaken, that when UAC is enabled, it will always query the user for interaction :(
That means that I do have to switch over to another application (like WMI).
Update:
My code itself is very straight forward, and it just calls devcon and captures its output. Afterwards I parse this string.
With WMI, I use the Win32_PnPsingendDriver methode.
The challange I had here was gathering all components belonging to a single device, but I figured that one out.
| [reply] |
The process that triggers UAC is the one running devcon, not the one calling devcon. You launch devcon multiple times, creating multiple processes. Each one of those triggers UAC no more than once.
| [reply]
[d/l]
[select] |