Yes what I was referring to was to get it to reboot when its in the mood to crash, as by definition you are typing blind and probably not typing to anything!
toggle quoted messageShow quoted text
Sent via blueyonder.
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
Newsgroup monitored: alt.comp.blind-users
----- Original Message -----
From: "Cyrille via Groups.Io" <email@example.com>
Sent: Friday, October 18, 2019 8:51 AM
Subject: Re : Re: [nvda-devel] Hmm.. Anyone had issues restarting Alpha snaps today?
To restart NVDA with add-ons disabled, you can press Windows+R and type the following:
nvda -r --disable-addons
Then press Enter.
Once you have restarted without add-ons, you may disable the suspected add-on and restart normally.
----- Mail d'origine -----De: Brian's Mail list account via Groups.Io <firstname.lastname@example.org>À: nvda-devel@...é: Fri, 18 Oct 2019 09:37:39 +0200 (CEST)Objet: Re: [nvda-devel] Hmm.. Anyone had issues restarting Alpha snaps today?
I'm suspicious that it might be something to do with the new dev version of the sounds add on. I'll need to deactivate it and wait for some more updates to the alpha to tell. It cannot be proved simply by restarting with add ons off as by definition, when its locked you cannot go in and turn stuff off!
bglists@... via blueyonder.Please address personal E-mail to:-briang1@..., putting 'Brian Gaff'in the display name field.Newsgroup monitored: alt.comp.blind-users----- Original Message ----- From: "Luke Davis" <luke@...>To: "NVDA Dev list on groups.io" <email@example.com>Sent: Thursday, October 17, 2019 10:36 AMSubject: Re: [nvda-devel] Hmm.. Anyone had issues restarting Alpha snaps today?
No such problems on last couple alphas on Win 10 64 bit 1903.>> On Thu, 17 Oct 2019, Brian's Mail list account via Groups.Io wrote:>>> I did a download yesterday, and found that it locked the machine up after >> the rising tones to load it. I rebooted the installed stable and that >> took an age to come up, one assumes it had to force closure. This morning >> another alpha update and the same thing happened again. Now of course >> once it has worked once, you get no further issues so I'm thinking it >> might be something to do with writing to a file which of course cannot be
>> logged if it cannot write to it. This is Windows 7, but I do not know apart from one very useful change, of anything that might appear to
cause >> this for me, as updates seem to have been fine for weeks till now.>> Brian>> >