Commander Not Printing All The Time フォローする
We print about 300 labels a day. Of those about about 1-5% of these do not print. (about 3-15 a day)
Commander log shows them as printed and has renamed the file.
I can then rename the file that did not print to the trigger name and it will then print.
After trying many things I believe commander – is renaming the
file before bartender has read it and printed it.
Is there a way to delay the commander renaming the file?
In your documentation you changed the locking process (see
below) – I wonder if changing this to lock the file again might help - Is
there a way to turn on Commander's file-locking scheme? _ as I am
"Unfortunately, it was recently learned that this
Windows-based file-locking methodology was not compatible with some non-Windows
file servers. Because it is common to have non-Windows file servers and
NOT common to have multiple instances of Commander scanning the same folder,
SR2 now turns off Commander's file-locking scheme by default."