Jump to content

AstroSkipper

Member
  • Posts

    4,565
  • Joined

  • Days Won

    457
  • Donations

    0.00 USD 
  • Country

    Germany

Everything posted by AstroSkipper

  1. That's why I usually avoid to modify the hosts file. The more configuration files are involved in establishing network connections, the more difficult to find the causer of issues. On my computer, only the firewall is responsible for the network connections. And Windows 10 Firewall Control Plus XP has been doing a great job without any problems. All configurations can be done with it. Enabling or disabling specific, self-created rules is very easy. No need to do it via the hosts file.
  2. So, long story short. The Project VORAPIS 0.9.0.0 script works fine in Mozilla based browsers like New Moon 28 and Serpent 52 which are the browsers this thread is about. And it also works in Mypal 68, all tested by me.
  3. @NotHereToPlayGames But TBH, the Project VORAPIS 0.9.0.0 script itself works as well as the TURBOLAUNCHER 2.1.0.0 script in New Moon 28 and Mypal 68 on my old machine. Therefore, I assume you configured your computer badly, and by that I mean your adblocker.
  4. 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.
  5. 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.
  6. 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.
  7. 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.
  8. 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.
  9. 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.
  10. Thanks for reporting! TBH, I didn't expect any further root certificate updates via CAupdater 1.0 or Certificate Updater 1.6. Great news!
  11. 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.
  12. 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.
  13. I already wrote about this general.config.sandbox_enabled preference in terms of the Nuchi-Sporif script loading method and other ones:
  14. I thought the general.config.sandbox_enabled preference is the one to be enabled if the user wants to use the sandbox feature.
  15. 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.
  16. 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.
  17. @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.
  18. 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.
  19. 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.
  20. 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.
  21. 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.
  22. I have looked at the documentation for disabling programme updates. Supposedly, there is an option with the entry: Did you really try this switch?
  23. 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.
  24. I'm really sorry, but I'm not a fan of meaningless drivel. You should use your time more wisely!
  25. 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.
×
×
  • Create New...