View Single Post
Old 12-07-2018, 09:29 AM   #132
DaltonST
Deviser
DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.DaltonST ought to be getting tired of karma fortunes by now.
 
DaltonST's Avatar
 
Posts: 2,265
Karma: 2090983
Join Date: Aug 2013
Location: Texas
Device: none
Quote:
But next time they were locked again.
Yes, and the message at startup tells you why, and that it is only "briefly". That "briefly" message is a good thing. Exit properly, restart, and all is normal.

The Customization has a spinbox to select the number of hours to wait for "orphaned locks". CS assumes a multi-user environment, including a single user running CS for the same library multiple times, and when it goes into safe mode, it has "orphaned locks". Set the spinbox to the lowest value, 2 hours. Also keep the .bat file to remove them immediately handy.

"Crash" means "command box closed before properly exiting CS via the Exit button". Or, exiting from Windows before properly exiting CS first.


DaltonST
DaltonST is offline   Reply With Quote