FIXED: Terminal: executables are not always executed
Posted: 15 Sep 2021 09:09
1) When I write anything, that is not recognized as a name of an executable or batch script in the current directory, I get this message:
2) When I try to execute a real executable, but not in the current directory, I get the same response. Command prompt is lost.
3) I need to go to the directory and only then I can execute my executable -- the last part of the animation below (gray rectangle) shows a part of its screen; btw this executable is RIOT, Radical Image Optimization Tool, superb freeware program (once plugin to IrfanView), the best one I know for manual control over the PNG/JPG/GIF optimization process (only static files).
Command prompt is lost.Executable or batch file
2) When I try to execute a real executable, but not in the current directory, I get the same response. Command prompt is lost.
3) I need to go to the directory and only then I can execute my executable -- the last part of the animation below (gray rectangle) shows a part of its screen; btw this executable is RIOT, Radical Image Optimization Tool, superb freeware program (once plugin to IrfanView), the best one I know for manual control over the PNG/JPG/GIF optimization process (only static files).