There is possible to safety kill a process by word?

[Citrusl]

Every one knows that when you work on Windows and you make a persistent process with C++ it will hurt your machine if you kill him on task manager. Creating temp trash and maybe it corrupts the memory or the disk in long term (tested and approved by me.)

Ok... a persistant process is part of the game, but i must close it in safe mode.
I could wait for a pressed key but that is not an option.
I would like to use a secret word, so here is is my question.

There is posible to read from the keyborad a fast concatenation or a complete message like "secretwordwichstopprocess"

I think, validate char by char could be a little unperforming.

I Usually use GetAsyncState but somebody told me something about PreTranslateMessage could be better.

... is this posible?

[Arjay]

Please explain:

>> Every one knows that when you work on Windows and you make a persistent process with C++ it will hurt your machine if you kill him on task manager.

What is a 'persistent process?' How will killing a process 'hurt your machine?'

[2kaud]

Re processes. There are basically/simply 2 types:

1) User process. These are either started automatically when a user logs on directly by the user
2) System service. These are started automatically by the OS when the system is started. Their state can be stopped/started etc.

For each of these types, they can be either user-produced from available source code (which can be amended and compiled) or part of the OS or part of an installed 'application'.

What type of 'process' are we talking about here?

[Arjay]

2kaud, Windows has only one type of process regardless of whether it's invoked by a user, user code, or the service control manager. Windows services expose additional functionality that the SCM hooks into but when they are started they are created and run like any other process.

[2kaud]

2kaud, Windows has only one type of process regardless of whether it's invoked by a user, user code, or the service control manager. Windows services expose additional functionality that the SCM hooks into but when they are started they are created and run like any other process.

Yes - perhaps I was being too simplistic in my post #3 in the context of the question asked.