Date
1 - 8 of 8
2019.1.1 released
|
Quentin Christensen
My apologies for the delay in replying - but since it has been a few days - how are you both going now? Did you get 2019.1 / 2019.1.1 installed ok? I did have someone report this issue (I think was it you Brian?) but we never got to the bottom of it, and we weren't able to replicate it. On Tue, Apr 16, 2019 at 6:14 PM Brian's Mail list account via Groups.Io <bglists=blueyonder.co.uk@groups.io> wrote: Yes this is win 7 as well. I have a suspicion that in fact the error occurs --
Quentin Christensen Training and Support Manager Official NVDA Training modules and expert certification now available: http://www.nvaccess.org/shop/ Facebook: http://www.facebook.com/NVAccess Twitter: @NVAccess |
|
|
|
Quentin Christensen
Howard, I've been busy this week so haven't caught up on messages, but do try this release and let us know either way (you probably already have - I will get to it!) I'm glad to hear it's working for others, and Brian there is definitely something about your system that plays up with new versions, but I'm glad it is working again now. We will get to the bottom of it one of these days. Quentin. On Tue, Apr 16, 2019 at 4:45 AM Howard Traxler <howard@...> wrote:
--
Quentin Christensen Training and Support Manager Official NVDA Training modules and expert certification now available: http://www.nvaccess.org/shop/ Facebook: http://www.facebook.com/NVAccess Twitter: @NVAccess |
|
|
|
Brian's Mail list account
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 message
Show quoted text
Its just one of those odd things. Brian bglists@... Sent via blueyonder. Please address personal E-mail to:- briang1@..., putting 'Brian Gaff' in the display name field. ----- Original Message -----
From: "Laurie Mehta via Groups.Io" <lauriemehta@...> 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@...> 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@... Sent via blueyonder. Please address personal E-mail to:- briang1@..., putting 'Brian Gaff' in the display name field. |
|
|
|
Howard Traxler <howard@...>
This may be my answer (19.1.1) rather than going back to earlier versions.
(See my question, probably posted later.)
Howard On 4/15/2019 1:26 PM, Rosemarie
Chavarria wrote:
|
|
|
|
Rosemarie Chavarria
Hi, Quentin,
I just downloaded it and it's working great for me.
Rosemarie
On 4/15/2019 5:13 AM, Quentin
Christensen wrote:
|
|
|
|
Laurie Mehta
I had that experience when updating to 2019.1 on my Win7 laptop. Interesting...
toggle quoted message
Show quoted text
-LM -------------------------------------------- On Mon, 4/15/19, Brian's Mail list account via Groups.Io <bglists@...> 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@... Sent via blueyonder. Please address personal E-mail to:- briang1@..., putting 'Brian Gaff' in the display name field. |
|
|
|
Brian's Mail list account
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.
toggle quoted message
Show quoted text
Anyway its working now again. Brian bglists@... Sent via blueyonder. Please address personal E-mail to:- briang1@..., putting 'Brian Gaff' in the display name field. ----- Original Message -----
From: "Quentin Christensen" <quentin@...> To: <nvda@nvda.groups.io> Sent: Monday, April 15, 2019 1:13 PM Subject: [nvda] 2019.1.1 released Hi everyone, |
|
|
|
Quentin Christensen
Hi everyone, We've released NVDA 2019.1.1. This release addresses some issues including a crash and formulas not reporting in Excel2007, a crash in Google Chrome, and an issue when copying settings to secure screens. Read the full notes and download from: https://www.nvaccess.org/post/nvda-2019-1-1-update-available-for-download/ If check for updates is enabled, NVDA itself should find the update in the next day or so and offer it to you. Kind regards Quentin |
|
|