GaryCN,
We are phasing out Blink Neighborhood Watch; it is simply Personal without the Anti-Virus engine and possibly the Vulnerability Assessment Scanner (depends if you obtained your NHW serial before 3.0 was released). Thanks for pointing out the URL which is still reachable when the exact path is known. I'll inform our web admin of this. We are simply no longer issuing any new Neighborhood Watch serials; however, for those such as yourself that might prefer the reduced feature-set, the installer for Blink Personal and Neighborhood Watch is the same and the version that is running after completing the initial configuration is controlled by the Serial Number. So you can use the same installer:
http://download.eeye.com/html/products/blink/personal/installer/blinkconsumersetup.exe
Then, when prompted to do so, after you paste in your original serial number this will controls the features that will be available. Of course, feel free to take advantage of the 1 year free Blink Personal promotion that is currently running.
Also, as you already identified, the
blink_<hostname> account that showed up in the User Accounts and maybe logon screen was fixed in the final release.
dottedquad,
I've updated the link in the release notes; thanks for pointing this out. The full installer can be downloaded directly from the following location:
http://download.eeye.com/html/products/blink/personal/installer/blinkconsumersetup.exe
It is currently only available as a full installer and not as an online update; however, we do support an over-install of the beta so you can keep your current configuration. With the beta still running, simply double-click on the file downloaded above and follow the series of dialog boxes which will walk you through the upgrade.
As for running Kaspersky and Zone-Alarm along with Blink, in general it isn't suggested that security applications that have similar features run along-side each other for two main reasons:
1) Since Blink also includes an AntiVirus engine and overlaps on the same firewall fundamentals, as each compete for the same resources (drivers, memory, etc) instability can occur.
2) Running more than one firewall can complicate troubleshooting as the user must contend with multiple rulesets when trying to figure out why, for example, certain traffic is being blocked.
Thank you everyone for the feedback.
Christopher I. (eEye)