reactos/base/services/umpnpmgr/umpnpmgr.rc

#define REACTOS_VERSION_DLL
#define REACTOS_STR_FILE_DESCRIPTION  "User-Mode Plug and Play Manager"
#define REACTOS_STR_INTERNAL_NAME     "Umpnpmgr"
#define REACTOS_STR_ORIGINAL_FILENAME "umpnpmgr.dll"
#include <reactos/version.rc>
[UMPNPMGR] - Turn the user-mode PnP Manager into a dll, as it is in Windows. However, on Windows 2k/XP/2k3, the dll is managed by services.exe (the SC Manager) (and its entry point name hardcoded in it), whereas on Vista/7+ it is managed by svchost.exe . Since we do not support external dll hardcoded services management in services.exe, make it svchost-compatible instead. - In the .spec file, we mention that a few API set is exported (in stdcall), but we use it also for RPC, and therefore one has to fix somewhere the calling conventions. - Add/modify the registry entries accordingly. svn path=/trunk/; revision=64292 2014-09-25 23:44:28 +00:00			`#define REACTOS_VERSION_DLL`
			`#define REACTOS_STR_FILE_DESCRIPTION "User-Mode Plug and Play Manager"`
[SERVICES] * Improve resource files. CORE-7637 svn path=/trunk/; revision=61123 2013-11-28 22:04:59 +00:00			`#define REACTOS_STR_INTERNAL_NAME "Umpnpmgr"`
[UMPNPMGR] - Turn the user-mode PnP Manager into a dll, as it is in Windows. However, on Windows 2k/XP/2k3, the dll is managed by services.exe (the SC Manager) (and its entry point name hardcoded in it), whereas on Vista/7+ it is managed by svchost.exe . Since we do not support external dll hardcoded services management in services.exe, make it svchost-compatible instead. - In the .spec file, we mention that a few API set is exported (in stdcall), but we use it also for RPC, and therefore one has to fix somewhere the calling conventions. - Add/modify the registry entries accordingly. svn path=/trunk/; revision=64292 2014-09-25 23:44:28 +00:00			`#define REACTOS_STR_ORIGINAL_FILENAME "umpnpmgr.dll"`
set most of trunk svn property eol-style:native svn path=/trunk/; revision=24701 2006-11-08 11:47:44 +00:00			`#include <reactos/version.rc>`