Access violation at address 75E09B60 in module 'msvcrt.dll'

2011-08-29 Thread Marek Mikus
Hello, Tb crashed on background with following error: Date: 29 Aug 2011 14:55:17 OS: Windows 7 Service Pack 1 build 7601 PhysMemFreeTotal: 912/2047 MB VirtMemFreeTotal: 1503/2047 MB Address: 75E09B60 ClassName: EAccessViolation Message: Access violation at address

Re: 5.0.22.12

2011-08-29 Thread Krzysztof Kudłacik
> The Bat! 5.0.22.12 (ALPHA) is available at After upgrade of Antispam Sniper 3.3.0.2 plugin stopped to work. Manual adding of path to .tbp file caused an alert "plugin is damaged and cannot be used". -- Pozdrowienia, Krzysztof Kudłacik Using Voyager v5.0.22.8 (ALPHA) on Windows 7 6.1 Bui

Re[2]: 5.0.22.12

2011-08-29 Thread Simon Martin
Title: Re[2]: 5.0.22.12 Hi Krzysztof et al. Monday, August 29, 2011, 8:28:39 AM, Krzysztof wrote: >> So add it to your address book > ok, let's put it clear: previous (alpha) versions of TB! didn't cause this > alert of 'untrusted' certificate First, let me say that the reason I have stopped

Re: 5.0.22.12

2011-08-29 Thread Krzysztof Kudłacik
> So add it to your address book ok, let's put it clear: previous (alpha) versions of TB! didn't cause this alert of 'untrusted' certificate -- Pozdrowienia, Krzysztof Kudłacik Using Voyager v5.0.22.8 (ALPHA) on Windows 7 6.1 Build 7600 __

Re: 5.0.22.12

2011-08-29 Thread Krzysztof Kudłacik
> or don't use self-signed certificate. :) It is rather impossible if you are employee of some corporation -- Pozdrowienia, Krzysztof Kudłacik Using Voyager v5.0.22.8 (ALPHA) on Windows 7 6.1 Build 7600 Current beta is 5.0.22.12 | '

RE: 5.0.22.12

2011-08-29 Thread Vilius Šumskas
> > The Bat! 5.0.22.12 (ALPHA) is available at > > I use TB! with Exchange server (via IMAP) that has self-signed > certificate. Now I cannot avoid annoying prompt about not trusted > certificate - the prompt window shows up ever time TB! connects to my > server So add i

Re: 5.0.22.12

2011-08-29 Thread Krzysztof Kudłacik
> The Bat! 5.0.22.12 (ALPHA) is available at I use TB! with Exchange server (via IMAP) that has self-signed certificate. Now I cannot avoid annoying prompt about not trusted certificate - the prompt window shows up ever time TB! connects to my server -- Pozdrowienia,