VistaLover

I realise VLC specifically is NOT the topic of this thread, but could you be so kind as to actually pinpoint/link to that version? On https://artifacts.videolan.org/vlc-3.0/nightly-win32/ you can see that their server retention goes back to last December, ONLY, so I expect, in the future, that older "artifacts" will be forever purged ; perhaps this last, XP-compatible, build deserves to be archived for posterity ... These recent VLC builds exhibit a very high CPU consumption on my old Core2 Duo processor when listening to radio (audio) streams using either the HLS/mpeg-dash streaming protocol, e.g. to BBC Radio 2 Live stream: http://as-hls-ww-live.akamaized.net/pool_74208725/live/ww/bbc_radio_two/bbc_radio_two.isml/bbc_radio_two-audio=96000.m3u8 I have identified the issue to be with recent versions of the "libadaptive_plugin.dll" module: .\plugins\demux\libadaptive_plugin.dll Swapping the 3.0.24 version with the 3.0.8 old one (from 2019!) reduces the CPU usage to just 25% of what the current version uses... Apologies again for the somewhat OT parts of this comment ... Best regards.

If it makes any difference, the "missing-titlebar-bug", https://github.com/Eclipse-Community/r3dfox/issues/177 https://github.com/e3kskoy7wqk/Firefox-for-windows-7/issues/147 , is caused by a change between v151.0a1-v4 (last GOOD build of the 151 branch) and v151.0.2 (first BAD build of the 151 branch); so, not that big of a "regression window" to dissect ...

Again, autodidact is NOT to blame ; go back some pages in this thread and you'll read (some) users of FFmpeg (on WinXP and elsewhere) declaring they don't want FFplay at all, because they ONLY use dedicated GUI players for playback of media files ; and I don't recall off-hand why the XP shared builds were axed, too, but autodidact simply delivered what (XP) members here asked for ...

... It would appear that Shane is still monitoring this thread ; inside the Supermium-v144-r4_01 release notes, https://github.com/win32ss/supermium/releases/tag/v144-r4_01 this shows up: https://github.com/win32ss/supermium/releases/download/v144-r4_01/supermium_uao.zip Edit: Rather the fix was a consequence of the discussion in: https://github.com/win32ss/supermium/issues/1907 ...

Actually, "supermium_uao.exe" won't launch under XP SP3 (32-bit) because of two missing functions on XP's kernel32 system file: # Report By YY.Depends.Analyzer (Target:5.1.2600-x86) ## kernel32.dll * [ ] InitializeCriticalSectionEx - Supported OS: 6.0.6000, 6.1.7600, 6.2.9200, 6.3.9600, 10.0.10240 - Ref Module: supermium_uao.exe * [ ] LCMapStringEx - Supported OS: 6.0.6000, 6.1.7600, 6.2.9200, 6.3.9600, 10.0.10240 - Ref Module: supermium_uao.exe Above is a log acquired via the YY-Thunks CLI tool; the command I used was: YY.Depends.Analyzer "supermium_uao.exe" /IgnoreReady /ReportView:CheckBox /Target:5.1.2600 As @mjd79 suggested (), if you redirect the kernel32.dll function calls to Supermium's wrapper DLL "pwrp_k32.dll", you'll be able to make the executable XP-compatible ...

FWIW, this tool has existed since Oct 2024 (!), but was being offered exclusively to Patreon paid-subscription members : https://www.patreon.com/posts/supermium-uach-113234339 (... and it does work under Vista SP2 32-bit ) @NotHereToPlayGames , have you read this ?

That last statement has been only PARTIALLY true, or even completely FALSE (based on a user setting), since a great-many number of past Chromium versions; since the "mid-50's", shortly after XP/Vista support went away, Chromium also comes with its own Certificate Store, a la Firefox; the OS cert store can be used as a supplement, too, or completely disabled; I'm too lazy now to search for the very first Chrome version that bundled its own cert store, but as the question involves (recent) Supermium, here's some "enlightening" pictures of Supermium's own CertManager: "localcerts" are the ones imported from the OS CertStore; they can be made available to Supermium, or completely ignored, as per my setting in the picture above ... "crscerts" are Supermium's own CertStore root certificates; there's even the ability to export the store to a PEM file, but NOT import a cert from other sources... Site certs are actually "server" certs; these have to be verified against a cert-chain, possibly involving also "intermediate" certs stored transiently in the store, whose end is always a Root Certificate stored in either the browser's store or the OS store; when server certs expire, the server owner has to renew them with new ones issued by a Certificate Authority (paid-for or free, like "Let's Encrypt"); root certs have very long validity durations and when they expire, it's up to the browser or OS vendor to renew them; also, some root certs sometimes get revoked (because of them having been compromised), so the cert store, be it in a browser or the OS. has to be properly "maintained"; "legacy" WinOSes, no longer supported by MS, usually have stale OS cert stores, so these should either be manually updated somehow , or the user should, instead. turn to apps with their own, maintained, root cert stores ...

Yes, and Moonchild acknowledges this: Perhaps the issue is more visible with tabs-on-bottom ? On Vista, with Aero-enabled, I can't easily tell any difference, though...

And whose fault is that? Certainly NOT @autodidact's ; many users here, especially the "XP-die-hards", complained of "inflated" FFmpeg binary sizes; that they ONLY wanted a binary capable of just remuxing downloaded formats (and only with the h264/aac codecs) from youtube.com; nothing more; IOW, a "bare-bones" FFmpeg compile... So, "they" got what "they" asked for (and no more shared builds, on top of that) ... I, of course, was against such a request, because I also use FFmpeg outside of a yt-dlp context; e.g., the latest XP binary can't even fetch MPEG-DASH streams on its own, because it has been compiled without an XML parser (libxml2)); since I'm on Vista SP2 x86, I stayed silent, as the "Vista builds" (many thanks for those shared binaries, too ) continue to fulfill most of my needs under Vista; no complaints here of any sort, @autodidact !

You're referring to the quickjs release claim, stated below: https://bellard.org/quickjs/ ... but they specifically mention the "bench-v8 (aka v8-v7) score", which I'm certain doesn't take into consideration using the library together with yt-dlp (especially on old, under-powered, H/W like the one many of us here use ) ... In any case, any performance improvement in general should have a beneficial impact even to us using quickjs for "youtube.com" purposes, and this is something that you verified yourself ...

There has been a new release (finally ) by its author, Bellard, of the quickjs JS runtime, necessary for de-scrambling YouTube's nsig challenges (present on most yt_player_clients, except for ANDR-V); the 32-bit binary can be found on: https://bellard.org/quickjs/binary_releases/quickjs-win-i686-2026-06-04.zip (64-bit binary: https://bellard.org/quickjs/binary_releases/quickjs-win-x86_64-2026-06-04.zip) quickjs is the only supported JS runtime on "legacy" WinOSes, like XP SP3/Vista SP2/Win7 SP1; I can't check on XP SP3 x86, but the new release does launch here (Vista SP2 x86): qjs -h => QuickJS version 2026-06-04 usage: qjs [options] [file [args]] -h --help list options -e --eval EXPR evaluate EXPR -i --interactive go to interactive mode -m --module load as ES6 module (default=autodetect) --script load as ES6 script (default=autodetect) --strict force strict mode -I --include file include an additional file --std make 'std' and 'os' available to the loaded script -T --trace trace memory allocation -d --dump dump the memory usage stats --memory-limit n limit the memory usage to 'n' bytes (SI suffixes allowed) --stack-size n limit the stack size to 'n' bytes (SI suffixes allowed) --no-unhandled-rejection ignore unhandled promise rejections -s strip all the debug info --strip-source strip the source code -q --quit just instantiate the interpreter and quit Additionally, the quickjs-ng fork has also seen a new release: https://github.com/quickjs-ng/quickjs/releases/tag/v0.15.1 https://github.com/quickjs-ng/quickjs/releases/download/v0.15.1/qjs-windows-x86.exe This runtime officially supports Win7 SP1 and later, but it can also work under Vista SP2 (but NOT on XP SP3): qjs -h => QuickJS-ng version 0.15.1 usage: qjs [options] [file [args]] -h --help list options -v --version print version string and then exit -e --eval EXPR evaluate EXPR -i --interactive go to interactive mode -C --script load as JS classic script (default=autodetect) -m --module load as ES module (default=autodetect) -I --include file include an additional file --std make 'std', 'os' and 'bjson' available to script -T --trace trace memory allocation -d --dump dump the memory usage stats -D --dump-flags flags for dumping debug data (see DUMP_* defines) -c --compile FILE compile the given JS file as a standalone executable -o --out FILE output file for standalone executables --exe select the executable to use as the base, defaults to the current one --memory-limit n limit the memory usage to 'n' Kbytes --stack-size n limit the stack size to 'n' Kbytes -q --quit just instantiate the interpreter and quit Both are fully supported by latest yt-dlp; performance-wise, they shouldn't differ much, if at all...

@NotHereToPlayGames : https://msfn.org/board/topic/187814-country-flags-missing-to-the-left-of-members-usernames/#findComment-1287938

... Well, I couldn't help noticing that member @Gregg (from the UK), who posted in the r3dfox thread (to which I'm subscribed ) and to which NHTPG kindly replied, now appears as "Guest Gregg" with no profile/membership at all ; I got the impression they were a 100% legitimate member, though ... Many thanks indeed for the prompt fix! Your efforts towards keeping MSFN "alive and kicking" are highly appreciated, and I'm not just saying this; MSFN is one of only two tech-forums I'm a member of, it really means much to me ... Well, for once you're wrong ; I do own a DeLorean myself, be it a plastic scale model of it ; actually, I got carried away by the forum's default date format, which is the one used in the US (i.e. MM/DD/YYYY); so, when composing my post, I mistook "06" as the day of the month (being accustomed to the European format of DD/MM/YYYY); so now you know ...

Today (June 4th 2026) I noticed that I can no longer view a member's country flag to the (upper) left of their username (and above their avatar picture): There appears to be an empty placeholder for the country flag, as one can see when hovering over the "place" the flag should've been displayed, but the actual flag is MIA ; could this issue be looked into, please? PS1: In my account settings, I have chosen to always view members' country flags (if available) ... PS2: This is a reappearance of this older Forum issue ...

... Some explanation to be found here, courtesy of @AstroSkipper ...