All, I've bought a new touchscreen tablet running Windows10 with the thought it might make the drawing by up easier than on my old computer. I can't seem to get the software to load, I've enclosed an image of the screen error. I'm hoping someone here will have an idea what may be going wrong here. Best regards Gareth Davies
Hi, looks like a bug. Could you please try latest dev snapshot, whether it fixes the issue? S. On Sun, 8 Dec 2019 at 11:39, Gareth Davies <welshcavediver@gmail.com> wrote:
All,
I've bought a new touchscreen tablet running Windows10 with the thought it might make the drawing by up easier than on my old computer. I can't seem to get the software to load, I've enclosed an image of the screen error. I'm hoping someone here will have an idea what may be going wrong here.
Best regards Gareth Davies _______________________________________________ Therion mailing list Therion@speleo.sk https://mailman.speleo.sk/listinfo/therion
Gareth,
Hi, looks like a bug. Could you please try latest dev snapshot, whether it fixes the issue?
https://therion.speleo.sk/download.php See the links: 1. "Therion for Windows" - this is the main download that you will probably have used. 2. "Development files: [...] current Therion for Windows." - this is the one you should try (the one we were discussing today). Tarquin
Stacho,
Hi, looks like a bug. Could you please try latest dev snapshot, whether it fixes the issue?
We got it working, using the latest snapshot (Dec 9, 2019 from the commit 19eb624). Looks like yes, there is a fault in Therion 5.4.4. It works on my machine (classic programmer statement) - Win 10 Pro, and Gareth's main laptop (Win 8, I think), but for some reason not on Gareth's tablet (Win 10 [home?]). Don't know what fix made it work, of course. Thanks for the hint :) Tarquin
Stacho,
We got it working, using the latest snapshot (Dec 9, 2019 from the commit 19eb624).
Sorry, I was wrong. 19eb624 fixed one problem. But instead, we now get this error when compiling: ERROR: Can not execute "command.com /c "C:\\Program Files\\Therion\\therion.exe" -x cave.th (I managed to find an old thread with this same message, but there was no fix in that thread.) However, the build from commit 802ad7c works correctly. Looks like commit 19eb624 has a regression that prevents it from running on Windows 10 at least (tested on Windows 10 Home only - I don't want to nuke my working Pro version, so please don't ask me to test there ;) ). There is no "command.com" on Windows 10... Cheers, Tarquin
On Thu, Dec 12, 2019 at 09:46:08PM +0000, Tarquin Wilton-Jones via Therion wrote:
ERROR: Can not execute "command.com /c "C:\\Program Files\\Therion\\therion.exe" -x cave.th
(I managed to find an old thread with this same message, but there was no fix in that thread.)
However, the build from commit 802ad7c works correctly. Looks like commit 19eb624 has a regression that prevents it from running on Windows 10 at least (tested on Windows 10 Home only - I don't want to nuke my working Pro version, so please don't ask me to test there ;) ).
There is no "command.com" on Windows 10...
The code in xtherion/global.tcl tries to run cmd.exe first and if that fails it assumes command.com: if {[catch { set fid [open "|cmd.exe /c" r] read $fid; close $fid }]} { set xth(gui,compcmd) "command.com /c $xth(gui,compcmd)" } else { set xth(gui,compcmd) "cmd.exe /c $xth(gui,compcmd)" } This code hasn't changes for ages. Perhaps it should just assume cmd.exe these days, but for now I'd try to work out when cmd.exe /c fails on your machine. Cheers, Olly
The code in xtherion/global.tcl tries to run cmd.exe first and if that fails it assumes command.com:
I had guessed this was the approach it might use. But this would not explain why commit 802ad7c worked correctly, but 19eb624 failed. Was it maybe an installation bug?
Both of those install files (and every one released in between) installed and ran just fine on my machine. Windows 10 Home 64 bit. It has cmd.exe but not command.com Bruce -----Original Message----- From: Therion <therion-bounces@speleo.sk> On Behalf Of Tarquin Wilton-Jones via Therion Sent: Friday, 13 December 2019 11:52 To: Tarquin Wilton-Jones via Therion <therion@speleo.sk> Cc: Tarquin Wilton-Jones <tarquin.wilton-jones@ntlworld.com> Subject: Re: [Therion] New development software issue
The code in xtherion/global.tcl tries to run cmd.exe first and if that fails it assumes command.com:
I had guessed this was the approach it might use. But this would not explain why commit 802ad7c worked correctly, but 19eb624 failed. Was it maybe an installation bug? _______________________________________________ Therion mailing list Therion@speleo.sk https://mailman.speleo.sk/listinfo/therion
ERROR: Can not execute "command.com /c "C:\\Program Files\\Therion\\therion.exe" -x cave.th
The code in xtherion/global.tcl tries to run cmd.exe first and if that fails it assumes command.com:
I had guessed this was the approach it might use.
But this would not explain why commit 802ad7c worked correctly, but 19eb624 failed.
Found the cause! This is a problem that will randomly affect other users, so it would be nice if there was a proper solution within Therion. The computer has "Segurazo real-time protection" installed, but this issue could probably show up with other Anti-Virus engines too. When you ask Therion to compile, it tries to load cmd.exe. Segurazo intercepts, and tries to scan cmd.exe. This randomly completes in time (which is why we thought it worked in one version and not another). If it takes too long, Therion thinks that it was denied access, so it tries command.com instead, and fails because Windows 10 has cmd.exe We could work around it by hitting F9 twice, really quickly (so it ran the second one while the AV was still scanning it from the first time). This is all Segurazo's fault, so we uninstalled it. But surely if one AV engine does it, then so will others. It would be nice if Therion was a little more patient, and allowed AVs the time to complete, before deciding that it needed to use "command.com" instead. Cheers, Tarquin
38 years old skeleton in a closet still scares? M. Odesláno z iPhonu 18. 12. 2019 v 13:00, Tarquin Wilton-Jones via Therion <therion@speleo.sk>:
ERROR: Can not execute "command.com /c "C:\\Program Files\\Therion\\therion.exe" -x cave.th
The code in xtherion/global.tcl tries to run cmd.exe first and if that fails it assumes command.com:
I had guessed this was the approach it might use.
But this would not explain why commit 802ad7c worked correctly, but 19eb624 failed.
Found the cause! This is a problem that will randomly affect other users, so it would be nice if there was a proper solution within Therion.
The computer has "Segurazo real-time protection" installed, but this issue could probably show up with other Anti-Virus engines too. When you ask Therion to compile, it tries to load cmd.exe. Segurazo intercepts, and tries to scan cmd.exe. This randomly completes in time (which is why we thought it worked in one version and not another). If it takes too long, Therion thinks that it was denied access, so it tries command.com instead, and fails because Windows 10 has cmd.exe
We could work around it by hitting F9 twice, really quickly (so it ran the second one while the AV was still scanning it from the first time).
This is all Segurazo's fault, so we uninstalled it. But surely if one AV engine does it, then so will others. It would be nice if Therion was a little more patient, and allowed AVs the time to complete, before deciding that it needed to use "command.com" instead.
Cheers,
Tarquin _______________________________________________ Therion mailing list Therion@speleo.sk https://mailman.speleo.sk/listinfo/therion
participants (6)
-
Bruce Mutton -
Gareth Davies -
Martin Sluka -
Olly Betts -
Stacho Mudrak -
Tarquin Wilton-Jones