VistaLover

Not quite... FxESR 52.9.0 (and later), as well as Basilisk (Serpent) 52/55 have this functionality as a native application feature, so they're not in need of the E-N-T extension; but this feature is native to the Australis (Fx 29-56) UI, used in both above browsers... Pale Moon (New Moon) 27/28 continue to use the pre-Australis (Fx 4.0-28.x) UI, and this lacks support for indicating tabs with audio content; to regain part of this functionality, on NM you have to install that special extension; I say part, because that extension only works in tabs with HTML5 audio(/video), whereas the native function in Australis Fx works even in tabs with an embedded Shockwave Flash player...

Hello The standalone windows executable, file youtube-dl.exe (32-bit, filesize 7.59 MiB ) has been compiled with Python 3.4.4 modules, which, AFAIK, is the last XP compatible Python version, most certainly not the latest (3.6.6/3.7.0). On my Vista laptop, issuing "youtube-dl --version && youtube-dl -v" in the command prompt window, in my yt-dl installation directory, I get: 2018.09.01 [debug] System config: [] [debug] User config: [] [debug] Custom config: [] [debug] Command-line args: ['-v'] [debug] Encodings: locale cp1253, fs mbcs, out cp737, pref cp1253 [debug] youtube-dl version 2018.09.01 [debug] Python version 3.4.4 (CPython) - Windows-Vista-6.0.6002-SP2 [debug] exe versions: ffmpeg N-91152-g7c333dc6a7, ffprobe N-91152-g7c333dc6a7, p hantomjs 2.1.1, rtmpdump 2.4 [debug] Proxy map: {} Usage: youtube-dl [OPTIONS] URL [URL...] My assessment is based on https://python.readthedocs.io/en/latest/using/windows.html#supported-versions While the latest release of the 3.4 branch is 3,4.9, every release after 3.4.4 has been made available only as source; the last XP compatible compiled installer is for 3.4.4, to be found here ... But even if/when in the future the yt-dl devs compile the standalone executable with non-XP compatible Python modules, all is not lost for XP users; yt-dl code has support for a variety of Python versions, methinks 2.6 to 3.7; so, an XP user can perform a full-blown Python installation on his/her system and then use the compiled zipped-executable version of yt-dl, file youtube-dl (size 1.62MB) on the GitHub Releases page... It can be invoked in the command line as python.exe youtube-dl [various yt-dl arguments] (you may have to use pip first to install additional python modules that yt-dl depends on, ones that do not come with the default (standard) installation on windows; but this is not a yt-dl support forum, ample info/help can be found on line already...) @Flame : While I spent 3 years on XP, I currently have no access to that OS (only to Vista SP2 32-bit + Win7 SP1 64-bit), so it would have been easier for you (... and me ) to get an answer to your query, had you kindly asked one of the many XP users that frequent this thread to test youtube-dl.exe for you (assuming you can't yourself...); but I didn't mind the challenge to answer it for you one single bit... Regards EDIT: @hotnuma beat me at posting, adding relevant information

... Nothing of this sort here... Trying a non-protected, non-music video like https://www.youtube.com/watch?v=I6M_vYUUx20 I can fetch without issues: I was curious to try a "protected" music video from VEVO, like https://www.youtube.com/watch?v=BilaShsQphM Even HD versions are available to download, provided I first select them in YT's embedded player (quality settings) Those MKV files contain VP9/opus encodes; if you are instead after a 720p MP4 file encoded in h264/aac, then you first have to disable (temporarily) Media Source Extensions (MSE) in NM28's settings Options -> Content tab -> Video -> uncheck MSE so that YT serves you that type of stream: If you're that interested in YT content, I'd recommend a specialised tool (not a browser plugin) like the constantly updated CLI app youtube-dl, if you're willing, that is, to work in the Windows Command Prompt... You should've created a separate support post and let @roytam1 know about this issue; needless to say, you should PM him log-in credentials too, if any hope of debugging this... Moonchilld have EOL'd Tycho (PM27), so 0 chances they address this now...

Latest builds announced by roytam1 here ; please also have a look at Roy's blog entries... Should create its own separate profile, but for good measure back-up any existing profile of Serpent52 on your system...

IDM integration v6.27.7 XUL ("legacy") browser extension is compatible with Firefox 52.9.0 ESR; since PM28XP is built on the UXP-T2 platform, forked from Mozilla 52.6.0 ESR, that same extension is compatible with PM28XP; sadly, it isn't installable out of the box, because its install.rdf file (inside extension's .xpi file) does not contain Pale Moon's GUID (={8de7fcbb-c55c-4fbe-bfc5-fc555c87dbc4}). You have two options: 1. Install "Moon Tester Tool" Pale Moon extension on NM28; open addons manager, locate MTT's entry there and access its preferences panel; click the Select file button and then navigate to IDM's installation directory (e.g. "C:\Program Files\Internet Download Manager") and select file idmmzcc2.xpi; it should now offer to install; restart browser and see the IDM addon installed and enabled! As you've already done, be sure to enable Pale Moon browser in the main IDM app's prefs... 2. Patch the existing extension version yourself; I won't provide a detailed guide here, but you should first decompress file idmmzcc2.xpi with 7-zip, open file install.rdf and after line 17 add a targetApplication block specific to PM: <!-- Pale Moon --> <em:targetApplication> <Description> <em:id>{8de7fcbb-c55c-4fbe-bfc5-fc555c87dbc4}</em:id> <em:minVersion>27.0.0a1</em:minVersion> <em:maxVersion>28.*</em:maxVersion> </Description> </em:targetApplication> Save the changes made; while you're at it, you can safely also delete dir META-INF, because PM does not enforce extension-signing... Re-zip modified contents of folder idmmzcc2 back to a idmmzcc2.xpi file and replace the original with it; restart NM28; if the extension is not picked up automatically, you may have to manually install it via drag-n-drop on NM28's addon manager tab...

@dencorso I'm probably just being dense due to the heat (34C here, on Sep 1st!), but you first quote a part of my post in which (part) I say nothing about Adobe Primetime CDM, then you proceed with discussing that same CDM; I don't get the connection... Yes, Mozilla has removed automated in-browser downloads (Bug 1337121, Bug 1304899) ... Do you actually mean that the CDM there is able to perform the role it was first designed for, decrypt DRM content? Please provide example cases... AFAIK, most DRM content providers won't use / don't support that deprecated CDM, either as a standalone decryption solution nor as a fallback when Widevine CDM is absent/disabled/non-functional... As I stated in that previous post of mine, so I can only surmise that by "still works OK" you are referring to that specific function of that CDM (which, for all intents and purposes, was not the reason it was conceived and bundled with the Firefox browser...). The Moebius platform both Basilisk 55 (by Moonchild - EOL'd) and Serpent 55.0.0 (by roytam1) build upon was forked from a Mozilla 53.0a1 platform snapshot; Mozilla themselves gutted out Adobe Primetime CDM support code from Firefox in Bug 1329543; mozilla-central Nightly-53.0a1 builds after 20170118 have no support for it; if Moonchild forked the platform from a snapshot after Jan 18th 2017, then it's safe to deduce Bk55 has no support, either; but I am uncertain of the exact code timestamp Moebius was forked from, so I'll leave the actual test to someone else... Most probably, Moebius has no support for that CDM... But Serpent 55.0.0 on XP does have native h264/aac decoding support, because roytam1 patched third party library ffvpx to include support for these patented codecs, too...

I am sorry to be the bearer of bad news, but if you're asking specifically for the Windows XP SP3 OS and the Spotify web player on a Mozilla type browser, there exist several serious reasons this isn't possible! 1, Spotify is one of the commercial media outlets that heavily use DRM for content protection; on Firefox and its forks, content decryption is delegated to CDMs (Content-Decryption-Modules), which are closed-source modules ("blackboxed") bundled with the open-source browser, to satisfy user watching/listening needs. 2. Mozilla had first incorporated Adobe Primetime CDM for the decryption of DRM'd content (a CDM familiar to XP users, as it is currently being "exploited" to enable h264/aac decoding support in the FxESR 52.x.x browser (... and some of its forks); this is not, however, a use intended initially by the Mozilla devs ), but that CDM was abolished in Fx 53.0+ in favour of the universally accepted, Google-owned, Widevine CDM. 3. As you probably know, all Mozilla browsers come without native support for patented decoders, like h264 (for video) and aac (for audio); if Mozilla went the "Google Chrome" way and bundled these decoders with Firefox, they'd have to pay annually huge sums of money as license fees to the patent holders (namely to the MPEG-LA group); they opted for a far less costly solution, that is to rely on system decoders (the ones bundled with the actual OS). 4. Speaking of Microsoft and the Windows OS, the first iteration of Windows with native h264/aac decoders came with the launch of Windows 7 OEM, though its predecessor OS, Windows Vista, was, too, equipped with similar support (be it less refined) when "Platform Update Supplement" for Vista SP2 was released via Windows Update.... Microsoft chose not to bestow h264/aac decoding support to Windows XP which is, in a way, the deal-breaker in your query... 5. Widevine CDM inside Firefox (or one of its forks) only executes decryption of the DRM'd media streams, the decrypted stream has then to be properly decoded to video and/or audio; Widevine in Firefox has been programmed to search for decoders only in the OS level (not the browser); remember that it is (very) closed source, this assumption is the result of tests only, no actual code for Widevine is, of course, publicly released... 6. Since Windows XP lacks native system decoders (and no, installed codec-packs don't work for Widevine), the Mozilla devs have disabled Widevine on XP, and only enabled it on Vista SP2 upwards; hence, minimum system requirements for services that employ Widevine on Firefox is WinVistaSP2+; however, since Vista has been EOL'd by Microsoft, this is currently read as Win7SP1+... 7. Specifically in the case of the Moonchild Productions' Pale Moon fork, because of their opposition to the closed-source nature of CDMs, they have purposely disabled DRM (CDMs) in the browser, so it's currently impossible to use DRM'd services (e.g Netflix, Amazon Prime etc.) in that browser, regardless of OS; the same holds true for New Moon 27+28, both Pale Moon forks... 8. Certain services that rely on Widevine did implement, at least in the past, a workaround when WV was absent in the browser, and that was to use the Microsoft owned Silverlight NPAPI browser plugin for both decryption+decoding; Silverlight has been deprecated by Microsoft and NPAPI plugins (except Adobe Flash) have been deprecated by all the major browser vendors, so using Silverlight in a browser as a WV fallback is pretty much a moot point; I am not subscribed to Spotify, so I can't be 100% sure it doesn't support Silverlight in Pale Moon (ergo New Moon); this chance is very bleak, if you ask me, though... 9. Of the rest of the "roytam1" browsers, excluding KM-Goanna and FxESR 45, only Serpent 52.9.0 and Serpent 55.0.0 were compiled with Widevine support, but, as stated previously, only if you are on Windows Vista SP2 or later; on XP, WV is disabled and doesn't show up inside about:plugins... (NB: Widevine on Serpent 55.0.0 on Windows Vista was initially non-functional (worked OK in Win7+), but this was rectified in https://github.com/roytam1/basilisk55/commit/cbc95b1 ; many thanks @roytam1 ) I wrote this analysis not only as an answer to your own query, but as a point of reference for other XP users... On XP, the only remedy I possibly see is trying to work things out with the last working version (49) of Google Chrome there; GC comes with its own version of patented decoders, and, AFAIK, has Widevine v1.4.8.903 inside; perhaps install an extension to fake a recent Chrome version to Spotify and see what comes out of it... Best of luck!

... I had explained this in fine detail in the past ; perhaps it was lost when the forum's database was corrupted back in June 1. First grab latest Polish language pack (for PaleMoon 28) from http://addons.palemoon.org/language-packs/ Do not install in NM28, just save to file (it should have an .xpi extension, filename=pl.xpi). 2. An .xpi file is just a renamed .zip file; if you have 7-zip installed, it can decompress .xpi files without issue; if not, rename the file to pl.zip and use your favourite archiver app to extract to a pl folder. 3. Open the folder and locate file install.rdf ; open that file in a proper text-editor (Notepad++, PSPad, etc.); if you don't have a proper text-editor installed (you should), use Window's notepad as a last resort... 4. Locate line 31 of that file; it should read: <em:maxVersion>28.0.*</em:maxVersion> 5. Change "28.0.*" to "28.1.*", save the change and close the file in your text-editor. { 5a. Optionally, you can also change line 12 to read: em:version="28.1.0" and then save the change to file } 6. Select all contents of folder pl (but not the actual folder itself) and re-zip them back to a pl.xpi file (you can also rename that to 28.1.0_pl.xpi, for telling apart from original download...) 7. Open latest NM28 (v28.1.0a1) and navigate to about:addons (addons manager); drag and drop file (28.1.0_)pl.xpi; it should offer you to install it; a browser restart would be needed... 8. For the LP to apply, you'd have to set in about:config general.useragent.locale;pl (followed by another browser restart). DISCLAIMER: The procedure outlined is just a hack; the localization may break with any future NM 28.1.x update, if new strings are added to the code by Moonchild devs for which no translated Polish strings are there in the installed pack; according to the extent of the breakage, some functions may be broken, or even the whole browser might be unable to start; in that case, start in safe mode, disable the language pack and restart in normal mode (en-US GUI). You should inquire about updated packs at the GitHub repo... @kitaro1 : That should also interest you! @roytam1: Maybe also pin this post to first page, because people seem to be unable to apply what is a simple procedure for you and me...

Hello there Since you appear to be a fellow Vista user, I decided to help and investigate... Two major issues for me: 1) I don't know any Polish, 2) (obviously) I'm not in Poland currently... I had to use a lot of Google Translate to decipher all these messages (in Polish) I was presented with and to be able to click the right on-screen buttons... I then had to find video content that wasn't geo-fenced (restricted to Polish IPs, only ); I think I settled for Ameryka-Marzen-Odcinek-12 I tried a variety of browsers on my Vista laptop, but to no avail; I suffered exactly what you reported, i.e. a black rectangle in the supposed place of their embedded player... I then kindly asked my sister to test that URL on her Firefox Quantum v61.0.2 (32-bit) copy on her Win7 SP1 64-bit laptop: she had to temporarily disable uBlock0 on that site, but, lo and behold, the programme started playing in an HTML5 player... After some further troubleshooting I did, I think I've solved the riddle: That (nasty!) Polish site performs User-Agent sniffing and simply doesn't like the Vista (NT 6.0) part of the UA, so they decline to load their player on Vista machines (didn't test, but I'm sure the same fate is reserved for XP, too, i.e. NT 5.x) The solution I chose was to apply a site-specific-UA-override (SSUAO) for "www.ipla.tv" to mimic Fx 62 (due imminently) on Win7 OS; in a "roytam1" browser (NM27/28, Serpent 52.9.0/55.0.0) open about:config and create a new string pref with name=general.useragent.override.www.ipla.tv value=Mozilla/5.0 (Windows NT 6.1; rv:62.0) Gecko/20100101 Firefox/62.0 restart browser, clear cookies for "www.ipla.tv" and reload VOD page; you are then presented with so you have to disable adblocker (ublock0 in my case) and reload ; after reloading, you have to literally sit in front of at least 3min worth of ads; if you change to another tab, the ads and time counter are paused and only resume if you focus back to that tab... Very nasty behaviour indeed Finally, after the ordeal ends, main video starts playing: The test above was conducted on a Windows Vista SP2 32-bit Home Premium laptop, browser was latest New Moon 27 offering (v27.9.1a1, 32-bit, 2018-08-24) with lav-dll-lite-mmx dlls put correctly in place...

... You are not to blame, but you simply misunderstood The green Verified button on the GitHub repository: has nothing to do with extension signing on AMO (addons.mozilla.org) (see here). The legacy (XUL) version of uBlock0 on GitHub is not signed, hence it couldn't be verified by Firefox for installation; in fact, if you navigate to the installation instructions for the XUL flavour, it is stated that:

You can easily change the name string of installed Java version to "Java 8 Update 181" with CCleaner: Tools Tab => Uninstall => Select "Java 8 Update 152" in the "Programs to Remove" column, then on the top right press the blue "Rename" button; but this will only change the name string (hence an aesthetic change), not the actual version string (for 8u181, it should be 8.0.1810.13)... [tested only in Vista SP2, YMMV with XP SP3]

According to FileHippo (Technical tab), it was June 12, 2018; same thing is suggested by the vendor themselves at: https://helpx.adobe.com/shockwave/release-note/release-notes-shockwave-12.html

Highly unlikely ... Slimjet uses Chromium's engine (webkit), in which every tab loads its own (content) process; you can inspect Slimjet's memory consumption by launching (SHIFT+ESC) its task manager; Slimjet comes with its own adblocker too, add to that various other addons you may have installed and the RAM goes up quickly... It is no secret that Chromium-based browsers achieve higher rendering speeds at the expense of your RAM; on the other hand, Mozilla based browsers, especially of the pre-Quantum type, use less memory (with the exact same tabs loaded) compared to Chromium browsers; this would be even lesser for Moonchild's browsers, where e10s (electrolysis) is by default either not supported (Pale Moon 27) or disabled (Pale Moon 28, Basilisk52, Basilisk55). Have you tried PM28XP yet (built on the same UXP platform like Serpent 52.9.0) ? I have been following this thread recently and not many other people have come forth with reports about "sluggishness" in FirefoxESR 52/Basilisk 52/Basilisk 55 in combination with MSE; only you and @heinoganda, both using Virtual Machines; it would be interesting to hear from someone not on an XP VM... The stable (release) channel is currently on version 61.0.1 (Firefox Quantum) and the new ESR channel is on version 60.1.0 (Firefox Quantum); 62.0 is the current version of the beta channel of Fx Quantum. ESR channels (usually) get a major version bump every 7 release cycles, e.g. FxESR 38 => FxESR 45 => FxESR 52. The next ESR channel after (the XP/Vista compatible) 52 would've been FxESR 59 (with Fx 52.8.x being the EOL release of ESR 52), but Mozilla shifted the next ESR major update to a Quantum 60.0 based one, hence FxESR 52 got an additional cycle's reprieve (FxESR 52.8.1 => FxESR 52.9.0) ... Same here; my Kaspersky Antivirus subscription ends in 3 months' time... FWIW, KAV behaves normally with referenced browsers (initial CPU increase when the browser is first launched and previous session restored, but afterwards things run smoothly; no sluggishness, apart from very "heavy" sites like facebook and instagram, which I practically never visit) ...

Thanks; we're already aware, thanks to @Vistapocalypse:

... Thankfully, a member of the Moonchild dev team has done that some 2.5 hours ago... #679

Thanks, but as I said this bug is present in all NM28 builds I tested over the last month; as for the build ID string, you, of course, should know better, as being the person compiling the builds, but I thought the string was unique to each build (and certainly different between the two architectures for the same source snapshot); of the files listed in your server (o.rthost.cf/palemoon) I haven't yet come across two different files with the same buildID ... Of course, that would be file "palemoon-28.0.0b4.win32-git-20180721-b4f748a7c-xpmod.7z"; what would be more important for me to know is whether you (or anyone else for that matter) are able to verify reported behaviour? No, in the end all of my initially composed message was submitted, it just would not get through in one go! I had to temporarily copy the content off the forum's editor to my local text editor (PSPad) and then, as said, post it in small installments... Another manifestation of the forum's software malfunctions is the fact, despite me having opted to "Notify me of replies", I wasn't notified by e-mail of the last two replies above this one (@siria's & @roytam1's), while previous replies in this thread were successfully announced via e-mail notifications...

I thought all the "about:" references were the culprit, however in the end they got through... Another suspect was the embedded imgur image link, or links native to the forum itself; however, the forum software errors sometimes do not follow a defined pattern and the full composed post just won't be submitted, for no apparent reason ; I had to do it by a real trial-and-error method, submitting single paragraphs (or even sentences), checking they went on-line and then editing post by adding another paragraph (or sentence), until my whole report was finally through... It was really a nerve endurance test...

I am running into a minor New Moon 28 bug, which has been persisting over several weeks; I can't tell how old it is, cause I started testing NM28 from v28.0.0a4; I was able to reproduce on a new clean profile, with no extensions added, using latest build 28.0.0b4 32-bit (buildID 20180720233208) STR In a new clean profile (happens in an old, "dirty" one, too), navigate to about:support; the "Application Basics" top section contains clickable links (in blue) to some internal (about:) pages; middle-clicking on all but one of these links (the "about:buildconfig" one) results in a blank (empty) new tab; so does right-clicking and selecting Open in a new tab, but left-clicking works as expected, opening the internal "about:" page in the same tab... I think this issue should be reported to Moonchild and be hopefully fixed; I do have a GitHub account myself, however, being on Vista, I can't run the official MC PM28 builds (Win7+) ; FWIW, Serpent 52.9.0, built on the same UXP platform, does not present this issue... [OT: I had a heck of a time trying to post this report, I did it literally line by line, as the forum software always responded with a Forbidden error message (must have received more than 20 of those...); I know this is a known situation, however it's getting worse to the point one can no longer post without being driven mad... ]

See also this I posted over at the Vista subforum...

It may well look as if Malwarebytes Anti-Exploit (MBAE) 1.12.1.90 be the last version to run on Windows Vista SP2; this was reported by a Vista user on their forum, several hours ago ; MBAE is a perpetual beta free software with all premium features turned ON for volunteers/testers; the new auto-update to v1.12.1.97 brought with it, alongside several serious issues with Chromium-based browsers on Win7+), loss of functionality on the Vista OS (XP too?), because of new functions missing in Vista's kernel32.dll Version 1.12.1.90 can be fetched navigating to vendor's official page here ; in the event that page changes, direct link to the setup is https://malwarebytes.box.com/s/hrxfh20wtbre7tfaimf56i5chlodia4z Special provision has to be taken not to trigger auto-update to the non-compatible 1.12.1.97 version, see: https://www.wilderssecurity.com/threads/malwarebytes-anti-exploit.354641/page-152#post-2770670 (courtesy of MSFN member @Sampei.Nihira)

Can you spot the oxymoron in the above statement with the following practice: IOW, you have excluded a browser process (FirefoxESR 52.9.0) from your Anti-Virus/Security Suite (MSE), which leaves you open for possible attacks while you browse/download (as an OS browser is the main app one accesses the web with and a perfect candidate vector for infection); I wouldn't do this myself, nor recommend it to others ; but, of course, you're the master of your own box ...

Hi . It appears the Tycho platform for Pale (New) Moon 27.x.x has been EOL'd, as per 5da550a So PM 27.9.4 will be (probably?) the last official stable (release) version on that platform (and the last to officially support Vista SP2 ). Since you were building New Moon 27.x.x not from the release branch 27.9_RelBranch but from the master branch, perhaps just recompile one final time, but you yourself update appVersion on the master branch to 27.9.5a1 (see c674a10) to make it more evident, beyond any doubt, that the code snapshot is some commits ahead of the last stable 27.9.4 release; just a humble suggestion for next weekend's eventual updates... I didn't have the slightest what TenFourFox is, so after searching I found out it is a fork of Mozilla Firefox for Power Macs that has significantly diverged from Mozilla code after the 45 ESR milestone; for transparency, are those changes the ones designated as M* and where exactly their details are to be found (somewhere inside https://github.com/classilla/tenfourfox perhaps?) ? Thanks for your ongoing hard work

According to this PAs.com comment : Electron framework requires Win7+ by definition ... and according to that thread, further code was removed by M$, hindering considerably stealth portabilisation of Skype 8 even on electron compatible OSes Nice find, many thanks!

The off-line windows 32-bit installer (file jre-8u181-windows-i586.exe) continues to function properly on this old Vista SP2 32-bit laptop; I suppose this is of no consolation to XP users of this thread, just reporting it as a FYI here; the GUI during installation (which itself took quite long, ca. 5min on this old, under-resourced, machine) was slightly redesigned to be of a more elongated rectangular shape; but it did include a link to the following Oracle article: Release Notice a message the XP users are unlikely to see, due to the installer being broken on that OS Regards

You do realise you can't/shouldn't stay put for ever on a specific browser code snapshot just for the sake of an extension, however valuable it might be for you . Pale Moon 28, at this stage of its development, is constantly evolving - it is expected that some things will break (including extensions) while other things (e.g. page rendering) and/or various bugs are being ironed out... In fact, even when PM28 reaches a stable/release status (early autumn 2018?), we don't expect full 100% compatibility with the Pale Moon 27 ecosystem ; this is due to huge changes in the underlying platform (Tycho [Mozilla 38] -> UXP [Mozilla 52]). I only made the jump from PM27 to NM28 last week and spent several days to tailor it according to my liking; some of the extensions that were working on 27 quit on 28, so upgrades/replacements had to be found; most of all, I mourned over the breakage of my favourite complete theme, FT Deep Dark v9.5.4, but then I moved on to a similar, but 28 compatible, one, Dark Moon 2.0.3 ... But I digress In what exact way does dTa! work badly? More importantly, what version have you got installed? Please see relevant PM forum thread: https://forum.palemoon.org/viewtopic.php?f=44&amp;t=19494 If still on 2.0.18.1, try upgrading to the stable 3.0 branch (i.e. v3.0.8): https://addons.mozilla.org/en-US/firefox/addon/downthemall/versions/?page=1#version-3.0.8 You can also try the nightly 3.0 branch (v3.0.9pre): https://code.downthemall.net/nightly/dta-3-0/ or even the nightly 3.1 branch (3.1.1pre): https://code.downthemall.net/nightly/trunk/ You need Moon Tester Tool Pale Moon extension to install above dTa! versions... (As a precaution when testing new things, always back up your NM profile first ) Regards OT: Nice to see the forum is usable again , after 3 days of serious issues...