03-25-2024, 02:34 PM
The only 100% workaround that I've found is just to write the shell command into a batch file and then call it from there. Crazy, but it is what it is.
I found another SHELL that was almost impossible to deciper the other day. It was something like:
foo print 123 > text.txt
From the command line, it worked with no isses.
From SHELL, it ended up having to be something like:
SHELL chr$(34) + "powershell 'foo print 123' > text.txt" + CHR$(34)
The entire powershell command had to be listed inside the single quotes, so it'd process as a single command, and then *everything* had to be encased in quotes so that CMD wouldn't break it apart into multiple, fractional calls to crap.
Lord, the hoops to ump throug, for something so simple!!
I found another SHELL that was almost impossible to deciper the other day. It was something like:
foo print 123 > text.txt
From the command line, it worked with no isses.
From SHELL, it ended up having to be something like:
SHELL chr$(34) + "powershell 'foo print 123' > text.txt" + CHR$(34)
The entire powershell command had to be listed inside the single quotes, so it'd process as a single command, and then *everything* had to be encased in quotes so that CMD wouldn't break it apart into multiple, fractional calls to crap.
Lord, the hoops to ump throug, for something so simple!!