Well I just updated to the latest master and it failed to restart. the error screen one could not read said it could not write to the log file and it thus stayed shut down. A manual start started it. I did look at the old log and noted that it was still dealing with attempting to delete old bits of files when it was asked to shut down, watchdog stopped then it all stopped with only the old error of multiple whatever they are then silence. I suspect as I said in the original ticket for this. its so busy processing locked files that when it comes to rename nvda.log to nvda.old.log it fails and hence does not create it and just gives up writing a log in the program files called nvda.exe.log which is the lack of ability to write to the log that it should have started as a new log but in fact is still locked in a queue waiting for windows to catch up and rename the old one!
Clear as mud? Well the good news is an easc and a restart of nvda is all it needes. Windowa 7 in this case.
Brian

bglists@...
Sent via blueyonder.
Please address personal email to:-
briang1@..., putting 'Brian Gaff'
in the display name field.