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 04/26/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. 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."
  4. 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
  5. 8 points
    I also don't see how frank was rude at all, sounds like you could use an emotional support animal.
  6. 8 points
    I see no rudeness whatsoever in Frank's post. Yours, OTOH, is unnecessarily offensive. People nowadays are too oversensitive...
  7. 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.
  8. 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."
  9. 7 points
    alright it works. new Saturday binaries will work with 1.3 compat mode.
  10. 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/
  11. 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!
  12. 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 !
  13. 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)
  14. 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.
  15. 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.
  16. 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.
  17. 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)"
  18. 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:
  19. 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.
  20. 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
  21. 5 points
    Hey - party's not over. Here's a beer!
  22. 5 points
    Well, you're much welcome to vent up. So am I to rant, right? Yeah, it goes like this: 1.) All the issues you mentioned have solutions described in detail in this very forum. 2.) Athough it's easy to filx the Word 2010 issue, one can remain using Word 2000 (or even Word 97) for most if not all tasks commonly performed with it. Same goes for XL and Powerpoint. 3.) Al that is required is to arm oneself with patience and read the threads where the solutions are described. XP went EoS, then POSReady 2009 went EoS. MS did it because it was in their power to do so and they've decided it was in their interest to do so. Regardless of what any of us thinks about it. So it's up to us, the die-hard users, to support ourselves 'n one another... it's less confortable than leaving all responsibility fall on MS. Then again, for one who loves XP or just isn't confortable (or able) to cave in, it sure is worth it. One may whine. Then again, one may stand up and fight. Long live XP!
  23. 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)
  24. 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.
  25. 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.
  26. 4 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
  27. 4 points
    He's gonna see whether you are a Winnie the Pooh fan and judge you. xD https://www.theguardian.com/world/2018/aug/07/china-bans-winnie-the-pooh-film-to-stop-comparisons-to-president-xi
  28. 4 points
    Well, the title of this thread (in the form of a question) is a tad misleading ; if the real question was Can you establish TLS 1.3 connections under Windows XP? then the answer, of course, is YES . Both UXP browsers (New Moon 28, Serpent 52.9.0), the Moebius fork (Serpent 55.0.0), the Tycho fork (New Moon 27) and probably other @roytam1's forks all support the final TLS 1.3 draft (RFC8446), as well as all three cipher suites associated with TLS 1.3: TLS_AES_128_GCM_SHA256 (0x1301) TLS_AES_256_GCM_SHA384 (0x1302) TLS_CHACHA20_POLY1305_SHA256 (0x1303) ; you can test TLS 1.3 support of these browsers with https://tls13.pinterjann.is/ https://swifttls.org/ https://cert-test.sandbox.google.com/ (and a few other test URLs...). BTW, the NSS library in these browsers was recently downgraded from v3.44 Beta to v3.43 stable release; perhaps @roytam1 could share a word (or two ...) why that was necessary ... Additionally, I was recently informed that the excellent project ProxHTTPSProxy by @heinoganda has indeed achieved TLS 1.3 support under XP for the type of browsers (IE8, Google Chrome 49 and, possibly, earlier) that don't come with their own TLS support but rely upon system libraries for secure connections; so TLS 1.3 in itself shouldn't be an issue... But what is indeed specific is the configuration of linked test server, https://tls13.1d.pw/ It is no coincidence that a Russian member of this forum brought this up, because, it turns out that, the administrator of said test server is a Russian guy, Александр Венедюхин ! In fact, he maintains a blog where he documents this project and the TLS 1.3 test configuration of the server; original articles can be found at: https://dxdt.ru/2018/08/05/8597/ https://dxdt.ru/2019/01/26/8672/ As I'm not at all fluent in Russian (), I had to enlist the help of (evil ) Google, but what the heck... : https://translate.google.com/translate?hl=en&sl=ru&tl=en&u=https://dxdt.ru/2018/08/05/8597/ https://translate.google.com/translate?hl=en&sl=ru&tl=en&u=https://dxdt.ru/2018/08/05/8597/ I don't consider myself proficient in the field of cryptography and/or secure connections, but what I gathered from the translated text was that the server is configured to send a special HelloRetryRequest response to force a renegotiation of connection parameters; the implementation of Encrypted Server Name Indication (ESNI) along with non-ECDH manifested a bug in Mozilla's NSS library, so that is probably why the Firefox forks won't connect currently to that specific test server! (they yield a SSL_ERROR_RX_MALFORMED_SERVER_HELLO error code ). Hopefully, the reported bug will be fixed in a future NSS version, if/when that is applied to UXP, we'll have successful connection in the UXP forks... Frankly, TLS 1.2 is still predominant, but with 1.3 steadily gaining ground; this specific connection test is but a margin case where 1.3 is involved, so I won't be losing any sleep over it...
  29. 4 points
    Nanobot informs me elsewhere, that DoaJC_Blogger guy is working to bring Chromium 76 to Win Xp: https://browser.taokaizen.com/forum/viewtopic.php?p=3219#p3219 https://browser.taokaizen.com/forum/viewtopic.php?t=2766
  30. 4 points
    Some months ago I complained about the poor performance of Hotmail after their last update became final. They gave me an URL to access the older version, which works much better with XP compatible browsers. It also solves the problem with Chrome 49. https://outlook.live.com/owa/?path=/fb
  31. 4 points
    ... As it finally turned out, it is yet again another case of intentional/artificial block of Vista by M$ ; the blocking code lies somewhere inside the compiled .EXE setup, but it's obviously absent in the unpacked .MSI installer.I do wonder if it's still possible to install 4.6.2 Final by running the Setup.exe file (86.1KB) that exists inside the (unpacked) directory; an inspection with Resource Hacker reveals it does indeed support Vista in its manifest: <compatibility xmlns="urn:schemas-microsoft-com:compatibility.v1"> <application> <!-- Windows 10 --> <supportedOS Id="{8e0f7a12-bfb3-4fe8-b9a5-48fd50a15a9a}" /> <!-- Windows 8.1 --> <supportedOS Id="{1f676c76-80e1-4239-95bb-83d0f6d0da78}" /> <!-- Windows 8 --> <supportedOS Id="{4a2f28e3-53b9-4441-ba9c-d69d4a4a6e38}" /> <!-- Windows 7 --> <supportedOS Id="{35138b9a-5d96-4fbd-8e2d-a2440225f93a}" /> <!-- Windows Vista --> <supportedOS Id="{e2011457-1546-43c5-a5fe-008deee3d3f0}" /> </application> </compatibility> I guess if that doesn't work, on a 32-bit platform one should run netfx_Full_x86.msi (in the unpacked directory); as mentioned by Osman, in the root of the unpacked setup one can see prerequisite windows updates for Win8 (KB3151804), Win8.1 (KB3151864) and Win10 (KB3151900), but, surprisingly, not for Win7 (and, of course, none for WinVista, which the package doesn't officially support) - in any case, it should be stressed that the (somewhat unorthodox) 4.6.2 install shouldn't be attempted on a Vista system which isn't fully updated (SP1+SP2+all subsequent updates at least until EoS on April 2017), just for good measure... All in all, a very positive outcome from a joint effort, started by @Osman Kovan and joyfully concluded by @WinClient5270! Cheers PS: I couldn't help noticing how a 59.1 MiB file (NDP462-KB3151800-x86-x64-AllOS-ENU.exe) blows up to more than 1.62 GiB (!) when expanded!
  32. 4 points
  33. 4 points
    New build of Firefox 45ESR SSE: test binary: https://o.rths.cf/gpc/files1.rt/firefox-45.9.15-20190511-bdebcdb5e-win32-sse.7z repo: https://github.com/roytam1/mozilla45esr Changes since my last build: - import changes from tenfourfox: - #446 + #334: trim refresh driver further; restore old Tele removal (4594eee51) - #446: cap default frame rate to 30fps (based on M1503339) (9465ea36d) - #547: block modal HTTP auth DOS M1312243 M377496 + glue code (d60d9721f) - #550: pref on mediasource for mp4 (37789a58a) - #399: null check in FindNearestCommonAncestorFrame from PM 978 (23f303460) (067eb934c) - nss: update nss to hg rev e5e10a46b9ad with vc2013 hackfix (811e2980a) - nss: update nss to hg rev 2d6adc7d8bfc with vc2013 hackfix (64d6370ee) - nss: go back to 3.43 release (319708fd5) - import changes from tenfourfox: - #551: M1538402 M1516325 M1544670 (a5f18b580) (without nspr changes) - #551: M1538619 M1538736 M1542829 M1543617 M1531346 M1540166 (54aa2d7cc) - #446: fine, eat your placebo and enjoy it (f6dd8303f) (37e403685) - import changes from tenfourfox: - #551: M1536768 M1546327 (4af72ac8c) (with vc2013 fix) - #551: update certs, pins, TLDs (bc5094b91) (bdebcdb5e)
  34. 4 points
    Today marks the 20th anniversary of the release of Windows 98 SE, which was on May 5th, 1999! The OS that changed my life forever! Share your birthday wishes and OS experiences here! Many great things awaits...
  35. 4 points
    Just publishing a short comprehensive guide I made on how to run Steam on Windows XP/Vista after 1 January 2019... (as opposed to reading the relevant chunks of the steam thread) It's not very hard, as you only need to download THIS archive, and then extract it, and you will have a working steam. On Windows XP at least you'll need to use ProxHTTPSProxy or a similar solution if you want to get game pictures/icons to load. ( Such as the version Heinoganda complied) Note: With using ProxHTTPSProxy I've noticed that sometimes I need to click 'retry' a few times when logging in. (Video version I made on YouTube)
  36. 4 points
    thats how build system works, things are done automatically once the command is issued. mozilla's build system can't handle different exe name when --enable-official compile time option is specified or not. not to mention keeping same exe name and same profile prefix for compatibility. no thats not. rn10950 changed version number in repo for a long time before I create a build. and the reason of delaying official retrozilla build from rn10950 is that, he changed the program's name, but not everything in the source, that makes program not fully functional and makes TLS connection fails.
  37. 4 points
    I quote myself to give you a little update. It may look like as if we are doing nothing, but we're not. @someguy25 asked me about Chromium 74 and since I really love Chromium, we re-forked it once again and I tried to backport for the 5th time. Compiling it using v141_xp and targeting XP leads to nowhere as the new SDK does not compile, however commenting out the sandbox and some other parts of the code made it compile, however the code was unusable as 27 calls were missing (including - but not limited to - the kernel). By removing many unnecessary components and taking it to its very bone, I managed to lower the number down and by linking it to the @Dibya modified kernel we managed to get this number even lower. Right now, the only missing calls are QueryThreadCycleTime, SymGetSearchPathW, SymSetSearchPathW, SHGetKnownFolderPath, SetProcessDPIAware, however the SymGetSearch can be delayed and not loaded at start-time and SetProcessDPIAware can be faked to equal true all the time, so the only really meaningful kernel call that has to be implemented and backported is QueryThreadCycleTime, 'cause once we get that and we fake SetProcessDPIAware, we're gonna get Chromium74 open and display the UI, which would be totally positive sign. BOOL QueryThreadCycleTime( HANDLE ThreadHandle, PULONG64 CycleTime ); It refers to the realtimeapiset.h which works on Windows7 and greater only and it has two parameters: ThreadHandle, which has either the PROCESS_QUERY_INFORMATION or PROCESS_QUERY_LIMITED_INFORMATION access right and CycleTime which is the number of CPU clock cycles used by the thread and it includes cycles spent in both user mode and kernel mode. In order to avoid to try to use it, I tried to convert the Thread32 function and use the elapsed time, however I didn't manage to get positive results as it's important to know the exact clock cycles as it varies between CPUs, for instance some CPUs will vary the frequency of the timer when changing the frequency at which the CPU runs and others will leave it at a fixed rate, so asserting it will almost certainly lead to wrong results (which is what happened in my case). Unfortunately I don't have much time to dedicate at this, nor my "virtual XP colleagues" like Dibya, Samuel and Peter do as we're all very busy for a reason or another and we don't also wanna become blind by staring at "apparently meaningless" lines of code... I'm sorry that my fifth attempt to backport Chromium led to nowhere once again... Good night, Frank...
  38. 4 points
    It's ironic how people decry the older operating systems like W2k Pro as outdated, yet can't even trust newer Windows 7 or Windows 10 systems far enough to let them update. These days, generally speaking, lots of new stuff sucks--because people take it for granted that new stuff is better. From that presumption, lazy thinking ensues, and movement replaces progress. So, although we still "go," we go backwards instead of forward. Windows illustrates the regression.
  39. 3 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.9, 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-20190525-7f9cc28f1-xpmod.7z Win64 http://o.rths.cf/basilisk/basilisk55-win64-git-20190525-7f9cc28f1-xpmod.7z repo: https://github.com/roytam1/basilisk55 Repo changes: - ported changes from mozilla upstream: bug1351303, bug1352235, bug1371508, bug1430268, bug1352734 (7f9cc28f1)
  40. 3 points
    I prefer my browsing habits sent to China than to Google anyway. And I never keep logged in to it... just for Gmail, if at all, when needed.
  41. 3 points
    It does seem to also work on Windows XP x64 SP2 with 360 Extreme Explorer, therefore it should work on all Windows XP editions.
  42. 3 points
    New build of Serpent/UXP for XP! Test binary: Win32 https://o.rths.cf/basilisk/basilisk52-g4.2.win32-git-20190518-c72afc3c8-xpmod.7z Win64 https://o.rths.cf/basilisk/basilisk52-g4.2.win64-git-20190518-c72afc3c8-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-20190518-c72afc3c8-xpmod.7z Win64 https://o.rths.cf/palemoon/palemoon-28.6.0a1.win64-git-20190518-c72afc3c8-xpmod.7z Official repo changes since my last build: - When using XRENDER, create Xlib-based offscreen image surfaces. (996887f40) - Issue #1084 - Add null check for URL Bar in the writePlaceholder() method (8b7d91e51) - [PALEMOON] buildHelpMenu() is executed by the shared help menu but not all windows have the AppMenu (f857efc35) - Update sync clear history function to use new clear() API call. (a53ab3f34) - Merge pull request #1086 from zootboy/master (70c5719dc) - Remove deprecated appending of #-moz-resolution from Pale Moon and left over from nsMediaFragmentURIParser.h (c7dc667e6) - Merge pull request #1060 from Ionic/bugfix/scrolling-regression (413ba3bad) - Rip broken telemetry out of the app AUS. (1595ee7da) - Fix scroll bar orientation on MacOS (06f7a03ff) - Map IntersectionObserver rect to the correct viewport. (34d5483ac) - Merge branch 'master' of https://github.com/MoonchildProductions/UXP (f932fb94d) - Implement String.prototype.trimStart and trimEnd. (354c6dcee) - Add nullcheck. (c72afc3c8)
  43. 3 points
    @Blados, no, both architectures are supported. But the developers, when they throw support for Vista, complained that the code was very different and difficult to maintain. Due to hardware acceleration. I tried to run the MSI file - it sends to setup.exe . Setup.exe requires Windows 7. I modified the MSI file and installed it. With .NET 4.7.2 is installed. ... is not Win32 application. Alas.
  44. 3 points
    ... Yes, that is indeed the case - it appears that all three 4.6.x flavours (4.6.0 [final], 4.6.1 [final], 4.6.2 [final]) are being patched by the same .exe files! I can only speculate, but, as feared, the 4.6.2 Preview has an internal version number different to the stable/final release of 4.6.2, which renders it not eligible for further 4.6.x patches (that is if the patch files check for some sort of version ID of the installed 4.6.x package); in fact, inspecting the setup files, one sees: 4.6.2 Preview setup: NDP462-KB3120735-x86-x64-AllOS-ENU.exe => File version 4.6.1532.0 4.6.2 (Final) setup: NDP462-KB3151800-x86-x64-AllOS-ENU.exe => File version 4.6.1590.0 Of course, the real puzzle here is what was actually changed by MS so that 4.6.1532.0 installs under Vista SP2, but 4.6.1590.0 doesn't ; is it just an artificial block for NT < 6.1 ? So, the prudent thing here is to stay on Final 4.6.1, for which compatible Security and Performance Updates are being rolled-out by MS and which can be manually downloaded (& installed) from their Update Catalog . Let me, once more, thank you immensely for your precious time spent conducting those tests for me (and, of course, other Vista users); I have a 12 year old low-end Vista laptop (and the OS has already started kicking the bucket last February ), no VM software installed (and my total RAM is only 3 GB), so no practical way I could test myself - I would also hate to lose 4.6.1 and all its manually applied updates for the sake of testing the 4.6.2 Preview - I hope you understand... )
  45. 3 points
    Signed up here principally just to thank heinoganda for his MSE Updater tool. I'm using Window 7 Pro 64 with its XPMode 32bit running on a VM (Virtual Machine) and I installed MSE on that XP VM as an ideal fit for this sort of purpose. Automatic definitions updates and manual updates via MSE stopped working in 2016 but I've been happy enough to download the MSE AV definitions update mpam-fe.exe on a weekly basis and install it that way. I've been doing that mostly without problem for three years. But then this new install problem suddenly happened and over the last month I've had very little luck even finding out that it was a typically MS way of ending support for something. Not providing any particular warnings let alone reasons why it is going to happen. Just doing it and letting the user sort it out themselves. I was pointed here by a helpful guy on another PC forum where I'd posted about the problem and I'm very grateful to them for doing that. I can confirm that the v1.9 MSE Updater works on my system (as described). My MSE installation is now showing it is up to date with the latest definitions. Thank you.
  46. 3 points
    New New Moon 27 Build! 32bit https://o.rths.cf/palemoon/palemoon-27.9.6.win32-git-20190504-249ad075c-xpmod.7z 32bit SSE https://o.rths.cf/palemoon/palemoon-27.9.6.win32-git-20190504-249ad075c-xpmod-sse.7z 32bit noSSE https://o.rths.cf/palemoon/palemoon-27.9.6.win32-git-20190504-249ad075c-xpmod-ia32.7z 64bit https://o.rths.cf/palemoon/palemoon-27.9.6.win64-git-20190504-249ad075c-xpmod.7z source repo: https://github.com/roytam1/palemoon27 repo changes since my last build: - import change from rmottola/Arctic-Fox: - Bug 1140709: Add a second bounds check for checking that the index is actually positive (b79e7923f) - pointer style (32c997296) - Bug 1135042: Optimize SIMD.storeX/storeXY/storeXYZ in Ion (cb99e5f91) - Bug 1144108 - Fix debugger tests that are confused by GC zeal (b492b7fd0) - pointer style (0aae53f82) - more pointer style (a55165e9b) - Bug 1134150 - Don't check type sweeping generation when accessing an unboxed object's layout during nursery collections (5f184fb4a) (1c67f373e) - import change from rmottola/Arctic-Fox: - more boring pointer style (9855fa50f) - Bug 1128646 part 1 - Optimize calls to own property scripted getters (6b7da146a) - pointer style (6ef381028) - Bug 1137180 - Allow unboxed objects to be extended with new properties (dafccfa9d) (249ad075c)
  47. 3 points
    @LoneCrusader thank you for your input! I had just learned a bit of business English and I learned lots of words from your post!
  48. 3 points
    Is it open source? I can't find any Github/SourceForge/Codeplex project. If it's not open source, then it would have to be disassembled with IDA Pro, thus producing potentially wrong unreadable everlasting lines of code. I.e you are better off forking Chromium 69 from the official repository. That said, I don't see Chinese people willing to cooperate on open source; I mean, if you are going to make a spyware built into your browser, the last thing you wanna do as a company is to make it explicitly readable/obvious with open source code, right?
  49. 3 points
    @roytam1 <-- Maybe RT could upload and list some 'clickable' HTML files that (aim/open) reference this MSFN.org Support Thread. For the BNAVIGATOR Browser, for download here: https://o.rths.cf/boc-uxp/ (Added: At above URL -- RT did add a 'clickable' reference that opens THIS Support Thread. And makes clear that RT 'XP OS' Browsers are NOT Supported by PALE MOON in any way.) You could upload these four HTML files to URL above, naming them: bnaa1--CLICK-For-BNavigator-Browser-SUPPORT-Forum-(MSFN.org).html bnaa2--PALE-MOON-Forum-does-NOT-SUPPORT-the-BNavigator-Browser.html bnzz1--PALE-MOON-Forum-does-NOT-SUPPORT-the-BNavigator-Browser.html bnzz2--CLICK-For-BNavigator-Browser-SUPPORT-Forum-(MSFN.org).html Under a 'NAME' Sort, these HTML files would list TOP and BOTTOM, bracketing the dated 'bnav' Browser files (versions). http://rtfreesoft.blogspot.com/search/label/browser RT could also make similar HTML 'CLICK' additions at the above URL. This is something that could be done fairly quickly, as a response to Mr. Tobin. And It would show that RT is 'doing something' to minimize the problem of any CONFUSION that the RT 'BNAV' Browser is associated with PALE MOON Browser. NOT saying this is a full solution, just a possible reasonable suggestion for consideration. Feedback --> "It's a two-way street, pinhead." I knew that!
  50. 3 points
    Although I myself solved the problem, I would like to thank all the MSFN members who expressed their ideas in this 3D. Each proposed solution has contributed to the final resolution, if only to eliminate any possible alternative.
  • Create New...