Leaderboard

New build of Serpent/UXP for XP! Test binary: Win32 https://o.rthost.win/basilisk/basilisk52-g4.8.win32-git-20220702-3219d2d-uxp-3926096df-xpmod.7z Win64 https://o.rthost.win/basilisk/basilisk52-g4.8.win64-git-20220702-3219d2d-uxp-3926096df-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-20220702-3219d2d-uxp-3926096df-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.6a1.win32-git-20220702-d849524bd-uxp-3926096df-xpmod.7z Win32 SSE https://o.rthost.win/palemoon/palemoon-28.10.6a1.win32-git-20220702-d849524bd-uxp-3926096df-xpmod-sse.7z Win64 https://o.rthost.win/palemoon/palemoon-28.10.6a1.win64-git-20220702-d849524bd-uxp-3926096df-xpmod.7z Official UXP changes picked since my last build: - Issue #326 - Part 3: Explicitly make the Script enum a 16-bit type (7c2d94821) - Issue #326 - Part 4: Update Unicode data to release 10.0 (54489c302) - Issue #326 - Part 5: Simplify the genUnicodePropertyData.pl tool to generate only the data we need to supplement ICU properties (b8e7234b7) - Issue #326 - Part 6: Regenerate Unicode data tables with the stripped-down tool (8ad8bfb4b) - Issue #1933 - Part 1: Update build system for libjpeg-turbo. (75e223e3b) - Issue #1933 - Part 2: Update libjpeg-turbo source. (fc2133f4d) - Issue #1935 - Update libogg to 1.3.5 (9f598a8ab) - Issue #1939 - Part 1: Update build system for libwebp. (56d49fd57) - Issue #1939 - Part 2: Update libwebp source. (8038505d6) - Issue #1941 - Update libvorbis to 1.3.7. (191a010f6) - Issue #1053 - Follow-up: Correct conditional define on POSIX systems. (c0f4b97fa) - Issue #21 - Follow-up: Remove some left-over telemetry plumbing. (c43ed8d93) - Issue #1933 - Follow-up: Fix building on ARM. (0eece8e5b) - Issue #1933 - Follow-up: Remove cmakedefine directives from neon-compat.h. (b29aa5d55) - Issue #1944 - Fix volume handling in sndio backend. (ef4db6f2a) - Issue #1944 - Follow-up: Make it clear that volume is a float. (5b40dbab4) - Issue #1937 - Part 1: Update build system for libaom. (d09a5eeca) - Issue #1937 - Part 2: Update libaom source. (ecb7ec737) - Issue #1937 - Follow-up: Fix sources.mozbuild not having exports (49696a788) - Issue #1937 - Follow-up: Add missing sources and includes in sources.mozbuild (8c7e76360) - Issue #1937 - Follow-up: Add missing sources, and remove unneeded ones in sources.mozbuild (463a50276) - Issue #1937 - Follow-up: Exclude aom_encoder.c/h from our build (932e9d8fc) - Issue #1937 - Follow-up: Remove some unnecessary includes and sources from sources.mozbuild (6f97a5012) No official Pale-Moon changes picked since my last build. No official Basilisk changes picked since my last build. My changes picked since my last build: - DownloadUIHelper: move `async` keyword position to prevent raising javascript error. (3926096df) * 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.

The mirror of latest BNavigator, Firefox 45ESR, IceApe, IceDove, K-Meleon 1.5.x/74/76, MailNews 52, New Moon 26.5/27/28 and Serpent 52/55 builds by @roytam1 has been updated -> soggi.org - tools. changelog: - added latest BNavigator 0.9 20220702 build - added latest IceApe 52 20220702 build - added latest IceDove 52 20220702 build - added latest K-Meleon 76 20220702 build - added latest MailNews 52 20220702 build - added latest New Moon 27 20220702 builds - added latest New Moon 28 20220702 builds - added latest Serpent 52 20220702 builds - added latest Serpent 55 20220702 builds I can confirm that latest NM28 (20220702) has no problems with downloading files anymore! :) BTW if I want to replace MS OE on Win XP SP3...MailNews is the right option!? I just have to know...have to go forward with our mail accounts...maybe...sometime. kind regards soggi

New NewMoon 27 Build! 32bit https://o.rthost.win/palemoon/palemoon-27.10.0.win32-git-20220702-20a13aae5f-xpmod.7z 32bit SSE https://o.rthost.win/palemoon/palemoon-27.10.0.win32-git-20220702-20a13aae5f-xpmod-sse.7z 32bit noSSE https://o.rthost.win/palemoon/palemoon-27.10.0.win32-git-20220702-20a13aae5f-xpmod-ia32.7z 64bit https://o.rthost.win/palemoon/palemoon-27.10.0.win64-git-20220702-20a13aae5f-xpmod.7z source repo: https://github.com/roytam1/palemoon27 repo changes since my last build: - import changes from `dev' branch of rmottola/Arctic-Fox: Bug 1195162 - Remove unused pref layout.debug.enable_data_xbl (r=sicking) (04c4996c90) (c5eef2df55) - imported changes from mozilla NSS: - Bug 1767590 - Initialize pointers passed to NSS_CMSDigestContext_FinishMultiple r=#nss-reviewers,kaie (118b893f8e) - Bug 1759794 - protect SFTKSlot needLogin with slotLock. r=rrelyea (1bbd8d8c) - Bug 1771497 - Uninitialized value in cert_VerifyCertChainOld. r=nss-reviewers,djackson (23be110c) - Bug 1771495 - unchecked return code in sec_DecodeSigAlg. r=nss-reviewers,djackson (d4fb4b83) - Bug 1771498 - Uninitialized value in cert_ComputeCertType. r=djackson (b28bc4cd) - Bug 1764392 - Add DigitCert Roots r=nss-reviewers,jschanck (0863d9ec) - Bug 1768970 - Add Certainly Roots. r=nss-reviewers,jschanck (6307e75b) - Bug 1770267 - Add E-Tugra Roots. r=nss-reviewers,jschanck (9555008f) - Bug 1759815 - Remove Hellenic Academic 2011 Root. r=nss-reviewers,jschanck (9c2cbf14) - Bug 1764206 - Bump nssckbi version number for June. r=nss-reviewers,jschanck (b3acf3d9) - zlib: also pick up https://github.com/madler/zlib/commit/4346a16853e19b45787ce933666026903fb8f3f8 (20a13aae5f)

A bit unrelated... but as one Waterfox classic contributor is trying to add a big missing Javascript feature into WC (Module/Dynamic imports) - i wonder if this can also be adopted to Pale Moon/New Moon? https://github.com/WaterfoxCo/Waterfox-Classic/issues/121 The only issue is that Pale Moon/New Moon is based on the Firefox 52 engine while WC is based on 56. But its one big addition which would be able to remove another big web incompatibility issue for UXP based browsers if that one somehow could be added. @roytam1 What do you think about this?

Thank you, @XPerceniol , for your reply; I shall wait another week for the next best version, those zeroed settings should be settled by then I hope.

@XPerceniol Thank you very much for this I might try it tomorrow and report back. (This computer I use in my uncle's internet shop)

Hello there.. Please go to your about:config and make changes. dom.max_chrome_script_run_time <- please change to 0 dom.max_script_run_time <-please change to 0 dom.moduleScripts.enabled <-please toggle false to see, this helps me very much. dom.ipc.processHangMonitor <-please toggle to false. dom.ipc.reportProcessHangs <-please toggle to false Keep us posted and good luck :)

Thanks for your advice. I will give a try. BTW, the ArcticFoxie build you mentioned is same telemetry-free modified as the build posted in this thread? Thanks.

first error in error console is resolved. https://github.com/roytam1/boc-uxp/commit/0abce9fa27bc80b444c3c6bb60b408bb3a97b581

A dump of the GPU memory sounds like what you want, but in my brief online search, anyone asking for that has their question ignored. The closest thing I could think of is to track all memory allocations (and memory freeing up) from the driver, and I am not aware of an off-the-shelf solution for that. I started writing my own drivers now, mostly to deal with the GPU issues and enhance other parts of the kernel. Hopefully there will be some results from that soon.

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 http://o.rthost.win/basilisk/basilisk55-win32-git-20220702-96fc6a7a2-xpmod.7z Win64 http://o.rthost.win/basilisk/basilisk55-win64-git-20220702-96fc6a7a2-xpmod.7z repo: https://github.com/roytam1/basilisk55 Repo changes: - import from UXP: Unconditionally switch on the INTL API on all platforms. (bbcc0d91) (d3c51965f) - import from UXP: Adjust tests for android-enabled Intl. (8726b2dc) (6036a1304) - import from UXP: Issue #324 - Remove the option to build without INTL/ICU (b19e3c34) (f42bfce68) - ported from UXP: ssue #325 Part 1: Remove the legacy non-IDNA2008 code path from nsIDNService. (1af1f5b3) (826a4e29e) - import from UXP: Issue #325 Part 2: Build ICUUtils unconditionally. (6008e3c1) (f4730eeea) - ported from UXP: Issue #325 Part 3: Remove support for using legacy Gecko normalization in gfxHarfBuzzShaper. (cbc1d586) (dbec8b9ec) - import from UXP: Issue #325 Part 4: Remove obsolete and archaic Unicode normalization implementation. (4d5e597e) (58974071f) - ported from UXP: Issue #325 Part 5: Remove non-Intl legacy code paths from js. (d1c16b13) (3cf2ae8cc) - import from UXP: Issue #325 Part 6: Remove non-Intl legacy code paths from line-breaker code. (3f6fb7bb) (c2ea171db) - ported from UXP: Issue #325 Part 7: Remove non-Intl legacy code paths from IndexedDB. (d4d0fbf3) (78909c9ed) - import from UXP: Issue #325 Part 8: Remove non-Intl legacy code paths from nsChromeRegistry. (29c4fdcc) (620fd957f) - ported from UXP: Issue #325 Part 9: Remove non-Intl legacy code paths from nsNumberControlFrame. (f2d90ee4) (1e45e634e) - ported from UXP: Issue #325 Part 10: Remove non-Intl conditionals from installer files. (b8114dcb) (7474422f7) - ported from UXP: Issue #325 Part 11: Fix up build files. (6b2478e2) (4027a0b3d) - ported from UXP: Issue #325 Part 12: Manually edit Unicode property tables. (f3ce7263) (233cf4826) - ported from UXP: Issue #325 Part 13: Remove Mozilla implementation of the bidi engine completely and use ICU. (04679df9) (69d97689b) - ported from UXP: Issue #325 Part 14: Remove EXPOSE_INTL_API conditionals. (8e9e42c7) (4a65b1830) - import from UXP: Issue #325 Part 15: Remove ENABLE_INTL_API and EXPOSE_INTL_API flags. (127b2c99) (7be85633a) - import from UXP: Clang needs a trailing new line in intl/hyphenation/glue/hnjstdio.cpp (276510c4) (8f8cd0c6e) - import from UXP: Issue #326 - Part 1b: Remove outdated ENABLE_INTL_API code. (291907ef) (2e9df1771) - partly ported from UXP: Issue #326 - Part 1c: Generated files for Unicode 9.0. (66d4f38c) (2073206a2) - partly ported from UXP: Issue #326 - Part 2: Update UTR-50 data to version 16 (cd64bfb1) (e1fa6197f) - import from UXP: Issue #326 - Part 3: Explicitly make the Script enum a 16-bit type (7c2d9482) (7e2beca25) - ported from UXP: Issue #326 - Part 4: Update Unicode data to release 10.0 (54489c30) (67643ae29) - ported from UXP: Issue #326 - Part 5: Simplify the genUnicodePropertyData.pl tool to generate only the data we need to supplement ICU properties (b8e7234b) (b64932ff5) - ported from UXP: Issue #326 - Part 6: Regenerate Unicode data tables with the stripped-down tool (8ad8bfb4) (24edb8053) - addendum of rev 67643ae2 (41e5f4a64) - import from UXP: - Issue #1933 - Part 1: Update build system for libjpeg-turbo. (75e223e3) - Issue #1933 - Part 2: Update libjpeg-turbo source. (fc2133f4) - Issue #1933 - Follow-up: Fix building on ARM. (0eece8e5) - Issue #1933 - Follow-up: Remove cmakedefine directives from neon-compat.h. (b29aa5d5) (f0f3447db) - import from UXP: Issue #1935 - Update libogg to 1.3.5 (9f598a8a) (4d9174310) - import from UXP: - Issue #1939 - Part 1: Update build system for libwebp. (56d49fd5) - Issue #1939 - Part 2: Update libwebp source. (8038505d) (2064b08be) - import from UXP: Issue #1941 - Update libvorbis to 1.3.7. (191a010f) (bf53b0653) - import from UXP: - Issue #1944 - Fix volume handling in sndio backend. (ef4db6f2) - Issue #1944 - Follow-up: Make it clear that volume is a float. (5b40dbab) (c5bc6b89f) - import from UXP: - Issue #1937 - Part 1: Update build system for libaom. (d09a5eec) - Issue #1937 - Part 2: Update libaom source. (ecb7ec73) - Issue #1937 - Follow-up: Fix sources.mozbuild not having exports (49696a78) - Issue #1937 - Follow-up: Add missing sources and includes in sources.mozbuild (8c7e7636) - Issue #1937 - Follow-up: Add missing sources, and remove unneeded ones in sources.mozbuild (463a5027) - Issue #1937 - Follow-up: Exclude aom_encoder.c/h from our build (932e9d8f) - Issue #1937 - Follow-up: Remove some unnecessary includes and sources from sources.mozbuild (6f97a501) (127f7cd69) - ported from Waterfox-Classic: Work around missing JSOP_GOTO functionality for optional chaining. (b5a3f1bd) (96fc6a7a2)

Hi again.. You could also take a look at this thread by our own @Sampei.Nihira ... I do hope you are doing well as I've not seen you around as much lately. On my @NotHereToPlayGames v11 just now... https://www.ghacks.net/2021/04/26/evaluate-your-content-blocker-with-ad-block-tester/ Give it a try

Hi there.. Yeah, sad to say, V11 is starting to show its age, hate to say it. I'm still using it, but, regrettably I've gone back to Serpent as my default. You will notice that V13 is still working very well, but is like a hoover vacuum when it comes to resources. Lol ... :) Have to give it top priority and cut back anything in the background which is a pain in the keister to have to do. Mini Browser after the last update doesn't work for me, but very grateful to all @Humming Owl and all involved and sad these browsers are only an afterthought given the hard work that went into it ;( Again, Still going to stay with V11 (I use ArcticFoxie build) but expect things to not work right as time goes on ... and there are other extensions besides Adguard that people use without issue here you could try. Good luck!

Howdy all .... :)

I'm just surprised that Firefox 52.9 ESR's built-in certificates still work when it dates from 2018, but I'm not complaining!

Thanks! If it was up to me, in https://github.com/RamonUnch/palefill/commit/a82544e I would've have also changed "Platform51Up" (two occurrences inside "main.js") to "Platform485Up", because (and call me pedantic ) : 1. UXP by Roytam is currently at v4.8.5, 2. 4.8.5 can't be >= 5.1.0 (i.e. 51Up ) Better checks were added yesterday I see. Current SeaMonkey's (not UXP) platform version is 60 something, so version check also wouldn't give the desired result in that browser. You can make it more complicated (function supersededFixes) and a bit more correct (no assumptions). No idea, I learn as I go.

They're not needed with @roytam1's Mozilla-based browsers, which have their own up-to-date TLS support built in. So the topic doesn't come up often in this thread. But both IE 8 and Chromium-based browsers use the TLS support built into Windows. The only use case for IE 8 these days is Windows/Microsoft Update and the Update Catalog, but the modern Internet often needs a Chromium-based browser on WinXP (to support the increasingly "Googlized" JavaScript language), yet also cryptographic functions that WinXP doesn't support. Although ProxHTTPSProxy and its brethren were originally designed to use Proxomitron with secure sites, they have the useful side effect of supporting cryptography beyond what WinXP has built in, so you can browse sites that require newer cryptographic functions with Chromium-based browsers. 360EE may be a special case; since it was designed to bring newer Chromium versions to the WinXP platform, it may have more up-to-date TLS support built in. I don't know. That's because you don't know its true purpose. It's been sold as a way to prevent eavesdroppers (including your ISP) from learning what sites you visit, and it does do that; but I believe its true purpose is a bit more sinister. I'm sure lots of folks here have used their "hosts" file to deliberately block telemetry, malware, or advertising servers. It's a simple but often quite effective tactic. There's even a network-wide version of this trick, called a "Pi-Hole," that's a deliberately defective DNS server to block those servers across your entire home network. These tricks have become a concern for the Googles of the world, whose business models rely on collecting our data and serving ads; so much so that some of them are building their own DNS clients into their adware to bypass any such misdirection. The built-in server always goes to the IP address of a well-known DNS server, thus bypassing any hosts file entries, Pi-Holes, or what have you. But that trick can be blocked too - at the router! The router can just be programmed to route requests to, say, 8.8.8.8, over to your local Pi-Hole instead. So the ad servers still get redirected and blocked. That's where Secure DNS comes in. If you redirect Secure DNS requests, the client will know about it, because the certificate will be incorrect. At that point, the client just says, "if I can't connect to my real DNS server, I'm not going to run at all! You either accept my telemetry and ads, or you get nothing! Good day, sir!"

A definitive "CloudFlare Browser Check" is trying to log-in to GitLab: https://gitlab.com/users/sign_in BTW, this happens when site admins - who are CF clients - have enabled a feature called "Browser Integrity Check" (BIC) ... CF have recently abolished the CAPTCHA challenges as part of BIC, replacing them with automated checking (JS) scripts, requiring the browser to pass mathematical "challenges"... It was those scripts that were being "racist" towards non-mainstream browsers and thus those browsers (including the UXP ones) were outright denied access to sites CF intend to "protect" from "unwelcome" traffic... That CF issue (please search this thread for more details) finally made it to prominent web sites/forums, not to mention the "loud voices" of some Pale Moon users (to which we owe big thanks ) on CF's Community Forums, so it had to be acknowledged and acted upon by real CF devs... It was "them" who fixed it for us (but some more "obscure" web browsers, like the Qt-based Otter Browser, are reported to still suffer from this "racism" ) ... OT: @Dave-H : Do you, hopefully, know what happened to https://thedndsanctuary.eu/ that used to post invaluable info about the Otter Browser ?

I'm not referring to Secure DNS (I do not use it and see it as "hype and propaganda"). I'm referring to Cloudflare "fingerprint" tests that some web sites will not let you visit until you demonstrate you are human by clicking on mountains, boats, traffic lights, bikes, et cetera. If you can visit the below website WITHOUT being asked to prove that you are human, then you are PASSING the Cloudflare browser checks. https://raybuck.com/firebird-vs-trans-am-history-trivia/

I was the first who posted about how to hex edit the DLL one way to extend the date, at least on MSFN. Didn't know about that project though...just hex-edited my DLL and forgot about it. FlashPatch! doesn't run on XP, but most of it can be made to run with small modifications. FlashPatch_NetFx4.zip FlashPatch_NetFx4_src.zip I threw out some unreferenced namepaces from .csproj file, commented out update checking function and fixed another error related to retrieving HRESULT code from Exception object occurring when accessing it directly on older .NET version, then it compiles on XP using .NET Framework 4's bundled tools: cd <path\to\FlashPatch\folder> C:\WINDOWS\Microsoft.NET\Framework\v4.0.30319\MSBuild.exe FlashPatch.csproj /p:Configuration=Release

because official builds don't have this enabled, newmoon28 front-end code with accessibility-enabled are totally untested

because newmoon is built with "--disable-accessibility" switch.

@VistaLover Great advices already by Humming Owl and RainyShadow. You can try few things yourself, to check what could be the problem by a process of elimination. If you have 2 RAM sticks, take out 1 and try starting your laptop just with 1 RAM stick, if it still gives black screen try only with the other RAM stick. Here is a video how to change RAM sticks - How To Add Ram Toshiba Satellite Laptop Increase Memory: https://www.youtube.com/watch?v=6vbxHF9w3ZE I only advise not to touch the RAM stick on the "golden" contacts, and hold it on the white labels instead. The advice to try with external monitor to check if the screen is the problem is also good.

Personally, mine are all at the default, except I do set dom.serviceworkers.enabled to true. But I keep service workers on a tight leash with this uBO filter: *$csp=worker-src 'none',domain=~mediafire.com|~html5test.com|~routerlogin.net|~mega.nz|~boonchapman.com|~archive.org That filter keeps them blocked except at the listed sites. Some of the above sites (including my home network router!) require them to work at all; others have workarounds if service workers are disabled. Generally, if I try a new site and it doesn't work, I try adding the domain to the filter above first. If that fixes it, I leave it on the filter, otherwise I remove it and resort to 360EE, figuring it's just another "Googlized" site.