Welcome!

By registering with us, you'll be able to discuss, share and private message with other members of our community.

SignUp Now!

@PSHELL?

May
12,804
161
Both of these work at a Powershell prompt.

Code:
V:\> (get-item .\timecheck.btm).length
1446

V:\> (get-item .\timecheck.btm:nist.txt).length
853

Only one of these works at a TCC prompt.

Code:
v:\> echo %@pshell[(get-item .\timecheck.btm).length]
1446

v:\> echo %@pshell[(get-item .\timecheck.btm:nist.txt).length]
ECHO is OFF

Any ideas?
 
In my previous post I was using TCC v27. It's better in v26.

Code:
v:\> *ver

TCC  26.02.43 x64   Windows 10 [Version 10.0.19042.685]

v:\> echo %@pshell[(get-item .\timecheck.btm).length]
1446

v:\> echo %@pshell[(get-item .\timecheck.btm:nist.txt).length]
853
 
Sadly my eval tcc27 expired weeks ago. At the time I had to use a piped echo to remove the "unknown command"
as for streams tcc hasn't been able to report on stream name properties at all
 
All of the Powershell integration is handled by NSILP_PowerShell.x64.dll (which hasn't changed between v26 & v27).

The only difference in the TCC code for Powershell between v26 & v27 is if you've defined a custom profile ID (PowerShellProfileID=xxxx). Otherwise, v26 & v27 are identical.
 

Similar threads

Back
Top