Re: Message base Voyager
Hello Gunivortus, You wrote that The Bat! didn't even start. In this case, try to run The Bat! with the /STARTUP_TIMING_LOG command line option and it will add more entries to the ex_log.txt files. There will be two such files (with different contents): one in %APPDATA% and another in %EMAIL%. These files may give us a clue. -- Best regards, Maxim Masiutin Current beta is 8.3.0.27 | 'Using TBBETA' information: http://www.silverstones.com/thebat/TBUDLInfo.html
Re: 8.3.0.27
Hello Maxim, Friday, June 8, 2018, 4:12:04 PM, you wrote: > The Bat! 8.3.0.27 (BETA) is available at > https://www.ritlabs.com/download/files3/the_bat/beta/tb83027-32.rar This version is up and running. Lots of great work this week. Can you run the 32 bit version and 64 bit version on the same system? Jerry -- Best regards, Ethanmailto:supp...@thedesk.ca Current beta is 8.3.0.27 | 'Using TBBETA' information: http://www.silverstones.com/thebat/TBUDLInfo.html
Re: Message base Voyager
Hello Gunivortus, I have found one issue in WinSocket initialization. Please The Bat! 8.3.0.27 (BETA) 64-bit https://www.ritlabs.com/download/files3/the_bat/beta/tb83027-64.rar and if it would not help, then try the 32-bit version https://www.ritlabs.com/download/files3/the_bat/beta/tb83027-32.rar -- Best regards, Maxim Masiutin Current beta is 8.3.0.27 | 'Using TBBETA' information: http://www.silverstones.com/thebat/TBUDLInfo.html
8.3.0.27
The Bat! 8.3.0.27 (BETA) is available at https://www.ritlabs.com/download/files3/the_bat/beta/tb83027-32.rar https://www.ritlabs.com/download/files3/the_bat/beta/tb83027-64.rar What's new in 8.3.0.27 since 8.3.0.26: [-] Trying to fix access violations which happens after Windows 10 update when getaddrinfo() API function is called [*] Removed TLS 1.2 until we finish implementing it Current beta is 8.3.0.26 | 'Using TBBETA' information: http://www.silverstones.com/thebat/TBUDLInfo.html
Re: Message base Voyager
Hello MAU, > As you can see in my signature, I am using v8.3.0.3 on Win10 Pro 64bit > with 1803 upgrade. I see. Well, these are two piece of TB log files which show problematic, but I can not recognize it exactly. From my ex_log.txt: v8.3.0.26 (BETA) 64-bit BOUDICCA3/Gunivortus 06.06.2018 16:05:56.209 MainForm:HideTrayIcon EOutOfResources Cannot remove shell notification icon v8.3.0.26 (BETA) 64-bit BOUDICCA3/Gunivortus 06.06.2018 16:17:55.141 ip_resolver:GetAddrInfoExW EAccessViolation Access violation at address 7FF81A0D0040. Read of address 7FF81A119338 v8.3.0.26 (BETA) 64-bit BOUDICCA3/Gunivortus 06.06.2018 16:17:55.159 ip_resolver:GetAddrInfoExW EAccessViolation Access violation at address 7FF81A0D0040. Read of address 7FF81A119338 v8.3.0.26 (BETA) 64-bit BOUDICCA3/Gunivortus 06.06.2018 16:17:55.165 ip_resolver:GetAddrInfoExW EAccessViolation Access violation at address 7FF81A0D0040. Read of address 7FF81A119338 v8.3.0.26 (BETA) 64-bit BOUDICCA3/Gunivortus 06.06.2018 16:17:55.186 ip_resolver:GetAddrInfoExW EAccessViolation Access violation at address 7FF81A0D0040. Read of address 7FF81A119338 v8.3.0.26 (BETA) 64-bit BOUDICCA3/Gunivortus 06.06.2018 16:17:55.197 ip_resolver:GetAddrInfoExA EAccessViolation Access violation at address 7FF81A0D0040. Read of address 7FF81A119338 v8.3.0.26 (BETA) 64-bit BOUDICCA3/Gunivortus 06.06.2018 16:17:55.201 ip_resolver:GetAddrInfoExA EAccessViolation Access violation at address 7FF81A0D0040. Read of address 7FF81A119338 v8.3.0.26 (BETA) 64-bit BOUDICCA3/Gunivortus 06.06.2018 16:17:55.219 ip_resolver:GetAddrInfoExA EAccessViolation Access violation at address 7FF81A0D0040. Read of address 7FF81A119338 v8.3.0.26 (BETA) 64-bit BOUDICCA3/Gunivortus 06.06.2018 16:17:55.229 ip_resolver:GetAddrInfoExA EAccessViolation Access violation at address 7FF81A0D0040. Read of address 7FF81A119338 v8.3.0.26 (BETA) 64-bit BOUDICCA3/Gunivortus 06.06.2018 16:17:55.239 ip_resolver:getaddrinfo EAccessViolation Access violation at address 7FF81A0D0040. Read of address 7FF81A119338 v8.3.0.26 (BETA) 64-bit BOUDICCA3/Gunivortus 06.06.2018 16:17:55.248 ip_resolver:getaddrinfo EAccessViolation Access violation at address 7FF81A0D0040. Read of address 7FF81A119338 v8.3.0.26 (BETA) 64-bit BOUDICCA3/Gunivortus 06.06.2018 16:17:55.259 ip_resolver:getaddrinfo EAccessViolation Access violation at address 7FF81A0D0040. Read of address 7FF81A119338 v8.3.0.26 (BETA) 64-bit BOUDICCA3/Gunivortus 06.06.2018 16:17:55.273 ip_resolver:getaddrinfo EAccessViolation Access violation at address 7FF81A0D0040. Read of address 7FF81A119338 v8.3.0.26 (BETA) 64-bit BOUDICCA3/Gunivortus 06.06.2018 16:23:11.515 ip_resolver:GetAddrInfoExW EAccessViolation Access violation at address 7FFEA1450040. Read of address 7FFEA1499338 v8.3.0.26 (BETA) 64-bit BOUDICCA3/Gunivortus 06.06.2018 16:23:11.515 ip_resolver:GetAddrInfoExW EAccessViolation Access violation at address 7FFEA1450040. Read of address 7FFEA1499338 v8.3.0.26 (BETA) 64-bit BOUDICCA3/Gunivortus 06.06.2018 16:23:11.546 ip_resolver:GetAddrInfoExA EAccessViolation Access violation at address 7FFEA1450040. Read of address 7FFEA1499338 v8.3.0.26 (BETA) 64-bit BOUDICCA3/Gunivortus 06.06.2018 16:23:11.615 ip_resolver:getaddrinfo EAccessViolation Access violation at address 7FFEA1450040. Read of address 7FFEA1499338 v8.3.0.26 (BETA) 64-bit BOUDICCA3/Gunivortus 06.06.2018 16:23:11.615 ip_resolver:getaddrinfo EAccessViolation Access violation at address 7FFEA1450040. Read of address 7FFEA1499338 v8.3.0.26 (BETA) 64-bit BOUDICCA3/Gunivortus 06.06.2018 16:23:11.631 ip_resolver:getaddrinfo EAccessViolation Access violation at address 7FFEA1450040. Read of address 7FFEA1499338 And from my thebat64_Exceptions.log: Date: 06 Jun 2018 16:23:11 OS: Windows 10 X64 (AMD or Intel) build 17134 PhysMemFreeTotal: 013744/016327 MB VirtMemFreeTotal: 0134213220/0134217727 MB CommandLine: "C:\Program Files\THE BAT!\thebat64.exe" /minimize Bitness: x64 MAPI #0: Windows Live Hotmail [Hotmail]; Path: C:\Program Files\Internet Explorer\hmmapi.dll (valid) MAPI #1: [Software]; Path: (not valid) MAPI #2: The Bat! [The Bat!]; Path: C:\Program Files\THE BAT!\tbmapi32.dll (not valid) MAPI #3: The Bat! Simple MAPI 32-bit [The Bat! Simple MAPI 32-bit]; Path: C:\Program Files\THE BAT!\tbmapi32.dll (not valid) MAPI #4: The Bat! Simple MAPI 64-bit [The Bat! Simple MAPI 64-bit]; Path: C:\Program Files\THE BAT!\tbmapi64.dll (valid) MAPI #5: [Windows Mail]; Path: (not valid) Default Profile: Address: 7FFEA1450040 ClassName: EAccessViolation Message: Access violation at address 7FFEA1450040. Read of address 7FFEA1499338 IsOSException: 1 Modules: 7FFEA145 ? ? 0040 20180605201901 C:\Program Files\THE BAT!\thebat64.exe Stack: 7FFEA1450040 [7FFEA145] 00DBB9D9
Re: Message base Voyager
Hello Gunivortus, > It is really a pain that The Bat does not work anymore since I > upgraded Windows 10 Pro 64 Bit to the 1803 Upgrade. As you can see in my signature, I am using v8.3.0.3 on Win10 Pro 64bit with 1803 upgrade. -- Best regards, Miguel A. Urech (Els Poblets (Alicante - Spain) Using The Bat! Version 8.3.0.3 (BETA) (64-bit) on Windows 10.0 My photos at: http://mau.smugmug.com My photoblog: http://mau.aminus3.com Current beta is 8.3.0.26 | 'Using TBBETA' information: http://www.silverstones.com/thebat/TBUDLInfo.html
Re: Message base Voyager
Hello Zygmunt, > Only import from TheBat! .TBB files may be useful. > All encrypted message base (folders and mail files) are in "Voyager\Mail" > directory and its subdirectories. Thank you, and also Lüko for helping me out with this. It is really a pain that The Bat does not work anymore since I upgraded Windows 10 Pro 64 Bit to the 1803 Upgrade. Hope, Maxim finds out what is the Problem. -- Kind regards, Gunivortus Current beta is 8.3.0.26 | 'Using TBBETA' information: http://www.silverstones.com/thebat/TBUDLInfo.html
