[CSRSRV][CONSRV]
- Fix the second parameter WaitType (aka. NotifyAll) of CsrNotifyWait. Indeed, we used before the constants WaitAll == 0 / WaitAny == 1 (see the WAIT_TYPE enum); however, it appeared that Win2k3's CsrNotifyWait wanted a WaitType parameter == 1 when waiting for all the waits in a given wait-list. Therefore we would have to use WaitAll for waiting for any of the wait blocks, and WaitAny for waiting for all the wait blocks... looks illogical. Therefore I use instead a BOOLEAN variable (that I call NotifyAll) which is TRUE when I want to wait for all the wait blocks, and FALSE otherwise (as done e.g. for the WaitForMultipleObjects API).
- Fix its usage in CONSRV.

Magically fix key presses problems in console, when using Win2k3 csrsrv.dll ...

git-svn-id: svn://svn.reactos.org/reactos/trunk@60551 97493ccd-5924-5043-b1f5-66cb403b36ce
[GDI32_WINETEST]
[USER32_WINETEST]
Use Jira bug ids.


git-svn-id: svn://svn.reactos.org/reactos/trunk@60552 97493ccd-5924-5043-b1f5-66cb403b36ce
[CSRSRV][CONSRV]
CSR_WAIT_FUNCTION functions are callbacks and therefore are __stdcall aka. NTAPI. Fix this.
Now, using either our csrsrv or win2k3' csrsrv works without problems; there is no console key-press problems anymore (aka. stack corruption when calling multiple times CsrNotifyWait, which called those CSR_WAIT_FUNCTION functions).

git-svn-id: svn://svn.reactos.org/reactos/trunk@60553 97493ccd-5924-5043-b1f5-66cb403b36ce
[CSRSRV]: Add the 0x prefix when we display some hex output.

git-svn-id: svn://svn.reactos.org/reactos/trunk@60554 97493ccd-5924-5043-b1f5-66cb403b36ce
[CSRSRV]: Less PPORT_MESSAGE casts.

git-svn-id: svn://svn.reactos.org/reactos/trunk@60555 97493ccd-5924-5043-b1f5-66cb403b36ce
[CSRSRV]: Fix long-time SMSS port name typo (it is SbApiPort).

git-svn-id: svn://svn.reactos.org/reactos/trunk@60556 97493ccd-5924-5043-b1f5-66cb403b36ce
[POWERCFG.CPL]
- Use Yes/No instead of Ok/Cancel for "Are you sure you want to delete the power scheme?" Patch by Lee Schroeder.
- Remove some unnecessary casts
CORE-7503 #resolve

git-svn-id: svn://svn.reactos.org/reactos/trunk@60557 97493ccd-5924-5043-b1f5-66cb403b36ce
[SETUPAPI]
Add _SP_INF_SIGNER_INFO and _SP_ALTPLATFORM_INFO defines.


git-svn-id: svn://svn.reactos.org/reactos/trunk@60558 97493ccd-5924-5043-b1f5-66cb403b36ce
[SETUPAPI]
Add stubs for SetupVerifyInfFile, called by VMWare tools installer.


git-svn-id: svn://svn.reactos.org/reactos/trunk@60559 97493ccd-5924-5043-b1f5-66cb403b36ce
[CSR]
During my investigations for making working Win2k3 csrsrv.dll (or other CSR servers) into ROS (to compare our behaviour with our own csrsrv.dll and Win2k3 one), I hit a problem: if I test a checked-build version of csrsrv (or other CSR servers), everything was fine when they were loaded, but if I use a release-build version (i.e. without any debug information), I systematically hit a memory access violation which was traced back to the moment when a CSR server's CsrInitialization entry point was called.
So I did the experiment, where I used our (debug-build) csrsrv with a free-build win2k3 CSR server dll (it was winsrv.dll, and I retested with basesrv.dll after). I hit the access violation. But if I took a debug-build version of winsrv.dll, everything was OK.
I then added in our csrsrv' server.c file the following line (around line 212 of the current file version):
DPRINT1("%s ; ServerDll->ValidTable = 0x%p ; ServerDll->NameTable = 0x%p ; ServerDll->SizeOfProcessData = %d ; ServerDll->ConnectCallback = 0x%p\n", DllString, ServerDll->ValidTable, ServerDll->NameTable, ServerDll->SizeOfProcessData, ServerDll->ConnectCallback);
and I saw that, when using a debug-build win2k3 CSR server, everything was fine (in particular the ServerDll->SizeOfProcessData member contained a reasonable value, e.g. a size of 88 bytes), whereas if I used a free-build version, I got an off-by-one problem, with the ServerDll->ValidTable pointer valid but the ServerDll->NameTable member being equal to 88 (i.e. invalid pointer) and the ServerDll->SizeOfProcessData member being equal to a very large value, which looked like a pointer value.
After more investigations, I saw that in debug-build CSR servers the list of API names were stored, whereas it was not the case in free-build versions. Therefore I concluded that the API names table was included *ONLY* in debug builds and not in release builds.

Hence, to be able to test in ROS either debug-builds or release-builds versions of Windows CSR servers in ROS (and vice-versa), I introduced a #define called CSR_DBG, which is defined only if the DBG macro is != 0, and which is not defined otherwise. When the CSR_DBG flag is defined, API names tables are added in CSR servers and otherwise, they are not.

Therefore, we are now able to test debug-build Windows CSR servers in ROS (the default possibility) or free-build versions of these CSR servers (but first, we have to build the other ones without the CSR_DBG flag, to avoid the off-by-one problem described above).

git-svn-id: svn://svn.reactos.org/reactos/trunk@60560 97493ccd-5924-5043-b1f5-66cb403b36ce
[CSRSRV]: In CsrCaptureArguments, be sure that the number of captured pointers is at most equal to MAXUSHORT (and not the total length of the captured buffer).

git-svn-id: svn://svn.reactos.org/reactos/trunk@60561 97493ccd-5924-5043-b1f5-66cb403b36ce
[BOOTDATA]
- Add some descriptions.
- Add HKLM\Software\Microsoft\Windows NT\CurrentVersion\IniFileMapping needed for win2k3 basesrv (otherwise it fails to initialize) (and ours when the INI File Mappings functionality will be fully implemented). INI File Mappings allows redirections from e.g. system.ini --> Adequate Registry Key, when you use APIs such that WritePrivateProfileString to write settings in those INI files (for 16-bit compat).

git-svn-id: svn://svn.reactos.org/reactos/trunk@60563 97493ccd-5924-5043-b1f5-66cb403b36ce
[DINPUT8]
* Speedup build.

git-svn-id: svn://svn.reactos.org/reactos/trunk@60564 97493ccd-5924-5043-b1f5-66cb403b36ce
[MSHTML/GECKO]
* Move the gecko prompt from the mshtml registration to the second stage installer itself. This allows mshtml to register properly regardless of the availability of the gecko package.

git-svn-id: svn://svn.reactos.org/reactos/trunk@60565 97493ccd-5924-5043-b1f5-66cb403b36ce