This particular one is caused by the file path exceeding 260 chars and the program not handling the error.
The result is that the program stops (crashes) during the file copy sequence.
If any of the files up to then have less than 260 chars they will have been copied. Any remaining files won't be copied. Hence the apparent intermittency of it.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Long file paths are supported by Windows if you are on a Win 10 build after about #1609, but you still have to call things slightly differently programatically.
Also added an error and (optional) comment logging scheme that puts a text file in C:\ProgramData\SpecProc2Browser\SpecProc2Browser
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
This particular one is caused by the file path exceeding 260 chars and the program not handling the error.
The result is that the program stops (crashes) during the file copy sequence.
If any of the files up to then have less than 260 chars they will have been copied. Any remaining files won't be copied. Hence the apparent intermittency of it.
Ok. v1.1 covers this.
Long file paths are supported by Windows if you are on a Win 10 build after about #1609, but you still have to call things slightly differently programatically.
Also added an error and (optional) comment logging scheme that puts a text file in
C:\ProgramData\SpecProc2Browser\SpecProc2Browser