Leaderboard
Popular Content
Showing content with the highest reputation on 04/25/2026 in all areas
-
New build of Serpent/UXP for XP! Test binary: Win32 https://o.rthost.win/basilisk/basilisk52-g4.8.win32-git-20260425-3219d2d-uxp-8a2c4ec1a0-xpmod.7z Win64 https://o.rthost.win/basilisk/basilisk52-g4.8.win64-git-20260425-3219d2d-uxp-8a2c4ec1a0-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-20260425-3219d2d-uxp-8a2c4ec1a0-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-20260425-d849524bd-uxp-8a2c4ec1a0-xpmod.7z Win32 IA32 https://o.rthost.win/palemoon/palemoon-28.10.7a1.win32-git-20260425-d849524bd-uxp-8a2c4ec1a0-xpmod-ia32.7z Win32 SSE https://o.rthost.win/palemoon/palemoon-28.10.7a1.win32-git-20260425-d849524bd-uxp-8a2c4ec1a0-xpmod-sse.7z Win64 https://o.rthost.win/palemoon/palemoon-28.10.7a1.win64-git-20260425-d849524bd-uxp-8a2c4ec1a0-xpmod.7z Win7+ x64 AVX2 https://o.rthost.win/palemoon/palemoon-28.10.7a1.win64-git-20260425-d849524bd-uxp-8a2c4ec1a0-w7plus-avx2.7z Official UXP changes picked since my last build: - Issue #3027 - completely remove all remaining usages of dbus-glib from our tree (1d0967ab3c) - Issue #3050 - Backport 1379814: Prevent HelperThreads master-task deadlock (9454fcf539) - Issue #3050 - Backport 1431353: Remove off-thread parse thread limit (52b3fada95) - Issue #3049 - backport libffi loongarch support (dd64525180) - Issue #3038 - Fix ARM assembler issues in libpixman. (e98a43e46c) - [NSS] ensure permittedSubtrees don't match wildcards that could be outside the permitted tree. (662d60c5bf) - [XPCOM] Update list of executable extensions on Windows. (4d73188003) - [DOM] More consistently use already-calculated image properties. (7aaf0ab764) - Issue #2946 - Follow-up: Sanity-check WMF video properties. (8ffe5094c9) - [network] use nsCOMPtr for mRequest in Base Channel's ScopedRequestSuspender (2ece521467) - [media] Check alpha data pointer instead of length. (700b73f155) - [NSS] Protect rwSessionCount with slotLock. (29233ebca8) - [NSS] Fix memory leak in NSC_GenerateKey error path. (69fdabab8d) - Issue #3058 - Part 1: Fix arithmetic issue in `ConvertYCbCrToRGB32` (6048fc0fb7) - [DOM] Update some DOM canvas checks. (4d91f637b6) - [network] Use locals for `VisitHeader` (269b0cdb58) - [DOM] Add a death grip. (9e00ce775a) - [network] Hold strong ref in `nsDownloader::OnDataAvailable`. (cecf760aa5) - [network] Handle WebSocketChannel::IsPersistentFramePtr correctly. (8d189c4890) - Issue #3060 - Align cookie magic prefix handling with the updated spec. (fe8d56078e) - [DOM] Fix access to shared RuntimeService::mNavigatorProperties. (2f1af7557f) - [webrtc] Hold a self-ref on behalf of sigslot, just in case. (b73e47ce1c) - [network] Force NUL termination in ToStringBuffer AF_LOCAL. (b55a39ac33) - [network] Hold strong ref in `nsSyncStreamListener::Available`. (68fd6722f0) - [network] Ensure UDPSocket remains alive during CloseWithReason. (b6dec9b37c) 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 and icu63.dll 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.4 points
-
2 points
-
New build of BOC/UXP for XP! Test binary: MailNews Win32 https://o.rthost.win/boc-uxp/mailnews.win32-20260425-40a79c75-uxp-8a2c4ec1a0-xpmod.7z BNavigator Win32 https://o.rthost.win/boc-uxp/bnavigator.win32-20260425-40a79c75-uxp-8a2c4ec1a0-xpmod.7z source repo (excluding UXP): https://github.com/roytam1/boc-uxp/tree/custom * Notice: the profile prefix (i.e. parent folder names) are also changed since 2020-08-15 build, you may rename their names before using new binaries when updating from builds before 2020-08-15. -- New build of HBL-UXP for XP! Test binary: IceDove-UXP(mail) https://o.rthost.win/hbl-uxp/icedove.win32-20260425-id-656ea98-uxp-8a2c4ec1a0-xpmod.7z IceApe-UXP(suite) https://o.rthost.win/hbl-uxp/iceape.win32-20260425-id-656ea98-ia-c642e3c-uxp-8a2c4ec1a0-xpmod.7z source repo (excluding UXP): https://github.com/roytam1/icedove-uxp/tree/winbuild https://github.com/roytam1/iceape-uxp/tree/winbuild2 points
-
Read my report here and you will fix it easily: https://github.com/martok/palefill/issues/1091 point
-
I'm not under XP, I use NewMoon x64 under Windows 7. One way, or the other, good or bad job (as I'm not blaming roytam at all, but reporting), the thing is that now NewMoon freezes more, after the 20260411 build. Even if 20260418 doesn't freeze that much, it just did on this page. On 20260411 and earlier, didn't. It is true that GitHub is very intensive, but until 20260425, and particularly about February or March builds, GitHub rendering on NewMoon has enhanced a lot, as there were some glitches with some site functions that drive you to empty pages, as for example mark threads as read/done, and now (until 20260418 because 20260425 just freezes) works better. There shouldn't be a difference if it runs on XP or Win7. In my opinion.1 point
-
I looked in the network log with developer tools to find the reason. One option is to permanently switch to a profile with --user-data-dir. CORS disablement only works in conjuction with this option. I guess this is how you get a portable version.1 point
-
Okay, I got that "tidal" page to *WORK* in Ungoogled Chromium v144. NO EXTENSION REQUIRED. All I had to do is add the --disable-web-security command line switch to my list of switches. NO NEW PROFILE REQUIRED (at least for my portable config [which already has its own profile directory]).1 point
-
The extension's 'action button' probably doesn't appear on the extensions toolbar by default. If the extension is installed, look at the drop-down which appears when you click the extensions button (the one which looks like a jigsaw piece). There should be a pin icon next to the extension's icon, and the button should come and go when you click it.1 point
-
ps - I read this as "How are others fixing these issues on YouTube?". I do *everything* with userstyles and userscripts and *not* with uBO custom filters/lists.1 point
-
I rarely (if ever) use YouTube these days. But these are all of the userscripts and userstyles I was using. A couple of these may need updated, not really sure, but the all seemed to work as of a few weeks ago when I last visited YouTube.1 point
-
Did it cast you a 'pretty penny'? I have a few pennies that are pretty and shiny. It's a longer story. Oddly enough, I've had various problems with Avast! this year. Will probably write about it at the weekend. Then I will have time for it. One thing I can say: Although I had some concerns about the country of manufacture, WiseVector StopX is a great AV program and requires only few resources in terms of used disk space, RAM usage and CPU load. It's just perfect for an old box like mine! And the software is constantly being developed and maintained, is Windows XP compatible and free of charge. But, you have to configure it very carefully!1 point
-
If you're talking about X-Chromium, version 49.0.2605.0 rev16 is the last to run on XP. But of course such a version makes no sense at all, as it is far too old. Besides, in this age category, Advanced Chrome Custom Build 54.20.6530.0 is by far the very best.1 point
-
Interesting! But, these versions including older ones are not compatible with Windows XP, of course. Therefore, only for Windows 7 and higher.1 point
-
You're welcome! On my computers, I do have a perfectly working imaging system to restore important partitions in a very short time if they are damaged and not recoverable. Has saved my a** a lot of times! Just a tip!1 point
-
Looks like something has changed in memory management compared to older Chrome or Chromium versions. Hopefully for the better! Hope dies last!1 point
-
Hope you've got a backup of this partition for recovering if nothing helps. Try to boot into safe mode to see if it works in this mode. Use chkdsk to look for file system errors. Delete all temporary files before. Try to boot again in normal mode. If booting in normal mode is impossible, go back to a previous, working state by using recovery console. In case of recovery is not possible anymore, you should restore your previous, hopefully existing backup. I know much more possibilities to repair a damaged partition but it is too complicated to describe here, and you need appropriate knowledge to perform such interventions, of course. And truth be told, a black screen never bodes well. In most cases, I got a black screen when there was some hardware defective.1 point
-
Thanks a lot! That are unbiased and objective findings. Same as mine. I think there is nothing more to say.1 point
-
I see, 360Chrome v13.5 always does something different with one empty tab opened. Today, it uses 100 MB and tomorrow, it will use 500 MB. Sorry, no, your facts and values are useless if they only apply in your system. My little proof shows the inadequacy of your statements. And, who cares how much this browser consumes in your system. Much more important is how it behaves in general. By the way, capital letters are always used by those who shout, and there is absolutely no reason for that. It is rather impolite. There is a nice saying in Germany: "Wer schreit, hat Unrecht." Translated: "Who shouts is wrong."1 point
-
I am not necessarily a fan of the Chrome browser by nature. On my Android tablet, however, there is no getting around the Chrome browser. I use the latest versions of Opera, Brave and Kiwi there. The original Chrome browser from Google, however, is a real disaster and a data slinger. In Windows XP, I usually try to avoid Chrome browsers if possible. A pure Chrome 102 browser would be a no go for me in any case. I would prefer only good forks or mods of Chrome which consume less resources and are cleaned in terms of telemetry and privacy.1 point
-
I am glad that with 360Crome 13.5, there is a browser in Windows XP that can load many Googlized and heavy web pages the UXP browsers cannot handle in terms of JavaScript & Co. You did a great job in removing telemetry crap and translating Chinese strings in the past. Thanks for that again, @NotHereToPlayGames! Frankly, I hate to bring you down to earth in your praise of 360Crome 13.5. But, I'm a mathematician, I am always trying to find true statements, verifying or falsifying them, and I'm very good in any calculation. In order to disprove your statement, I use the principle of a counter-example. Your statement: I'm showing 360Chrome v13.5 with only the start tab open to consume 126 MB RAM. My assertion: 360Chrome v13.5 with only an empty tab opened consumes more than 450 MB. Proof: I disabled all my extensions in 360Chrome v13.5 and closed all tabs except one empty tab. I restarted the browser. Here is a screenshot while 360Chrome v13.5 is running. Here is a screenshot of CleanMem after closing 360Chrome v13.5: The RAM usage is shown in two different ways, by CleanMem and Process Hacker. My calculation: First method: Determination of RAM consumption by subtracting two RAM consumption values (360Chrome opened and closed) MEM1 = "Memory used while running 360Chrome v13.5" MEM2 = "Memory used after closing 360Chrome v13.5" RAMUSAGE = "RAM usage of 360Chrome v13.5 with all extensions disabled and only one empty tab opened" RAMUSAGE = MEM1 - MEM2 = 990.70 MB - 522.38 MB = 468.32 MB > 450 MB Second method: Determination of RAM consumption by adding all process usage values There are five processes: 360Loader.exe 4.75 MB 360chrome.exe 124.11 MB 360chrome.exe 113.60 MB 360chrome.exe 115.07 MB 360chrome.exe 119.43 MB Total: 476.96 MB > 450 MB Conclusion: With only one empty tab opened and all extensions disabled, your little darling tragically consumes more than 450 MB. Therefore, your statement is wrong, and my assertion is true. q.e.d. Unfortunately, the truth is this browser is a RAM eating machine at its best. If I enable a few extensions and open one or two more tabs, everything gets much worse, RAM consumption increases enormously, and my system is blocked and no longer responds. For users, having a huge amount of RAM in their computers, no problem at all, of course, but for the others ... Truth be told, I don't know where you get your values from, but in any case, they have nothing to do with reality. Such "facts" are meaningless! Sorry to say that! For me, and I speak only for myself here, 360Chrome v13.5 is not really a no-brainer win. But, using this browser with only one tab opened is possible, of course. And no offence, only real facts and the truth! Kind regards, AstroSkipper1 point