Leaderboard

I had been otherwise occupied all day long, so only recently skimmed through the numerous MSFN e-mail notifications on this subject... My input: Moonchild wrote: Really? English is not my mother tongue, but doesn't "should continue" imply they are currently able to run on Vista? This is the furthest thing from the truth! Lots of places inside their forum; I did a quick search and I came up, amongst others, with: https://forum.palemoon.org/viewtopic.php?f=1&t=15806 This was when Moebius/UXP-T1 was forked from a Mozilla Platform 53.0a1 code snapshot; that snapshot was already devoid of any residual XP/Vista OS support, as the good () guys over at Mozilla had already excised all relevant code... MC team did absolutely nothing to restore at least partial Vista support... https://forum.palemoon.org/viewtopic.php?p=114825#p114825 https://forum.palemoon.org/viewtopic.php?f=61&t=18253 (Basilisk and Windows Vista; I urge you to read the entire thread , but I've selected the following part:) Officially released Basilisk 55.x.x.x was never compatible with Vista; by pure luck (or negligence on their part), the compiler flags were such that lowering the subsystem value of the executables (6.1 -> 6.0) would allow for them to run on the Vista kernel, but OS integration was suboptimal; non-existing code targeting Vista resulted in WMF (and possibly other parts, e.g. EME, aka Widevine DRM plugin) being broken! https://forum.palemoon.org/viewtopic.php?p=132054#p132054 And when in the start of spring this year they ditched Moebius in favour of UXP-T2 (now just UXP), they forked a Mozilla 52 ESR platform with full XP+Vista support and what was the first thing they did? Meticulously removed all that support (as it's always easier to delete existing code than write new one...). Are we to believe that MC has just now had a sudden change of heart and he's willing to devote precious coding time to undoing the Vista massacre? I'm not that gullible... What's worse, in official Basilisk 52 + Pale Moon 28, they have amended their compiler flags/optimisations to fully ignore NT 6.0 (Vista/Server 2008); this has been already documented previously in this thread by esteemed member @WinClient5270, but it was also the result of my own tests weeks ago, when the first official builds were publicly released... Unfortunately, it's more than those... Inspecting latest (official) PaleMoon_unstable-28.0.0b1.en-US.win32[buildID=20180625093249] package with dependency walker, I am disheartened; focusing on just xul.dll module, this has calls to 6 missing functions in kernel32.dll GetCurrentProcessorNumberEx K32EnumProcessModules K32GetModuleFileNameExW K32GetProcessImageFileNameW K32GetProcessMemoryInfo K32QueryWorkingSet and to 2 missing functions in shell32.dll SHGetPropertyStoreForWindow SetCurrentProcessExplicitAppUserModelID Main executable (palemoon.exe) has lesser issues, of course I wasn't bothered to check other DLLs... Similar results are obtained with official Bk52 releases... And I emphasise again, it isn't only compilation configuration that needs to be changed to target Vista, it's actual browser code that needs to be rewritten to accommodate a fully functional, Vista compatible, application... Will Moonchild deliver? I think not... (and until PM 28 "stable" gets released in the final quarter of 2018, Vista user-base will have dropped even lower to merit his support considerations...) @WinClient5270, if memory serves right, I recollect you having registered previously in the Pale Moon forums (about an issue with Visual Studio 2013 dlls affecting PM 64-bit, that I had identified for you...); perhaps the best way to clear the FUD once and for all would be to post in the linked thread (by Jody) and ask plain and simple what MC's definitive decisions are; not his thoughts/intentions, but if he's actually determined to support Vista in PM28 (at least in the same level he supported Vista in PM27); please don't hesitate to convey some of my reservations/points I raised here ; full WMF+MSE support on both 32-bit/64-bit Vista architectures would be a must; UXP (unlike Tycho) is suitable for that, if they're willing to undo the damage they did to it concerning Vista; these days, noone wants a browser that won't play back embedded audio-visual content... Here's hoping...

Please note that with the release of Adobe Flash Player 30, SSE processors are no longer supported. Adobe Flash Player 29 (29.0.0.171) is the final version for SSE processors. I have moved the final SSE installers here: http://sdfox7.com/xp/sp3/EOL/flash_sse_29.0.0.171/

There was a new cumulative update for me from Build 17134.112 to 17134.137. 1) A new folder in 'C:\AeroGlass\symbols\dwmcore.pdb' needs to be created named as follows: D1149747277D9F7BA3C1C34E145203531 2) A new 'dwmcore.pdb' needs to be downloaded from the following link: http://msdl.microsoft.com/download/symbols/dwmcore.pdb/D1149747277D9F7BA3C1C34E145203531/dwmcore.pdb 3) The downloaded .BLOB file needs to be renamed 'dwmcore.pdb' and copied to the folder created in the first step. 4) Click the 'retry' button in the 'incompatibility' popup window and it should work.

Because he couldn't care less. Then again, we have @roytam1's PM mods already, which do work fine, and he's committed to keep 'em coming and to give 'em support... reason enough, IMO, for us all to ignore moonchild, instead of caring for what he thinks/wants/will actually do. My 2¢, of course.

Ok, so if you've installed the latest 1.5.8 version, then replaced the DWMGlass.dll with the beta version, & you don't see a Symbols sub-folder in your Aeroglass folder, then just create the folders yourself. Then follow the steps that sbkw1983 provided

Very detailed analysis VistaLover. I thought it was claimed to be incompatible on their end, but couldn't be 100%. Very confusing. I'll trust my memory from now on. :)

... not "may" ; Pale Moon 28 (currently at version 28.0.0a4) is built on the UXP platform, which by design does not support NT < 6.1 (i.e. minimum OS version required is Win7); as such, official Pale Moon 28 builds don't/won't run on Vista; the official Pale Moon unstable channel has switched, for some weeks now, to v28, incompatible with Vista... For historical purposes, the last Pale Moon unstable build to run on Vista was PaleMoon_unstable-27.9.1a1-git-20180503-g57f668c.en-US.win32, buildID=20180503064227 (I have kept a zipped copy...) If you are an unstable-channel user on VIsta, you are cautioned not to update any further (the update server doesn't check your current OS, so you'll end up with a non-running 28.0.0a4 update), but you are advised to switch to the stable channel, currently at v27.9.3; this will continue to receive mostly security (plus selected performance) updates for some more weeks, though a definite EOL date hasn't been yet announced... Vista users can try the New Moon (fork/rebrand) 28.0.0a4 builds by roytam1, to be found in the eponymous Windows XP forum thread...