Quote:
Originally Posted by BetterRed
Please read what I actually wrote; it's about what is running when the msi installer is started, nothing to do with installing portable itself.
I've attached some screenshots - the executables that the portable launchers start are identical to the installed calibre executables, the difference is that they're loaded from a different location and some variables are set to precondition the execution environment.
I have no idea if that is relevant to your plugin. Knowing you don't use Windows, I wanted to make sure that you were aware that the msi installer will not run to completion if any of the calibre executables are running from a portable install.
Added: Perhaps you're not aware that 'installed calibre' and multiple copies of 'calibre portable' can coexist on the same Windows system.
BR
|
@BetterRed,
Thank you for the detailed explanation and the screenshots! I now see exactly what you mean: since the executables share the same names regardless of their location, the MSI installer will trigger a conflict if any of them are active.
Even though I'm on Linux, the plugin's logic for Windows actually accounts for this. It uses image name filtering (e.g., taskkill /IM calibre-parallel.exe) rather than specific file paths.
This means that even if a user is running a Portable version from a different drive, the plugin will detect those processes by name, attempt to close them, and wait for them to disappear before launching the MSI.
So, thanks to your observation, I can confirm that version 1.2.1 is safer than ever!