This build has good startup time on Vista even with Sophos "on-access
scanning" enabled.
> But I want to note that unpacked version has 100-300ms slower on
> Win2k/WinXP so I really dislike the idea to switch using unpacked
> bzr.exe. So I'm resist to idea to make unpacked variant the default.
I was also able to measure a significant timing difference, although it
is < 100ms on my XP box. So I understand your resistance.
If the packed bzr.exe remains the default, then I think the download
link on the website should make it clear that the standalone build is
*not* recommended for Vista.
Another idea: it is possible that Sophos just looks at the .ZIP file
extension to decide that the file may be "unsafe." I wonder if simply
using a different archive name, e.g. "library.foo" would solve the
problem.
On Sun, Feb 03, 2008 at 11:47:40PM -0000, Alexander Belchenko wrote: bzrdev. bialix. com/bzr- setup-1. 2.0.dev. 0-unpacked. exe
> The test build without library.zip for testing is here:
> http://
This build has good startup time on Vista even with Sophos "on-access
scanning" enabled.
> But I want to note that unpacked version has 100-300ms slower on
> Win2k/WinXP so I really dislike the idea to switch using unpacked
> bzr.exe. So I'm resist to idea to make unpacked variant the default.
I was also able to measure a significant timing difference, although it
is < 100ms on my XP box. So I understand your resistance.
If the packed bzr.exe remains the default, then I think the download
link on the website should make it clear that the standalone build is
*not* recommended for Vista.
Another idea: it is possible that Sophos just looks at the .ZIP file
extension to decide that the file may be "unsafe." I wonder if simply
using a different archive name, e.g. "library.foo" would solve the
problem.
Paul