VistaLover

... I can confirm that the most current release (v7.6.1) continues to be Vista SP2 compatible: Notepad2-mod hasn't been updated in a long while; its github repo is marked as archived, last commit was pushed on Aug 15, 2017. So it is safe to assume that this project has become "abandonware", with the latest official release v4.2.25.998 becoming in essence the very last (final) one (still compatible with Windows XP SP3 + Vista SP2): As you say, NotePad3 does not officially support the Vista OS (and the new owners, Rizonesoft, also dropped WinXP support): However, the last stable release v4.18.512.992 apparently runs fine on Vista SP2: Most sadly, the rosey story ends up here ; during the autumn, the dev team moved on to a new compiler with revised compiler settings/kernel optimisations so that the new branch 5 released builds (currently in the Release Candidate dev stage) are not capable of being launched under Vista, due to missing API calls: So, version 4.18.512.992 should be marked as the last Vista compatible one ; obviously, the maintainers themselves have no intention of restoring Vista support to the app, but it is my gut belief - without, that is, browsing the code itself - that, again, we may have to deal with an artificial Vista block; the app is open source, so hopefully the code could be recompiled targeting again the Vista OS... Here's hoping...

... I am curious as to why it was not suggested in this thread already, but why was the solution of running WinXP (and MMJB on it) in a Virtual Machine (e.g. free VirtualBox) hosted in one of @Roffen's recent hardware+OS boxes not given a thought? Perhaps one of the savvy good-hearted people here could hand-guide him (e.g. via TeamViewer) to set up the VM with XP in it? Also, it would be interesting to know the exact version of the audio software concerned; Wikipedia has a nice entry on Musicmatch Jukebox ; it's stated that Version 10 builds can still be found in oldapps ; after that, the product was acquired by Yahoo! (versions 10.1+)...

It can be retrieved by installing the Classic Add-ons Archive XUL extension (mentioned previously in this thread, as I recall ): https://github.com/JustOff/ca-archive/#compatibility-and-installation After successful installation, open "caa:addon/empty-cache-button/versions" in a tab; you would need latest "Version 2.7.1-signed.1-signed"; download the .xpi file to disk (storage of the file kindly provided by the Waterfox project) and manually install to New Moon 28 / Serpent 52.9.0 (both on the UXP platform) by dragging the file onto "about:addons"; you will be asked to restart browser to complete the installation; just a usage tip: be sure to close the caa:addon/* tab prior to restarting, else it would take quite a lot of time for the browser to reload post restart... Yes, Version 3.4 (WE format) does install and function correctly in latest Serpent 55.0.0/moebius, but does not install/work in Serpent 52.9.0/UXP, because it requires WebExtension APIs not present in[/backported to] the UXP platform... PS: if you like the "metro" style of the icons used in this WE version 3.4 of "empty-cache-button" (which, as said, can't be installed in either NM/Bk52), I have taken the liberty of "patching" the XUL version 2.7 (linked-to above, GLGPLv3 lic ) so as to include the "metro" icons (instead of the default "3D" ones); ergo empty_cache_button-2.8-pm27-28.xpi

... There was a recent identical thread over at the Vista subforum: Read my detailed reply here... or TL;DR: 1. Use Basilisk52[Serpent 52.9.0] with a SSUAO for Discord to pretend you're using FirefoxESR 60 on Win7+, or 2. Use FirefoxESR 52.9.0 and change its default UAO for Discord, with the aid of extensions, to the one of FxESR 60 (on Win7+). New Moon (27 or 28) won't work at all, because of no support for WebRTC (used by Discord's voice chat feature).

... Spoken too soon, am afraid... Latest New Moon 27 win32 build [Version: 27.9.1a1 (32-bit) (2018-12-14), buildID=20181214153010, package filename: palemoon-27.9.1a1.win32-git-20181215-c581f09b3-xpmod.7z] on Windows Vista SP2 32-bit. 1. First bug: When the browser sidebar is open (displaying Bookmarks in my case), the site header is shrunk to include a "hamburger" menu button on the far right; clicking that button does nothing in the case of NM27 [FWIW, when the sidebar is closed, the site header displays OK]... Sidebar visible: Sidebar hidden: 2. Second bug: All images+thumbnails on the site are displayed as blurry: Page Info => Multimedia Tab reveals that, e.g., the Discourse Dark style preview is loaded from https://imageproxy.openusercss.org/50x/https://github.com/StylishThemes/Discourse-Dark/raw/master/images/Atom-after.png which is a tiny 50x35 pic... When loading https://openusercss.org in FirefoxESR 52, the site is being rendered correctly: ... and in that case the Discourse Dark style preview is loaded from https://imageproxy.openusercss.org/540x/https://github.com/StylishThemes/Discourse-Dark/raw/master/images/Atom-after.png which is a medium sized 540x373 pic... So it appears that NM27 is unable to load and display the proper resolution thumbnail/picture ... @roytam1, would you be so kind as to investigate those two bugs? Would it be possible to backport Mozilla code (from Fx versions > 38ESR ) to, hopefully, fix them? As ever, much obliged for your on-going support

... This is, of course, off-topic (as this concerns XP), but it appears on Vista that feature is ON by default: [Provided merely as a FYI for others reading - I'm not on XP (any more), but still following this thread ... ]

... Yes, I know This issue was first reported last July in the official PM forum; according to Moonchild himself: Broken userstyles.org on Tycho was another reason that expedited the release of (stable) PM28 on the UXP platform... Thank you both for your suggestions ; this improves considerably over what I have been doing thus far and may possibly also cure the userstyles' (auto-)updating issue... E.g. for https://userstyles.org/styles/31267/global-dark-style-changes-everything-to-dark the direct URI to the userstyle (via either suggestion) is found to be : https://userstyles.org/styles/31267/global-dark-style-changes-everything-to-dark.css Then I can install it in Stylem 2.2.4 via the "Install from URLs..." feature (so no need to copy the entire CSS code and "Write New Style" ). However, the main flaw of this procedure, as already pointed out by the both of you, is: meaning the need for a (second) browser, able to render correctly the site (which could then be browsed/searched normally for userstyles) isn't alleviated... I'm still hopeful that this specific PM27 bug will be properly addressed in due course... Thanks, I am well aware; site always visited with uB0 ON, some personal "cosmetic" filters also added (to negate their endless plug for the android version of their adware/spyware version of WE Stylish): ! https://userstyles.org/ userstyles.org##.overlay_background userstyles.org##.android_button_banner userstyles.org###top_android_button userstyles.org##.android_button_button userstyles.org##.head userstyles.org##.body userstyles.org##.footsteps userstyles.org##.shadow userstyles.org##.x_button ||userstyles.org/ui/images/icons/close-icon.svg$image ||userstyles.org/ui/images/280x294.png$image userstyles.org##div.us-stylecard--short:nth-of-type(3) userstyles.org##div.us-stylecard--short:nth-of-type(5) userstyles.org##div.us-stylecard--short:nth-of-type(12) userstyles.org##.navigation The thing is, Stylem (a fork of [XUL] Stylish 2.0.7 made by a member of the official PM community) hasn't been updated in a while and has little support for userstyle "portals" other than the original one (userstyles.org, supported in Stylish); even that support is currently lagging, as Stylem can't install correctly configurable styles (e.g. YouTube DeepDark Classic , with the "Customize Settings" button); that issue has been properly reported here, but the developer hasn't yet acknowledged it or come up with a fix Also, due to the shady practices of SimilarWeb, current owners of userstyles.org, many style authors are switching over to other infrastructures, e.g. OpenUser.CSS (loads fine in NM27, BTW), and a new "format" of userstyle called usercss (which is configurable post-install); Stylem has 0 support for these ; this new "usercss" type of userstyle and the new "OUCSS" repo are fully supported in the userstyle manager called Stylus , but this is a WebExtension, not installable in New Moon 27/28 (and only certain versions of it can be installed - with some manifest.json modifications - in Basilisk52/UXP). OT: Yes I know, another long-winded post I am afraid, but hopefully with info useful to the MSFN community

... With GitHub now fully functionable in New Moon 27, the only deal-breaker for me currently is Tycho's inability to load userstyles.org , hence I am unable to install user styles from there with Stylem 2.2.4; if that were to be remedied , it would be a tremendous enhancement! FWIW, the workaround I have to currently apply is 1) first install the user style in one of the UXP browsers (or FxESR 52.9.0/Serpent 55.0.0), 2) copy its full CSS code and 3) manually install it [via "Write new style"] in NM27; some of these "locally" installed styles don't receive future updates (so the process above has to be repeated when an updated style has been released) ...

More info here: https://github.com/mtrojnar/stunnel/blob/master/INSTALL.W32 ... and I found some kind of a Russian fork, stunnel-msspi, but of the v5.50 32-bit released binaries : stunnel-5.50-msspi-0.135_windows-386.zip only the CLI (stunnel-msspi-cli.exe) would run in my Vista laptop, whereas the GUI (stunnel-msspi.exe) probably requires Win7+ (the EXE makes API call to K32getModuleFileNameExA not to be located in Vista's kernel32.dll ) ...

... Perhaps you inadvertently selected (Ctrl+I) the Italics font in the post's editor? (bolded capital I, next to bolded capital B, top left in the editor's "ribbon"?

Found it: Update application startup with proper error messages. (28 Jul 2015) Reverted 6 months later in Remove POSReady sanity check. (28 Jan 2016) ... with a more transparent commit title...

That's pretty much what I hinted about, thanks dencorso ; if the original code he forked contained, by default, parts that would enable it to compile and run on XP/Vista, he would meticulously excise those parts to make sure his fork is not compatible with said (older) OSes; you said he considers those parts as bloat (which can be indeed the case, but who really knows what's inside that person's head? ), I merely emphasised the result of him removing that "bloat": Another aspect which isn't clear in my previous comment is build-time-compiler-optimizations: targeting strictly Win7+ kernel when building his forked code, so that the officially released binaries be non-executable on XP/Vista... Moonchild et co. have a precedent on that: When they were releasing (between Nov 2017 and Mar 2018) official binaries of Basilisk 55 (on their now deprecated moebius platform), compiler opts were such that a simple lowering of the subsystem version string (from 6.1 to 6.0) in the EXE's headers would enable the Basilisk.exe binary to run on Vista (with only few flaws, namely disabled WMF features...). When apps (Basilisk 52 and Pale Moon 28) on the UXP platform started being officially released, the binaries were built under revised compiler optimisations; previous "hack" wouldn't now work, because at least 8 (new) API function calls were introduced in various app DLLs/EXEs that are not present inside Vista's versions of important system DLLs (kernel32.dll, user32.dll, psapi.dll etc)... If you ask me, that was not a coincidence As for adding code to their tree that is knowingly WinXP incompatible, the Moonchild team has already done that by switching over their ffvpx library to using FFmpeg 4.0+ source; to be fair though, it's safe to assume they didn't do it out of spite for eventual XP users on forks; they simply just don't support XP or Vista, so these OSes have been totally left out from any coding considerations on their part...

@mockingbird Thanks , but it was already posted by roytam1 himself, last Saturday I believe :

It would appear that the image hosting service (prntscr.com) doesn't like my current IP address issued by my ISP, or my ISP's IP pool in general ; by running my UK VPN service (which gives me a virtual UK IP address), I can access the screengrab URI directly and, as expected, the image shows up as embedded in the mentioned thread post... Go figure!

Thanks for checking Unfortunately, even after clearing cache+cookies, disabling uBlock Origin and restarting the browser, no go, still; here's how @WinClient5270's post displays at my end: Same goes for other browsers on my system ; and it makes no difference either whether I am logged-in to MSFN or not... Digging a bit deeper (Page Source), I find that the actual picture URI is https://image.prntscr.com/image/Xjj2ae1WSPO3sNi_B1jOTw.png but going to that I get a "403 Forbidden" nginx server error ??? Furthermore, https://image.prntscr.com/ does only generate a 500 Internal Server Error (nginx server); so is the problem on them (CDN server closest to my physical location) or still something with my network connection?

Can't comment on this, as I still haven't upgraded to it (Vista Home Premium SP2 x86 here.) Will probably do so tomorrow and let you know how it went . ... Well, the upgrade to the latest version of New Moon 28 [v28.3.0a1 (32-bit) (2018-11-30), buildID=20181130230404] on my Vista SP2 laptop was problem-free; here's a screengrab running a new/clean test profile: I then loaded my current (dirty) profile, no issues at all I understand this might not be actually helpful for you , at least it proves it's not a generalised problem for Vista users...

For whatever reason, I can't get the embedded screenshot to show up [New Moon 28.2.0a1 (32-bit) (2018-11-23)]; perhaps re-upload?

Please have a look over at the other Python [3.5] thread: A patch to enable pip has been provided...

... Then get yourself educated! ... and there's no need to "scream" with bold capitals In fact, you should care who that person is: He's the "right hand", so to speak - no insult intended to left-handed people , of Moonchild himself, an integral part of Moonchild Productions, the dev team behind the UXP platform and all the applications built on it: Pale Moon 28 [New Moon 28.x.xa1], Basilisk 52 [Serpent 52.9.0] and Matt A. Tobin's most recent offerings, Interlink [Mail News] and Borealis Navigator [BorealisXP]... Matt A. Tobin contributes a lot of code to the UXP repo, all this code will end up virtually unchanged inside @roytam1's XP/Vista compatible forks... He's infamous for harbouring a strong aversion to Windows XP (and Windows Vista) and being generally extremely hostile to fans/users of these OSes; and make no mistake: he'll go the extra mile to make sure his code is NOT compatible with said OSes, making Roy's hard work even harder ... So yes, the subject of "Matt Tobin" is sort of relevant to this thread... It seems my previous detailed reply to you has fallen onto deaf ears (or shut eyes, to be precise...); Roytam's task is not to rewrite the Pale Moon code committed by the Moonchild Productions team to accommodate a specific user's personal needs, he has only reverted those bits of code that prevent it from compiling and successfully running on XP+Vista OSes, period... Had you bothered to check my link to UPX PR #874, you would have noticed that Matt A. Tobin had nothing to do with the "tab-audio-indicator" code that you're implying and you feel strongly vexed about; this PR was submitted by @FranklinDM, another dev in their team... We haven't yet witnessed in this thread other NM28 users complaining about the issue affecting your setup(s), so, as of now, it appears to be only manifesting itself on your systems; worse yet, you haven't produced a list of system specifics and detailed reproduction steps so as to facilitate troubleshooting of your issue... Moonchild code targets "recent" Oses (Win7+) and "recent" hardware (e.g. SSE2+ capable CPU), so if your system is under-resourced it would not run NM28 properly... In closing, if "rebuild NM28 without the new feature" is what you actually want, then, again, I have provided the links for that: 1. Clone the UXP repo 2. Revert PR #874 commits 3. Apply latest UXP patch by Roytam1 4. Provided you have a suitable building environment set up (Win7SP1+ 64-bit with 12+GB RAM, Visual Studio 2015+,etc. ), build from modified source; I am certain that @roytam1 would be willing to guide you through, that is if his spare time permits him to... So, no more moaning on your side, please...

He's just lucky that GitHub have not imposed a "profanity" filter - simple as that FWIW, anyone with a GitHub account can report @mattatobin for using objectionable language...

..."Muito obrigado" indeed for that!

Hi all For starters, I have never used Discord (dedicated desktop app / browser version), so am completely unfamiliar with it ; that is why I never bothered to chime in with regards to @Jaguarek62's plee for help... BTW, it is bad netiquette to create exact duplicate posts for the same issue on different threads (first there , then here ). @dencorso, perhaps it would be better to transfer this recent discussion about the web edition of Discord in Vista to the standalone thread started by @Jaguarek62 ? Some points I want to make: I'm quite certain that these voice features are based on the WebRTC API; however, Pale Moon (ergo New Moon) has removed support for that one (by choice of the Moonchild dev team), so New Moon would never work for that discord functionality This feature is called Site-Specific-User-Agent-Override (SSUAO) ; old Firefox did have it enabled, but it was later crippled in favour of extensions ; besides Pale Moon (New Moon), other browsers with that feature ON are Basilisk (55/moebius + 52/UXP) and its fork Serpent 52.9.0, CyberFox 52.9.1 (can be patched to run on Vista SP2, but, sadly, is now a dead project) and SeaMonkey 2.49.4 (also EOL'ed). The reason Serpent 52.9.0 works for Discord Voice features is 1. It has native support for WebRTC 2. It has native support for SSUAO FWIW, Firefox ESR 52.9.0 [EOL'ed] does support WebRTC (but not SSUAO), so you could restore the Voice Features there by creating a General-User-Agent-Override (GUAO) with NT 6.1+ inside it and a recent (supported) Firefox version, e.g. general.useragent.override;Mozilla/5.0 (Windows NT 6.1; WOW64; rv:60.0) Gecko/20100101 Firefox/60.0 (60.0 is the current ESR branch); if you don't want to appear to all sites as FirefoxESR 60 on Win7 64-bit, then, as hinted, you'd have to use extensions in FxESR 52.9.0 (e.g. UAControl + User-Agent JS Fixer)... Regards

... Are you by any off-chance using a third party theme for New Moon 28? For the moment, these don't support the new native feature (tab audio icon) and would have to be updated in due time... Read this and the following comment... If you want to keep using your non-default theme, you can still utilise the new feature (to mute/unmute the audio in the tab) via the tab's context menu (second after "Reload tab"); or revert to the default theme (until your theme gets updated...). Should be palemoon-28.2.0a1.win32-git-20181124-b37e8f87c-xpmod.7z (buildID [x86] = 20181123223555) Can't comment on this, as I still haven't upgraded to it (Vista Home Premium SP2 x86 here.) Will probably do so tomorrow and let you know how it went .

Here's how it went: Pale Moon 27 (Tycho platform) did support Vista (and higher), but not XP; the New Moon 27 fork was created by @roytam1 to restore WinXP support; I can assure you that NM27 runs on Vista just as good (possibly better) as it does on WinXP... Then Moonchild Productions created Pale Moon 28, built on the UXP platform; UXP forked MozillaESR 52, which did support both XP+Vista; but Moonchild Productions removed both these OSes from their forked platform, so that UXP now supports Win7+. To the rescue came, again, @roytam1 , who restored support in UXP for BOTH WinXP and Vista; in fact, New Moon 28 and Serpent 52.9.0 are almost the only browser choices for Vista users nowadays, browsers which are under continued development and not EOL'd... And when have I disputed that? I merely said: Unless numerous other members (on XP/Vista/whatever) come forth here with the same affliction as yours, i.e. severe performance degradation of New Moon 28 as the result of the ported (from Australis) audio-tab-icon enhancement, let's, for the sake of argument, assume that, for the time being, what you're experiencing has to somehow do with your own setup(s). For the record, the last NM28 build without the feature was (x86): palemoon-28.2.0a1.win32-git-20181117-c94825c86-xpmod.7z and this feature/enhancement was introduced first in (x86): palemoon-28.2.0a1.win32-git-20181124-b37e8f87c-xpmod.7z (and is still present in latest build...); so people reading this should test and report back, if this is to be troubleshot... Calm down, please ! You have to understand first that the New Moon 28 builds are provided by @roytam1 as a pure courtesy to WinXP and Vista users and under no circumstances is he any part of the decision making with regards to browser features that get implemented (or not!); the entire browser code is being modified upstream by the Moonchild dev team, @roytam1 only intervenes to the extent of making that code successfully compile and run on XP+, NOTHING MORE... This has been explained before in this thread, but I suspect its sheer size has now become a deterrent for new members to read it... If you have a gripe about this feature, you should've directed your frustration over at Moonchild et company, not at Roy; but Moonchild only support "new" Win OSes (Win7+) and "new" hardware, so even that is a moot point... To re-iterate, you may indeed have a genuine issue on your setup, but: 1. It's wrong to generalise as if every NM28 user on every possible configuration has that same issue (and issue directives/guidelines as to what people should or shouldn't install in their browsers)... 2. Even if you're the only one with the problem, you'd have to provide ample details and reproduction steps to the current maintainer so he's in a position to first reproduce and, second, hopefully offer you some fixes for it... FYI, the code in the upstream repo that implemented this enhancement you detest is covered in UXP Pull Request #874: https://github.com/MoonchildProductions/UXP/pull/874 You'll find there all links to individual commits... ======================== OT: Maybe it's my own false sense, but to me you're coming off as a tad aggressive in your last two posts (of a total of 3); this isn't very becoming of "new" members, especially when you expect feedback/help from other members here - we are all volunteers and, of course, no one is perfect, but we do try our best to help (at least I do... ).

@NM-Newbie Personally, I haven't seen any degradation in the performance of New Moon 28 by the introduction of the audio-in-a-tab indicator code, which is a thing already present by default in Serpent 52.9.0 (and FirefoxESR 52.9.0); this feature was introduced by the Mozilla devs as part of the Australis GUI, to replicate Google Chrome's behaviour (and this is what Mozilla devs have kept doing over the last years: clone Chrome! ); since Pale Moon does not implement the Australis GUI, that feature was missing; it was brought to PM by popular demand, as many PM users asked for that in the official forum... Prior to this change, I, and several other users here, had been using in New Moon the Pale Moon extension Expose Noisy Tabs, which in fact shares almost the same code as the one introduced now natively in Pale/New Moon; so, if you had that addon installed in New Moon and have now updated to the latest build of it, you should disable/uninstall that addon, because; 1) it's now redundant, 2) may conflict with the native code and cause issues... If you don't have the ENT extension installed and, for whatever personal reason, would like to disable this new native feature (audio-in-a-tab indicator), then the code that implements this feature is fully controlled by a user pref; toggling that pref should make the related code not load when NM runs; the user pref is browser.tabs.showAudioPlayingIcon So, load about:config?filter=showAudio in a tab, toggle the pref (to false), restart New Moon and you should be good...