Powershell call fails with "Scripting Integrator 2016 (PowerShell)" license error

May 20, 2017
I seem to have a little trouble getting powershell to work from within TCC 21. Powershell itself works:

D:\bin\btm> powershell get-help get-help


Displays information about Windows PowerShell commands and concepts.

[… remainder of output elided …]

D:\bin\btm> ver /r

TCC 21.00.27 x64 Windows 10 [Version 10.0.15063]
TCC Build 27 Windows 10 Build 15063
Registered to FKL

Regrettably, the owners of IPworks somehow have their fingers in this pie, too:

D:\bin\btm> echo %@pshell[get-help get-help]
[Error message is displayed, see attached screen shot]

D:\bin\btm> pshell /s get-help get-help
[Error message is displayed, see attached screen shot; then:]
PSHELL: Could not find a valid license for Scripting Integrator 2016 (PowerShell) in this system. For more information, please visit www.nsoftware.com.

This happens after a number of attempts that just report the error "PSHELL: The library file is missing or specified functions can't be found."

Soon after the license error pops up, TCC becomes unstable and crashes.

Any help is appreciated.



May 20, 2017
This is a bug in the updated version of the third-party library. I'm rolling it back to the previous version pending a fix from the developers and will post a new TCMD build today.
Thank you for the speedy response and, of course, for the 23 years that I've been using 4DOS, 4NT and now TCC/TCMD!

I don't know exactly what is happening, but the command in my previous post causes a file named "]" to be created in the CWD.
v:\> d ]*

v:\> echo %@pshell[get-help get-help]
TCC: (Sys) The process cannot access the file because it is being used by another process.

v:\> d ]*
2017-05-24  01:00               0  ]