PG Icon colors

Discussion in 'ProcessGuard' started by figtrees, Mar 17, 2004.

Thread Status:
Not open for further replies.
  1. figtrees

    figtrees Registered Member

    Joined:
    Mar 17, 2004
    Posts:
    7
    The PG icon in the systray is sometimes red and sometimes blue. What do these colors mean? o_O
     
  2. siliconman01

    siliconman01 Registered Member

    Joined:
    Mar 6, 2003
    Posts:
    780
    Location:
    West Virginia (USA)
    Gray with X means Process Guard is NOT active

    Red means Process Guard is active and protecting

    Blue means that Process Guard is active, protecting, but has logged an event block. This is when you want to look at the log and see what program is being blocked.
     
  3. figtrees

    figtrees Registered Member

    Joined:
    Mar 17, 2004
    Posts:
    7
    Thank you for your reply. :) As to my going to the log to look, wouldn't it be better if a window automatically opened to show me the entry which caused the icon to change to blue? o_O
     
  4. Jason_DiamondCS

    Jason_DiamondCS Former DCS Moderator

    Joined:
    Nov 11, 2002
    Posts:
    1,046
    Location:
    Perth, Western Australia
    Whilst it does sound like a good idea, the Window would pop up too many times and be an "annoyance" to the user. The icon changing blue doesnt necessarily mean there is something wrong on your system, it just means something has been logged, which could be important, or could be benign. :)

    -Jason-
     
  5. Andreas1

    Andreas1 Security Expert

    Joined:
    Jan 29, 2003
    Posts:
    367
    Location:
    Mainz (Ger)
    Jason, maybe there would be a way to (temporarily) highlight the line that was added first after ProcessGuard lost focus. So the window doesn't pop up, but the user doesn't have a hard time finding the right "entry-point" when he/she opens it...?

    Andreas
     
  6. figtrees

    figtrees Registered Member

    Joined:
    Mar 17, 2004
    Posts:
    7
    Hmm. So the new topic in this thread is logs. Alright. The log for IMSecure is an example of how NOT to make a log while the logs for Avast anti-virus are at the other end of the bell curve, yes?
     
Thread Status:
Not open for further replies.