Timeline
Jan 8, 2021:
- 8:04 PM Ticket #3798 (SciTE4AutoIt incompatibilty with SSE instruction set) updated by
- Ok, adding this in the vcxproj file does the trick then for the VC2017 build: […] Previously I added this to the standard scite.mak and scitilla.mak files but that doesn't seem to work: […] Found somewhere another option to try: […] .. and uploaded that to https://www.autoitscript.com/autoit3/scite/download/beta_SciTE4AutoIt3/ia32/mak/ Could you try that version for me to see if that fixes it? Jos
- 3:25 PM Ticket #3798 (SciTE4AutoIt incompatibilty with SSE instruction set) updated by
- Btw, thanks very much for that, mLipok. I only just spotted the new username.
- 3:15 PM Ticket #3798 (SciTE4AutoIt incompatibilty with SSE instruction set) updated by
- We have progress. Having successfully installed the (2015) redistributable package, both the lite and the full versions of SciTE that you compiled with Visual Studio (in "comment9") open and seem to run fine when dropped into the beta set-up. So this means the recent Visual Studio SciTE compilations have something (that ensures compatibility with my device) that the published versions don't.
- 3:21 AM Ticket #3798 (SciTE4AutoIt incompatibilty with SSE instruction set) updated by
- Replying to Jos: > .....which I believe are standardly installed these days....... Unfortunately not. I have similar issue at my work, when we install some software on fully udpated Win10 Pro, then we must to especially install this following vcredist pack. @Ant Try to install those 3 following MS Visual C++ Redistributable package: vcredist_x86_2005.exe vcredist_x86_2008.exe vcredist_x86_2015.exe EN version->vcredist_x86_2015.exe
Jan 7, 2021:
- 9:14 AM Ticket #3800 (Number() - case sensivity with scientific notation by using $NUMBER_AUTO) closed by
- Fixed: Already solver for the next Beta/Release
- 7:48 AM Ticket #3800 (Number() - case sensivity with scientific notation by using $NUMBER_AUTO) created by
- Following Script: […] produces: […] The capitalized letter "E" …
Jan 6, 2021:
- 7:21 PM Ticket #3798 (SciTE4AutoIt incompatibilty with SSE instruction set) updated by
- I feels like you are running on a (very) old/limited OS as these files are part of the standard Microsoft Visual C ++ Redistributable package, which I believe are standardly installed these days. So it could very well be that older systems aren't compatible with the latest version of the VisualStudio compiler and SciTE options set for the compiler/linker. When this is the case, you will have to use the latest version available of WinXP on the downloadpage, unless you have other ideas. Jos
- 4:23 PM Ticket #3798 (SciTE4AutoIt incompatibilty with SSE instruction set) updated by
- Sorry for taking a while to reply. Both sets of files when placed in their respective installations produce an application error message reporting that the file MSVCP140.DLL is missing. Presumably, this is a runtime file that's been added to the project, perhaps by Visual Studio, but isn't included as a distributable with any of the AutoIt, SciTE or beta packages (and is therefore unrelated to the original error). If the file is needed, are you able to include it with the beta files?
Jan 5, 2021:
- 10:06 AM Ticket #3001 (Added AutoIt3x_64.dll to Excel Add-in list loads it as initial spreadsheet.) closed by
- Works For Me: After deep analysis with Water it is working for us
Jan 3, 2021:
- 4:01 PM Ticket #3702 (Make Execute capable of processing declarations) updated by
- Hi sorry for this long delay, but I thing that using Dim $a[$d1] or Dim $a[$d1][$d2] or Dim $a[$d1][$d2][$d3] when needed do the job no need to extend Execute() Can you provide a more complete script which can describe what you need? Thanks Happy new year
- 2:31 PM Ticket #2652 (Allow ExpandVarStrings to expand com properties as well.) updated by
-
Owner, Status changed
Hi, I introduce a new option to expand expression Opt("ExpandExpStrings", 1) to expand string containing expression such as "($vars.widget.window.title)" a COM evariable must be evaluated before it can be used. Fix sent to Jon - 8:51 AM Ticket #3525 (Support for binding to multicast group) updated by
-
Owner, Status changed
I add a new function UDPJoinMulticastGroup(Ipaddr, Port, IPMulticastGroup) I sent the fix to Jon Thank, sorry for the long delay
Jan 1, 2021:
- 6:13 AM Ticket #2866 (regread cant read x64 keys remote) updated by
-
Owner, Status changed
Fix sent to Jon
Dec 29, 2020:
- 1:47 PM Ticket #3182 (MouseGetPos may return the wrong value when used with mulitple display ...) updated by
-
Owner, Status changed
Finaly I found access to a multiple screen. I confirm that the error was in MouseMove() Fix Sent to Jon
Dec 28, 2020:
- 6:21 PM Ticket #3798 (SciTE4AutoIt incompatibilty with SSE instruction set) updated by
- Ok, well I have no idea at this moment why the full version crashes and have no means to test. When the official version of SciTE also crashes, it does make sense my full version does too as that is more or less similar. I do not see any obvious difference between the lite and full builds of SciTE. I have done a recompile of the lite and the full version with visual studio 2017 and put them in this directory in their own subdirectory: https://www.autoitscript.com/autoit3/scite/download/beta_SciTE4AutoIt3/ia32/ Could you try both version to see if it is still the case that the lite version works and the full version crashes? Jos
- 10:29 AM Ticket #2835 (Change the TCP*() funktions to optional use non blocking ports.) closed by
- Completed: Sorry to be so late on the subject. I recheck the AutoIt code and find out that TCPConnect() is doing exactly except for the Shutdown(ConSock, 2); in fact this possibility has been added in a new TCPShutdownSocket(2) perhaps in your case the complete closing of the socket is better with the new extension of the TCPCloseSocket(sock, 2)
Dec 27, 2020:
- 11:11 PM Ticket #3575 (TCP functions slow and TCPCloseSocket with shutdown) updated by
-
Summary changed
- 10:51 PM Ticket #3575 (TCP functions slow and TCPCloseSocket with shutdown) updated by
-
Owner, Status changed
Re thinking of the pb I think it can be useful to add a TCPShutdownSocket(listensocket,1) which can be called before TCPCloseSocket(listensocket) this can be combined with an extension of TCPCloseSocket(listensocket, 1) Addition sent to Jon My last addition are to help the Jos finding. Nothing to do with TCP Slowdown I could have open another ticket - 10:47 PM Ticket #3575 (TCP functions slow and TCPCloseSocket with shutdown) reopened by
- 5:09 PM Ticket #3798 (SciTE4AutoIt incompatibilty with SSE instruction set) updated by
- Yes... dropping the two files into a full / fresh installation of SciTE4AutoIt. (I don't know what the dependencies are.) Plus, my working environment is SciTE-Lite and I don't want to break it.
- 4:59 PM Ticket #3575 (TCP functions slow and TCPCloseSocket with shutdown) closed by
- Works For Me: sorry for this very late updating under the current beta every thing work fine. #1 is OK #3 is even a little be better
Dec 25, 2020:
- 2:17 PM Ticket #2695 (For ... in ... next loop modifying items) closed by
- Rejected: Sorry for the so late answer. But the doc has been written on what can be reasonably implemented, so we will not add such improvement
- 10:39 AM Ticket #2794 (FileDelete ability to remove the file stream) closed by
- Rejected: Sorry for the late answer, In fact the internal autoIt code handle wildcard so it involve a lot of internal change So as _WinAPI_DeleteFile() is OK just use it for Metadata
Dec 24, 2020:
- 3:20 PM Ticket #3799 (_ChooseFont (Canceling the dialog) suggestion.) closed by
- No Bug: @error not zero should be checked […]
- 3:08 PM Ticket #3731 (Binary() performs hidden and wrong conversion on strings) updated by
-
Owner changed
- 12:56 PM Ticket #3799 (_ChooseFont (Canceling the dialog) suggestion.) created by
- Currently, when the _ChooseFont is called, and the font dialog is …
- 11:09 AM Ticket #3798 (SciTE4AutoIt incompatibilty with SSE instruction set) updated by
- Full install? You only need to copy the 2 files right?
- 8:35 AM Ticket #3798 (SciTE4AutoIt incompatibilty with SSE instruction set) updated by
- No. Neither the standard SciTE nor the new ia32 files work. (Did a full installation for both.)
Dec 22, 2020:
- 2:20 PM Ticket #3798 (SciTE4AutoIt incompatibilty with SSE instruction set) updated by
- Does the standard SciTE binary work for you? available here: https://www.scintilla.org/wscite32_446.zip Could you also redownload the files from ia32 and test those as I think I have used the wrong mak parameter the last time. Thanks Jos
Dec 21, 2020:
- 11:12 PM Ticket #3798 (SciTE4AutoIt incompatibilty with SSE instruction set) updated by
- No. The ia32 files give the same result. Apologies. I've just discovered it's not possible to copy and paste Windows' error report. This is the error signature. AppName: scite.exe AppVer: 4.2.0.0 ModName: scite.exe ModVer: 4.2.0.0 Offset: 000415ce Here's the CPU-related info. CPU Properties: CPU Type..........Intel Celeron, 1100 MHz (11 x 100) CPU Alias..........Coppermine-128 CPU Stepping..........cD0 Instruction Set..........x86, MMX, SSE Original Clock..........1100 MHz L1 Code Cache..........16 KB L1 Data Cache..........16 KB L2 Cache..........128 KB (On-Die, ATC, Full-Speed) Instruction Set: 64-bit x86 Extension (AMD64, Intel64)..........Not Supported AMD 3DNow!..........Not Supported AMD 3DNow! Professional..........Not Supported AMD 3DNowPrefetch ..........Not Supported AMD Enhanced 3DNow!..........Not Supported AMD Extended MMX..........Not Supported AMD FMA4..........Not Supported AMD MisAligned SSE..........Not Supported AMD SSE4A..........Not Supported AMD XOP..........Not Supported Cyrix Extended MMX..........Not Supported Enhanced REP MOVSB/STOSB..........Not Supported Galois Field New Instructions (GFNI)..........Not Supported Float-16 Conversion Instructions..........Not Supported IA-64..........Not Supported IA AES Extensions..........Not Supported IA AVX..........Not Supported IA AVX2..........Not Supported IA AVX-512 (AVX512F)..........Not Supported IA AVX-512 4x Fused Multiply-Add Single Precision (AVX512_4FMAPS)..........Not Supported IA AVX-512 4x Neural Network Instructions (AVX512_4VNNIW)..........Not Supported IA AVX-512 52-bit Integer Multiply-Add Instructions (AVX512_IFMA)..........Not Supported IA AVX-512 Bit Algorithm (AVX512_BITALG)..........Not Supported IA AVX-512 Byte and Word Instructions (AVX512BW)..........Not Supported IA AVX-512 Conflict Detection Instructions (AVX512CD)..........Not Supported IA AVX-512 Doubleword and Quadword Instructions (AVX512DQ)..........Not Supported IA AVX-512 Exponential and Reciprocal Instructions (AVX512ER)..........Not Supported IA AVX-512 Neural Network Instructions (AVX512_VNNI)..........Not Supported IA AVX-512 Prefetch Instructions (AVX512PF)..........Not Supported IA AVX-512 Vector Bit Manipulation Instructions (AVX512_VBMI)..........Not Supported IA AVX-512 Vector Bit Manipulation Instructions 2 (AVX512_VBMI2)..........Not Supported IA AVX-512 Vector Length Extensions (AVX512VL)..........Not Supported IA AVX-512 VPOPCNTDQ..........Not Supported IA BMI1..........Not Supported IA BMI2..........Not Supported IA FMA..........Not Supported IA MMX..........Supported IA SHA Extensions..........Not Supported IA SSE..........Supported IA SSE2..........Not Supported IA SSE3..........Not Supported IA Supplemental SSE3..........Not Supported IA SSE4.1..........Not Supported IA SSE4.2..........Not Supported Vector AES (VAES)..........Not Supported VIA Alternate Instruction Set..........Not Supported ADCX / ADOX Instruction..........Not Supported CLDEMOTE Instruction..........Not Supported CLFLUSH Instruction..........Not Supported CLFLUSHOPT Instruction..........Not Supported CLWB Instruction..........Not Supported CLZERO Instruction..........Not Supported CMPXCHG8B Instruction..........Supported CMPXCHG16B Instruction..........Not Supported Conditional Move Instruction..........Supported Fast Short REP MOV Instruction..........Not Supported INVPCID Instruction..........Not Supported LAHF / SAHF Instruction..........Not Supported LZCNT Instruction..........Not Supported MONITOR / MWAIT Instruction..........Not Supported MONITORX / MWAITX Instruction..........Not Supported MOVBE Instruction..........Not Supported MOVDIR64B Instruction..........Not Supported MOVDIRI Instruction..........Not Supported PCLMULQDQ Instruction..........Not Supported PCOMMIT Instruction..........Not Supported PCONFIG Instruction..........Not Supported POPCNT Instruction..........Not Supported PREFETCHWT1 Instruction..........Not Supported PTWRITE Instruction..........Not Supported RDFSBASE / RDGSBASE / WRFSBASE / WRGSBASE Instruction..........Not Supported RDRAND Instruction..........Not Supported RDSEED Instruction..........Not Supported RDTSCP Instruction..........Not Supported SKINIT / STGI Instruction..........Not Supported SYSCALL / SYSRET Instruction..........Not Supported SYSENTER / SYSEXIT Instruction..........Supported Trailing Bit Manipulation Instructions..........Not Supported VIA FEMMS Instruction..........Not Supported VPCLMULQDQ Instruction..........Not Supported WBNOINVD Instruction..........Not Supported
- 12:45 PM Ticket #3797 (PCRE update to recent PCRE-8.44 or even to PCRE2-10.36) closed by
- No Bug: I cn not get a pcretest-10.36.exe as the 8.44 does change the result from 8.41, I close the ticket
Dec 20, 2020:
- 8:37 PM Ticket #3798 (SciTE4AutoIt incompatibilty with SSE instruction set) updated by
- Replying to Ant: > Yes. I spotted that too late. Replaced the existing SciTE.exe with the beta. Yep. Same again. Also tried dropping the rest of the beta files (except the SciTELite and discontinued folders) into the SciTE folder just in case. > > Would Windows' error report be any help? I could also give you a list of the instruction sets, etc. that the target machine does/doesn't support. Could you first try the version in the subdirectory ia32? You require both SciTE.exe & scilexer.dll Thanks, Jos
- 8:24 PM Ticket #3798 (SciTE4AutoIt incompatibilty with SSE instruction set) updated by
- Yes. I spotted that too late. Replaced the existing SciTE.exe with the beta. Yep. Same again. Also tried dropping the rest of the beta files (except the SciTELite and discontinued folders) into the SciTE folder just in case. Would Windows' error report be any help? I could also give you a list of the instruction sets, etc. that the target machine does/doesn't support.
- 7:29 PM Ticket #3798 (SciTE4AutoIt incompatibilty with SSE instruction set) updated by
- Strange as the full version and the lite version use the same project file. Does the current Beta version also have this problem? https://www.autoitscript.com/autoit3/scite/download/beta_SciTE4AutoIt3/ By the way: The referred ticket talks about disabling the SSE option: Dang. Visual Studio 2012 enables the SSE option by default even though I'd not explicitly set it. I'll have force it to be disabled. I'll recompile it with this option for any 3.3.10.2+ release.
- 6:51 PM Ticket #3798 (SciTE4AutoIt incompatibilty with SSE instruction set) created by
- SciTE4AutoIt (version 19.1127.1402.0) crashes immediately. …
Dec 19, 2020:
- 9:02 PM Ticket #3797 (PCRE update to recent PCRE-8.44 or even to PCRE2-10.36) updated by
- not sue to get an executable version for pcre2 10.36 but for 8.41 […]
Dec 18, 2020:
- 11:31 PM Ticket #3797 (PCRE update to recent PCRE-8.44 or even to PCRE2-10.36) updated by
- Replying to Jpm: > in fact pcretest.exe 8.44 give the following result Please post the same kind of result but generated by pcretest.exe 8.41 and regardles of the fact that @Jon said "no no no" ... please also show the same kind of result but generated by pcretest.exe 10.36 Then it will be possible to compare results from all this 3 versions of pcretest.exe (8.41 ... 8.44 ... 10.36) . As for now the way how pcretest.exe show results is is not very readable (for people like me accustomed to a different way of giving the result of a RegEx query). And for this reason comparative data are needed.
- 9:29 PM Ticket #3797 (PCRE update to recent PCRE-8.44 or even to PCRE2-10.36) updated by
- in fact pcretest.exe 8.44 give the following result so I don't know which is right […]
- 8:37 PM Ticket #3797 (PCRE update to recent PCRE-8.44 or even to PCRE2-10.36) updated by
- I check 8.44 same result …
- 6:38 PM Ticket #3797 (PCRE update to recent PCRE-8.44 or even to PCRE2-10.36) updated by
- I will look at 8.44 for PCRE2 noway Jon answer it was a too big change (snif snif)
Dec 17, 2020:
- 8:00 PM Ticket #3797 (PCRE update to recent PCRE-8.44 or even to PCRE2-10.36) updated by
-
Version changed
Automatic ticket cleanup. - 7:40 PM Ticket #3797 (PCRE update to recent PCRE-8.44 or even to PCRE2-10.36) updated by
-
Description changed
- 7:36 PM Ticket #3797 (PCRE update to recent PCRE-8.44 or even to PCRE2-10.36) created by
- In fact there was recently closed ticket: …
Dec 15, 2020:
- 8:39 AM Ticket #3538 (Make ByRef parameters for _PathSplit optional) closed by
- Fixed: I asked @jpm in PM on the forum about this: https://www.autoitscript.com/trac/autoit/ticket/3540#comment:5 Answer: Should be fixed together with #3540
- 8:38 AM Ticket #3538 (Make ByRef parameters for _PathSplit optional) reopened by
Dec 13, 2020:
- 2:46 AM Ticket #3540 (Implement optional ByRef parameters for functions) updated by
- Replying to TheDcoder <TheDcoder@…>: > Ticket #3538 can be completed if this feature request was accepted! @jpm what you can say about #3538 which TheDcoder mentioned above.
Note:
See TracTimeline
for information about the timeline view.
