I just updated to the new 3.2 beta...thanks. I still keep my old protection and security lists. PG started smoothly. PG alerted me to one new startup app that I needed to set security permissions on. I noticed procguard is still set at "System" startup. I thought it was going to be changed to "Automatic" in future issues of PG because of errors being reported such as mine. I haven't seen the need to change "System" to "Automatic" so far.
Where did you get the beta 2 from ? I just downloaded from the following link which was provided in the follow-up e-mail and it's exactly the same as the first beta (ie. MD5 hashes of installer are the same) ~snipped [private] beta link ||| Please Do Not Post this link Publically~ dog
It appears I received the file from the same method as you did. I did not check the MD5 hash of the installer though. So it seems that there is no change then. At first, without an updated changelist, I found it hard to see any difference between the two betas. I did mention that the procguard driver was still set to "System" rather than "Automatic" which I thought would of been changed in this beta version. This made it harder to determine any changes.
OK now...got a revised link to a new beta 2 file...this time with a different MD5 hash. Thanks Wayne! I could of tried the "Check Version" feature since ZA security recognized it as changed and would not have done so before. Good call Defenestration! Everything is running smooth so far. Still see that procguard is set for "System" though. I'm not sure what is new or changed from the last beta.
Likewise have the new version of beta 2. Seems to work fine. Wayne and Gavin. A change log, and also what in particular you want tested would be helpful. Pete