Pale Moon forum

I run the portable version and I was a bit annoyed by the fact that it always reset the last download folder to the default "internal" folder. I managed to fix it by replacing
with
in the "Palemoon-Portable.ini" file.

You may want to add this to the portable download page among the other "ini-tips".

Thanks, but setting the download dir to a path in the Pale Moon Portable folder on start-up is by design. It is to prevent, when you actually use it on a stick, that a download dir is remembered between sessions that may be on different computers. Getting an invalid path will make Windows automatically select its "default path" which is usually somewhere in the "My Documents" folder on the hard drive of the PC the stick is used in - that is not desired behavior.

If you install it on your hard disk, then it would be better to simply remove the statement by placing a semicolon in front of it: This way it will act like the desktop version and remember the last used one.

Moonchild wrote:If you install it on your hard disk, then it would be better to simply remove the statement by placing a semicolon in front of it:

Code: Select all

    ;(download directory)
    ;browser.download.lastDir=$Download$|\\"

This way it will act like the desktop version and remember the last used one.

Thank you, that is very helpful.

I installed Pale Moon Portable on a hard disk, but it was a portable hard disk. I only use it on one other computer, for the most part, but I use it with the PortableApps platform, so I like Pale Moon Portable to start in \Documents on the drive. I don't mean to tell you how to bundle your software as it's fine how it is, but perhaps copying the Firefox Portable release would be fairly easy. Then maybe you could get listed in their app directory (I'm not entirely sure how that works) and PortableApps users could get updates automatically (the platform searches for updates every time it starts as long as it hasn't done so in the last 24 hours, I believe).

I'm sorry, but the PortableApps way of supplying portable applications is one I decided against because it relies on a third-party framework.
This means that the browser would not be stand-alone and be tied in with "portableapps.com" that I am not affiliated with, and rely on their updates and development of their framework.

Pale Moon Portable should remain completely standalone.

In addition, the current way of working is much easier to maintain, and I don't see a reason to do double work packaging Pale Moon for the "Apps" platform specifically.