> While MSDOS had subdirectories, pipes were not supported at the kernel level. It was simply a convenience of COMMAND.COM that simulated pipes by running each command sequentially.
You are confusing the lack of concurrency with lack of pipes -- the mere fact that COMMAND can do what you describe requires UNIX-like pipes and channels (e.g. stdin/out/err), and programs avoiding direct console I/O (way common for DOS programs...). Comm software such as Kermit did the same thing to simulate remote login (I used this one in the day, at least).
https://forum.winworldpc.com/discussion/comment/171783/#Comm... (devices in \dev, "-" as switch char, etc.).
> While MSDOS had subdirectories, pipes were not supported at the kernel level. It was simply a convenience of COMMAND.COM that simulated pipes by running each command sequentially.
You are confusing the lack of concurrency with lack of pipes -- the mere fact that COMMAND can do what you describe requires UNIX-like pipes and channels (e.g. stdin/out/err), and programs avoiding direct console I/O (way common for DOS programs...). Comm software such as Kermit did the same thing to simulate remote login (I used this one in the day, at least).