Secondary instances (as opposed to secondary launches) create the folder AppnamePortable\Data\Temp. Is that right?
Also, if launched from another portable app (ie: portable file manager), the app's plugins folder is in the file manager's temp folder:
[PortableApps.comLauncher] Status=running PluginsDir=C:\DOCUME~1\xxx\LOCALS~1\Temp\Explorer++PortableTemp\nshFD.tmp
So if the file manager is closed first, it can't delete its own temp folder.
Tested with:
FoxitReaderPortable (secondary launch goes to first instance).
SMPlayerPortable (secondary launch opens second instance).
Explorer++Portable (the portable file manager).
Can you rebuild the launchers with PAL 2.2?
Previously known as kAlug.
Same in 2.2 except that now *all* secondary launches (regardless of whether they create a new instance) create AppnamePortable\Data\Temp.
I believe this behavior has been somehow triggered by this change.
By the way, do you want to be the Official PortableApps.com Launcher's Tester?
EDIT: We can't change the location of
$PLUGINSDIR
. Maybe if we make the launcher fix$TEMP
and then relaunch itself.Previously known as kAlug.
I suppose I didn't notice that change at the time or didn't think much about it. It was reading it from the file on purpose; $WaitForProgram is intentionally set to false for secondary launches (see Segments\InstanceManagement.nsh, line 33). This is a regression; we need to analyse it more fully to make the correct fix.
I am a Christian and a developer and moderator here.
“A soft answer turns away wrath, but a harsh word stirs up anger.” – Proverbs 15:1
And the parent changeset is
Made WaitForProgram=false be ignored when Live mode is enabled
.Also, here is the IRC log of July 23.
We need to understand a) what's going on and b) why was the change made at first place.
/* @prapper: Can you test it on PAL 2.1 (no 2.1.1)? */
Previously known as kAlug.