Jump to content

NotHereToPlayGames

Member
  • Posts

    6,746
  • Joined

  • Last visited

  • Days Won

    83
  • Donations

    0.00 USD 
  • Country

    United States

Everything posted by NotHereToPlayGames

  1. Agreed and many thanks. Yes, 360Chrome has been a game-changer for me as well (unsure how long it will last). I'd be curious on XP versus Vista versus 7. My paradigm is that NEW vulnerabilities are created only for NEW operating systems. How many people in the entire universe spends their time seeking out vulnerabilities and seeking to gain access to Win 3.1 systems? One also has to remember that CVE "vulnerabilities" are often times "theoretical" and have never been encountered "in the wild". Don't misread, we must "safeguard" and all of us MSFN XP users have our own lines of defense - we're not running the streets naked, as the saying goes.
  2. In a nutshell - not relevant. For one, that only tracks "official Chromium", not Chromium Forks. Further, this sort of "vulnerability tracking" is only relevant to those that do not run XP. If you are "concerned" or "worried" when you visit a "report" such as that, then XP IS NOT FOR YOU. Neither is Win10, as far as that goes. When a user opts to run "older" Operating Systems and in turn Browsers working on Older NT-Family OSes (ie, the TITLE OF THIS THREAD), that user is aware and ACCEPTS the RISKS associated therein.
  3. I have opted to do a 13.5.2036 in the coming days/weeks. No real timeline on estimated completion.
  4. In rethinking this, I am leaning towards a possible Build 2036 Rebuild 1 in the near future. 13.5.2022 was released in May 2022 and there were THREE releases in ELEVEN DAYS. Four MONTHS passed before 13.5.2036 was released in September 2022. We are now just shy of SEVEN months since Build 2036 was released. My HOPES are that upstream is officially at a "final" v13.5. At any rate, the several months and no "three releases in eleven days" is more reassuring that Build 2036 didn't INTRODUCE bugs.
  5. Rebuild 8 is still to be considered "latest and greatest". I've uploaded Rebuild 6 so that Anbima can verify that rebased chrome.dll is or is not the cause of other programs now being problematic.
  6. Links for Rebuild 6. Not rebased. But will also be missing other miscellaneous changes made along the way as I do not document "change logs" for such a niche project. https://www.dropbox.com/s/bwtlmyoebk4j0hc/360ChromePortable_13.5.1030_rebuild_6_ungoogled.zip?dl=1 https://www.dropbox.com/s/sn3s4ra40gby6cp/360ChromePortable_13.5.1030_rebuild_6.zip?dl=1
  7. I'll upload this evening. I wouldn't suspect the rebase to cause errors with other programs but doesn't hurt to verify.
  8. My course of action thus far has been to run XP x64 as my Host and only run Win10 as a VirtualBox Guest. So far, I've needed that Win10 VM zero times. But yeah, I'm prepared for the day that I will have to resort to it just to reconcile a credit card statement.
  9. lol Figures something "kiddy-like" [ie, "child-like"] (kitty-like?) that exists. I still define that as "for the gamer" and I've not played any games since the Mrs. Pac-Man table-top unit was no longer at the local Dairy Queen in the late 80s or early 90s.
  10. Looks to me like an "identity crisis" web browser. Intended customer is the "gamer" crowd that want their web browser to look like a "game". Not for me, but "to each their own". All it's missing is a machine gun at the bottom that you aim at your mouse-clicks using a "game controller" instead of a mouse.
  11. Very possible. That's why two of my laptops now have Win10 instead of XP. So by the time 2025 rolls around, I should have it tweaked and customized to my liking. I have no plans. Don't let the build number fool you, it has no "real world" benefit over the previous TWENTY (not an actual count) versions of v13.0 and v13.5 combined. All the same exact v86 rendering engine with just Chinese "stuff" thrown in that we strip out anyway.
  12. I have my own modified version of DcBrowser. But I am not a fan of DcBrowser, it's a step "backwards" (v75 versus v86), I don't like the GUI, and so I've abandoned it before sharing it publicly.
  13. That seems like a step backwards when we have v86 and v87 forks available.
  14. I personally prefer the SQUARES. Why install a font that I can not read?
  15. I don't see anything! If the web site loads and functions, then who cares if it throws up some "banner" saying they don't "support" your browser. Those "banners" citing "support" despite the web site "working" is about as usefull as the web site owner plastering a banner on what sports team s/he "supports".
  16. Technically, v11 is faster. It launches faster, it scores faster, and it passes more checks at BrowserAudit. BUT it's too old for me to use because my banking sites will not function on v11. What I don't understand is the hype surrounding DcBrowser and MiniBrowser, I've never liked either one but web browsers are always always always "in the eye of the beholder".
  17. My Google Drive works perfectly fine in v13.5. What part of Google Drive is not working for you?
  18. Not likely. And I say that as an XP user. I think we XP users think far too highly of our influence in this world.
  19. In tracking something else down (below pic), I may have found the bookmark star clickety-clickety-clickety. But may be a long while before I upload another round.
  20. Ah, thanks. I have not been able to replicate here either. Well, I did once but I have not been able to repeat it consistently. But I also cannot understand why somebody would click the star "repeatedly".
×
×
  • Create New...