On Sat Aug 30 17:01:29 2025 +0000, eric pouech wrote:
Thanks for the answers. A) I was wondering if there were a specific handling for devices vs per device specific behaviors. As copy /b com1 is handled in binary whereas copy /b con isn't (and assuming you did test "copy /b con foo" and not "copy con foo /b"), keeping per device behavior looks a good choice. B) For the tests I would add: Copy /a con+in out Copy /a in+con out Copy /b con+in out Copy /b in+con out Copy con+in out Copy in+con out Where in is a file containing a ctrl-z, and checkin in out file the final result (just to be sure that forcing ascii for con has no impact on prev/next copied files)
I ran each of the tests that you specified, on both native Win10 and Wine with my changes. Behaviour seems correct. In cases where /b was specified, the ^Z character was preserved in the output file. In cases where /b was not specified, the ^Z character did not exist in the output file. Behaviour on both Win10 and Wine were the same. In no case was the ^Z character removed from the input file.
I did discover a new bug with the TYPE command. On Win10, TYPE terminates output at the ^Z character. Wine outputs the ^Z character and continues to output the remaining characters until the end of the file.