Re: 8.3.0.22
Hello mse, The list that you have posted shows that your CPU does not support SHA instructions. It would have shown "CPUID2:SHA extension" if it would. -- Best regards, Maxim Masiutin Current beta is 8.3.0.22 | 'Using TBBETA' information: http://www.silverstones.com/thebat/TBUDLInfo.html
Re: 8.3.0.22
Hello Maxim, MM> Hello mse, MM> Saturday, June 2, 2018, 10:58:54 PM, you wrote: >> Nice! >> My CPU can do stuff... MM> Do you mean that your CPU supports hardware SHA-1 instructions? What CPU model do you have? Honestly, I was just impressed by the list. I have an Intel Core i5 8250U, which is rather new, so I hope SHA-1 is supported. 02.06.2018 21:44:25.018 CPUID0:presence of Time-Stamp Counter 02.06.2018 21:44:25.052 CPUID0:availability of CLFLUSH instruction 02.06.2018 21:44:25.052 CPUID0:MMX support 02.06.2018 21:44:25.068 CPUID0:FXSR bit, denoting availability of XMM registers 02.06.2018 21:44:25.068 CPUID0:SSE support 02.06.2018 21:44:25.068 CPUID0:SSE2 support 02.06.2018 21:44:25.083 CPUID0:Hyperthreading, which is used to distinguish cores with shared cache 02.06.2018 21:44:25.083 CPUID:0 BFEBFBFF 02.06.2018 21:44:25.099 CPUID1:availability of PCLMULQDQ instruction 02.06.2018 21:44:25.099 CPUID1:SSSE3, Supplemental SSE3, support 02.06.2018 21:44:25.115 CPUID1:AMD XOP support (forced to zero on non-AMD CPUs) 02.06.2018 21:44:25.115 CPUID1:MOVBE instruction 02.06.2018 21:44:25.130 CPUID1:AES-NI instruction set extension 02.06.2018 21:44:25.130 CPUID1:XSAVE bit, lack of which in combination with MOVBE is used to identify Atom Silvermont core 02.06.2018 21:44:25.146 CPUID1:OSXSAVE bit, denoting availability of YMM registers 02.06.2018 21:44:25.146 CPUID1:AVX extension 02.06.2018 21:44:25.162 CPUID1:RDRAND instruction 02.06.2018 21:44:25.162 CPUID:1 7FFAFBBF 02.06.2018 21:44:25.162 CPUID2:BMI1 instructions, e.g. ANDN 02.06.2018 21:44:25.177 CPUID2:AVX2 instructions 02.06.2018 21:44:25.177 CPUID2:BMI2 instructions, e.g. MULX and RORX 02.06.2018 21:44:25.193 CPUID2:RDSEED instruction 02.06.2018 21:44:25.208 CPUID2:ADCX and ADOX instructions 02.06.2018 21:44:25.208 CPUID:2 029C67AF 02.06.2018 21:44:25.224 CPUID:3 02.06.2018 21:44:25.224 CPUID:4 02.06.2018 21:44:25.240 CPUID:5 02.06.2018 21:44:25.240 CPUID:6 02.06.2018 21:44:25.255 CPUID:7 02.06.2018 21:44:25.255 CPUID:8 Best regards, mse -- Using The Bat! Version 8.3.0.22 (BETA) (32-bit) Pro on Windows 10 (Build 17134) (64-bit) without OTFE Current beta is 8.3.0.22 | 'Using TBBETA' information: http://www.silverstones.com/thebat/TBUDLInfo.html
Re: 8.3.0.22
Hello mse, Saturday, June 2, 2018, 10:58:54 PM, you wrote: > Nice! > My CPU can do stuff... Do you mean that your CPU supports hardware SHA-1 instructions? What CPU model do you have? -- Best regards, Maxim Masiutin Current beta is 8.3.0.22 | 'Using TBBETA' information: http://www.silverstones.com/thebat/TBUDLInfo.html
Re: 8.3.0.22
Hello mse, Saturday, June 2, 2018, 10:58:54 PM, you wrote: > My CPU can do stuff... We will implement hardware SHA-2 too. -- Best regards, Maxim Masiutin Current beta is 8.3.0.22 | 'Using TBBETA' information: http://www.silverstones.com/thebat/TBUDLInfo.html
Re: 8.3.0.22
Hello Maxim, MM> [+] New command-line parameter /LOG_IA32CPUID to write list of MM> CPU capabilities to the ex_log.txt file. Nice! My CPU can do stuff... Best regards, mse -- Using The Bat! Version 8.3.0.22 (BETA) (32-bit) Pro on Windows 10 (Build 17134) (64-bit) without OTFE Current beta is 8.3.0.22 | 'Using TBBETA' information: http://www.silverstones.com/thebat/TBUDLInfo.html
Re: 8.3.0.21
Hello Maxim, Saturday, June 2, 2018, 9:02:38 PM, you wrote: > I am interested to know. I mean the first guy who replied is very valuable for me. -- Best regards, Maxim Masiutin Current beta is 8.3.0.22 | 'Using TBBETA' information: http://www.silverstones.com/thebat/TBUDLInfo.html
Re: 8.3.0.21
Hello Anton, Saturday, June 2, 2018, 2:20:28 PM, you wrote: > no one is interested, if you got the file or not. I am interested to know. -- Best regards, Maxim Masiutin Director Ritlabs, SRL www.ritlabs.com Current beta is 8.3.0.22 | 'Using TBBETA' information: http://www.silverstones.com/thebat/TBUDLInfo.html
8.3.0.22
The Bat! 8.3.0.22 (BETA) is available at https://www.ritlabs.com/download/files3/the_bat/beta/tb83022-32.rar https://www.ritlabs.com/download/files3/the_bat/beta/tb83022-64.rar What's new in 8.3.0.22 since 8.3.0.21: [+] Support for "Intel SHA extensions" instructions for SHA-1 on CPUs that support it for hardware acceleration of SHA-1. These instructions are introduced on Intel Goldmont microarchitecture processors, e.g. Pentium J4205, Celeron J3455, Atom C3958, etc. These instructions are currently supported for 64-bit version of The Bat! only. [+] New command-line parameter (must be specified as a first parameter in order to be accepted, other parameters may follow it): "/SHA1_BENCHMARK". For example, you can run /SHA1_BENCHMARK /NOLOGO /LOG_IA32CPUID [+] New command-line parameter /LOG_IA32CPUID to write list of CPU capabilities to the ex_log.txt file. Current beta is 8.3.0.21 | 'Using TBBETA' information: http://www.silverstones.com/thebat/TBUDLInfo.html
Re: 8.3.0.21
Hello Maxim, Saturday, June 2, 2018, 5:38:47 AM, you wrote: > The Bat! 8.3.0.21 (BETA) is available at > https://www.ritlabs.com/download/files3/the_bat/beta/tb83021-32.rar Up and running. Test this version now. Jerry -- Best regards, Ethan J. Mings | Support Desk Current beta is 8.3.0.21 | 'Using TBBETA' information: http://www.silverstones.com/thebat/TBUDLInfo.html
Re: 8.3.0.21
> got it ... no one is interested, if you got the file or not. can you skip these useless comments next time, capisce? -- E-mail: lowtru...@lowtrucks.net Web site: http://lowtrucks.net/ Current beta is 8.3.0.21 | 'Using TBBETA' information: http://www.silverstones.com/thebat/TBUDLInfo.html
Re: GMail issue
Hello Cees, On Sat, 2 Jun 2018, at 11:24:16 [GMT +0200] (which was 11:24 where I live) Cees wrote: > don't get any GMail e-mails anymore. > This is the error I get: > >>2-6-2018, 11:20:17: IMAP - Owner: US, California, Mountain View, Google LLC, imap.gmail.com. >>2-6-2018, 11:20:17: IMAP - Issuer: US, California, Mountain View, Google >>LLC, imap.gmail.com. > !2-6-2018, 11:20:17: IMAP - TLS handshake failure. Invalid server > certificate. The certificate or one of the certificates in the > certificate chain does not have a valid signature.. The certificate > or certificate chain is based on an untrusted root. > 2-6-2018, 11:20:37: IMAP - Connecting to IMAP server imap.gmail.com on port > 993 > 2-6-2018, 11:20:38: IMAP - Initiating TLS handshake >>2-6-2018, 11:20:38: IMAP - Certificate S/N: 5446E3, algorithm: RSA (512 >>bits), issued from 5/29/2018 3:24:03 PM to 5/24/2038 3:24:03 PM, for 1 >>host(s): imap.gmail.com. >>2-6-2018, 11:20:38: IMAP - Owner: US, California, Mountain View, Google LLC, >>imap.gmail.com. >>2-6-2018, 11:20:38: IMAP - Issuer: US, California, Mountain View, Google >>LLC, imap.gmail.com. > !2-6-2018, 11:20:38: IMAP - TLS handshake failure. Invalid server Please check your antivirus software or The Bat! spamfilter plugin which scans SSL and lowers certificate security. -- Regards Gwen Using The Bat! Version 8.3.0.20 (BETA) (32-bit) on Windows 10.0 (Build 17134 ) pgpJcVfLkIy1l.pgp Description: PGP signature Current beta is 8.3.0.21 | 'Using TBBETA' information: http://www.silverstones.com/thebat/TBUDLInfo.html
Re: 8.3.0.21
> The Bat! 8.3.0.21 (BETA) is available at > https://www.ritlabs.com/download/files3/the_bat/beta/tb83021-64.rar thanks, Maxim. working fine here. -- E-mail: lowtru...@lowtrucks.net Web site: http://lowtrucks.net/ Current beta is 8.3.0.21 | 'Using TBBETA' information: http://www.silverstones.com/thebat/TBUDLInfo.html
8.3.0.21
The Bat! 8.3.0.21 (BETA) is available at https://www.ritlabs.com/download/files3/the_bat/beta/tb83021-32.rar https://www.ritlabs.com/download/files3/the_bat/beta/tb83021-64.rar What's new in 8.3.0.21 since 8.3.0.20: [-] If a Windows API function to resolve host name fails with an Access Violation error or other exception, The Bat! no longer uses that API function [*] The Bat! now tries to call the GetAddrInfoExW function instead of GetAddrInfoExA. Only if GetAddrInfoExW is not available, it reverts to GetAddrInfoExA. This may probably fix problems on recent Windows 10 updates Current beta is 8.3.0.21 | 'Using TBBETA' information: http://www.silverstones.com/thebat/TBUDLInfo.html
GMail issue
Hallo Tbbeta, don't get any GMail e-mails anymore. This is the error I get: >2-6-2018, 11:20:17: IMAP - Owner: US, California, Mountain View, Google LLC, imap.gmail.com. >2-6-2018, 11:20:17: IMAP - Issuer: US, California, Mountain View, Google LLC, >imap.gmail.com. !2-6-2018, 11:20:17: IMAP - TLS handshake failure. Invalid server certificate. The certificate or one of the certificates in the certificate chain does not have a valid signature.. The certificate or certificate chain is based on an untrusted root. 2-6-2018, 11:20:37: IMAP - Connecting to IMAP server imap.gmail.com on port 993 2-6-2018, 11:20:38: IMAP - Initiating TLS handshake >2-6-2018, 11:20:38: IMAP - Certificate S/N: 5446E3, algorithm: RSA (512 >bits), issued from 5/29/2018 3:24:03 PM to 5/24/2038 3:24:03 PM, for 1 >host(s): imap.gmail.com. >2-6-2018, 11:20:38: IMAP - Owner: US, California, Mountain View, Google LLC, >imap.gmail.com. >2-6-2018, 11:20:38: IMAP - Issuer: US, California, Mountain View, Google LLC, >imap.gmail.com. !2-6-2018, 11:20:38: IMAP - TLS handshake failure. Invalid server certificate. The certificate or one of the certificates in the certificate chain does not have a valid signature.. The certificate or certificate chain is based on an untrusted root. 2-6-2018, 11:21:51: IMAP - Connecting to IMAP server imap.gmail.com on port 993 2-6-2018, 11:21:52: IMAP - Initiating TLS handshake >2-6-2018, 11:21:52: IMAP - Certificate S/N: 5446E3, algorithm: RSA (512 >bits), issued from 5/29/2018 3:24:03 PM to 5/24/2038 3:24:03 PM, for 1 >host(s): imap.gmail.com. >2-6-2018, 11:21:52: IMAP - Owner: US, California, Mountain View, Google LLC, >imap.gmail.com. >2-6-2018, 11:21:52: IMAP - Issuer: US, California, Mountain View, Google LLC, >imap.gmail.com. !2-6-2018, 11:21:52: IMAP - TLS handshake failure. Invalid server certificate. The certificate or one of the certificates in the certificate chain does not have a valid signature.. The certificate or certificate chain is based on an untrusted root. anyone any idea how to solve this problem?? Thanks, Cees -- Hartelijke groet, Cees Schouten, The Hague. The Netherlands running on Windows 10 17134 0 with TheBat! 8.3 Current beta is 8.3.0.20 | 'Using TBBETA' information: http://www.silverstones.com/thebat/TBUDLInfo.html
8.3.0.20
The Bat! 8.3.0.20 (BETA) is available at https://www.ritlabs.com/download/files3/the_bat/beta/tb83020-32.rar https://www.ritlabs.com/download/files3/the_bat/beta/tb83020-64.rar What's new in 8.3.0.20 since 8.3.0.19: [-] If a Windows API function to resolve host name fails with an Access Violation error or other exception, The Bat! no longer uses that API function Current beta is 8.3.0.19 | 'Using TBBETA' information: http://www.silverstones.com/thebat/TBUDLInfo.html
