Difference between revisions of "Batch File Not Running"
Jump to navigation
Jump to search
Chris Huxley (talk | contribs) |
Chris Huxley (talk | contribs) |
||
| Line 4: | Line 4: | ||
<br> | <br> | ||
=Suggestions= | =Suggestions= | ||
| − | This is most likely caused by using a " "(space) before and/or after the "=" in the batch file after the set variable command<br> | + | This is most likely caused by using a " "(space) before and/or after the "=" in the batch file after the set variable command<br> |
For example (incorrect format): | For example (incorrect format): | ||
{| class="wikitable " | {| class="wikitable " | ||
| Line 12: | Line 12: | ||
|} | |} | ||
To solve this issue, please remove the " "(space) next to the "=".<br> | To solve this issue, please remove the " "(space) next to the "=".<br> | ||
| − | + | For example (correct format): | |
{| class="wikitable " | {| class="wikitable " | ||
|- | |- | ||
Revision as of 15:29, 1 February 2018
Description
When running TUFLOW with a batch file and setting the TUFLOW executable path of other commands as variable, the command prompt shows error and no simulations are executed (as shown below).
Suggestions
This is most likely caused by using a " "(space) before and/or after the "=" in the batch file after the set variable command
For example (incorrect format):
set TUFLOWEXE = C:\TUFLOW\Releases\2017-09-AC\w64\TUFLOW_iSP_w64.exe |
To solve this issue, please remove the " "(space) next to the "=".
For example (correct format):
set TUFLOWEXE=C:\TUFLOW\Releases\2017-09-AC\w64\TUFLOW_iSP_w64.exe |