It seems trying to redirect the echo off command (at least under windows
in a cmd prompt) does indeed create the echoed test on the screen
because of the STDERR being directed to the screen as stated above.
Regular echo commands however do redirect just fine
<shrug>
I'm fairly certain though that at some point I did solve this issue, and
I'd seriously thought it was via redirects. Perhaps other dos versions
(PTTS/open handle things differently, though I'd not expect it. I don't
currently have either one of those environments available for testing
though, so can't say for sure if they'd behave identically or not.
On 2/26/2022 9:37 AM, Travis Siegel wrote:
On 2/26/2022 9:14 AM, Mateusz Viste wrote:
On 26/02/2022 15:09, Travis Siegel wrote:
Barring those solutions, you could always redirect the @echo off
line to null, which would prevent it from displaying on the screen.
It would not, since the error message is output to stderr.
That's not been my experience, but it has been a while since I've used
MSDOS, so perhaps on that particular version, your statement is true.
I've generally stuck to PTS dos, or opendos where ever possible, and
redirecting batch file output to null works just fine on those dos
versions. (at least it did when I last used them, which admittedly
has been a few years).
_______________________________________________
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user
_______________________________________________
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user
