Discussion in 'Prevx Releases' started by Triple Helix, May 16, 2012.
Just updated here! And to both Beta and Standard users! Changelog will follow soon!
Thanks TH. .184 running nice and smooth on three systems here!!!
Changelog: .177 > .184
Foreign language support - 11 languages are now supported. The supported languages are: English, Japanese, German, Dutch, French, Korean, Spanish, Russian, Portuguese, Chinese and Italian. So far this is only in the agent itself and parts of the portal. Backup & Sync and Password Management are still only in English and Japanese. Language selection is made at the time of installation. Changing a language can only be accomplished via uninstall and reinstall.
Keystroke entry issues with Everquest
Compatibility with nProtect GameGuard
Generic Identity Shield fixes that may address a few other random problems
From Jim at Webroot!
Daniel, wasn't there a .179 build? Never got it and still running .177. ??
Daniel updated to 184 running like a well tuned sports car.
It's was to Closed Beta users only! https://www.wilderssecurity.com/showthread.php?t=323844
Daniel In The Lions Den
Good to hear!
.184 is live to non-beta users as well so everyone will receive the update in the next couple days
Got the .184 and all works just fine.
I thing the combination of win xp pro firewall and the WSAE suits me perfectly!
On an AZERTY keyboard, still getting the problem of the double @@ when in https://, which I had already mentioned here (notice: this first post of mine dates back to mid-January ?!?! ), here and here, surprisingly still not resolved, although v220.127.116.11 is supposed to be French supported... Surely this little detail cannot be so very difficult to resolve??
Nevertheless, despite this one somewhat exasperating quirk, I find the Anti-Virus, Security and Identity Shield modules of WSA to be otherwise flawless and much, much better than some AV reviews would appear to indicate...
EDIT: I can confirm that, as suggested in the third of my above posts, this doubling of @ when typing just one @ only happens when on https:// pages. (Having said that, I have just had a doubling of the @ whilst editing this post. So, I should qualify the above by saying: "almost only"!)
Same issue here I'm afraid. Solution from support was to turn off ID-shield for the browser you use. I don't know whether that means that there will be no fix anytime soon.