Jump to content

NotHereToPlayGames

Member
 View Profile  See their activity

  • Posts

    6,741

  • Joined

  • Last visited

  • Days Won

    83

  • Donations

    0.00 USD 

  • Country

    United States

 Content Type 

Everything posted by NotHereToPlayGames

  1. NotHereToPlayGames
    For v27 - I have to go all the way back to 20190803 to get a version where the Permissions Manager works. Win XP x86 and Win XP x64.
  2. NotHereToPlayGames
    The Permissions Manager does not seem to work in this build of v27. Version numbers are highly misleading. If you compare the "whatsnew" of both, you will very likely find that the version 28.10 from here includes nightly patches that have not made it into version 28.12 from "there". ie, "here" might be a 'lower' version number but it contain NEWER fixes/patches than a official release from "there". And to confuse the two will get you thumped in the head by people from over "there", lol.
  3. NotHereToPlayGames
    Greatly Appreciated! No crashes during Stylem edits, have not yet tested the more than 10 tabs or the about:support crashes.
  4. NotHereToPlayGames
    Correction - I'm back to 28.1.0a1 (Sept. 21, 2018) as my DEFAULT do-it-all browser-of-choice. v27 kept crashing during Stylem style edits.
  5. NotHereToPlayGames
    I've force over a dozen crashes via about:support without the .dll files and Event Viewer doesn't show anything for any of them. Same results for XP x86 and XP x64. Did not test in Win 2k3 or Win10. Windows Event Log Service is running and logging forced crashes in other applications.
  6. NotHereToPlayGames
    When the about:support or the Stylem-edit cause a crash for me, I don't get any error dialogs or nothing, the process terminates and there is no warning or error dialog of any kind. THAT is why I asked "How did you track the crash down to this .dll?". Aside from that, yes, the .dll did fix the about:support crash - but then I immediately deleted the three .dll files because I have no use for them.
  7. NotHereToPlayGames
    How did you track the crash down to this .dll? I prefer to default to v27 but now I get crashes if I have a Stylem style-edit window open.
  8. NotHereToPlayGames
    about:support does now crash for me also - it did work yesterday tested today in Win XP x86 after a hibernate = crash tested today in Win XP x64 after a full reboot = crash did not test in Win 2003 or Win 10 I'd like to recompile but the instructions are too ancient and no longer work. Anybody have up-to-date instructions on how to compile?
  9. NotHereToPlayGames
    nope...
  10. NotHereToPlayGames
    AWESOME !!! this is the first version since 28.1.0a1 (Sept. 21, 2018) that I've been able to revert to my preferred v27 and have Citi login work, a few other finance sites work, and Google Sheets work... Hip Hip Hooray!!! back to v27 as my DEFAULT do-it-all browser-of-choice... ps - I do not get any crash in xul.dll when opening about:support (tested in Win XP, Win XP x64, Win Server 2003, and Win 10)...
  11. NotHereToPlayGames
    Ouch! I'm glad you caught that, I'm not sure if I would have noticed. Please keep us posted if you see this in the next version as I've been "trying" to revert to NM27 as my "default-for-all".
  12. NotHereToPlayGames
    I hope that a moderator or admin stumbles upon this post. I have been SOLICITED BY A FRAUDULENT PARTY and it CAME FROM THIS WEBSITE. I hope that a moderator or admin can find out WHO used THIS WEBSITE to send me an e-mail and that this person be BANNED - PERMANENTLY! I do **NOT** want my e-mail address accessible by people that view my profile. I'm not sure if I jumped through all the hoops to set up this preference - as my view is that it should have been the DEFAULT to begin with! UGH!!!
  13. NotHereToPlayGames
    I second the "just leave the names alone and quit rehashing this every few months." I say that at risk of the "other" forum member(s) who visit here will now try to get me banned from here. Because I know for a fact they ban "us" on 'their' forum! Or at very least pound out a chest-beating "Why are you even here?" Don't know how to "mend" the relationship with the "other" forum WITHOUT jumping through the branding - but I still vote for "just leave alone".
  14. NotHereToPlayGames
    Noted. Will keep an eye on both threads - I highly prefer to run NM27 or ArcticFox as my default for *everything*.
  15. NotHereToPlayGames
    I can signin at Citibank but it then lands on the dashboard page but it is empty - can't do anything without the dashboard page loading. But this is something that would require an actual Citibank account to be able to witness.
  16. NotHereToPlayGames
    Looking forward to it! I much prefer nm27 over nm28 because it uses roughly 31 MB *less* of a memory footprint.
  17. NotHereToPlayGames
    Awesome! This works for PM28. But it does not work for PM27 or ArcticFox
  18. NotHereToPlayGames
    Roytam, this is the original post. It has the link, the working, and the non-working PM version info.
  19. NotHereToPlayGames
    I was starting to wonder...
  20. NotHereToPlayGames
    I don't disagree, I was being facetious. A jab in the ribs to those that perceive New Moon issues with Citi login (third largest bank in US) as an "off-topic" discussion (regardless of the COMMUNAL discourse "to the side", it IS a VALID topic!) But again, it doesn't work "upstream" either, so *I* don't expect Roytam to 'fix it' (but I also see that a shame as patches are "cherry-picked"). But again, I digress... Again, lol...
  21. NotHereToPlayGames
    All the virus and mask talks seem way WAY "off-topic" to me. But I digress...
  22. NotHereToPlayGames
    THANK YOU !!! !!! !!!
  23. NotHereToPlayGames
    Yeah, beware of upstream. The Citi issues pointed out earlier also exist upstream (which is why I don't expect RT builds to 'fix' it).
  24. NotHereToPlayGames
    Is this Paranoia or Conspiracy Theory? I wasn't asking anybody to visit Citi's web site, for the record. As I've stated over-and-over, I run version 28.2.2 (or thereabouts) from September 2018. Because IT works for me and "newer" versions do NOT. I 'all but' place people on "ignore" that chastise me for using a browser "from 2018" and wag their 'security hype' finger my way. I'm HAPPY with my September 2018 version.
  25. NotHereToPlayGames
    Not true. If you have a browser NEWER than Nov. 2018, you get the error that has been screen-cap'd above whether you put a real account username/password or a bogus account username/password. If you have a browser OLDER than Nov. 2018, you get a DIFFERENT error !!! So you do NOT need a Citi account to test this - you get the screen-cap'd error on NEWER browser but NOT on OLDER browsers. User Agent settings do NOT alter outcome.
×
×
  • Create New...