I'd like a clarification on the/N switch

[AnrDaemon]

The documentation states that

…
/N If TCC was started as a service, use the /N option to prevent TCC from being closed on a Windows CTRL_LOGOFF_EVENT.

However, description for _SERVICE internal variable states that

_SERVICE returns 1 if TCC was started as a service (TCC /N).

…which apparently implies that "/N" option not only prevents reaction to CTRL_LOGOFF_EVENT, but also enables TCC to report as a system service.

What is true?

 

[rconn]

They're both true.

 

[vefatica]

What does it mean to run TCC as a service?

 

[AnrDaemon]

You can install TCC (batch file) as system service and it would not require wrappers like srvany or what not.

 

[AnrDaemon]

Except it does not.

Error starting the "TCC test service" service on DAEMON2
Service did not report to the request in time.

 

[AnrDaemon]

I suggest to either remove references to the "system service" from documentation, or properly implement reporting. https://www.codeproject.com/Articles/499465/Simple-Windows-Service-in-Cplusplus

 

[vefatica]

You can install TCC (batch file) as system service and it would not require wrappers like srvany or what not.

Where did you find that info? What batch file? _SERVICE was introduced in version 11, the "/D" startup option documented much later (v15?). I have never seen an explanation of what "started as a service" means.

I'm not surprised that it doesn't work. Neither TCC.EXE nor TAKECMD.DLL import the two most basic functions needed by a service, RegisterServiceCtrlHandler(), and SetServiceStatus().

 

[AnrDaemon]

I find that info in the help file. Quite unsurprisingly.

 

[vefatica]

I find that info in the help file. Quite unsurprisingly.

Where in the help?

 

[AnrDaemon]

mk:@MSITStore:C:\Users\anrdaemon\help\tcmd.chm::/_service.htm

 

[rconn]

TCC does not have the built-in support to run as a service. (Any more - it did at one time, but it was causing some compatibility issues.)

The /N option is intended to be used when you're wrapping TCC with a third-party "run as a service" app. It's of extremely limited use, and was originally done for a single corporate customer who had a custom TCC configuration.

 

[AnrDaemon]

What kind of issues, I'm wondering? Since service entry is separate from main one, and you don't have to call it.