Database Search
If you can't find the information using the categories below, post a question over in our WinBatch Tech Support Forum.
TechHome
Run Winbatch as a Service
- A NT Service - More Info
- A NT Service Template Script - For Beginners
- A NT Service Template Script - For Experts
- Anyway to Stop a Stop_Pending Service
- Can You Run a Uncompiled Script as a Service
- Explanation of Problems with NT Services
- Initialize variables for the SvcWaitForCmd
- Internal NT Errorwith WB Services
- Passing Parameters to a WinBatch Service
- Run Winbatch as a Service Sample Code
- Running a Service Script with Both Interact with Desktop and Network Access
- Sample Code to Start and Stop a Service
- SvcWaitForCmd User Commands
- UDF to Run Native Winbatch Service
- WB Service to Interact with Network Share
- XP SP2 Rebooting from Winbatch Service Failing
Can't find the information you are looking for here? Then leave a message over on our WinBatch Tech Support Forum.
Initialize variables for the SvcWaitForCmd
Keywords: Initialize variables for the SvcWaitForCmd
Question:
what do these variables mean:SERVICE_CONTROL_USER128=28 ;User command 128 SERVICE_CONTROL_USER129=129 ;User command 129 SERVICE_CONTROL_USER130=130 ;User command 130 SERVICE_CONTROL_USER131=31 ;User command 131 SERVICE_CONTROL_USER255=255 ;User command 255
Answer:
Services have the capability of accepting up to 128 different application-defined commands.Windows calls these "user" commands in the sense that an user-written servcice is a "user" (and not the person)
Thus you can write a Winbatch service to "listen" to user defined commands.
The wntSvcControl function can send these commands to a service.
Article ID: W15682
File Created: 2003:05:13:11:29:32
Last Updated: 2003:05:13:11:29:32