Re: 2019.1.1 released
|
Brian's Mail list account <bglists@...>
Yes this is win 7 as well. I have a suspicion that in fact the error occurs due to all the failed to removed messages at update time hanging onto the current log file and hence when the new copy starts the old log is locked rather than renamed to old as it should be. Whether the routines in 7 are slower or its as I say something in the hardware or software that compounds it, I have no idea, but only a handful of people have the issue and its not every time either, and it proved impossible to duplicate by any developer back several issues ago, It all started when renaming folderrs so the correct support files were used was brought in by Mick to solve another issue.
toggle quoted messageShow quoted text
Its just one of those odd things. Brian bglists@blueyonder.co.uk Sent via blueyonder. Please address personal E-mail to:- briang1@blueyonder.co.uk, putting 'Brian Gaff' in the display name field.
----- Original Message -----
From: "Laurie Mehta via Groups.Io" <lauriemehta=yahoo.com@groups.io> To: <nvda@nvda.groups.io> Sent: Monday, April 15, 2019 4:22 PM Subject: Re: [nvda] 2019.1.1 released I had that experience when updating to 2019.1 on my Win7 laptop. Interesting... -LM -------------------------------------------- On Mon, 4/15/19, Brian's Mail list account via Groups.Io <bglists=blueyonder.co.uk@groups.io> wrote: Subject: Re: [nvda] 2019.1.1 released After a long absence this release gave me the windows error again when it tried to reboot that the log file could not be written to and then it wrote a small log to the other log file that is in the working directory. I had to clear the error then reboot and then its fine again. I wish we could get to the bottom of this, but I fancy its harrdare or software affected and hence a pig to debug. Anyway its working now again. Brian bglists@blueyonder.co.uk Sent via blueyonder. Please address personal E-mail to:- briang1@blueyonder.co.uk, putting 'Brian Gaff' in the display name field.
|
|
|