Leaderboard

New build of Serpent/UXP for XP! Test binary: Win32 https://o.rthost.win/basilisk/basilisk52-g4.8.win32-git-20250712-3219d2d-uxp-b9ebe5b259-xpmod.7z Win64 https://o.rthost.win/basilisk/basilisk52-g4.8.win64-git-20250712-3219d2d-uxp-b9ebe5b259-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-20250712-3219d2d-uxp-b9ebe5b259-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-20250712-d849524bd-uxp-b9ebe5b259-xpmod.7z Win32 IA32 https://o.rthost.win/palemoon/palemoon-28.10.7a1.win32-git-20250712-d849524bd-uxp-b9ebe5b259-xpmod-ia32.7z Win32 SSE https://o.rthost.win/palemoon/palemoon-28.10.7a1.win32-git-20250712-d849524bd-uxp-b9ebe5b259-xpmod-sse.7z Win64 https://o.rthost.win/palemoon/palemoon-28.10.7a1.win64-git-20250712-d849524bd-uxp-b9ebe5b259-xpmod.7z Win7+ x64 AVX2 https://o.rthost.win/palemoon/palemoon-28.10.7a1.win64-git-20250712-d849524bd-uxp-b9ebe5b259-w7plus-avx2.7z Official UXP changes picked since my last build: - Issue #2106 - Part 1: Un-prefix -moz-user-select (cc55a380f6) - Issue #2106 - Part 2: Align value names (17b594b705) - No issue - Fix mixing of tabs with space-indented code. (552cb8dbcc) - Issue #2045 - Part 1: Revert "Temporarily force hidden elements to be actually hidden." (dd2cf17d30) - Issue #2045 - Part 2: Add handling and storage for the revert unit and value (7f3f90eed4) - Issue #2045 - Part 3: Implement cascade origin tracking to CSS parser (b0f0972314) - Issue #2045 - Part 4: Parse "revert" in property values wherever "unset" is allowed (9105c58a30) - Issue #2045 - Part 5: Serialize shorthands using "revert" like those containing "unset" (801d4a2db8) - Issue #2045 - Part 6: Treat "revert" values as the same as "unset" when encountered in the rule node (c4b6135c99) - Issue #2045 - Part 7: Override revert values during presentation hint cascade (166e98d2b9) - Issue #2045 - Part 8: Remap revert keyword values to a higher cascade level (a47f44e93d) - Issue #2045 - Part 9: Include the revert keyword in the list of accepted values for CSS properties returned by inDOMUtils (5346e55655) - Issue #2045 - Part 10: Regenerate devtools CSS database and include the revert keyword in related devtools code (f0b8d1df2c) - Issue #2106 - Part 3: Add 'contain' as user-select value, retain 'element' (e6b48fcc95) - [devtools] Further improve special character escaping in "copy as curl". (2d9cb22a28) - No Issue - Add detection for medium in border shorthand (9f7430f8b9) - Issue #2124 - Adjust overflow parser to handle two values (f4ffb1ec16) - Issue #2662 - Implement axis-shorthand parsing (7c52fd934f) - Issue #2124/2662: Optimize overflow shorthand parsing and serialization (7626c99ceb) - Issue #2124/2662: Cleaning of code (dae72b452c) - Issue #2106 - Follow-up: Additional Un-prefixing (1a5b3dcae6) - Issue #2106 - Follow-up: Un-prefix DOM Attribute MozUserSelect (abb891ff26) - Issue #2106 - Follow-up: Additional contain Keyword Entries (f1815317c3) - Issue #2106 - Clean-up: Remove Defunct -moz-user-select CSS Directives (8f46cd0d63) - Issue #2106 - Clean-up: Un-prefix -moz-user-select in Comments (b11affbdf3) - Issue #2780: Add back the mismatch overflow handling in nsRuleNode.cpp (c3590da576) - Issue #2757: Create a new basicShape of type inset then set inset coords to zero. (67421b3048) - Issue #2757 - Follow-up: Add clip-path test (manual QA) (3f67905afc) 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: - gfx: relax DrawTargetCairo::IsValid() check, fixes crash when loading spectrumsurveys.com (10b96192dd) - layout: plug back alias of -moz-user-select so it won't break pages/extensions relying on this (4c8df426a8) 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.

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-20250712-6129895b4-xpmod.7z Win64 https://o.rthost.win/basilisk/basilisk55-win64-git-20250712-6129895b4-xpmod.7z repo: https://github.com/roytam1/basilisk55 Repo changes: - ported from UXP: Issue #2106 - Part 1: Un-prefix -moz-user-select (cc55a380) (cfadbb5d6) - ported from UXP: Issue #2106 - Part 2: Align value names (17b594b7) (3a0677ec7) - import from UXP: No issue - Fix mixing of tabs with space-indented code. (552cb8db) (4634fe9d1) - import from UXP: Issue #2045 - Part 1: Revert "Temporarily force hidden elements to be actually hidden." (dd2cf17d) (29e601bb8) - import from UXP: Issue #2045 - Part 2: Add handling and storage for the revert unit and value (7f3f90ee) (f49dc1068) - ported from UXP: Issue #2045 - Part 3: Implement cascade origin tracking to CSS parser (b0f09723) (13380336f) - import from UXP: - Issue #2045 - Part 4: Parse "revert" in property values wherever "unset" is allowed (9105c58a) - Issue #2045 - Part 5: Serialize shorthands using "revert" like those containing "unset" (801d4a2d) (f780f6a0c) - ported from UXP: Issue #2045 - Part 6: Treat "revert" values as the same as "unset" when encountered in the rule node (c4b6135c) (0ddba686d) - ported from UXP: Issue #2045 - Part 7: Override revert values during presentation hint cascade (166e98d2) (33497a7bb) - import from UXP: Issue #2045 - Part 8: Remap revert keyword values to a higher cascade level (a47f44e9) (7e8276dd1) - import from UXP: Issue #2045 - Part 9: Include the revert keyword in the list of accepted values for CSS properties returned by inDOMUtils (5346e556) (5b3195dad) - ported from UXP: Issue #2045 - Part 10: Regenerate devtools CSS database and include the revert keyword in related devtools code (f0b8d1df) (e92c563a4) - import from UXP: Issue #2106 - Part 3: Add 'contain' as user-select value, retain 'element' (e6b48fcc) (f073823cd) - ported from UXP: [devtools] Further improve special character escaping in "copy as curl". (2d9cb22a) (28bf4bcf2) - ported from UXP: No Issue - Add detection for medium in border shorthand (9f7430f8) (4f0690a20) - import from UXP: Issue #2124 - Adjust overflow parser to handle two values (f4ffb1ec) (ae483ab3b) - ported from UXP: Issue #2662 - Implement axis-shorthand parsing (7c52fd93) (f7844356c) - ported from UXP: Issue #2124/2662: Optimize overflow shorthand parsing and serialization (7626c99c) (55a3af5f7) - ported from UXP: Issue #2124/2662: Cleaning of code (dae72b45) (9c80beb8f) - ported from UXP: Issue #2106 - Follow-up: Additional Un-prefixing (1a5b3dca) (82ff6f599) - import from UXP: Issue #2106 - Follow-up: Un-prefix DOM Attribute MozUserSelect (abb891ff) (2b505c1fd) - import from UXP: Issue #2106 - Follow-up: Additional contain Keyword Entries (f1815317) (db2c8fdb5) - ported from UXP: Issue #2106 - Clean-up: Remove Defunct -moz-user-select CSS Directives (8f46cd0d) (37991f84a) - import from UXP: Issue #2106 - Clean-up: Un-prefix -moz-user-select in Comments (b11affbd) (477ab51c4) - import from UXP: Issue #2780: Add back the mismatch overflow handling in nsRuleNode.cpp (c3590da5) (0ee810368) - import from UXP: Issue #2757: Create a new basicShape of type inset then set inset coords to zero. (67421b30) (0ea914daf) - import from UXP: Issue #2757 - Follow-up: Add clip-path test (manual QA) (3f67905a) (1b8fbc344) - import from `custom` branch of UXP: gfx: relax DrawTargetCairo::IsValid() check, fixes crash when loading spectrumsurveys.com (10b96192) (6129895b4)

New build of BOC/UXP for XP! Test binary: MailNews Win32 https://o.rthost.win/boc-uxp/mailnews.win32-20250712-7bda12e7-uxp-b9ebe5b259-xpmod.7z BNavigator Win32 https://o.rthost.win/boc-uxp/bnavigator.win32-20250712-7bda12e7-uxp-b9ebe5b259-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-20250712-id-656ea98-uxp-b9ebe5b259-xpmod.7z IceApe-UXP(suite) https://o.rthost.win/hbl-uxp/iceape.win32-20250712-id-656ea98-ia-c642e3c-uxp-b9ebe5b259-xpmod.7z source repo (excluding UXP): https://github.com/roytam1/icedove-uxp/tree/winbuild https://github.com/roytam1/iceape-uxp/tree/winbuild

Strange, but it appears that the issue has completely resolved itself.

So I updated my Vista SP2 x64 to 2016, still no joy. Chromium for Windows 7 by e3kskoy7wqk starts with the same method! Ideas? I don't understand what else CatsXP wants, aren't those both made for win 7?

What for? It's obsolete, no matter how good it was 2 years ago. D.Draker no longer recommends this browser due to the age. https://msfn.org/board/topic/186346-i-moved-to-centbrowser-im-not-happy-about-it/page/5/#findComment-1275874

At least the acronym (BSoD) will still be valid, since both black and blue begin with the letter 'b' c

I think we have to take Shane's word for it that the patch has been applied to Supermium 132. As I said earlier, it's an ESR version, which surely should be capable of having the patch applied to it, as it should be fully supported until the next ESR version is released. I'm not sure how we can test whether the patch has been applied successfully or not.

Then it's a good idea to use the patched ungoogled for Server 2008 R2. No one knows and no one can guarantee how good and when the old 132 Supermium will (ever?) be patched for that serious vulnerability. https://github.com/e3kskoy7wqk/Chromium-for-windows-7/releases/tag/ungoogled-chromium_138.0.7204.96 Edit/ They say it's been patched in R5. But in the article they say the patch is for 138+! Contradictory. https://github.com/win32ss/supermium/releases/tag/v132-r5

That was clear, but from what they tell, looks like the patch is intended to be applied only to 138+. Who would write a patch for the old 132, while we are at 140+ already?

New release "74.1.0 New features added, some sites will be fixed New version number is 74 because addons like custumbuttons check it and breaks expecting xul things from 68 which has been removed." https://github.com/Feodor2/Mypal68/releases/tag/74.1.0 EDIT: "UPDATE 14.07.2025 Fixed bug about privace settings not shown" BTW, this release feels slower than the previous one...

I took a closer look at updated file "update.py": https://github.com/nicolaasjan/youtube-dl/blob/embedthumbnail/youtube_dl/update.py which you originally copied from: https://github.com/ytdl-org/ytdl-nightly/blob/master/youtube_dl/update.py The update process correctly "calculates" the hashsum of "current" version, Latest version: 2025.07.12.1, Current version: 2025.07.12 Current Build Hash 58815fc0de70a06e76a9e9ca0337dfcdda59b1db0ffed12d150df626d8cd7735 which is indeed identical to the value displayed at https://github.com/nicolaasjan/youtube-dl/releases/tag/2025.07.12 Which part of the code inside "update.py" is responsible for that? I understand that your tags/releases don't have a SHA2-256SUMSfile as asset... Updating to version 2025.07.12.1 ... WARNING: no hash information found for the release According to https://github.com/nicolaasjan/youtube-dl/releases/tag/2025.07.12.1 the missing hashsum value for youtube-dl.exe should be: 21534c1543d62f4543efff017da1c8dd18a47e64995fd7e8c84215a433752db5 Why isn't "update.py" able to "calculate" it and, more importantly, how can it be fixed? GitHub adding a "sha256:*" column under assets (not as separate asset) is a relatively new feature, AFAIAA... In file update.py, I can identify two hashsum calculating blocks: https://github.com/nicolaasjan/youtube-dl/blob/da27e0bb378940575d4ac1a5d2a9c9899f7f94ec/youtube_dl/update.py#L84-L91 Is this one for "current" (non-updated) binary? Then, there is: https://github.com/nicolaasjan/youtube-dl/blob/da27e0bb378940575d4ac1a5d2a9c9899f7f94ec/youtube_dl/update.py#L130-L138 which obviously pertains to the "updated" binary; I can see mentions there of files "SHA2-256SUMS" that your fork lacks; lastly, the WARNING is issued as a result of lines: https://github.com/nicolaasjan/youtube-dl/blob/da27e0bb378940575d4ac1a5d2a9c9899f7f94ec/youtube_dl/update.py#L172-L174 Someone knowledgeable in Python needs to review the "update.py" file and come up with a "fix"; perhaps if you kindly ask dirkf in GitHub, he could oblige ... C'mon, you know me better than that ... Sorry for being a PITA, best wishes !

I don't know anything about Python either, but I just uploaded the new `update.py` (with only one line changed) into the GitHub web editor and committed.

... Huh, I see ... This is very puzzling, indeed ; in fact, the "yt-dl.org" domain now auto-redirects to yt-dlp GitHub URLs, e.g. https://yt-dl.org => https://github.com/yt-dlp/yt-dlp , which, of course, is a fork of the original youtube-dl project; I think dirkf doesn't have immediate access to the "yt-dl.org" server (wasn't that one blocked in Germany at some point?), so the answer about who arranged the autoredirection to yt-dlp might be possibly found inside the yt-dlp repo itself (too hot here currently for me to check, sorry ) ... I know; however, I have a small list of test commands I issue with fresh releases of both youtube-dl (nightly branch) and yt-dlp (your "Vista" compatible build) and that same list was used to test your 2025.07.11 compile; that was how I noticed the change in behaviour for " -vU" ... As I'm not proficient in Python (quite the opposite, in fact ), that was what I was about to suggest to you ; glad you got it sorted already ... The same with most "yt-dl.org" links contained inside: https://ytdl-org.github.io/youtube-dl/download.html I know ; I had already modified locally the latest "official" Nightly release (2025.05.05) according to your posted diff on GH; let's hope a py3.4 solution becomes available if evil Google start blocking Chrome > 97 UAs... Best regards !

We need a "benign exploit" page (a page that triggers the bug but doesn't do anything harmful) to test for this vulnerability. We had one for the WebP vulnerability.

They have. There's an "ancient" one called xoblite. It's kind of like using fluxbox on Windows instead of Linux. Check out the screenshots and you'll see what I mean. xoblite™ / Blackbox for Windows

@VistaLover That's because of line 37 in `./youtube_dl/update.py`. UPDATE_URL = 'https://yt-dl.org/update/' For some reason it redirects to: https://github.com/yt-dlp/yt-dlp/update/ ---> 404. In version 2025.06.26 (and previous versions) I had it set to: UPDATE_URL = 'https://ytdl-org.github.io/youtube-dl/update/' (also 404, by the way) My version is not supposed to be updated with `-U`. Do you perhaps have any idea how to change `update.py` for my fork to actually make it work with `-U`? [Edit] I think I managed to fix it. Took `update.py` from youtube-dl Nightly as an example. youtube-dl -vU [debug] System config: [] [debug] User config: ['--console-title', '--rm-cache-dir', '-i', '-o', '/dev/shm/test-ytd/%(title)s.%(ext)s', '-f', 'bestvideo[height<=1080][ext=mp4][vcodec^=avc]+bestaudio[ext=m4a]/best[ext=mp4]/best', '--no-mtime', '--embed-thumbnail', '--force-ipv4'] [debug] Custom config: [] [debug] Command-line args: ['-vU'] [debug] Encodings: locale UTF-8, fs utf-8, out utf-8, pref UTF-8 [debug] youtube-dl version 2025.07.12 [debug] Lazy loading extractors enabled [debug] Single file build [debug] Python 3.10.12 (CPython x86_64 64bit) - Linux-5.15.0-143-generic-x86_64-with-glibc2.35 - OpenSSL 3.0.2 15 Mar 2022 - glibc 2.35 [debug] exe versions: ffmpeg N-120171-g05094c1749-20250705, ffprobe N-120171-g05094c1749-20250705, rtmpdump 2.4 [debug] Proxy map: {} Latest version: 2025.07.12, Current version: 2025.07.12 youtube-dl is up to date (2025.07.12) Removing cache dir /home/nico/.cache/youtube-dl .. I also don't understand why @dirkf still hasn't updated the Installation section in the Readme. It's a complete mess. BTW, I've made a significant change to `./youtube_dl/utils.py`, as I suggested here. Youtube-dl actually works now.

There's something wrong with the latest (v2025.07.11) youtube-dl.exe build downloaded from GitHub: https://github.com/nicolaasjan/youtube-dl/releases/tag/2025.07.11 https://github.com/nicolaasjan/youtube-dl/releases/download/2025.07.11/youtube-dl.exe youtube-dl -vU => [debug] System config: [] [debug] User config: [] [debug] Custom config: [] [debug] Command-line args: ['-vU'] [debug] Encodings: locale cp1253, fs mbcs, out cp737, pref cp1253 [debug] youtube-dl version 2025.07.11 [debug] Lazy loading extractors enabled [debug] Single file build [debug] Python 3.4.4 (CPython x86 32bit) - Windows-Vista-6.0.6003-SP2 - OpenSSL 1.0.2d 9 Jul 2015 [debug] exe versions: none [debug] Proxy map: {} Traceback (most recent call last): File "C:\Users\nico\Desktop\youtube-dl_source\youtube_dl\update.py", line 48, in update_self File "c:\Program Files (x86)\Python3.4.4\lib\urllib\request.py", line 470, in open File "c:\Program Files (x86)\Python3.4.4\lib\urllib\request.py", line 580, in http_response File "c:\Program Files (x86)\Python3.4.4\lib\urllib\request.py", line 502, in error File "c:\Program Files (x86)\Python3.4.4\lib\urllib\request.py", line 442, in _call_chain File "c:\Program Files (x86)\Python3.4.4\lib\urllib\request.py", line 685, in http_error_302 File "c:\Program Files (x86)\Python3.4.4\lib\urllib\request.py", line 470, in open File "c:\Program Files (x86)\Python3.4.4\lib\urllib\request.py", line 580, in http_response File "c:\Program Files (x86)\Python3.4.4\lib\urllib\request.py", line 508, in error File "c:\Program Files (x86)\Python3.4.4\lib\urllib\request.py", line 442, in _call_chain File "c:\Program Files (x86)\Python3.4.4\lib\urllib\request.py", line 588, in http_error_default urllib.error.HTTPError: HTTP Error 404: Not Found ERROR: can't find the current version. Please try again later. The previous compile, of version 2025.06.26: https://github.com/nicolaasjan/youtube-dl/releases/download/2025.06.26/youtube-dl.exe , behaves as expected: youtube-dl -vU => [debug] System config: [] [debug] User config: [] [debug] Custom config: [] [debug] Command-line args: ['-vU'] [debug] Encodings: locale cp1253, fs mbcs, out cp737, pref cp1253 [debug] youtube-dl version 2025.06.26 [debug] Lazy loading extractors enabled [debug] Single file build [debug] Python 3.4.4 (CPython x86 32bit) - Windows-Vista-6.0.6003-SP2 - OpenSSL 1.0.2d 9 Jul 2015 [debug] exe versions: none [debug] Proxy map: {} youtube-dl is up to date (2025.06.26) Many thanks for your ongoing efforts towards maintaining support for "our" older OSes ...

Check out here. While it is still up, anyway :)

they did this because they want jemalloc to be integrated into C runtime, which is un-recommended by MS later.

Normally the same as in the PCIe HD graphics card, e.g. AMD HD7450: Audio output from Intel CPU is over HDMI, DP or DVI (DVI only if in bios is function Audio over DVI and you need DVI > DP or DVI > HDMI cable:

The unofficial guide "How to get MyPal 68 working on Windows XP SP1!" is now available. This guide is made by me. This would be useful for Althon XP/Pentium III machines running Windows XP SP1, because Supermium does NOT support processors without SSE2 yet. https://sites.google.com/view/clara-incorporated/modernization/windows-xp-sp1/firefox-based-browsers/mypal-68 @feodor2and @roytam1

Okay. Your suggestion just worked for me as well as FindNextFileA works too when I got mypal68 to work on Windows XP SP1.

Version 138 is required for the fix; the bug goes back earlier though: Good catch. Google is being tight-lipped on exactly when this vulnerability crept in. I doubt it goes all the way back to 2008, though. Today's V8 looks nothing like the original. I believe (and should have said) versions prior to the V8 optimizer are not vulnerable. I suspect 360EE (and Kafan MiniBrowser) aren't vulnerable because the option to turn off the optimizer isn't there (presumably because there's nothing to turn off), but I can't be sure with the limited info we have.

The alternative forum is now available. It is located here: https://tripredacus.net/forum/index.php This forum is actively managed by myself and has public status sections for the three websites that I am providing temporary forums for. The fallback boards are not visible to the public and are not segregated, meaning if you can see a board, you can post in it if you want. The sections will always be open, even if the hosted site has an Up status such as MSFN currently does. This forum is not intended to, nor can it replace MSFN. It is also not meant to be a replacement for other unmanaged or unofficial meatup destinations such as any Discord channels, Steam or Facebook groups. It simple is a place to go in case there is a problem or you want to get info about whatever might be happening. This is not an indication that there is any longevity issue with MSFN. The forum rules are not MSFN's rules, with the exception that discussion about circumventing MSFN rules 1 are not allowed. UK/EU members make sure you read the end of the Registration Agreement. Whether you decide to register on it or not is up to you. This post is just to make you aware that it exists. You choose your own level of involvement. If you decide to register, you should edit your profile to put your MSFN name as it explains in the appropriate profile field. Doing so will cause a MSFN icon appear on your info card if you post in a thread.

You can find the download link for the CAupdater in my main article ProxHTTPSProxy and HTTPSProxy in Windows XP for future use in the section 11.2.4. Downloads related to Root Certificate Updates.

I strongly suggest you all simply ignore those dimwits. let their businesses go bankrupt. Enough of this nonsense. Recently, I was willing to spend several grands on a bag, yet I have problems with their site. I'll think twice now. And looks like they just lost a customer. In details. https://msfn.org/board/topic/186728-chanel-french-bags-website-err_http2_protocol_error-from-my-ip-blocked-from-vpn-too/

He lied to you, the owner simply put the slider to the "maximum protection". Again, Cloudflare could care less what the owner chooses.

The owner of the website determines what level of "protection" is used, not Cloudflare. Cloudflare simply gives the tools to the owner.

Ok. I was able to improve a bit my custom button for calling up the "Manage Cookies and Site Data" window. Both, the about:preferences#privacy and three seconds later the desired dialogue are now loaded in the same chrome window which avoids an additional loading of a tab. Nevertheless, I hope that there is a better solution yet. As custom buttons are actually the topic of this thread, I have decided to post about this stuff here again. My project of creating a custom button to directly call up the "Manage Cookies and Site Data" dialogue in Mypal 68 seems to have come to a temporary end. It works perfectly. I have solved the issues encountered in my own way and I am currently in testing mode. Here is a short preview:

Wow! The interest in Comodo security programmes seems to be huge.

@genieautravail BTW, I tested the SUPERAntiSpyware Free Edition last night. The installation worked without any problems. Also the update of the programme to version 10.0.1266 and the update of the signatures database. Additionally, I carried out a function check. Everything ran as it should. TBH, I have no idea what's going on in your Windows XP system. But one thing is clear. Your hasty conclusions are simply wrong. And this is unfortunately not the first time.

SUPERAntiSpyware Free Edition works absolutely fine here. No issues. No DLL problems. I can access all features. I think your system is the causer. You can alternatively try the installer version 10.0.1250 as this version was the one before incompatibilities with the programme appeared the first time. BTW, I have been using SUPERAntiSpyware since 2007 without any serious issues. So, please check your system first before posting issues one can't confirm!

I will check my registry entries when I am back at my desktop computer. Thanks for the heads up!

TBH, I don't think that any website operator is still interested in compatibility problems of an unsupported and rather unknown browser like Serpent on an operating system like Windows XP that has not been supported for a long time. So don't expect an answer or support!

And now, disable Circular Kernel Context Logger and Audio logger. Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\WMI\Autologger] "Status"=dword:00000000 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\WMI\Autologger\Audio] "Start"=dword:00000000 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\WMI\Autologger\Circular Kernel Context Logger] "Start"=dword:00000000

WMItracing.log OFF (Vista) Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WBEM\Tracing\WMI] "SessionEnabled"=dword:00000000 "Level"=dword:00000000

Spar

Spring

Reading. (town in Berkshire)

Knickerbocker Glory

FYI, my toggle buttons can easily be modified to switch other Boolean preferences. I explained it in the corresponding posts. TBH, there is nothing to be changed in the button's code. I think you rather mean changing the selected preferences which you want to control. This is to be done in the main user interface window of Pref Toggler via the button "Edit List". That's good to hear. Thanks for your feedback!

Did you also try different user agents on this website?

@dmiranda, @Ascii2 Do you still use custom buttons at all? This was actually my initial question. What do you think about custom buttons in general? And have you ever tried the Pref Toggler custom button or my modded version I recently presented here?

You will only know whether these custom buttons are compatible with @roytam1's browsers or not when trying to install them and checking their functionality. Most of these custom buttons are very old. Unfortunately, many of them don't work in Firefox 52 based browsers any longer. They would have to be fixed if possible at all. I personally use only those which are fully functional. My self-created custom buttons have been developed for UXP based browsers and are compatible with @roytam1's browsers and most probably with Pale Moon, too. I even managed some of them to also work in Mypal 68. Have a look here: https://msfn.org/board/topic/183657-mypal-68-in-windows-xp-custom-buttons-and-extensions/?do=findComment&comment=1229639 The more universal the JavaScript coding of these custom buttons, the more compatible. And you have to target only functions which are supported in all browsers. That's why only a few of the old custom buttons can be used in Mypal 68.

gpt.ini

aspnet_perf.ini

Probably they implemented some anti-hack feature, in addition to limiting youtube's videos frequently posted by some members?

Thank you for the detailed explanation!

I fail to understand why do they all patch only the standard chrome, not ungoogled.