New version of ZoneAlarm available

in :

the chkdsk issue has been resolved since 5.1.033. The newest 5.5.062
seems pretty solid, but the final 4.5.594 release was solid too.

I'm gonna add my input re this thread.

My exper has been mostly with Win9x until very recently.
I still have a WinME hooked on equal terms to the WinXP via retail router. (both using ZA 5.1.033)

I always do 'fresh' reinstalls of ZA updates. Za auto-cfgs the adapters of each computer, but I have to enter both computer's Ips (as
used/assigned by the router) into ZA's Trusted zone. WinXP needs additional Trusted zone entries, both are localhost Ips: 127.0.0.1 and
0.0.0.0
This is to fix some weird XP problem.. I Googled the trouble and found one of the mvps recommending adding the localhosts to cure this
trouble I had at the time.


-----
Re CA's etrust (eztrust whatever)

I briefly tried the 'trial' EZ FW (=ZA 4.xx...) and EZ AV. Neither seemed very complete/thorough. And I didn't want to use EZ's old ver of
the ZA FW. So, on the xp, for awhile, I ran the current ZA (5.1.033) with the EZ AV. Saw no signs of problems, updating, that I recall... but
soon after I deleted EZ AV and installed NAV, so there's no EZ anymore.

---
...found this thread when Googling to read comments on the LATEST ZA update :-)

I always do 'fresh' reinstalls of ZA updates. Za auto-cfgs the adapters
of each computer, but I have to enter both computer's Ips (as
used/assigned by the router) into ZA's Trusted zone. WinXP needs additional
Trusted zone entries, both are localhost Ips: 127.0.0.1 and
0.0.0.0
This is to fix some weird XP problem.. I Googled the trouble and found one
of the mvps recommending adding the localhosts to cure this
trouble I had at the time.


OP:
The 0.0.0.0 address is required for DHCP clients, as they use it during
bootup in communicating with a DHCP server.