After carefully followin the "guerilla guide" posted by oliver specifically the registry changes section, i created a launcher for orbit downloader.. Now when run the launcher it goes back to the default settings..I created almost 26 keys under [RegistryValue] specifically for HKCU.. The app stores some .xml & .dat files in %APPDATA% folder..
You should really give more information on what you did / what the app did not to when it was supposed to, eg.
- your INI (in .. tags!!)
- your folder structure
- does this happen on each run or only on first?
otherwise it's unlikely that anybody here can help you.
"Der Klügere gibt nach, deshalb regieren Dumme die Welt."
I'll post the regshot html,my launcher next time i use a computer to login.. I'm using a mob to login..
There is no substitute for experience...
There's a file being written AppNamePortableSettings.ini in %PAL:DataDir% .. Is it this ini ur talkin about??
There is no substitute for experience...
He is talking about the launcher configuration - what you wrote.
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
Thanks guys for showing me a way ahead... At last i've made a portable edition of "Orbit Downloader 4.0.0.3".. Will post the portabte app in beta testing whenever i can..
There is no substitute for experience...
I followed everything... When i follow [FilesMove] for one app[Opera],it works.. When i follow that for another app[Orbit] it worked once.. Now it doesnt..
[Comment created by mod Chris; now please provide the launcher.ini code so that we can see what you're doing.]
There is no substitute for experience...
[Put in a <pre> code block; also removed duplicate from slightly less-relevant thread - I'll see it in whichever thread so we'll keep it in this one - mod Chris]
There is no substitute for experience...
Sorry, but what you've got there is largely wrong. First of all, any values which you're having as the default should be omitted.
ProgramExecutable is probably the only value you want; only set WorkingDirectory if it's absolutely necessary, only require running as admin if you absolutely need to, only set SinglePortableAppInstance to true if it won't work properly otherwise, only use LaunchAppAfterSplash for things that change the resolution (as the manual says).
This should be done as a single [DirectoriesMove] line, Orbit=%APPDATA%\Orbit. Don't put in trailing slashes, and avoid using subdirectories.
As noted in the manual,
HKEY_USERS\S-1-5-21-1409082233-1957994488-725345543-1008
is HKEY_CURRENT_USER (HKCU). Get rid of the S-*.If Orbit is using Internet Explorer, forget it completely. You can't just set this stuff and make it portable, as Internet Explorer isn't portable. Also an incidental note - the key won't be being backed up, so that's no good, and if the key doesn't exist it won't be created. When you need things like that you need at least a RegistryKeys directive of some sort to cover the key.
You don't touch these things. They're not relevant.
Some of these values won't be relevant. Also the quotes after the REG_SZ: will be interpreted as literal quotes; you probably don't want them.
Don't fiddle with any of these. It's not safe or proper.
The format is wrong. RegistryCleanupForce is just number=key; no value included, nor string for the value. What's more, mainly for the reasons above, this isn't correct.
FilesMove moves the things back and forth itself; the manual never mentions anything like this and it's not correct (to be precise, it will be ignored as it's a second declaration of the section: only the first will be read).
I'm not clear on whether Orbit is using HKCU or HKLM. You seem to have mixed references to it. I would presume it uses HKCU.
I'm sorry that I need to find so many faults with it; I don't mean to be discouraging. If you try, you'll learn. I suspect Orbit isn't really a very nice one to start with.
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
U've seen my launcher.. I'm a total noob here..
few questions please!!
*should i use the PAL or the .nsi way for creating launchers..
(atleast i know some basics about PAL launchers)
*some very basic examples to start with
There is no substitute for experience...
Hi SantoshV,
If I may offer some advice from a "noob" to a "noob"(note that I'm still experimenting myself) :
1- I believe the purpose behind PAL is to reduce the amount of programming required to create your own launcher - its a universal launcher in-effect. I think its clear, then, which you should use.
2- I've found it invaluable to first think about what purpose a certain part/function of PAL has and second its general role in the PAL system. Do you understand, at least, what a "launcher" is and what is its relationship with the app to be made portable? Judging from your previous posts you have used an automated system to form your .ini files - you won't learn much this way.
3- Its very important to understand the specification :
https://portableapps.com/development/portableapps.com_format
To be able to answer questions from my second suggestion you will need to know what is the purpose and place of each folder, their appropriate naming convention and most importantly the role and place of the .ini files.
4- When I started I knew there would be a need for constant experimentation and changes. The first thing I did is to set up a "development environment": downloaded the specification template, renamed folders and files according to the specification, modified the "appinfo.ini" and added basic program files. I then ran the PAInstaller(in admin mode if vista/7) to check if I had the basics right - since the PALauncher relies on this being so(I used a dummy launcher). I then setup the launcher(which requires the NSIS portable package), put a single entry in "\App\AppInfo\Launcher\appnameportable.info" - "[Launch]ProgramExecutable=appname\appname.exe" - and created a first pass launcher. Experiment with each of the functions of the launcher.ini to understand what they do.
5- Now you have to isolate the program from the system. I recommend you use this order of isolation : 1 - system/program files/dirs (then test) 2 - Data/MRU files/dirs (then test) 3-Registry (then test). You can use whatever software you like, personally however, I don't use "Regshot" since this tends to capture a great deal more changes then are necessary - and is not progressive. Most developers, primarily for the benefit of their own sanity, follow obvious naming conventions and therefore efficient file and registry search tools suffice most of the time. Personally I use "regfromapp"/"Process Monitor"/"OpenFilesView"/"ProcessActivityView" - "Everything"(voidtools) - "Registrar Registry Manager"(not free, unlike others).
Hope this helps. I welcome any corrections/comments/questions.
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