VistaLover

... You shouldn't be, had you read more closely what I've written in my previous post (Hint: It depends on what the user setting is for Preferences -> General -> When Pale Moon starts: )

Hi and welcome to MSFN forums What you describe isn't a bug to fix but intended behaviour implemented by the Mozilla devs and thus inherited in the FxESR52 based UXP platform (so present in upstream Pale Moon 28 and forked New Moon 28); you can read more about it in the following SU question: https://superuser.com/questions/1183272/re-enable-the-multiple-tabs-close-warning-in-firefox-50 If you have configured NM28 to save and restore previous tab session when launching, then the following Mozilla logic applies: If this is not implemented upstream, then implementing it only downstream (in NM28) will cause the official Pale Moon language packs (maintained and provided by the Pale Moon devs and community) to break when installed in New Moon 28; we don't want this (and have avoided this breakage several times during the past months by not implementing downstream-only patches that introduce new strings - it may be done in Serpent 52.9.0 for which no official language packs exist, but it's undesirable in New Moon) . As suggested, best route is using a tab-related extension! I'm recommending Duplicate in Tab Context Menu, retrievable via the Classic Add-ons Archive (CAA) extension: caa:addon/duplicate-in-tab-context-menu Regards

Thankfully, I'm not seeing this here, not yet anyway - however, things do look grim in the weeks to come: 1. Today is the release date of Firefox ESR v60.9.0, the last member of the 60esr branch: https://www.mozilla.org/en-US/firefox/60.9.0/releasenotes/ v60.9.0 will become EoS on Oct 22nd, when v68.2.0 will be released (there won't be a 60.10.0, of course) and existing 60.9.0esr users will be migrated to 68.2.0esr. https://wiki.mozilla.org/Release_Management/Calendar 2. UXP's (platform) support for GitHub is based on the fact the javascript code they (GitHub) are serving to Firefox ESR 60.x.x (which they'll support until it reaches EoS) is still compatible with UXP (and hence with browsers like New Moon 28 and Serpent 52.9.0 built on top of it...). 3. Serpent 52.9.0 doesn't have a native SSUAO for GitHub, but if the following prefs are at these posted values: general.useragent.compatMode.firefox;true (user set) general.useragent.compatMode.version;60.9 (default) I find that GitHub still works at the time of this writing: I also find that a SSUAO for GitHub of the following format: general.useragent.override.github.com;Mozilla/5.0 (Windows NT 6.0; rv:52.0) Goanna/4.4 Basilisk/52.9.0 also does the job if I set the previous pref to a value of 52.9 (Serpent 52.9.0 is really NOT Firefox 60.9 - this value was a setting implemented by MCP to achieve better compatibility with recent sites (which tend to use UA sniffing rather than browser feature set detection); actually, I feel better having the browser advertise itself as Fx 52.9 and then create as needed SSUAOs for those sites that break with that setting... When FxESR 68 becomes the only one available ESR branch, no doubt the sites implementing UA sniffing will raise the bar, so to speak, to demand Firefox 68.0 as a minimum Fx version; spoofing UXP browsers to Fx 68.9 in the state they are now may or may not work for those sites; if the sites update along the javascript+CSS code they serve to Fx 68.0, then that SSUAO hack won't work ; indeed, using a SSUAO for GitHub in Serpent 52.9.0 and making it pose as Firefox 68.0 (or 69.0) will give you grief, as GitHub will be broken . When we come to that point, we (using UXP browsers on XP/Vista) will be at the mercy of the Moonchild team; they'll have to successfully backport newer Javascript and CSS iterations to UXP (Pale Moon + Basilisk), so we can benefit, in turn, in the NM28 and St52 forks!

... My e-mail client on my 12-year-old Vista Home Premium SP2 32-bit laptop is, to this day, the default one provided by the OS, i.e. Windows Mail; while I rarely use today IE9 itself to browse the web, Windows Mail does use the IE9 engine to preview and display e-mails; without TLS 1.2 support present (in IE9), you risk having e-mails, certainly the ones in Rich Text (HTML) format, render broken, e.g. if in-line images are served exclusively over TLS 1.2! Using Windows Mail in 2019 might not be the smartest choice security-wise; but AFAIAA, very few current e-mail clients are being actively developed with Vista in mind; the one several of our XP friends have migrated to is the Interlink (a Win7+ client developed by notorious Matt A. Tobin) fork called MailNews, maintained by roytam1, the same dev who gives us New Moon 28 and Serpent 52.9.0/55.0.0!

... And if I added the figures right, that would be a sum total of HK$7447 (for those of us in the Eurozone , it's ca. 852 Euros; in Boris's UK, it's ca. 774 GBP; and in Trump's USA, make it ca. US$950); so, as I said some weeks ago when you announced this intended purchase, quite a small fortune it is! May you get every single cent out of this high-end hardware; congratulations for your new rig ; may you long enjoy it ! Greetings from 35 Celsius northern Greece

Bingo! ... Not to toot my own horn, of course, but I think I was the first (only?) person to have suggested the eventual connection of that directory to your reported issue; first here and then repeated here; so I feel slightly vindicated TBH . Anyhow, all's well that ends well Cheers

Basilisk is the upstream official browser application built on the UXP platform, developed and released by Moonchild Productions (supported officially under Win7+); Serpent is the generic name for an unbranded, unofficial, build of a Basilisk fork, in our case the fork (supported under WinXP+) maintained by our dear @roytam1 here in MSFN! Due to various development decisions made by both parties involved, the fork has started to diverge somewhat from the upstream application; some things/features removed by MCP (Tab Containers, WebExtensions support, etc.) have stayed in Serpent, so I can definitely say they aren't the same thing Hope it's all clear now!

... Skype for Web doesn't work in New Moon 28, even with a SSUAO; as advised previously, test either Serpent 52.9.0 or 55.0.0 Good to know! Cheers

There was no need to do that, because your original thread has already been migrated to the XP subforum, as per @Vistapocalypse's request! Windows XP forums: https://msfn.org/board/forum/34-windows-xp/ Your original thread (this one - migrated from the Vista subforum): Roblox is ending support for Windows Vista/XP => https://msfn.org/board/topic/179888-roblox-is-ending-support-for-windows-vistaxp/ Your newly started, duplicate, thread: Roblox is shortly ending support for Windows XP and Windows Vista => https://msfn.org/board/topic/179953-roblox-is-shortly-ending-support-for-windows-xp-and-windows-vista/ @dencorso, I am indeed sorry to trouble you, but I'm afraid additional housecleaning is in order!

... I was always intrigued by these Win7->WinVista transformation packs, although applying them appeared to me to be a tad over my skills; also was/am unsure of their impact on the whole OS performance. With Win7 reaching EoS in 5 months, they sort of look as moot to me now... My 2007 Toshiba laptop (originally with Vista 32-bit OEM) is now on its dying bed ; hardware is quite outdated compared to 2019 requirements (embedded gfx card doesn't even have h264 hardware decoding capabilities, so all video decoding is delegated to the CPU ) and despite some 2015 hardware upgrades (replacement of the original 128GiB HD with a 500GiB one, RAM augmented to 3GiB from 2GiB, repair of the screen etc.), the OS has become corrupted and sluggish; I am not prepared to invest more money on the machine/OS (also taking into consideration the miserable state of Vista with regards to current software support), the only realistic option would be to, sadly, move on to a recent laptop model with, no doubt, Win10 ()... Now, I know that a Win8[.1]->WinVista transformation pack does exist, because @WinClient5270 was using it on his machine, although I'm not sure a video tutorial has been created for it ; if a Win10->WinVista TP had been available by now, it would be an idea I would gladly entertain, as I simply and utterly loathe the abomination that is the Win10 interface! But then I wake up and realize one is not likely to appear, given the nature itself of Win10, "Windows As A Service", not a finished product, rather a constantly evolving "beta" OS (for which updates are massive and difficult to control; with every major OS update, the TP would probably break... ).

Thanks; it is essentially a SSUAO (UA the same as the one I'm using, for URL[site] https://web.skype.com/) issued via command line switches... Yes, Chrome and forks, without specialised extensions, rely on the proxy management wizard provided by the OS (the one under IE's Tools -> Internet Options -> Connections tab); the same is true, as I'm sure you're aware, about the certificate store/management... Never a Chromium fan myself, TBH...

... At the risk of sounding repetitive and/or tiring, I can confirm, once more, that Web Skype works as expected in my FirefoxESR 52.9.1 32-bit copy, under Vista SP2 32-bit: The date/time at the tray area reads Friday Aug 16th 2019, 17:39 EEST (= UTC+0300, BST+0200) No UA modifying extension used, but the two ".js file" method and the SSUAO reported here @Dave-H: As advised, please test either Serpent 55.0.0 or Serpent 52.9.0 (both by @roytam1) with a SSUAO (either mine or the one proposed by @Mathwiz), so you/we could gather additional info; if you experience the same Skype failures in Serpent (while for others, including myself, Serpent does work for web.skype.com), then we can safely assume the issue is not specific to FxESR 52; FWIW, the fact Google Chrome 49 does work (I suspect with a UA changing extension, no doubt!) excludes ISP/IP address related issues...

I don't have the exact answer to your query, but Wikipedia suggests the last version that would run in Windows 2000 is 4.11 (released on Feb 2012); then you could use trial-and-error with the winrar versions > 4.11 available in their ftp server: ftp://ftp.rarlab.com/rar/ to precisely locate the last versions compatible with XP RTM/XP SP1 ; be advised, old winrar versions have known unpatched (and exploitable) vulnerabilities, but I suspect this isn't high in your priorities... Regards (OT: What an exotic place to live in )

@Dave-H, @Mathwiz I conducted several tests with Firefox ESR 52.9.1 x86 (on Windows Vista SP2 x86) and I concluded that I had no issue whatsoever loggin' in and connecting to a skype account, starting from the web.skype.com URI First, loading the URL with my dirty profile, without a SSUAO: As expected, I get the "Browser not supported" message . As posted elsewhere in these forums, in my FxESR 52.9.1 copy I'm not using any extensions to apply SSUAOs, instead I have implemented the two .js files manual patch, to re-initialise the dormant relevant browser module. As such, in about:config I simply created the following string user pref: general.useragent.override.skype.com;Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/73.0.3683.86 Safari/537.36 BTW, @Mathwiz is right: Also, I did not have to create a SSUAO for the "*.live.com" domain, either... Just trying anew the web.skype.com URL, I am now presented with the login.live.com sign-in prompt: After the skype username and skype password have been (successively) successfully input, I had no issues connecting: I very much doubt this is an XP vs Vista case, my tests solidify my opinion that the predicament under which @Dave-H finds himself is probably caused by something at his end... I would restart router to get a new IP, restart the OS (this seems to be a cure-all ), restart browser, clear again browser cache and cookies; if all fails, then I would suggest starting with a new, clean, browser profile and testing there (obviously, at least one UA changing extension must be installed, or the .js files method applied). Often times, simply disabling content blockers and/or security extensions is not enough on its own... Also, has attention been paid to my previous tip: Cheers

I won't take an oath, but it's highly probable! Having grown up in Greece, I don't harbour such discriminatory preconceptions; in the grand scheme of geopolitical/historical things, Greece as a nation/state hasn't had a true ally (and you just have to simply study the last 300 yrs of European/global history to easily conclude that); has always been a pawn on the world's chessboard; the big powers of each era just manipulated Greece in a way to better suit their agendas, with Greece ending up being the party with the bigger losses... To return to the topic, using Windows 10 (possibly previous versions, too) and/or a Google product, some of your sensitive data are bound to be stored in some US-owned server, the NSA/FBI/CIA or any other federal agency would have little trouble accessing it if you somehow found yourself under their spotlight. Similarly, some of the Russian software may store sensitive user data to Russian servers and make them accessible to state agencies, that is if you somehow attracted their interest; of course, it is broadly known that this phenomenon (regime spying on internet users) is much more widespread with Chinese browsers, so one should always keep this in mind... I am not likening Trump's USA to Putin's Russia, certainly none of them to Jinping's China; but to me, "superpowers" are just that, more or less they'll have their way irrespective of my beliefs... And really, in the year 2019, do you still consider Russia as an adversary nation? In fact, I quite like Yandex.Browser and have even installed it in my sister's Win7 machine, instead of Google Chrome. The GUI is pleasing (also has a dark theme in the Win7 compatible version), has compatibility with both Opera and Google Store (for installing extensions), the English localisation is quite good and it's very easy to de-Russify (which isn't the case with the Chinese browsers). All in all, quite pleased with it (... and President Putin can freely read all of my MSFN posts, I don't mind ). About Torch browser: Latest offline installer is of version 69.0.0.1674, as posted; of course, I didn't try to run it, instead unpacked it like @win32 with 7-zip; the chromium binaries are deeply buried in the directory tree, after several more decompressions, I was finally able to test chrome.dll with Dependency Walker: As you can see, many missing functions in three implicitly dependent modules (kernel32.dll, shell32.dll, user32.dll), missing delay-load dependency modules, missing functions also in some of them; in other words, it won't run in Vista. Now, some previous versions forked on Chromium <=50, if were to be found, might actually run in Vista but, frankly, I'm not interested...

... And I'm so tired reading that same ol' mantra there: As if they (third party software developers) would give one nickel whether someone's setup is secure or not; what is the underlying truth inside this PR talk is that Microsoft themselves make it gradually impossible for third party software developers to target older OSes with their (M$'s) updated Windows SDKs! ... and it always comes down to that! Win7 will soon reach End of Extended Support, hence it'll also be "outdated and unsupported by Microsoft", with no more "security patches"; what is their stance on Win7? Security reasons my... behind!

"web.skype.com" logs in and works as expected in Serpent 52.9.0 using the following three "Chrome73 on Win10" SSUAOs: general.useragent.override.skype.com;Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/73.0.3683.86 Safari/537.36 general.useragent.override.skypeassets.com;Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/73.0.3683.86 Safari/537.36 general.useragent.override.live.com;Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/73.0.3163.100 Safari/537.36 In times of trouble: 1. Wait and re-try, if possible, at a later time; more often than not, I have found it to be some intermittent issue with their servers 2. Clear cache and skype related cookies, restart browser, wait a minute and re-try... 3. Clear any skype related folders in your browser's "<ProfileDir>\storage\default" directory, restart browser and re-try... Hope I've helped

Buone vacanze! ... I see ... and no worries, software debugging can certainly wait!

@Windows Vista Welcome to MSFN forums Yandex.Browser already covered in the first post of this thread: The link provided in that first post, as well as the link one gets when visiting https://browser.yandex.com/ with an XP/Vista User Agent string (*NT 5.x*/*NT 6.0*) is for a stub (on-line) installer! Official download link for off-line (Full/Standalone) installer, for version 17.4.1.1026: http://download.cdn.yandex.net/browser/update/17_4_1_1026_2644_w_s_m/yandex.exe 17.4.1.1026 is built on Chromium 57.0.2987.1026 source and is the last officially supported version on Vista; however, it is not the latest version that can be reliably run on Vista (but not XP); that one is version 17.6.0.1633, built on Chromium 58.0.3029.1633 source: Most sadly, it has proven impossible to locate a stub and/or full installer for that version, thankfully a third party portable (PAF) package has been archived in SourceForge (and is the one used here ): https://sourceforge.net/projects/thumbapps/files/Internet/Yandex%20Browser/YandexPortable_17.6.0.1633_on_Chrome_58.0.3029.1633.paf.exe/download Considering latest Yandex.Browser (19.6.1.153) is based on Chromium 74.0.3729.15 source, version 17.6.0.1633 should be considered deprecated/insecure by today's web standards; be that as it may, I find most websites render OK, with the exception, of course, of github.com (since they insist on always using the cutting edge version of Javascript code); if you spoof your UA to being FirefoxESR 60.x.x, even github works OK (but I suspect this hack will soon break, as FxESR60 will reach EoL towards the end of this month...). Cheers

... But you do have access to a Win10 machine, you've posted screenshots of it (running latest Chrome...) ; does latest PotPlayer work as intended there?

Cliqz is just a German Mozilla Firefox fork, based on release branch source; they follow upstream development with religious dedication and are keen on removing older versions from the web, for security reasons; yet their notion of privacy/security as implemented in their product can attract lots of criticism; infamous was the Cliqz test pilot experiment pushed in Germany in 2017 by Mozilla to several unsuspected Firefox users: https://www.zdnet.com/article/firefox-tests-cliqz-engine-which-slurps-user-browsing-data/ As you can imagine, latest (and only one offered) version is Quantum based, excluding any Vista compatibility ; Vista/XP are not supported since 2017, as per their statement: https://cliqz.com/en/support/support-ende-windows-xp-und-vista Use Fx ESR 52.9.0 with the "Cliqz extension for Firefox" ? Thanks, but NO thanks... As for lawlietfox, it's just as it is described in the SF link: ... So the developer (I think he's Chinese) has implemented basically PGO on top of vanilla Firefox, where: PGO = Profile Guided Optimization (more here ) ... All in all, nothing really exciting about either lawlietfox or Cliqz browsers, at least for the Vista community...

Many thanks for testing! (... but sorry for the negative result on XP ; would it even install at all?) ? I kind of lost you there When I visit https://www.kaspersky.com/free-antivirus I now get offered the same product as when visiting page: https://www.kaspersky.com/free-cloud-antivirus (this wasn't the case some weeks ago...) Both DOWNLOAD NOW buttons (red in the first URL, green in the second one) offer the same free product, labelled Kaspersky Security Cloud – Free (not KFA 2020, not SAAS), one ends up downloading a stub installer named ks3.020.0.14.1085aen_18801.exe Some localised Kaspersky sub-sites, e.g. the UK (and Greek) one, haven't yet updated, so on https://www.kaspersky.co.uk/free-antivirus you are still being offered Kaspersky Free (Antivirus), this is KFA2019 (19.0.0.1088aben, includes patches a+b, en-GB GUI), the stub installer downloaded is named just startup_14833.exe Where have you accessed KFA2020 ? ... and about SAAS; do you mean SaaS (Security as a Service) ? Which other free Kaspersky product is that? Thanks for any elaboration... In practice, mostly true, with two exceptions: 1. installing: Though hidden by Kaspersky Labs, one might find off-line installers, too (both official and RePacks); e.g. the link for KFA2018 provided by @pcalvert yields an off-line (full) installer. 2. activating: You only need activate (probably) once a year - I can't seem to find literature on off-line activation (was possible with older Kaspersky products, which used key files; might be still possible by using third party tools like KRT Club). 3. updating: See my post here for a way to update KAF2018/KAF2019 off-line Best regards

... Maybe not officially, but it has already been reported as running fine there: KFA2019 = v19.0.0.1088 As pointed out already, both KFA2018 & KFA2019 require .NET FW 4.0 on XP... FWIW, there isn't going to be a KFA2020 version, the free product has been rebranded as "Kaspersky Security Cloud - Free" recently: https://www.kaspersky.com/free-cloud-antivirus https://www.kaspersky.com/downloads/thank-you/try-free-cloud-antivirus It also doesn't support XP officially; any brave person here with a curiosity to test it on XP?

Oddly enough, the Cloudflare representative there (member @sandro MVP) suggested the following test: http://sitemeer.com/#o.rths.cf which claims that among European locations, o.rths.cf is being inaccessible from only the UK (Slough) CF node, with Italy (Arezzo) supposedly in the clear! It'll be a tough one to crack, for sure...

Many thanks for checking this out With all due respect, how is this going to contribute to current/future bug resolution on the UXP platform, that we also share here? 1. Moonchild won't accept bug reports if they came from unbranded forks (NM28+St52) users (if you ask me, he himself should test if present in his official builds, before dismissing those users, but all parties here realize this is never gonna happen!) 2. Effort has been taken recently in these forks (with initial requests by @TechnoRelic and other members, put in place by PRs kindly authored by @Mathwiz) to direct all issue reports here and, ultimately, to have them reviewed by the forks' maintainer, i.e. you 3. I'd argue that the majority of the fork(s) users do so because, either by choice or necessity, find themselves using an OS not sanctioned by the upstream devs (namely XP and Vista), and who (which is currently the case with me) don't have immediate/easy access to the officially sanctioned/supported OSes (Win7+). 4. Moonchild, in general, dislikes people posting issues directly in his GitHub issue tracker (apparently only reserved to a team of selected developers/"sidekicks"), instead prefers his users to post first to the official forum, and then he could "triage" them there as he sees fit . My humble opinion is that you should post the issue in the forums, with concrete proof it was diagnosed in an official build (so, no references or links to here); that way, Moonchild will have no justification to dismiss the bug report, even if it came from his worst enemy on this planet (which, obviously, you're not! ). I see only two other approaches: 1. Somehow push code yourself to your custom UXP branch to rectify reported issue(s) on your own. 2. This broader community is otherwise in need of a person/member that: a. Has a (whitelisted) official forum (forum.palemoon.org) account b. Optionally, has also a GitHub account c. Is a user of a UXP forked application, namely New Moon 28 and Serpent 52.9.0 d. Has easy access to an OS that supports the official counterpart applications, i.e. Pale Moon 28 and Basilisk 52.9.20xx.xx.xx) e. Is able to reproduce/confirm bugs (found initially in the forks) in the official builds. f. Is able to post a no-frills coherent report in the forums, and then let MCP et co. do the rest FWIW, last time I asked a favour from such a person, he kindly declined (and I have no right whatsoever to blame him...). Again, this is NOT about my petty bug (for which I've already found and posted a working fix); it's about the course of actions one is supposed to follow with regards to meaningful UXP bug report and hopeful resolution! Thanks again for your time reading this, thanks eternally for your efforts and binaries (... back now to deploying a strategy on how to combat a 42 Celsius heatwave pestering us for the next two days )