Re-installed from here: https://github.com/iseahound/Vis2/archive/master.zip
But once executed, following the instructions here: https://github.com/iseahound/Vis2
... I ended up with the (kinda expected) error message about ~"[tesseract] not compatible with the system ...
I'd guess it's (still) compiled as a 32bit executable not running on (my) Win 7 64bit with AHKU64.exe
Using the tesseract.exe from a few days ago is showing up empty results but won't fail during execution.
a) while the "(file in) folder structure" setup is explicitly mentioned/advised here: https://autohotkey.com/boards/viewtopic ... 89#p168389
b) ... it's shown differently here: https://github.com/iseahound/Vis2
c) ... and it extracts from the zip the same way as described in b) not as in a)
Question, why not already provide the file you've advised to create manually (let's name it "my.ahk") ...
"Create a new AHK script in the same folder as Vis2.ahk, copying the code below."
... within the zip-archive that gets extracted to Vis2's root
folder, while Vis2.ahk itself will be hosted within the lib-folder (together with a local copy of an image and Gdip_All.ahk)
Based on that, the #Include-path within my.ahk would have been adjusted to point to Vis2.ahk in the lib-folder accordingly. All except the "capture text manually"-samples could be already part of my.ahk!
That would provide the user that "WOW"-effect right from scratch, and would decrease the number of support requests bc of errors made by the most error-prone part of scripting: me in front of the keyboard