New threshold not working for me
25 March, 2020 at 3:25 am #2713
I thought I had a grasp on the new threshold syntax but doesn’t seem to work for me.
Here is what I have
TOPPROCESSCPU=active:1,interval:5,threshold1:3 95 %Red%,display:%1 [%2] %3%
TOPPROCESSMEM=active:1,interval:5,threshhold1:3 %500mb% %Red%,display:%1 [%2] %3[1.1b]B
When I run Prime95 torture test to raise the cpu and ram past the threshold, the numbers go up but the colors are not changing to red as I had hoped.
25 March, 2020 at 7:01 am #2716
Oh dear, looks like I’ve broken the thresholds. I’ll look at that today.
25 March, 2020 at 12:11 pm #2717
I like this idea! set=key:500mb,value:524288000 🙂
25 March, 2020 at 12:49 pm #2721
Check out v2.4.2
26 March, 2020 at 12:40 am #2725
Good morning and thanks for the quick turnaround for an update!
I gave it a go and I have good news and bad.
Top Process CPU now turns red at 95%+ as expected.
Top Process Mem still does not turn red at 500mb+ 🙁
Perhaps this is a clue? I found this in the error log when I started 2.4.2
25-03-20 08:11:49:363 ERROR TOPPROCESSMEM () [Error] : Mapping.GetTopProcessPu failed
I do have this set higher up in the .ini:
#64 Bit Goodness
So I flipped it to 0 just to see if that made a difference. The error above did go away but still no threshold color change for the memory.
Also, when I launch DesktopInfo v2.4.2, I get a new pop up asking about installing something from the app store (see attachment). This comes up when double clicking the exe normally or right click and Run as Administrator. 2.4.1 does not have this popup. If I click “No” to this new pop up, I get the normal UAC and can still run it.
26 March, 2020 at 6:57 am #2730
Thanks for the feedback.
TopProcessMem is working for me with the following:
TOPPROCESSMEM=interval:10,counter:pu,text:Top Memory,display:%1 (pid:%2) %3[1.1b]B,threshold1:3 %500mb%
it also works if i put a value directly in the threshold.
the mapping error is not unusual. dti always silently recovers from that.
I can’t account for the App Store popup. I’ve never seen that, ever, on any computer. So you’re saying if you run 2.4.1 and 2.4.2 together, the former doesn’t trigger the App Store popup and the latter always triggers it?
can you try this config on a different computer?
26 March, 2020 at 8:46 am #2733
I got the threshold thing to work. For future reference, threshold only has 2 h’s and not 3. (DOH!)
On the topic of launching 2.4.2. The VM I’m doing these tests on is a fairly fresh install of Server 2019. I did run 2.4.2 on a Server 2016 and it did not have that alert. Just the normal UAC. When I run it on my Win 10 box, a Windows Defender SmartScreen screen does pop up (see attached). I click “Don’t Run” and try the same thing with 2.4.1, no Defender screen. Run 2.4.2 again on my Win 10 and this time click “Run anyway”. It runs and any additional runs after that point no longer has that Defender screen come up.
I did notice a difference between UAC notifications with 2.4.1 and 2.4.2. 2.4.2 appears you removed “Mr” from the publisher name and the file origin says Downloaded from the Internet. 2.4.1 says the file origin is the hard drive from the computer.
Went into the properties of the 2.4.2 exe, I can then click the unblock box and then life is just dandy again.
26 March, 2020 at 9:06 am #2738
Yeah that’ll do it!
I haven’t tested on Server 2019, probably time to start doing that. Right now it’s just 2012 and 2016. So, so far it appears to be peculiar to 2019.
Smart Screen: The certificate was recently renewed so it’s possible your Win 10 box couldn’t find the renewed certificate (or something).
Screen shot 2 and 3 is last year’s certificate versus this year’s. If you open the exe properties and drill down to the certificate details, you’ll see the expiry date. They just decided to change the name for no reason. They do that.
26 March, 2020 at 12:17 pm #2739
I just installed 2019 and ran 2.4.2. No smartscreen, no uac, just ran without any prompts. I don’t know what the difference might be.
26 March, 2020 at 11:57 pm #2744
That is curious. I’m assuming when you installed 2019, you left most of the settings to defaults? When I compare my 2016 with 2019 settings, there are some differences with how the UAC and Smartscreen are set. I know I never messed with those settings in those 2 instances so perhaps they were set via domain group policy? (See attachments for differences)
At any rate, I’m able to get v2.4.2 going on 2019 as stated before and will poke at it a little more to get it just the way I’d like it. 🙂
- This reply was modified 1 year, 10 months ago by phlegmer.
26 March, 2020 at 5:55 am #2728
One other observation. With the older version I have been using (v1.5), both the left column and right column would turn red when a threshold was met. This 2.4.2 version, just the right column changes color. Don’t know if it matters to me but something different.
26 March, 2020 at 8:00 am #2732
Ahh, I see this change in the changelog. Nevermind…. 🙂
27 March, 2020 at 7:17 am #2757
Yes. The 2019 settings are all defaults. The UAC is the same as your 2016 and the SmartScreen is the same as your 2019. I set the UAC to the highest and ran DTI and still no prompts, not even when Run As Admin.
- The topic ‘New threshold not working for me’ is closed to new replies.