Title: | Digital PATHWORKS 32 |
Moderator: | SPELNK::curless |
Created: | Fri Nov 01 1996 |
Last Modified: | Fri Jun 06 1997 |
Last Successful Update: | Fri Jun 06 1997 |
Number of topics: | 337 |
Total number of notes: | 1612 |
I have a customer that is trying to create a script file that uses the EXEC command to call a DOS batch file that runs a Basic Program. He has tried it, and it does not appear to work. He has given the whole path for the .exec, but cannot get it to work. He did the EXEC "notepad.exe" and that does work fine. Is this supported? Is it supposed to work? He has tried Procomm and that does what he wants it to. Thanks, Bryna Gesson DTN: 343-1048
T.R | Title | User | Personal Name | Date | Lines |
---|---|---|---|---|---|
263.1 | JAMIN::WASSER | John A. Wasser | Thu May 01 1997 17:39 | 11 | |
> trying to create a [PowerTerm] script file that uses the EXEC command > to call a DOS batch file that runs a Basic Program. > He did the EXEC "notepad.exe" and that does work fine. Perhaps he can try: EXEC "command.com -c batch.bat" Note: He may have to specify the path to command.com if the correct version is not in whatever search path that PowerTerm uses. | |||||
263.2 | should use CMD.EXE not COMMAND.COM on NT | SPELNK::curless | Thu May 01 1997 17:56 | 9 | |
Or if using NT how about: EXEC "%SystemRoot%\system32\cmd.exe /c batch.bat" You might want to add /q (turn off echo) and /x (enable NT version of the CMD.EXE extensions). Jeff |