66cats

Late to the party. Surprised no one uses Passmark 8: [download page, scroll to "older versions" for "PerformanceTest 8.0] - small download, short run time, less gamer-centric, offers a friendly, detailed graph breakdown. This is the box i'm on now, XP 64 installed on NVMe drive / X99 i7 6800k. Fancy HW, though even overclocked, cooking grade i7 6700k (and even i7 4770k) outperform it in XP benchmarks, especially with older ones like 3DMark 2001 :'(

The same place bottled water manufacturers write "WARNING: CONTENTS MAY BE WET!" Again,

Sure, and imaginary (made up) laws are also a subset of "any laws," and, thereby, actionable. Some would argue that such a literalist reading is absurd, complaining that a reasonable person reading the TOS of a US company understands that "any laws," in such a context, means US (not Canadian or fictitious) laws. Not i -- just tossing it out there for your consideration. Not without running afoul of US law, no. Though a US company choosing to to comply with US law is, in this case, inconvenient, that's simply how our current reality is structured.

Sorry if i didn't make myself clear, i'll try again: why would you expect GitHub (a US company) to warn users that it may follow US law? Seems self-evident to me. A bit of an idee fixe (your native tongue?) for you. Let me reassure you, i'm a US national, posting from US.

That a US company may comply with US law?

US entities must comply with US (rather than Russian, Canadian, or Sharia) law. Simply how US law works. GitHub may take down content violating US law and GitHub TOS -- legal and reasonable. It is sufficient for foreign nationals to adhere to US law and GitHub TOS when using GitHub. Why would you want a more restrictive policy?

Windows 3.1 didn't run on 8088, 95 wanted a 386, 98 wanted a 486, XP wouldn't install on a 486, etc., no one thought it unreasonable. When MS set the bar too low for Vista, that's when everyone complained. If we don't insist on official support, sticking 11 on older/unsupported HW is as simple as checking a couple of boxes in Rufus. 11 officially supports Coffee Lake (2017). Pouring time/money in outdated HW support is unlikely to result in higher profits. C2Ds came out in 2006, currently in the hands of a few labs/businesses (gear that doesn't have drivers/software for newer OSes, so XP) & hobbyists (who got C2Ds specifically to run XP on "period correct" HW). 11 on C2D is doable (maybe not 24H2), though can't see anyone doing it out of necessity.

360Chome 13.5, Windows 10, works here (without changing user-agent).

The alternative is to simply ignore new instructions, available on more recent CPUs.

No opinion, it's supposed to melt all at once, instead of being semi-molten over a few degrees range like 60/40. By 60/40, i just meant basic tin/lead solder, not exact Sn/Pb ratio. Re. your bad memory stick: have you tried all the usual stuff, like different slots/raising the voltage/loosening timings? BTW, generic 800MHz DDR2 sticks are still cheap/plentiful on US eBay, ~$5 shipped, "buy it now," for a 2GB stick.

Abomination, abhorrent to God. Since you're running into HW problems in another thread (which might involve replacing caps), get some regular 40/60 tin/lead rosin core solder. When you desolder, add some of this to the solder joints -- resultant alloy will have a lower melting point & make parts removal much easier.

In Vista+ (where hardware acceleration works by default), for me, there's no difference. In XP, this progwrp.dlll allows HW acceleration.* With HW acceleration enabled, you should see measurable improvements in browser benchmarks like Speedometer 3.0, especially in graphics benchmarks like MotionMark (50 to 100% higher scores on my HW). Can't say the difference is immediately obvious outside of benchmarks. *To enable HW acceleration, launch Supermium with --use-angle=d3d9 --ignore-gpu-blocklist. This setting won't work with older GPUs/may introduce additional issues (v1.2 is still "pre-release").

There's a new version for 124, 1.2.0.5065. Direct download here.

Just tested with with some old 360Chrome 13.5, seems to work (gives me "We do not recognize your username and/or password. Please try again.").

Found out too late, see edit. Correction to the edit: h264ify does do its thing, it just so happened that the vids i was clicking through, being new, were AVC1 by default.