[Bug 21132] 'cmd echo on' sometimes fails

http://bugs.winehq.org/show_bug.cgi?id=21132

--- Comment #6 from Frédéric Delanoy  2011-11-09 19:58:38 CST ---
(In reply to comment #0)
> $ rm a
> $ wine cmd
> Z:\home\austin>echo on > a
> Z:\home\austin>type a
> on
>
> but running:
> austin@laptop:~$ wine cmd /c echo on > a
> austin@laptop:~$ cat a
>
> shows an empty file.

On w2k, 'echo on > a' sets echo mode, and creates an empty "a" file
Similar results when "cmd /c echo on > a" is used (except caller's echo mode is
not altered)

I'm not quite sure why one would want to use commands like 'echo on > a' though