Some time around 6/1/03 18:43:03, I think I heard Allie Martin say:
::> -----BEGIN PGP SIGNED MESSAGE-----
::> Hash: SHA1
::> - From my personal experience, as well as the experience of quite a few
::> other TB! users, when ZA starts being problematic with TB!, this heralds
::> the onset of other problems. I've never heard of a solution to this
::> problem other than switching to another firewall. This isn't difficult
::> since there are a lot of other alternatives. My personal favourite is
::> Kerio Personal Firewall.
I am sorry, but I cannot accept the (now common) "solution" of
ignoring the problem and trying a different firewall. I rolled back
to the previous version of TB (1.61) and everything works fine again.
And just to be sure, I re-installed v 1.62r, tried again, rolled back
to v1.61, re-tried, (sprinkled with reboots in between, just in case)
and the results were consistent: TB v1.61 works fine with ZA
v2.6.362; ZA detects the network access attempts by TB and prompts me
for permission, to which I accept and mail is transferred back and
forth. Whereas TB v1.62r just stalls when trying to access the
network (while ZA is running), and the tasks cannot be aborted or
deleted. I basically have to kill the task manually (using WinTop).
When ZA is not running TB v1.62r works fine.
I will look into Kerio or another FW, but for different reasons. I do
not think it wise to switch firewalls when the only problem that ZA
has given me so far is with the latest version of TB. TB v1.61 works
for me so I will not be upgrading any time soon until this issue is
properly investigated, identified and, if possible, solved. From
other users' comments I know that I am not the only one who has
experienced problems with TB and ZA.
Thanx anyway for your help.
-dZ.
________________________________________________
Current version is 1.62r | "Using TBUDL" information:
http://www.silverstones.com/thebat/TBUDLInfo.html
