AstroSkipper

Disregard! That was short-lived! Videos are consistently stopping about three and half minutes in then the infamous swirling circle indicating buffering rears its ugly head! One to two hours! You've never been satisfied with anything for so long. I think that's a new record. Install the TURBOLAUNCHER 2.1.0.0 script (a launcher script for VORAPIS) instead of the Project VORAPIS 0.9.0.0 script itself! Works fine in New Moon 28 on my old machine. No interruptions of the stream, and no swirling circle here.

You are running the New Moon 28 SSE release. I assume your CPU does not have the SSE2 instruction set and is a very old one like mine although my Pentium 4 CPU is equipped with the SSE2 instruction set. The website https://www.auf1.tv can be accessed with New Moon 28 (palemoon-28.10.7a1.win32-git-20250222-d849524bd-uxp-e43876ec84-xpmod.7z) but on old, weak computers, it's more of a pain than a pleasure. You should avoid this website, at least on old devices. The page is overloaded with media, loads terribly slowly and uses around 200 MB of RAM. The CPU load is high due to all animations and transitions. I can block them via CSS, and the CPU load immediately becomes normal. But then the news ticker is no longer running, of course. I think such websites should be accessed on modern devices, and the reason for your issue is most probably the lack of the SSE2 instruction set in your CPU which might be necessary to correctly load this website.

Disregard! That was short-lived! Videos are consistently stopping about three and half minutes in then the infamous swirling circle indicating buffering rears its ugly head! One to two hours! You've never been satisfied with anything for so long. I think that's a new record.

On the Mozilla Support website https://support.mozilla.org/en-US/kb/root-certificate-expiration, you can find this announcement: In terms of Window 7 computers, this means that users of Firefox 115 ESR should update their browser at least to version 115.13 ESR to fix certificate problems. As far as I know, the nssckbi.dll file inside the Firefox programme folder defines the default set of trusted root certificates. The more recent this nssckbi.dll file, the more recent Firefox's default root certificates.

FYI, since Firefox 58, Mozilla has changed the files cert8.db/key3.db to cert9.db/key4.db. Therefore, you won't find a cert8.db or key3.db file in the profile folder of Firefox 115..x.x ESR releases. And the certificates are stored in the cert9.db file. This file is generated by Firefox and stored in the profile folder. If it is deleted, it will be immediately generated by the browser again. Firefox also checks the system root certificates and automatically performs some imports. Here is a quotation from a Mozilla website (an important note was made bold by me): If I was on Windows 7 and used Firefox 115 ESR there, I would first update to the latest version (at the moment 115.20.0 from February 2025). This does not improve a rubbish browser , but the certificates it contains should actually be up-to-date. And after performing a backup of the profile folder, one can import certificates until the doctor comes (German saying ) and then check whether it works or not. If not, delete the cert9.db file or restore the profile backup. It's as simple as that.

I don't know where you've got the information about the latest release of DreamMail Pro from. On its homepage https://www.cy-email.com/, the latest offered version is 6.7.1.8 from 22.02.2025 which is listed as XP-compatible. In any case, there is no version 7.

Thanks for reporting! TBH, I didn't expect any further root certificate updates via CAupdater 1.0 or Certificate Updater 1.6. Great news!

At the moment, I have reverted to the last officially compatible version 1.46. But I will test the 1.56 version again. Thanks for the hint! @feodor2 I moved to the most recent, final version of uBlock Origin which is 1.62 at the moment. The logger works fine in multi-process mode but in single-process mode, the logger popup window is very unstable. Some extensions, scripts and whatever else interfere considerably with the loading and display of the logger popup. It often remains empty. Resizing the logger window helps in some cases. I investigated this further and found that changing the advanced setting loggerPopupType from popup to normal may be a solution. In this case, the logger is opened in a normal window in which it loads fine as far as I could see until now. At least, on my computer with its current configuration. I'll keep an eye on that. P.S.: @feodor2 Now, I have realised what you meant by using the context menu. I have never opened the logger interface via its icon context menu before. Indeed, this also works in both process modes to properly open the logger in a tab or window. However, changing the advanced setting loggerPopupType from popup to normal is of interest for those who prefer only one normal left-click on the logger icon as usual.

Today, I created a subroutine to catch errors ,for example a TypeError, caused by the document.getElementById() or document.querySelector() commands when a page is loading too slowly. I use these error messages to check as long as a successful access to an element is granted and then to immediately execute the desired commands. This avoids unnecessary, static setTimeout commands and error messages in the Browser Console.. Works like a charm. And I'm not in the mood to use observers everywhere.

I already wrote about this general.config.sandbox_enabled preference in terms of the Nuchi-Sporif script loading method and other ones:

I thought the general.config.sandbox_enabled preference is the one to be enabled if the user wants to use the sandbox feature.

At the moment, I have reverted to the last officially compatible version 1.46. But I will test the 1.56 version again. Thanks for the hint! @feodor2 I moved to the most recent, final version of uBlock Origin which is 1.62 at the moment. The logger works fine in multi-process mode but in single-process mode, the logger popup window is very unstable. Some extensions, scripts and whatever else interfere considerably with the loading and display of the logger popup. It often remains empty. Resizing the logger window helps in some cases. I investigated this further and found that changing the advanced setting loggerPopupType from popup to normal may be a solution. In this case, the logger is opened in a normal window in which it loads fine as far as I could see until now. At least, on my computer with its current configuration. I'll keep an eye on that.

Keeping single-process mode is really a good idea and very important for those running Windows XP on old, weak computers. Actually, this mode works much better in Mypal 68.14.7b than in the previous releases. I've already mentally and emotionally prepared myself for the next compatibility breakages you'll soon be unleashing. I am really curious to see what will no longer work in the next version as it did in Mypal 68.14.5b. In the meantime, I have written a whole series of UC.JS scripts to be on the safe side if a lot of my older stuff do not work anymore. Hope the Custom Buttons extension will still work in your next Mypal 68 release as it should actually be able to run in newer Firefox versions up to at least 136 as well. And if it works there, it should also be possible in newer Mypal 68 versions with a much lower JavaScript level.

@feodor2 When creating UC.JS scripts, I noticed that some Vanilla JavaScript commands behave differently in single-process mode compared to multi-process mode. When starting the browser, loading new tabs or windows, accessing elements via document.getElementById() and especially via document.querySelector() needs much more time in multi-process mode than in single-process mode. Is there any explanation for this? Is this by default or rather a Mypal 68 specific behaviour? When, for example, starting the browser with the about:addons page, it takes nearly 8 seconds after DOM is loaded to be able to access an element in multi-process mode via document.querySelector() . In single-process mode, it can be accessed directly. This is very strange and does not make the multi-process mode particularly attractive.

Where did you see that this switch is only for automatic definitions updates? BTW, I have not only linked a screenshot, but also quoted from the online help: That sounds to me not only like definition updates, but also like programme updates. I cannot judge what is ultimately meant by this, as I do not have a licence.

IMHO, a very simple and clean way is to unpack the new Mypal 68 archive file to a new folder, open the browser from there and create a new profile with the same name of your old profile to be imported by using Mypal 68's profile manager. Then, close the browser. Now, delete all files of your just created profile folder and copy the old ones from your backup into it. Now, start the browser again with this new profile. Done! At the moment, I have 10 different Mypal 68 programme folders and many, many profiles, only for the purpose of developing and testing, of course. No problems here.

TBH, updating New Moon 28 is as quick and easy as reverting to a previous version. So, there is really no reason to be afraid.

Thanks for your report! Avast 18.8.4084 was a terrible version from the start. As I reported at the time, it produced many problems. In the end, it couldn't even be uninstalled in the normal way. When I have the time and inclination, I'll try Avast 18.5.2342, although I've actually shelved Avast.

I have looked at the documentation for disabling programme updates. Supposedly, there is an option with the entry: Did you really try this switch?

Interestingly, your French Amazon site runs better in New Moon 28 than in Mypal 68, i.e. switching between the different models works, albeit rather sluggishly, at least on my old computer.

I'm really sorry, but I'm not a fan of meaningless drivel. You should use your time more wisely!

Nobody asked you to neglect your "career". BTW, no one has spoken of this, and it is not the issue here at all. But if you take the trouble to reproduce something I said, then it should correspond to what I said. And if you don't really understand it, you should either quote it verbatim as you have done now: Bingo! or simply not refer to it at all. P.S.: I think bragging about your "above-average salary", whatever that means and whoever cares, is rather inappropriate and doesn't belong here.

I think it is more something like that ... There was no alpha but a correlation coefficient r of r > 0.95 to express the almost perfectly linear correlation between two statistical variables, the user interest and the (actually my) willingness for publishing. If you want to refer to what I have stated, then please in a correct way. To put it in simple, non-mathematical terms, the greater the user interest, the greater my mood to publish something.

I already reported here that Amazon Germany stopped working properly in Mypal 68.14.x: https://msfn.org/board/topic/183495-mypal-68/page/76/#findComment-1275586 Your posted article on Amazon France has even led to a crash of Mypal 68.14.7b on my old Windows XP machine when clicking on 8 ports Métal 34,99€. The causer of this misery is of course not @feodor2, but the website designers at Amazon, strictly following the rule: The more bloated, the better. However, I personally hope that @feodor2 can fix it one day.

Not necessary - here the custumbutton already published by you /*Initialization Code*/ var prefName = "security.csp.enable"; var enabledImage = "data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAUCAYAAACNiR0NAAAAAXNSR0IArs4c6QAAAARnQU1BAACxjwv8YQUAAAAgY0hSTQAAeiYAAICEAAD6AAAAgOgAAHUwAADqYAAAOpgAABdwnLpRPAAAAO1JREFUOE9jZPgPhFQFIAOpCalqGNi31HQdfQz8R6Gb4drVwLGNwGlQGWQxWAC5Iqnjg7LnwtSD/G0GFYSFpzSQzwTEfWjiIANhPgCx7aGG6COpg6bD/wxuWLzagWYgcgSCDDSG6pmHzcBuHGEH83IEmjxI3A4qpoDNQJBrcMFcpDCDqYFZFACV248chiBJayzGgcLrA5I4SF0tTCOQNsCiByxkBLXlJVTBOSCdA8RiaGEIMnADkoGmuAwEGSqO5C2QxlYgPg8VY4bSoCQCgqFIasPQDMViB2ZI/iFKFUQfCUqJy/WjBhIXTnhUAQCxF7FzNVSQlgAAAABJRU5ErkJggg=="; var disabledImage = "data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAUCAYAAACNiR0NAAAAAXNSR0IArs4c6QAAAARnQU1BAACxjwv8YQUAAAAgY0hSTQAAeiYAAICEAAD6AAAAgOgAAHUwAADqYAAAOpgAABdwnLpRPAAAAOlJREFUOE9j/M/AAERUBCADqYlBzhvpBv6jMAjgYagGiW04ToMajCwGYoPC3BVJHR+UPRemHqTADCoIiyBpIJ8JiPvQxEEGwnwAYttDDdFHUgd2IUjSDYtXO9AMRE4RID3GUD3zsBnYjSPsYF6OQJMHidtBxRSwGQhyDa40mYsUZjA1MIsCoHL7kcMQJGmNxUBQeH1AEgepq4VpBNIGWPSAw9AIastLqIJzQDoHiMXQwhBk4AYkA01xGQgyVBzJWyCNrUB8HirGDKVBSQSkNhRJbRiaoUTl5T94whc93IkykJQCZNRAygtbAOb2sXODGkDmAAAAAElFTkSuQmCC"; this.onclick = function (aE) { if (aE.button === 0) { Services.prefs.setBoolPref(prefName, !Services.prefs.getBoolPref(prefName)); setSelfImage(); } }; function setSelfImage() { if (Services.prefs.getBoolPref(prefName)) self.image = enabledImage; else self.image = disabledImage; } setSelfImage(); replace "security.csp.enable" with the desired thing Toggle CSP is a custom button I created for only toggling one preference in about:config and made it available almost two and a half years ago. To be honest, there wasn't much interest in this button. And your suggestion to use this button as a template is a little off the mark. Toggling the browser.tabs.remote.autostart preference has no direct effect while the browser is running and can't be a solution as you actually should know. More steps are to perform. If you compare the two buttons, you should notice that the PMT - Process Mode Toggler custom button has a much more complex functionality than the Toggle CSP custom button. BTW, I have revised the Toggle CSP custom button some time ago and designed it so that the manual switching of the security.csp.enable preference, for example, in about:config is also registered by the custom button to always display the correct status via the button image as well as via the button tooltip, even in such or similar cases. However, the PMT - Process Mode Toggler custom button does not need such modification, and thus, I have already removed it again, as solely toggling the browser.tabs.remote.autostart preference has no effect on the current browser session in terms of its process mode. Why to tease then? Teasing? I do not tease anyone. I just demonstrated what custom buttons are capable of, and I made it clear to think about publishing if sufficient interest was shown. No more, no less. However, I cannot see this at the moment. And to be honest, I don't know what your problem actually is. Regarding the PMT - Process Mode Toggler custom button, which I already made available for you only, I am the creator and decide for myself if and when I publish something. Just like you do when it comes to Mypal 68. One thing is clear: you are you, and I am me. No pills will help. @feodor2 If you want to tell me something specific, you should articulate it as clearly as possible. I’m not a fan of reading between the lines or subliminal hints.