Record locking refinement (Windows): After about 15 seconds of looping on a lock request, A-Shell now displays the lock pending trace messages which previously only displayed if the LOCKS TRACE flag was set. The idea is that after 15 seconds, chances are that the user will think the process has hung, which may lead to unnecessary tech support / debugging; the lock pending message, however cryptic, will at least make clear the cause of the delay.
The messages appear on the bottom status line. In another refinement, the bottom status line will be automatically enabled, if necessary so the messages can be seen, without overwriting possibly important screen text on line 24.
One further refinement: when the user hits ^C to abort from a lock wait, the lock event is now always logged to the ashlog.log file. Previously, lock events were only logged if both the LOCKS and PERF TRACE flags were set.
