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. 


Leaderboard


Popular Content

Showing content with the highest reputation since 06/25/2018 in Posts

  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
    UPDATE [June 7, 2019]: Post-SP4 Update Pack released! This final update pack should be applied to Windows XP installation media immediately after slipstreaming SP4 v3.1b to a Windows XP RTM/SP1/SP2/SP3 source. This will update installation media to May 2019, including every single update released until the POSReady 2009 end-of-life in May 2019. Download available at RyanVM.net.
  5. 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."
  6. 9 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.
  7. 9 points
    I'm far from sure about that. He sure wants us out of his forum, but I'm quite OK with that. I'd not like having him here either. But I doubt he'd go the extra lenght of actually inserting code to actually prevent his browsers from running on either Vista or XP. He's taken out code intended to enable that, because he sees it as bloat, of course. But adding code to forestall XP/Vista use would be adding bloat, which contradicts his slim-and-mean optimized code philosophy, IMO. Now, if people, like @Dibya, keeps on nagging him, that might change...
  8. 9 points
    First, I don't break it. If someone must take responsibility for this, then it should be Mozilla and Moonchild Productions, not me. Second, you should study whats the difference between gecko 38 and 52, and how many changes do Moonchild people changed that enhance speed and security, and changes that prevents running in old windows, and how much effort I put to restore functionality on old windows. If you failed to do this, then please leave this thread.
  9. 8 points
    Notice: These projects have no affiliation with any upstream community code sources or organizations. Please direct all support or related questions to here. "Serpent", "New Moon", "MailNews" are generic debranded names and they are subject to change in the future. Archive directory names and archive filenames will only be changed once generic debranded names are not used in the future. Latest changelog is available here as well: http://rtfreesoft.blogspot.com/search/label/browser Serpent/UXP browser (MCP reforked 52ESR as new base), and NM28XP releases: Binaries are moved to here: (I'm lazy to edit all previous posts) https://o.rths.cf/palemoon/?sort=date&order=desc BOC related binaries: Binary list: https://o.rths.cf/boc-uxp/?sort=date&order=desc FAQ: Q: Having audio distorted when watching Twitter/etc.? A: Please try turning on "Firefox compatibility" in options dialog or either "general.useragent.compatMode = 2" or "general.useragent.compatMode.firefox = true" in about:config and reload the page. Q: Can't play H264 clips? (for PM27/KM76) A: Download following packages for your browser edition(32bit/64bit) and extract DLLs to same place as palemoon.exe lives. 32bit LAV dlls are in separated package (extracted from K-Lite codec pack 13.5.5) https://o.rths.cf/palemoon/lav.7z Just in case if you have an older processor which has no SSE instruction set support: 32bit NoSSE (ffmpeg 3.1.1 lite build) https://o.rths.cf/palemoon/lav-dll-lite-mmx.7z 32bit No ASM (ffmpeg 3.1.1 lite build, if build above doesn't work on your processor) https://o.rths.cf/palemoon/lav-dll-lite-noasm.7z 64bit LAV dlls are in separated package (LAV Filters 64bit 0.70.2) https://o.rths.cf/palemoon/lav64.7z Q: AV1 Support? (for UXP-based applications except mailnews) A: You need to enable "media.av1.enabled" in about:config Q: VP9 Support? (for PM27) A: VP9 works if async MSE option is unchecked and "Enable MSE for WebM Video" checked in options. Q: Extensions/Themes not working after updating binaries. A: If you encounter extensions not show icon, clicking options button of extension causing browser unresponsive, etc. please try following actions: 1.a Killing palemoon.exe process 1.b Copy whole extensions folder out of profile folder (to somewhere else for example, desktop) 1.c Restart browser without restoring previous sessions 1.d Goto about:addons page 1.e Drop XPI files from the copied-out extensions folder to about:addonss page One-by-One. 1.f After all XPI files are dropped and installed/updated, restart browser Q: Virus detected? A: Tell your anti-virus program to exclude palemoon.exe and/or plugin-container.exe. Some anti-virus heuristic engines (for example symantec's sonar engine) is too sensitive to palemoon.exe/plugin-container.exe network activities. Q: Where's your patches for compiling my own? A: Please visit the link above "FAQ:". Latest source patch files are named "sources_patches_YYYYMMDD.7z" in that page. Q: basilisk browser showing basic pages in GMail? A: set these to "ture" in about:config general.useragent.compatMode.firefox general.useragent.compatMode.gecko Q: How to change User Interface language? A: Please see this post: Q: Portable Loader? A: You can always use official portable launcher with my binaries, or you can use my simple portable loader written in NSIS: Q: How to install extensions/themes in BNavigator browser? A: Please check this post out: ------------------------------------- NewMoon 27 build: ------------------------------------- Serpent/moebius browser (deprecated by MCP, forked by me), and also 26.5 as playground : And NewMoon 26.5 and K-Meleon 74 with Goanna 2.2 (newmoon-26.5) for vanilla Win2000 build: ------------------------------------- K-Meleon browser with Goanna/Tycho engine: It has its own sub-forum in K-Meleon official forum! http://kmeleonbrowser.org/forum/list.php?19 Latest build: ------------------------------------- Firefox ESR 45 with TenFourFox fixes for SSE-only machines: ------------------------------------- K-Meleon Original cross-post is here: ----original post message belows---- Today's build with portable LAV libraries. Place LAV dlls (av*.dll) in same place as palemoon.exe lives. Official repo changes since my last build: -Clobber for Brotli/WOFF2 update -Fix some comments (no code change) -Enable Brotli content-encoding by default (https only). -Pull woff2 upstream update. -Update Brotli decompressor. My changes since my last build: - Upgrade Mozilla NSPR and NSS to 4.16 and 3.22 for (hopefully) faster AES operations 32bit: https://o.rths.cf/palemoon/palemoon-27.6.0a1.win32-git-20171002_2-e68ab5b3d-xpmod.7z 64bit: https://o.rths.cf/palemoon/palemoon-27.6.0a1.win64-git-20171002_2-e68ab5b3d-xpmod.7z
  10. 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
  11. 8 points
    I also don't see how frank was rude at all, sounds like you could use an emotional support animal.
  12. 8 points
    I see no rudeness whatsoever in Frank's post. Yours, OTOH, is unnecessarily offensive. People nowadays are too oversensitive...
  13. 8 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!
  14. 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.
  15. 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."
  16. 8 points
    Hey guys, I put together an installer for Roy's browsers. It checks a file on my server to see the latest version (keeping that updated shouldn't be an issue for me) and then it downloads the latest browser version from roys site and installs it. Currently it supports Basilisk (x86 and x64), and New Moon (x86 and x64). Tested OSes with the installer include XP and Vista (both x86 and x64 editions) Other builds are not currently supported due to the sometimes irregular build interval http://i430vx.strangled.net/files/XP/RoyTam Browser Installer.exe If you find any bugs, LMK Thanks for @WinClient5270 for noticing that you must have the visual basic runtime installed first for the installer to work. (Install VC Redist 2008 from Microsoft)
  17. 8 points
    ... 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...
  18. 8 points
    I see you've decided to come trolling again Jody... because what else is this really? If you no longer use XP, you no longer care about XP, and you think XP users are somehow backward, then why do you bother to come here to read the XP forum or even attempt to engage the XP users? You say you come here for "discussion" - but most of the time you're only interested in pushing the "accept change and move on" argument. You will agree or semi-agree with some minor point here and there to maintain the impression that you're having a fair discussion or that you're open-minded, but in the end your opinion never really changes. So why do you keep expecting other users minds to change? Do you just like to keep the disagreement stirred up to waste everyone's time? Why do you have such an intense interest in what operating system others choose to use if your mind is already made up about it? Why does it seem to bother you so much when other people don't just "go with the flow?" Who are you to question anyone else for their choices, or to seek "justifications" for those choices? (even if, as you claim, you mean nothing ill by it) If you really believe that something newer is always better, then you're welcome to your opinion. But that's nothing more than "chronological snobbery." The fact that something is newer does not make it better than something older. In fact, the reverse is frequently true. This attitude (prevalent most everywhere I look online these days) that it's OK to force, browbeat, insult the intelligence of, shame, chide, or in any other manner "push" users of any product to give it up for something newer just because someone else says it's better is a cancer, pure and simple. I'll bet that most people pushing this drivel would be deeply offended if say, someone told them their political views were wrong and that they should change because someone else says so. Too many people today are willing to sing the praises of freedom until that freedom applies to something they don't like. Yes, Microsoft has a right to change their products and/or change their business philosophy or whatever. But as far as I am concerned they have a moral obligation to NOT WILLFULLY make it more difficult for users of previous products to keep those products operating. Said users paid for those products, and the fact that some time has passed does not make those users somehow obligated to give up something that works perfectly well and buy something else because Microsoft says so. Don't want to support it any longer? Fine. But don't start putting roadblocks out for those older systems intentionally. This is the main root of the problem that many of us have with Microsoft and many other software/tech companies. It's not what they choose to do, but how they go about doing it. So they want to release a new operating system? Fine. Release it, and if it's really better than what users already have then people will begin to move to it of their own accord. Where the problem arises is 1)when they start pushing FUD garbage about how suddenly you will become vulnerable to this or that catastrophe simply because you haven't chosen to move on; 2)when they use their "influence" to push other companies and products to no longer support an older system; and 3)when they start "manipulating history" to remove information or files relevant to older products, thereby making it more difficult to keep the older systems running (which once again were paid for, and the fact that time has passed does not invalidate this). Very few things make me angrier than when I follow a link to Microsoft's site that is supposed to lead me to some documentation or update for an older system and instead I get some garbage like "We're sorry. This page/update is no longer available. Update to Windows 10 today! It's up to date, fast and secure!" My response? Sure. When .... freezes over. +1 Amen. +1
  19. 7 points
    New build of Serpent/UXP for XP! Test binary: Win32 https://o.rths.cf/basilisk/basilisk52-g4.2.win32-git-20190525-315ffd563-xpmod.7z Win64 https://o.rths.cf/basilisk/basilisk52-g4.2.win64-git-20190525-315ffd563-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-20190525-315ffd563-xpmod.7z Win64 https://o.rths.cf/palemoon/palemoon-28.6.0a1.win64-git-20190525-315ffd563-xpmod.7z Official repo changes since my last build: - Unhook Unboxed Objects option (3ded48cbe) - remove unboxed code chunk (wip1) (9a3141515) - Remove initial chunk of Unboxed Objects machinery part 2 (3b36a43e8) - Remove Unboxed Objects in ScalarReplacement (d40bcc350) - Remove unboxed objects from GC (5fd4b8726) - Remove unboxed object code from iteration. (8feffe707) - Remove array header (a5c2961c4) - Remove Unboxed Objects from vm/ Part 1 + fix deprot (543fa1674) - Remove unboxed object code from jit, Part 1 (fa8bfa1a0) - Remove Unboxed Objects from vm/ - Part 2 (201d8ee48) - Implement array.flat and array.flatMap (162e22a7d) - Implement Symbol.prototype.description (41731a7f3) - Issue #971 - Fix browser.link.open_newwindow functionality in Pale Moon (f9dc4e8cc) - Merge pull request #1097 from FranklinDM/pm_external_sametab-work (a1f96f11d) - Merge pull request #1091 from MoonchildProductions/remove-unboxed (be8d03cf1) - Remove a stubbed telemetry function from app AUS. (bb5e0a1be) - Enable double buffering when using XRENDER. (2fd300786) - Merge pull request #1100 from Ionic/bugfix/xrender-flicker (372fccddf) - Issue #1104 - Set the browser's opener when adding a new tab - This modifies `loadOneTab` and `addTab` to accept an opener - This code was adapted from Basilisk's copy of tabbrowser.xml without the refactored code changes (which is a lot more involved as it divides addTab's functions into multiple functions) (797697e26) - Issue #1104 - Pass an opener to loadOneTab in the openURI function (10318170b) - Issue #1101 - Support gzip-compressed SVGs in OpenType+SVG fonts (73f9b2c70) - Merge pull request #1108 from g4jc/svg_opentype (f8157b8a6) - Merge pull request #1105 from FranklinDM/pm_uri_tabbrowser-work (f0e357608) - Merge pull request #1099 from adeshkp/remove-telemetry-func (315ffd563) My changes since my last build: - ported changes from mozilla upstream: bug1351303, bug1352235, bug1371508, bug1430268, bug1352734
  20. 7 points
    alright it works. new Saturday binaries will work with 1.3 compat mode.
  21. 7 points
    Although this could go in the "browsers" thread, I didn't want this to get buried in the many pages of that thread. After some detective work, I've located Firefox 52.9.1 ESR buried on Mozilla's servers and confirmed it works on Windows XP. The 52.9.0 version is dated 25-JUN-2018 while the 52.9.1 version is dated 06-SEP-2018. The links are https://download-origin.cdn.mozilla.net/pub/firefox/tinderbox-builds/mozilla-esr52-win32/1536215521/firefox-52.9.1.en-US.win32.installer.exe and alternate link is https://archive.mozilla.org/pub/firefox/tinderbox-builds/mozilla-esr52-win32/1536215521/firefox-52.9.1.en-US.win32.installer.exe. I've also added it to my FTP: http://sdfox7.com/xp/sp3/EOL/firefox-52.9.1.en-US.win32.installer.exe I'm not sure why Mozilla didn't make this release public, but ENJOY! Note that I don't use XP 64 bit but I would expect the same results.
  22. 7 points
    Adobe Flash Player 32.0.0.192 has been released today (confirmed working with Windows XP SP3/Windows XP x64 SP2) Internet Explorer ActiveX: http://fpdownload.adobe.com/get/flashplayer/pdc/32.0.0.192/install_flash_player_ax.exe Mozilla Firefox NPAPI (also for Opera Presto/Google Chrome 44 and earlier): http://fpdownload.adobe.com/get/flashplayer/pdc/32.0.0.192/install_flash_player.exe Google Chrome 45 through 49 PPAPI: http://fpdownload.adobe.com/get/flashplayer/pdc/32.0.0.192/install_flash_player_ppapi.exe
  23. 7 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.
  24. 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.
  25. 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!"
  26. 7 points
    @VistaLover Kind and helpful people like you make this forum warmer and inviting to visit more frequently. Nasty egoboosters having fun trampling over innocent others make forums icy and hostile. Keep your 'longwinded' postings coming please. Always very valuable and interesting! Although I usually don't react, but appreciate them, very much :)
  27. 7 points
    New out-of-cycle release of Adobe Flash Player 31 came today: 31.0.0.153 (tested/working on Windows XP SP3 and XP x64 SP2) Internet Explorer ActiveX: http://fpdownload.adobe.com/get/flashplayer/pdc/31.0.0.153/install_flash_player_ax.exe Mozilla Firefox NPAPI (also for Opera Presto/Google Chrome 44 and earlier): http://fpdownload.adobe.com/get/flashplayer/pdc/31.0.0.153/install_flash_player.exe Google Chrome 45 through 49 PPAPI: http://fpdownload.adobe.com/get/flashplayer/pdc/31.0.0.153/install_flash_player_ppapi.exe
  28. 7 points
    +1. Let's let Roy concentrate solely on that, which is of paramount importance to both XP and Vista communities.
  29. 6 points
    *UPDATE!* I have disabled two non essential options regarding the management of SVG layers: svg.display-lists.hit-testing.enabled and svg.marker-improvements.enabled. They seem to improve the browser's responsiveness and apparently don't affect the way sites behave. Archive build is n2d. 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 UPDATE: A little tip I discovered that there are three parameters that for some reasons, the patch ignores, but they can be edited manually in the about:config. Here they are: image.mem.max_decoded_image_kb - 512000 browser.urlbar.maxRichResults - 1 browser.sessionstore.restore_on_demand - False While it's not strictly compulsory to reduce the awesome bar to just one entry, I do it to save RAM. It's important to set the max decoded image memory to 512000 though, as that further speeds up images rendering. For some reasons, the browser ignores just these three parameters. But it's just a quick fix, just open about:config and edit the parameters above. 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.6.9.32 or v2.6.9.27 for New Moon, and v2.9.0.9 for Firefox 45 ESR SSE) Decentraleyes 1.4.2 Bluhell Firewall 2.5.3 UAControl 0.1.3.1.1 (To change the user agent on the fly, per website) uBlock Origin 1.10.0 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!
  30. 6 points
    New build of Serpent/UXP for XP! Test binary: Win32 https://o.rths.cf/basilisk/basilisk52-g4.2.win32-git-20190615-c9edf588e-xpmod.7z Win64 https://o.rths.cf/basilisk/basilisk52-g4.2.win64-git-20190615-c9edf588e-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-20190615-c9edf588e-xpmod.7z Win64 https://o.rths.cf/palemoon/palemoon-28.6.0a1.win64-git-20190615-c9edf588e-xpmod.7z Official repo changes since my last build: - Add Atomics.notify instead of Atomics.wake according to revised spec. (284b4cffd) - Add Yandex (ru) search plugin (c9edf588e) My changes since my last build: - import change from mozilla upstream: Bug 1384330 - Blocking the mozAddonManager when pref 'privacy.resistFingerprinting.block_mozAddonManager' is true. r=arthuredelstein,mossop (f05d85ff6) - Move app.feedback.baseURL pref to branding (a7d2a6260) - Move app.feedback.baseURL into branding prefs (f4b8b0d90) - Move app.feedback.baseURL here and point to MSFN (8584b233f) - Merge pull request #4 from Mathwi/custom (044e258d9) - revert "Remove e10s code from browser widget. (083d322b7)" to keep e10s useful. (ef715102e)
  31. 6 points
    Introduction: Here, you will find a list of AMD/Intel CPUs/chipsets and Intel/NVIDIA/AMD GPUs which support Microsoft® Windows Vista™. If you have any additions that aren't currently listed, feel free to reply with them and they will be added as soon as possible. Supported CPUs: Intel (Desktop/Server): Note: Windows Vista has been known to work with Pentium III and even some Pentium II processors, however this configuration is extremely suboptimal and the OS is practically unusable on these processors, so using at least a Pentium 4 (Prescott), plus installing Windows Vista Service Pack 2 is recommended for acceptable performance. Intel Pentium 4 (Prescott, 2004-2005) *x64 is only supported from the Pentium 4 505 Processor and newer Intel Pentium 4 Extreme Edition (Prescott, 2005) *Supports both x86 and x64 Intel Pentium 4 HT (Northwood, 2003-2004) *x86 only Intel Pentium 4 HT (Prescott, 2004-2005) *x64 is only supported by F-series, 5x1, 517, 524 and few OEM models in E-series (SL7QB, SL7Q8) Intel Pentium 4 HT (Prescott 2M, 2005) *Supports both x86 and x64 Intel Pentium 4 HT (Cedar Mill, 2006) *Supports both x86 and x64 Intel Pentium D & Pentium Extreme Edition, all models Intel Celeron, all Netburst-based models (Williamette & Northwood-128, 2002-2003) *x86 only Intel Celeron D (Prescott, 2004-2005) *x64 only supported by 3x1, 3x6, 355 models Intel Celeron D (Cedar Mill, 2006-2007) *Supports both x86 and x64 Intel Celeron *all Core-based and newer models up to Ivy Bridge based Celerons; Braswell/Haswell and later do not properly work with Vista. Intel Core 2 Duo, all models Intel Core 2 Extreme, all models Intel Core 2 Quad, all models Intel Pentium up to Sandy/Ivy Bridge G series processors; Haswell and later do not properly work with Vista. Intel Core i3 *all models up to 3rd generation Ivy Bridge processors; Haswell and later do not properly work with Vista. Intel Core i5 *all models up to 3rd generation Ivy Bridge processors; Haswell and later do not properly work with Vista. Intel Core i7 *all models up to 3rd generation Ivy Bridge processors; Haswell and later do not properly work with Vista. Intel Xeon 1.4 "Foster" - Intel Xeon 3.2 "Gallatin" *x86 only Intel Xeon, all models from 2.8 "Nocona" to 3rd generation Ivy Bridge Xeon processors; Haswell and later do not properly work with Vista. Intel (Mobile): Intel Pentium M, all models *86 only Intel Pentium 4-M, all models *x86 only Mobile Pentium 4, all models *x86 only Mobile Pentium 4 HT, all models *x86 only Intel Atom *all models up to Bonnell microarchitecture (2012); Silvermont (2014) and later do not properly work with Vista. Intel Core Solo, all models Intel Core Duo, all models Intel Core 2 Solo, all models Intel Core 2 Duo, all models Intel Core 2 Quad, all models Intel Core 2 Extreme, all models Intel Pentium up to Sandy/Ivy Bridge mobile processors, Haswell and later do not properly work with Vista. Intel Core i3 *all models up to 3rd generation Ivy Bridge processors; Haswell and later do not properly work with Vista. Intel Core i5 *all models up to 3rd generation Ivy Bridge processors; Haswell and later do not properly work with Vista. Intel Core i7 *all models up to 3rd generation Ivy Bridge processors; Haswell and later do not properly work with Vista. AMD (Desktop/Server): AMD Athlon 800 - Athlon 1000 (Pluto/Orion, 2000) *x86 only AMD Athlon 800 - Athlon 1400C (Thunderbird, 2000-2001) *x86 only AMD Duron 800 or later (2000-2003) *x86 only AMD Athlon XP, all models (2001-2003) *x86 only AMD Athlon 64, all models AMD Athlon 64 X2, all models (X2 & K10) AMD Phenom, all models AMD Opteron, all models AMD Sempron (Palermo, Socket 754; July/August 2005) *x64 only supported by all models with an OPN ending in BX and CV) AMD Sempron (Palermo, Socket 939; October 2005) *x64 only supported by all models with an OPN ending in BW AMD Sempron "Manilla" or later, all models AMD FX (Bulldozer Family), all models AMD Ryzen (all Summit Ridge models; Raven Ridge has yet to be tested) AMD (Mobile): AMD Mobile Sempron, all models (2003-2006) *x86 only AMD Mobile Athlon 64, all models (2004-2005) AMD Turion 64, all models (2005) AMD Kite Platform - AMD Carrizo Platform, all CPUs & APUs (2006-2015); Bristol Ridge (2016) may work but has yet to be tested. Supported GPUs: Intel GPUs: Intel 915GM/GMS will work with Windows Vista by using XP drivers, however Aero Glass isn't supported due to lack of WDDM drivers. Intel GMA 950 (Desktop: 945GC, 945GZ, 945G; Mobile: 945 Family) or newer, last Intel GPU to support Vista is Intel HD 4000 series (Ivy Bridge; Desktop and Mobile). Download Intel HD 4000 Graphics drivers for Vista here. ATI/AMD GPUs: ATI Radeon 9250 and all later GPUs released prior to the 9500 will work with Vista using XP drivers, however Aero Glass isn't supported due to lack of WDDM drivers. ATI Radeon 9500 or later; last AMD GPU to support Vista is AMD RX 300 series; drivers are coming soon. The first official version of ATI Catalyst to support Vista is version 7.1. The last official version of AMD Catalyst to support Vista is version 13.12 (Download: 32 bit 64 bit). However, newer versions up to 15.6 Beta for Windows 7 can be modified to work on Vista. View this thread for more details. NVIDIA GPUs: NVIDIA GeForce 5200 and later; last NVIDIA GPU to officially support Vista was the GTX 980 along with driver version 365.19. Download here: 32 bit 64 bit - Note: Vista 3D Vision support was dropped around version 310.00. The GTX 1060, 1070, and 1080 can also be made to work with Vista, as driver versions up to 372.70 work with Vista, albeit not officially supported by NVIDIA. Download here: 32 bit 64 bit - Note: DirectX applications aren't properly utilized by these drivers under Windows Vista, so this will cause a bottleneck in performance over using the GTX 980 or older, where the 365.19 drivers (more optimized for Vista as they're officially supported) can be used. Final Apple Mac Computers to support Vista via Boot Camp: iMac; all Late-2009 models Macbook Air; all Mid-2009 models (32-bit only) Macbook and Macbook Pro; all Mid-2010 models Mac Mini; Mid-2010 (This is the only Mac Mini to support Windows Vista 64-bit; earlier models are 32-bit only.) Mac Pro; Mid-2010 Miscellaneous Hardware: Looking for an Xbox One Controller driver for Windows Vista? View this thread for download + how to install (HUGE THANKS TO @GTAGAME for this.) Download Elgato HD 60 S Capture Card drivers here - to install, extract the exe with 7-ZIP and manually install the drivers in Device Manager (thanks again to GTAGAME for pointing this out).
  32. 6 points
    I have always thought that having the latest is never the best. The latest operating system (or now version of Windows 10) is the worst thing you can have for security. Computers must be updated but not to the latest version. For example, it is better to have Windows 1803 updated than 1809 updated. Microshit uses our computers as a test bench and the correct updates are passed on to companies after 4 months or more. The proof of this is in the Windows 10 itself, update options and selection of the download semi-annual channel.
  33. 6 points
    Microsoft Update offered me two suppsedly important updates for Office 2010 on Windows XP a couple of days ago, KB2863821 and KB4461522. They installed fine, but the next day I came to use Word, and it would not run, with the error message - Application popup: winword.exe - Entry Point Not Found : The procedure entry point GetDateFormatEx could not be located in the dynamic link library KERNEL32.dll. This was followed by "The operating system is not presently configured to run this application". I quickly found that no Office programs would now run, with the same error messages. I removed the two updates, and all returned to normal. I have no idea which of the updates caused the problem, and I haven't been offered either of them again so far, but if you are offered them, beware as they may well completely break your Office installation!
  34. 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 !
  35. 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)
  36. 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.
  37. 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.
  38. 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)
  39. 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.
  40. 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.
  41. 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!
  42. 6 points
    no, I'll still build browsers weekly.
  43. 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)
  44. 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.
  45. 6 points
    I have hard time with influenza and took me time to fix database server issue.
  46. 6 points
    MKVToolnix announced that they were going to officially drop XP with version 9.x in 2015. Luckily, the next version v.10.0 was working on XP anyway. Today I decided to update it after a while and I found out that it wasn't working anymore. I took a look at the source code and luckily it didn't use anything weird and it was possible to compile every component targeting XP. As to the UI, this one was tricky. The mkvextractgui hasn't really been modified during the latest commits and relies on old calls, so it was easy to compile. As to to the mkvmergegui (mkvtoolnixgui), in the main branch it has been update to use functions available on Windows 7 only (not even Vista!). I was kinda curious to see what they did and they basically broke Vista and XP compatibility with the GUI to implement some "fancy" W7 loading bars and a few totally useless stuff. Anyway, I re-used the code from version 10.0 for the mkvmergegui ('cause it was XP compatible) and made it work with the new components and... guess what? It works. It's gonna complain about a "mismatch" between the GUI version and the components version as soon as you launch mkvtoolnixgui, but just ignore it and use the program 'cause it's working flawlessly. I just muxed a few .ts and .mp4 files into .mkv and it worked. I even extracted subtitles from a few .mkv files and it worked. Let me know if you find bugs and please note that this is an unofficial version, so DO NOT update via the GUI and DO NOT report bugs on the official MKVToolnix site, but only here. v25.0: REMOVED v26.0: REMOVED V27.0: REMOVED V28.0: REMOVED V29.0: https://mega.nz/#!GJcmUS6R!FvWCCGWxStx5_23MSSJ8l_PC0eJOPaGFaMRtN2XTZFM
  47. 6 points
  48. 6 points
  49. 6 points
    I was recently on a tour to Ignalina Nuclear Power Plant and saw some PCs running XP
  50. 6 points
    to fix recaptcha issue: for PM27 users: 1. goto about:config, add new Boolean value named "dom.messageChannel.enabled" and set it "true". 2. reload the page that has recaptcha next PM27 build will address it.
×
×
  • Create New...