Leaderboard

I'm working on the solution and the implementation to avoid similar malfunction in the future.

X64 version is possible

There's no need for addons though, in Pale Moon's case, you can set any user agent you want in about:config, you (or rather, Jaguarek in this case) just have to: 1. Type about:config in the address bar, press enter and confirm the warning. 2. Right click anywhere and from the menu choose New -> String 3. In the dialog box, add this as the preference name: general.useragent.override.discordapp.com 4. Set this: Mozilla/5.0 (Windows NT 6.1; rv:63.0) Gecko/20100101 Firefox/63.0 As the string value, then click OK. (You also can obviously set NT 6.0 instead of 6.1, but there are sadly a couple sites which refuse to work for whatever reason, if they detect NT version any lower than the one of Windows 7.)

I agree with it being pinned. It's a very useful resource. Does this contain all updates, or just those pertaining to post-SP2 & post-EOL? What exactly was added in terms of tweaks etc? I'd like to see a list before downloading and trying it out, especially as it gives a good idea as to why the archive is 3GB or so. Nice work however :D

Finally a snake is caught . Python37_WinXP_20181128_105126167.exe https://www114.zippyshare.com/v/FBBJz5vw/file.html Special thanks to Samuka since I stole his API implementation. Special thanks to FranceBB for making installer for me . I believe it will help Https proxy development too.

That had of course occurred to me! I think it's very unlikely that those XP users reporting problems on the Avast forums are all running with the POSReady hack, at least no-one seems to have ever mentioned it there, but it might be worth asking! I did try installing Avast without the POSReady hack registry entries, just in case the installer didn't think it was a Windows XP system or something, but that made no difference. You are quite right that one or more of the POSReady updates might be causing the problem though. I'm not about to uninstall them all to try to find out!

"Παρακαλώ"!

..."Muito obrigado" indeed for that!

Avast! people couldn't care less for XP die-hards even if they tried real hard to. That was the case with AVG, too. Up to it's takeover by Avast! (late 2016) they kept releasing definitions for AVG 2011 (the last version to really work seamlessly with XP SP3). Afterwards, they forced people (even those holding still-valid licences to the paid-for versions) to update to their "latest and greatest version", which purportedly still supported XP (but not really-really, obviously). That was when I moved on to old MSE v. 4.4.304.0, which I keep using with no regrets whatsoever. IMO, they're just wishing very hard we XP die-hards fall down the memory hole, the sooner, the better! Living is learning, isn't it?

That's pretty awesome stuff :3 anyhow... yeah it's still good a company does provide definition updates for older systems to keep them going (and for both people and businesses that's a good thing)

I'm the same person; I knew people working there and I used to talk to them, and be unofficially informed about the development in summer 2015 'till the very beginning of 2016. As a matter of fact, I still think that Avast 16 was one of the best UI and programme version. After that, I haven't been involved in anything and when a new management got the company the people I knew started to be less and less 'till now, the moment in which I'm not even a beta tester anymore (but I'll have the "sticker" beta on the latest stable version of the programme forever as a memory). A few pictures ("old-goodies", actually) from 2015, which seems like an eternity ago already:

Oh, one important thing. _socket.pyd ws2_32.dll inet_ntop inet_pton These are missing.

@FranceBB Didn't you used to work for Avast a few years ago (or am i thinking of a different individual that was around xpforums in 2015) ? While I don't particularly like Avast in general (after the CCleaner incident) I do appreciate that they will keep it updated

Yeah, I'm using Aeromoon, was even going to mention that but for some reason I didn't... at least now I know why I didn't have the speaker icon, thank you.

Mypal is the only usable one that has both a binary and portable option (important to me because I don't want IE as default browser), and works just fine for me, so I'll go with it! ^^

My FB cover photo

Yeah, that'd be pretty awesome too! Seconded. Thanks for providing all these contributions at no cost... I owe it to everyone keeping XP/Vista alive in these dark times ^^

Well done and thank you. Would you be able to port over the x64 version?

Since you're running 64-bit Vista, be sure to go to HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Internet Explorer\AdvancedOptions\CRYPTO and delete the 'OSVersion' values in the 'TLS1.1' and 'TLS1.2' keys (folders).

... 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 .

DAMN... this is awesome! Thanks:D

Whenever you became cognizant that software is not "no-strings-attached do-what-you-want-with-it freeware" but some sort of restricted-circulation donationware. If the author took the trouble to lay any rules, the author must have the means to enforce them or that's an exercise in futility. I don't want to convey the idea that bigmuscle's rules in the present case are specifically either nonsensical or arbitrary, what I meant to say is that rules generally may be fully nonsensical, arbitrary or otherwise preposterous, but once one accepts to abide by them one should be true to it. To do otherwise is sheer bad faith, not any type of misunderstanding.

Good to know. jaclaz I find it hard to believe you hadn't presumed it, way back when... Not at all. Rules are just that: rules. When one decides to use the software, one agrees to abide by them, no matter how nonsensical or arbitrary they may be.

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...

This is greatThis should be pinned here so it wouldn't go to the memory land

Holy win https://linustechtips.com/main/topic/1002853-windows-xp-pc-first-ram-slot-not-working/?tab=comments#comment-12031484 It got fixed

Windows Media Player 11 is not a must, but windows media 11 runtime (wmfdist11.exe, most recent for Windows XP) can be used without any problem even if an older Windows Media Player (9,10) is installed. This ensures that programs that are runtime-dependent on the latest windows media runtime display smoothly.

oleaut32.dll File Verson: 5.1.2600.7594 (ENU) CRC32: 97A44211 MD4: B3EB8646DDBDDF37D8880F29E477DAF6 MD5: F979C49B339660A6035D942E76A56409 SHA-1: 0CD70F58F7BA37C258DEDDD9F92E40C57EC1A827 SHA-256: A094CC487E4EB86D3114C2A25E1C7B91DA4CB271AE276F1BAD95AF064A96DF94

Any love for bk55 fanboy?

New build of basilisk/UXP for XP! Test binary: Win32 https://o.rths.cf/basilisk/basilisk52-g4.1.win32-git-20181201-d7bb17571-xpmod.7z Win64 https://o.rths.cf/basilisk/basilisk52-g4.1.win64-git-20181201-d7bb17571-xpmod.7z diff: https://o.rths.cf/basilisk/UXP-xp-gitdiff-20181110.7z PM28XP build: Win32 https://o.rths.cf/palemoon/palemoon-28.3.0a1.win32-git-20181201-d7bb17571-xpmod.7z Win64 https://o.rths.cf/palemoon/palemoon-28.3.0a1.win64-git-20181201-d7bb17571-xpmod.7z Official repo changes since my last build: - Remove remaining MOZ_GONK_MEDIACODEC code (513bf1b68) - Remove OMX_PLATFORM_GONK (4c8c14a71) - Merge pull request #879 from trav90/code-cleanup (083c6b7b9) - Remove VR hardware support. (7504ca8ab) - Remove VR Hardware input support (gamepad type) (2f954010c) - Update HSTS preload list (3eef7ab26) - [TychoAM] Give the second <hbox> an ID so it can be targeted in extensions.xul (fe11e14d3) - Revert "[PALEMOON] Sanitize - "Form and search history" sanitize also the Findbar text and history (Ctrl-Z)" (3e89a288d) - Merge pull request #886 from JustOff/PR_sanitize_findbar (b585dad9b) - Fix typo for Firefox compatmode prefs. (e2d0c96a9) - Merge branch 'master' of https://github.com/MoonchildProductions/UXP (1bf68529f) - Update GMP AUS URL (da447504d) - Issue #890 - Port cpp aboutRedirector to javascript (26f7e0ce3) - Issue #889 - Clean up the Pale Moon tree - Part 1a: Move abouthome to components (71737d61f) - Issue #889 - Clean up the Pale Moon tree - Part 1b: Move newtab to components (6acc5f912) - Issue #889 - Clean up the Pale Moon tree - Part 1c: Move pageinfo to components (a801955d6) - Issue #889 - Clean up the Pale Moon tree - Part 1d: Move sync to components (ac6c6be1c) - Issue #889 - Clean up the Pale Moon tree - Part 2a: Make moz.build consistent (7406a31bc) - Issue #889 - Clean up the Pale Moon tree - Part 2b: Make jar.mn consistent (2fa90d9b3) - Merge pull request #892 from binaryoutcast/pmTreeCleanup (d7bb17571) My changes since my last build: - update libaom to git rev 38a956221da4f1f56dad3a5862806a2a58715e20

Avast recognized recent Basilisk.exe from Roytam1 as malware by heuristic engine. I reported that to Avast as false positive.

You definitely need to invest in an image backup solution so you can revert your system when making a change that doesn't pan out. I would certainly recommend investing in a copy of Acronis Backup & Recovery software which will also provide a "try and decide" option to test unknown software or changes to your system.

Install the latest version available for XP of the K-Lite Codec Pack and install PotPlayer / MPC-HC. They are light and very powerful players, way better than VLC and they'll let you choose which renders to use (D3D9, Haali, MadVR, OpenCl) and the hardware acceleration (DXVA2-copyback, Intel QuickSync, NVCUID etc). They will also let you choose whether you want post-processing or not, like linear interpolation (which is like the true motion function on TVs), Denoise, Debanding and so on via frameserver (Avisynth) and many other options. PotPlayer and MPC-HC are way more tweakable than VLC and other player and with the K-Lite Codec Pack (which includes LAV Filters) you are good to go.

BTW, a bit late, but here are the November updates: Replaced Monthly Rollup with the new KB4467706 (located on the root directory of the repository) Added Security Only Update, KB4467700 (located in the folder "/Security Only (Post August 2018)") Replaced Internet Explorer Cumulative Update KB4466536 (located in the folder "/Security Only (Post August 2018)") Replaced .NET Framework Security and Quality with: -KB4459933 for .NET 2.0 SP2 (located in "/NET 2.0 SP2/Security and Quality Rollup") -KB4459945 for .NET 4.5.2 (located in "/NET 4.5.2/Security and Quality Rollup") -KB4459942 for .NET 4.6-4.6.1 (located in "/NET 4.6-4.6.1/Security and Quality Rollup") https://mega.nz/#F!txxRyLzC!1vBMGzMHiL864f3bl1Rj1w I think Microsoft already released this update for NT 6.0. Checkout KB4039648 on the Extras folder of the repository. They also released this update for Windows 7 in around 2015, if my mind serves me correct. What might change in the coming months is that MS may incorporate this update into the Monthly Rollups... we'll see. EDIT: Also forgot to add the new timezone update, KB4468323. It's now in the extras folder.

Oh yes.I just waked up and i see @Dibya ported the latest python on XP.Thank you soo much and everyone who tries to make XP live long

@someguy25 and @Mathwiz I bet you were looking forward to see this. It works fine on my machine and on Dibya's one. A big fat thank you to both Dibya and Samuel (Samuka).

Not sure if it's the right topic to post in but: According to this: https://www.ghacks.net/2018/11/20/running-windows-7-or-server-2008-you-will-need-this-patch/ Beginning in April next year, Microsoft will sign all updates for Server 2008 using SHA-2 instead of SHA-1, also they will release an update about a month earlier that adds SHA-2 compatibility to Server 2008. I just hope that this update will be compatible with Vista as well.

It is all explained (but not in a convincing fashion) in https://bugs.chromium.org/p/chromium/issues/detail?id=451733#c19 https://bugs.chromium.org/p/chromium/issues/detail?id=451733#c66 as a result of: https://bugs.chromium.org/p/chromium/issues/detail?id=426573 TL;DR : At the time that decision was made, Vista user base was very thin, compared to either the XP or Win7+ one, so for code refactoring/simplification they decided to merge the Vista codepath to the XP one; for Google, it is only numbers that count ; plus, that gave them a perfect opportunity to dump Vista altogether (along with XP) a whole one year prior to Vista SP2 becoming EOL by M$ (and close to 5 years before Vista's Server counterpart, Windows Server 2008 SP2, reaches EOL in Jan 2020 ). Once Google made the first move (dragging along with them all webkit-based browsers), many other software makers soon followed (they had a "nice" justification) in a trend that put Vista, 1.5 years after its official EOL, in the sorry state it is currently in... The only way to properly fix this is to first grab the source for Chromium 41 (-50?) - Chromium, yes, because Google Chrome itself is closed-source - and then revert https://chromium.googlesource.com/chromium/src.git/+/f29562d138f8c2222c6f24bddbd1a665ed036658 Some additional details in https://bugs.chromium.org/p/chromium/issues/detail?id=426573#c10 => https://codereview.chromium.org/755293003/diff/1/ui/base/win/shell.cc#newcode153 This isn't a task for the faint-hearted ... You would need a Win7+, 64-bit, machine with lots of RAM and a powerful multi-core CPU, MS Visual Studio 2013+, lots of time/patience and, of course, you should be well versed in that field (compiling open-source browsers in VS)... Two MSFN members come to mind, @roytam1 and @FranceBB, but I am unsure whether they're interested in compiling Google Chrome 49.0.2623.112 (last officially supported build on Vista) or 50.0.2661.102 (last Vista compatible, but not officially supported) with Aero-Glass enabled in Vista... I, as much as other Vista users, would be all up for this, even if it is realised purely as a challenge only, given that both Chrome 49+50 are quite outdated (in both security and performance aspects) when dealing with the web of 2019... Those two screenshots @VistaPAE posted in OP are not from his own system ... First one is taken from https://bugs.chromium.org/p/chromium/issues/detail?id=451733#c83 That person compiled Chromium 49.0.2579.0 64-bit with the aero-disabling commits reverted... So did this one (Chromium 45.0.2415.0 64-bit) : https://bugs.chromium.org/p/chromium/issues/detail?id=451733#c68 The second screenshot in the OP is taken from https://bugs.chromium.org/p/chromium/issues/detail?id=451733#c67 It emerged that this was actually a hoax/cheat ; the OS used to generate the shot is Win7 SP1 64-bit, disguised as Windows Vista (much like @WinClient5270 's guide found in his signature...) So now you know PS: For the history of it, the last build on Vista SP2 with Aero turned ON was Google Chrome 41.0.2243.0 in the dev channel; I keep a portable copy of it on my system just for fun, it's not used for normal browsing: Next build 41.0.2245.0 had Aero turned OFF in Vista...

If you want the actual Brinks-3D6H-SD3B.ISO, find it attached jaclaz Brinks-3D6H-SD3B.ISO

Not at all. It's a sad day. Every time a technology that gives one a hardcopy of what one buys dies is a time some of our collective freedom is lost. You must understand one has a book or a CD/DVD with a .pdf, or with music, or whatever, one owns that... one has a text into kindle or a music in iTunes one got nothing, and it can be taken from one anytime with little or no explanation and no money back, because one had previously given them the right to do it, when buying that. Ever heard of the memory hole?

There is no story about this one: