no need to apologize... getting patches into Wine is always a bit constrained because of ensuring that we mimic Windows' behavior... and cmd is even more combersome as testing cmd is even more constrained for testing, you can subscribe to testbot.winehq.org (there you can test on several windows versions) I recommend if you can test first locally (your Win10 setup is a good choice), then run the changes in testbot for all default test env (anyway the patch will be tested in the integration pipeline against these, so better test in advance), then update the MR... concerning your failing code, you could use: ``` cmd /c `block_if_eof1.cmd` ``` with a comment explaining why you need to enclose the test inside another instance of cmd (and I don't thing there's lot of value to check %errorlevel% upon cmd exit)
-
eric pouech (＠epo)