Strictly Scott is correct, but unfortunately the ".NET" name is overloaded. ".NET 3.0" does not include any updates to the Common Language Runtime (the core execution engine), the Base Class Library, Windows Forms, ADO.NET or ASP.NET, which remain unchanged from their .NET 2.0 versions. The only parts that are new are Windows Presentation Foundation (WPF), Windows Communication Foundation (WCF), InfoCard and Windows Workflow Foundation (abbreviated WF). .NET Framework 3.5 will also be 'pure extensions' to .NET 2.0 but will require .NET Framework 2.0 SP1 to be installed, which will ship at the same time. I'm not completely sure how this will work out, whether System.dll will be replaced or not. So the answer is, if you're targetting Windows Forms or ASP.NET, you need .NET Framework 2.0, but if you're using WPF, WCF, InfoCard or Workflow, you need 3.0 as well. DoEvents: Generating unexpected recursion since 1991

Well, since any message can be reduced to binary data - and IS behind the scenes anyway, you can send any kind of message you want.  The processing of said messages is up to you.    Peace! -=- James Please rate this message - let me know if I helped or not! * * * If you think it costs a lot to do it right, just wait until you find out how much it costs to do it wrong! Avoid driving a vehicle taller than you and remember that Professional Driver on Closed Course does not mean your Dumb Ass on a Public Road! See DeleteFXPFiles

Have you Googled for such, or checked MSDN? "A good athlete is the result of a good and worthy opponent." - David Crow "To have a respect for ourselves guides our morals; to have deference for others governs our manners." - Laurence Sterne

Is Windows Forms really the right forum for this question? the last thing I want to see is some pasty-faced geek with skin so pale that it's almost translucent trying to bump parts with a partner - John Simmons / outlaw programmer Deja View - the feeling that you've seen this post before.

http://windowsvistablog.com/blogs/windowsvista/archive/2006/12/08/windows-vista-power-management.aspx[^] Vasudevan Deepak Kumar Personal Homepage Tech Gossips

abhiramsss wrote: Can you pls help in Using Power management to Monitor UPS Read the power management [^]section in MSDN. This section lists all the power management functions, messages, along with overview. Nibu thomas A Developer Programming tips[^]  My site[^]

For security reasons, you can't. It's impossible to launch a process remotely as interactive unless the target machine is Windows 2000 SP2 or LOWER. It cannot be done on Windows 2000 SP3 and above, including XP and 2003, and expressly documented as such here[^]. Dave Kreskowiak Microsoft MVP - Visual Basic

The best solution is the following DWORD Currtime; DWORD SecondTime; DWord Diff; CurrTime=timeGetTime(); // Wait for some time here.. say about 10 seconds... Sleep (10000); SecondTime=timeGetTime(); now, Second Time - Currtime will be equal to 10000. i think its clear enough... :) haribabu (impossible to understand)

abhiramsss wrote: Sendmessage as Wparam parameter to other remote process(iam using sockets for remote connevtion). and at remote Application i will capture this wparam and display the message I suggest don't use SendMessage to send the data between client and server. Go through the following sample you will get the solution how to send the CString to remote process. http://www.codeproject.com/useritems/MFCSockets.asp[^] wrote: Knock out 't' from can't, You can if you think you can :cool:

abhiramsss wrote: and pass this CString to Sendmessage as Wparam parameter to other remote process(iam using sockets for remote connevtion). umm you don't use SendMessage to communicate to another process using a socket. :sigh: led mike

Windows 2000 Server does not support the Win32_PingStatus WMI class. http://www.microsoft.com/technet/prodtechnol/exchange/Analyzer/91aac86e-60e8-4b90-9453-1c209cf75fd5.mspx?mfr=true[^] led mike