Quirky

Member
  • Content Count

    95
  • Joined

  • Last visited

  • Days Won

    2

Quirky last won the day on September 20

Quirky had the most liked content!

Community Reputation

5 Neutral

About Quirky

  • Rank
    Active Member

Profile Information

  • Gender
    Male

Recent Profile Visitors

2809 profile views
  1. For the moment only Delayed helps, but I can't complain about your support which remains excellent.
  2. Yes, you should turn it off. No, the tooltip is correct (although indeed somewhat confusing) because performance issues are most likely to come if you turn it on (= pagefile used, more disk activity, Windows becomes slower etc.). We want to use the RAM here, not the pagefile. Some confusion may arise because a user intuitively assumes that "performance issues" could be caused by the ~300MB needed by EAM so the user feels the option should be on (= less RAM used). It seems like extra, unnecessary RAM usage. But it is not. Most systems can spare 200-300MB of RAM nowadays and that option should only be enabled in critical situations, like not having enough RAM to even open and run programs, for example.
  3. Am I wrong in assuming that EAM initially decides on its own whether to enable that option or not? I seem to remember on a PC with limited memory that it was turned on by default. Tarnak, if you have enough memory you should let EAM use it and leave that option disabled - everything will work better this way.
  4. I also confirm an unusual amount of issues (already reported) with some programs crashing or displaying high CPU usage, all caused by the recent EAM updates. 2018.8 is fine. Excluding/disabling doesn't work (this makes me wonder about the effectiveness of these options), only a full EAM uninstall does, or a switch to 2018.8.
  5. That is not a given at all. They are very different browsers now and distance in only growing. Such a "merge" might not even be applicable due to the aforementioned differences, both in underlying technology and even developer mentality. In any case, we will see. Now Surf Protection works, as always. The future? No one can predict that.
  6. Try Pale Moon, one of the few sane browsers left. Zero issues with Surf Protection, too.
  7. Chiming in about the new UI: 1. I use 125% DPI. The UI window (2018.8.1) needs to be much larger (almost full screen) in order to contain most of the information it did before the update. This also applies when using the "slim icon-only bar to keep it as compact as possible". I'm sorry but what I read at the beginning here is simply not true - or does not apply at all on my system. 2. The scrolling: it does not "make things more user-friendly", because: unless fully memorised, you don't really know where settings are. You have to keep scrolling to find them. I've mentioned it elsewhere, it's an "eyes" issue, not just personal preference and all this extra scrolling (on an almost full-screen UI no less) makes the whole thing very uncomfortable. Really sorry that I can't report anything positive about it. In the years I've been using EIS/EAM, I don't recall any "feature reversions" so I can only suggest this: please consider the use of themes/skins etc. so that we could have the previous, "steady" UI as an option.
  8. Any chance we can have this? Note that this is different from what Lode suggests above. It's not about any of the currently available Notification settings, but a handy, alternative way to this: Protection/File Guard/manually locate or add rule/enable "Don't alert when this file changes" within the Application rule.
  9. I'd give them a bit more credit than that!
  10. But WFC is not a firewall -totally unrelated to Online Armor and even EIS- and it'd make an excellent in-built companion to EAM which actually promotes the Windows Firewall. Anyway, I guess it's too late for that.
  11. Quirky

    Pale Moon a system process?

    I don't think it's currently digitally signed: No more code-signing options
  12. One issue left: since the forum still uses browser user-agent sniffing, it fails with Pale Moon. There's an old issue with some websites: when they see the word 'Goanna' they believe they are dealing with a 'Goa' mobile device instead of a desktop browser and fail in various ways. In this forum, post replies cannot be added so it becomes unusable. The forum works fine when using these user-agent strings for example: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:52.9) Gecko/20100101 PaleMoon/27.6.2 Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:52.9) Gecko/20100101 Firefox/52.9 PaleMoon/27.6.2 The forum does not work properly with any of these native Pale Moon strings: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:3.4) Goanna/20171124 PaleMoon/27.6.2 Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:3.4) Gecko/20100101 Goanna/20171124 PaleMoon/27.6.2 Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:52.9) Gecko/20100101 Goanna/3.4 Firefox/52.9 PaleMoon/27.6.2 It'd be nice if you could forward this to the forum software guys, so that we won't have to use such overrides. Thanks.
  13. Quirky

    CLOSED App lock issue/question

    I've enabled that option and it seems to lock apps more consistently now, but I'll need to test a bit more.
  14. Quirky

    CLOSED App lock issue/question

    Same device and Android version. No other security app (All-In-One-Toolbox is installed), EMS 3.2.1 with admin access. I also see a notification access option with only EMS as an option (disabled). Should that be enabled? I don't have any apps that apply power-saving except for what Android itself does.