On Thu, 19 Oct 2023, at 06:12, Brian Westerman wrote: > In fact, it works VERY well. I don't mind the dos boxes opening and > closing, they are REALLY fast and if there wern't so many of them you > probably would not notice that anything happened.
In the past I've used a small utility named SilentCMD which suppresses those briefly-opening cmd.exe terminal windows. I found it especially useful for commands run from the Windows task scheduler & commands run before & after profiles run by a backup utility where the annoying flash of a briefly opened window would happen at unpredictable moments. It's available from: https://github.com/stbrenner/SilentCMD Despite the comments which suggest it's just for running .bat or .cmd files I often used it for running ooRexx execs ie my first argument was often "rexx.exe". My old notes suggest that rexxhide.exe (meant to run an exec without a console window) didn't work properly (though I don't remember precisely how, nor which version of ooRexx that was with) when the exec was started by the task scheduler, but that using SilentCMD.exe solved that. Stephan Brenner also has a basic website (from which you can find his linkedin profile) at: https://www.stephan-brenner.com There's also a forked version that apparently supports use with Powershell or Python scripts, & makes changes to logging & use of work directories, at: https://github.com/mikefirefly/SilentCMD though I've not tried that one. -- Jeremy Nicoll - my opinions are my own. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
