On Aug 17, 12:29 am, Stefan Küng <tortoise..._at_gmail.com> wrote:
> I won't deny the possibilty that an x64 build may show some problems
> that the 32-bit build does not. But since some Subversion developers
> also use an x64 build (most of them use Linux), I would assume that such
> a bug would have been found already.
> Are you absolutely sure you disabled the virus scanner/firewall
> *completely? I'm just asking because most of those 'things' allow you to
> disable certain 'features' but then in the background still mess around
> because they think that users (even though they configured it) didn't
> *really* want to disable it.
> For example, we have to use Kapersky in our office, and that also messes
> around, even if all ports which it should monitor are removed. To get
> svn+ssh:// working again, you have to completely disable it, and I mean
> completely.
>
> If that doesn't help, you should maybe ask on the Subversion mailing
> list for help: the error message is thrown by the Subversion library
> which TSVN uses, so it's something internal to the library, not the TSVN
> code...
Okay, I'll push the question over to there. Thank you again for your
time.
For Norton, I cleared the flags "Enable Auto-Protect" and "Enable
Firewall". About the only way to turn off more that I'm aware of would
be to uninstall it, but I'll check around. I'll note that TSVN works
fine with the same Norton configuration on XP. And I'm not using svn
+ssh, but rather http without encryption. I don't know that the x64
has anything to do with it...I was using that more to identify the
machine than point at a cause. I've been doing software development
long enough now (15+ years) to know better than to make assumptions!
Off to the Subversion list...
NRN
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_tortoisesvn.tigris.org
For additional commands, e-mail: users-help_at_tortoisesvn.tigris.org
Received on 2008-08-17 20:28:09 CEST