VistaLover

It's also missing in New Moon 28, but that's because uBlock0 filters "took care" of it Disable uBlock0, clear ALL "*.adobe.com" set cookies, clear browser cache and reload the page: The "optional offer" is just adware, I'm glad it's out of the way for me ; why would one even complain about missing it? Clicking the "Actualizar ahora" button with uBlock0 enabled just loads: https://get3.adobe.com/es/flashplayer/download/?installer=FP_32_for_Firefox_-_NPAPI&os=Vista&browser_type=Gecko&browser_dist=Firefox&type=au&browser_vers=52&stype=7782 for me, after which I am presented with a "save file" prompt, as already previously posted... As you can see by that URI, the page checks for (and needs to know) your OS and browser type/version, so it can fetch the most suitable for you edition of the stub Flash installer...

... Four hours prior to you posting the above: Festive Greetings!

Since the author of that application does already provide a "portable" version of his software, there's not much sense in doing that for HeidiSQL 10.3 ; besides, OP wants an installer for proper (non-portable) installation; my advice: use the previous XP-compatible installer, then overwrite old binaries with the new ones contained inside the portable package; some registry manual correction would be then needed (probably just "cosmetic") to make the OS aware that a "new" version of the app is now in place... (if OP has access to a Vista+ machine, he could install there while using a registry/installation monitoring application, extract the registry keys HeidiSQL 10.3 created during installation and then, with minor edits, merge those keys in his XP/Server2k3 machine...) Just my 2 eurocents

@msfntor I can (re)assure you ALL video-tests and video links you provided WORK AS INTENDED here with Serpent 52.9.0, even on my dirty profile; to simulate Windows XP better, I disabled Vista's native h264/aac decoder (by setting media.wmf.enabled to false) and let Serpent 52 use its bundled decoders, same as on XP... I can provide screengrabs if you're not convinced, but trust me, I wouldn't lie to you... Two notes: 1. On https://www.international.tbs.com/ several clips are no longer available, e.g. "Miracle Workers, Season 1"; but others, like "Those Who Can’t, SEASON 3", do load and play fine... 2. This is quite normal, since both the (older) AVI media container and the Xvid video decoder ARE NOT supported in Mozilla type browsers; I don't think even Chromium-based browsers have such support... At best, only WebM (a sub-species of the Matroska) and MP4 containers are supported in HTML5 embedded players (and with a limited choice for video stream codecs); remember, web browsers shouldn't be (or turn into) dedicated media players! If I were you, I'd stop chasing ghosts; as told before, your issues are probably derived from your extensive use of content blockers (you mentioned uMatrix), privacy extensions/settings, proxy/VPNs etc... The only content blocker here installed in Serpent 52 is uBlock Origin, with the default + several custom filter lists! Everything works as it should! If you ask for uMartix support to make your videos properly load, then I'm sorry, I'm not the guy to offer that... ... Not a big fan of Travolta's myself... ... Yes, in Remove Basilisk from the Unified XUL Platform repository which leads to https://github.com/MoonchildProductions/Basilisk Presumably, all that "relocation" was done to address UXP issue #969: Split applications off from platform (UXP) in order to Is it really "easier" for you @roytam1 that way? Also, do note last comment by M.A.T. regarding Basilisk (hence Serpent 52): https://github.com/MoonchildProductions/UXP/issues/969#issuecomment-566201633 for which https://github.com/MoonchildProductions/Basilisk/issues/1 was created

Can't confirm here: ... so it's probably something at your end Either location/CDN related, ISP related, firewall related, AV application related or, most likely, Serpent 52 profile related ; if it works in a new, clean profile without any extension and with the default settings (GUI and in about:config), then it will signal your issue is due to personal customisations in your current/dirty profile; that could be anything from a GUI-changed setting, a user-set about:config pref, user-installed extension(s) and its (/their) configuration, etc... It's hard to offer meaningful/rectifying advice when one is not able to reproduce your issue(s) ... BTW, updating/installing Adobe NPAPI Flash via that route is probably not recommended on Windows XP; at best, you'll get an on-line (aka stub) installer, which will then attempt to fetch the bulk of needed files using OS (XP) libraries; I haven't tried that stub installer recently on XP, but even on Vista there had been reports of the installer being only SHA2 code-signed (this specific one is not ) and attempting to connect to Adobe's servers via TLS 1.2 exclusively... Your best bet is updating via SHA1 off-line installers, as per Adobe Flash Player has been updated to 32.0.0.303 today

Hi again ; how am I to know that, since you never told us about this fact? ... You are correct; before Firefox Quantum (v57.0+) was finalised and made it to the release branch, a non-Quantum user could install lightweight themes (previously known as personas) directly from AMO; they were at the time simply renamed to just "Themes" by Mozilla, while Complete Themes (the ones previously called "Themes") where demoted and made much more difficult to discover in AMO; that is because they were slated for slaughter , as not being compatible with Quantum... Shortly after Quantum was released, AMO withdrew all "legacy" extensions, together with all Complete Themes ! To add fuel to the fire, they did also remove most "legacy" lightweight themes, while those they kept underwent the Web Extension treatment, to render them compatible with Quantum (similar things happened to language packs and search-engine plugins ). There's a relevant and quite interesting thread in the official Pale Moon Forums that discusses the old vs the new (WE) format of Firefox personas: https://forum.palemoon.org/viewtopic.php?p=177818#p177818 Some "legacy" personas are still recoverable via the Web Archive; the one you already have and suggest to others has, luckily, only one working web capture and can be installed in either FxESR52/Serpent52/Serpent55 through that page: https://web.archive.org/web/20170913041318/https://addons.mozilla.org/en-US/firefox/addon/mussala-856-meters/ This is also available via CAA (caa:addon/lwthemes) and is indeed useful to save to disk (and then be able to re-apply ) an already installed persona, no more to be found on AMO...

See (few posts above) :

You are kindly asked to check the validity of what you post ; the OP asked for a "theme" for his Serpent 52.9.0 copy and what you've linked to is a (lightweight) theme (previously known as persona) packaged in a Web Extension format, targeting at minimum Firefox 53.0; that WE persona won't even install in Serpent 55.0.0, because both UXP and Moebius do not support WE lightweight themes... Most unfortunately, there's currently a very limited choice for Personas compatible with Serpent 52.9.0: https://addons.basilisk-browser.org/personas/

Oops! Wrong link added ; sorry about that... Remove Pale Moon from the Unified XUL Platform repository => https://github.com/MoonchildProductions/Pale-Moon (this probably means additional hurdles for Roytam1, as he'd have to also fork that new repo and make new arrangements for producing his UXP-based browser forks... )

... Running XP SP2 32-bit, i.e. without SP3/SP4, does kind of put you in a minority of XP users here; most software still targeted at XP these days assumes SP3 plus all M$ updates until the End of Extended Support (for XP) ... That is why I said you need to be specific... FWIW, from my own recollections many years ago when I was on XP SP2, the Adobe Primetime CDM (which, for some obscure reason, has become quite en vogue in these forums ), does require SP3 to be present (all I know is I was unable to get it working there; it did install, but no MP4 decoding was possible; ofc, I could be wrong - and no way to retest now...).

Comodo IceDragon 64-bit, forked from Firefox Quantum v65.0 and run on Windows 7 SP1 64-bit is a tad Off Topic for this thread, IMHO ; be that as it may, per my recent post, CID (Fx 65.0 derived) will download and install Widevine CDM v4.10.1146.0 when Play DRM content (or whatever it's called in Fx 65.0) is ticked in Options; but that specific version is currently DEPRECATED by Google (their Widevine licence servers), so if you visit a media site with DRM that requires the Widevine CDM to play its content (video/audio), then you're out of luck with CID; you must use a version of another browser (FirefoxESR 68.3.0, Firefox release 71.0, Google Chrome latest, Waterfox Classic 56.2.13) that has support for the latest supported version of Widevine, v4.10.1440.19 The CID devs will have to either patch their current browser milestone to enable it with v4.10.1440.19 support (which shouldn't be that easy in itself, but definitely easier than porting v4.10.1440.19 support to UXP ) or rebase their fork to use at least a Firefox 68.3.0/69.0+ codebase, which comes with native support for WVCDM v4.10.1440.19 ... Also, on your Comodo forums post, you wrote: Please, DON'T MIX completely unrelated things! The Adobe Primetime CDM was an older DRM implementation (offered by Adobe) that 1. is no longer used by any media site for DRM purposes, 2. it was only internally supported by Firefox versions up to (and including) v52.x.x; starting with Fx v53.0, all Adobe Primetime CDM support code was obliterated from inside Firefox; so, there's no chance a Firefox 65 based fork would download and install APCDM... I re-iterate: (Google) Widevine and (Adobe) Primetime CDMs are NOT interchangeable! And even if you use a browser that does support APCDM, you don't need it at all (as a h264/aac decoder) under Windows 7+ (see more below...) If you're using Serpent 55.0.0 under Windows 7 SP1 64-bit, you have absolutely no need to even install and use Adobe Primetime CDM there; you can't use it as a replacement to the non-working Widevine CDM v1.4.8.903 that St55 installs under Vista+, and you don't need it as a decoder for h264/aac (html5 MP4 video), because, under Win7, St55 already comes with two such decoders: a.) the OS provided one via WMF framework, media.wmf.enabled;true b.) the one bundled within the browser in a custom ffvpx library, media.ffvpx.enabled;true If you're using Serpent 55.0.0 under Windows XP, then, likewise, APCDM can't be used for DRM purposes... And if you need html5 MP4 video decoding support, then media.ffvpx.enabled;true is still valid... Should you wish to install APCDM as an alternate second decoder in St55, then, a) Serpent 55.0.0 originally was forked from a Firefox 53.0a1 snapshot, where APCDM support code was already removed! b) @roytam1 , at some later point after Basilisk/Moebius was abandoned by upstream, did re-introduce APCDM support in St55: https://github.com/roytam1/basilisk55/commit/8dc3c7f3ece162392af056a3b82ce43105ee8938 (ported change from iceweaselXP-53: Restored eme-adobe plugin support for Windows XP systems) As you can see, that support was imported from another fork (not straight from Firefox <=52.x.x); in any case, Serpent 55.0.0 reports itself as being Firefox 55.0, so its GMP-manager will never download APCDM by default... You can try the trick posted in the APCDM thread (and recently mentioned by @Mathwiz): (which, IMHO, should be modded to read: "52.x.x ESR, Serpent 52.9.0, Serpent 55.0.0 users...") and if that wouldn't work, you'll have to manually download and install APCDM v17 as detailed in the relevant thread; but, again, this won't solve any DRM issues you might be experiencing, on any Windows version you might be running Serpent 55.0.0 I have provided, I hope, very clear and detailed explanations/instructions, so make the best you can with them...

@roytam1 : I smell SERIOUS trouble in the air: Remove Pale Moon from the Unified XUL Platform repository ( ... No need to guess whose work was that... )

That would be v2019.6.27 ; actually, AMO, again , made a big blunder there and marked the extension as Firefox 60.0+ compatible; but if you manually download the .XPI file https://addons.mozilla.org/firefox/downloads/file/3060290/https_everywhere-2019.6.27-an+fx.xpi and manually install it in FirefoxESR 52.9.x (drag-n-drop it in about:addons), you'll find it's still compatible: Nothing to apologise for... Simply another case of being misled by the wreck that Mozilla and AMO have now become...

FYI, Firefox versions 49.0.x-55.0.3 will download (and have internal support for) WVCDM v1.4.8.903 56.0.x-59.0.x will download (and have internal support for) WVCDM v1.4.8.1008 60.0.x-63.0.x will download (and have internal support for) WVCDM v1.4.9.1088 64.0.x-67.0.x will download (and have internal support for) WVCDM v4.10.1146.0 68.0.x will download (and has internal support for) WVCDM v4.10.1440.18 69.0.x-71.0.x will download (and have internal support for) WVCDM v4.10.1440.19 (currently supported version by Widevine licence servers; min OS requirement = Win7SP1) This list is only for the Firefox release channel, as the other branches (ESR, Beta/Developer, Nightly) will download different CDM versions... ... Nice detective work, BTW I'd expect you to go about installing Adobe Primetime CDM on browsers installed only in your Windows XP VM (sorry, I lost track: is that on your work or home setup?), as those browsers on Win7 don't need it for decoding purposes ; as Widevine CDM will only install under Vista+, I never considered the case of APCDM parallel install on Win7 ... Yes, that does look as the most plausible scenario! FWIW, my portable installation of FirefoxESR 45.9.1 32-bit under Vista SP2 has no issues automatically downloading/extracting/installing Adobe Primetime CDM v15 (NB, NOT v17) with the default value of about:config pref media.gmp-manager.url: https://aus5.mozilla.org/update/3/GMP/45.9.1/20170613084034/WINNT_x86-msvc-x86/en-US/esr/Windows_NT%206.0%20%28x86%29/default/default/update.xml Best wishes for the coming Holidays

... Latest version 2019.11.7 is still compatible with FxESR 52.9.x; I have it installed in the FxESR52 derived Tor Browser v7.5.6 : Huge thanks for your efforts!

... Of course I believe you ; but I insist that shouldn't happen ! To humour you, I just created a new/clean/pristine (call it what you want...) Serpent 52.9.0 2019.11.15 (32-bit) profile, and by simply going to about:preferences#content and ticking "Play DRM content", apparently a WVCDM v1.4.9.1088 download started in the background! By restarting the browser after ca. 5min, about:addons => Plugins shows the CDM correctly installed and activated: So, most probably, something is amiss in your current Serpent 52 profile (NB: Serpent 55 will still download and install WVCDM v1.4.8.903 !); make sure the pref media.gmp-manager.url is at its default value: https://aus5.mozilla.org/update/3/GMP/60.0/%BUILD_ID%/%BUILD_TARGET%/%LOCALE%/%CHANNEL%/%OS_VERSION%/%DISTRIBUTION%/%DISTRIBUTION_VERSION%/update.xml Under Win7 (x86), that above template should produce: https://aus5.mozilla.org/update/3/GMP/60.0/20191115221435/WINNT_x86-msvc-x86/en-US/release/Windows_NT%206.1.1.0.7601%20%28x86%29/default/default/update.xml ... where the direct link to the CDM (32-bit) is https://redirector.gvt1.com/edgedl/widevine-cdm/1.4.9.1088-win-ia32.zip You can always find the exact URI gmp-manager uses on your OS+Serpent 52 flavour by opening Browser Console before the CDM fetch begins (i.e. before checking "Play DRM content") ...

Glad to know ; perhaps you could apply a similar patch to latest version Kill Sticky 1.6 and upgrade to that, while you're at it? BTW, getting extensions from "unknown sources" is a major NO-NO in my world... ... You're not alone, sadly, but having been a Firefox Nightly tester in the past, I have always advocated here in these forums that the correct way is to always start with a pristine profile and then selectively and gradually transfer over things from the older one, especially when that older profile was touched by a different browser version/fork... Again, foiled by transplanting a Fx52 profile; those prefs don't normally exist in Serpent 52, they are just carried over from Fx52; Serpent has only one such pref, extensions.strictCompatibility, which defaults to false. I had no trouble installing that extension in Serpent 52.9.0 after having patched its install.rdf file to read: <em:minVersion>2.0</em:minVersion> <em:maxVersion>52.*</em:maxVersion> EDIT: The extension will install in St52 without patching its install.rdf file by modifying pref extensions.minCompatibleAppVersion;4.0 to extensions.minCompatibleAppVersion;2.0; but I'm not recommending this! Firefox 2.0 era addons are highly unlikely to function correctly with Australis era Serpent 52 (though this one does); you risk serious profile corruption by installing incompatible extensions, especially those targeting Fx 2.0; you won't know the outcome of such an experiment beforehand; you're on your own on this... BTW, this is a really old legacy extension, dating from 2010, which is currently only available through CAA (caa:addon/export-cookies), Export Cookies 1.2.1-signed.1-signed; but I have verified it still works! A similar extension from 2011 is also available in CAA, Cookies Export/import 1.0.1-signed.1-signed (caa:addon/cookies-exportimport), which does install as is on Serpent 52 ; might want to try that!

I have a patched (unsigned) Tab Tally v1.2.0 installed (in St52) and AFAICS it doesn't come with a "drop-down menu"; it does come with a toolbar button which, admittedly, doesn't stand out well inside FTDD's dark tab-toolbar (where I put it myself), but the number of open tabs is clearly shown in white - plus, when you hover over its button, a tooltip with dark background but light blue characters is shown: Which version of TT do you have installed? First, there's a legacy version (tab_tally-0.1.1-fx-windows.xpi) to be found inside CAA, the versions currently hosted on AMO are, ofc, all of the WE format; versions 1.0.0 to 1.3.0 are id-less, so, as per recent discussion, won't normally install in St52; version 1.4.0 (latest) is not id-less and does install, but it doesn't display the number of tabs in real time unless clicked (so that's why I avoid it!) ... ... OK, I see now you have probably installed v1.4.0, which does spawn a pop-up menu when left-clicked: It's probably possible via CSS to fix the fonts' colour so it would stand out behind the dark background, but am no CSS wizard ; instead, it should be more straightforward to patch the extension itself, should you wish to stick with v1.4.0 that is: Hint: Patch internal extension file popup.html as below: Line 10: - color: #444; + color: #00ADEE; Regards

WVCDM v1.4.8.903 was the version installed and supported by FirefoxESR 52.9.x on Vista+ (so in Win7, too); that version of the CDM was deprecated by Google on Sep 6th 2018; was your St52 profile migrated "dirty" from FxESR52? To update it further on St52 (for purely academic reasons now), with St52 exited delete all WV related directories inside its profile: .<profile>\gmp\WINNT_x86-msvc\gmp-widevinecdm .<profile>\gmp-widevinecdm then launch St52, load about:config and reset all WV related prefs media.gmp-widevinecdm.abi media.gmp-widevinecdm.autoupdate media.gmp-widevinecdm.lastUpdate media.gmp-widevinecdm.version ...make sure media.gmp-widevinecdm.enabled;true media.gmp-widevinecdm.visible;true Exit St52 once more, relaunch, in about:preferences#content make sure DRM content is ticked; visit https://drm.axinom.com/bitmovin-and-unified-streaming/ (or some other test site that requires the CDM) and St52 should prompt you to enable DRM (if not already) and inform you it's downloading "components"... Let it do so for 3 to 5 minutes, then restart St52; upon relaunch, WVCDM v1.4.9.1088 should be properly installed! Visit the test page again, only to find the content isn't being displayed ; Google have deprecated v1.4.9.1088 on Aug 14th 2019 : Being pedantic, with interface v10 of the CDM, Google have introduced some "re-versioning", omitting the first major version number, 1; latest WV CDMs are numbered as 4.10.xxxx.xx (e.g. 4.10.1440.19, 4.10.1582.1, 4.10.1582.2) - 4.10.1196.0 was the last Vista compatible CDM, all newer versions require at least Win7 ... Actually, if your findings coincide with mine, I'll expect you to find WV CDM vanish from both about:addons->plugins and about:plugins ; and yes, APCDM should still be there, but in a non-working state... * NB: Widevine CDM discussion doesn't apply on Serpent 52.9.0 used under Windows XP !

Hello and welcome to the MSFN forums May I ask where did you retrieve an UNSIGNED version of the Kill Sticky firefox extension? This is of the Web Extension (WE) format and, as such, it can't be found inside the CAA addon, while ALL versions of it currently hosted on AMO are SIGNED BTW, the latest version there is 1.6, not 1.4; both claim to be Fx 52 compatible (but we've known from past examples that this is not written in stone, Mozilla may be - and have been - wrong, I'm convinced no-one of their staff manually tests released WEs with older - unsupported - Firefox versions ). Now, although Serpent 52.9.0 has retained whatever limited WE support was originally present in the UXP platform (contrary to official Basilisk 52 which has ditched WE support altogether ), Serpent 52 is NOT ON PAR with Firefox ESR 52.9.0 when it comes to WE support; several WE APIs were removed upstream (by MCP) from Serpent, so telling us that a certain WE addon works in Fx52 but doesn't in St52 isn't something conclusive... I decided to investigate myself, and Kill Sticky v1.4 is an id-less extension, a type of WEs that is not supported in Serpent 52.9.0/UXP out-of-the-box; if you've made the common mistake of transplanting an existing dirty Firefox 52 profile onto Serpent 52/UXP, then it's no surprise the extension got disabled... When changing browsers, always start with a new, clean profile! Trying to install Kill Sticky v1.4 in a Serpent 52 new profile, you'll be met by failure: As already mentioned, this is because it's an id-less WE; but you can patch the XPI file yourself to add the missing id, e.g. edit its manifest.json file like below: { "manifest_version": 2, "name": "Kill Sticky", "version": "1.4", "description": "Kill off the annoying floating things blocking the website you're trying to see", "icons": { "32": "icons/32t.png", "48": "icons/48t.png" }, "background": { "scripts": [ "background.js" ] }, "permissions": [ "activeTab" ], "optional_permissions": ["tabs"], "browser_action": { "default_icon": "icons/32t.png", "default_title": "Kill Sticky" }, "applications": { "gecko": { "id": "kill_sticky@mozilla.org" } } } Of course, that way you'll invalidate the extension's signature, so you can also remove directory META-INF! Have you reached so far yourself? Is this what you mean by an "unsigned" version of KS 1.4? I have no trouble installing my patched version of kill_sticky-1.4-an+fx.xpi in a clean profile of latest Serpent 52.9.0 (2019-12-06); its button shows up in the address bar, the addon is listed as ENABLED in the AOM, and it doesn't get disabled after several browser restarts : Slightly OT, but if you want an extension that can remove "web page overlays", then the legacy extension Behind The Overlay v0.1.6 (via CAA) works nicely in my St52 profile... I personally believe this is not "extension blocklist" related, but deleting a blocklist would only offer a temporary remedy, as the browser will automatically re-download it and place it within its profile... Best regards EDIT: Apparently, boolean user pref extensions.blocklist.enabled (defaults to true) controls the blocklist implementation; there exist several other extensions.blocklist.* prefs, one of which is extensions.blocklist.url; I guess by modifying its current value (string) to an invalid URI, you can stop the browser from fetching it... But I stress I don't believe myself the OP's issue is blocklist related... (but I could be wrong, once more... )

It is with sadness I have to report my favourite Bit Torrent client of close to 6 years now, qBittorrent, has dropped Vista (and probably XP) support! I was running the portable PAF version and just found out the hard way, after accepting a prompt to upgrade to the recently released new version 4.2.0: Inspection of the main x86 executable with Dependency Walker reveals further missing function calls in Vista's system files: in SHELL32.DLL Shell_NotifyIconGetRect in MFPLAT.DLL MFCreateMFByteStreamOnStream in USER32.DLL ChangeWindowMessageFilterEx CloseTouchInputHandle GetTouchInputInfo IsTouchWindow RegisterTouchWindow UnregisterTouchWindow The application is compiled with the Qt Framework, last version of which to be compatible with Vista+XP is 5.6.x (I think 5.6.3 was the last release of the 5.6 branch); the app's code is open-source, published on GitHub: https://github.com/qbittorrent/qBittorrent Browsing that repo, it becomes evident that the team of devs willingly moved past NT6.0 support, e.g. https://github.com/qbittorrent/qBittorrent/commit/5d0d8a0b7b032ed6f850325921eddc2f7303d9a8 https://github.com/qbittorrent/qBittorrent/commit/a4b9a4d9da9c9479eb1e63c8b8157aa4209c627c https://github.com/qbittorrent/qBittorrent/commit/7276a79cefe00f3e82fec8760ec876aa8a276df0 https://github.com/qbittorrent/qBittorrent/commit/2f0ae7a7d8c53d8c1d1bee08d61e5dcb28cfd61b https://github.com/qbittorrent/qBittorrent/commit/3ab2fe907f9519a9a90e072576ba6cfbbd52857d https://github.com/qbittorrent/qBittorrent/commit/74fc86e2ab2896bff9e90ab710b722027f2b9678 where the last commit dates from March 17th (!) 2019 and contains the changelog lines: - WINDOWS: Drop support for < Windows 7 (snip) - OTHER: Raise minimum Qt version to 5.9.0 (sledgehammer999) Another reason I did not see that coming was the fact the pre-release alpha builds, v4.2.0alpha, had been available only in the x64 architecture (on their site: "For Windows, only the 64-bit build is available for the alpha release."), so I couldn't test them prior to the official 4.2.0 x86 release... Had I been more cautious, I could have 1. spotted, between the lengthy release notes of 4.2.0, and in the downloads page itself So, I guess I'm stuck at the last version of qbittorrent that's Vista SP2 compatible, which is v4.1.9.1 https://www.fosshub.com/qBittorrent-old.html?dwl=qbittorrent_4.1.9.1_setup.exe https://sourceforge.net/projects/qbittorrent/files/qbittorrent-win32/qbittorrent-4.1.9.1/ Portable version, in PAF format: https://portableapps.com/downloading/?a=qBittorrentPortable&n=qBittorrent Portable&s=s&p=&d=pa&f=qBittorrentPortable_4.1.9.1.paf.exe Many years ago, I'd be using Shareaza (remember that?) as my P2P client, for both ed2k and bittorrent shares, but when emule went out of fashion, I switched to μTorrent for the BT network... But when that turned into a horrible adware , I gladly switched to qbt, which offers pretty much the same GUI (minus the adds...); plus, its Python powered search feature is not to be missed... Other BT clients I had also tried in the past, showing a preference to Tixati ; but I stayed with qbt ; I don't want to derail this thread, but should I be considering switching to another BT client for the duration I'm still on Vista SP2? What is your personal experience with the other choices?

Welcome to MSFN Forums ; judging by that screenshot, what you're after is a "Complete Theme" Several Complete Themes do exist for New Moon 28 in the official Pale Moon extensions repository: https://addons.palemoon.org/themes/ However, if you want one for Serpent 52.9.0, then only one is officially available: https://addons.basilisk-browser.org/themes/ and to add insult to injury, that unique one only works correctly on Win7+ (it contains specific Win7+ CSS code ) You'll have better luck installing a Firefox 52 compatible complete theme; however, 1. AMO (addons.mozilla.org) has had all Complete Themes removed since Quantum (Fx 57.0+) was released... 2. The ill-fated, now taken down, legacycollector site did not list any Complete Firefox Themes 3. Likewise, the CAA (Classic Addons Archive) extension does not contain any reference to Complete Firefox Themes (a very unfortunate/poor decision by its maintainer, if I may say so myself) ... Your only source of Complete Firefox Themes currently is what has been salvaged from AMO by the web archive: http://web.archive.org/web/20181124130244/https://addons.mozilla.org/en-US/firefox/complete-themes/ You can start from there and hopefully find your way to an archived XPI theme file... Mine (depicted in your screenshot) is FTDeepDark v14.3 (slightly patched to accommodate minor Serpent issues...): https://web.archive.org/web/20180729192834/https://addons.mozilla.org/en-US/firefox/addon/ft-deepdark/versions/?page=1#version-14.3 Direct link to XPI file: https://web.archive.org/web/20170829121054if_/https://addons.cdn.mozilla.net/user-media/addons/295337/ft_deepdark-14.3-fx-windows.xpi?filehash=sha256%3A1a92752850c0e90b0962eec6b0d5e5343c703d4a8b64905d756a82621ef5b5c8 Regards

Most unfortunately, I can reproduce ; and it isn't only the Adobe Primetime CDM affected, as reported by @dencorso, but also the Widevine CDM too, which is installed and visible under Vista+; Widevine CDM v1.4.9.1088 is currently broken since August 13th 2019, due to Google changes - effort is underway by MCP to restore Widevine support in official Basilisk ( see here ), which is currently hitting a deadend, but any success won't benefit Vista users of Serpent, as updated Widevine DLLs don't run on Vista and require Win7+; still, having a working implementation of WV on Serpent would certainly benefit St users on Win7+ I normally don't have Adobe Primetime CDM (APCDM) installed in my Serpent 52 profile, but to humour @dencorso I did correctly install it (v17) and made sure I disabled the other h264/aac decoders: media.wmf.enabled;false (Vista's native WMF decoder) media.ffvpx.enabled;false (Serpent's bundled FFmpeg decoder) while I made sure media.gmp.decoder.enabled;true (APCDM's decoder) Widevine CDM (WVCDM) v1.4.9.1088 is also correctly installed. Extended testing reveals that: A. 2019-11-15 Serpent win32 build is the last good build where: 1. WVCDM appears installed in both "about:addons => Plugins" and about:plugins : 2. APCDM's decoder properly works for MP4 HTML5 video; e.g., first test clip on https://tekeye.uk/html/html5-video-test-page (1: HTML5 MPEG Video Test) B. By simply updating to the next Serpent 52 build, 2019-11-22, one discovers that it's the first bad one, since: 1. WVCDM magically vanishes from both "about:addons => Plugins" and about:plugins : 2. APCDM, while still present in both "about:addons => Plugins" and about:plugins, simply quits functioning as a h264/aac decoder (as reported by dencorso): @Mathwiz : Could you be so kind as to confirm my tests, preferably on Win7 where Widevine CDM is visible (thanks in advance ) ? ====================================== Now, examining more closely related code, MCP did remove APCDM support in official Basilisk in UXP #1259 ; the bulk of the patches would have landed in the 2019-11-15 build, as per but you did revert those (more accurately, did not apply at all in your custom branch), as per ... furthermore, the reversion has been successful, as the 2019-11-15 build is, according to my analysis above, the LAST GOOD one The MCP devs did not revisit issue #1259, except for https://github.com/MoonchildProductions/UXP/pull/1293 (Adjust Widewine strings after removing Adobe Primetime support) and thus https://github.com/MoonchildProductions/UXP/commit/36c81a9 This would have normally landed in the 2019-11-22 build of Serpent 52: while you did not technically revert that, you added your own version with a slightly modified code: https://github.com/roytam1/UXP/commit/e50e93c Since I'm not a code wizard by any stretch of the imagination, I can't be certain that the culprit for the issues reported here lies within that commit of yours... What is absolutely certain is the offending changeset(s) lives inside the changelog (in your custom UXP branch) between Serpent build 2019-11-15 and build 2019-11-22 ; please, at your discretion, investigate further ... Because, while you took the extra effort to keep APCDM support inside Serpent 52 alive (against MCP's agenda), not only did we end up with a crippled APCDM installation, but also Widevine took an unexpected hit and did a disappearing act... Thanks for your time reading this long report, hopefully you'll get it sorted out! Many thanks, as ever, for providing your forks to the community! Best regards

Am afraid no-one else but you can answer that question ... Only you know the exact configuration of your OS/system and your browsers - the rest of us here trying to help are not clairvoyants; and, as you can imagine, all have our personal issues in both digital (!) and real life... So, when asking for help, be extremely precise about your CPU/OS and browser; and in the case of browser, type/version/architecture/EXTENSIONS/user-modified prefs are of high importance! Then, of course, there are cases where manifested issues are due to factors beyond your control, e.g. hick-ups at your ISP or server-specific outages... Many things can go wrong (but, thankfully, few do at the same time...) ! You have proclaimed your "love" for using Proxies, VPNs and privacy related tools; a shot in the wild, but maybe one of these is the cause for your issues? And I'll emphasise once again that the first troubleshooting step when it comes to browser problems is to START WITH A BRAND NEW (CLEAN) PROFILE (no extensions, default "GUI" and "hidden" settings), using your DIRECT ISP connection - if you can't reproduce the problem there, then you know it's caused by something YOU did... FWIW, all images load fine here: FWIW, plays fine here (Serpent 52.9.0): This is only used within a WebRTC context (not supported in New Moon, but is supported in Serpent 52/55); if you're on Windows XP (with SP3 I presume, fully updated until the EOS MS updates), then by default New Moon 28/Serpent 52.9.0/Serpent 55.0.0 will come with a bundled h264/aac decoder (in the form of a custom ffvpx library - make sure media.ffvpx.enabled (in about:config) is in its default value, true); so you shouldn't have MP4 video playback issues...

The LIVE (i.e. non-archived) edition of the Tek Eye test page loads and works fine here (Serpent 52.9.0) : So, whatever issues you're having must be at your end...