T
TomStevens6
In our Fortran output files resulting from a technical analysis, it has been our practice to echo the input data file at the front of output computed. Because a Fortran print file will result, it is also necessary to place a blank character in front of each echoed input line lest the first datum character be interpreted as carriage control.
This has always worked swimmingly for earlier Windows systems prior to Windows 10. When we moved our technical computing over to Windows 10 from Windows 7, however, some input echo lines would go missing. There would practically always be a few.
If you view the link: Anomaly , you will find three files:
@FOR /F "usebackq tokens=1 delims=" %%i in (INFILE) do @echo %%i >> "OUTBACK"
I have taken the above command from a larger script. The name of the input file INFILE and the output file OUTBACK are hard coded in the command, as above and within Decko.bat. In the script, they would be coded in via environment variables.
So to see the anomaly in action, you can compare the existing OUTBACK with INFILE (lines shifted a character to the right). You can also rename the OUTBACK supplied and generate a new OUTBACK of your own. Do this by opening a Windows 10 command prompt window, cd'ing to the folder in which you have placed the files and enter the command:
Decko
Wait for a bit for it to complete. It takes a bit of time when run this way (and can give the impression of not working). Eventually, it does finish and yields a new OUTBACK. You will find that some of the lines have been skipped. If you compare your new OUTBACK with the original renamed, you will probably find they are not the same, that different lines have been skipped. And if you repeat the experiment, different INFILE lines will probably be skipped each time.
Once again, this happens only for Windows 10 among the operating systems tried. It did not happen with XP, Windows 10 or the Windows we use on our technical servers. And it happens with Windows 10 on the Ienovo technical machines we use at my company and on the ASUS machine I have at home on which Windows 10 is also installed.
Continue reading...
This has always worked swimmingly for earlier Windows systems prior to Windows 10. When we moved our technical computing over to Windows 10 from Windows 7, however, some input echo lines would go missing. There would practically always be a few.
If you view the link: Anomaly , you will find three files:
- Decko.bat is a batch run file with the one command which we use to accomplish this input echo
- INFILE is a suitable input deck.
- OUTBACK is the generated target file: lines from INFILE shifted one character to the right.
@FOR /F "usebackq tokens=1 delims=" %%i in (INFILE) do @echo %%i >> "OUTBACK"
I have taken the above command from a larger script. The name of the input file INFILE and the output file OUTBACK are hard coded in the command, as above and within Decko.bat. In the script, they would be coded in via environment variables.
So to see the anomaly in action, you can compare the existing OUTBACK with INFILE (lines shifted a character to the right). You can also rename the OUTBACK supplied and generate a new OUTBACK of your own. Do this by opening a Windows 10 command prompt window, cd'ing to the folder in which you have placed the files and enter the command:
Decko
Wait for a bit for it to complete. It takes a bit of time when run this way (and can give the impression of not working). Eventually, it does finish and yields a new OUTBACK. You will find that some of the lines have been skipped. If you compare your new OUTBACK with the original renamed, you will probably find they are not the same, that different lines have been skipped. And if you repeat the experiment, different INFILE lines will probably be skipped each time.
Once again, this happens only for Windows 10 among the operating systems tried. It did not happen with XP, Windows 10 or the Windows we use on our technical servers. And it happens with Windows 10 on the Ienovo technical machines we use at my company and on the ASUS machine I have at home on which Windows 10 is also installed.
Continue reading...