Check whether your application is running - Revision history

Anders: /* Using a Win32 Synchronization Object */ Fixed typo

2021-06-03T17:32:16Z

Using a Win32 Synchronization Object: Fixed typo

â† Older revision		Revision as of 17:32, 3 June 2021
Line 56:		Line 56:
	Example:		Example:
	<highlight-nsis>		<highlight-nsis>
	System::Call 'kernel32::OpenFileMapping(i 0x000F001F, o 0, t "MyAppFileMapping")p.R0'		System::Call 'kernel32::OpenFileMapping(i 0x000F001F, i 0, t "MyAppFileMapping")p.R0'
	IntPtrCmp $R0 0 notRunning		IntPtrCmp $R0 0 notRunning
	System::Call 'kernel32::CloseHandle(p $R0)'		System::Call 'kernel32::CloseHandle(p $R0)'

Anders: Use IntPtrCmp

2021-06-03T17:31:35Z

Use IntPtrCmp

â† Older revision		Revision as of 17:31, 3 June 2021
Line 44:		Line 44:
	Example:		Example:
	<highlight-nsis>		<highlight-nsis>
	System::Call 'kernel32::OpenMutex(i 0x100000, b 0, t "MyAppMutex") i .R0'		System::Call 'kernel32::OpenMutex(i 0x100000, i 0, t "MyAppMutex")p.R0'
	~~IntCmp~~ $R0 0 notRunning		IntPtrCmp $R0 0 notRunning
	System::Call 'kernel32::CloseHandle(i $R0)'		System::Call 'kernel32::CloseHandle(p $R0)'
	MessageBox MB_OK\|MB_ICONEXCLAMATION "MyApp is running. Please close it first" /SD IDOK		MessageBox MB_OK\|MB_ICONEXCLAMATION "MyApp is running. Please close it first" /SD IDOK
	Abort		Abort
Line 56:		Line 56:
	Example:		Example:
	<highlight-nsis>		<highlight-nsis>
	System::Call 'kernel32::OpenFileMapping(i 0x000F001F, b 0, t "MyAppFileMapping") i .R0'		System::Call 'kernel32::OpenFileMapping(i 0x000F001F, o 0, t "MyAppFileMapping")p.R0'
	~~IntCmp~~ $R0 0 notRunning		IntPtrCmp $R0 0 notRunning
	System::Call 'kernel32::CloseHandle(i $R0)'		System::Call 'kernel32::CloseHandle(p $R0)'
	MessageBox MB_OK\|MB_ICONEXCLAMATION "MyApp is running. Please close it first" /SD IDOK		MessageBox MB_OK\|MB_ICONEXCLAMATION "MyApp is running. Please close it first" /SD IDOK
	Abort		Abort

Bugmenot: /* Using the name of the process (with Windows' tasklist command) */ typo

2014-09-25T17:15:41Z

Using the name of the process (with Windows' tasklist command): typo

â† Older revision		Revision as of 17:15, 25 September 2014
Line 89:		Line 89:
	''Note: tasklist tool is only present in Windows XP professional or more recent Windows. Ergo, this will not work on Windows XP Home Edition.		''Note: tasklist tool is only present in Windows XP professional or more recent Windows. Ergo, this will not work on Windows XP Home Edition.

	An alternative to the FindProc plugin above is to check the output of Windows'~~s '~~tasklist' command to see if it contains the process name. (FindProc didn't seem to work for the author of this subsection). This ''could'' be done with the ExecWait command, but that would flash a command prompt window. Instead, the [[ExecCmd_plug-in]] can be used to run the command in a hidden window.		An alternative to the FindProc plugin above is to check the output of Windows' <code>tasklist</code> command to see if it contains the process name. (FindProc didn't seem to work for the author of this subsection). This ''could'' be done with the ExecWait command, but that would flash a command prompt window. Instead, the [[ExecCmd_plug-in]] can be used to run the command in a hidden window.

	Again, make sure your application executable has an easily identifiable name, or you risk detecting another unrelated application having the same name as yours.		Again, make sure your application executable has an easily identifiable name, or you risk detecting another unrelated application having the same name as yours.

Bugmenot: /* Using the name of the process (with Windows's tasklist command) */ typo

2014-09-25T17:14:13Z

Using the name of the process (with Windows's tasklist command): typo

â† Older revision		Revision as of 17:14, 25 September 2014
Line 86:		Line 86:
	'' Note: there seems to be an alternative working for NSIS 2.46 at [[NsProcess_plugin]]		'' Note: there seems to be an alternative working for NSIS 2.46 at [[NsProcess_plugin]]

	== Using the name of the process (with Windows's tasklist command) ==		== Using the name of the process (with Windows' tasklist command) ==
	''Note: tasklist tool is only present in Windows XP professional or more recent Windows. Ergo, this will not work on Windows XP Home Edition.		''Note: tasklist tool is only present in Windows XP professional or more recent Windows. Ergo, this will not work on Windows XP Home Edition.

Bugmenot: typo

2014-08-06T20:33:17Z

typo

â† Older revision		Revision as of 20:33, 6 August 2014
Line 66:		Line 66:
	Advanced applications may use other Win32 named synchronization objects like an Event or a Pipe to send a signal or a command to the application.		Advanced applications may use other Win32 named synchronization objects like an Event or a Pipe to send a signal or a command to the application.

	== ~~using~~ the name of the process ==		== Using the name of the process ==
	You can detect if your application is running by using the [[FindProcDLL plug-in]] to check if a process having the name of your application executable is running.		You can detect if your application is running by using the [[FindProcDLL plug-in]] to check if a process having the name of your application executable is running.

Line 86:		Line 86:
	'' Note: there seems to be an alternative working for NSIS 2.46 at [[NsProcess_plugin]]		'' Note: there seems to be an alternative working for NSIS 2.46 at [[NsProcess_plugin]]

	== ~~using~~ the name of the process (with Windows's tasklist command) ==		== Using the name of the process (with Windows's tasklist command) ==
	''Note: tasklist tool is only present in Windows XP professional or more recent Windows. Ergo, this will not work on Windows XP Home Edition.		''Note: tasklist tool is only present in Windows XP professional or more recent Windows. Ergo, this will not work on Windows XP Home Edition.

Line 113:		Line 113:
	''Note: this version might give unexpected results when running the setup from an UNC Path as cmd.exe itself doesn't support it. The result might include a complaining message. To ovverrride this limitation, see this link: http://support.microsoft.com/kb/156276 . DO IT ON YOUR OWN RISK!!!		''Note: this version might give unexpected results when running the setup from an UNC Path as cmd.exe itself doesn't support it. The result might include a complaining message. To ovverrride this limitation, see this link: http://support.microsoft.com/kb/156276 . DO IT ON YOUR OWN RISK!!!

	== ~~using~~ a window class or title ==		== Using a window class or title ==
	If your application creates a (main) window with a specific classname or title, you can use it to detect whether the application is running.		If your application creates a (main) window with a specific classname or title, you can use it to detect whether the application is running.

Line 142:		Line 142:
	and this function to match a partial title http://nsis.sourceforge.net/Enhanced_FindWindow_for_variable_window_title_names		and this function to match a partial title http://nsis.sourceforge.net/Enhanced_FindWindow_for_variable_window_title_names

	== ~~using~~ a registry entry ==		== Using a registry entry ==
	Your application could, for example, write 1 on startup in a registry entry, and write 0 when the application is closed.		Your application could, for example, write 1 on startup in a registry entry, and write 0 when the application is closed.
	You can then test this registry in your (un)installer.		You can then test this registry in your (un)installer.

Bugmenot: /* using a Win32 Synchronization Object */ typo

2014-08-06T20:30:00Z

using a Win32 Synchronization Object: typo

â† Older revision		Revision as of 20:30, 6 August 2014
Line 33:		Line 33:
	</highlight-nsis>		</highlight-nsis>

	== ~~using~~ a Win32 Synchronization Object ==		== Using a Win32 Synchronization Object ==
	Many applications typically create a named mutex to prevent multiple instance of the application.		Many applications typically create a named mutex to prevent multiple instance of the application.
	Your (un)installer could call the Win32 API "OpenMutex" to detect if this named mutex is active.		Your (un)installer could call the Win32 API "OpenMutex" to detect if this named mutex is active.

Bugmenot: /* using a DDE server */ typo

2014-08-06T20:28:58Z

using a DDE server: typo

â† Older revision		Revision as of 20:28, 6 August 2014
Line 9:		Line 9:
	If you want to check at the very start, use the <code>.onInit</code> (installer) or <code>un.onInit</code> (uninstaller) [http://nsis.sourceforge.net/Docs/Chapter4.html#4.7 function]. Or you may want to do it later, in a [http://nsis.sourceforge.net/Docs/Chapter4.html#4.6 section] or a [http://nsis.sourceforge.net/Docs/Chapter4.html#4.5.3 page callback function].		If you want to check at the very start, use the <code>.onInit</code> (installer) or <code>un.onInit</code> (uninstaller) [http://nsis.sourceforge.net/Docs/Chapter4.html#4.7 function]. Or you may want to do it later, in a [http://nsis.sourceforge.net/Docs/Chapter4.html#4.6 section] or a [http://nsis.sourceforge.net/Docs/Chapter4.html#4.5.3 page callback function].

	== ~~using~~ a DDE server ==		== Using a DDE server ==
	If the application implements a DDE server, your (un)installer can use the [[nsisDDE plug-in]] to contact the DDE server to query its state, bring the application to the foreground or ask the application to exit.		If the application implements a DDE server, your (un)installer can use the [[nsisDDE plug-in]] to contact the DDE server to query its state, bring the application to the foreground or ask the application to exit.

	If your application is written in MFC, it is very easy to add a DDE server in it.. (don't forget to use GuidGen tool to generate a unique service identifier specific to your application)		If your application is written in MFC, it is very easy to add a DDE server in it. (don't forget to use GuidGen tool to generate a unique service identifier specific to your application)

	Many applications already implement such a DDE server (typically used by Explorer to open/print documents). You can search for "ddeexec" keys under HKEY_CLASSES_ROOT to find the name of applications' DDE server.		Many applications already implement such a DDE server (typically used by Explorer to open/print documents). You can search for "ddeexec" keys under HKEY_CLASSES_ROOT to find the name of applications' DDE server.

MarkusH: /* using the name of the process */

2013-11-21T09:08:37Z

using the name of the process

â† Older revision		Revision as of 09:08, 21 November 2013
Line 83:		Line 83:

	'' Note: the [[FindProcDLL plug-in\|FindProcDLL documentation]] states that as of NSIS 2.46 this plugin no longer works...		'' Note: the [[FindProcDLL plug-in\|FindProcDLL documentation]] states that as of NSIS 2.46 this plugin no longer works...

			'' Note: there seems to be an alternative working for NSIS 2.46 at [[NsProcess_plugin]]

	== using the name of the process (with Windows's tasklist command) ==		== using the name of the process (with Windows's tasklist command) ==

85.201.184.5: /* using a window class or title */

2013-04-29T22:57:08Z

using a window class or title

â† Older revision		Revision as of 22:57, 29 April 2013
Line 138:		Line 138:

	As FindWindow does not allow wildcards you may try this function to search for partial class name of a window - http://nsis.sourceforge.net/Enhanced_FindWindow_for_variable_window_class_names		As FindWindow does not allow wildcards you may try this function to search for partial class name of a window - http://nsis.sourceforge.net/Enhanced_FindWindow_for_variable_window_class_names
	and this ~~fonction~~ to match a partial title http://nsis.sourceforge.net/Enhanced_FindWindow_for_variable_window_title_names		and this function to match a partial title http://nsis.sourceforge.net/Enhanced_FindWindow_for_variable_window_title_names

	== using a registry entry ==		== using a registry entry ==

85.201.184.5: /* using a window class */

2013-04-29T22:55:44Z

using a window class

â† Older revision		Revision as of 22:55, 29 April 2013
Line 111:		Line 111:
	''Note: this version might give unexpected results when running the setup from an UNC Path as cmd.exe itself doesn't support it. The result might include a complaining message. To ovverrride this limitation, see this link: http://support.microsoft.com/kb/156276 . DO IT ON YOUR OWN RISK!!!		''Note: this version might give unexpected results when running the setup from an UNC Path as cmd.exe itself doesn't support it. The result might include a complaining message. To ovverrride this limitation, see this link: http://support.microsoft.com/kb/156276 . DO IT ON YOUR OWN RISK!!!

	== using a window class ==		== using a window class or title ==
	If your application creates a (main) window with a specific classname or title, you can use it to detect whether the application is running.		If your application creates a (main) window with a specific classname or title, you can use it to detect whether the application is running.

Line 137:		Line 137:
	Once you obtained the window handle with <code>FindWindow</code>, you can also use <code>SendMessage</code> to send [http://support.microsoft.com/kb/178893 WM_CLOSE to close the application]. Note that this may not work gracefully with all applications, for example applications with multiple top-level windows.		Once you obtained the window handle with <code>FindWindow</code>, you can also use <code>SendMessage</code> to send [http://support.microsoft.com/kb/178893 WM_CLOSE to close the application]. Note that this may not work gracefully with all applications, for example applications with multiple top-level windows.

	As FindWindow does not allow wildcards you may try this function to search for partial name of a window - http://nsis.sourceforge.net/Enhanced_FindWindow_for_variable_window_class_names		As FindWindow does not allow wildcards you may try this function to search for partial class name of a window - http://nsis.sourceforge.net/Enhanced_FindWindow_for_variable_window_class_names
			and this fonction to match a partial title http://nsis.sourceforge.net/Enhanced_FindWindow_for_variable_window_title_names

	== using a registry entry ==		== using a registry entry ==