Volatile PG Checksums for TDS DLL's

The TDS companion product (to PG) has a couple of files advscan.dll and dcsmutex.dll that are likely to be automatically changed by downloading a revised Radius Database of trojan attack information. This, in turn, triggers Process Guard's checksum process to seek confirmation on what is going on with a surprise change to a DLL file.

I have several members of my family who use the same computer and would like to avoid them having to make quality decisions regarding PG's checksums. Can the current version of PG be customised to avoid these TDS file checksums, or do I have to either turn off the whole checksum process or leave it permanently in Learning Mode?

 

Hi Derek G, If you are using one user account for all your family then they all have administrative rights. If they were using limited accounts I do not think this would be a problem but to be honest I have not tried it. There are very few programs that require regular quality decisions - The dcsmutex is usually only updated one a week for instance.

Having a an opt out list on checksums for regular updates such as your radius file is already on the Process Guard wish list.

Enjoy your weekend - Pilli

 

Pilli, Sorry for the delay in getting back to the forum. I will get around to testing the limited account suggestion when I next get a chance. I am also glad the PG checksum opt-out proposal is on the suggestion list. Thanks again for showing an interest in my difficulties.

 

Even as a limited user I think you will have the PG screen pop up for confirmation by the poor unfortunate limited user if they are actually running a scan of TDS-3 after the update of the DcsMutex file or the file is in any other way active.

I am often cursing PG from stopping my scans of TDS-3 in mid-flight but at the same time it is reassuring to know that PG is on the ball.