Hi roger,
I would try installing NVDA again on your desktop. Actually, any screen reader should be uninstalled and then reinstalled after up grading to win10. NVDA should show up in your notification area with your volume and those icons. You should also have a NVDA icon on your desktop. Take care.


-----Original Message----- From: Roger Stewart
Sent: Saturday, June 4, 2016 4:50 PM
To: nvda@nvda.groups.io
Subject: [nvda] nvda and win 10

My desktop was just forced to upgrade to Win 10. This seems to have
worked just fine. However, nvda isn't showing up at all in Ease Of
Access Center as it is on my laptop with Win 10. Can anyone help?


Thanks.


Roger







.

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Brian Vogel
Sent: June-04-16 8:56 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] WIN 10 startup sound

Yep, but getting it to actually play is a bit more complicated than it used to be.

With the advent of Windows 8 a new feature called Fast Start is enabled by default.  When this is enabled shutting down your computer does not really shut down your computer but instead puts it into a modified version of hibernation where the full system state is stored in a hibernation file (hiberfile) but the user state (e.g., the programs you were running, etc.) is not included like it is in full hibernation.  So, when you restart a system that has been shut down using shut down you will not get the startup sound if Fast Start is enabled.  You will always get the startup sound when you do a Restart because, oddly, this forces a full shut down before automatically kicking off a system boot from scratch.

If you want to turn off Fast Start I believe I've already posted a step-by-step on how to do that in this forum or on one of the other blind and low-vision technology related forums and I can dig that up on request.
--
Brian

I worry a lot. . . I worry that no matter how cynical you become it's never enough to keep up.

If you turn off the colour announcment what happens then?
Brian

bglists@...
Sent via blueyonder.
Please address personal email to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
----- Original Message -----
From: "Danni" <luv2ride67@...>
To: <nvda@nvda.groups.io>
Sent: Friday, June 03, 2016 9:06 PM
Subject: Re: [nvda] Weird issue

No because sometimes I can hear colors or options and sometimes I can't! which tells me something is going on I just don't know what!

----- Original Message -----
From: "Andre Fisher" <andrefisher729@...>
To: <nvda@nvda.groups.io>
Sent: Friday, June 03, 2016 8:46 AM
Subject: Re: [nvda] Weird issue

Maybe the site's layout was changed, don't you think?

On 6/3/16, Danni <luv2ride67@...> wrote:

No I can't see it! things are not in the usual place normally on the page it

shows or reads item number then title of item pics and such then price size

color description and so on with of course buttons for adding to cart and
such but it's moving colors before sizing it's too early my brain can't
think of all changes but it's moved around though sometimes it will read the

page the way it normally is!

I don't know how to explain it but will check firefox thanks anyway
----- Original Message -----
From: "Brian's Mail list account" <bglists@...>
To: <nvda@nvda.groups.io>
Sent: Friday, June 03, 2016 1:23 AM
Subject: Re: [nvda] Weird issue

When you say moved around, can you see the screen? Often those who can and

also use speech complain that the order is different for the screenreader

to the sighted user. In my mind this implies muddled accessability bolted

on as an afterthought.
If other sites behave as you would expect, its probably the site. Might be

worth trying it in another browser.
Brian

bglists@...
Sent via blueyonder.
Please address personal email to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
----- Original Message -----
From: "Danni" <luv2ride67@...>
To: <nvda@nvda.groups.io>
Sent: Friday, June 03, 2016 6:54 AM
Subject: [nvda] Weird issue


I'm not sure if it's NVDA or I?E that is causing the issue but when I go
to qvc.com and read through the page the colors are not being read and I
noticed too that the page is mixed around am not sure how to explain it
exactly but things are out of place and i can't figure out what to check
in order to fix it?

Hi,

When I tried NVDA (latest version) with Chrome 51, NVDA still doesn't read the character that I've deleted in a number of text boxes, specifically the Facebook status composing box and I think this applies to all textareas.

Is this a NVDA bug or a Chrome bug?

Okay. I can completely understand that. I didn't have to re-add many words, as I've added very few since last august, but as I don't remember where the dictionary files that I created are stored, and since I've hardly tinkered with anything in that location since the year before last, I haven't backed up those dictionaries yet. Please don't be angry with me. I wasn't dismissing your advice out-of-hand. I was, however, still recovering from the shock of nearly losing use of my computer due to my screwing up (without a screen reader, I may as well not have a computer), and alternating between thanking God I had a portable copy so close at hand and cursing the file that had gotten me into this mess in the first place.

I was saying what I did in case you wanted to experiment with NVDA in future.  I was saying that experimenting with a portable version is safe.  I was addressing the question for the future because there may be times when you would benefit significantly by making changes to NVDA. 

 

Also, my speech dictionary is not large but I have built it up slowly during a number of years.  I have it backed up so I can put a new copy into NVDA if necessary.  It is important to do this to guard against loss of the dictionary. 

 

Gene

----- Original Message -----

From: Sharni-Lee Ward

Sent: Saturday, June 04, 2016 8:54 AM

To: nvda@nvda.groups.io

Subject: Re: [nvda] espeak issue fixed

Regardless, I'm not messing with that again until there's a more official fix for the problem. That was the most harrowing half hour of my life and I have no desire to relive it.

On 4/06/2016 11:06 PM, Gene wrote:

It isn't a case of experimenting or not experimenting.  Backing up the folder so you could replace it with the original should be done if you are ever going to experiment in this way.  or, you could have the installer create a portable version and experiment with that.  Dictionary files can, and should, be backed up regardless of whether you experiment with NVDA.  They should be backed up just as any files you don't want to lose should be backed up. 

 

Gene

From: Sharni-Lee Ward

Sent: Saturday, June 04, 2016 7:44 AM

To: nvda@nvda.groups.io

Subject: Re: [nvda] espeak issue fixed

...

I just did this and succeeded in screwing up my copy of NVDA. I copied in the "Espeak Data" folder as was suggested, and suddenly everything NVDA was saying was incomprehensible to me. I tried to undo what I'd done. All I ended up with was silence. Horrible, horrible, unbroken silence. With sighted help, I did a system restore, which accomplished nothing, then had to resort to using a portable copy of NVDA which I hadn't updated since 2015.2, uninstalling NVDA from my computer, reinstalling it from the portable copy and updating it back to 2016.2. I've probably lost a few dictionary entries and I'm right back where I started, but I infinitely prefer speech with a few squished syllables to no NVDA at all. Did I mention after I tried undo NVDA wouldn't even start, probably because it's default synth had been stuffed around with? Oh yeah, it did that.

I am never, ever messing with my screen readers data files again.

On 4/06/2016 7:21 PM, Shaun Everiss wrote:

Hi all.
Ok here is a solution to the espeak issue.
This will go on the skype group as well
https://www.dropbox.com/s/7e35z5au9bc05vh/espeak.7z?dl=1
Anyway, testing looks as if its the espeakdata itself either the phonem or the actual synth data.
What I did.
While I was not able to find previous releases of 2016-2015 in compiled form I was able to find via sourceforge 2014.4 and this had espeak in it.
I coppied over the espeakdata folder over itself in nvda program folder.
While this will have to be done for just about every coppy it does mean that while espeak will remain the new ng with the voice as it is, the squished crap is at least back to normal.
I have not tried to override the espeak dll but the link has 2 folders synthdrivers which has the old espeak state from 2014.4 and the new ng dataset.
Anyway, it looks like its the data files rather than the driver itself.
So if we can figure out what the hell is going on with this, then it may be easier to fix than we first thought.
Now I didn't replace the driver because although it has some harsh elements I wanted to see what this would do.
Its fixed it such that the mangled squished elements are gone.
This file will remain up until at least we can fix it.
Aniother way is to download the latest old espeak sapi and run it I have yet to see compiled ng binaries for windows sapi, etc so till we see that and as long as sourceforge keeps the depricated espeak project up we will be ok.
To the devs and such trying to solve this especially if you have access to the espeak list which I have no desire to handle and since this may happen on multiple platforms it seems to be the database itself or something in the database causing the trouble currently faced.
I am unsure about what part of the database is naff though, this will require some other beepstard to troubleshoot.
I'd like to but I have never fiddled with this and pluss I am not that interested.
For all users though this is one way out of the current issue for now.
The buty of this is as long as we replace the data we can still use the latest engine.
I will keep other units the same however as it is not needed that we fiddle with our units like this but at least for my own personal it will work.

I was saying what I did in case you wanted to experiment with NVDA in future.  I was saying that experimenting with a portable version is safe.  I was addressing the question for the future because there may be times when you would benefit significantly by making changes to NVDA. 

 

Also, my speech dictionary is not large but I have built it up slowly during a number of years.  I have it backed up so I can put a new copy into NVDA if necessary.  It is important to do this to guard against loss of the dictionary. 

 

Gene

----- Original Message -----

From: Sharni-Lee Ward

Sent: Saturday, June 04, 2016 8:54 AM

To: nvda@nvda.groups.io

Subject: Re: [nvda] espeak issue fixed

Regardless, I'm not messing with that again until there's a more official fix for the problem. That was the most harrowing half hour of my life and I have no desire to relive it.

On 4/06/2016 11:06 PM, Gene wrote:

It isn't a case of experimenting or not experimenting.  Backing up the folder so you could replace it with the original should be done if you are ever going to experiment in this way.  or, you could have the installer create a portable version and experiment with that.  Dictionary files can, and should, be backed up regardless of whether you experiment with NVDA.  They should be backed up just as any files you don't want to lose should be backed up. 

 

Gene

From: Sharni-Lee Ward

Sent: Saturday, June 04, 2016 7:44 AM

To: nvda@nvda.groups.io

Subject: Re: [nvda] espeak issue fixed

...

I just did this and succeeded in screwing up my copy of NVDA. I copied in the "Espeak Data" folder as was suggested, and suddenly everything NVDA was saying was incomprehensible to me. I tried to undo what I'd done. All I ended up with was silence. Horrible, horrible, unbroken silence. With sighted help, I did a system restore, which accomplished nothing, then had to resort to using a portable copy of NVDA which I hadn't updated since 2015.2, uninstalling NVDA from my computer, reinstalling it from the portable copy and updating it back to 2016.2. I've probably lost a few dictionary entries and I'm right back where I started, but I infinitely prefer speech with a few squished syllables to no NVDA at all. Did I mention after I tried undo NVDA wouldn't even start, probably because it's default synth had been stuffed around with? Oh yeah, it did that.

I am never, ever messing with my screen readers data files again.

On 4/06/2016 7:21 PM, Shaun Everiss wrote:

Hi all.
Ok here is a solution to the espeak issue.
This will go on the skype group as well
https://www.dropbox.com/s/7e35z5au9bc05vh/espeak.7z?dl=1
Anyway, testing looks as if its the espeakdata itself either the phonem or the actual synth data.
What I did.
While I was not able to find previous releases of 2016-2015 in compiled form I was able to find via sourceforge 2014.4 and this had espeak in it.
I coppied over the espeakdata folder over itself in nvda program folder.
While this will have to be done for just about every coppy it does mean that while espeak will remain the new ng with the voice as it is, the squished crap is at least back to normal.
I have not tried to override the espeak dll but the link has 2 folders synthdrivers which has the old espeak state from 2014.4 and the new ng dataset.
Anyway, it looks like its the data files rather than the driver itself.
So if we can figure out what the hell is going on with this, then it may be easier to fix than we first thought.
Now I didn't replace the driver because although it has some harsh elements I wanted to see what this would do.
Its fixed it such that the mangled squished elements are gone.
This file will remain up until at least we can fix it.
Aniother way is to download the latest old espeak sapi and run it I have yet to see compiled ng binaries for windows sapi, etc so till we see that and as long as sourceforge keeps the depricated espeak project up we will be ok.
To the devs and such trying to solve this especially if you have access to the espeak list which I have no desire to handle and since this may happen on multiple platforms it seems to be the database itself or something in the database causing the trouble currently faced.
I am unsure about what part of the database is naff though, this will require some other beepstard to troubleshoot.
I'd like to but I have never fiddled with this and pluss I am not that interested.
For all users though this is one way out of the current issue for now.
The buty of this is as long as we replace the data we can still use the latest engine.
I will keep other units the same however as it is not needed that we fiddle with our units like this but at least for my own personal it will work.

Oh, well I was told you can't change the start sound as windows opens. I
had a friend who wanted to do that. but couldn't do it for some reason.
Just the same. I like the start up sound for 7. I think I heard someone say
vista had that sound then it went to 7. Does Ten have that sound like 7
does?

-----Original Message-----
From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Ron
Canazzi
Sent: June-03-16 6:28 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA Curiosity

Hi Arlene,


Ah yes, but I saved all the XP sounds and if you put them in your
/windows/media folder in Windows 7, you could--if you wish--assign the
sounds as such in Windows 7.



On 6/3/2016 8:22 PM, Arlene wrote:

No, You can't put the start sound that xp used at start up. I like the
sound start up for windows 7. Does ten have that same sound at start up

like

you would in 7?

-----Original Message-----
From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Ron
Canazzi
Sent: June-03-16 12:57 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA Curiosity

Hi Carlos,


Yes, you are right. For sentimental reason, I kept an old XP SP3
system--mostly for storage and because I finagled a way to play some DOS
games on it through the command line structure. But just this past
week, the old faithful gave up the ghost: some sort of motherboard issue
as well as a shaky hard drive. So I decided to replace it with a
reconditioned Windows 7 Home Premium system for about $125 plus tax. I
am used to having tons of back-ups in the event of a calamity so I am
comfortable with 3 computers: my 2 Windows 8 systems (one to be upgraded
shortly to ten or when I get the nerve) and the old XP system, now to be
replaced with the Windows 7 reconditioned box. Oh for the tragedy of
not hearing that old XP boot sound! I know you can configure the new
system with the old sounds--but just like dating a blonde you really
liked and then when she dumps you dating another blonde; it's really not
quite the same <laugh>!


...And so it goes.



On 6/3/2016 2:49 PM, Carlos wrote:

Hello:

The newer the PC/machine; the less problems are encountered with
new software!

At some point some NVDA users will be hit with the reality that
Windows XP has lived a very very long life and wants to retire/be left
alone!

There are a number of charitable organizations/groups that sell
rebuilt PC's at economical prices that at least run Windows 7.

There are a number of software developers that warn customers that
their software no longer will support vintage PC's!

So, if users insist on continued usage of old PC's/machines. Then
don't complain/whine when operating systems/software does not run
correctly on your machines!

Yes! I do sound like an old curmudgeon! And, I'm very proud to
represent my age group! (55 Years and above)



On 6/3/2016 11:29 AM, Roger Stewart wrote:

I'm having no problems with the newest nvda and I use Firefox and
Thunderbird--no issues at all.

Roger








On 6/3/2016 1:01 PM, Chris Shook wrote:

This goes along with my last post labeled NVDA devils advocate.
Over the last few days, I've noticed a lot of people pointing out
issues with the latest version of NVDA.
For a little perspective, how many people are not having these issues.
So far, everything has worked fine for me.
Is there any one else that is not having any problems with NVDA 2016.2?
Chris

Hi!
NVDA 2016.2 is working fine for me as well: I haven't spotted any issues
since I installed the latest full version.
Bye for now!
From Clare

-----Original Message-----
From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Andre
Fisher
Sent: vendredi 3 juin 2016 20:03
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA Curiosity

I have no problems with it. I love it!

On 6/3/16, Chris Shook <chris0309@...> wrote:

This goes along with my last post labeled NVDA devils advocate.
Over the last few days, I've noticed a lot of people pointing out
issues with the latest version of NVDA.
For a little perspective, how many people are not having these issues.
So far, everything has worked fine for me.
Is there any one else that is not having any problems with NVDA 2016.2?
Chris

Regardless, I'm not messing with that again until there's a more official fix for the problem. That was the most harrowing half hour of my life and I have no desire to relive it.

It isn't a case of experimenting or not experimenting.  Backing up the folder so you could replace it with the original should be done if you are ever going to experiment in this way.  or, you could have the installer create a portable version and experiment with that.  Dictionary files can, and should, be backed up regardless of whether you experiment with NVDA.  They should be backed up just as any files you don't want to lose should be backed up. 

 

Gene

From: Sharni-Lee Ward

Sent: Saturday, June 04, 2016 7:44 AM

To: nvda@nvda.groups.io

Subject: Re: [nvda] espeak issue fixed

...

I just did this and succeeded in screwing up my copy of NVDA. I copied in the "Espeak Data" folder as was suggested, and suddenly everything NVDA was saying was incomprehensible to me. I tried to undo what I'd done. All I ended up with was silence. Horrible, horrible, unbroken silence. With sighted help, I did a system restore, which accomplished nothing, then had to resort to using a portable copy of NVDA which I hadn't updated since 2015.2, uninstalling NVDA from my computer, reinstalling it from the portable copy and updating it back to 2016.2. I've probably lost a few dictionary entries and I'm right back where I started, but I infinitely prefer speech with a few squished syllables to no NVDA at all. Did I mention after I tried undo NVDA wouldn't even start, probably because it's default synth had been stuffed around with? Oh yeah, it did that.

I am never, ever messing with my screen readers data files again.

On 4/06/2016 7:21 PM, Shaun Everiss wrote:

Hi all.
Ok here is a solution to the espeak issue.
This will go on the skype group as well
https://www.dropbox.com/s/7e35z5au9bc05vh/espeak.7z?dl=1
Anyway, testing looks as if its the espeakdata itself either the phonem or the actual synth data.
What I did.
While I was not able to find previous releases of 2016-2015 in compiled form I was able to find via sourceforge 2014.4 and this had espeak in it.
I coppied over the espeakdata folder over itself in nvda program folder.
While this will have to be done for just about every coppy it does mean that while espeak will remain the new ng with the voice as it is, the squished crap is at least back to normal.
I have not tried to override the espeak dll but the link has 2 folders synthdrivers which has the old espeak state from 2014.4 and the new ng dataset.
Anyway, it looks like its the data files rather than the driver itself.
So if we can figure out what the hell is going on with this, then it may be easier to fix than we first thought.
Now I didn't replace the driver because although it has some harsh elements I wanted to see what this would do.
Its fixed it such that the mangled squished elements are gone.
This file will remain up until at least we can fix it.
Aniother way is to download the latest old espeak sapi and run it I have yet to see compiled ng binaries for windows sapi, etc so till we see that and as long as sourceforge keeps the depricated espeak project up we will be ok.
To the devs and such trying to solve this especially if you have access to the espeak list which I have no desire to handle and since this may happen on multiple platforms it seems to be the database itself or something in the database causing the trouble currently faced.
I am unsure about what part of the database is naff though, this will require some other beepstard to troubleshoot.
I'd like to but I have never fiddled with this and pluss I am not that interested.
For all users though this is one way out of the current issue for now.
The buty of this is as long as we replace the data we can still use the latest engine.
I will keep other units the same however as it is not needed that we fiddle with our units like this but at least for my own personal it will work.