Jump to content
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble

MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically. 


  • Content count

  • Donations

  • Joined

  • Last visited

Community Reputation

7 Neutral

About Flame.

Profile Information

  • OS
    none specified
  • Country
  1. Yep, it's totally fine. Could even be the best option, UNLESS you want to make that profile the default system browser. In which case you have to: either 1) patch the main binary, or 2) redirect profile folders relative to binary. I am currently in process of migrating to the second option, since Roytam chose not to mess with the first. (like Feodor did, apparentlly) I can not write step-by-step tutorial on that yet, sorry, but feel free to google for topics and pages with info about "tmemutil.dll" and using it in mozilla browsers' builds. I have tested it with Palemoon, NewMoon and Basilisk, in addition to vanilla Firefox 52 ESR, and all went as expected. One difference to other portable options is the default location of profile folders, which is configurable. The other, probably less comfortable difference is that every update must be made manually, including not only rewriting of files, but also editing of one particular configuration file.
  2. Why is it "not clean"? I was using the same approach until recently with no problems. The only important thing to remember — to wipe bin folder completely between major updates to make sure there are no deprecated dlls and such. And since there is no autoupdate in NewMoon (yet?) you will be forced to use the same method in any portable configuration.
  3. Sounds like a major PITA. If possible, try to grab that text by using, for example, NirSoft's SysExporter — https://www.nirsoft.net/utils/sysexp.html or similar software, there are TONS of them.
  4. Hi, yep, that's a problem with portable mozillas. Please take a look at this question http://www.msfn.org/board/topic/177125-my-build-of-new-moon-temp-name-aka-pale-moon-for-xp/?do=findComment&comment=1146299 and author's response to it http://www.msfn.org/board/topic/177125-my-build-of-new-moon-temp-name-aka-pale-moon-for-xp/?do=findComment&comment=1146328 Looks like he was not overly happy with this task and, frankly, I don't blame him. So, other workarounds/options could be: 1) Start browser in portable mode beforehand, and then every time you try opening a link with same default browser you will get a new tab in that browser, unless it is started with "-no-remote" option. 2) Use that "proggie" of yours to configure the default browser to be started always with appropriate "-profile" option, or you may need to fiddle with the registry manually to do that.
  5. Yep, could be useful for some people. Why SSE is it required at all? I don't get it. O_o This should be platform-independent and Qt ARM builds are not considered something unique, right? Also, if by any chance you have access to any static analyzer, please consider checking the QtWeb code with it, for crashes and memory leaks are some of the most notable problems of that browser, IMO.
  6. Sorry for being a little off-topic here, but I'd suggest trying QtWeb for your tasks. Once you turn off external plugins (they don't work nowadays properly anyway) and maybe s as well, it becomes the real mean humble texting machine. With only 35-40 Mb on start/one opened page, it should be exactly what you are looking for. Expect crashes and misbehavior on some heavy/fancy sites though, as its engine is moderately old and based on Qt 4 Webkit. Similar, but a bit less "spartan" option: Qupzilla, with its older versions also being based on Qt4, but with a little more web support and memory requirements. Older versions are available in a topic "List of Web Browsers Working with XP".
  7. @roytam1 Could you please share your source code for a portable launcher? Also, seems like last version (2017-11-21) of New Moon doesn't like it for some reason, e.g. bookmark tab disappears after start. But the same version with PortableApps launcher isn't affected.
  8. Why of course there is! https://addons.mozilla.org/ru/firefox/addon/suspend-tab/ Oh, and don't forget about heavy cavalry: https://addons.palemoon.org/addon/bartab-tycho/
  9. https://stackoverflow.com/questions/639540/how-much-memory-can-a-32-bit-process-access-on-a-64-bit-operating-system While you (in theory) can get 4+ GB memory usable by XP, with Palemoon you are out of luck - the only way (sorta) for 32 bit software to use more than 4 GB of memory is to split itself into several processes, like Chrome or Firefox with E10S, but Palemoon is explicitly ONE process only (not counting the flash container). So, get NoScript, uBlock, uMatrix and cut most pages of their excessive fat while you still can.
  10. It is already compiled with 3GB-aware flag (kudos for that), so besides setting it in XP, nothing else could be done realistically, except for switching to 64 bits. Firefox also can use it, btw. Oh, and ofc you can use some RAM-disk that is smart enough to use memory above XP limit, and set browser cache, temp and swap there.
  11. @roytam1 Do you feel confident enough to move portability to the main executable instead of a launcher? Basically, you need to check any of following conditions on start to set profile to current directory: File name of executable ends with "-portable" (or something like this) There is a file "palemoon.ini" (or something like this) in the same directory as executable, with relative profile path. Or just an empty file. Each one has its strong sides in different situations. Now, the main reason for doing this is - while all simple (non-virtualizing) launchers work relatively fine in common case like "start-use-exit", they do not provide any reliable means for keeping the run arguments (keys, switches) between restarts, which can potentially lead to many problems, but the most important one in this context would be the loss of initial profile path, provided by "-profile" argument. Most commonly encountered cases: A simple restart after installing/updating addons or changing important settings. A crash, with potential subsequent (auto)restart by crash dumper. An external call by another program, which can result (or not) in a mess with another running instance. What do you think of this?