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. 


roytam1

My build of New Moon (temp. name) a.k.a. Pale Moon for XP

Recommended Posts

JFYI:

Why You Shouldn’t Use Firefox Forks Like Waterfox, Pale Moon, or Basilisk

https://www.howtogeek.com/335712/update-why-you-shouldnt-use-waterfox-pale-moon-or-basilisk/

Brought to you by this guy:

https://www.howtogeek.com/author/chrishoffman/

Quote

Chris is Editor in Chief of How-To Geek. He's always tracking the latest Windows 10 news, tapping at his iPhone, and playing with all kinds of technology.

jaclaz

Share this post


Link to post
Share on other sites

curiosil said:


Thanks for your replies, but the solutions given could still be viable knowing that, as I said, this problem doesn´t occur with Chrome?
If the problem were hardware acceleration or the graphics card drivers, it should happen also with Chrome, right?
But, if this WebGL is broken, where is it broken? If clean installations of new browsers have the same problem, the problem doesn´t seem to be within the 'about:config' configuration of the browser, does it?


No it often means nothing if something works in one browser and in another not, as so many people seem to assume. Sometimes yes, but very often not. Not everything depends from the system only, browsers can also bring some own capabilities too.
Especially that encryption/SSL/TLS stuff is contained completely independent inside all Firefoxes and the forks, as I've been told here. Unlike other browsers which fully depend on system capabilities. That's the reason why Firefox forks can still be updated to use TLS1.2 on systems even older as Win98, and other browsers are stuck with what the old system can do.

Yet lots of things which work fine can still fail if they simply aren't enabled in the settings.
Settings are an incredible jungle in FF/gecko, there are over 3000 prefs, and some most important ones not even showing up in aboutconfig, and many cross-influencing each other.
Clean installations also are no guarantee that everything is fully enabled out-of-box, as so many people assume. For example some of roytam's browsers for very old systems, like FF2, are now equipped with TLS1.2, yet out-of-box still have the ancient default setting of max TLS 1.0. Or stuff like hardware-acceleration, those settings are infamous to be helpful on one system yet disastrous on another, so intentionally not always enabled by default.

At any rate, if the map first shows up fine and then vanishes again, the browser CAN do it, and it really doesn't matter what Chrome or the system can. The solution or the workaround to persuade the server to send the tiles must be somewhere in the settings....

Share this post


Link to post
Share on other sites
3 hours ago, jaclaz said:

JFYI:

Why You Shouldn’t Use Firefox Forks Like Waterfox, Pale Moon, or Basilisk

https://www.howtogeek.com/335712/update-why-you-shouldnt-use-waterfox-pale-moon-or-basilisk/

Brought to you by this guy:

https://www.howtogeek.com/author/chrishoffman/

jaclaz

already discussed: https://forum.palemoon.org/viewtopic.php?f=3&t=19262&p=142312&hilit=howtogeek#p142312

  • Like 1
  • Upvote 2

Share this post


Link to post
Share on other sites

New build of basilisk/UXP for XP!

Test binary:
Win32 https://o.rths.cf/basilisk/basilisk52-g4.1.win32-git-20190202-a31b9e067-xpmod.7z
Win64 https://o.rths.cf/basilisk/basilisk52-g4.1.win64-git-20190202-a31b9e067-xpmod.7z

diff: https://o.rths.cf/basilisk/UXP-xp-gitdiff-20181110.7z

PM28XP build:
Win32 https://o.rths.cf/palemoon/palemoon-28.4.0a1.win32-git-20190202-a31b9e067-xpmod.7z
Win64 https://o.rths.cf/palemoon/palemoon-28.4.0a1.win64-git-20190202-a31b9e067-xpmod.7z

Official repo changes since my last build:
- Only use white audio indicator when using a lightweight theme (46958a2aa)
- Only use white audio indicator when using a lightweight theme [pinned tabs] (b39e0b131)
- Merge pull request #945 from FranklinDM/audioindicator-lwtheme-fix (2d43b6eee)
- Add nullcheck for addons (pre-installed webextensions return null) (d6a2deb0c)
- Remove remote add-on debugging control. (2e581f48e)
- Always treat composition time offsets as signed (bed24fdb7)
- [BASILISK] Align browser glue with TychoAM for enableable add-ons. (2cbbc5de4)
- [PALEMOON] Remove some dead code from browser glue (plugin update service) (e82fdef9c)
- Reduce number of allocations in AutoStopwatch (3476c1d60)
- Revert "Reduce number of allocations in AutoStopwatch" (abcaa560f)
- Reduce number of allocations in AutoStopwatch (b55d41c24)
- Merge pull request #948 from trav90/media-work (7f992d50e)
- [TychoAM] Fix GMP* so that EME works in Basilisk (a606410ba)
- [AM] Remove spurious warning for staged cleanup. (efac6cc1c)
- Remove telemetry leftovers from JS engine. (493c956d8)
- Revert "Fix bookmarks backup logic." (dcc5d6a78)
- Only state the stop notification for JSDownloads in nsWebBrowserPersist::EndDownload (aa28523a5)
- Merge pull request #952 from adeshkp/remove-telemetry-js (fecab2c54)
- Merge pull request #954 from MoonchildProductions/TychoEME-work (6edfc0a20)
- Set incremental GC slice to 20 ms duration (278eda6a0)
- Update HSTS preload list (a31b9e067)

My changes since my last build:
- update nss to git rev 4aea92b574d2d674ee75838d46ea95b113e8fecb with nss339-vc2013.diff applied
- update Twemoji font to v11.3 based build.
- update libaom to rev 0ec86ac7ae1e32a7e70410fa4972a655ec3670a4 (without moz.build and aom_ports/aom_once.h)

  • Like 4

Share this post


Link to post
Share on other sites

New build of BOC/UXP for XP!

Test binary:
MailNews Win32 https://o.rths.cf/boc-uxp/mailnews.win32-20190202-733833f-uxp-a31b9e067-xpmod.7z
Browser-only Suite Win32 (removed due to request)

source patch (excluding UXP): (removed due to request)

Official repo changes since my last build:
- [PLATFORM] Update commit pointer (e5e04a0)
- [NAVIGATOR] Reconfiguration (886d0f7)
- [NAVIGATOR] Take select search plugins and fonts directly from Pale Moon (f4f6373)
- [NAVIGATOR] Remove Weave (03589cc)
- Issue #46 Remove Safe Browsing - Part 2: Navigator (9a18586)
- [NAVIGATOR] Fix Fonts (09aad28)
- [NAVIGATOR] Fix installer makefile (1d3c9f5)
- [MAIL] Fix main moz.build for fonts (b377bb9)
- [NAVIGATOR] Remove Doorhangers (5e10e68)
- [MAIL] Fix accidental convars edit (a05468f)
- [NAVIGATOR] Remove Migration (fab0217)
- [NAVIGATOR] Reorganize the menus (ab39ff4)
- [NAVIGATOR] Fix search service issues (3841ce1)
- [NAVIGATOR] Add Cookie Manager (75f1256)
- [NAVIGATOR] Delicious delicacies (8a50ddf)
- [PLATFORM] Update commit pointer (3447d95)
- [NAVIGATOR] Replace the unused Permissions Manager with a superior one and actually use it (53177cb)
- [NAVIGATOR] Fix subscribing to feeds via live bookmark (7b180bb)
- [NAVIGATOR] Offline Data Permissions Manager should show block not allow (76a7eea)
- [PLATFORM] Update commit pointer (f4d9db9)
- [NAVIGATOR] Make the Add-ons Manager as a Window preserve it's metrics and position (eaf32bb)
- [PLATFORM] Update commit pointer (ffcd4b4)
- [INSPECTOR] Add Navigator Support (733833f)

For UXP changes please see above.

Edited by roytam1

Share this post


Link to post
Share on other sites

New Palemoon 27 Build!
* This build is beyond official 27.9.4 build.

32bit https://o.rths.cf/palemoon/palemoon-27.9.1a1.win32-git-20190202-92d2d7f76-xpmod.7z
32bit SSE https://o.rths.cf/palemoon/palemoon-27.9.1a1.win32-git-20190202-92d2d7f76-xpmod-sse.7z
32bit noSSE https://o.rths.cf/palemoon/palemoon-27.9.1a1.win32-git-20190202-92d2d7f76-xpmod-ia32.7z

64bit https://o.rths.cf/palemoon/palemoon-27.9.1a1.win64-git-20190202-92d2d7f76-xpmod.7z

source repo: https://github.com/roytam1/palemoon27

repo changes since my last build:
- disable nsAutoOwningThread, which cause crash in KM (9e8200e7a)
- snappy: update snappy to r114 from UXP (c2d58c15a)
- update NSS to git rev e76a339d424a5fad9bc42a7e91154a4dd89b83f3 with nss339-vc2013.diff applied (e37e83161)
- import changes from rmottola/Arctic-Fox:
 - change some pointer style, or patches do not apply (0de8fac13)
 - Bug 1137523 - Unprefix most js_* functions. (16507a434) (65938cdd9)
- import changes from rmottola/Arctic-Fox:
 - Bug 1130166 - Use SizePrintfMacros.h when printing line numbers. (9fd08a254)
 - Bug 1133369 - Use consistent allocation kinds for new objects after converting an unboxed group (51e5f25bc)
 - Bug 1129510 - Trace references to JS heap from Profiler buffers. (90dfbed12) (743d64fb7)
- import changes from rmottola/Arctic-Fox:
 - Bug 994016: TI: add removeSet (slightly reworked) (4cccc36c4)
 - Bug 994016: IonMonkey: Add MTypeOf folding to MCompare (9eb64c54a)
 - Bug 994016: IonMonkey: Use high level TI API for improving types at branches (what was left unapplied) (959c796ab)
 - Bug 994016: IonMonkey: Improve types at compares with MTypeOf (c8e580d34)
 - Bug 994016: IonMonkey: More agressively improve types at branches (5d4be5bfd) (129bd4b32)
- import changes from rmottola/Arctic-Fox:
 - Bug 1136925 part 1. Stop passing a parent to JS_CloneObject (02806f3cb)
 - Bug 1136925 part 2. Stop passing a parent to Wrapper::New. (1d51cbd34)
 - Bug 1136925 part 3. Stop passing parents to js::NewProxyObject. (dc13db8da)
 - Bug 1136925 part 4. Stop passing parents to ProxyObject::New. (e2d30e340)
 - Bug 1130679: IonMonkey: Make it possible to guard on type changes/bailouts (ecec18313)
 - Bug 1136980 part 1. Get rid of JS_SetParent uses in DOM/XPConnect. (5cad9c256)
 - Bug 1136980 part 2. Remove JS_SetParent, even though we have a CLOSED TREE (96cf58c85)
 - Bug 1066229 - Part 5: Emitter support for basic ES6 ClassStatements. (e2a3cc979)
 - Bug 1135423 - Use unboxed objects for object literals where possible, clean up object literal creation and property initialization code (1d9e381c2) (0838d9d1a)
- import changes from rmottola/Arctic-Fox:
 - Bug 1137523 part 2 - Unprefix a few js_* functions I forgot in part 1 (e6beaf0d8)
 - Bug 1135816 - Handle unboxed object receivers when compiling getter/setter calls in baseline/Ion (82233087e) (94617d85e)
- update Twemoji font to v11.3 based build. (92d2d7f76)

  • Like 2

Share this post


Link to post
Share on other sites

New build of Firefox 45ESR SSE:

test binary: https://o.rths.cf/gpc/files1.rt/firefox-45.9.13-20190202-f0dd40394-win32-sse.7z

repo: https://github.com/roytam1/mozilla45esr

Changes since my last build:
- update NSS to git rev e76a339d424a5fad9bc42a7e91154a4dd89b83f3 with nss339-vc2013.diff applied (2ebe1a28d)
- update nss to git rev 4aea92b574d2d674ee75838d46ea95b113e8fecb with nss339-vc2013.diff applied (2c1850be4)
- import changes from tenfourfox:
 - #540: M1510114 M1502871 M1494364 M1485864 (2dba79e82) (M1485864 not applied due to patchede source in nss git)
 - #540: update certs, pins, TLDs (715c9087d) (7edbd8bf5)
- hack: treat `const` in `for(const x in y)` as `let`. idea from https://github.com/classilla/tenfourfox/issues/541 (f0dd40394)

Share this post


Link to post
Share on other sites

New regular/weekly KM-Goanna release:
https://o.rths.cf/kmeleon/KM76.1-Goanna-20190202.7z

Changelog:

Out-of-tree changes:
* update Goanna3 to git 21b0da255..92d2d7f76:
- disable nsAutoOwningThread, which cause crash in KM (9e8200e7a)
- snappy: update snappy to r114 from UXP (c2d58c15a)
- update NSS to git rev e76a339d424a5fad9bc42a7e91154a4dd89b83f3 with nss339-vc2013.diff applied (e37e83161)
- import changes from rmottola/Arctic-Fox:
 - change some pointer style, or patches do not apply (0de8fac13)
 - Bug 1137523 - Unprefix most js_* functions. (16507a434) (65938cdd9)
- import changes from rmottola/Arctic-Fox:
 - Bug 1130166 - Use SizePrintfMacros.h when printing line numbers. (9fd08a254)
 - Bug 1133369 - Use consistent allocation kinds for new objects after converting an unboxed group (51e5f25bc)
 - Bug 1129510 - Trace references to JS heap from Profiler buffers. (90dfbed12) (743d64fb7)
- import changes from rmottola/Arctic-Fox:
 - Bug 994016: TI: add removeSet (slightly reworked) (4cccc36c4)
 - Bug 994016: IonMonkey: Add MTypeOf folding to MCompare (9eb64c54a)
 - Bug 994016: IonMonkey: Use high level TI API for improving types at branches (what was left unapplied) (959c796ab)
 - Bug 994016: IonMonkey: Improve types at compares with MTypeOf (c8e580d34)
 - Bug 994016: IonMonkey: More agressively improve types at branches (5d4be5bfd) (129bd4b32)
- import changes from rmottola/Arctic-Fox:
 - Bug 1136925 part 1. Stop passing a parent to JS_CloneObject (02806f3cb)
 - Bug 1136925 part 2. Stop passing a parent to Wrapper::New. (1d51cbd34)
 - Bug 1136925 part 3. Stop passing parents to js::NewProxyObject. (dc13db8da)
 - Bug 1136925 part 4. Stop passing parents to ProxyObject::New. (e2d30e340)
 - Bug 1130679: IonMonkey: Make it possible to guard on type changes/bailouts (ecec18313)
 - Bug 1136980 part 1. Get rid of JS_SetParent uses in DOM/XPConnect. (5cad9c256)
 - Bug 1136980 part 2. Remove JS_SetParent, even though we have a CLOSED TREE (96cf58c85)
 - Bug 1066229 - Part 5: Emitter support for basic ES6 ClassStatements. (e2a3cc979)
 - Bug 1135423 - Use unboxed objects for object literals where possible, clean up object literal creation and property initialization code (1d9e381c2) (0838d9d1a)
- import changes from rmottola/Arctic-Fox:
 - Bug 1137523 part 2 - Unprefix a few js_* functions I forgot in part 1 (e6beaf0d8)
 - Bug 1135816 - Handle unboxed object receivers when compiling getter/setter calls in baseline/Ion (82233087e) (94617d85e)
- update Twemoji font to v11.3 based build. (92d2d7f76)

* Notice: the changelog above may not always applicable to XULRunner code which K-Meleon uses.

  • Like 1

Share this post


Link to post
Share on other sites

And, TBH, I've been reading how-to-geek some time ago regularly, but somewhen they started their review geek sub-section, and I feel they they've turned from help and guide articles into being big advertising tube. Now their articles are more "old is bad, new is good" themed, and argumentation "it's official, so it MUST be working better than replacement".

And as for this particular article, I can agree that PM and Basilisk are slower than quantum-based Firefox, which anyone can test on his own PC, but the author also mentions security risk involved in using PM and Basilisk... and then it would be cool if he mentioned any real vulnerability that is present in Basilisk or PM, and not in the recent Firefox ESR.

And last but not least, many of roytam1's builds suers were with Firefox 52ESR for as long as it was supported. We're in XP board, and there is no official alternative for this system. Remember that ;)

  • Like 1

Share this post


Link to post
Share on other sites

Since this issue has been discussed here , I would like to inform you that Mozilla 64 also suffers from the 23/25 min youtube mozilla bug. As it seems either they have not been able to fix it or simply they do not care.

 

cheers

  • Like 1

Share this post


Link to post
Share on other sites
17 hours ago, siria said:

 


No it often means nothing if something works in one browser and in another not, as so many people seem to assume. Sometimes yes, but very often not. Not everything depends from the system only, browsers can also bring some own capabilities too.
Especially that encryption/SSL/TLS stuff is contained completely independent inside all Firefoxes and the forks, as I've been told here. Unlike other browsers which fully depend on system capabilities. That's the reason why Firefox forks can still be updated to use TLS1.2 on systems even older as Win98, and other browsers are stuck with what the old system can do.

Yet lots of things which work fine can still fail if they simply aren't enabled in the settings.
Settings are an incredible jungle in FF/gecko, there are over 3000 prefs, and some most important ones not even showing up in aboutconfig, and many cross-influencing each other.
Clean installations also are no guarantee that everything is fully enabled out-of-box, as so many people assume. For example some of roytam's browsers for very old systems, like FF2, are now equipped with TLS1.2, yet out-of-box still have the ancient default setting of max TLS 1.0. Or stuff like hardware-acceleration, those settings are infamous to be helpful on one system yet disastrous on another, so intentionally not always enabled by default.

At any rate, if the map first shows up fine and then vanishes again, the browser CAN do it, and it really doesn't matter what Chrome or the system can. The solution or the workaround to persuade the server to send the tiles must be somewhere in the settings....

 

Problem solved: MyPal 28.3.1 works fine. So I´m gonna use this browser for now. Swapping browsers when a problem arise in any of them.

 

BTW, I tried changing the settings as explained before but it didn´t work. On the other hand, some other browsers did work, like old Chrome,

old Firefox and old Maxthon. Weird... because none of roytam1´s latest versions of Pale Moon browser worked on Google Maps.

Thanks anyway.

 

Share this post


Link to post
Share on other sites

 

Another thing... I don´t remember if there is already a solution for this, but, is it possible now to install this roytam1´s Pale Moon browser in portable

mode so it doesn´t create folders in C:? It does create two 'Pale Moon' folders here. MyPal in portable mode doesn´t create them.

Thanks.

Share this post


Link to post
Share on other sites
6 minutes ago, curiosil said:

is it possible now to install this roytam1´s Pale Moon browser in portable mode?

No.

  • Like 1

Share this post


Link to post
Share on other sites

WebGL work only with DirectX9 cards. The last DireceX9.0с and the driver is necessary for Windows XP

Fx5*** and Radeon 95**- x1200 - only CPU WebGL (layers.prefer-d3d9, webgl.force-enabled and webgl.disable-angle - true)

GF6100+ and Radeon x1300 + - GPU WebGL ( layers.prefer-d3d9, layers.acceleration.force-enabled, webgl.force-enabled - true)

Test https://get.webgl.org/

 

pm27.JPG

Edited by grey_rat
  • Like 1

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×