Leaderboard

better try compiling directly from rmottola's AF dev branch first, you may just fork it and create a new branch for your changes. I do have a winbuild branch of AF to merge upstream's dev branch changes. and my changes in my repo comes from upstream's dev branch changes and my winbuild branch changes squashed with `git diff oldrev..newrev` and apply it in my NM27 master branch(also needs fixing since my master branch doesn't very winbuild branch alike). but these nightmares are long-gone for me as it doesn't fit my needs now.

I wonder if this could be done with a plug-in? I realize that NPAPI plug-ins are considered passe and aren't supported by more modern browsers, but UXP still supports them; if it would work it would be a perfect way to add support for new image compression formats without having to add bloat to the browser itself. They may be right; I don't know. But that's a question for Web sites to consider, not for browser developers like MCP! The question for MCP should be, are there enough Web sites using AVIF that lack of support is a barrier to using PM? If not, don't spend time on it; there are other areas that need more attention. But if there are, then MCP needs to support it, even if it's crappy; or PM will lose even more users. MCP is not Google! (Thank goodness!) They can't kill something they don't like by refusing to support it; they can only hurt themselves.

I'll join the chorus of disagreement, integrating storage drivers is perhaps the most important option, on many systems doing so is the only way XP x64 can be installed.

@feodor2 Here is my feedback to your new release Mypal 68.14.7b: I can confirm that the loading and scrolling websites issue in multi-process mode doesn't occur anymore. Same applies to the issue that the GIF image animation was broken in single-process mode. This issue doesn't occur anymore, either. And last not least, same applies to the issue that the last confirmation popup is incorrectly displayed when installing extensions. This issue doesn't occur anymore, either. Good job! So, thank you very much for your quick bug fix version and for all your efforts! Greetings from Germany, AstroSkipper

Then you simply haven't read many of the posts in this thread and in my thread about UXP browsers. FYI, I have neither ruled out nor promised a release of the PMT - Process Mode Toggler custom button even though I generally create custom buttons for personal use. I have written at least six new custom buttons for Mypal 68 in the last few months. And long before that quite a few for the UXP browsers. After releasing some of them, I could not recognise any significant interest. BTW, I have also deepened my JavaScript and CSS knowledge considerably to modify already existing UC.JS scripts and especially to create new ones from scratch. Both are in full swing. It should be mentioned at this point that everything is purely self-taught. Programming is just a hobby of mine. I never learned it professionally. Anyway! Due to a lack of real interest in legacy custom buttons, it seems pointless to me to publish my custom buttons at the moment. I have put it in a nutshell here: Apart from that, I have already published so many different things in this forum that it is difficult for me to keep track. But I don't necessarily have to publish things that nearly nobody appreciates or wants to use. That's exactly how I see it. But we are probably the exceptions here. And then the user would also have to familiarise themselves with the special JavaScript language and its syntax provided by the Custom Buttons extension (there are commands and variables that do not exist in the standard JavaScript language) ... After all, a similar button as a template for a desired one is not always available. Long story short: the ball is now in the court of the readers of this thread.

I don't agree with this statement, I personally integrated those, all worked fine. It's not "stupid".

@feodor2 Thanks in advance! And since you are the creator of Mypal 68, have kindly restored compatibility with the legacy Custom Buttons extension and have already installed it, I have chosen you as the very first to install my new custom button PMT - Process Mode Toggler, which I created for use in Mypal 68, only if you want, of course. I am really interested in your opinion, which you are welcome to post here or in my thread Mypal 68 in Windows XP - Custom Buttons and Extensions. I'll send you the download link via PM. The use of this custom button is explained in the Button Help which can be accessed by a right-click onto this button. Greetings from Germany, AstroSkipper

@feodor2 And after all the issues I've reported here, here's something positive that I've noticed. Mypal 68.14.6b runs pleasantly fast in single-process mode and seems to use less RAM than before. That is really pleasing. Thanks for that!

Mypal 68.14.6b - Confirmation popup incorrectly displayed when installing extensions @feodor2 When installing extensions in Mypal 68.14.6b, the last confirmation popup is incorrectly displayed. It doesn't matter whether running the browser in single-process mode or multi-process mode. Here is a screenshot: Here is, for example, a screenshot taken from Mypal 68.14.4b where this confirmation popup is correctly displayed. TBH, this issue is not as important as the previous ones but it is an issue. Or did you make this change consciously?

I'm using DiskGenius 5.6.1.1580 on XP and it works fine. It is however one of those programs that won't install on XP, you have to use the portable version.

I have a great deal of appreciation and respect for what Moonchild, MCP, and you have accomplished with PM, Basilisk, and the UXP platform, but, "always?" I think the word "originally" would be more accurate. I first downloaded and used PM back in the early 2000's when I was still using Windows 98. At that time, PM was basically just a clone of Firefox, but compiled for better performance; much appreciated on that old 733 MHz Pentium machine. But PM and Basilisk (and @roytam1's versions of those) have gotten quite a bit away from just being Firefox compiled with better optimizations. Today, folks (including me) turn to them for many good reasons, but I daresay no one uses them nowadays because they want a higher-performance FF clone! The words in bold are doing a lot of work there. In fact, I believe that not running on older CPUs was a strong implicit motivation, as opposed to an explicitly stated reason, for the change. I chose the word "noticeable" poorly when I said "... not to give PM a noticeable performance improvement on newer 64-bit processors that do support AVX instructions." Perhaps I should have said "significant," as the meaning I wanted to convey was "enough performance improvement to turn the use of PM on Javascript-laden sites from a painfully slow experience into a reasonably responsive one."

@roytam1 I have a Visual C++ 2013 update 4 build of your New Moon 27.10.0 20241220 build, taken from the palemoon27-master branch in your repository. Previously, you had merged Arctic-Fox commits into your palemoon27 repository, and "squashed" them so that all the Arctic-Fox commits you merged will appear as 1 commit. If I have the source code to palemoon27-master, and the Arctic-Fox-master git information (presently at version 45.2 from January 6th 2025), what git command do you recommend I use in order to merge commits from Arctic-Fox (I only know git cherry-pick)? Also, I asked you if you could create a VC2015 branch in your palemoon27 repository, and see if you could merge the latest Arctic-Fox commits to that branch. I finally decided to try a VC2015 build of New Moon 27.10.0 20241220, and it failed 8 minutes in with errors in the type_traits file built into Visual C++ 2015, but when I tried a VC2013 build, it compiled cleanly taking 76 minutes. That means creating a "VC2015" branch for the purpose of evading Visual C++ 2013 compatibility is not necessary in my opinion, but a "tracking" branch that is not meant to be compiled but merged to may be helpful to determine if merging commits from Arctic-Fox will still work (I'm scared of git).

New build of post-deprecated Serpent/moebius for XP! * Notice: This repo will not be built on regular schedule, and changes are experimental as usual. ** Current moebius patch level should be on par with 52.9, but some security patches can not be applied/ported due to source milestone differences between versions. Test binary: Win32 https://o.rthost.win/basilisk/basilisk55-win32-git-20250201-762691794-xpmod.7z Win64 https://o.rthost.win/basilisk/basilisk55-win64-git-20250201-762691794-xpmod.7z repo: https://github.com/roytam1/basilisk55 Repo changes: - import from UXP: Issue #2686 - Don't rely on return value of ExecutionContext::Compile when the context may forbid running scripts (0590764f) (36eaeed46) - import from UXP: Issue #2688 - Don't apply auto min-sizing when flex max-sizing. (0849deea) (1f720079b) - import from `custom` branch of UXP: Update eTLD list (PSL) (064d8757) (762691794)

New build of Serpent/UXP for XP! Test binary: Win32 https://o.rthost.win/basilisk/basilisk52-g4.8.win32-git-20250201-3219d2d-uxp-bf90272692-xpmod.7z Win64 https://o.rthost.win/basilisk/basilisk52-g4.8.win64-git-20250201-3219d2d-uxp-bf90272692-xpmod.7z source code that is comparable to my current working tree is available here: https://github.com/roytam1/UXP/commits/custom IA32 Win32 https://o.rthost.win/basilisk/basilisk52-g4.8.win32-git-20250201-3219d2d-uxp-bf90272692-xpmod-ia32.7z source code that is comparable to my current working tree is available here: https://github.com/roytam1/UXP/commits/ia32 NM28XP build: Win32 https://o.rthost.win/palemoon/palemoon-28.10.7a1.win32-git-20250201-d849524bd-uxp-bf90272692-xpmod.7z Win32 IA32 https://o.rthost.win/palemoon/palemoon-28.10.7a1.win32-git-20250201-d849524bd-uxp-bf90272692-xpmod-ia32.7z Win32 SSE https://o.rthost.win/palemoon/palemoon-28.10.7a1.win32-git-20250201-d849524bd-uxp-bf90272692-xpmod-sse.7z Win64 https://o.rthost.win/palemoon/palemoon-28.10.7a1.win64-git-20250201-d849524bd-uxp-bf90272692-xpmod.7z Official UXP changes picked since my last build: - Issue #2686 - Don't rely on return value of ExecutionContext::Compile when the context may forbid running scripts (0590764f1f) - Issue #2688 - Don't apply auto min-sizing when flex max-sizing. (0849deeacf) - Update eTLD list (PSL) (064d8757f5) No official Pale-Moon changes picked since my last build. No official Basilisk changes picked since my last build. Update Notice: - You may delete file named icudt*.dat inside program folder when updating from old releases. * Notice: From now on, UXP rev will point to `custom` branch of my UXP repo instead of MCP UXP repo, while "official UXP changes" shows only `tracking` branch changes.

I do not get why @AstroSkipper do not want put it for all available. There is nothing extraordinary, you can make any custum button you want, take another similar button available as example and replace inside its setting with process switch.

The 68.14.7 version is finished. https://codeberg.org/Theodor2/Mypal68/releases

Update Download: Make_WinPE_Trusted-97 - E = file Encrypted with pw=bootwimb - Cleanup of File_List files - Removal of duplicates in file entries - SMALL_Add_Install_Files_10.txt improved with extra 30 MB PE Size so that Desktop DPI Setting is working with DPIScalingMFCApp.exe It means in fact that SMALL = WinXShell Version and LARGE = Explorer Version have almost the same List of Added files from install.wim Advantage is a much better PE Desktop now also for the SMALL = WinXShell Version with adjustable DPI Setting Windows 11 24H2 requires additional extra files to get Desktop DPI Setting working with DPIScalingMFCApp.exe For the time being this is considered as the final version ..... But for sure new adjustments will be needed when New Windows ISO Versions arrive ...

I compared the extracted WD HDD from My booksplastic box, which I wrote about before, and it's identical to the famous Red Series (NAS drives). WD80EFZZ, ir was still produced, at least in 2022. The only difference is the label, mine is white, without the red stripes. It's 100% made by Hitachi.

Just a small hint. My custom button is called PMT - Process Mode Toggler. It toggles the process mode and is therefore a toggler. Back to your statement. If you really want to install the Custom Buttons extension for only one custom button without any deeper interest in Mypal 68 anyway, since you are a user who always deletes everything after a short time, then it's not worth the effort at all. This extension actually only makes sense if you want to retrofit missing features or if you plan to replace a lot of extensions by custom buttons which have only a very low resource consumption and are much less restricted than webextensions. These custom buttons can do things which webextensions are not allowed to do . And especially my self-created custom buttons do exactly what I want them to do.

This is incorrect. Pale Moon was always intended to be a browser that was utilized newer CPU optimizations to increase performance. Your claim that it was done with the explicit intention of running on older CPUs is false, although that is an unfortunate side effect of enabling the AVX instruction set. There is absolutely a noticeable performance improvement when comparing the AVX builds to the pre-AVX builds. I disagree with the requirement to have AVX instruction support to run Pale Moon and I think it was a bad move on Moonchild's part, but basically every claim here that you've made is either false or misguided.

US withdraws from Paris climate deal on Jan. 27, 2026 https://www.reuters.com/business/environment/us-withdraw-climate-deal-jan-27-2026-says-un-2025-01-28/

+1

Mypal 68.14.6b - GIF image animation broken in single-process mode @feodor2 Purely by chance, I have discovered that the animation of GIF images in Mypal 68.14.6b does not work when the browser is operated in single-process mode. Of course, the preference image.animation_mode is set to the value normal. When switching to multi-process mode, however, the animation of GIF files works again. So this seems to be an issue that only affects the single-process mode. Look at my Matrix GIF image below! I should still mention that this issue didn't occur in your previous releases. Cheers, AstroSkipper

We are here to study, if you don't, then don't reply. No one's interested to read your spam.