Kotesh.N wrote: Is there an specific structure you can see it as memeory location! "Opinions are neither right nor wrong. I cannot change your opinion. I can, however, change what influences your opinion." - David Crow cheers, Alok Gupta Global Interface Table: An Easy Way to Marshal an Interface Pointer[new] VC Forum Q&A :- I/ IV Support CRY- Child Relief and You

Kotesh.N wrote: Why __cdecl Calling convention set to be Default. what do you want to know abt it "Opinions are neither right nor wrong. I cannot change your opinion. I can, however, change what influences your opinion." - David Crow cheers, Alok Gupta VC Forum Q&A :- I/ IV Support CRY- Child Relief and you

A point for you from the direction Mike just pointed you, So if you are using a function which is called twenty times, the cleanup code will be placed only once in the function called, if __stdcall is used. But if __cdecl is used, it will be twenty times in the code, i.e., everywhere in main after function is called, and if we have say fifty functions in a file each of which is called twenty times, then the size of the EXE in CDecl will be large. But then what is the advantage of __cdecl... that's something that only C has and not even C++. Dario: How is "directory" in French? (I mean a file system directory). John Simmons: "zee file holdaire thingie"

A service is *most of the time* a console application. But not mandatory. This does not mean necessary that the service displays an user interface, but if the project was compiled with /subsystem:console or /subsystem:windows. Other than this, a service application is registered in system as such, accepts certain control codes, and is managed by SCM (Service Control Manager). One can write a service that can interact with the desktop and even display an user interface (although not recommended, sure), not only because a service *must* be a console application, but because this kind of application is intended to be not interactive, system managed, and perform a continuous "service" - hence the name - without user interface. However, a service can create hidden windows for special purpose messages, or use functions that require a message loop. Even COM uses special purpose windows from what I know, so indirectly creating, say, CoCreateInstance, in a service does not makes a service "window free". A console application is what its name says, just an application compiled for and executed in a console window. Nothing more. Nuclear launch detected

Kotesh.N wrote: Hai, I have a doubt regarding Windows Services whether In which level windows services are running ( Low , Kernel, Application ) Regards, application level.. but is running under System Account(Most Powerful account)!.. "Opinions are neither right nor wrong. I cannot change your opinion. I can, however, change what influences your opinion." - David Crow cheers, Alok Gupta VC Forum Q&A :- I/ IV Support CRY- Child Relief and you

What's the difference between stopping and terminating a service? To stop a service use ControlService() with a SERVICE_CONTROL_STOP for dwControl. cheers, Neil