OK. It does look like you are right; I skipped a line and the current universal is equivalent to VS5PEw/MSDN Premium. So at the same price that's OK. I'll go back to my Yugo now.:suss: tim Founder, TMurgent Technologies www.tmurgent.com tmangan@tmurgent.com

...one suspects you don't pay for it out of your own pocket then... But seriously, a 2x to 5x increase in price for an annual subscription is a bit much. It is a real kick in the (you know) to the independent developer. I need those premium packages to test against. Maybe Chris M can get us a really sweet deal? You know, something like $3000, but in canadian!;) tim Founder, TMurgent Technologies www.tmurgent.com tmangan@tmurgent.com

Forget the features. DID YOU SEE THE PRICES? http://msdn.microsoft.com/howtobuy/vs2005/compare/[^] Here is a link to the features - although it seems awfully slow: http://msdn.microsoft.com/howtobuy/vs2005/chart/[^] mass confusion to follow... tim Founder, TMurgent Technologies www.tmurgent.com tmangan@tmurgent.com

Looking for anyone with experience developing a decoupled WMI provider - without .net class nor ATL. SDK examples just don't do it, and microsoft forum is no help either. Hint: It would be a GREAT article for codeproject posting! tim

You might use the windows performance monitor api. If you have used the windows performance monitor, you know that you can look at a report of what processes are running. Look at WMI. Alternatively, rather than query for all that info and make a remote decision, why not signal a check on the computer to be shut down? You would write a service that would run on the shutdown-able PCs. There are multiple ways to signal the remote service, however since you probably are interested in signalling all such PCs, a mailslot (using a * for the coputer name) may be the easiest approach. Obviously, I'm not providing details here, but direction for further research on your part. tim tim Founder, TMurgent Technologies www.tmurgent.com tmangan@tmurgent.com

Short answer: The button can't do it for you. You need to retrieve the current value and save it. Then use that value when you re-create it. If you want to have it remember between sessions, you would save that in the regisitry (HKEY_CURRENT_USER PLEASE!). tim Founder, TMurgent Technologies www.tmurgent.com tmangan@tmurgent.com

1. If you have a mapped variable for the dialog item: 1A) If it is a static item created with the visual editor: itemmappedvariable.EnableWindow(BOOL); 1B) If it is a dynamic item created on the fly: itemmappedvariable->EnableWindow(BOOL); where BOOL is TRUE or FALSE. Setting to FALSE makes the item greyed out and not selectable by the user, which is what most people mean by disabled. 2) If you want the dialog item to completely disapear, you use: 2A) itemmappedvariable.ShowWindow(var); 2B) itemmappedvariable->ShowWindow(var); where var=SW_SHOW to make it visible var=SW_HIDE to make it disapear. If you don't know what a mapped variable is, either: 1) Ggo to the item in the dialog editor. Click on the dialog item, Right click, select create variable. Fill in the name, hit OK. This makes all the coding changes so that you can use the A syntax above. If you search your dialog .h and .cpp you can see the simple changes and do others by hand. Pay attention to the lack of trailing semicolons if you do. 2) You can also use GetDlgItem(IDC_WHATEVER)->EnableWindow(BOOL) or GetDlgItem(IDC_whatever)->ShowWindow(var). Less efficient this way if you do it a lot. Good luck! tim Founder, TMurgent Technologies www.tmurgent.com tmangan@tmurgent.com