Oct 19, 2017, 11:07 AM
Post #1 of 4
I have scripts that run the system() procedure for years, calling a system command with parameters, like thus:
Why have my system commands stopped working(windows)
system("dir /AD /B");
This used to work fine, but recently I noticed my scripts failing, it looks like the system command is not longer handling system command parameters the same.
I get this error on the above command:
dir: cannot access '/AD': No such file or directory
dir: cannot access '/B': No such file or directory
It's not taking in the options, its trying to run the command on them. I noticed the same issue with other windows commands like rmdir.
I have been running this code for years, but we have updated our windows servers with security patches that must have changed something.
Anyone else see this and know a solution for getting the system() routine to work correctly?
Thanks a bunch