Jump to content

NotHereToPlayGames

Member
  • Posts

    6,759
  • Joined

  • Last visited

  • Days Won

    84
  • Donations

    0.00 USD 
  • Country

    United States

Everything posted by NotHereToPlayGames

  1. Yes. I personally keep that option UNCHECKED.
  2. The most recent Arcticfox has no status bar. I didn't see any even when hovering over a link. Previous Arcticfox versions had the status bar always shown. The latest doesn't have any status bar. None at all. Not even on hover.
  3. Thanks. Have not tried the --no-sandbox parameter yet. The "disappearing act" does seem to only be v11 (which is unfortunate because it is my favorite because the GUI loads the fastest on my systems). But it's also completely random. I haven't found a repeatable do A, then B, then C to force it to happen.
  4. I disagree. Developers have the intellectual knowledge to know the probability of a "theoretical vulnerability" that will STATISTICALLY NEVER HIT A REAL-LIFE COMPUTER versus applying a patch that 100% STATISTICALLY DEGRADES PERFORMANCE. And you also know the large number of "patches" that tend to be graphic-based vectors and scalars, really nothing to do with "security". But that DEGRADE performance. I no longer follow the patches, but I do know that a very large number have NOTHING to do with "security". "Stability", perhaps. But not "security". At any rate, keep up the great work, it may appear that I'm "arguing" but I'm not trying to, just trying to paint the full picture.
  5. My v13 (and 13.5) crashed randomly with DEP AlwaysOff (I've not enabled DEP in over 20 years). I've yet to encounter any crashes with Accelerated 2D canvas disabled. You're on XP x86 SP2... I'm on XP x64 SP2 and XP x86 SP3... I wouldn't expect both our computers to behave identically...
  6. Well, the "security" answer WAS NOT AN ANSWER. It was a "copout", plain and simple. I *guarantee* you it will not be "reverted" - because that answer tells us that it's a THOUSAND different "patches" and cannot be tracked down to "a few", so the "security" answer was thrown out willy-nilly. Security is a RED HERRING. Tell people that changing a pixel color from white to black and that it was done for "security" and most people will BELIEVE YOU. Security schmacurity. Don't get me wrong, Roytam is doing it the way the MAJORITY of his followers prefer it, sacrifice PERFORMANCE for the sake of "security". It is a VALID approach! I am not trying to undermine that. But I take the opposite approach, I use OLDER versions of Roytam's browsers and prefer PERFORMANCE over "security". WE ALL HAVE THAT OPTION. Don't be "fooled" by the claim that newer offers more "security". Just my two cents. Greatly appreciate Roytam's work. It's all a matter of personal preference and we can all decide for ourselves if an older version best fits our needs or if a newer version best fits our needs.
  7. "theoritically"... "red herring"...
  8. Good news! I think! I've kinda avoided using v13 (still avoid v13.5 but for different reasons!) because v13 was randomly crashing (especially here at MSFN!) With Accelerated 2D canvas disabled, I've had this reply box open for an hour or so, had YouTube playing random videos, and had a Stylus stylesheet editor window open. I think Accelerate 2D canvas is what was causing my random crashes. Mileage may vary. Will continue to run v13 as default for the next couple of days for verification.
  9. Same here! Seems to me that only "attention-seeking" folks would really even CARE what the "count" is. The Facebook "like/dislike" crowd!
  10. Basemark Web 3.0 test locks up at 9/20 in 55 and completes in 52. Other than that it seems that 55 is microscopically faster than 52.
  11. Can we put a LIMIT to how many posts any single member can post in one day? waka waka waka
  12. Marquee was one of the most CHILDISH elements ever to exist! edit -- and thankfully, although able to "marquee" when creating this post, the forum software does REMOVE the marquee element.
  13. I'm curious as well. NEITHER one will work for American Water billpay. BUT it has always been my perception that 52 is more advanced that 55, despite the numbering confusion of 55 being higher than 52.
  14. I use VirtualBox version 4.3.28. I can't recall if there was a specific reason for using that version, but I tend to operate that way, I don't doubt that I selected it for a reason, just don't recall it offhand. All legally owned, during college days the bookstore sold all Microsoft products for $5 with student ID, here are the "size" of all of my VMs, kinda tells you how "bloated" Operating Systems have become - Win 3.1 == 20 MB Win 3.11 == 78 MB Win 98SE == 218 MB Win NT4 == 236 MB Win 2000 == 578 MB Win XP x86 SP3 == 635 MB Win 2003 == 1.07 GB Win XP x64 SP2 == 1.12 GB Win 7 x86 Enterprise == 1.28 GB Win 10 x86 LTSB 2016 == 1.84 GB Win 7 x86 (default install, no customization to install media) == 3.08 GB Win 10 x64 (default install, no customization to install media) == 4.55 GB Win 7 x64 (default install, no customization to install media) == 5.04 GB
  15. I personally avoid ALL updates on my Win10. I use 2016 LTSB on a Dell Latitude E5470 with an i5-6300U @ 2.4 GHz with 8.0 GB RAM and this laptop has NEVER been updated and NEVER will. I personally feel more "secure" NOT letting the laptop ever "see" a Microsoft/Windows Update. That's one of two "dedicated" Win10s (the other being a garage computer used for nothing other than a media jukebox). The other laptop is a triple-boot XP/7/10 but I can't recall the last time I've ever booted into anything other than XP. All three of my desktop PCs run XP and XP alone (one x64 SP2, two x86 SP3).
  16. My fully unattended install basically takes three steps -- 1) Windows XP with slipstreamed updates and signed drivers, 2) nLite's GuiRunOnce list of .exe's, then 3) a dozen and a half or so AutoIt .exe's. If I recall, Step 1 takes ~20 minutes, Step 2 takes ~10 minutes, and Step 3 takes ~10 minutes. So XP by itself is really only ~20 minutes.
  17. I'll be keeping my 360Chrome around even once Mypal 2.0 shows up. They (and Humming Owl's, from what I see) have basically matured to the point of nothing else to really do for them, use them as-is from here on out. I would like to see progress made on the "compile" front, but I cannot take the lead on that. Too steep of a learning curve.
  18. I don't think MAT was kicked out. He's been "put in his place" but that's all I've seen thus far. I don't follow it unless folks here post on it. What I've been very eager to see is Mypal 2.0, or whatever it's going to be called, THAT will be a day of celebration in my book. Because, um, Roytam browsers simply can NOT handle the modern web, period. Unfortunate, but TRUE. I've given up on all of Roytam releases.
  19. How many of you have bumped into portions of text disappearing? The "fix" suggesed in 2019 in the thread I pulled this image from cited disabling Hardware Acceleration (which I never enable to begin with, has always caused more harm than good and DISABLING is always the "go-to" suggestion to "fix" things). I'm currently DISABLING Accelerated 2D canvas, will keep you posted if I see portions of text disappear while this flag is disabled.
  20. Thanks. Thanks. Looks like that's the end of the line for my Arcticfox, I gotta have an always-on status bar. Everyone has their must-have's, that's one of mine.
  21. I have zero clue on what that gitbub page is saying. What is the last version of Arcticfox that still has the always-on status bar?
  22. Speaking of Arcticfox, when did it lose the always-on status bar?
  23. THERE it is! See msfntor, it has NOTHING to do with YOUR posts on MSFN. The nitter site admin is not an MSFN member. The world does not revolve around MSFN (especially not the "Older NT-Family OSes" threads). The nitter bug reports on the proper channels (which is not MSFN) was reported on November 21 by GitGondola. Your first post regarding nitter ( https://msfn.org/board/topic/182993-360-extreme-explorer-arcticfoxie-versions/?do=findComment&comment=1209723 ) was Friday, December 17. TWENTY SIX DAYS LATER, if I counted correctly. My point being, the world does not revolve around MSFN. The nitter cite Admin is not an MSFN member and nitter was not fixed by complaining about nitter on MSFN. There are proper channels to report nitter bugs and it was GitGondola that got that ball rolling. But anywhoo...
  24. Your point being? Of course an MSFN site Admin will read your hundreds of posts. A Google site Admin will not. A Twitter site Admin will not. A Facebook site Admin will not. A Nitter site Admin will not.
×
×
  • Create New...