While I think it is important to correct the problem of tor-zonealarm
incompatibility I don't think anybody who uses tor should use
zonealarm. Tor is an anonymity and privacy tool and zone-alarm doesn't
respect either of these fundementals. When installed+run, zone-alarm
"phones-home" (check for yourself with a packet sniffer) even if you
tell it not to access anything. In other words, it breaks it's own
rules and I wouldn't trust my privacy/anonymity to it.<br><br><div><span class="gmail_quote">On 9/15/06, <b class="gmail_sendername">Lee Fisher</b> <<a href="mailto:blibbet@gmail.com">blibbet@gmail.com</a>> wrote:</span>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">> No, Windows says it has created a error log, but I don't know where.<br><br>Debugging Tools for Windows
<br><a href="http://www.microsoft.com/whdc/devtools/debugging/default.mspx">http://www.microsoft.com/whdc/devtools/debugging/default.mspx</a><br><br>use a debugger to catch the problem as it happens. or use postmortem<br>
tools to look at the dump.<br><br>programs like ZoneAlarm are hooking NT file system I/O and network port<br>calls, and checking them. if file system filter drivers are not WELL<br>written and WELL tested (especially interop with similar software
<br>installed on the same box) things will go wrong in strange ways.<br><br>tools like this may also help:<br><a href="http://www.osronline.com/article.cfm?article=199">http://www.osronline.com/article.cfm?article=199</a>
<br><a href="http://www.osronline.com/article.cfm?article=154">http://www.osronline.com/article.cfm?article=154</a><br></blockquote></div><br>