M
Matt Gilarde
Guest
I'm back from vacation and here with the "authoritative response" Garry promised. Unfortunately, the response is "We don't know exactly what happened". What we do know is that the Windows Subsystem for Linux was the cause of many of the problems OpenEdge applications had with the recent Windows 10 Creators Update. Part of the Linux subsystem is a huge update to the Windows command shell (also known as the Command Prompt). This update caused issues at many companies, not just at Progress, as judged by the large list of issues reported to Microsoft's command shell team on Github. I reported an issue with entering non-ASCII characters to the command shell team and the issue was fixed within a few weeks of reporting it. That was a different issue than the one discussed in this thread. I don't know specifically how the issue underlying the INPUT THROUGH problem was addressed by Microsoft (that is, whether they fixed it or rolled back the changes which caused it). In any case, we have made changes in OpenEdge 11.7.1 to make the implementation of INPUT THROUGH, OUTPUT THROUGH, and INPUT-OUTPUT THROUGH more robust so hopefully we won't have further issues as the evolution of the command shell continues.
Continue reading...
Continue reading...