There is no Service Pack 4. If you follow the instructions in the section marked "Resolution" in the link you gave already (http://support.microsoft.com/default.aspx?scid=kb;en-us;814414[^]) then you should resolve your problem. My: Blog | Photos | Next SQL Presentation WDevs.com - Open Source Code Hosting, Blogs, FTP, Mail and More

Hi Chak. > How to detect logoff and lock event from atl COM Service It's easy with logoff - simply call SetConsoleCtrlHandler and catch the CTRL_LOGOFF_EVENT. Lock events are trickier. I guess the easiest way to catch them is via a Winlogon Notification Package[^]. Note: Because the notification Dll gets loaded by Winlogon and because Winlogon is running under the local System account (your COM Service probably isn't?), you can't use the SendMessage API as a means of IPC communication between them. Try memory mapped files or named pipes instead. Also, set the Impersonate[^] reg-value of your notification Dll to 1 or modify the Dacl of your memory mapped file/named pipe appropriately (check this: A NotQuiteNullDacl Class[^]). RK PS: This were just presumptions from the top of my head -> for the exact behavior/terminology and implementation check the MSDN documentation.

Thats a fair point, but in the example you cite I am assuming you are talking about VB6 or earlier. The comparison between VB6 and C++ is pretty one sided. However, I would say that you can do some pretty goo stuff with VB6, but making it easy to expand and maintain is more the responsibility of the developer. The comparison between VB.NET and C#, in my opinion is a closer run thing. For any reasonably experienced programmer, learning the syntax of VB.NET, C# or any other language is probably less than a days work. The challenge is learning what the framework can do and how to do it! Once you've got that mastered you can use whatever language you like, and thats what I think is clever!