[Outdated] PortableApps.com Launcher 1.0 Alpha 4

Debug messages are pretty hard to turn off; there's actually a bug that keeps them from ever being turned off.

!macro DebugMsg _MSG
	!ifdef DEBUG_ALL
		!define _DebugMsg_DEBUG
	!else
		!ifdef Segment
			!ifdef DEBUG_SEGMENT_${Segment}
				!define _DebugMsg_DEBUG
			!endif
 		!else
 			!define _DebugMsg_DEBUG
		!endif

should be

!macro DebugMsg _MSG
	!ifdef DEBUG_ALL
		!define _DebugMsg_DEBUG
	!else
		!ifdef Segment
			!ifdef DEBUG_SEGMENT_${Segment}
				!define _DebugMsg_DEBUG
			!endif
;		!else
;			!define _DebugMsg_DEBUG
		!endif

I just commented out two lines so _DebugMsg_DEBUG isn't defined unless one of the "bigger" debug constants is; the extra code is so people can put the fix in the appropriate code section with as little trouble as possible.

Also, what settings can verbose have?

Looks like %PAL:DataDir% is failing on paths with spaces. For the KidSafe launcher, here's my launcher.ini:

[Launch]
ProgramExecutable=KidSafe\KidSafe.exe
DefaultCommandLineArguments=-SETTINGSDIR="%PAL:DataDir%"
AssignContainedTempDirectory=true
WaitForProgram=false

Regardless of whether I quote or unquote %PAL:DataDir%, KidSafe always gets the same result: an unquoted path. When the path contains spaces, KidSafe errors out and creates the data folder in the wrong spot; that's how I learned there was a problem in the first place.

Chris,

It's time to have a play with your new launcher. I have quickly made a simple launcher, and figured out the basics. It worked fine for me.

Now for a slightly higher degree of difficulty. Move an ini file to the c: drive. I cannot get a file copy to work. I am not clear on the syntax requirements under the [FilesMove] section of your help file. If I want to copy the junk.ini file from x:\PortableApps\AppName\junk.ini to c:\Documents and Settings\user\Application Data\AppName\junk.ini, and then back after running the portable app, the commands in the Launcher.ini file would look like.....?

Can you give me the two or three line example please? This will get me moving.

Regards,

Kim

Firstly, the launcher itself seems to require admin rights and if I cancel gives me error 1223. Secondly, after that pop up is closed, another appears stating that it cannot find appinfo.ini or launcher.ini when they are in the correct folder.

1st - I'm Having Trouble With The Registry I Want To Have The HKLM And HKCU Backup. But The Launcher only Backups The HKCU. How Can I Have Both Of Them.

2nd - Some Of My Software Installs dll's in windows and system32 directory and you nethier have both can you add them

I did a feature request for a registry backup function which accepts wildcards in the keys some days ago.

I've now done some code to do something like this with the search function of the registry plugin
Include into your launcher if you want.

Link to the file: http://www.speedyshare.com/files/21132272/BackupRegistrySearch.nsh

; by Benedikt93

!include "Registry.nsh"

Function _BackupRegistrySearch

	Var /Global _HKey
	Var /GLOBAL _RegPath
	Var /GLOBAL _SearchKeys
	Var /GLOBAL _SearchValues
	Var /GLOBAL _SearchStrings
	Var /GLOBAL _SearchFor
	Var /GLOBAL _CaseSens
	Var /GLOBAL _Type
	Var /GLOBAL _SubKeys
	Var /GLOBAL _FileName
	Var /GLOBAL _Handle
	
	Var /GLOBAL _ResultPath
	Var /GLOBAL _ResultValueOrKey
	Var /GLOBAL _ResultString
	Var /GLOBAL _ResultType
	Var /GLOBAL _FoundItemNumber
		StrCpy $_FoundItemNumber 0
	
	Pop $_FileName
	Pop $_SubKeys
	Pop $_Type
	Pop $_CaseSens
	Pop $_SearchFor
	Pop $_SearchStrings
	Pop $_SearchValues
	Pop $_SearchKeys
	Pop $_RegPath
	Pop $_HKey
	
	StrCmp $_CaseSens 0 _NotCaseSensitive _CaseSensitive
	_NotCaseSensitive:
		StrCpy $_SearchFor "/NI=$\"$_SearchFor$\""
	_CaseSensitive:
		StrCpy $_SearchFor "/NS=$\"$_SearchFor$\""
		
	StrCmp $_Type "" _StartSearch 0
		StrCpy $_Type "/T=$_Type"
	
	_StartSearch:
		${registry::Open} "$_HKey\$_RegPath" "/K=$_SearchKeys /V=$_SearchValues /S=$_SearchStrings $_SearchFor $_Type /G=$_SubKeys /B=0" $_Handle
		StrCmp $_Handle 0 _Error 0
		
	_SearchLoop:
	
		${registry::Find} "$_Handle" $_ResultPath $_ResultValueOrKey $_ResultString $_ResultType
		StrCmp $_ResultType "" _End 0
		StrCmp $_ResultType "REG_KEY" _BackupRegKey _BackupRegValue
		
		_BackupRegValue:
			${registry::SaveKey} "$_HKey\$_ResultPath" "$_FileName" "/A=1 /N=$_ResultValueOrKey /G=0" $0
			StrCmp $0 -1 _Error 0
			IntOp $_FoundItemNumber $_FoundItemNumber + 1
			
		_BackupRegKey:
			${registry::SaveKey} "$_HKey\$_ResultPath\$_ResultValueOrKey" "$_FileName" "/A=1" $0
			StrCmp $0 -1 _Error 0
			IntOp $_FoundItemNumber $_FoundItemNumber + 1
	
		Goto _SearchLoop
	
		_Error:
		${registry::Close} "$_Handle"
		Push -1
		Return
	
	_End:
		${registry::Close} "$_Handle"
		Push $_FoundItemNumber
		Return
	
FunctionEnd

!macro BackupRegistrySearch HKey RegPath SearchKeys SearchValues SearchStrings SearchFor CaseSens Type SubKeys FileName

	Push "${HKey}"
	Push "${RegPath}"
	Push "${SearchKeys}"
	Push "${SearchValues}"
	Push "${SearchStrings}"
	Push "${SearchFor}"
	Push "${CaseSens}"
	Push "${Type}"
	Push "${SubKeys}"
	Push "${FileName}"
	
	Call _BackupRegistrySearch
  
!macroend

I think usage is self-explaning, but if not ask

I Think I Will Wait For The Beta Release. The Launcher Is Not Organize Enough And John Hasn't Add Anything yet.

Maybe take a hint from wraithdu's Sandboxie Portable - it's got one launcher, SandboxiePortable.exe, for launching Sandboxie and one other launcher, CrashCleanup.exe, to bring back data, clean up, etc. after a crash. I've been thinking about the stability thing for some time, and this seems to be the best way, IMHO.
Benefits:
* Users can still get their data back
* The host PC can stay clean (and no worries about having the disk/USB stick removed - users would need to run CrashCleanup from the disk/USB stick)

Downsides:
* Users have to run a separate executable to clean up after a crash; that's somewhat inconvenient, but users will probably be willing to do it to get their data back.

Is there a way of creating multiple launchers for multiple executables? I haven't found a way of doing this, since it seems there can only be one launcher.ini file, but I've got a certain "pet project" I'd like to do in a week or so that will require multiple launchers, because it's got multiple executables with different functionality.

Thanks!

In The Data Folder. Can't You Just Make it Like This.
An AppData, LocalAppData, WinDir Folders And Then Users Just Copy The File In There That the portable App Needed so that newbies like me don't get confused in the launcher.ini and this is more easy and practical.

I want to use your launcher as the launcher for Unicode NSIS Portable.
But I ran into a few specific NSIS Portable issues:

1. NSIS Portable is normally set-up to run NSIS.exe. But if I drag'n drop a file onto the portable launcher it will send the parameters to makensisw.exe.
But I do realize it will be work to implement this, probably just to be used by one specific app.

2. NSIS Portable needs 3 default executable's to wait for, before it can clean-up !

[Launch]
ProgramExecutable=NSIS\NSIS.exe
WaitForEXE=makensisw.exe
;=== really I would need some line like the following
WaitForEXE2=zip2exe.exe

But please, do not let me put you of your next release! It can probably wait for next time, and I can pull the fixes of mercurial anyway !

1. What about implementing the NewTextReplace plugin, so we are able to update utf-16 files as well. Anyway this is the plugin which is used in UnicodeNsisPortable(but there it's named TextReplace.dll for compatibility). But it could wait till you're using unicode to compile.

2. What about appending a registry file, at the moment I got to do it this way:

[RegistryKeys]
PDF-XChangeViewerPortable=HKEY_CURRENT_USER\Software\Tracker Software\PDFViewer
PDF-XChangeViewerPortable2=HKEY_LOCAL_MACHINE\SOFTWARE\Tracker Software\PDFViewer

3. Shouldn't [DirectoriesCleanupForce] first backup it self, so keys couldn't accidentally be deleted from the host.

4. About the services, I'm trying mp3gain-win-full-1_2_5.zip, the launcher seems to register the service, but on exit the launcher goes into a heavy loop.
This is what my PAL ini looks like:

[Launch]
ProgramExecutable=MP3Gain\MP3GainGUI.exe

[Activate]
Registry=true

[RegistryKeys]
MP3Gain="HKEY_CURRENT_USER\Software\VB and VBA Program Settings"

[FileWrite1]
Type=Replace
File=%PAL:DataDir%\settings\MP3Gain.reg
Find=%PAL:LastDrive%\
Replace=%PAL:Drive%\

[Service1]
Name=MSCOMCTL.OCX
Path=%PAL:AppDir%\MP3Gain
Type=service
User=none
Display=MP3_Service
IfExists=skip

This is what I implemented in my regular launcher, and didn't give problems.

RegDLL "$EXEDIR\App\${APP}\MSCOMCTL.OCX"
...
ExecWait '"$PROGRAMDIR\$PROGRAMEXE" $R0'
...
UnRegDLL "$EXEDIR\App\${APP}\MSCOMCTL.OCX"

[edit: for your info, the loop is before any registry keys and the service gets cleanup]

Sorry if I shouldn't post in this forum.

But it's the first time I take a look at "what PortableApps.com Launcher may look like" and it looks very powerfull (service managment ?) and understandable (ini based).

Good luck and thank you

Just ported SharpDevelop to Beta 4, and now I'm getting weird drive letter replacement behavior again. For example, in my default settings, I have the project path set to P:\Documents\Projects, with the LastDrive in DefaultData set to P:. However, when I run SD the first time, the path gets changed to this oddity:

P:L:\DocumentsL:\SharpDevelop Projects

My launcher.ini:

[Launch]
ProgramExecutable=SharpDevelop\bin\SharpDevelop.exe

[LiveMode]
CopyApp=false

[DirectoriesMove]
profile=%APPDATA%\ICSharpCode\SharpDevelop3.0

[DirectoriesCleanupIfEmpty]
1=%APPDATA%\ICSharpCode

[FileWrite1]
Type=Replace
File=%PAL:DataDir%\profile\SharpDevelopProperties.xml
Find=%PAL:LastDrive%\
Replace=%PAL:Drive%\

Also, the find/replace scheme seems like it would break if DefaultData contains default settings but no AppPortableSettings.ini--just like my HxD bug from a while back. DriveLetterUpdate was a better scheme, IMO.

Hi Chris,
I've updated the German.nsh with the new strings.
If I'll time for having a look at mercurail I'll update directly (next time).

${LangFileString} LauncherFileNotFound "$AppNamePortable kann nicht gestartet werden. Bitte installieren Sie die Anwendung ggf. neu. (FEHLER: $MissingFileOrPath wurde nicht gefunden.)"
${LangFileString} LauncherAlreadyRunning "Es läuft bereits eine andere Instanz von $AppName. Bitte schließen Sie erst alle anderen Instanzen von $AppName, bevor Sie $AppNamePortable starten."
${LangFileString} LauncherAskCopyLocal "$AppNamePortable scheint an einem Ort ohne Schreib-Zugriff zu laufen. Möchten Sie eine temporäre Kopie auf Ihrer lokalen Festplatte erstellen und das Programm von dort aus starten?$\n$\nHinweis zum Datenschutz: Wenn Sie Ja sagen, werden Ihre persönlichen Daten aus $AppNamePortable temporär auf Ihre lokale Festplatte kopiert. Diese Daten werden zwar wieder gelöscht, sobald Sie $AppNamePortable schliessen, können aber unter Umständen trotzdem von Dritten gelesen werden."
${LangFileString} LauncherNoReadOnly "$AppNamePortable kann nicht direkt von einem Ort ohne Schreib-Zugriff gestartet werden und wird jetzt geschlossen."
${LangFileString} LauncherPathTooLong "Der Pfad zu $AppNamePortable ist zu lang.  Bitte verkürzen Sie den Pfad durch die Auslassen einiger über dieser Anwendung liegenden Verzeichnissse oder durch Kürzen der Verzeichnisnamen."
${LangFileString} LauncherNoUNCSupport "$AppNamePortable kann nicht aus einem UNC-Netzwerkpfad gestartet werden. Bitte ordnen Sie dem Netzlaufwerk einen Laufwerksbuchstaben zu und versuchen Sie es dann erneut."
${LangFileString} LauncherNoSpaces "$AppNamePortable kann nicht aus einem Verzeichnis mit Leerzeichen gestartet werden. Bitte ändern sie den aktuellen Pfad ($EXEDIR) und entfernen Sie alle Leerzeichen. Starten Sie dann die portable Anwendung neu.  Weitere Informationen erhalten Sie in der help.html."
${LangFileString} LauncherRequiresAdmin "$AppNamePortable erfordert zur Ausführung administrative Rechte."
${LangFileString} LauncherNotAdminTryAgain "Bitte 'Wiederholen' klicken, um die Authentifizierung erneut zu versuchen oder 'Abbruch' zum Beenden."
${LangFileString} LauncherNotAdminLimitedFunctionality "Einige Funktionen von $AppNamePortable werden nicht funktionieren, wenn Sie sie nicht als Administrator ausführen."
${LangFileString} LauncherNotAdminLimitedFunctionalityTryAgain "Klicken Sie 'abbruch' zum Beenden, 'Widerholen', um die Authentizierung erneut zu versuchen oder 'Ignorieren', um trotzdem weiter zu machen."
${LangFileString} LauncherAdminError "Ausführung als Administrator nicht möglich, Fehler $0"
${LangFileString} LauncherAdminLogonServiceNotRunning "$AppNamePortable erfordert administrative Rechte, aber der Windows Logon Service läuft nicht. $AppNamePortable kann nicht gestartet werden."