Initial implementation of Utility Manager (Accessibility)

[GeoB99]

Purpose

This is the implementation of Utility Manager. For people that don't remember what it is, it's a program to manage accessibility tools which it can be found on Windows XP and Server 2003. The basic functionality is already implemented therefore more has to come.

Presentation

URL Video: https://www.youtube.com/watch?v=6UCuiSpNAVg

JIRA

JIRA Issue: https://jira.reactos.org/browse/CORE-15974

[HBelusca]

[00:07:42] c:\reactos-cov\base\applications\utilman\process.c(77): error C4311: 'type cast': pointer truncation from 'HINSTANCE' to 'INT'

[GeoB99]

As per the documentation:

If the function succeeds, it returns a value greater than 32. If the function fails, it returns an error value that indicates the cause of the failure. The return value is cast as an HINSTANCE for backward compatibility with 16-bit Windows applications. It is not a true HINSTANCE, however. It can be cast only to an int and compared to either 32 or the following error codes below.

Either I am doing it wrong or it's the documentation that says it wrongly. If it's the latter is there an alternative way to catch the code value returned by ShellExecuteW()?

[amber8706]

Perhaps, it is necessary to take information from the registry?: "hklm\software\microsoft\windows nt\currentversion\accessibility"

[GeoB99]

hard coded? Windows retrieve this values from registry: "hklm\software\microsoft\windows nt\currentversion\accessibility"

As said, this is an initial implementation of Utility Manager. Implementation of registry configuration handler will come later (see NOTES on commit files) as it'll take quite a couple of time to figure out the correct implementation.

Thank you for pointing out the registry key though. This will help me know where are the values which Utility Manager manages stored.

[learn-more]

Is there a reason for not always using ShellExecuteW?

[HBelusca]

To be picky:
The OSK can be used also before logging in (in winlogon's secure desktop) and in other situations for example in Windows / NT installations where the shell (and thus, shell32) has not been installed yet.

[learn-more]

Something to refactor on the next PR for this tool:
You can largely combine IsProcessRunning and CloseProcess, by creating one helper function that simply finds the process ID of the process you are interested, and returns that (or 0 if it's not found).
Then both functions do not need to walk the process list exactly the same way.