Jump to content
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble

MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically. 


Popular Content

Showing content with the highest reputation since 02/18/2019 in all areas

  1. 12 points
    You actually expect anyone here to take you seriously while you continue to maintain a condescending attitude toward roytam1 and everyone else in this community? You can't even speak of these things without lacing it with some ignorant derogatory language or FUD. Emphasis mine. I assume once again that users are intended to believe that "poor modification" is an acceptable definition of "restoring the pre-existing functionality that you intentionally chose to break?" Not one of us here cares one iota whether or not roytam1 has some useless eye-candy website or some fancy branding for his browser builds. What we care about is that they work and that he is very responsive to bug reports and quick to address other issues that may arise on the target platform(s). Yourself and "Moonchild Productions" could do with some lessons from what you find here. When the rest of the world leaves your precious Windows 7 and your "outdated" Mozilla forks, along with their "outdated" addons behind, where will you be? In the same boat with the rest of us. If you expect anyone here to take you seriously, you'd better learn to treat people here with respect whether you agree with them or not.
  2. 10 points
    GOOD NEWS EVERYONE! Thanks to @Osman Kovan for figuring out how to install Microsoft .NET Framework 4.8 on Windows Vista, I was able to use that same method to install Microsoft .NET Framework 4.6.2 Final on Windows Vista. I just extracted the setup .exe file with 7zip and ran the .MSI installation file contained within it, netfx_Full_x64.msi: After installing, I then tested ShareX Portable to see if it gave the same missing dependency errors that it does when running it with .NET Framework 4.8 Preview installed, and to my delight, it works just fine in Vista with 4.6.2 Final! Remembering what @VistaLover asked me to try with 4.6.2 Preview installed, I then decided to try the latest .NET Framework 4.6.x security rollup for Windows Server 2008 to see if it would patch .NET Framework 4.6.2 Final on Vista, and, lo and behold: It works! This means that .NET Framework 4.6.2 Final CAN be installed and patched on Windows Vista using @Osman Kovan's installation method, and then by downloading the .NET 4.6 patches for Server 2008 manually from the Microsoft Update Catalog. As such, Microsoft .NET Framework 4.6.2 Preview has been replaced with the final version on the list: Special thanks to @VistaLover, @Osman Kovan, and @artomberus for helping make this possible!
  3. 10 points
    Hmm.. let's see. "Not doing a good job" could easily be defined as "breaking things that already work." For example existing code support for older operating systems. Nice and simple. I fail to see how roytam's software is "abused," give that he is actually fixing things you or Moonchild have broken, on purpose. See above. No one claimed they are official. In fact the About dialog in these builds clearly states they are not. "Not doing a good job" again..? See above. I'd like to see some proof of this supposed "massive confusion." If there is any confusion, it must come from those who are clueless in the first place. You cannot fault roytam for users who are too ignorant to read the About dialog or to deal with any issues here, where the builds are linked, rather than going to you or to the official PaleMoon forum. Also I'd love to see even one example where you or Moonchild or anyone else in your "group" has "cleaned up a mess when something goes wrong" that addressed the first single issue that affected these older operating systems or users of the unofficial builds on these systems. It sounds more to me like you're just a butthurt jerk who is having a tantrum because someone is making your toy work in places where you don't want it to. If you don't like it, write your own closed source program and stop "abusing" Mozilla's existing code. Without Mozilla's existing code, which once again I will remind you already provides compatibility for the systems roytam is targeting, and which you have intentionally broken, your pet projects would be nonexistent.
  4. 9 points
    I have yet to see any evidence of these supposed "misguided people." We have only your word on the subject, which, given your general behavior and attitude, is not necessarily reputable. If one takes the source code for a given program (X) and re-compiles it targeting another platform (Y), how is it NOT "X for Y"? These programs are open source. If someone chooses to recompile them targeting a different platform, they have every right to do so, whether you like it or not. Good luck switching to "closed source," drop back by in a few years when you reach a closed-source state equivalent to the current open-source one you "leeched" from Mozilla. I've seen how you deal with these "poor ___ Linux builders" as you refer to them. You drop in, make demands and threats, create a general atmosphere of negativity that poisons the waters and turns everyone off, all the while hoping that no one stands up to your bullying. Most people eventually give in and give up, not willing to deal with your constant attacks. I'm afraid that modus operandi will not work here. I know for a fact that roytam's New Moon 27 builds are in fact named "New Moon" and not "Pale Moon" and do include a disclaimer on the About dialog that states the build is unofficial and specifically says not to request help on the official Pale Moon forum or otherwise. This thread is also mentioned. So what more do you expect? If the supposed "misguided people" you refer to are too ignorant to read and abide by these disclaimers then nothing else is going to stop them either. In the end all of these programs, including yours and those of Moonchild Productions, descend from Firefox or other Mozilla sources. The "chain of descent" is there, and it is not going away because someone changes a name or writes a disclaimer. Even if the name were changed, what happens when someone simply asks "what is this based on?" When the answer is given no one can control how others may use that piece of information to seek out the project's "upstreams." Even after all this ranting you still have not made any set of concrete "minimal acceptable changes" from your point of view. You keep changing them based on your level of annoyance each time you post. First it's change a name. Then it's full branding. Then "unofficial branding" is OK. Then it isn't. You noted at one point that mentions of the original names would be necessary for "profile compatibility reasons." Now, "ALL THE ORIGINAL NAMES MUST GO!" This is beyond ridiculous. Maybe roytam isn't a good graphics artist? I myself certainly wouldn't want to have to undertake the task of creating new "branding" that is worthy of the underlying code here. I'm no programmer, but I would take bets that changing the names and such would also create more headaches for roytam and his users in the fact that this could cause Addons and other associated applications to not recognize roy's builds, thereby forcing him or his users to manually modify every single Addon or associated application in order to get it working as it should. If my assumption of this is correct, what reasonable person with a life and better things to do who would choose this path? I'm sorry, but no truly serious user of these builds has any confusion whatsoever about what they are using. If the official installer(s) won't run on your non-supported platform and you had to get a build from here, that's self explanatory. And, if you're running on a supported platform where the official installer(s) work, that's self explanatory as well, and why would you come here in the first place? Covered this above, but once again - "If one takes the source code for a given program (X) and re-compiles it targeting another platform (Y), how is it NOT "X for Y"?" You "don't want to hear" these things because you don't like the fact that someone had the gall and took the time to compile your project for a different target platform that you disapprove of. That's the beauty of open source. Also once again - "Good luck switching to "closed source," drop back by in a few years when you reach a closed-source state equivalent to the current open-source one you "leeched" from Mozilla." See above about causing issues with Addons and associated applications. You claim that there is some "advantage" in the changes you are demanding when it seems more likely that this will only create more work for the developer. I see no advantage whatsoever to be gained by these projects from your suggestions, only that you just want things your way. I don't speak for roytam, but if I were in his shoes I would be all the less inclined to acquiesce to any of your demands simply based on your behavior. You have chosen to act in a condescending and demanding manner laced with threats to keep throwing roadblocks in the way of or create problems in any way possible for roytam's projects. On the other side, you create more annoyance for yourself by coming here and ranting about supposed "misguided users" who are troubling you, when it would be simpler (and probably better for your health) just to tell them off and go on about your day. You appear to thrive on creating a negative environment and beating dead horses. And, in the end, if you decide to try and make good on your threats then you will create more work for yourself in rewriting closed-source code to replace the open-source code you "borrowed" but don't like others "borrowing." Based on this and in the interest of civility I will state that I believe this "discussion" is never going anywhere. Please stop wasting everyone's time with your threats, condescension, and negative attitude. These will get you nothing here, except an end to OUR "diplomacy."
  5. 8 points
    Well it turns out that Microsoft .NET Framework 4.7.2 can also be installed on Windows Vista using the same installation method for 4.6.2 Final, and it can also be patched using the .NET 4.6 security updates for Server 2008! In addition, ShareX still works with this version installed, and no dependency errors are present: Now, I could not find an application that specifically required this version of .NET Framework, but it appears that ShareX is able to use it without any issues, in contrast to .NET Framework 4.8 Preview... As such, I have also added this version of .NET Framework to the list Also, this is irrelevant to .NET Framework, but Twitch Desktop App recently dropped support for Windows XP and Vista, so it has been removed from the list
  6. 8 points
    I also don't see how frank was rude at all, sounds like you could use an emotional support animal.
  7. 8 points
    I see no rudeness whatsoever in Frank's post. Yours, OTOH, is unnecessarily offensive. People nowadays are too oversensitive...
  8. 8 points
    I think we all understand that you are not Moonchild nor do you speak for MCP in this case. However you get grouped together with MCP here because you have been variously associated with them and apparently share the same condescending attitude toward XP (and Vista) users. This attitude is what turns everyone here off; I mean really, what do "you guys" care what operating system other people choose to use? Don't want to "support" it in your projects? Fine. Just don't break it on purpose, and don't act as if someone is committing a sin by using it on a "unapproved" platform. I fail to understand what bothers you so much about people asking about the XP builds based on this latest statement. Why not just tell them to "p*** off" as you put it and go on about your day? Now, back to the issue. If you wish to make a "reasonable" request, then do so in a "reasonable" and diplomatic manner. Coming in here and making demands and threats will get you nowhere. I'm willing to accept that your desire to have these "forked projects" disassociated from "Binary Outcast" is a "reasonable" request. However you need to lose the attitude first and foremost, and then make a clear policy on whether or not and how you wish to be credited or mentioned at all in any subsequent "forked" project. You have given conflicting statements on this depending on your attitude whenever you were posting. Do you want roytam to just change the names, icons and such? Do you want any stated credit such as "this project is forked from ___ " "created by ____"? Do you want to be "erased" entirely from the resulting fork? If roytam does these things you "request," then does that mean you will lose the condescending attitude and derogatory language in reference to these builds here and elsewhere? In your opinion; which most everyone here does not share. This is a nonstarter here. It doesn't matter how much "insight" you believe you have into this code; it works on these older platforms and since we have no other options it's a very good option, regardless of your opinion. Addressed most of this above I believe. However, you still seem to think that roytam can somehow exert mind control over those who choose to use his builds and keep them all from "wandering" into the wrong places for support. I'll wager that a good number of these people who are supposedly causing you problems are trolling, especially given your attitude about the builds and since you seem to be very easily triggered by anyone who mentions XP. Since you don't distribute these builds from your site, and most likely one must visit here in the first place in order to get the links for the builds, I find it strange that any serious user doing as such would not "stop here" first for help. They seem to be purposely seeking you out rather than sincerely needing help; and if this is the case, no one here can do anything about that. What's not "sufficient" here? This forum has been around for a long time and has hosted the support for many projects. I'd rather see a developer dedicated to his or her project rather than dedicated to extraneous "infrastructure." Nothing wrong with having "infrastructure;" mind you, but in the end it is secondary to the project itself. roytam has enough to keep him busy with a $dayjob and building his various browsers, and since he has no help in doing so it's not reasonable to expect him to spend time on a website or otherwise.
  9. 8 points
    LOL, couldn't help drafting such a disclaimer novel ;-P "For any help, support and discussion of roytam1 browsers, the best place is here: (link to NewMoon topic in msfn) Attention: Do not under any circumstances bother the PaleMoon team, especially Moonchild and Matt A. Tobin, with anything related to this forked browser, to anything XP-related, or mention any of roytam1 browser builds in the Pale Moon forum. They intentionally removed all XP-support for their products a long time ago, and do NOT tolerate any longer to be bothered by people using forked builds, especially not forks with restored XP support. Only discussion of their own original builds is allowed there. They have very STRICTLY declared this multiple times, in their own forum and also in the MSFN forum. So, please, abide by their request and go to MSFN only for support."
  10. 7 points
    alright it works. new Saturday binaries will work with 1.3 compat mode.
  11. 7 points
    Adobe Flash Player has been released today (confirmed working with Windows XP SP3/Windows XP x64 SP2) Internet Explorer ActiveX: http://fpdownload.adobe.com/get/flashplayer/pdc/ Mozilla Firefox NPAPI (also for Opera Presto/Google Chrome 44 and earlier): http://fpdownload.adobe.com/get/flashplayer/pdc/ Google Chrome 45 through 49 PPAPI: http://fpdownload.adobe.com/get/flashplayer/pdc/
  12. 7 points
    Not in my opinion. Although the more paranoid may eschew it, I do believe the more browser alternatives we have, the merrier! In fact, to me it's clear that day-to -day use requires just a decently working browser and, preferably, also a not-too-paranoid real-time antivirus. All the rest can be done without any need to use the very latest version of whatever program one must use. So Chrome 360 actually is a welcome gust of much needed fresh air into our already very claustrophobic EoS-is-not-EoL situation. Long Live XP!
  13. 7 points
    An interesting little change I noticed in the April 2019 update rollup: For those that didn't notice, since 2009 with the release of SP2, Windows Vista's build number has been 6.0.6002 (while SP1 was build 6001, and RTM 6000). However, with the new rollup, Vista's build number has been changed to build 6.0.6003. At first I wondered if this was an error/discrepancy on MS's part, but turns out the change was intentional, according to this article: https://support.microsoft.com/en-us/help/4495374/build-number-changing-to-6003-in-windows-server-2008 Just an interesting little thing I thought I'd point out This change doesn't seem to affect functionality of anything though (at least not that I'm aware of), which is good.
  14. 7 points
    It's finally fixed. After almost a year of a major bug that prevented me from shipping, I finally got a working build! Expect 2.2 in the coming days, possibly even tonight.
  15. 7 points
    I actually had an "extended discussion" with Moonchild some time back and attempted to point out just how illogical his position was in regard to older OS'es. It of course fell on deaf ears and he ended the discussion without even attempting to answer any of my points. I tried to get across to him just how irrational it was to be committed to preserving an older "browser interface/UI" while at the same time being determined to discard support for any older operating system as soon as possible. With one hand he pushes the "latest and greatest" and insists people should "upgrade" and not use "outdated" operating systems; and with the other hand he promotes an "outdated" browser interface now built on "outdated" code and now using "outdated" addons (in the eyes of the same people who push similar "latest and greatest" rubbish), purposely breaking the already existing support for older systems that was already in place. How one can contort themselves into such a strange position and consider themselves as having a reasonable standpoint on the issue is beyond me. When PaleMoon eventually starts bleeding off its users who subscribe to the flawed logic of "latest and greatest"; or when those remaining are left without options for addon/plugin compatibility and compatibility with the "modern" web, then I've got a feeling those of us here will have the last laugh, and can tell Moonchild and company "Welcome to the party, pal!"
  16. 6 points
    ... And despite all recent incidents involving Mr. Matt A. Tobin and Moonchild Productions in general, there still exist people who post in the official Pale Moon forums questions related to Feodor2's MyPal and @roytam1's New Moon forks: https://forum.palemoon.org/viewtopic.php?f=4&t=22110 These "people" are only doing a disservice to the XP and Vista communities benefiting from the continued existence of these forks and they must be stopped from continuing such an infantile and foolish behaviour; the only unwanted effect they'll cause is more aggravation for the MCP devs, more hostility towards the maintainers of the forks and their users! Who in his/her right mind would go to the official Pale Moon community (devs+users) forum and query about third-party "unsupported" forks running on OSes that the mere mention of their names would cause those people to throw a hissy fit? Please, anyone here with a PM forum account (I know several exist) contact that @DJboutit individual and try to talk some sense into him/her . We can't risk any additional animosity from the upstream devs !
  17. 6 points
    New build of Serpent/UXP for XP! Test binary: Win32 https://o.rths.cf/basilisk/basilisk52-g4.2.win32-git-20190511-1b5c261b8-xpmod.7z Win64 https://o.rths.cf/basilisk/basilisk52-g4.2.win64-git-20190511-1b5c261b8-xpmod.7z source code that is comparable to my current working tree is available here: https://github.com/roytam1/UXP/commits/custom NM28XP build: Win32 https://o.rths.cf/palemoon/palemoon-28.6.0a1.win32-git-20190511-1b5c261b8-xpmod.7z Win64 https://o.rths.cf/palemoon/palemoon-28.6.0a1.win64-git-20190511-1b5c261b8-xpmod.7z Official repo changes since my last build: - Update Readability from mozilla-central release branch (FF 66.0.3). Tag #361. (ccc436346) - Update surrounding code for new Readerable module. Tag #361. (945b03265) - Replace explicit pref observer with lazy preference getters. Tag #361. (952e65590) - Fix parse node limit preference. Tag #361. (2db53003e) - Bug 1399616 - add WP emoji styling to reader mode. (742f5aa24) - Bug 1422680 - simplify aboutReader.css font-size classes using CSS variables r=Gijs (0612246b0) - Bug 1151735 - Hide font panel when text is being selected r=Gijs (b430def77) - Bug 1429442 - Buttons in "type control" popup in reader mode should have tooltips r=Gijs,MarcoZ (5c350eebc) - De-unify accessibility build on Mac. (758663e88) - Merge pull request #1075 from adeshkp/deunify-accessible-build-2 (c40086cfa) - Update icon to the new and improved branding. (aa4055cb4) - Don't shrink the tab bar in customize mode (6458c3464) - backport m-c 1510114: Fix Use-After-Free in the HTML5 Parser (4ed4303dd) - Merge pull request #1077 from g4jc/cve_2018_18500 (d0f1f53e5) - Merge pull request #1078 from Lootyhoof/issue-1072 (12d23fb00) - Merge pull request #1080 from Ascrod/readerview (d0b65e8b3) - Issue #1082 - Restore a getBoolPref global shim in utilityOverlay.js for Extension compatibility (fc937d1ee) - Issue #1083 - Deprecate FUEL extension helper javascript library (5d119ce85) - Issue #1081 - Restore "release notes" item in the help menu (95607bd72) - Issue #968 - Preload the permissions manager with permissions file (1b5c261b8)
  18. 6 points
    So much for the "more constructive approach." I had a feeling this was insincere. roytam1 has no control over the actions of those who decide to use his XP-compatible builds. Even if he were to change names, remove references, yada yada yada. there could still be "ignorant" users (or even troublemakers just trolling) who will keep going to the wrong places for support or to ask questions. How hard is it to say "I don't support those builds" and link them here? Much easier than ranting there, ranting here, and rewriting a bunch of code.
  19. 6 points
    New build of Serpent/UXP for XP! Test binary: Win32 https://o.rths.cf/basilisk/basilisk52-g4.1.win32-git-20190427-3424afcca-xpmod.7z Win64 https://o.rths.cf/basilisk/basilisk52-g4.1.win64-git-20190427-3424afcca-xpmod.7z source code that is comparable to my current working tree is available here: https://github.com/roytam1/UXP/commits/custom NM28XP build: Win32 https://o.rths.cf/palemoon/palemoon-28.5.0a2.win32-git-20190427-3424afcca-xpmod.7z Win64 https://o.rths.cf/palemoon/palemoon-28.5.0a2.win64-git-20190427-3424afcca-xpmod.7z Official repo changes since my last build: - Issue #991 Part 1: Pale Moon (9a37ab727) - Issue #991 Part 2: Basilisk (759132691) - Issue #991 Part 3: Devtools (609a7215e) - Issue #991 Part 4: Network and URILoader (c7796280a) - Issue #991 Part 5: DOM and layout (1d0af8b59) - Issue #991 Part 6: Services (2d3b7717a) - Issue #991 Part 7: Toolkit Components (714e9c907) - Issue #991 Part 8: Toolkit everything else (8757548a3) - Pref try/catch block fixup. Tag #991. (40fc72376) - Merge branch 'master' into default-pref (af7e140d4) - Remove unused try/catch block. Tag #991. (21b4cb27c) - Remove unused parameter from call (b73287811) - Stop building /accessible unified and fix deprot. (32577bdb3) - Merge pull request #1041 from Ascrod/default-pref (e0116ac2b) - Handle URL token in a closer way to the CSS3 spec (d9137b4b7) - Remove geo-specific search engine default preferences. Tag #245. (c78cd6fb9) - Remove geoip lookup for search engine defaults. Tag #245. (60e283715) - Remove browser.search.region usage. Tag #245. (a3a34dad1) - Merge pull request #1047 from JustOff/PR_css3_url_token (550d87388) - Version bump (bccf86a10) - Fix variable used before being declared in UpdateUtils.jsm (bca1943ca) - [PHOENIX] Fix missing default from lastSync in browser-syncui.js in Pale Moon and replace the tryblock in Basilisk (5d02c2207) - Remove SecurityUI telemetry. (b10712de8) - Issue #1049 - Show sync status via label of sync-button (ccd86d8c0) - Merge pull request #1045 from ThosRTanner/patch-1 (864f1cfdb) - Update platform version to reflect major changes in platform. (33ebc885e) - Merge branch 'master' of https://github.com/MoonchildProductions/UXP (1d7664d3a) - Update Twemoji Mozilla COLR font to 0.4.0 (TweMoji v11.4.0) (7d61305b0) - Merge pull request #1051 from adeshkp/remove-telemetry-security_ui (8bd7da130) - Merge pull request #1048 from Ascrod/geodefaults (228e55129) - Remove tests from search service (0c84220a4) - Sort out search service (63295d008) - Issue #1053 - Drop support Android and remove Fennec - Part 1a: Remove mobile/android (abe80cc31) - Issue #1053 - Drop support Android and remove Fennec - Part 1b: Remove MOZ_FENNEC (325b204d2) - [minor] Fix a variable name in Basilisk error page (2e781c998) - Add application ID and widget toolkit placeholders to UpdateUtils.jsm (cb5d20deb) - Don't use UpdateChannel.jsm in nsBlocklistService.js (a9ae19957) - Use UpdateUtils in GMPInstallManager.jsm (c11a0b276) - Remove UpdateChannel.jsm (9cf2c92c3) - [PALEMOON] Remove errent extensions.blocklist.* from shared branding prefs (e86f0e555) - Remove useless assert. Resolves #1055. (51af3decb) - Merge pull request #1054 from adeshkp/patch-11 (ace7f20fa) - Capture delayed events and cancel as necessary. (3424afcca) My changes since my last build: - nss: go back to 3.43 release (b314cfa40) - a11y: fix build (2faa94fa0) * since MCP deleted lots of files, this might affect Serpent's functionality of updating WE extension. please test and report if there is any irregularities.
  20. 6 points
    New build of Serpent/UXP for XP! Test binary: Win32 https://o.rths.cf/basilisk/basilisk52-g4.1.win32-git-20190420-51722cd4f-xpmod.7z Win64 https://o.rths.cf/basilisk/basilisk52-g4.1.win64-git-20190420-51722cd4f-xpmod.7z source code that is comparable to my current working tree is available here: https://github.com/roytam1/UXP/commits/custom NM28XP build: Win32 https://o.rths.cf/palemoon/palemoon-28.5.0a1.win32-git-20190420-51722cd4f-xpmod.7z Win64 https://o.rths.cf/palemoon/palemoon-28.5.0a1.win64-git-20190420-51722cd4f-xpmod.7z Official repo changes since my last build: - Stub out FxA context menu functions. (8e44bbb43) - Merge branch 'master' into Sync-weave (51b821b3f) - Merge pull request #998 from MoonchildProductions/master (bf0413359) - Remove CloudSync (4c4314864) - Remove some fxa tests. (aa1a39311) - Remove fxAccountsEnabled checks. (f999f544a) - Merge branch 'master' into Sync-weave (88083f8c6) - Merge branch 'master' into Sync-weave (473291f8f) - [BASILISK] Add configure option to disable sync (3e466a01e) - [BASILISK] Remove FxA Synced Tabs Sidebar (711c9cd6c) - [BASILISK] Remove FxA infected Sync - Part 1: Remove or condition CUI and Integration Points (349ceffd8) - [BASILISK] Remove FxA infected Sync - Part 2: Sync Client (3face1acf) - [BASILISK] Remove FxA infected Sync - Part 3: Remove about:accounts (12885d441) - [BASILISK] Remove FxA infected Sync - Part 3b: nsModule (757424eed) - [BASILISK] Port PM Sync Client - Part 0: Add PanelUI sync button static images (17a54a70d) - [BASILISK] Port PM Sync Client - Part 1: Initial transfer (f98cdab7a) - [BASILISK] Port PM Sync Client - Part 2: Basic Integration with glue and preferences (f6c16cff3) - Merge branch 'master' into Sync-weave (ce3979c72) - Merge branch 'master' into Sync-weave (015f385ec) - Merge branch 'master' into Sync-weave (6968a3e40) - [BASILISK] Fix merge induced error in base jar.mn (dc4c5d4c7) - Merge branch 'master' into Sync-weave (8e5056ce2) - [BASILISK] Restore Tabs from Other Devices history menu item and Add First Sync Progress (0ea4dabde) - Remove some BEOS 1st party code leftovers. (095ea5568) - Merge pull request #1 from MoonchildProductions/master (5a1843c9f) - Bug1408701: Ensure that we continue to show dark scrollbar thumbs on.. (577ca2cd6) - Merge branch 'master' into Sync-weave (dea594744) - [BASILISK] Port PM Sync Client - Part 4: Tools menu items (Set Up Sync/Sync Now) (519d0cf55) - Merge pull request #1042 from wicknix/master (07381c3ed) - [BASILISK] Port PM Sync Client - Part 5: Port the original sync toolbar button and create a synced tabs toolbar button (868c9b8d7) - Merge branch 'master' into Sync-weave (df0c78a8c) - [BASILISK] Port PM Sync Client - Part 6a: Obvious ifdef'ing and clean up (7008afd8e) - [BASILISK] Port PM Sync Client - Part 6b: Don't build the sync client ui when it is disabled, duh. (1e868fadf) - Merge branch 'Sync-weave' (3eb4310cd) - Remove FxAccounts front-end module references (8a6883251) - Remove various FxA tests (cdc962dca) - Remove Firefox Accounts service and tie-ins. (de75f133a) - Merge branch 'Sync-weave' (51722cd4f) My changes since my last build: - update Twemoji font to upstream 0.4.0. (6a07ab850) - nss: update nss to hg rev 2d6adc7d8bfc with vc2013 hackfix (0daf4d9cc) - update libaom to rev 76574b6c09515d6687ebfa9760319e521f5abeb3 (without moz.build and aom_ports/aom_once.h) (ef35212f8)
  21. 6 points
    It was to be expected that the MS will shut down the update system. So I've created my own update rollups (DEU and ENU) to circumvent this problem. Following a list of the updates that are included in my rollups.
  22. 6 points
    Regarding the title of this thread, something just occurred to me: once you've installed all the updates you intend to, now would be a good time to make a full system backup. That way, if you ever need to restore, you'll be able to restore a fully-patched system and not have to worry about whether Windows Update still works for XP.
  23. 6 points
    If, instead, MS nuked Windows 10 with extreme prejudice and released 7 SP2, 8 SP1 and 8.1 SP1, the world would become a wonderful place.
  24. 6 points
    I sometimes wonder if MS guys throw patches with errors they can't solve, and then watch MSFN boards and wait for you guys to solve them. Y'all rock!
  25. 6 points
    no, I'll still build browsers weekly.
  26. 6 points
    New New Moon 27 Build! 32bit https://o.rths.cf/palemoon/palemoon-27.9.6.win32-git-20190330-d86d78c8b-xpmod.7z 32bit SSE https://o.rths.cf/palemoon/palemoon-27.9.6.win32-git-20190330-d86d78c8b-xpmod-sse.7z 32bit noSSE https://o.rths.cf/palemoon/palemoon-27.9.6.win32-git-20190330-d86d78c8b-xpmod-ia32.7z 64bit https://o.rths.cf/palemoon/palemoon-27.9.6.win64-git-20190330-d86d78c8b-xpmod.7z source repo: https://github.com/roytam1/palemoon27 repo changes since my last build: - partly ported change from tenfourfox: - chemspill: M1537924 M1538006 (backported to ESR45) (b22dfbd77) (161cf6eb4) - import changes from rmottola/Arctic-Fox: - Bug 1140586 part 1. Add some asserts about us not caring too much about the parents of native functions. (dd735591e) - Bug 1140586 part 2. Stop passing non-null funobjArg to js::NewFunction and js::NewFunctionWithProto. (b4d148f53) - Bug 1137180 - Only mark inner scripts as having failed a bounds check after bailing out (22ded5bd9) - Bug 1140582. Remove the parent argument from JS_NewObjectWithUniqueType. (a49a25f88) - Bug 1139993 - Add VectorBase::ConstRange that gives out |const T&| entries. (409317be0) - Bug 1136906 part 1. Stop passing parents to JS_NewObject in ctypes code. (14412c561) - Bug 1136906 part 2. Stop passing a parent to JS_NewObject in xpconnect code. (e5769c27d) - Bug 1136906 part 3. Remove the parent arg from JS_NewObject. (98f1b9c37) (ee2d17418) - import changes from rmottola/Arctic-Fox: - Bug 1140670 part 1. Just use the global, not the proto's parent, as the default parent in NewObjectWithGivenTaggedProto. (d2ef7ee90) - Bug 1140670 part 2. Just use the global as the parent in js::CreateThis and js::CreateThisForFunctionWithProto. (025d25703) - Bug 1140670 part 3. Add an assertParentIs() for asserting the parent is something specific and use it in various places to eliminate getParent() calls. (d814a6344) - Bug 1140573 part 1. Drop the parent argument from JS_NewFunction. (d657e25c7) - Bug 1140573 part 2. Drop the parent argument from JS_NewFunctionById. (2259f4027) - Bug 1140573 part 3. Drop the parent argument from js::NewFunctionWithReserved. (84ab2d944) - Bug 1140573 part 4. Drop the parent argument from js::NewFunctionByIdWithReserved. (a10821f1a) - Bug 1142266. Remove the parent argument from js::NewObjectWithProto. (efe9144e3) - Bug 1142241. Stop using getParent() in js::GetObjectEnvironmentObjectForFunction. (b04a4a38e) - some pointer style for better patching (608e1a6ad) (c1ae338ae) - import change from rmottola/Arctic-Fox: - Bug 1133085 - PropDesc::initFromPropertyDescriptor should understand JSPROP_GETTER without JSPROP_SETTER and vice versa. (d83f16200) (d86d78c8b)
  27. 6 points
    New build of Serpent/UXP for XP! Test binary: Win32 https://o.rths.cf/basilisk/basilisk52-g4.1.win32-git-20190330-843e4ceff-xpmod.7z Win64 https://o.rths.cf/basilisk/basilisk52-g4.1.win64-git-20190330-843e4ceff-xpmod.7z source code that is comparable to my current working tree is available here: https://github.com/roytam1/UXP/commits/custom NM28XP build: Win32 https://o.rths.cf/palemoon/palemoon-28.5.0a1.win32-git-20190330-843e4ceff-xpmod.7z Win64 https://o.rths.cf/palemoon/palemoon-28.5.0a1.win64-git-20190330-843e4ceff-xpmod.7z Official repo changes since my last build: - Issue #756 - Remove Contextual Identity References from Pale Moon (ad5bbbdb6) - Issue #756 - Remove contextual identity from BackgroundPageThumbs.jsm (d0b4eb41b) - Issue #756 - Remove Contextual Identity from Basilisk (1f5194b5f) - Issue #756 - Remove Contextual Identity from UnifiedComplete (2d20c38f8) - Issue #756 - Remove Contextual Identity from DevTools (1413b3d6f) - The result of adding any percentage factor to a size that is zero should also be zero (96dfb2e6d) - Remove leftover updater lines in about box (cda6937fc) - Merge pull request #1019 from JustOff/PR_nsLayoutUtils_AddPercents (f33a272de) - Restrict ExtractLinearSum to monotonous operation in infinite math space. (357ea8cae) - Restrict ExtractLinearSum to monotonous operation in infinite math space. (054794f8c) - Merge branch 'master' of https://github.com/MoonchildProductions/UXP (cc3f51ad6) - Grab caching capturing content with local variable. (5ea1d913c) - Bump Goanna version for layout handling changes. (89d0316e3) - Convert UI-dictating FTP errors to console errors. (976be8743) - Escape '!' to '\041' in posix strings ($'...') (3cfdf908c) - Check for osint argument when checking for greomni and appomni arguments. (10982181d) - Disallow getUserMedia on null principals. (36fbcc630) - Unregister ProcessHangMonitor as a hang annotator on shutdown. (68acc67dd) - Check if CopyData succeeded. (5ddaf2aef) - Revert "Unregister ProcessHangMonitor as a hang annotator on shutdown." (1709b8a59) - WebRTC: Add explicit mutex on callback receiver for cases it's not already locked. (9fc25801f) - Bug 1338306 - nsIPrefBranch.get*Pref should support providing a default value, r=bsmedberg. (cac3f9678) - Merge pull request #1021 from Ascrod/default-pref (834ea744c) - Remove obsolete getPref helpers. (c9d2e9bcf) - Merge pull request #1023 from Ascrod/default-pref (a1ad1d835) - Only write the newtab URL if the machinery for it had previously been initialized. (eb77e289b) - Merge branch 'master' of https://github.com/MoonchildProductions/UXP (917a2c450) - Update the 7z installer stub source to 18.05. (f2902217b) - Add the customization .diff to the 7z stub. (24b1f14e0) - Merge pull request #834 from g4jc/remove_contextid (aa816b3d8) - Prevent mistaken overwriting of browser.newtab.url when using the browser preferences dialog (a15e49e42) - Revert "Only write the newtab URL if the machinery for it had previously been" (d72bcc92f) - Merge pull request #1027 from JustOff/PR_newtab_choice (55d249557) - Installer: Update 7zstub binaries, add license and readme. (1df844b95) - Clean up installer scripts a little. (91d17efc6) - Simplify some alias sets in IonMonkey. (0b999100f) - Replace unsupported `null` default values with an empty string. (843e4ceff) My changes since my last build: - restore pre-vista logic that is deleted in https://github.com/MoonchildProductions/UXP/commit/3c02dbad946487a83783a1923463a1ebb96aae19 (aa7849b37) - ported change from tenfourfox: - chemspill: M1537924 M1538006 (backported to ESR45) (b22dfbd77) (7c4246424) - ffvpx: update to 3.4.6 (402c27b56) - update libaom to rev 5bdd95475e07ac8641114cb139105b8d734a1b60 (without moz.build and aom_ports/aom_once.h) (fb515ea77) - utilityOverlay: restore getBoolPref for compatibility (caab96c96)
  28. 6 points
    Trying to build it now. Despite the fact that I'm building on WinXP, I still had to explicitly tell it to build for WinXP: perl Configure VC-WIN32 -D_WIN32_WINNT=0x0501 Without the -D just about every test failed; apparently the stupid Configure script just assumes Win 7+ rather than grabbing the version it's actually running on . That may explain why so many of the "compatible with XP" builds aren't actually compatible with XP. Edit: Final (apparently XP-compatible) build of OpenSSL v1.1.1b is about 3 MB when written to a .7z archive file. You can download it from my company's Web site.
  29. 5 points
    You can force "multiprocess mode" in FF 52 by creating the Boolean preference browser.tabs.remote.force-enable and setting it to true. (Also works in Serpent, BTW.) This splits FF (or Serpent) into two processes. Not as good as Chrome, where each tab is a separate process, but it can still help.
  30. 5 points
    The latest version of Qihu's 360 Extreme Explorer (v11.0.2086.0, released May 16th 2019 - its default UA declares a Chromium 69.0.3497.100 compatibility ) will also pass the test : But this is on Windows Vista SP2 32-bit, not on XP SP3 32-bit (hence, one of you XP users would have to test... ) EDIT: Make sure in "flags" that chrome://flags/#tls13-variant is set to "Enabled (Final)"
  31. 5 points
    The support may be over, but this doesn't mean that people stopped using XP. Today I've been to the dentist and he is using XP. When I asked him why, he said that XP is connected to the sensors of the tools he uses on a daily basis and that he upgraded to Windows 10 months ago as he changed his computer, however the technician he called spent hours trying to make it work with those sensors but he failed, so he reverted to Windows XP. "I've been using these things since 2005" he said, "I'm gonna keep using XP until I'll change the whole thing, its tools and its sensors, which is unlikely to happen anytime soon". Since I wasn't able to take a clear shot, I told him about the Windows XP Spotter group and I quickly told him that we take pictures of XP running in businesses 'cause we are fan of the OS, so he kindly let me take this picture:
  32. 5 points
    It says that "The vulnerability doesn't affect Windows 8.1 or 10 (or Server variants starting with 2012), but it does affect Windows 7, Windows Server 2008 and 2008 R2". Windows Server 2008 R2 is based on Windows 7, but the 2008 version is based on Vista, so I'm pretty sure that Vista is also affected.
  33. 5 points
    If you would've told a costumer from 2001 that their purchase of Windows XP would get updates until 2019 they would not believe you! Yet, here we are with a new patch out of the regular POSReady 2009 support window
  34. 5 points
    Hey - party's not over. Here's a beer!
  35. 5 points
    New build of Serpent/UXP for XP! Test binary: Win32 https://o.rths.cf/basilisk/basilisk52-g4.1.win32-git-20190504-d9d9d1ed8-xpmod.7z Win64 https://o.rths.cf/basilisk/basilisk52-g4.1.win64-git-20190504-d9d9d1ed8-xpmod.7z source code that is comparable to my current working tree is available here: https://github.com/roytam1/UXP/commits/custom NM28XP build: Win32 https://o.rths.cf/palemoon/palemoon-28.6.0a1.win32-git-20190504-d9d9d1ed8-xpmod.7z Win64 https://o.rths.cf/palemoon/palemoon-28.6.0a1.win64-git-20190504-d9d9d1ed8-xpmod.7z Official repo changes since my last build: - Fix failure to print when pages contain zero-sized <canvas> element. Fixes #1058 (1091fcac8) - Merge pull request #1059 from g4jc/print_preview_fix (6e8e07e2c) - New cycle version bump. (b63098646) - Merge branch 'master' of https://github.com/MoonchildProductions/UXP (722cc9091) - [PALEMOON] Prevent overlapping modal prompts and preserve prompt order. (cd296c598) - Improve dead compartment collection js/src (5a65d8739) - Improve dead compartment collection js/src/gc (2cb4d2ee5) - Improve dead compartment collection js/src/builtin (bb1fad0fa) - Improve dead compartment collection js/ipc (cf319d581) - Space to comment. (44e59151e) - Add newline at end of files js/src (d57c13c6d) - add newline at end of files js/src/gc (22116f9a7) - Add newline at end of file js/src/builtin (6f15c693f) - Add newline at end of files (038d437d7) - tab to spaces js/src (0e70828f2) - tab to spaces js/src/gc (9fb6b925f) - tab to spaces js/src/builtin (f8d671ab7) - tab to spaces js/ipc (d59b5441e) - remaining tabs to space js/src/jsgc.cpp (4d03ec5c2) - Remaining tabs to spaces JavaScriptShared.cpp (53e748f9b) - Remove some empty lines (a2dbd23b0) - Remove rest of empty lines. (0c8c58314) - Whitespaces, typo, tabs to space (31ea8c7e9) - Braces and one more typo fix for comment (2ec2389d7) - Merge pull request #1065 from win7-7/Improve-dead-compartment-collection (871b926f6) - Restore BROWSER_NEW_TAB_URL check in Basilisk. (aca5eb2cd) - patch to Bug 1363423 (7975665f6) - patch to Bug 1377329 (9b750203d) - unnecessary space at the end removed (99d111ad8) - Merge pull request #1070 from win7-7/PresShellPaint-performance-patch (d9404b77b) - Merge pull request #1071 from win7-7/nsDisplayListBuilder (650585f03) - Only change the default and hover text color on buttons for Windows 8+ HC Themes (aero-lite) (d9d9d1ed8)
  36. 5 points
    In terms of Security it is certain that Chrome 360 is more secure than Chrome49. For Privacy with so little data and fragmentation it is impossible to establish any conclusion. I can advise you to use Chrome360 with my privacy and security settings: Chrome --no-referrers --ssl-version-min=tls1.2 -cipher-suite-blacklist=0x002F,0x0035,0x000A,0x009C,0x009D --disable-webg Chrome://Flags Extension Content Verification - Enforce Strict Enable AppContainer Lockdown - Enabled Framebusting-requires-sameorigin-or a-user gesture - Enabled Extensions: Cookie Autodelete BP Privacy Block All Font and Glyph Detection U.B.O. Decentraleyes ScriptSafe - Only the functions described below are enabled: Block Browser Plugin Enumeration Protection from Canvas Fingerprints Block Audio Fingerprinting Block Battery Fingerprinting Block Enumeration of the Device Block Access to Canvas Font The start of each of my browsers in Windows XP is with limited rights.
  37. 5 points
    A word of caution about HTML5test.com: Many of the points awarded by that site are for features that have privacy and/or security concerns: e.g., 15 points if your browser supports geolocation; 10 points for "service workers," a point for the "ping" attribute, etc. A very high score may not be the best news about your browser.
  38. 5 points
    Today I make an update of the acpi.sys driver for Windows XP SP3 32 bit which should work on any compi. AMD, Intel, language does not matter Dietmar acpi.rar
  39. 5 points
    Good news: Visual Studio 2019 can still target Windows XP: https://docs.microsoft.com/en-us/visualstudio/releases/2019/compatibility
  40. 5 points
    Adobe Flash Player has been released today (confirmed working with Windows XP SP3/Windows XP x64 SP2) Internet Explorer ActiveX: http://fpdownload.adobe.com/get/flashplayer/pdc/ Mozilla Firefox NPAPI (also for Opera Presto/Google Chrome 44 and earlier): http://fpdownload.adobe.com/get/flashplayer/pdc/ Google Chrome 45 through 49 PPAPI: http://fpdownload.adobe.com/get/flashplayer/pdc/
  41. 5 points
    *UPDATE!* I have released a new version of the UOC Patch that fixes the less than stellar framerate issue with the newest version of Firefox 45 ESR SSE, plus adding some more performance tweaks. Please update! A brief introduction Hi everybody, I'm writing this thread because I would like to share with you an experiment I made as a result of two years of using an old, single core system (an overclocked Pentium III-S Tualatin 1.4GHz) with the modern web. As you all know, the most versatile and useful web browser to use for old machines, especially XP ones, is Mozilla Firefox, thanks to its customizability, the numerous forks that it spawned and the built in certificates manager that makes things easier if we want to connect old computers to the internet. This thread focuses specifically on @roytam1's browsers for XP, such as New Moon 27 SSE and Firefox 45 ESR SSE, because they are the ones I use on my Pentium III system and the ones I used as a base to develop my "patch". We know that old computers, especially if single core or SSE only systems, can struggle a bit with the stock versions of these browsers, because they are quite resource intensive, and so the experience is quite limited unless you have an hardware that is capable enough to run the browser comfortably. So, a year ago, back when my Tualatin was still a 800Mhz Coppermine system, I started delving into the about:config of Pale Moon first, and New Moon later, in order to reduce as much CPU and RAM consumption as possible. Had to do several trials and errors, but in the end, I finally managed to get improvements in responsiveness and overall speed on the browser and so, after six revisions, I officially want to release the UOC Patch, my personal attempt, inspired by the community and by my experience of using an old computer as a daily driver, at making web browsing with Firefox and derivatives a much more enjoyable experience. Ok ok, good. So what's the UOC Patch? The UOC Patch (shortened form of Ultra One Core Patch) is a custom Global Preferences file available for any Mozilla based browser that uses the codebase of Firefox 38 ESR (such as Pale Moon and Roytam1's New Moon) or Firefox 45 ESR (i.e. Firefox 45 ESR SSE always by Roytam1), that is aimed at optimizing the browser to run on old machines and to consume less resources. Bear in mind that I developed the UOC Patch for my machine, which used to be a 800Mhz Coppermine and now is an overclocked 1.4GHz Tualatin, so it might perform differently on yours, but it should bring some improvement in terms of speed. The UOC Patch is a Defaults Override file, meaning that it goes in the following directory "C:\Program Files\{Your Mozilla based browser}\Defaults\Pref\". As soon as you put the patch into the "Pref" folder, the default about:config parameters will be replaced by the ones of the patch, unless you have modified the same parameters. If so, you can switch to the UOC Patch parameters by simply resetting them in the about:config. (If you feel adventurous, you can even open the patch with your favourite text editor, replace the "Pref(" parameter with "user_pref(" and embed it in your Prefs.js file, but this method might be cumbersome for beginners.) The requirements? Surely it has them. Well, yeah. The UOC Patch requires at least a DirectX 9 capable graphics card. Even though it will work on a DirectX 8 card, I don't have one I can use to test it so it's pretty much untested. I tested the patch with a Geforce FX5500, an FX5600, a 6800GT and an ATI Radeon HD3850 and my current graphics card, an X1950 Pro, and the patch speeds up the browser as it should. Then, ideally, the CPU. A 800MHz CPU and higher can give you a better experience, again, I don't know how it does perform on a slower CPU. RAM wise, any system that can run New Moon 27 and derivatives or Firefox 45 ESR SSE will support the UOC Patch without issues. So, to recap, you need: A DirectX 9 capable graphics card with at least a 128 bit buss A 800MHz CPU or faster for better performance Enough RAM to support New Moon 27/Firefox 45 ESR SSE and other Roytam1's Mozilla based browsers Ok now that we know the specs, how to install it? Installing the UOC Patch is a very easy process. Just go in your browser folder (C:\Program Files\Mozilla Firefox or Pale Moon or any other Mozilla based browser you use), then go in the "Defaults" then the "Pref" folder and extract the UOC_Patch38.js or UOC_Patch45.js you will find in their respective archive in the above folder and start the browser. The UOC Patch will be automatically applied alongside your existing preferences. But as a safety measure, do make a backup of your prefs.js file inside your profile folder, before launching the patched browser. In order to access your profile folder, you must make sure that the hidden folders are visible (if not, you must go in the Control Panel, then choose Folder Options, and tick the box that says "Show Hidden Folders"), then navigate to your Firefox/New Moon/Mozilla browser profile folder (i.e. C:\Documents and Settings\{Your Username}\Application Data\Mozilla\Firefox\Profiles\{Your Profile Folder}), you will find a file called "prefs.js". Make a copy of the file and rename it to "prefs.bak" to back it up. Enough with the words! I want to download it! Okay, okay. There you go. These are the download links for the UOC Patch. Remember, you must not absolutely use the UOC Patch for a particular codebase with a browser that uses a different one. You might experience issues. These two versions are conceived for the Firefox 38 ESR and 45 ESR codebases, so any fork of Firefox that uses those codebases, will work with their respective version of the patch. Choose carefully. For Firefox 38 ESR based browsers (i.e. New Moon 27): Click Here For Firefox 45 ESR SSE and 45 ESR based browsers: Click Here A Final Note Please, by all means, test the patch on as many systems as possible! The more the configurations, the better will be. Due to space constraints and lack of money, I don't have access to different systems I can test the patch with, and my Tualatin is the computer I used as a testbed for its development and so, I made it focusing on the hardware I had and currently have. The UOC Patch is not strictly limited to single core systems, but it can be used on any old and slow computer that runs Roytam1's Mozilla forks, it would be interesting to see if it can bring some benefits even on faster systems, or even slower ones: I don't have a Pentium II or an AMD/Intel Socket 7 system to test the patch with, otherwise I would have tried it on those too. The UOC Patch has not been tested on K-Meleon and SeaMonkey, but mostly because I'm still experimenting with those and so if you want to try it on those browsers, it's entirely up to you. There are some extensions I heartedly recommend to use alongside the UOC Patch to make the experience much better. These are: NoScript (I recommend v2.90.14 for performance reasons, at least for Pentium 3 systems) Decentraleyes 1.4.2 Bluhell Firewall 2.5.3 UAControl (To change the user agent on the fly, per website) uBlock Origin Vacuum Places Improved 1.2.1 And this one is optional, Youtube 2 Player, a nifty plugin that turns Youtube links into redirects to VLC, so whenever you click on a Youtube link, the video will be loaded automatically in VLC, thus saving resources and CPU cycles. Okay, that's all folks. Now if you want to throw rocks or tomatoes or veggies at me, feel free to do so. I developed this in my free time with a desire of curiosity and experimentation, to see if I can push my old machine to its extreme limit, and so far, at least personally, I'm quite satisfied. But as always, it's up to you to judge whether the UOC Patch is actually useful for your system, or it's an utter piece of garbage. Be aware I'm not responsible of any pandemy, nuclear warfare, space/time continuum and so on caused by your system. I upload the UOC Patch for experimental purposes, and it's provided AS IS. Happy RDD'ing!
  42. 5 points
    New build of post-deprecated Serpent/moebius for XP! * Notice: This repo will not be built on regular schedule, and changes are experimental as usual. ** Current moebius patch level should be on par with 52.8, but some security patches can not be applied/ported due to source milestone differences between versions. Test binary: Win32 http://o.rths.cf/basilisk/basilisk55-win32-git-20190330-09b851794-xpmod.7z Win64 http://o.rths.cf/basilisk/basilisk55-win64-git-20190330-09b851794-xpmod.7z repo: https://github.com/roytam1/basilisk55 Repo changes: - ffvpx: update ffmpeg to 3.4.5 (ff7089326) - update libaom to rev b46542180d551d5e4eb666cf35dd62395ba43f3e (without moz.build and aom_ports/aom_once.h) (8de1c2b90) - libwebp: update to 1.0.2 (bb84e2eed) - import changes from UXP: - Make resuming of decoding work for anonymous decoders. (64d65e096) - Make Sourcebuffer::AppendFromInputStream handle canceled image loads. (87bef3e99) - Check for contiguous buffer state. (8dd8df90b) (097da0429) - update NSS to git rev e76a339d424a5fad9bc42a7e91154a4dd89b83f3 with nss339-vc2013.diff applied with ssl.gyp changes reverted (59066dcc2) - update nss to git rev 4aea92b574d2d674ee75838d46ea95b113e8fecb (d0d6cc15e) - update Twemoji font to v11.3 based build. (3abe807b6) - update libaom to rev 0ec86ac7ae1e32a7e70410fa4972a655ec3670a4 (without moz.build and aom_ports/aom_once.h) (b246b0a6e) - nspr: update nspr to hg rev 753fe0f7964c (d151c0c67) - nss: update nss to hg rev 395a93dbc02e with vc2013 patch applied (ebfc3f0a8) - revert most of "Switch working copy to Goanna 4" (https://github.com/MoonchildProductions/moebius/commit/c4895374053ab93b4f365d3e690e99a30ffa1a2f) in order to keep upstream patch applicable (f63e51e47) - ported change from tenfourfox: - chemspill: M1537924 M1538006 (backported to ESR45) (b22dfbd77) (141fdee14) - webextension: revert this part of changes in rev f63e51e471c0e57fed750971a5c5b6fc397061a6 (abd82fe1f) - ffvpx: update to 3.4.6 (b4d5e6c32) - update libaom to rev 5bdd95475e07ac8641114cb139105b8d734a1b60 (without moz.build and aom_ports/aom_once.h) (09b851794)
  43. 5 points
    I released v3.0a for English. http://blog.livedoor.jp/blackwingcat/archives/1980734.html
  44. 5 points
    XP will live longer than 98se, and some people still use that for games, and old programs, hardware as a hobby.
  45. 5 points
    The cryptography 2.6.1 module with OpenSSL -1.1.1b (thanks to @Mathwiz) for Python 3.4.4 I have tested so far with the following modules: altgraph==0.16.1 appdirs==1.4.3 asn1crypto==0.24.0 cffi==1.12.2 colorama==0.4.1 cryptography==2.6.1 future==0.17.1 idna==2.8 macholib==1.11 packaging==19.0 pefile==2018.8.8 pyasn1==0.4.5 pycparser==2.19 PyInstaller==3.4 pyOpenSSL==19.0.0 pyparsing==2.3.1 PySocks==1.6.8 pywin32==221 pywin32-ctypes==0.2.0 six==1.12.0 urllib3==1.24.1 For Installing: Uninstall the older cryptography module beforehand (pip uninstall cryptography), then simply unpack the two directories in the python directory python34\lib\site-packages. Download (The latest cryptography module 2.7.dev1 from March, 11 2019 for testing is also included) Note: The manually installed cryptography module can be uninstalled the usual way (pip uninstall cryptography)!
  46. 5 points
    Ok, I've had time to update the repository with the January and February updates. Just in time, before Microsoft unleash the March ones. Replaced Monthly Rollup with the new KB4487023 (located on the root directory of the repository) Added Security Only Updates, KB4480957 and KB4487019 (located in the folder "/Security Only (Post August 2018)") Replaced Internet Explorer Cumulative Update with KB4486474 (located in the folder "/Security Only (Post August 2018)") Replaced .NET Framework Security and Quality with: -KB4483457 for .NET 2.0 SP2 (located in "/NET 2.0 SP2/Security and Quality Rollup") -KB4483455 for .NET 4.5.2 (located in "/NET 4.5.2/Security and Quality Rollup") -KB4483451 for .NET 4.6-4.6.1 (located in "/NET 4.6-4.6.1/Security and Quality Rollup") Added .NET Security Only Updates with: -KB4480084 and KB4483482 for .NET 2.0 SP2 (located in "/NET 2.0 SP2/Security Only") -KB4480076 and KB4483474 for .NET 4.5.2 (located in "/NET 4.5.2/Security Only") -KB4480072 and KB4483470 for .NET 4.6-4.6.1 (located in "/NET 4.6-4.6.1/Security Only") Added Extra updates KB4486459, KB4487354 and KB4490514 (located in "/Extras") with an updated readme file Funny enough, the timezone update KB4486459 does not replace the previous KB4468323. Also worth noting that KB4487354 in the extras folder is not needed if you install the Monthly Rollups. That is all for now https://mega.nz/#F!txxRyLzC!1vBMGzMHiL864f3bl1Rj1w EDIT: I've rearranged the repository for easier navigation. Now the pre-Monthly Rollup Security Updates are in a folder named "Security Updates (May 2017-August 2018)"
  47. 5 points
    New build of Serpent/UXP for XP! Test binary: Win32 https://o.rths.cf/basilisk/basilisk52-g4.1.win32-git-20190302-e64dae886-xpmod.7z Win64 https://o.rths.cf/basilisk/basilisk52-g4.1.win64-git-20190302-e64dae886-xpmod.7z source code that is comparable to my current working tree is available here: https://github.com/roytam1/UXP/commits/custom NM28XP build: Win32 https://o.rths.cf/palemoon/palemoon-28.5.0a1.win32-git-20190302-e64dae886-xpmod.7z Win64 https://o.rths.cf/palemoon/palemoon-28.5.0a1.win64-git-20190302-e64dae886-xpmod.7z Official repo changes since my last build: - WIP fix 1 (c962e2051) - Move default-enable pref to application. (c08b490c5) - Update Basilisk FE code with HTTP Auth DoS protection. (f227feb6e) - Make the Auth prompt DOS protection a browser-element opt-in feature. (c1ece93c2) - Improve the http basic auth DOS protection heuristics. (e64dae886)
  48. 5 points
    @roytam1 I would like to start this post by saying that I believe SOME of my interpretations from you and reactions to me have been partly hampered by cultural and language issues.. That isn't to say I don't have my moments of being a complete a s s h o l e or anything.. Everyone knows this but perhaps we can start to correct some of that going forward. I hope you get a chance to go through your website soon but if you are working at your job and are loosing sleep over this then do take your time. Your good faith efforts will be enough for me. As for your rebranding efforts.. I want to renew my offer to help you work out all the branding points you need to deal with in the actual codebase. The one specific issue is the navigator codebase.. SeaMonkey never fully separated out branding from the rest of the main application code as Firefox and Thunderbird did over time so I have to completely rework how branding works in Navigator to accommodate that for not only my project but also people who do rebuilds and forks. As well as consistency sake. I want to help you make your selection of products for Windows XP unique to you and to be as successful as possible. You do seem to want to do your own thing past simple rebuilds and I can very much respect that.. So let's work together to make sure you and your users have products they can be proud of. @LoneCrusader As an aside, Lunaris and Draconis are AWESOME names and I am jealous I didn't think of them.
  49. 5 points
    Good grief. Hyperbole much? An anti-vaxxer? Because, I guess, "everyone knows" computer viruses are still written and tested to target the 3% or so of Windows users still running XP, and "everyone knows" none of those users ever update their AV software What an ignorant statement. That quote wasn't from Matt Tobin, by any chance?
  50. 5 points
    They can do whatever they want, and so do I. It is a smorgasbord and I'll pick whatever I want to my dish.
  • Create New...