1. nvda@nvda.groups.io
  2. Messages
   Date   
Re: Accessible Word Processor Biblos--Why did I never know about this?

Lanie Molinar
 

I just downloaded this and will be trying it out. I've been using LibreOffice, but I'm always open to trying other options, and I like that this supports Markdown.


On Fri, Aug 6, 2021 at 2:41 PM Jackie <abletec@...> wrote:
Ok, so I guess this is not strictly NVDA-related per se, though the
program does have an addon specifically for use w/NVDA. Here's some of
the impressive features the software offers.

It's called Biblos, & it allows the opening and saving of files of an
incredible number of formats, to include .docx, .doc, .rtf, Markdown
(woohoo!) & more. & no, woohoo is *not* a file format lol. It's just
that those who know me even a little know what a fangirl of Markdown I
am.

It allows printing of files to Braille.

It allows drawing of vector graphics, especially for tactile graphics,
but also for any purpose where vector graphics can be used. Thus, we
can draw pictures using text representations.

It allows typical formatting all word processors have in common, ie,
bold, italic, headings, endnotes, footnotes, etc.

I hate to say it, but I think 1 of the reasons this little gem has
been overlooked is because the gentleman who programmed it seems to be
fluent only in Italian, & translation of the software into other
languages is kind of automated. So yeah--some of the help guide syntax
is a bit awkward, but folks, really--I consider myself pretty well
acquainted w/what's out there, & I haven't encountered this 1 before.
Yall can get it at:
http://www.digrande.it/en/Biblos.aspx

Once downloaded, go to the scripts folder and install the NVDA addon
appropriate to your version of NVDA, & you're golden.

For those looking for a free and accessible alternative to Word, you
might wish to check this 1 out! As for me, adios, Jarte, as well as to
my now unsupported version of Word.

--
Subscribe to a WordPress for Newbies Mailing List by sending a message to:
wp4newbs-request@... with 'subscribe' in the Subject field OR by
visiting the list page at http://www.freelists.org/list/wp4newbs
& check out my sites at www.brightstarsweb.com & www.mysitesbeenhacked.com
Re: Introducing NVDA-addons.org, the largest international add-ons store with official and unofficial add-ons from all NVDA communities

Brian Vogel
 

Iván,

Trouble report:  If you change the sort order using the drop-down on the first page, it only works on the first page.  When hit the Next link on the bottom of  page one the subsequent page reverts to your default ordering.

--

Brian - Windows 10, 64-Bit, Version 21H1, Build 19043  

Nothing in all the world is more dangerous than sincere ignorance and conscientious stupidity.

         ~Martin Luther King, Jr.

 
Re: Resource: Youtube Video From Thee Quinn: How to Use Microsoft Access With NVDA: Part 1

Brian Vogel
 

On Fri, Aug 6, 2021 at 08:36 PM, Gary Metzler wrote:
Does anyone know if there are any more parts to this series?
-
Yes.  She has a channel with a many additional videos, including, but not limited to, Part 2 of this series.

https://www.youtube.com/channel/UCGp2C2CdwO824TvdIfhqAcQ 
 
--

Brian - Windows 10, 64-Bit, Version 21H1, Build 19043  

Nothing in all the world is more dangerous than sincere ignorance and conscientious stupidity.

         ~Martin Luther King, Jr.

 
Re: Resource: Youtube Video From Thee Quinn: How to Use Microsoft Access With NVDA: Part 1

Gary Metzler
 

Does anyone know if there are any more parts to this series?

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Brian Vogel
Sent: Friday, August 6, 2021 7:31 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Resource: Youtube Video From Thee Quinn: How to Use Microsoft Access With NVDA: Part 1

 

On Fri, Aug 6, 2021 at 11:03 AM, tim wrote:

You know its interesting just how far and how much its lost with JFW and its access with Microsoft office products have dropped.

-
I honestly have no idea how to interpret this statement.

I've been around JAWS since JFW 10 (I think, it might have been 9) and I have seen nothing but an upward trend in accessibility for MS-Office programs, with the exception of MS-Access, on the whole.

I'd say, in fact, that accessibility in general, across the board, has been on nothing but an upward trend with the occasional (and really frustrating) one step back after multiple steps forward.  And most of those steps back do not seem to be the result of intent, but because of either an actual bug or because a given screen reader maker is not keeping up with changes Microsoft is making.  There are very few changes to Microsoft software that are not announced, and even development versions made available, well in advance of their actual release.  The last time I witnessed big screen reader lag was at the introduction of Windows 10 back in 2015, and almost all of it was because the screen reader software was not updated in a timely manner for something known to have been coming for some time in advance.
--

Brian - Windows 10, 64-Bit, Version 21H1, Build 19043  

Nothing in all the world is more dangerous than sincere ignorance and conscientious stupidity.

         ~Martin Luther King, Jr.

 
Re: Introducing NVDA-addons.org, the largest international add-ons store with official and unofficial add-ons from all NVDA communities

Iván Novegil
 

Hi.


I've kept the current default option, that is, it moves most recently updated add-ons to the top of the table, but also added a combo box to choose if you want to order it by name or summary, A-Z. I've also added a checkbox to only show official add-ons as a quick solution for grouping by official and unofficial, but I'll look into it deeper in the following days, since some more suggestions where made that would need to rebuild the SQL query structure and the table.


Regards.

Iván Novegil Cancelas
Equipo de xestión web e desenvolvemento



Asociación Comunidad Hispanohablante de NVDA
- Tel.: (+34) 910 05 33 25 ext. 2000
- ivan.novegil@...
- www.NVDA.es
- @nvda_es

Usuario do NVDA en galego

***Esta mensaxe e/ou os seus adxuntos están dirixidos ao seu destinatario e poden conter información privilexiada ou confidencial. A utilización, copia ou divulgación dos mesmos por parte de alguén diferente do destinatario mencionado non están permitidas sen autorización. Se recibiu esta mensaxe por erro pregámoslle o comunique por esta mesma vía e a destrúa.***

O 07/08/2021 á(s) 1:23, Brian Vogel escribiu:

Iván,

I'll never argue that giving the user the ability to choose their sort order is a bad idea.  Better than sticking with my suggestion as a fixed "one and only" option.  I still think it makes sense as a default option, but others may feel very differently.

But when this comes to fruition some default order will need to be selected.

--

Brian - Windows 10, 64-Bit, Version 21H1, Build 19043  

Nothing in all the world is more dangerous than sincere ignorance and conscientious stupidity.

         ~Martin Luther King, Jr.

 
Re: Does anyone have any tips for clicking on links that won’t click with NVDA

Tony Malykh
 

Here are a few options to try:
1. Try NVDA+Enter. Sometimes it works better on links that don't work with just Enter.
2. NVDA+NumPadSlash, then NumPadSlash. This routes mouse cursor and simulates a click.
3. Just NVDA+NumPadSlash. Since you mentioned there is hover over menu, it might appear at this point, and you might be able to navigate either using arrows or tab to other menu items. And then try options 1 and 2 on them.
4. If everything else fails, you might want to ask someone sighted to click this once for you and put down URL it takes you to. So next time you can either just go to that URL directly if it is constant, or if it contains any IDs you can think of a way to reconstruct it with correct IDs every time you need to use it.

On 8/6/2021 9:41 AM, Khalid Anwar wrote:
I’m using A website calledCACs Enterprise by CGI it’s a billing and payment platform, one of the problems I’m having is that there is a link which is actually a hover over menu, so hovering over it with the mouse will open up a list of other options but NVDA sees it only as a link.
i’ve tried clicking it but I’ve had no luck, and pressing shift plus NVDA  plus M to move the mouse over it, NVDA will read out the options on the list but there is no way to get at them to click them.
Does anyone have any ideas or tips?
Re: Resource: Youtube Video From Thee Quinn: How to Use Microsoft Access With NVDA: Part 1

Brian Vogel
 

On Fri, Aug 6, 2021 at 11:03 AM, tim wrote:
You know its interesting just how far and how much its lost with JFW and its access with Microsoft office products have dropped.
-
I honestly have no idea how to interpret this statement.

I've been around JAWS since JFW 10 (I think, it might have been 9) and I have seen nothing but an upward trend in accessibility for MS-Office programs, with the exception of MS-Access, on the whole.

I'd say, in fact, that accessibility in general, across the board, has been on nothing but an upward trend with the occasional (and really frustrating) one step back after multiple steps forward.  And most of those steps back do not seem to be the result of intent, but because of either an actual bug or because a given screen reader maker is not keeping up with changes Microsoft is making.  There are very few changes to Microsoft software that are not announced, and even development versions made available, well in advance of their actual release.  The last time I witnessed big screen reader lag was at the introduction of Windows 10 back in 2015, and almost all of it was because the screen reader software was not updated in a timely manner for something known to have been coming for some time in advance.
--

Brian - Windows 10, 64-Bit, Version 21H1, Build 19043  

Nothing in all the world is more dangerous than sincere ignorance and conscientious stupidity.

         ~Martin Luther King, Jr.

 
Re: Introducing NVDA-addons.org, the largest international add-ons store with official and unofficial add-ons from all NVDA communities

Brian Vogel
 

Iván,

I'll never argue that giving the user the ability to choose their sort order is a bad idea.  Better than sticking with my suggestion as a fixed "one and only" option.  I still think it makes sense as a default option, but others may feel very differently.

But when this comes to fruition some default order will need to be selected.

--

Brian - Windows 10, 64-Bit, Version 21H1, Build 19043  

Nothing in all the world is more dangerous than sincere ignorance and conscientious stupidity.

         ~Martin Luther King, Jr.

 
Re: Introducing NVDA-addons.org, the largest international add-ons store with official and unofficial add-ons from all NVDA communities

Iván Novegil
 

I think it would be useful, in general, to add an sorting system where the user could select the field which sort addons by. E.g: combo box, order by: name, summary, last updated. I think it shouldn't be very difficult to implement it. I have to redesign some parts of the home page, so noted down this as well.


Regards.

Iván Novegil Cancelas
Equipo de xestión web e desenvolvemento



Asociación Comunidad Hispanohablante de NVDA
- Tel.: (+34) 910 05 33 25 ext. 2000
- ivan.novegil@...
- www.NVDA.es
- @nvda_es

Usuario do NVDA en galego

***Esta mensaxe e/ou os seus adxuntos están dirixidos ao seu destinatario e poden conter información privilexiada ou confidencial. A utilización, copia ou divulgación dos mesmos por parte de alguén diferente do destinatario mencionado non están permitidas sen autorización. Se recibiu esta mensaxe por erro pregámoslle o comunique por esta mesma vía e a destrúa.***

O 07/08/2021 á(s) 1:12, Brian Vogel escribiu:

Iván,

First and foremost, thank you for all the time and effort to bring this to fruition.  It's a welcome addition.

I am about to make a suggestion, if I may, and that is to organize the add-ons list by add-on name.  As it looks now, the arrangement may be much like the old community add-ons page, which shifted based upon when the last update to a given add-on was made.  I have always hated this, and find it to be a very confusing arrangement (and some of that is because I can see, and having things change spots "at random" as updates occur doesn't allow one to get used to where anything "should be" on a given webpage).  I find it far easier to have a list where, like most things that have names, alphabetical order by name is used.  Although I know this may not be done, you won't get what you don't ask for.
--

Brian - Windows 10, 64-Bit, Version 21H1, Build 19043  

Nothing in all the world is more dangerous than sincere ignorance and conscientious stupidity.

         ~Martin Luther King, Jr.

 
Re: Introducing NVDA-addons.org, the largest international add-ons store with official and unofficial add-ons from all NVDA communities

Brian Vogel
 

Iván,

First and foremost, thank you for all the time and effort to bring this to fruition.  It's a welcome addition.

I am about to make a suggestion, if I may, and that is to organize the add-ons list by add-on name.  As it looks now, the arrangement may be much like the old community add-ons page, which shifted based upon when the last update to a given add-on was made.  I have always hated this, and find it to be a very confusing arrangement (and some of that is because I can see, and having things change spots "at random" as updates occur doesn't allow one to get used to where anything "should be" on a given webpage).  I find it far easier to have a list where, like most things that have names, alphabetical order by name is used.  Although I know this may not be done, you won't get what you don't ask for.
--

Brian - Windows 10, 64-Bit, Version 21H1, Build 19043  

Nothing in all the world is more dangerous than sincere ignorance and conscientious stupidity.

         ~Martin Luther King, Jr.

 
Introducing NVDA-addons.org, the largest international add-ons store with official and unofficial add-ons from all NVDA communities

Iván Novegil
 

Dear NVDA users across the world,


I'm pleased to announce to you the availability of the final version of NVDA-addons.org, the first website created to serve as an international directory for both official and unofficial NVDA add-ons.

Indeed, this project aims to gather the download links of all possible add-ons, within logical standards of usability. You won't have to search in Google anymore to, at the end, find an outdated version uploaded to Dropbox, or ask through your preferred mailing list until someone is able to rescue and send you as an attachment that add-on that is distributed from mailbox to mailbox for years. In NVDA_addons.org, your favourite add-on may be hosted by Dropbox, but we, both users and administrators, will make our best to guarantee you its most updated release. Moreover, you'll be able to know before downloading any add-on its exact compatibility range and development status.

The platform has been self-developed by us and has the following features:

  • Table of add-ons on the home page: As simple as typing NVDA-addons.org in your preferred web browser. Last updated add-ons are shown at the top and official add-ons, those published at add-ons.nvda-project.org, are flagged as "verified".
  • Filters: You can filter add-on table by add-on's name, summary, release channel, minimum NVDA version and last tested NVDA version.
  • Paginator: Browse the add-on table 50 by 50.
  • Dedicated page for each add-on: See its author, website, description and available downloads, with supported NVDA version range for each of them.
  • Direct download both from home page and add-on page.
  • Supported by advancedAddonFiles: The directory already contains all the add-ons added to the Spanish-speaking NVDA Community website, NVDA.es. This is because NVDA-addons.org is only an interface for advancedAddonFiles, the application that manages add-on additions and updates.
  • Automatic translator in all pages, powered by Google.
  • top 10 downloaded add-ons: All pages include a widget showing the 10 most downloaded add-on releases along with their last tested NVDA version.
  • Newsletter: With our newsletter, you'll get a digest of updated and added add-ons each week, and also special notices and information about review requests. Subscribe by sending a blank message to news+subscribe@.... This is also displayed as a widget in all pages.
  • Donate: We'd prefer not to ask for donations, but the Spanish-speaking NVDA Community Association, stablished in Spain as a legal nonprofit, survives thanks to them. Maintaining NVDA-addons.org is only one of our initiatives. You can donate through PayPal, credit/debit card and GitHub Sponsors, using the widget at the bottom of each page.
  • Direct contact: We are human and willing to help. Send us your thoughts, questions and suggestions to admin@....

How can you collaborate?

  1. Adding new add-ons: You can submit a review request for one add-on that is not registered. It doesn't matter if you are its author or not. Once we've verified it doesn't contain spam, it'll be published to receive public comments regarding add-on usability and security. In absence of them, or after they've been resolved, the add-on will be added to the database. If you've specified your email, you'll be given direct access to update that add-on. You can also submit a review request for already registered add-ons to discuss usability or security issues.
  2. Letting us know of add-on updates: If you find an outdated add-on in our database, don't hesitate to reach us at admin@... with all the information you have about the new version. We'll happy to publish that new version, provieded that it's from the same author or we have reasonable evidences of abandonment from that maintainer and a new one continues the development.

What happens if you have an interested friend who doesn't know English? That's, in fact, the idea behind the translate widget. Just choose your native language and enjoy. We know that no translation can match a human translation, but this is our easiest and simplest solution to have NVDA-addons.org internationalized. If you want to export our catalog to your local NVDA website, don't forget that it's available in JSON format at https://nvda-addons.org/files/get.php?addonslist

On the other hand, don't worry to write us a message in another language. We'll make our best to reply you.

What is coming next? We're now announcing the first version of the website but can't wait to think about the future. Héctor Benítez has developed an add-ons store prototype for NVDA-addons.org, which will be enhanced until it gets to a stable version that we all can use to review the catalog and download the add-ons we want from NVDA directly. You can download the prototype, in spanish, from: https://nvda-addons.org/files/get.php?file=tienda


I really hope this new tool is useful for you and every NVDA user you know. If you have any questions, don't hesitate to ask.

Best regards.

--

Iván Novegil Cancelas
Equipo de xestión web e desenvolvemento



Asociación Comunidad Hispanohablante de NVDA
- Tel.: (+34) 910 05 33 25 ext. 2000
- ivan.novegil@...
- www.NVDA.es
- @nvda_es

Usuario do NVDA en galego

***Esta mensaxe e/ou os seus adxuntos están dirixidos ao seu destinatario e poden conter información privilexiada ou confidencial. A utilización, copia ou divulgación dos mesmos por parte de alguén diferente do destinatario mencionado non están permitidas sen autorización. Se recibiu esta mensaxe por erro pregámoslle o comunique por esta mesma vía e a destrúa.***
Re: Accessible Word Processor Biblos--Why did I never know about this?

Jackie
 

Except when you want a live view, Pawel. & there are those, though I'm
not 1 of them, who are extremely uncomfortable w/the CLI.

On 8/6/21, Pawel Urbanski <pawel@e-urbanski.com> wrote:
Markdown + Pandoc = fantastic setup.

On 06/08/2021, Jujube <ellaxyu@gmail.com> wrote:
Hello, I also just found out about Biblos yesterday in hopes of
clearing up some issues with some brf files I have on a braille
notetaker. For a while I was looking for software that would let me
work with brf files and although I got a duxbury demo, for my really
specific situation it just didn't work so I just kept searching. I
tried Braille Blaster but it wasn't right for what I was trying to do,
so I googled "free braille translator", came across the page at Index
embossers, and found Biblos. Biblos saved the day. I used Biblos to
convert my wrongly encoded brf files from my notetaker to the correct
encoding which can be read by most devices and it worked and I'm so
happy! I did it by opening the braille file in windows notepad,
copying the contents, pasting it into Biblos and exporting the brf.
Anyway, this is a really special use case for Biblos but man it really
saved my life and I'm so happy. Biblos may come into handy for other
things but for now i'll use it to fix my lovely brf files lol.

On 8/6/21, Jackie <abletec@gmail.com> wrote:
Ok, so I guess this is not strictly NVDA-related per se, though the
program does have an addon specifically for use w/NVDA. Here's some of
the impressive features the software offers.

It's called Biblos, & it allows the opening and saving of files of an
incredible number of formats, to include .docx, .doc, .rtf, Markdown
(woohoo!) & more. & no, woohoo is *not* a file format lol. It's just
that those who know me even a little know what a fangirl of Markdown I
am.

It allows printing of files to Braille.

It allows drawing of vector graphics, especially for tactile graphics,
but also for any purpose where vector graphics can be used. Thus, we
can draw pictures using text representations.

It allows typical formatting all word processors have in common, ie,
bold, italic, headings, endnotes, footnotes, etc.

I hate to say it, but I think 1 of the reasons this little gem has
been overlooked is because the gentleman who programmed it seems to be
fluent only in Italian, & translation of the software into other
languages is kind of automated. So yeah--some of the help guide syntax
is a bit awkward, but folks, really--I consider myself pretty well
acquainted w/what's out there, & I haven't encountered this 1 before.
Yall can get it at:
http://www.digrande.it/en/Biblos.aspx

Once downloaded, go to the scripts folder and install the NVDA addon
appropriate to your version of NVDA, & you're golden.

For those looking for a free and accessible alternative to Word, you
might wish to check this 1 out! As for me, adios, Jarte, as well as to
my now unsupported version of Word.

--
Subscribe to a WordPress for Newbies Mailing List by sending a message
to:
wp4newbs-request@freelists.org with 'subscribe' in the Subject field OR
by
visiting the list page at http://www.freelists.org/list/wp4newbs
& check out my sites at www.brightstarsweb.com &
www.mysitesbeenhacked.com













--
Subscribe to a WordPress for Newbies Mailing List by sending a message to:
wp4newbs-request@freelists.org with 'subscribe' in the Subject field OR by
visiting the list page at http://www.freelists.org/list/wp4newbs
& check out my sites at www.brightstarsweb.com & www.mysitesbeenhacked.com
Re: Accessible Word Processor Biblos--Why did I never know about this?

Pawel Urbanski
 

Markdown + Pandoc = fantastic setup.

On 06/08/2021, Jujube <ellaxyu@gmail.com> wrote:
Hello, I also just found out about Biblos yesterday in hopes of
clearing up some issues with some brf files I have on a braille
notetaker. For a while I was looking for software that would let me
work with brf files and although I got a duxbury demo, for my really
specific situation it just didn't work so I just kept searching. I
tried Braille Blaster but it wasn't right for what I was trying to do,
so I googled "free braille translator", came across the page at Index
embossers, and found Biblos. Biblos saved the day. I used Biblos to
convert my wrongly encoded brf files from my notetaker to the correct
encoding which can be read by most devices and it worked and I'm so
happy! I did it by opening the braille file in windows notepad,
copying the contents, pasting it into Biblos and exporting the brf.
Anyway, this is a really special use case for Biblos but man it really
saved my life and I'm so happy. Biblos may come into handy for other
things but for now i'll use it to fix my lovely brf files lol.

On 8/6/21, Jackie <abletec@gmail.com> wrote:
Ok, so I guess this is not strictly NVDA-related per se, though the
program does have an addon specifically for use w/NVDA. Here's some of
the impressive features the software offers.

It's called Biblos, & it allows the opening and saving of files of an
incredible number of formats, to include .docx, .doc, .rtf, Markdown
(woohoo!) & more. & no, woohoo is *not* a file format lol. It's just
that those who know me even a little know what a fangirl of Markdown I
am.

It allows printing of files to Braille.

It allows drawing of vector graphics, especially for tactile graphics,
but also for any purpose where vector graphics can be used. Thus, we
can draw pictures using text representations.

It allows typical formatting all word processors have in common, ie,
bold, italic, headings, endnotes, footnotes, etc.

I hate to say it, but I think 1 of the reasons this little gem has
been overlooked is because the gentleman who programmed it seems to be
fluent only in Italian, & translation of the software into other
languages is kind of automated. So yeah--some of the help guide syntax
is a bit awkward, but folks, really--I consider myself pretty well
acquainted w/what's out there, & I haven't encountered this 1 before.
Yall can get it at:
http://www.digrande.it/en/Biblos.aspx

Once downloaded, go to the scripts folder and install the NVDA addon
appropriate to your version of NVDA, & you're golden.

For those looking for a free and accessible alternative to Word, you
might wish to check this 1 out! As for me, adios, Jarte, as well as to
my now unsupported version of Word.

--
Subscribe to a WordPress for Newbies Mailing List by sending a message
to:
wp4newbs-request@freelists.org with 'subscribe' in the Subject field OR
by
visiting the list page at http://www.freelists.org/list/wp4newbs
& check out my sites at www.brightstarsweb.com &
www.mysitesbeenhacked.com
Re: Accessible Word Processor Biblos--Why did I never know about this?

Jujube
 

Hello, I also just found out about Biblos yesterday in hopes of
clearing up some issues with some brf files I have on a braille
notetaker. For a while I was looking for software that would let me
work with brf files and although I got a duxbury demo, for my really
specific situation it just didn't work so I just kept searching. I
tried Braille Blaster but it wasn't right for what I was trying to do,
so I googled "free braille translator", came across the page at Index
embossers, and found Biblos. Biblos saved the day. I used Biblos to
convert my wrongly encoded brf files from my notetaker to the correct
encoding which can be read by most devices and it worked and I'm so
happy! I did it by opening the braille file in windows notepad,
copying the contents, pasting it into Biblos and exporting the brf.
Anyway, this is a really special use case for Biblos but man it really
saved my life and I'm so happy. Biblos may come into handy for other
things but for now i'll use it to fix my lovely brf files lol.

On 8/6/21, Jackie <abletec@gmail.com> wrote:
Ok, so I guess this is not strictly NVDA-related per se, though the
program does have an addon specifically for use w/NVDA. Here's some of
the impressive features the software offers.

It's called Biblos, & it allows the opening and saving of files of an
incredible number of formats, to include .docx, .doc, .rtf, Markdown
(woohoo!) & more. & no, woohoo is *not* a file format lol. It's just
that those who know me even a little know what a fangirl of Markdown I
am.

It allows printing of files to Braille.

It allows drawing of vector graphics, especially for tactile graphics,
but also for any purpose where vector graphics can be used. Thus, we
can draw pictures using text representations.

It allows typical formatting all word processors have in common, ie,
bold, italic, headings, endnotes, footnotes, etc.

I hate to say it, but I think 1 of the reasons this little gem has
been overlooked is because the gentleman who programmed it seems to be
fluent only in Italian, & translation of the software into other
languages is kind of automated. So yeah--some of the help guide syntax
is a bit awkward, but folks, really--I consider myself pretty well
acquainted w/what's out there, & I haven't encountered this 1 before.
Yall can get it at:
http://www.digrande.it/en/Biblos.aspx

Once downloaded, go to the scripts folder and install the NVDA addon
appropriate to your version of NVDA, & you're golden.

For those looking for a free and accessible alternative to Word, you
might wish to check this 1 out! As for me, adios, Jarte, as well as to
my now unsupported version of Word.

--
Subscribe to a WordPress for Newbies Mailing List by sending a message to:
wp4newbs-request@freelists.org with 'subscribe' in the Subject field OR by
visiting the list page at http://www.freelists.org/list/wp4newbs
& check out my sites at www.brightstarsweb.com & www.mysitesbeenhacked.com
Accessible Word Processor Biblos--Why did I never know about this?

Jackie
 

Ok, so I guess this is not strictly NVDA-related per se, though the
program does have an addon specifically for use w/NVDA. Here's some of
the impressive features the software offers.

It's called Biblos, & it allows the opening and saving of files of an
incredible number of formats, to include .docx, .doc, .rtf, Markdown
(woohoo!) & more. & no, woohoo is *not* a file format lol. It's just
that those who know me even a little know what a fangirl of Markdown I
am.

It allows printing of files to Braille.

It allows drawing of vector graphics, especially for tactile graphics,
but also for any purpose where vector graphics can be used. Thus, we
can draw pictures using text representations.

It allows typical formatting all word processors have in common, ie,
bold, italic, headings, endnotes, footnotes, etc.

I hate to say it, but I think 1 of the reasons this little gem has
been overlooked is because the gentleman who programmed it seems to be
fluent only in Italian, & translation of the software into other
languages is kind of automated. So yeah--some of the help guide syntax
is a bit awkward, but folks, really--I consider myself pretty well
acquainted w/what's out there, & I haven't encountered this 1 before.
Yall can get it at:
http://www.digrande.it/en/Biblos.aspx

Once downloaded, go to the scripts folder and install the NVDA addon
appropriate to your version of NVDA, & you're golden.

For those looking for a free and accessible alternative to Word, you
might wish to check this 1 out! As for me, adios, Jarte, as well as to
my now unsupported version of Word.

--
Subscribe to a WordPress for Newbies Mailing List by sending a message to:
wp4newbs-request@freelists.org with 'subscribe' in the Subject field OR by
visiting the list page at http://www.freelists.org/list/wp4newbs
& check out my sites at www.brightstarsweb.com & www.mysitesbeenhacked.com
Re: Adobe DC Pro crashes with NVDA

Shaun Everiss
 


In addition to this unless you need pro features to avoid all the syncronisers running I wouldn't even sign in.


On 7/08/2021 3:02 am, falkogiepmans@... wrote:
Hi all,

I have someone whose Adobe Reader DC Pro crashes when reading PDF files. He got the following setup:

Windows versie: 1909 (Enterprise)

Adobe Acrobat Pro DC versie: 2021.005.20048

NVDA 2021.1

When opening a PDF with Adobe Acrobat Pro NVDA starts loading. When that finishes we step trhough the document with down arrow but Adobe gives a crash report shortly after that. I will paste that below if there is a wizard that can read that.
The reason why I post it here is because this only occurs with NVDA. I get a "frozen in stack" error as in the nvda.log snippet below.

I have tried COM Registration fix tool and updated from 2020.4 to 2021.1 but those did not change the problem. Is there someone that might know what this is and how to potentionally fix this?

Kind regards,
Falko


NVDA LOG SNIPPET


ERROR - watchdog._watcher (13:43:17.729) - watchdog (7856):
Core frozen in stack!
INFO - watchdog._watcher (13:43:17.805) - watchdog (7856):
Listing stacks for Python threads:
Python stack for thread 12924 (Dummy-2):
  File "comtypes\_comobject.pyc", line 148, in call_without_this
  File "_UIAHandler.pyc", line 534, in IUIAutomationFocusChangedEventHandler_HandleFocusChangedEvent
  File "_UIAHandler.pyc", line 859, in isNativeUIAElement
  File "_UIAHandler.pyc", line 838, in getNearestWindowHandle
  File "comtypesMonkeyPatches.pyc", line 27, in __call__

Python stack for thread 2728 (watchdog.CancellableCallThread.execute(<_FuncPtr object at 0x0C12AC60>)):
  File "threading.pyc", line 890, in _bootstrap
  File "threading.pyc", line 926, in _bootstrap_inner
  File "watchdog.pyc", line 332, in run
  File "threading.pyc", line 552, in wait
  File "threading.pyc", line 296, in wait

Python stack for thread 12388 (visionEnhancementProviders.NVDAHighlighter.NVDAHighlighter):
  File "threading.pyc", line 890, in _bootstrap
  File "threading.pyc", line 926, in _bootstrap_inner
  File "threading.pyc", line 870, in run
  File "visionEnhancementProviders\NVDAHighlighter.pyc", line 454, in _run
  File "winUser.pyc", line 425, in getMessage

Python stack for thread 7856 (watchdog):
  File "threading.pyc", line 890, in _bootstrap
  File "threading.pyc", line 926, in _bootstrap_inner
  File "threading.pyc", line 870, in run
  File "watchdog.pyc", line 141, in _watcher
  File "watchdog.pyc", line 62, in getFormattedStacksForAllThreads

Python stack for thread 19672 (touchHandler.TouchHandler):
  File "threading.pyc", line 890, in _bootstrap
  File "threading.pyc", line 926, in _bootstrap_inner
  File "touchHandler.pyc", line 241, in run

Python stack for thread 2192 (winInputHook):
  File "threading.pyc", line 890, in _bootstrap
  File "threading.pyc", line 926, in _bootstrap_inner
  File "threading.pyc", line 870, in run
  File "winInputHook.pyc", line 79, in hookThreadFunc

Python stack for thread 3776 (_UIAHandler.UIAHandler.MTAThread):
  File "threading.pyc", line 890, in _bootstrap
  File "threading.pyc", line 926, in _bootstrap_inner
  File "threading.pyc", line 870, in run
  File "_UIAHandler.pyc", line 340, in MTAThreadFunc
  File "queue.pyc", line 170, in get
  File "threading.pyc", line 296, in wait

Python stack for thread 4296 (braille._BgThread):
  File "threading.pyc", line 890, in _bootstrap
  File "threading.pyc", line 926, in _bootstrap_inner
  File "threading.pyc", line 870, in run
  File "braille.pyc", line 2199, in func

Python stack for thread 19644 (Thread-1):
  File "threading.pyc", line 890, in _bootstrap
  File "threading.pyc", line 926, in _bootstrap_inner
  File "C:\Users\C40813\AppData\Roaming\nvda\addons\vocalizer-driver\synthDrivers\vocalizer\_vocalizer.py", line 32, in run
    func, args, kwargs = bgQueue.get()
  File "queue.pyc", line 170, in get
  File "threading.pyc", line 296, in wait

Python stack for thread 15012 (MainThread):
  File "nvda.pyw", line 359, in <module>
  File "core.pyc", line 750, in main
  File "wx\core.pyc", line 2237, in MainLoop
  File "gui\__init__.pyc", line 838, in Notify
  File "core.pyc", line 712, in run
  File "queueHandler.pyc", line 88, in pumpAll
  File "queueHandler.pyc", line 55, in flushQueue
  File "scriptHandler.pyc", line 162, in _queueScriptCallback
  File "keyboardHandler.pyc", line 516, in executeScript
  File "inputCore.pyc", line 202, in executeScript
  File "scriptHandler.pyc", line 208, in executeScript
  File "cursorManager.pyc", line 243, in script_moveByCharacter_forward
  File "cursorManager.pyc", line 165, in _caretMovementScriptHelper
  File "browseMode.pyc", line 1347, in _set_selection
  File "review.pyc", line 177, in handleCaretMove
  File "api.pyc", line 220, in setReviewPosition
  File "vision\visionHandler.pyc", line 314, in handleReviewMove
  File "extensionPoints\__init__.pyc", line 47, in notify
  File "extensionPoints\util.pyc", line 170, in callWithSupportedKwargs
  File "visionEnhancementProviders\NVDAHighlighter.pyc", line 484, in handleReviewMove
  File "visionEnhancementProviders\NVDAHighlighter.pyc", line 471, in updateContextRect
  File "vision\util.pyc", line 72, in getContextRect
  File "api.pyc", line 234, in getNavigatorObject
  File "baseObject.pyc", line 26, in __get__
  File "textInfos\offsets.pyc", line 483, in _get_NVDAObjectAtStart
  File "virtualBuffers\__init__.pyc", line 180, in _getNVDAObjectFromOffset
  File "virtualBuffers\__init__.pyc", line 155, in _getFieldIdentifierFromOffset

ERROR - watchdog._watcher (13:43:32.757) - watchdog (7856):
Core frozen in stack!
INFO - watchdog._watcher (13:43:32.767) - watchdog (7856):
Listing stacks for Python threads:
Python stack for thread 2728 (watchdog.CancellableCallThread.execute(<_FuncPtr object at 0x0C12AC60>)):
  File "threading.pyc", line 890, in _bootstrap
  File "threading.pyc", line 926, in _bootstrap_inner
  File "watchdog.pyc", line 332, in run
  File "threading.pyc", line 552, in wait
  File "threading.pyc", line 296, in wait

Python stack for thread 12388 (visionEnhancementProviders.NVDAHighlighter.NVDAHighlighter):
  File "threading.pyc", line 890, in _bootstrap
  File "threading.pyc", line 926, in _bootstrap_inner
  File "threading.pyc", line 870, in run
  File "visionEnhancementProviders\NVDAHighlighter.pyc", line 452, in _run
  File "winUser.pyc", line 425, in getMessage

Python stack for thread 7856 (watchdog):
  File "threading.pyc", line 890, in _bootstrap
  File "threading.pyc", line 926, in _bootstrap_inner
  File "threading.pyc", line 870, in run
  File "watchdog.pyc", line 141, in _watcher
  File "watchdog.pyc", line 62, in getFormattedStacksForAllThreads

Python stack for thread 19672 (touchHandler.TouchHandler):
  File "threading.pyc", line 890, in _bootstrap
  File "threading.pyc", line 926, in _bootstrap_inner
  File "touchHandler.pyc", line 241, in run

Python stack for thread 2192 (winInputHook):
  File "threading.pyc", line 890, in _bootstrap
  File "threading.pyc", line 926, in _bootstrap_inner
  File "threading.pyc", line 870, in run
  File "winInputHook.pyc", line 79, in hookThreadFunc

Python stack for thread 3776 (_UIAHandler.UIAHandler.MTAThread):
  File "threading.pyc", line 890, in _bootstrap
  File "threading.pyc", line 926, in _bootstrap_inner
  File "threading.pyc", line 870, in run
  File "_UIAHandler.pyc", line 340, in MTAThreadFunc
  File "queue.pyc", line 170, in get
  File "threading.pyc", line 296, in wait

Python stack for thread 4296 (braille._BgThread):
  File "threading.pyc", line 890, in _bootstrap
  File "threading.pyc", line 926, in _bootstrap_inner
  File "threading.pyc", line 870, in run
  File "braille.pyc", line 2199, in func

Python stack for thread 19644 (Thread-1):
  File "threading.pyc", line 890, in _bootstrap
  File "threading.pyc", line 926, in _bootstrap_inner
  File "C:\Users\C40813\AppData\Roaming\nvda\addons\vocalizer-driver\synthDrivers\vocalizer\_vocalizer.py", line 32, in run
    func, args, kwargs = bgQueue.get()
  File "queue.pyc", line 170, in get
  File "threading.pyc", line 296, in wait

Python stack for thread 15012 (MainThread):
  File "nvda.pyw", line 359, in <module>
  File "core.pyc", line 750, in main
  File "wx\core.pyc", line 2237, in MainLoop
  File "gui\__init__.pyc", line 838, in Notify
  File "core.pyc", line 712, in run
  File "queueHandler.pyc", line 88, in pumpAll
  File "queueHandler.pyc", line 55, in flushQueue
  File "scriptHandler.pyc", line 162, in _queueScriptCallback
  File "keyboardHandler.pyc", line 516, in executeScript
  File "inputCore.pyc", line 202, in executeScript
  File "scriptHandler.pyc", line 208, in executeScript
  File "cursorManager.pyc", line 243, in script_moveByCharacter_forward
  File "cursorManager.pyc", line 165, in _caretMovementScriptHelper
  File "browseMode.pyc", line 1347, in _set_selection
  File "review.pyc", line 177, in handleCaretMove
  File "api.pyc", line 220, in setReviewPosition
  File "vision\visionHandler.pyc", line 314, in handleReviewMove
  File "extensionPoints\__init__.pyc", line 47, in notify
  File "extensionPoints\util.pyc", line 170, in callWithSupportedKwargs
  File "visionEnhancementProviders\NVDAHighlighter.pyc", line 484, in handleReviewMove
  File "visionEnhancementProviders\NVDAHighlighter.pyc", line 471, in updateContextRect
  File "vision\util.pyc", line 72, in getContextRect
  File "api.pyc", line 234, in getNavigatorObject
  File "baseObject.pyc", line 26, in __get__
  File "textInfos\offsets.pyc", line 483, in _get_NVDAObjectAtStart
  File "virtualBuffers\__init__.pyc", line 180, in _getNVDAObjectFromOffset
  File "virtualBuffers\__init__.pyc", line 155, in _getFieldIdentifierFromOffset




END OF NVDA LOG SNIPPET







START OF ADOBE REPORT CRASH

<?xml version="1.0"?>

<!DOCTYPE AdobeCrashReport SYSTEM "AdobeCrashReporter.dtd">

<crashreport serviceVersion="4.7.0" clientVersion="4.7.0" applicationName="Adobe Acrobat" applicationVersion="21.005.20048" build="0" source="Windows-Client-WER" crashType="n/a">

<time year="2021" month="7" day="9" hour="13" minute="38" second="3" timeoffset="60" timezone="West-Europa (zomertijd)"/>

<user guid="f69f073f-3072-436b-b63d-1d674976076d"/>

<system platform="Windows 10 Enterprise" osversion="10.0" osbuild="18363" applicationlanguage="nl-nl" userlanguage="nl-NL" oslanguage="en-GB" ram="16194" machine="Intel(R) Core(TM) i5-8365U CPU @ 1.60GHz" model="Intel64 Family 6 Model 142 Stepping 12" cpuCount="8" cpuType="586" cpuFreq="1896 MHz" processorArchitecture="0"/>

<gpu>

<gpuinfo availability="Running/Full Power" adapterCompatibility="Intel Corporation" adapterRAM="1024 MB" caption="Intel(R) UHD Graphics 620" description="Intel(R) UHD Graphics 620" driverDate="20190925000000.000000-000" driverVersion="26.20.100.7262" videoModeDescription="2560 x 1440 x 4294967296 kleuren" pnpDeviceID="PCI&#92;VEN_8086&#38;DEV_3EA0&#38;SUBSYS_08E11028&#38;REV_02&#92;3&#38;11583659&#38;0&#38;10" installedDisplayDrivers="igd10iumd64.dll,igd12umd64.dll,igdumdim64.dll"/>

</gpu>

<crash exception="EXCEPTION_ACCESS_VIOLATION" exceptionCode="0xc0000005" instruction="0x0EE4146B">

<backtrace crashedThread="0">

<thread index="0">

<stackStatement index="0" address="0x000000000EE4146B" symbolname="ObsoleteProc"/>

<stackStatement index="1" address="0x000000000EE2C5F2" symbolname="ObsoleteProc"/>

<stackStatement index="2" address="0x00000000796405AA" symbolname="AIDE::PixelPartInfo::operator="/>

<stackStatement index="3" address="0x0000000078A7997F" symbolname="PlugInMain"/>

<stackStatement index="4" address="0x000000007752FC24" symbolname="NdrByteCountPointerUnmarshall"/>

<stackStatement index="5" address="0x00000000774F4D02" symbolname="NdrStubCall2"/>

<stackStatement index="6" address="0x0000000076349A6D" symbolname="CStdStubBuffer_Invoke"/>

<stackStatement index="7" address="0x0000000075FA5DB2" symbolname="OACleanup"/>

<stackStatement index="8" address="0x0000000076349878" symbolname="WindowsIsStringEmpty"/>

<stackStatement index="9" address="0x0000000076349413" symbolname="WindowsIsStringEmpty"/>

<stackStatement index="10" address="0x00000000762FB5F1" symbolname="CStdStubBuffer_AddRef"/>

<stackStatement index="11" address="0x000000007631B9C1" symbolname="RoGetApartmentIdentifier"/>

<stackStatement index="12" address="0x00000000762FC3E7" symbolname="CStdStubBuffer_AddRef"/>

<stackStatement index="13" address="0x00000000762FDAEB" symbolname="CStdStubBuffer_AddRef"/>

<stackStatement index="14" address="0x00000000762F93AA" symbolname="CoTaskMemFree"/>

<stackStatement index="15" address="0x0000000075A847AB" symbolname="AddClipboardFormatListener"/>

<stackStatement index="16" address="0x0000000075A652AC" symbolname="CallWindowProcW"/>

<stackStatement index="17" address="0x0000000075A643FE" symbolname="DispatchMessageW"/>

<stackStatement index="18" address="0x0000000075A641E0" symbolname="DispatchMessageW"/>

<stackStatement index="19" address="0x0000000078BB017E" symbolname="DllCanUnloadNow"/>

<stackStatement index="20" address="0x0000000078BAFEBE" symbolname="DllCanUnloadNow"/>

<stackStatement index="21" address="0x0000000078BAFD54" symbolname="DllCanUnloadNow"/>

<stackStatement index="22" address="0x0000000078B326C1" symbolname="AcroWinMainSandbox"/>

<stackStatement index="23" address="0x0000000078B32169" symbolname="AcroWinMainSandbox"/>

<stackStatement index="24" address="0x000000000015B6C1" symbolname="unknown"/>

<stackStatement index="25" address="0x000000000030BCCA" symbolname="IsSandboxedProcess"/>

<stackStatement index="26" address="0x0000000074EB6359" symbolname="BaseThreadInitThunk"/>

<stackStatement index="27" address="0x00000000776287A4" symbolname="RtlGetAppContainerNamedObjectPath"/>

<stackStatement index="28" address="0x0000000077628774" symbolname="RtlGetAppContainerNamedObjectPath"/>

</thread>

</backtrace>

<registerSet>

<register name="EAX" value="0x0000000000001446"/>

<register name="EBX" value="0x00000000050FEA00"/>

<register name="ECX" value="0x000000000000FFFF"/>

<register name="EDX" value="0x0000000010000000"/>

<register name="ESI" value="0x0000000000000001"/>

<register name="EDI" value="0x0000000000000000"/>

<register name="ESP" value="0x00000000050FE800"/>

<register name="EBP" value="0x00000000050FE808"/>

<register name="EIP" value="0x000000000EE4146B"/>

<register name="EFL" value="0x0000000000010217"/>

</registerSet>

 

<binaryImageSet>

<binaryImage start="0x0000000000150000" end="0x00000000004F6000" path="adobe\Acrobat.exe"/>

<binaryImage start="0x00000000775C0000" end="0x000000007775A000" path="ntdll.dll"/>

<binaryImage start="0x0000000074EA0000" end="0x0000000074F80000" path="kernel32.dll"/>

<binaryImage start="0x0000000075D00000" end="0x0000000075EFF000" path="KERNELBASE.dll"/>

<binaryImage start="0x0000000075A40000" end="0x0000000075BD8000" path="user32.dll"/>

<binaryImage start="0x0000000076DA0000" end="0x0000000076DB7000" path="win32u.dll"/>

<binaryImage start="0x0000000075580000" end="0x00000000755A1000" path="gdi32.dll"/>

<binaryImage start="0x0000000077160000" end="0x00000000772BD000" path="gdi32full.dll"/>

<binaryImage start="0x00000000760D0000" end="0x000000007614C000" path="msvcp_win.dll"/>

<binaryImage start="0x0000000075BE0000" end="0x0000000075D00000" path="ucrtbase.dll"/>

<binaryImage start="0x0000000076C40000" end="0x0000000076CBA000" path="advapi32.dll"/>

<binaryImage start="0x0000000076530000" end="0x00000000765EF000" path="msvcrt.dll"/>

<binaryImage start="0x0000000075500000" end="0x0000000075576000" path="sechost.dll"/>

<binaryImage start="0x00000000774F0000" end="0x00000000775AB000" path="rpcrt4.dll"/>

<binaryImage start="0x0000000074D80000" end="0x0000000074DA0000" path="sspicli.dll"/>

<binaryImage start="0x0000000074D70000" end="0x0000000074D7A000" path="CRYPTBASE.dll"/>

<binaryImage start="0x0000000075F00000" end="0x0000000075F62000" path="bcryptPrimitives.dll"/>

<binaryImage start="0x0000000076150000" end="0x0000000076194000" path="shlwapi.dll"/>

<binaryImage start="0x0000000076250000" end="0x00000000764C7000" path="combase.dll"/>

<binaryImage start="0x0000000073E20000" end="0x0000000073E28000" path="version.dll"/>

<binaryImage start="0x00000000772F0000" end="0x0000000077315000" path="imm32.dll"/>

<binaryImage start="0x000000006BEE0000" end="0x000000006C0EF000" path="comctl32.dll"/>

<binaryImage start="0x0000000070980000" end="0x00000000709A9000" path="ntmarta.dll"/>

<binaryImage start="0x000000006BBC0000" end="0x000000006BC18000" path="prntm.dll"/>

<binaryImage start="0x0000000074DA0000" end="0x0000000074E97000" path="ole32.dll"/>

<binaryImage start="0x00000000707A0000" end="0x000000007080B000" path="winspool.drv"/>

<binaryImage start="0x0000000075F80000" end="0x0000000076012000" path="oleaut32.dll"/>

<binaryImage start="0x000000006C4E0000" end="0x000000006C4EA000" path="secur32.dll"/>

<binaryImage start="0x0000000076DC0000" end="0x0000000076DCF000" path="kernel.appcore.dll"/>

<binaryImage start="0x0000000076F30000" end="0x0000000076F49000" path="bcrypt.dll"/>

<binaryImage start="0x000000006BC20000" end="0x000000006BD0E000" path="msvcr120.dll"/>

<binaryImage start="0x000000006BD10000" end="0x000000006BD81000" path="msvcp120.dll"/>

<binaryImage start="0x00000000746B0000" end="0x00000000746E2000" path="IPHLPAPI.DLL"/>

<binaryImage start="0x0000000070530000" end="0x00000000705F5000" path="propsys.dll"/>

<binaryImage start="0x0000000076CC0000" end="0x0000000076D44000" path="SHCore.dll"/>

<binaryImage start="0x0000000078AF0000" end="0x000000007AEB6000" path="adobe\Acrobat.dll"/>

<binaryImage start="0x0000000074F80000" end="0x00000000754FB000" path="shell32.dll"/>

<binaryImage start="0x0000000076DE0000" end="0x0000000076E1B000" path="cfgmgr32.dll"/>

<binaryImage start="0x000000007BEE0000" end="0x000000007C1C4000" path="adobe\CoolType.dll"/>

<binaryImage start="0x000000007B830000" end="0x000000007BE5F000" path="adobe\AGM.dll"/>

<binaryImage start="0x000000007C2A0000" end="0x000000007C433000" path="adobe\libeay32.dll"/>

<binaryImage start="0x00000000765F0000" end="0x0000000076BB0000" path="windows.storage.dll"/>

<binaryImage start="0x00000000755D0000" end="0x00000000755E7000" path="profapi.dll"/>

<binaryImage start="0x0000000077430000" end="0x000000007748E000" path="ws2_32.dll"/>

<binaryImage start="0x00000000719F0000" end="0x0000000071AB3000" path="winhttp.dll"/>

<binaryImage start="0x0000000076020000" end="0x0000000076063000" path="powrprof.dll"/>

<binaryImage start="0x000000006C0F0000" end="0x000000006C15F000" path="msvcp140.dll"/>

<binaryImage start="0x000000006C160000" end="0x000000006C174000" path="VCRUNTIME140.dll"/>

<binaryImage start="0x0000000077150000" end="0x000000007715D000" path="umpdc.dll"/>

<binaryImage start="0x00000000772D0000" end="0x00000000772E3000" path="cryptsp.dll"/>

<binaryImage start="0x0000000051A00000" end="0x0000000051A08000" path="SensApi.dll"/>

<binaryImage start="0x0000000006EC0000" end="0x0000000006EE1000" path="adobe\BIB.dll"/>

<binaryImage start="0x000000000C330000" end="0x000000000C424000" path="adobe\ACE.dll"/>

<binaryImage start="0x0000000070440000" end="0x00000000704BA000" path="uxtheme.dll"/>

<binaryImage start="0x0000000076E20000" end="0x0000000076F23000" path="msctf.dll"/>

<binaryImage start="0x0000000070410000" end="0x0000000070435000" path="dwmapi.dll"/>

<binaryImage start="0x0000000076BC0000" end="0x0000000076C40000" path="clbcatq.dll"/>

<binaryImage start="0x00000000672B0000" end="0x00000000672E1000" path="dataexchange.dll"/>

<binaryImage start="0x0000000067140000" end="0x00000000672AA000" path="dcomp.dll"/>

<binaryImage start="0x0000000066F60000" end="0x000000006713E000" path="d3d11.dll"/>

<binaryImage start="0x0000000066E90000" end="0x0000000066F51000" path="dxgi.dll"/>

<binaryImage start="0x0000000067670000" end="0x0000000067689000" path="DXCore.dll"/>

<binaryImage start="0x0000000066CA0000" end="0x0000000066E83000" path="twinapi.appcore.dll"/>

<binaryImage start="0x0000000066C80000" end="0x0000000066C9F000" path="rmclient.dll"/>

<binaryImage start="0x0000000070A80000" end="0x0000000070A98000" path="mpr.dll"/>

<binaryImage start="0x0000000077770000" end="0x0000000077779000" path="drprov.dll"/>

<binaryImage start="0x000000006F950000" end="0x000000006F994000" path="winsta.dll"/>

<binaryImage start="0x000000000B410000" end="0x000000000B422000" path="ntlanman.dll"/>

<binaryImage start="0x000000000B450000" end="0x000000000B469000" path="davclnt.dll"/>

<binaryImage start="0x0000000077760000" end="0x000000007776A000" path="davhlpr.dll"/>

<binaryImage start="0x0000000073EA0000" end="0x0000000073EAB000" path="netutils.dll"/>

<binaryImage start="0x0000000070350000" end="0x000000007035E000" path="cscapi.dll"/>

<binaryImage start="0x0000000071CF0000" end="0x0000000071E9A000" path="urlmon.dll"/>

<binaryImage start="0x0000000071AC0000" end="0x0000000071CEA000" path="iertutil.dll"/>

<binaryImage start="0x000000007C440000" end="0x000000007C47C000" path="adobe\AXE8SharedExpat.dll"/>

<binaryImage start="0x000000000B490000" end="0x000000000B738000" path="msftedit.dll"/>

<binaryImage start="0x0000000078900000" end="0x0000000078A4F000" path="Windows.Globalization.dll"/>

<binaryImage start="0x0000000052540000" end="0x0000000052585000" path="Bcp47Langs.dll"/>

<binaryImage start="0x0000000052260000" end="0x0000000052283000" path="BCP47mrm.dll"/>

<binaryImage start="0x00000000788E0000" end="0x00000000788FC000" path="globinputhost.dll"/>

<binaryImage start="0x000000000B760000" end="0x000000000B7D1000" path="adobe\AdobeXMP.dll"/>

<binaryImage start="0x000000007BEB0000" end="0x000000007BEDB000" path="adobe\BIBUtils.dll"/>

<binaryImage start="0x0000000050060000" end="0x0000000050130000" path="nvdaHelperRemote.dll"/>

<binaryImage start="0x0000000073F40000" end="0x00000000740CF000" path="dbghelp.dll"/>

<binaryImage start="0x0000000060750000" end="0x00000000607A3000" path="oleacc.dll"/>

<binaryImage start="0x0000000073F10000" end="0x0000000073F34000" path="dbgcore.dll"/>

<binaryImage start="0x0000000050020000" end="0x000000005003E000" path="minHook.dll"/>

<binaryImage start="0x0000000060090000" end="0x00000000600A7000" path="usp10.dll"/>

<binaryImage start="0x0000000051A10000" end="0x0000000051A2C000" path="IAccessible2Proxy.dll"/>

<binaryImage start="0x0000000050040000" end="0x0000000050059000" path="ISimpleDOM.dll"/>

<binaryImage start="0x0000000078A50000" end="0x0000000078AE8000" path="adobe\Accessibility.api"/>

<binaryImage start="0x000000006B580000" end="0x000000006B608000" path="sxs.dll"/>

<binaryImage start="0x000000005FD00000" end="0x000000005FD82000" path="TextInputFramework.dll"/>

<binaryImage start="0x000000005FA10000" end="0x000000005FC6E000" path="CoreUIComponents.dll"/>

<binaryImage start="0x000000005FC70000" end="0x000000005FCF9000" path="CoreMessaging.dll"/>

<binaryImage start="0x0000000060650000" end="0x0000000060727000" path="WinTypes.dll"/>

<binaryImage start="0x000000000CDB0000" end="0x000000000DC11000" path="adobe\AcroForm.api"/>

<binaryImage start="0x0000000077320000" end="0x0000000077421000" path="crypt32.dll"/>

<binaryImage start="0x0000000075F70000" end="0x0000000075F7E000" path="msasn1.dll"/>

<binaryImage start="0x000000007B220000" end="0x000000007B2CC000" path="adobe\AXSLE.dll"/>

<binaryImage start="0x000000007B2D0000" end="0x000000007B449000" path="adobe\DigSig.api"/>

<binaryImage start="0x000000000E540000" end="0x000000000ECB2000" path="adobe\PPKLite.api"/>

<binaryImage start="0x0000000061180000" end="0x0000000061188000" path="wsock32.dll"/>

<binaryImage start="0x000000000EE20000" end="0x000000000EE9B000" path="adobe\PDDom.api"/>

<binaryImage start="0x0000000060DC0000" end="0x0000000060FB3000" path="UIAutomationCore.DLL"/>

<binaryImage start="0x0000000077780000" end="0x00000000777BB000" path="OneCoreCommonProxyStub.dll"/>

<binaryImage start="0x0000000011A10000" end="0x0000000011B93000" path="explorerframe.dll"/>

<binaryImage start="0x00000000608B0000" end="0x000000006094F000" path="apphelp.dll"/>

<binaryImage start="0x0000000060730000" end="0x0000000060743000" path="NetworkExplorer.dll"/>

<binaryImage start="0x0000000008400000" end="0x000000000845E000" path="adobe\reflow.api"/>

<binaryImage start="0x0000000009050000" end="0x00000000090CA000" path="adobe\sqlite.dll"/>

<binaryImage start="0x0000000009160000" end="0x00000000091C0000" path="adobe\CRClient.dll"/>

<binaryImage start="0x0000000076D50000" end="0x0000000076D96000" path="wintrust.dll"/>

<binaryImage start="0x0000000070360000" end="0x0000000070368000" path="dpapi.dll"/>

<binaryImage start="0x0000000014DA0000" end="0x0000000014DF1000" path="adobe\PaperCapture.api"/>

<binaryImage start="0x0000000073E90000" end="0x0000000073EA0000" path="wkscli.dll"/>

<binaryImage start="0x0000000060FE0000" end="0x0000000061074000" path="mscms.dll"/>

<binaryImage start="0x0000000060FC0000" end="0x0000000060FD1000" path="ColorAdapterClient.dll"/>

<binaryImage start="0x0000000074230000" end="0x000000007424E000" path="userenv.dll"/>

<binaryImage start="0x0000000073EB0000" end="0x0000000073F02000" path="mswsock.dll"/>

<binaryImage start="0x000000006F940000" end="0x000000006F948000" path="winnsi.dll"/>

<binaryImage start="0x0000000076DD0000" end="0x0000000076DD7000" path="nsi.dll"/>

<binaryImage start="0x00000000719D0000" end="0x00000000719E3000" path="dhcpcsvc6.DLL"/>

<binaryImage start="0x0000000073D10000" end="0x0000000073D25000" path="dhcpcsvc.dll"/>

<binaryImage start="0x000000006C630000" end="0x000000006C6A7000" path="webio.dll"/>

<binaryImage start="0x000000006C4F0000" end="0x000000006C521000" path="PeerDist.dll"/>

<binaryImage start="0x0000000060190000" end="0x0000000060206000" path="schannel.dll"/>

<binaryImage start="0x0000000060810000" end="0x0000000060821000" path="mskeyprotect.dll"/>

<binaryImage start="0x000000006BEB0000" end="0x000000006BED1000" path="ncrypt.dll"/>

<binaryImage start="0x000000006BE80000" end="0x000000006BEA8000" path="ntasn1.dll"/>

<binaryImage start="0x00000000607B0000" end="0x00000000607CF000" path="ncryptsslp.dll"/>

<binaryImage start="0x0000000073E40000" end="0x0000000073E6F000" path="rsaenh.dll"/>

<binaryImage start="0x000000006E0B0000" end="0x000000006E0CE000" path="gpapi.dll"/>

<binaryImage start="0x000000001BAC0000" end="0x000000001BC3B000" path="adobe\LogSession.dll"/>

<binaryImage start="0x0000000074250000" end="0x00000000746AC000" path="wininet.dll"/>

<binaryImage start="0x000000001BC40000" end="0x000000001C172000" path="adobe\MakeAccessible.api"/>

</binaryImageSet>

<dumpType>

Mini

</dumpType>

<hbLogSessionDllStatus>

ERROR_HB_UNABLE_TO_LOAD_DLL

</hbLogSessionDllStatus>

</crash>



END OF ADOBE REPORT CRASH




 
 
Re: Adobe DC Pro crashes with NVDA

Shaun Everiss
 

Well he needs to remove adobe reader and then install the 32 bit version.

Have no idea why the fudge adobe reader dc 64 bit crashes when reading pdfs I mean it shouldn't.

I loaded it a few months ago because well for the hell of it.

And well it crashed with every pdf I loaded into it its unknown why it does it but its not like it matters.

Happily thunderbird 64 bit works here but after issues with firefox 64 bit I am back on 32 bit as well.

If you can get to the adobe reader ftp site under the adobe/ reader/ win/ adobe dc you can get the latest classic adobe reader dc in your language of choise though it doesn't matter what version you get.

If you get that you can upgrade from that to the continuous release and thats what I am doing from now on.

Of course that was always 32 bit and since adobe don't seem to be updating their font and spelling components and all of those work on 32 bit only I see no reason to bother with adobe reader 64.



On 7/08/2021 3:02 am, falkogiepmans@... wrote:
Hi all,

I have someone whose Adobe Reader DC Pro crashes when reading PDF files. He got the following setup:

Windows versie: 1909 (Enterprise)

Adobe Acrobat Pro DC versie: 2021.005.20048

NVDA 2021.1

When opening a PDF with Adobe Acrobat Pro NVDA starts loading. When that finishes we step trhough the document with down arrow but Adobe gives a crash report shortly after that. I will paste that below if there is a wizard that can read that.
The reason why I post it here is because this only occurs with NVDA. I get a "frozen in stack" error as in the nvda.log snippet below.

I have tried COM Registration fix tool and updated from 2020.4 to 2021.1 but those did not change the problem. Is there someone that might know what this is and how to potentionally fix this?

Kind regards,
Falko


NVDA LOG SNIPPET


ERROR - watchdog._watcher (13:43:17.729) - watchdog (7856):
Core frozen in stack!
INFO - watchdog._watcher (13:43:17.805) - watchdog (7856):
Listing stacks for Python threads:
Python stack for thread 12924 (Dummy-2):
  File "comtypes\_comobject.pyc", line 148, in call_without_this
  File "_UIAHandler.pyc", line 534, in IUIAutomationFocusChangedEventHandler_HandleFocusChangedEvent
  File "_UIAHandler.pyc", line 859, in isNativeUIAElement
  File "_UIAHandler.pyc", line 838, in getNearestWindowHandle
  File "comtypesMonkeyPatches.pyc", line 27, in __call__

Python stack for thread 2728 (watchdog.CancellableCallThread.execute(<_FuncPtr object at 0x0C12AC60>)):
  File "threading.pyc", line 890, in _bootstrap
  File "threading.pyc", line 926, in _bootstrap_inner
  File "watchdog.pyc", line 332, in run
  File "threading.pyc", line 552, in wait
  File "threading.pyc", line 296, in wait

Python stack for thread 12388 (visionEnhancementProviders.NVDAHighlighter.NVDAHighlighter):
  File "threading.pyc", line 890, in _bootstrap
  File "threading.pyc", line 926, in _bootstrap_inner
  File "threading.pyc", line 870, in run
  File "visionEnhancementProviders\NVDAHighlighter.pyc", line 454, in _run
  File "winUser.pyc", line 425, in getMessage

Python stack for thread 7856 (watchdog):
  File "threading.pyc", line 890, in _bootstrap
  File "threading.pyc", line 926, in _bootstrap_inner
  File "threading.pyc", line 870, in run
  File "watchdog.pyc", line 141, in _watcher
  File "watchdog.pyc", line 62, in getFormattedStacksForAllThreads

Python stack for thread 19672 (touchHandler.TouchHandler):
  File "threading.pyc", line 890, in _bootstrap
  File "threading.pyc", line 926, in _bootstrap_inner
  File "touchHandler.pyc", line 241, in run

Python stack for thread 2192 (winInputHook):
  File "threading.pyc", line 890, in _bootstrap
  File "threading.pyc", line 926, in _bootstrap_inner
  File "threading.pyc", line 870, in run
  File "winInputHook.pyc", line 79, in hookThreadFunc

Python stack for thread 3776 (_UIAHandler.UIAHandler.MTAThread):
  File "threading.pyc", line 890, in _bootstrap
  File "threading.pyc", line 926, in _bootstrap_inner
  File "threading.pyc", line 870, in run
  File "_UIAHandler.pyc", line 340, in MTAThreadFunc
  File "queue.pyc", line 170, in get
  File "threading.pyc", line 296, in wait

Python stack for thread 4296 (braille._BgThread):
  File "threading.pyc", line 890, in _bootstrap
  File "threading.pyc", line 926, in _bootstrap_inner
  File "threading.pyc", line 870, in run
  File "braille.pyc", line 2199, in func

Python stack for thread 19644 (Thread-1):
  File "threading.pyc", line 890, in _bootstrap
  File "threading.pyc", line 926, in _bootstrap_inner
  File "C:\Users\C40813\AppData\Roaming\nvda\addons\vocalizer-driver\synthDrivers\vocalizer\_vocalizer.py", line 32, in run
    func, args, kwargs = bgQueue.get()
  File "queue.pyc", line 170, in get
  File "threading.pyc", line 296, in wait

Python stack for thread 15012 (MainThread):
  File "nvda.pyw", line 359, in <module>
  File "core.pyc", line 750, in main
  File "wx\core.pyc", line 2237, in MainLoop
  File "gui\__init__.pyc", line 838, in Notify
  File "core.pyc", line 712, in run
  File "queueHandler.pyc", line 88, in pumpAll
  File "queueHandler.pyc", line 55, in flushQueue
  File "scriptHandler.pyc", line 162, in _queueScriptCallback
  File "keyboardHandler.pyc", line 516, in executeScript
  File "inputCore.pyc", line 202, in executeScript
  File "scriptHandler.pyc", line 208, in executeScript
  File "cursorManager.pyc", line 243, in script_moveByCharacter_forward
  File "cursorManager.pyc", line 165, in _caretMovementScriptHelper
  File "browseMode.pyc", line 1347, in _set_selection
  File "review.pyc", line 177, in handleCaretMove
  File "api.pyc", line 220, in setReviewPosition
  File "vision\visionHandler.pyc", line 314, in handleReviewMove
  File "extensionPoints\__init__.pyc", line 47, in notify
  File "extensionPoints\util.pyc", line 170, in callWithSupportedKwargs
  File "visionEnhancementProviders\NVDAHighlighter.pyc", line 484, in handleReviewMove
  File "visionEnhancementProviders\NVDAHighlighter.pyc", line 471, in updateContextRect
  File "vision\util.pyc", line 72, in getContextRect
  File "api.pyc", line 234, in getNavigatorObject
  File "baseObject.pyc", line 26, in __get__
  File "textInfos\offsets.pyc", line 483, in _get_NVDAObjectAtStart
  File "virtualBuffers\__init__.pyc", line 180, in _getNVDAObjectFromOffset
  File "virtualBuffers\__init__.pyc", line 155, in _getFieldIdentifierFromOffset

ERROR - watchdog._watcher (13:43:32.757) - watchdog (7856):
Core frozen in stack!
INFO - watchdog._watcher (13:43:32.767) - watchdog (7856):
Listing stacks for Python threads:
Python stack for thread 2728 (watchdog.CancellableCallThread.execute(<_FuncPtr object at 0x0C12AC60>)):
  File "threading.pyc", line 890, in _bootstrap
  File "threading.pyc", line 926, in _bootstrap_inner
  File "watchdog.pyc", line 332, in run
  File "threading.pyc", line 552, in wait
  File "threading.pyc", line 296, in wait

Python stack for thread 12388 (visionEnhancementProviders.NVDAHighlighter.NVDAHighlighter):
  File "threading.pyc", line 890, in _bootstrap
  File "threading.pyc", line 926, in _bootstrap_inner
  File "threading.pyc", line 870, in run
  File "visionEnhancementProviders\NVDAHighlighter.pyc", line 452, in _run
  File "winUser.pyc", line 425, in getMessage

Python stack for thread 7856 (watchdog):
  File "threading.pyc", line 890, in _bootstrap
  File "threading.pyc", line 926, in _bootstrap_inner
  File "threading.pyc", line 870, in run
  File "watchdog.pyc", line 141, in _watcher
  File "watchdog.pyc", line 62, in getFormattedStacksForAllThreads

Python stack for thread 19672 (touchHandler.TouchHandler):
  File "threading.pyc", line 890, in _bootstrap
  File "threading.pyc", line 926, in _bootstrap_inner
  File "touchHandler.pyc", line 241, in run

Python stack for thread 2192 (winInputHook):
  File "threading.pyc", line 890, in _bootstrap
  File "threading.pyc", line 926, in _bootstrap_inner
  File "threading.pyc", line 870, in run
  File "winInputHook.pyc", line 79, in hookThreadFunc

Python stack for thread 3776 (_UIAHandler.UIAHandler.MTAThread):
  File "threading.pyc", line 890, in _bootstrap
  File "threading.pyc", line 926, in _bootstrap_inner
  File "threading.pyc", line 870, in run
  File "_UIAHandler.pyc", line 340, in MTAThreadFunc
  File "queue.pyc", line 170, in get
  File "threading.pyc", line 296, in wait

Python stack for thread 4296 (braille._BgThread):
  File "threading.pyc", line 890, in _bootstrap
  File "threading.pyc", line 926, in _bootstrap_inner
  File "threading.pyc", line 870, in run
  File "braille.pyc", line 2199, in func

Python stack for thread 19644 (Thread-1):
  File "threading.pyc", line 890, in _bootstrap
  File "threading.pyc", line 926, in _bootstrap_inner
  File "C:\Users\C40813\AppData\Roaming\nvda\addons\vocalizer-driver\synthDrivers\vocalizer\_vocalizer.py", line 32, in run
    func, args, kwargs = bgQueue.get()
  File "queue.pyc", line 170, in get
  File "threading.pyc", line 296, in wait

Python stack for thread 15012 (MainThread):
  File "nvda.pyw", line 359, in <module>
  File "core.pyc", line 750, in main
  File "wx\core.pyc", line 2237, in MainLoop
  File "gui\__init__.pyc", line 838, in Notify
  File "core.pyc", line 712, in run
  File "queueHandler.pyc", line 88, in pumpAll
  File "queueHandler.pyc", line 55, in flushQueue
  File "scriptHandler.pyc", line 162, in _queueScriptCallback
  File "keyboardHandler.pyc", line 516, in executeScript
  File "inputCore.pyc", line 202, in executeScript
  File "scriptHandler.pyc", line 208, in executeScript
  File "cursorManager.pyc", line 243, in script_moveByCharacter_forward
  File "cursorManager.pyc", line 165, in _caretMovementScriptHelper
  File "browseMode.pyc", line 1347, in _set_selection
  File "review.pyc", line 177, in handleCaretMove
  File "api.pyc", line 220, in setReviewPosition
  File "vision\visionHandler.pyc", line 314, in handleReviewMove
  File "extensionPoints\__init__.pyc", line 47, in notify
  File "extensionPoints\util.pyc", line 170, in callWithSupportedKwargs
  File "visionEnhancementProviders\NVDAHighlighter.pyc", line 484, in handleReviewMove
  File "visionEnhancementProviders\NVDAHighlighter.pyc", line 471, in updateContextRect
  File "vision\util.pyc", line 72, in getContextRect
  File "api.pyc", line 234, in getNavigatorObject
  File "baseObject.pyc", line 26, in __get__
  File "textInfos\offsets.pyc", line 483, in _get_NVDAObjectAtStart
  File "virtualBuffers\__init__.pyc", line 180, in _getNVDAObjectFromOffset
  File "virtualBuffers\__init__.pyc", line 155, in _getFieldIdentifierFromOffset




END OF NVDA LOG SNIPPET







START OF ADOBE REPORT CRASH

<?xml version="1.0"?>

<!DOCTYPE AdobeCrashReport SYSTEM "AdobeCrashReporter.dtd">

<crashreport serviceVersion="4.7.0" clientVersion="4.7.0" applicationName="Adobe Acrobat" applicationVersion="21.005.20048" build="0" source="Windows-Client-WER" crashType="n/a">

<time year="2021" month="7" day="9" hour="13" minute="38" second="3" timeoffset="60" timezone="West-Europa (zomertijd)"/>

<user guid="f69f073f-3072-436b-b63d-1d674976076d"/>

<system platform="Windows 10 Enterprise" osversion="10.0" osbuild="18363" applicationlanguage="nl-nl" userlanguage="nl-NL" oslanguage="en-GB" ram="16194" machine="Intel(R) Core(TM) i5-8365U CPU @ 1.60GHz" model="Intel64 Family 6 Model 142 Stepping 12" cpuCount="8" cpuType="586" cpuFreq="1896 MHz" processorArchitecture="0"/>

<gpu>

<gpuinfo availability="Running/Full Power" adapterCompatibility="Intel Corporation" adapterRAM="1024 MB" caption="Intel(R) UHD Graphics 620" description="Intel(R) UHD Graphics 620" driverDate="20190925000000.000000-000" driverVersion="26.20.100.7262" videoModeDescription="2560 x 1440 x 4294967296 kleuren" pnpDeviceID="PCI&#92;VEN_8086&#38;DEV_3EA0&#38;SUBSYS_08E11028&#38;REV_02&#92;3&#38;11583659&#38;0&#38;10" installedDisplayDrivers="igd10iumd64.dll,igd12umd64.dll,igdumdim64.dll"/>

</gpu>

<crash exception="EXCEPTION_ACCESS_VIOLATION" exceptionCode="0xc0000005" instruction="0x0EE4146B">

<backtrace crashedThread="0">

<thread index="0">

<stackStatement index="0" address="0x000000000EE4146B" symbolname="ObsoleteProc"/>

<stackStatement index="1" address="0x000000000EE2C5F2" symbolname="ObsoleteProc"/>

<stackStatement index="2" address="0x00000000796405AA" symbolname="AIDE::PixelPartInfo::operator="/>

<stackStatement index="3" address="0x0000000078A7997F" symbolname="PlugInMain"/>

<stackStatement index="4" address="0x000000007752FC24" symbolname="NdrByteCountPointerUnmarshall"/>

<stackStatement index="5" address="0x00000000774F4D02" symbolname="NdrStubCall2"/>

<stackStatement index="6" address="0x0000000076349A6D" symbolname="CStdStubBuffer_Invoke"/>

<stackStatement index="7" address="0x0000000075FA5DB2" symbolname="OACleanup"/>

<stackStatement index="8" address="0x0000000076349878" symbolname="WindowsIsStringEmpty"/>

<stackStatement index="9" address="0x0000000076349413" symbolname="WindowsIsStringEmpty"/>

<stackStatement index="10" address="0x00000000762FB5F1" symbolname="CStdStubBuffer_AddRef"/>

<stackStatement index="11" address="0x000000007631B9C1" symbolname="RoGetApartmentIdentifier"/>

<stackStatement index="12" address="0x00000000762FC3E7" symbolname="CStdStubBuffer_AddRef"/>

<stackStatement index="13" address="0x00000000762FDAEB" symbolname="CStdStubBuffer_AddRef"/>

<stackStatement index="14" address="0x00000000762F93AA" symbolname="CoTaskMemFree"/>

<stackStatement index="15" address="0x0000000075A847AB" symbolname="AddClipboardFormatListener"/>

<stackStatement index="16" address="0x0000000075A652AC" symbolname="CallWindowProcW"/>

<stackStatement index="17" address="0x0000000075A643FE" symbolname="DispatchMessageW"/>

<stackStatement index="18" address="0x0000000075A641E0" symbolname="DispatchMessageW"/>

<stackStatement index="19" address="0x0000000078BB017E" symbolname="DllCanUnloadNow"/>

<stackStatement index="20" address="0x0000000078BAFEBE" symbolname="DllCanUnloadNow"/>

<stackStatement index="21" address="0x0000000078BAFD54" symbolname="DllCanUnloadNow"/>

<stackStatement index="22" address="0x0000000078B326C1" symbolname="AcroWinMainSandbox"/>

<stackStatement index="23" address="0x0000000078B32169" symbolname="AcroWinMainSandbox"/>

<stackStatement index="24" address="0x000000000015B6C1" symbolname="unknown"/>

<stackStatement index="25" address="0x000000000030BCCA" symbolname="IsSandboxedProcess"/>

<stackStatement index="26" address="0x0000000074EB6359" symbolname="BaseThreadInitThunk"/>

<stackStatement index="27" address="0x00000000776287A4" symbolname="RtlGetAppContainerNamedObjectPath"/>

<stackStatement index="28" address="0x0000000077628774" symbolname="RtlGetAppContainerNamedObjectPath"/>

</thread>

</backtrace>

<registerSet>

<register name="EAX" value="0x0000000000001446"/>

<register name="EBX" value="0x00000000050FEA00"/>

<register name="ECX" value="0x000000000000FFFF"/>

<register name="EDX" value="0x0000000010000000"/>

<register name="ESI" value="0x0000000000000001"/>

<register name="EDI" value="0x0000000000000000"/>

<register name="ESP" value="0x00000000050FE800"/>

<register name="EBP" value="0x00000000050FE808"/>

<register name="EIP" value="0x000000000EE4146B"/>

<register name="EFL" value="0x0000000000010217"/>

</registerSet>

 

<binaryImageSet>

<binaryImage start="0x0000000000150000" end="0x00000000004F6000" path="adobe\Acrobat.exe"/>

<binaryImage start="0x00000000775C0000" end="0x000000007775A000" path="ntdll.dll"/>

<binaryImage start="0x0000000074EA0000" end="0x0000000074F80000" path="kernel32.dll"/>

<binaryImage start="0x0000000075D00000" end="0x0000000075EFF000" path="KERNELBASE.dll"/>

<binaryImage start="0x0000000075A40000" end="0x0000000075BD8000" path="user32.dll"/>

<binaryImage start="0x0000000076DA0000" end="0x0000000076DB7000" path="win32u.dll"/>

<binaryImage start="0x0000000075580000" end="0x00000000755A1000" path="gdi32.dll"/>

<binaryImage start="0x0000000077160000" end="0x00000000772BD000" path="gdi32full.dll"/>

<binaryImage start="0x00000000760D0000" end="0x000000007614C000" path="msvcp_win.dll"/>

<binaryImage start="0x0000000075BE0000" end="0x0000000075D00000" path="ucrtbase.dll"/>

<binaryImage start="0x0000000076C40000" end="0x0000000076CBA000" path="advapi32.dll"/>

<binaryImage start="0x0000000076530000" end="0x00000000765EF000" path="msvcrt.dll"/>

<binaryImage start="0x0000000075500000" end="0x0000000075576000" path="sechost.dll"/>

<binaryImage start="0x00000000774F0000" end="0x00000000775AB000" path="rpcrt4.dll"/>

<binaryImage start="0x0000000074D80000" end="0x0000000074DA0000" path="sspicli.dll"/>

<binaryImage start="0x0000000074D70000" end="0x0000000074D7A000" path="CRYPTBASE.dll"/>

<binaryImage start="0x0000000075F00000" end="0x0000000075F62000" path="bcryptPrimitives.dll"/>

<binaryImage start="0x0000000076150000" end="0x0000000076194000" path="shlwapi.dll"/>

<binaryImage start="0x0000000076250000" end="0x00000000764C7000" path="combase.dll"/>

<binaryImage start="0x0000000073E20000" end="0x0000000073E28000" path="version.dll"/>

<binaryImage start="0x00000000772F0000" end="0x0000000077315000" path="imm32.dll"/>

<binaryImage start="0x000000006BEE0000" end="0x000000006C0EF000" path="comctl32.dll"/>

<binaryImage start="0x0000000070980000" end="0x00000000709A9000" path="ntmarta.dll"/>

<binaryImage start="0x000000006BBC0000" end="0x000000006BC18000" path="prntm.dll"/>

<binaryImage start="0x0000000074DA0000" end="0x0000000074E97000" path="ole32.dll"/>

<binaryImage start="0x00000000707A0000" end="0x000000007080B000" path="winspool.drv"/>

<binaryImage start="0x0000000075F80000" end="0x0000000076012000" path="oleaut32.dll"/>

<binaryImage start="0x000000006C4E0000" end="0x000000006C4EA000" path="secur32.dll"/>

<binaryImage start="0x0000000076DC0000" end="0x0000000076DCF000" path="kernel.appcore.dll"/>

<binaryImage start="0x0000000076F30000" end="0x0000000076F49000" path="bcrypt.dll"/>

<binaryImage start="0x000000006BC20000" end="0x000000006BD0E000" path="msvcr120.dll"/>

<binaryImage start="0x000000006BD10000" end="0x000000006BD81000" path="msvcp120.dll"/>

<binaryImage start="0x00000000746B0000" end="0x00000000746E2000" path="IPHLPAPI.DLL"/>

<binaryImage start="0x0000000070530000" end="0x00000000705F5000" path="propsys.dll"/>

<binaryImage start="0x0000000076CC0000" end="0x0000000076D44000" path="SHCore.dll"/>

<binaryImage start="0x0000000078AF0000" end="0x000000007AEB6000" path="adobe\Acrobat.dll"/>

<binaryImage start="0x0000000074F80000" end="0x00000000754FB000" path="shell32.dll"/>

<binaryImage start="0x0000000076DE0000" end="0x0000000076E1B000" path="cfgmgr32.dll"/>

<binaryImage start="0x000000007BEE0000" end="0x000000007C1C4000" path="adobe\CoolType.dll"/>

<binaryImage start="0x000000007B830000" end="0x000000007BE5F000" path="adobe\AGM.dll"/>

<binaryImage start="0x000000007C2A0000" end="0x000000007C433000" path="adobe\libeay32.dll"/>

<binaryImage start="0x00000000765F0000" end="0x0000000076BB0000" path="windows.storage.dll"/>

<binaryImage start="0x00000000755D0000" end="0x00000000755E7000" path="profapi.dll"/>

<binaryImage start="0x0000000077430000" end="0x000000007748E000" path="ws2_32.dll"/>

<binaryImage start="0x00000000719F0000" end="0x0000000071AB3000" path="winhttp.dll"/>

<binaryImage start="0x0000000076020000" end="0x0000000076063000" path="powrprof.dll"/>

<binaryImage start="0x000000006C0F0000" end="0x000000006C15F000" path="msvcp140.dll"/>

<binaryImage start="0x000000006C160000" end="0x000000006C174000" path="VCRUNTIME140.dll"/>

<binaryImage start="0x0000000077150000" end="0x000000007715D000" path="umpdc.dll"/>

<binaryImage start="0x00000000772D0000" end="0x00000000772E3000" path="cryptsp.dll"/>

<binaryImage start="0x0000000051A00000" end="0x0000000051A08000" path="SensApi.dll"/>

<binaryImage start="0x0000000006EC0000" end="0x0000000006EE1000" path="adobe\BIB.dll"/>

<binaryImage start="0x000000000C330000" end="0x000000000C424000" path="adobe\ACE.dll"/>

<binaryImage start="0x0000000070440000" end="0x00000000704BA000" path="uxtheme.dll"/>

<binaryImage start="0x0000000076E20000" end="0x0000000076F23000" path="msctf.dll"/>

<binaryImage start="0x0000000070410000" end="0x0000000070435000" path="dwmapi.dll"/>

<binaryImage start="0x0000000076BC0000" end="0x0000000076C40000" path="clbcatq.dll"/>

<binaryImage start="0x00000000672B0000" end="0x00000000672E1000" path="dataexchange.dll"/>

<binaryImage start="0x0000000067140000" end="0x00000000672AA000" path="dcomp.dll"/>

<binaryImage start="0x0000000066F60000" end="0x000000006713E000" path="d3d11.dll"/>

<binaryImage start="0x0000000066E90000" end="0x0000000066F51000" path="dxgi.dll"/>

<binaryImage start="0x0000000067670000" end="0x0000000067689000" path="DXCore.dll"/>

<binaryImage start="0x0000000066CA0000" end="0x0000000066E83000" path="twinapi.appcore.dll"/>

<binaryImage start="0x0000000066C80000" end="0x0000000066C9F000" path="rmclient.dll"/>

<binaryImage start="0x0000000070A80000" end="0x0000000070A98000" path="mpr.dll"/>

<binaryImage start="0x0000000077770000" end="0x0000000077779000" path="drprov.dll"/>

<binaryImage start="0x000000006F950000" end="0x000000006F994000" path="winsta.dll"/>

<binaryImage start="0x000000000B410000" end="0x000000000B422000" path="ntlanman.dll"/>

<binaryImage start="0x000000000B450000" end="0x000000000B469000" path="davclnt.dll"/>

<binaryImage start="0x0000000077760000" end="0x000000007776A000" path="davhlpr.dll"/>

<binaryImage start="0x0000000073EA0000" end="0x0000000073EAB000" path="netutils.dll"/>

<binaryImage start="0x0000000070350000" end="0x000000007035E000" path="cscapi.dll"/>

<binaryImage start="0x0000000071CF0000" end="0x0000000071E9A000" path="urlmon.dll"/>

<binaryImage start="0x0000000071AC0000" end="0x0000000071CEA000" path="iertutil.dll"/>

<binaryImage start="0x000000007C440000" end="0x000000007C47C000" path="adobe\AXE8SharedExpat.dll"/>

<binaryImage start="0x000000000B490000" end="0x000000000B738000" path="msftedit.dll"/>

<binaryImage start="0x0000000078900000" end="0x0000000078A4F000" path="Windows.Globalization.dll"/>

<binaryImage start="0x0000000052540000" end="0x0000000052585000" path="Bcp47Langs.dll"/>

<binaryImage start="0x0000000052260000" end="0x0000000052283000" path="BCP47mrm.dll"/>

<binaryImage start="0x00000000788E0000" end="0x00000000788FC000" path="globinputhost.dll"/>

<binaryImage start="0x000000000B760000" end="0x000000000B7D1000" path="adobe\AdobeXMP.dll"/>

<binaryImage start="0x000000007BEB0000" end="0x000000007BEDB000" path="adobe\BIBUtils.dll"/>

<binaryImage start="0x0000000050060000" end="0x0000000050130000" path="nvdaHelperRemote.dll"/>

<binaryImage start="0x0000000073F40000" end="0x00000000740CF000" path="dbghelp.dll"/>

<binaryImage start="0x0000000060750000" end="0x00000000607A3000" path="oleacc.dll"/>

<binaryImage start="0x0000000073F10000" end="0x0000000073F34000" path="dbgcore.dll"/>

<binaryImage start="0x0000000050020000" end="0x000000005003E000" path="minHook.dll"/>

<binaryImage start="0x0000000060090000" end="0x00000000600A7000" path="usp10.dll"/>

<binaryImage start="0x0000000051A10000" end="0x0000000051A2C000" path="IAccessible2Proxy.dll"/>

<binaryImage start="0x0000000050040000" end="0x0000000050059000" path="ISimpleDOM.dll"/>

<binaryImage start="0x0000000078A50000" end="0x0000000078AE8000" path="adobe\Accessibility.api"/>

<binaryImage start="0x000000006B580000" end="0x000000006B608000" path="sxs.dll"/>

<binaryImage start="0x000000005FD00000" end="0x000000005FD82000" path="TextInputFramework.dll"/>

<binaryImage start="0x000000005FA10000" end="0x000000005FC6E000" path="CoreUIComponents.dll"/>

<binaryImage start="0x000000005FC70000" end="0x000000005FCF9000" path="CoreMessaging.dll"/>

<binaryImage start="0x0000000060650000" end="0x0000000060727000" path="WinTypes.dll"/>

<binaryImage start="0x000000000CDB0000" end="0x000000000DC11000" path="adobe\AcroForm.api"/>

<binaryImage start="0x0000000077320000" end="0x0000000077421000" path="crypt32.dll"/>

<binaryImage start="0x0000000075F70000" end="0x0000000075F7E000" path="msasn1.dll"/>

<binaryImage start="0x000000007B220000" end="0x000000007B2CC000" path="adobe\AXSLE.dll"/>

<binaryImage start="0x000000007B2D0000" end="0x000000007B449000" path="adobe\DigSig.api"/>

<binaryImage start="0x000000000E540000" end="0x000000000ECB2000" path="adobe\PPKLite.api"/>

<binaryImage start="0x0000000061180000" end="0x0000000061188000" path="wsock32.dll"/>

<binaryImage start="0x000000000EE20000" end="0x000000000EE9B000" path="adobe\PDDom.api"/>

<binaryImage start="0x0000000060DC0000" end="0x0000000060FB3000" path="UIAutomationCore.DLL"/>

<binaryImage start="0x0000000077780000" end="0x00000000777BB000" path="OneCoreCommonProxyStub.dll"/>

<binaryImage start="0x0000000011A10000" end="0x0000000011B93000" path="explorerframe.dll"/>

<binaryImage start="0x00000000608B0000" end="0x000000006094F000" path="apphelp.dll"/>

<binaryImage start="0x0000000060730000" end="0x0000000060743000" path="NetworkExplorer.dll"/>

<binaryImage start="0x0000000008400000" end="0x000000000845E000" path="adobe\reflow.api"/>

<binaryImage start="0x0000000009050000" end="0x00000000090CA000" path="adobe\sqlite.dll"/>

<binaryImage start="0x0000000009160000" end="0x00000000091C0000" path="adobe\CRClient.dll"/>

<binaryImage start="0x0000000076D50000" end="0x0000000076D96000" path="wintrust.dll"/>

<binaryImage start="0x0000000070360000" end="0x0000000070368000" path="dpapi.dll"/>

<binaryImage start="0x0000000014DA0000" end="0x0000000014DF1000" path="adobe\PaperCapture.api"/>

<binaryImage start="0x0000000073E90000" end="0x0000000073EA0000" path="wkscli.dll"/>

<binaryImage start="0x0000000060FE0000" end="0x0000000061074000" path="mscms.dll"/>

<binaryImage start="0x0000000060FC0000" end="0x0000000060FD1000" path="ColorAdapterClient.dll"/>

<binaryImage start="0x0000000074230000" end="0x000000007424E000" path="userenv.dll"/>

<binaryImage start="0x0000000073EB0000" end="0x0000000073F02000" path="mswsock.dll"/>

<binaryImage start="0x000000006F940000" end="0x000000006F948000" path="winnsi.dll"/>

<binaryImage start="0x0000000076DD0000" end="0x0000000076DD7000" path="nsi.dll"/>

<binaryImage start="0x00000000719D0000" end="0x00000000719E3000" path="dhcpcsvc6.DLL"/>

<binaryImage start="0x0000000073D10000" end="0x0000000073D25000" path="dhcpcsvc.dll"/>

<binaryImage start="0x000000006C630000" end="0x000000006C6A7000" path="webio.dll"/>

<binaryImage start="0x000000006C4F0000" end="0x000000006C521000" path="PeerDist.dll"/>

<binaryImage start="0x0000000060190000" end="0x0000000060206000" path="schannel.dll"/>

<binaryImage start="0x0000000060810000" end="0x0000000060821000" path="mskeyprotect.dll"/>

<binaryImage start="0x000000006BEB0000" end="0x000000006BED1000" path="ncrypt.dll"/>

<binaryImage start="0x000000006BE80000" end="0x000000006BEA8000" path="ntasn1.dll"/>

<binaryImage start="0x00000000607B0000" end="0x00000000607CF000" path="ncryptsslp.dll"/>

<binaryImage start="0x0000000073E40000" end="0x0000000073E6F000" path="rsaenh.dll"/>

<binaryImage start="0x000000006E0B0000" end="0x000000006E0CE000" path="gpapi.dll"/>

<binaryImage start="0x000000001BAC0000" end="0x000000001BC3B000" path="adobe\LogSession.dll"/>

<binaryImage start="0x0000000074250000" end="0x00000000746AC000" path="wininet.dll"/>

<binaryImage start="0x000000001BC40000" end="0x000000001C172000" path="adobe\MakeAccessible.api"/>

</binaryImageSet>

<dumpType>

Mini

</dumpType>

<hbLogSessionDllStatus>

ERROR_HB_UNABLE_TO_LOAD_DLL

</hbLogSessionDllStatus>

</crash>



END OF ADOBE REPORT CRASH




 
 
Re: Does anyone have any tips for clicking on links that won’t click with NVDA

Gene
 

Did you try object navigation? 
 
Gene

-----Original Message-----
Sent: Friday, August 06, 2021 11:41 AM
Subject: [nvda] Does anyone have any tips for clicking on links that won’t click with NVDA
 
I’m using A website calledCACs Enterprise by CGI it’s a billing and payment platform, one of the problems I’m having is that there is a link which is actually a hover over menu, so hovering over it with the mouse will open up a list of other options but NVDA sees it only as a link.
i’ve tried clicking it but I’ve had no luck, and pressing shift plus NVDA  plus M to move the mouse over it, NVDA will read out the options on the list but there is no way to get at them to click them.
Does anyone have any ideas or tips?
Does anyone have any tips for clicking on links that won’t click with NVDA

Khalid Anwar
 

I’m using A website calledCACs Enterprise by CGI it’s a billing and payment platform, one of the problems I’m having is that there is a link which is actually a hover over menu, so hovering over it with the mouse will open up a list of other options but NVDA sees it only as a link.
i’ve tried clicking it but I’ve had no luck, and pressing shift plus NVDA  plus M to move the mouse over it, NVDA will read out the options on the list but there is no way to get at them to click them.
Does anyone have any ideas or tips?
Re: Resource: Youtube Video From Thee Quinn: How to Use Microsoft Access With NVDA: Part 1

tim
 

You know its interesting just how far and how much its lost with JFW and its access with Microsoft office products have dropped.

When i beta tested office 4.3 with JFW 3 it was totally accessible.

However, that was under henter Joyce and he wanted Office to be the power for those that work.

Now you have to fight for the accessibility he tried to achieve.

Thanks to him I got A's for all my Microsoft classes witch got me in the beta program. Back then office was so easy everything worked..

On 8/6/2021 10:37 AM, Brian Vogel wrote:
While I'll agree that any method to use MS-Access with a screen reader that works is absolutely amazing, this is an instance where I think that "going the GUI route" is a way to make things far, far more difficult than they need be.

I cut my teeth with databases before the age of the GUI interface learning SQL, which is still very widely in use to this day and which is supported (or was, anyway) by MS-Access and a lot of other relational databases.

The amount of work to learn SQL to commit and manipulate databases is not herculean.  The ability to deal with it when you're a screen reader user, since SQL is just plain text code, and pretty directly understandable plain text code for most of the basic database wizardry, it's just so much easier to deal with overall.  And that even applies to report formatting and generation.  

It's worth having a look at SQL as a possible option.  You might be pleasantly surprised at what you find.
--

Brian - Windows 10, 64-Bit, Version 21H1, Build 19043  

Nothing in all the world is more dangerous than sincere ignorance and conscientious stupidity.

         ~Martin Luther King, Jr.

 
8881 - 8900 of 95653