NotHereToPlayGames

My guess is that Google is "experimenting" and it hasn't actually "landed" yet. I don't think that they are even aware (yet) that their "experiment" is even making H#LL out of using Google on even something as modern as Chrome v136. Did not go beyond that, I only know that my v136 is hit with a CAPTCHA each and every d#mn browsing session !!! I can't believe that this is what they "intended" to do to those of us that run "ungoogled" or session-only or cacheless browsers even on something as 'new' as v136. I have witnessed these every-d#mn-session CAPTCHAs in the past on Google and it takes them a WEEK or so to realize it and reverse the experiment, "oops, that wasn't what I was expecting".

In Task Manager, are there any processes running over 80% or so during your slow connectivity?

This one in particular wasn't even "disguised", the .js file has "browser-detect" right in its name. Watch that uBlock LOGGER and you will learn to spot these before you know it. The LOGGER even has a little arrow to click that opens the .js file in a new tab so that you can read the javascript. Reading these will not turn you into a "coder", but you will learn things to watch for. Such as the browser-detect js being discussed here (discourse) does use Firefox's user agent to define if "unsupported" but does not test for Edge or Chrome user agent. And a small list of CSS entries which define if "unsupported". I've seen more **CSS** render websites unsupported in the last couple of years than javascript functions, which is an odd twist of fate as it used to always be the other way around.

Been that way for a LONG time. I haven't wasted time altering a UA string for almost TWO YEARS. Sure, they often times still work, but that is OLD SCHOOL and we (all) should be learning the NEW SCHOOL methods and not hold ourselves back by not looking outside that old-school-box.

Not "exactly" what you are looking for, but a far superior (IMHO) method of password management - https://webextension.org/listing/autofill-forms.html

Easiest would be that if you unlocked/deleted a FOLDER by the name of FOLDER, then *before* you reboot you would create a FILE *without any dot-extension* by the name of FOLDER. ie, replace the FOLDER with a FILE of the same exact name.

These work in 7 so therefore should also work in 8.1 -- https://github.com/e3kskoy7wqk/Chromium-for-windows-7

I have not been following the back-and-forth on PayPal "slide mouse". I can only report that it DOES WORK on first attempt in my OLDER version of Serpent.

You only cite "Serpent 52.9". I use Serpent 52.9 *daily* (for texting from home computer as I do not own a phone!). Therefore, I feel compelled to report, as a *daily* user of "Serpent 52.9", that I do not get this small save-file window. I personally use the below version as I have always had issues with SESSION-RESTORE not working in anything "newer". I have not tried any "newer" version in the last couple of month or so because doing so has somewhat become a "waste of my time" as SESSION-RESTORE issues are never in the changelog!

That's one way to look at it. But another way to look at it is that your computer is supposed to do some of the work for you, otherwise you may as well be living in the 1800's. At work, I can do the work of THREE people because I use scripts and macros and know how to get my computer to do some of the work for me. That is, afterall, why they hired me instead of another one of the folks doing 1/3rd the "efficiency".

ps - if you want to try something one step further and upon your next install, launch the IE6 **BEFORE** your network driver/connectivity, then axe IE6. I personally axe IE by way of the below as a run-as-admin bat-file. Basically, the exe is replaced with a folder of the same name and the exe has its name changed. Windows does not allow a folder and file to be the same exact name. I **KEEP** IE as the OS "default browser" but my IE *cannot* launch. Nothing INTRODUCES security holes in an OS more than having a "default browser"! Unsure why SP2 requires IE6 to be launched but this is not a requirement in SP3 (my SP3's require no IE launch in order for 360Chrome to work). ; takeown /f "c:\program files\internet explorer" /r /d y ; takeown /f "c:\program files (x86)\internet explorer" /r /d y echo y| cacls "c:\program files (x86)\internet explorer\iexplore.exe" /P everyone:f @echo off C: cd "\Program Files (x86)\Internet Explorer" if not exist IEXPLORE.EXE goto End if exist IEXPLORE.EX_ del IEXPLORE.EX_ if not exist IEXPLORE.DIR md IEXPLORE.DIR if not exist IEXPLORE.DIR goto End attrib -r -h -s IEXPLORE.EXE ren IEXPLORE.EXE IEXPLORE.EX_ if exist IEXPLORE.EXE goto End ren IEXPLORE.DIR IEXPLORE.EXE echo IE disabled. echo If prompted, click "Cancel" then "Yes" on File Protection restore. echo Run enable-ie.bat to allow IE to run again. :End echo y| cacls "c:\program files\internet explorer\iexplore.exe" /P everyone:f @echo off C: cd "\Program Files\Internet Explorer" if not exist IEXPLORE.EXE goto End if exist IEXPLORE.EX_ del IEXPLORE.EX_ if not exist IEXPLORE.DIR md IEXPLORE.DIR if not exist IEXPLORE.DIR goto End attrib -r -h -s IEXPLORE.EXE ren IEXPLORE.EXE IEXPLORE.EX_ if exist IEXPLORE.EXE goto End ren IEXPLORE.DIR IEXPLORE.EXE echo IE disabled. echo If prompted, click "Cancel" then "Yes" on File Protection restore. echo Run enable-ie.bat to allow IE to run again. :End

Agreed. Something with the OS-Level "certificate chain" is not fully installed until after IE6 is launched. No risk, in my opinion. I personally trust the 10sec launch to link that chain together over and above any other certificate-repair/update out there. I personally *avoid* interfering with that linkage via "third-party" cert-interference.

And you can rename the 360Loader to ThoriumLoader or whatever else you decide. Just make sure that the loader EXE and the loader INI both have the same NAME (but one is name.exe and the other is name.ini). Makes it very easy to have dozens upon dozens of browsers/versions all handy for testing purposes between browsers/versions.

And not to confuse the issue any more than it may already be, but I would submit that it also depends on HOW you are using Thorium. Me personally, when I did use Thorium (or Supermium), I only used them as "wrapped portables". I never (ever!) "install" web browsers (of any flavor). Again, not to confuse, but you can (because that's how I ran it) run Thorium using 360Chrome's "loader". Then you just do the UA string exactly like you did in 360Chrome (ie, edit the loader's .ini).

For my freshly installed XP x86 SP2 - All I had to do in order to get 360Chrome to finally load ht-tpS sites was to LAUNCH SP2'S NATIVE IE6, let the "internet" icon display in the lower right corner, EXIT NATIVE IE6, then 360Chrome started working. Albeit with an "insecure padlock" - but I ignore those on XP!