Since this happens, apparently, in the Prince step, perhaps you could manually run Prince on command line with different output paths, and see if you can reproduce the error with some combination of long filename and "unusual" characters.
Quote:
|
Nothing wrong with Windows 10. It's quote good.
|
Do you mean it's "good"
