Quote:
Originally Posted by correnos
Great. So I have to get a VM running just to download code to the stupid bot?
|
The point wasn't that you need a VM to do this, the idea was that it works on a cleanly installed computer...
Here is some advice from WindRiver:
I've seen Workbench fail before with this message: "cannot execute command: cmd", this basically means the Windows the customer is running on cannot find cmd.exe in it's path, this is very unusual indeed.
The last time we saw this we made the customer add "%SystemRoot%\system32\" to his path and then run workbench, in this case I'd suggest to alter the path and then re-install from scratch since postinstall might not work in such cases either...
You can update the path variable in the System properties (right click on the computer name in explorer), then properties, then "Advanced" tab. Then "Environment variables", then under the "System variables" area, edit the one called PATH. Make sure that "%SystemRoot%\system32\" is in the list, and if not add it using a semicolon to separate it from the other items in the list.
Since I can't duplicate the problem, I can't know for sure if this will fix your situation.