>>> 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 [email protected] https://mailman.speleo.sk/listinfo/therion
