UCyborg

Rufus won't bypass the new requirement for SSE4.2 support.

But then they'll keep making more Chromium exclusive web pages... Is it just me, or are there more and more sites that have the problem as exhibited on https://www.tomsguide.com/?

Moonchild mentioned a workaround - set dom.forms.button.standards_compliant to false on about:config page and restart the browser (page reload is not enough). Maybe it works for this too?

I ran XP on a 2 GHz Celeron machine back in the day and it was kinda mediocre.

Accident

Are we really, though? There's so much computers on the market that I wouldn't have the slightest idea what to buy if I was in the market for a new one. Admittedly, my interest in computers waned with loss of interest in gaming, and having to do things I dislike on computer at work doesn't help.

Rebasing will help a lot with memory usage if you currently see chrome.dll in orange when you open thorium.exe in Process Hacker->Modules tab. Slightly off-topic, anyone else finds it bizarre there's newer Chromium for WinXP than for Android 7 (released in 2016) and older?

Multi-process won't work as designed then. https://www.ghacks.net/2017/07/11/firefox-nightly-out-of-process-web-extensions/ And potential compatibility issues with extensions, eg. https://github.com/hackademix/noscript/issues/148

The message comes from Gitea. The workaround for the problem (missing SubmitEvent) is supposedly implemented, that's why there's a warning. Although the question is whether the discussed failure is related or not. Hm, Moonchild crew migrated from GitHub because it (the web interface) didn't support their browser (maybe there were other reasons too), now they use Gitea to host their source code repo which also expects stuff missing from their browser.

LOL, calm down!

I think we don't really know the real troubling factor and just speculating so far. If you force affinity to one core, then OS will schedule that program on that one core, so theoretically, things wouldn't be able to truly run in parallel in that program. Regarding 32-bit and 64-bit, they're just 2 modes and the OS must setup things for 32-bit programs, so I guess 32-bit context is as real as on 32-bit CPUs. That one core on multi-core CPU will obviously be different than the core of other single-core CPUs, but I guess you could say the same for different single-core CPUs.

No idea, but I didn't manage to reproduce on my machine, I tried forcing Mypal 68.14.0b on single-core, kept multi-process enabled, couldn't break uBO 1.57.2.

https://www.youtube.com/watch?v=OR4VCf_J338 Interesting, and there's me taping the old phone together.

Never mind...

Some bugs could look like that in practice. One program I work with at my workplace had an issue in the past where a specific function caused the crash, we noticed at some point during diagnosis the customer is using single-core CPU. It crashed on our test systems as well when we ran the program with affinity set to 1 core.

Might be, I said I don't recall exactly, just seem to (mis?)remember that LED on USB flash drives always powered down on my Windows systems (if this is any indication), but it's been a while since I've actually used Windows 7 specifically and don't have a usable Win7 install at hand to test. Win7 was my main OS in the older days. I wanted to point out generalizations may not be 100% accurate. For example, if I "eject" my phone on XP x64, it still charges. If I do that on Win10, charging stops.

True. You fix those with an USB cable and typing strange commands in console. Strange things are always encountered when deviating from official or just being on too old. I deleted Android Auto as it seems to be a dead end on an old phone. Maybe not if you're hacking wizard. Maybe I should buy an iPhone next time? Noticed on APKMirror Google's apps' version histories are absolutely insane. I'd say both email and smartphone already form a master key these days.

There isn't anything they can do I think, old uBO simply doesn't have the function for removing parameters from URLs.

I don't recall Windows 7 not powering down USB device on eject. Maybe it was some strange chipset driver?

That would be (Android) 2.3. I still have a Samsung Galaxy Mini, sitting unused in a drawer, half physical buttons broken with a battery which depletes in half-hour or so. It was upgraded to Android 4 something unofficially. Latest Android 4 is also pretty much dead. I wanted to try Android Auto on a newer phone (unofficially upgraded to Android 7.1.2) some time ago, not because it is something I really need, just curious as the new car came with Android Auto support. Turned out that software also comes with expiration date. Can't even use an older version of the app. Searching "run android auto on older phones" returned practically nothing. Late edit: I've got a hitch to experiment with this again, actually got further this time with one of the latest versions that could still be run (7.4.620993), made it to the main interface somehow, not sure if adding Android Auto to MagiskHide was the key (hiding root access from it). Android Auto wants oversized Google App to run, we'll see if the phone is still usable with it installed...had to do the dance with deleting whole Dalvik cache (which AFAIK isn't even Dalvik on Android 7 but the folder is still called like that) to force install Google App along with updated Maps on very size limited internal storage. Did experimenting with Android Auto before rebooting, which is a bad idea when I've just nuked the cache... Later when I rebooted the phone, it took a while, but it didn't get stuck and still have little breathing room on internal storage. Still have to check if it even works in the car...

I noticed it on Google Street View.

Vintage vehicles don't have Google's software on-board, modern ones may do.

I've got better things to do than figure out what every site's inline script I visit does. A lot of it is non-free JavaScript (like Richard Stallman puts it), so you could say it's oppressive in a way. But you either trust the sites or you don't and I still have a little bit of faith, if I didn't, my existence would be completely unbearable. My brain only has limited capacity, so there's a lot of free code out there that I have trouble understanding as well. If regular expressions aren't your thing, Proxomitron won't be either.

Firefox works as expected here. Here, I get the same as @AstroSkipper, so "ETC/GMT-1". Edit: Serpent 52 also shows correct output when run on Windows 11.

I also observe the problem with new Date().toLocaleString(); with the clock lagging behind by one hour in Serpent 52. XP x64, usual settings for Slovenia, so GMT +01:00 + auto adjust for DST. I do use registry hack for the OS to interpret CMOS clock as UTC time, although I guess I'm one of the few that do, from which it seems fair to assume it's likely not related. Pale Moon on Win11 shows actual current time for my location. Also still lagging by one hour when called like this on Serpent: new Date().toLocaleString('sl'); New Chromium backports (Supermium and Thorium) seem to behave as expected on XP in that regard. I haven't checked Firefox 52.9 yet.