Hi All,
I am no computer whiz, and I would appreciate, those of you who are, to
take a look at the www.spreely.com social network to see what can be done
from our end to make the sight more accessible. These are some of the
issues I encountered so far: Links do not open right away;
Editing to comment or post are very difficult as the voice becomes silent
and the cursor tends to get stuck; Difficult to locate received comments
and notifications;
The developers Marc and Terry will also appreciate receiving your experts
feedback. Many thanks
Blessings
Pascal

-----Original Message-----
From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Brian's
Mail list account via Groups.Io Sent: Wednesday, December 12, 2018 1:50 PM
To: nvda@nvda.groups.io
Subject:

And if all else fails often typing it into google can give a clue.
Brian

bglists@blueyonder.co.uk
Sent via blueyonder.
Please address personal E-mail to:-
briang1@blueyonder.co.uk, putting 'Brian Gaff'
in the display name field.
----- Original Message -----
From: "Chris via Groups.Io" <chrismedley=btinternet.com@groups.io>
To: <nvda@nvda.groups.io>
Sent: Wednesday, December 12, 2018 6:41 PM
Subject: Re: [nvda] Weird error on boot.


If you think its coming from that specific program then try setting it not
to start on logon see fi that fixes it

If it fixes the issue then reinstall the program see if that fixes

Otherwise the error is to generic to be certain what is causing it

Good luck
From: John Isige
Sent: 12 December 2018 18:04
To: nvda@nvda.groups.io
Subject: [nvda] Weird error on boot.

Hey all. I'm writing in hopes that somebody knows where this is coming
from. It's possible it's NVDA but I doubt it. I updated Windows to 1809
and everything works fine. But every time I boot up, I get this error.


"Could not load file or assembly 'MOM.Implementation' or one of its
dependencies. The system cannot find the file specified."


Anybody know where this is from, and more importantly, how to fix it? I
suspected TWBlue but I just quit and ran it again, and the error didn't
show up. Oh yeah, I'm running NVDA 2018.4-RC1 on 64-bit Windows.