And how did you re-regester the DLL file?

-----Original Message-----
From: Brian's Mail list account via Groups.Io
Sent: Tuesday, January 23, 2018 8:30 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] update on dll issue

So not clear what the difference is between the two, but to me it sounds
like the dll had become unregistered and now its registered again.
I used to get this issue a lot with dlls belonging to the mp3 decoder used
by Goldwave when Winamac was on the system. in the end I had to copy another
copy to the right place then register that with the system and it has never
complained since. My feeling is that its easy to get multiple entries in the
registry or delete ones that have path details needed by a different piece
of soft3ware. Brian

bglists@...
Sent via blueyonder.
Please address personal email to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
----- Original Message -----
From: "The Wolf" <hank.smith966@...>
To: <nvda@nvda.groups.io>
Sent: Monday, January 22, 2018 10:18 PM
Subject: [nvda] update on dll issue

Hello just for the hell of it I installed jaws 18 along with jaws 2018 and now the nvda doesn't give me the error message

not sure if installing jaws 18 fixed the jaws 2018 dll issue with nvda can any one please confirm this am trying to figure out if I need to send a nvda log with the error that it was giving me

something screwy is conflicting I mean I got the issue fixed for now but I need to see if I am the only one having this issue if not then I think a bug needs to be filed.

if I am the only one running in to this issue what can I do to help track this issue?

Hank