VistaLover

No, he's right: Pale Moon (28) is the official browser by Moonchild Productions that targets Win7+; the fork maintained by @roytam1 is a yet unbranded one, with the (interim) name being New Moon, that adds (restores) XP and Vista compatibility to the browser; over the course of development, Pale Moon and New Moon (and certainly Basilisk and Serpent) have diverged even further, beyond the initial point of New Moon being just "Pale Moon for XP"; also, you're kindly asked to refer to the fork as New Moon only, because using the official branding (Pale Moon) when actually meaning the fork tends to aggravate the upstream developers (who then make angry appearances here and lash out at the fork maintainer and users...). I realise you're a new addition to the MSFN forums, I'd like to welcome you, too, but kindly advise you to get some facts straight first by reading existing threads... Regards

... A pain? In what way? Re-installing on top of an existing installation should leave the app's settings intact, AFAIAA; if the app is "properly" installed, then all (custom) settings are stored in the registry; the GUI of the app provides a very handy feature to export its settings as a .reg file, which can be imported (merged) later, after a new (re-)installation, to restore the player's settings like before: Another scenario is if you're using a "portable" installation, where you selected the setting "Store settings into .ini file": In that case, you only have to back-up that .ini file (in my case, it's PotPlayerMini.ini, but I'm on Vista...) found in the "installation" folder, to be put back in place after a new (re-)installation... So, me thinks you're just exaggerating... Best wishes

(The discussion topic here is horizontal scrolling via mousewheel ) Hi ; most members frequenting this thread are on Windows XP (or older OSes), with the exception of the few Vista users like me; not all of such members have ready access to Win7 or higher... I tested several Firefox versions (up-to-and-including v53) that would run in my system, I wasn't able to enable HS in any of them, via either of the following "mousewheel.with_*.action" prefs: mousewheel.with_control.action;4 mousewheel.with_shift.action;4 It turns out that HS was enabled in Firefox only as recently as v58.0: Horizontal Scrolling with Mouse wheel+ modifier key and, mind you, that was a bug originally opened in 2002 (!) ... Mercurial commit that implemented the fix: https://hg.mozilla.org/mozilla-central/rev/63b547bb4078 So, pray tell, which was "every other version of firefox" ? Actually, that's quite an interesting story... Horizontal scrolling had been implemented in a perfect way by MCP in the previous PM platform, Tycho, forked off Mozilla ESR 38; New Moon 27.9.x, currently maintained by @roytam1, is built on Tycho ; HS in Tycho can be enabled by setting one of the "mousewheel.with_*.action" prefs to a value of 4. HS in Tycho works on both pages and frames; to test it on a page, zoom the page content until a horizontal scroll bar appears in the bottom of the tab; keep the designated key pressed and by simply moving the mousewheel, that bar should move, too... To test on a frame, just load https://www.bing.com in a tab and then have the bookmarks/history sidebar displayed (e.g. ctrl+B); increase the sidebar's width to the right, so that a horizontal scroll bar appears in the bottom of the bing tab... When PM was ported from Tycho to UXP, that feature (HS) regressed : https://forum.palemoon.org/viewtopic.php?f=37&t=20119 => https://github.com/MoonchildProductions/UXP/issues/732 => https://github.com/MoonchildProductions/UXP/commit/f0e053a However, Moonchild's fix was only partial, in that HS works in PM/NM28 for pages only, not frames; relevant UXP bug is still open: https://github.com/MoonchildProductions/UXP/issues/1173 will have a look later to see if I can fix it or not What you can obviously do is try whether UXP bug 732 (linked to above) applies cleanly in Moebius; of course, it would be just as partial, i.e. only apply on pages... IDK whether Mozilla bug 143038 is a better approach to the issue at hand... FWIW, legacy extension "Shift + Scroll (Horizontal Scrolling)" is available via CAA ("caa:addon/shift-scroll", originally over at AMO ); not tested ...

CTR is still available outside of the CAA extension (which is where you obviously obtained that direct link from ) in the author's GitHub repository: https://github.com/Aris-t2/ClassicThemeRestorer/releases If you're using the official Basilisk application on Win7+, then the latest CTR_v1.7.8.2019.10.27 is recommended; if, OTOH, you're using Serpent 52.9.0/55.0.0, then CTR_v1.7.8 is the last (EoS'ed) version for Serpent; the add-ons manager (AOM) is now different between Bk and St (Bk now uses PM's AOM with no support for WEs, while St retains FxESR52's AOM), Aris is currently maintaining CTR for official Bk (and classic Waterfox), only...

Ciao @resistor83 ; first thing I needed to do was get acquainted with PEC e-mail, since it's not used over here ; the following two links proved helpful: https://en.wikipedia.org/wiki/Certified_email https://vademecumitalia.com/pec-what-is-it-why-should-you-need-a-pec-address-and-how-to-get-one/ Now, I would strongly advise you to implement TLS 1.1/1.2 on your machine, regardless; probably better use the newer MS update, as per @erpdude8 : I can't see any way it could harm your existing setup; BTW, you did not say anything regarding Windows Updates in your system (only official Vista SP2 ones, till Vista EOL?) ... You specifically asked about Microsoft Outlook (part of Microsoft Office Suite), but, again, as pointed out by @Vistapocalypse, you neglected to tell about the used version... I am using myself the native e-mail client under Vista, Windows Mail, which, AFAIK, uses IE9's internet settings - I just checked the headers in the source of a gmail e-mail I received recently and I can spot the following (some parts obscured for privacy): Received: from mail-yw1-fxx.google.com (mail-yw1-fxx.google.com [209.85.xxx.xx]) by MX-IN-05.xxxxxxxx.gr (8.15.2/8.15.2) with ESMTPS id x8TKAo60027571 (version=TLSv1.2 cipher=AES256-GCM-SHA384 bits=256 verify=NOT) so I believe I can receive e-mails over TLS 1.2; but, of course, as detailed in this thread, IE9 supports only a limited number of TLS 1.2 cypher suites... Another solution for you to try on Vista would be the latest supported version of Thunderbird (52.9.1?) ... As for Microsoft Outlook, @Vistapocalypse is probably right; versions 2007 and 2010 use the WinHTTP library to connect to servers; Windows applications using WinHTTP on WinOSes < 10 can't normally use TLS 1.1/1.2, even if these protocols are enabled system-wide in the SChannel library, because WinHTTP is hard-coded to use only TLS 1.0. Mom (!) Microsoft decided to not mitigate this under Windows Vista (and Windows Server 2008) SP2, but did so for its Win7+ children (!) - Thanks M$! https://support.microsoft.com/en-us/help/3140245/update-to-enable-tls-1-1-and-tls-1-2-as-default-secure-protocols-in-wi Installation of that update should be followed by manually creating some registry keys, as instructed in the KB article; most sadly, an equivalent Vista/WS2008 update was NEVER released ... Some relevant articles (but fixes applicable only in Win7+): https://jaapwesselius.com/2018/09/23/outlook-2010-disconnected-with-tls-1-2/ https://www.ryadel.com/en/enable-tls-1-1-1-2-windows-7-8-os-regedit-patch-download/ https://www.greengeeks.com/tutorials/article/how-to-enable-tls-1-1-and-1-2-in-outlook-windows-7/ Illuminating SO answer regarding Vista: (from https://stackoverflow.com/questions/49497058/ ) Regards.

... But you haven't answered in the question kindly asked by @roytam1: Have you tried a fresh New Moon 28.8.0a1 profile (with no extensions) and try gmail behaviour there? In your screenshot (where NM28 is run under Win7) I see you have installed uBlock Origin (legacy), Disconnect and NoScript; they are bound to conflict with each other - also bear in mind that NoScript is explicitly incompatible with Pale/New Moon and UXP based browsers, so it's better to be avoided! IMHO, your gmail issues arise from using too many/incompatible content/script blockers. Second, you were told earlier (I think in the original thread) that you are not to compare latest versions of browsers (latest Chrome and Chromium based forks, latest Firefox Quantum/Browser) with the older-Firefox based forks in terms of behaviour on heavily-scripted sites; Google and the rest of the gang (e.g Facebook) always target the latest browser versions on new era hardware and OSes (and it can be argued that browser vendors have to always catch up with Google and gang in order to retain compatibility with whatever alpha Javascript/CSS features they are implementing on their sites) ... You only have yourself to blame for this "great" problem of yours... New Moon is mainly targeted for XP (and for the few of us on Vista), where official PM won't run; thus, XP+Vista users of NM won't ever be faced with the problem you've created... As for NM+PM on Win7 and higher, what you report is to be expected - don't use both browsers, as, of course, they'll share the same profile location - but, and this is worse, New Moon isn't anymore just PM for XP; the codepaths have diverged (and this is even more pronounced in the case of Serpent52/Basilisk52); e.g., the NSS library used currently by MCP in official PM is different to the one used in NM, so expect profile corruption to occur when the same profile folder is being alternatively shared by the two browsers. If you still insist on using both NM28 and PM28 on the same computer (and windows account), then you should be using the official Pale Moon Portable package, http://www.palemoon.org/download.shtml#Portable_versions so that New Moon maintains a discrete profile and PM28-portable another discrete one... ======================================== To cure your self-inflicted issues: 1. Uninstall official PM28 2. Back-up the corrupted NM28 profile, in order to salvage what can be salvaged from there... 3. Delete the original, old (saved elsewhere), NM28 profile. 4. Make sure you have the latest NM28 version, launch it and you should be in a new fresh profile - then start anew with configuring it the way you like - but heed to step 5... 5. Avoid installing too many blockers - ublock0-legacy alone would suffice. 6. When you're finished configuring NM28, exit it. 7. "Install" the portable version of official PM28 - that version should always be launched via the palemoon-portable.exe launcher (you can create a desktop shortcut for it) and with NM28 exited.

@-SnooPY-: Python 2.7.17 has been recently released: https://www.python.org/downloads/release/python-2717/ So, whenever it's out, v2.7.18 will be the EoL/EoS Python 2.7 release...

... I think they themselves stopped calling it that way ; recently, I had the chance to view the "about" box of latest stable Mozilla Firefox v70.0.1 (in sister's Win7 SP1 laptop ) and was surprised to see it was now referred to as "Firefox Browser"; any bet what it'll be called come v85.0 (I guess it'll make it there, as they'll be increasing major version numbers each month soon...) ?

Many thanks, finally ... and apologies for pestering you all night with this, it's just an OCD of mine to not get along well with half-baked solutions... For the curious: try { fp.isGoanna = (prefs.getCharPref("browser.search.searchEnginesURL").match(/(palemoon|basilisk)/) != null); if(!fp.isGoanna) fp.isGoanna = (prefs.getCharPref("app.feedback.baseURL").indexOf("palemoon") > 0); } catch(e) {} Have a fine new week!

Thanks @siria ; at least the second and third referenced prefs "kill two birds with one stone" (both NM28 & recent St52) : services.sync.syncKeyHelpURL;http://www.palemoon.org/sync/keyhelp.shtml services.sync.addons.trustedSourceHostnames;addons.palemoon.org,addons.mozilla.org but, sadly, leave out Serpent 55/Moebius: services.sync.syncKeyHelpURL;https://services.mozilla.com/help/synckey services.sync.addons.trustedSourceHostnames;addons.mozilla.org New snippet try { fp.isGoanna = (prefs.getCharPref("browser.search.searchEnginesURL").indexOf("palemoon") > 0); if(!fp.isGoanna) fp.isGoanna = (prefs.getCharPref("app.feedback.baseURL").indexOf("palemoon") > 0); } catch(e) {} will probably miss current Serpent 52.9.0/UXP, browser.search.searchEnginesURL;https://addons.basilisk-browser.org/search-plugins/ and (because of @Mathwiz's PRs): app.feedback.baseURL;https://msfn.org/board/topic/177125-my-build-of-new-moon-temp-name-aka-pale-moon-fork-targetting-xp/?do=getNewComment ... unless "palemoon" = "pale-moon" If the JS .indexOf function uses REGEX, perhaps it should just search for "moon" ? FTR, existing snippet will catch Serpent55/Moebius, app.feedback.baseURL;https://forum.palemoon.org/viewforum.php?f=61 unless, of course, that URL is also changed via a future PR...

Many thanks indeed for your swift response and efforts ; ... but I'm not in immediate need of the feature implemented, nor in a state to test its successful implementation myself, as I lack access to a SOCKSv5 proxy server with mandatory authentication; @Mabeso is the one to properly test that build, if he's currently reading this, he's kindly invited to test and report back ! ... So, no need anymore to keep the META-INF directory ; and, since it's not obvious by the current filename, it was originally the foxyproxy_standard-4.6.5 flavour of the extension... This is done, AFAICS, in the code below: try { fp.isGoanna = (prefs.getCharPref("browser.search.searchEnginesURL").indexOf("palemoon") > 0); } catch(e) {} Apologies if I get this wrong (as said multiple times, I can't code myself ), but I expect the above code to NOT WORK in the cases of Serpent 52.9.0 (Goanna 4.x.x) and Serpent 55.0.0 (Goanna 4.0.x), because, St52 => (by default) : browser.search.searchEnginesURL;https://addons.basilisk-browser.org/search-plugins/ and St55 => (by default) : browser.search.searchEnginesURL;https://addons.mozilla.org/%LOCALE%/firefox/search-engines/

The FoxyProxy extension checks for fp.isGecko45 = this.vc.compare(this.appInfo.platformVersion, "45.0a1") >= 0; because rudimentary authentication (with login credentials) for SOCKSv5 proxy was finally implemented in Firefox Nightly 45.0a1 when Bugzilla #1200802 landed: Accept SOCKS credentials in proxyInfo object The above condition isn't met for UXP apps (NM28/St52) and St55, because they use the Goanna 4.x versioning; but because UXP[Goanna4.x] was forked from Mozilla[Gecko] 52 (> 45.0a1), #1200802 code exists in the UXP tree and thus, by applying the patch fp.isGecko45 = true; the requested feature now works (same logic applies to Moebius[Goanna4.0] forked from Mozilla[Gecko] 53 (> 45.0a1) ) ... NM27 builds on the Tycho platform; Tycho[Goanna3] was forked from Mozilla[Gecko] 38 (< 45.0a1), and so is AF, thus the fix introduced by #1200802 is absent in the Tycho code tree; hence the FP patch doesn't work there... If @roytam1 was to apply, somehow, the fix from #1200802 to Tycho, then the FoxyProxy "patch" would also work in NM27 - however, the diff introduced by #1200802 involves modifying 20 files, it's unclear (to me) whether it would apply cleanly to Tycho and whether, ultimately, would work... @roytam1, would you care to try and hopefully compile a test build? I'm sure @Mabeso would be more than happy to test... Best regards

Methinks the UOC Enforcer file (user.js) hasn't been correctly installed, as both directories depicted are not the main profile directories of either New Moon 27 nor FirefoxESR 45! Page 1 of this thread says: To easily locate your main browser profile folder, use the browser's about:support internal tab, from there "Application basics" => "Profile folder" => "Open folder" button... E.g. for FxESR 45 it should be located at: "C:\Documents and Settings\Tualatin\Application Data\Mozilla\Firefox\Profiles\e0afyh62.default" Regards

... I'm sorry to hear that ; I'm completely unfamiliar with KM, though... If you're using the KM-Goanna3 fork by @roytam1, perhaps try with a different version of GM; caa:addon/greasemonkey/versions suggests v3.11 is compatible with Fx 38+, on which Tycho+Goanna3 was forked; unless GM v3.9 is the absolute max version that can be installed in KM-Goanna3... It would appear the ViewTube userscript is incompatible with that old a GM version - maybe it could be possible to edit/patch the script to force-make it v3.9 compatible (???); ask around...

The above extension is installed as part of .NET Framework 3.5 SP1 : https://docs.microsoft.com/en-us/dotnet/framework/wpf/app-development/firefox-add-ons-to-support-net-application-deployment#net-framework-assistant-for-firefox It can't be uninstalled the normal way via about:addons; more below: https://support.microsoft.com/el-gr/help/963707/how-to-remove-the-net-framework-assistant-for-firefox

The extension's XPI file is hosted on GitHub which, as you might know already, is now owned by Microsoft; it is a relatively big file (for an extension that is ), so it's probably consuming a big chunk of GH's bandwidth with its downloads - a "valid" pretence for them to request its removal from a free repository - IOW, I don't trust M$ one bit ; fortunately, the extension is just a database, the legacy addons themselves are being hosted on Waterfox servers... Aren't you able to even run the SSE-only compile of New Moon 27? Not even the ia32 (no-SSE) compile? Because CAA installs and loads fine here in New Moon 27 (the standard, SSE2+, build)... As for the legacycollector.org site/service, the alphabetical index resides here ; please give the URL proper time to load fully (it's all on one scrollable page; I guess this is a poor web design choice on the part of the maintainer ). The database for this site is humangous, circa 15 GiB, so not quite sure at what extent it could be saved in the Internet Archive... Of course, individual legacy extension users like you and me have one month (?) to save (both locally and on the IA) those addons they're interested in... The admin of the site has also generated a compressed archive of the whole site (in .tar.xz format, circa 8.23 GiB) and made it available over the Bit Torrent network (but not for long), for people wishing to pick up the baton...

... I've hinted about this previously in this thread: So, for browsers not supporting the WebExtensions iteration of ViewTube (e.g. NM27/28 or FxESR 45), it is necessary to first install an XUL flavour of a userscript manager (like GMfPM) and then proceed with installing the userscript (*.user.js) flavour of ViewTube...

You win! I sure am ; I was planning to post a detailed new article in the Vista forum (when my spare time permitted), but since you couldn't wait, I didn't want to come off as giving you the cold shoulder... FTR, the setup file itself (mpas-fe.exe) used to be (until and including Sun Oct 20th) dual signed (both SHA1 & SHA2 digest algorithms); that file is comprised by four other files: MpSigStub.exe mpengine.dll mpasbase.vdm mpasdlta.vdm mpas-fe.exe v1.303.1946.0 released on Fri Oct 18th was the last one to be itself and all of its constituents dual signed - engine version in that file was 1.1.16400.2 (as said, dual signed); this was the last version of mpas-fe.exe (and, of course, mpam-fe.exe for MSE) installable on a Vista SP2 OS without SHA2 code-signing support present! Later that day (in my timezone), new version 1.305.17.0 was released (might've been another 1.305.x.x version I missed prior to that ); while file mpas-fe.exe was still at the time dual-signed (but I could only see the SHA1 sig then), to my great dismay I discovered that running the file would not update my WD defs ; to cut a long story short, and after at least an hour of troubleshooting (which included dependency walker, as I was misled by what M$ did to the XP users of MSE/WD), I realised that 1. The 1.305.x.x series introduced a new engine version, v1.1.16500.1 2. While I could see SHA1 sigs for files mpas-fe.exe, MpSigStub.exe, mpasbase.vdm, mpasdlta.vdm, I couldn't for the engine DLL file, mpengine.dll, so I assumed it was only SHA2 signed. In the past, I wasn't that worried about files only signed with SHA2, other than the fact I couldn't be 100% sure the file hadn't been tampered with... For executables, a prior update, KB2763674 , made it possible to run them (although, in retrospect, not a clever thing to do if one is unable to verify EXE's signature...). But in the case of WD (and MSE), the anti-malware application has to verify (via the OS) the updated engine and definitions files (contained in the downloaded mpas-fe.exe setup) for it to load them; not being able to verify mpengine.dll, WD remained stuck at defs v1.303.1946.0 (with engine v1.1.16400.2) Since I was not running Avast, I decided to install (latest) SHA2 code-signing support in my OS and retry with the 1.305.x.x mpas-fe.exe files; it WORKED! It wasn't until sometime during Sun, Oct 20th, that M$ posted some relevant details in their now "rebranded" Security intelligence page: Intelligence my... behind (!) ; make no mistake - you read right: they had already broken mpas-fe.exe on Vista SP2 since the evening (UTC+0300) of Fri 18th... FWIW, latest (1.305.941.0) mpas-fe.exe file is itself only SHA2 signed, files MpSigStub.exe + mpasbase.vdm are dual-signed and files mpengine.dll + mpasdlta.vdm only SHA2 signed (i.e. still a mess! ) It isn't I have blind faith in WD's efficacy these days, I have a paid-for full Internet Security Suite (Kaspersky) as my line of defence, WD is kept going for "legacy" reasons; KIS doesn't object to WD being enabled, nor did it manifest any adverse symptoms after the update to Vista 6003. Windows Update is busted in this machine since the first week of July 2019 (still at build .6002 then), when M$ reconfigured things; in any case, only WD (delta) definition updates were coming via WU until that time (I don't have M$ Office 2010); and, as expected, even after installing both KB4474419-v4 and KB4517134 (latest SSU for WS2008SP2), I still have to manually update WD... Regards

I had to install recently the standalone KB4474419v4 file to enable SHA-2 code signing support in my SP2 system; I can, too, confirm it comes with raising the build number to 6003:

Addition: The above procedure may only be relevant for those who have not yet posted in this new thread; once one posts here for the first time, and according to one's own forum preferences, a "Notify me of replies" switch button should be present to the far left of the "Submit Reply" button - in the bottom of your newly composed post - turned to ON by default...

@S75: Welcome to the MSFN forums First thing you should ask yourself is whether you actually expect any legacy (XUL) version of the Pushbullet extension to work today; this extension relies on third-party infrastructure (secure logins to their servers, etc.) and they may have blocked old "unsupported" versions of their addon, on old "unsupported" browsers, on old "unsupported" OSes (you get my drift...) from even connecting to their service (for "security" reasons, no doubt... ). The latest version 347 of their Firefox extension is still available, but - as expected - in WebExtensions format, not compatible with New Moon 27/28, but possibly compatible with FirefoxESR 52.9.1 and Serpent 52/55: https://addons.mozilla.org/en-US/firefox/addon/pushbullet/versions/ In the remote possibility any XUL Pushbullet version is still functional, then CAA extension caa:addon/pushbullet/versions reveals that the latest legacy version 316 dates from Dec 28th 2015, while the last "supposedly" NM27 compatible version 179[.1-signed] dates from Feb 22nd 2015 The Tycho platform (forked from FxESR 38) on which NM27 is built doesn't support Jetpack SDK legacy extensions, and that was a decision made at the time by the Moonchild team of developers; so you can't directly install such extensions in NM27, as the browser itself warns you about... The tool pointed to by @IntMD was developed to mitigate that imposed limitation (among several others), but it does not work universally on all types of JetPack SDK extensions - don't ask me why, I'm not an XUL extension developer. Force-installing an officially unsupported extension via the aid of the MTT always carries an inherent risk of browser profile corruption! Do keep this in mind and act accordingly (i.e. back up!). Second, if the unsupported extension is force-installed (in [TEST] mode) via said tool, you have no reassurance it will function as designed... I have run some tests on my old NM27 version here, I first downloaded to disk file pushbullet-179-fx.xpi, selected it via MTT (about:addons => Moon Tester Tool 1.2.0 => Options => Select file...) and it was still impossible to install I then tried to do the same with latest legacy version 316, which claims to support Fx 38.0a1 - 49.*; since Tycho is forked from FxESR 38, we stand a fair chance of it being NM27 compatible; following the same procedure, file pushbullet-316-an+fx.xpi did manage to install successfully - but I can't vow about its usability... OT: I wrote this post with NM27 that I seldom use now (UXP forks are mostly used here) and discovered the MSFN post editor has several minor issues (absent on UXP) - but is otherwise functional...

I don't think you can have HW gfx acceleration for in-browser HTML5 MP4 video (and certainly not HW video decoding) under XP (please someone chime in if you know otherwise ) ... HW video decoding when the Adobe Primetime CDM is being used as a h264 decoder is not possible, even on WinOSes where the WMF framework is present (Vista SP2+; the browser there has access to patented video decoders) and a compatible GPU is installed...

iF I understood correctly, the ViewTube userscript generates direct links to Youtube video clips, which are then fed to the WMP NPAPI browser plugin; the plugin then simply invokes an instance of WMP11 loaded with the YT clip to be played back; however, WMP11 lacks native support for the formats (container and codecs) employed by YT; have you noticed ? You need to have installed an SSE-only version of K-Lite CP (or other Codec Pack) to enable WMP11 to play (at least) MP4 (h264+aac) youtube clips; is that requirement met in your setup? 45 is earlier than 48, so it won't work. @Mathwiz: The userscript variety of ViewTube will install and work in FxESR 45 if an appropriate userscript manager (legacy) extension is already installed there; what won't work in FxESR 45 (but will in Fx 48) is the WebExtension flavour of ViewTube (simply because rudimentary WE support was first introduced in Fx 48 ). Actually, many years before that! https://web.archive.org/web/20170304053612/http://www.interoperabilitybridges.com/windows-media-player-firefox-plugin-download

With respect , the maintainer of that page has already warned visitors that the original functionality of the test page is now broken, for reasons outside his control: where by "test cases" he actually means the embedded HTML5 video clips... You should move to an alternate HTML5 video playback test site, e.g. https://tekeye.uk/html/html5-video-test-page http://www.bbc.co.uk/html5 http://web.archive.org/web/20190805082454/https://www.youtube.com/html5 (currently web.archive.org is DOWN for me... )

... And their download page states (both Free and Pro editions): ... Makes one think they have purposely excluded (omitted?) Windows Vista from their support list... It's only when one digs further and visits the dedicated product page, https://www.partitionwizard.com/free-partition-manager.html and then scrolls close to the bottom of it, to the Technical Specification section, that one finds Windows Vista is indeed supported... Given the recent debacle about the Comodo IceDragon browser, detailed in another thread, I've started to grow weary of the System Requirements software authors put up on their sites, especially in what concerns Windows XP and Vista; for the record, ICBB to install and verify true Vista support in MTPW...