<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style></head><body lang=EN-US link=blue vlink="#954F72" style='word-wrap:break-word'><div class=WordSection1><p class=MsoNormal>Hi Samuel, I first tried brltty-win-6.4-0-libusb-1.0.exe, then brltty-win-6.4-0-libusb-1.0.zip. I can’t find the driver for the NLS Ereader anywhere, which is why I tried BRLTTY in the first place, as it lists the NLS Ereader in it’s list of supported braille displays. I’m beginning to think it wasn’t the right choice at all. </p><p class=MsoNormal>When I try to install brltty-libusb-1.0.inf</p><p class=MsoNormal>I get: The third-party INF does not contain digital signature information.</p><p class=MsoNormal>I tried the following instructions to fix that, but it didn’t work:</p><p class=MsoNormal>1. Launch an elevated CMD prompt (run as Admin)</p><p class=MsoNormal>2. Type in:</p><p class=MsoNormal>bcdedit /set loadoptions DDISABLE_INTEGRITY_CHECKS</p><p class=MsoNormal>and press the ENTER key</p><p class=MsoNormal>3. Type in:</p><p class=MsoNormal>bcdedit /set testsigning on</p><p class=MsoNormal>and press the ENTER key</p><p class=MsoNormal>4. Try the install again</p><p class=MsoNormal>I didn’t even get feedback from command prompt as I used to do. I think I’m just going to have to wait a year or 2 until more people start using the NLS Ereader, maybe NVDA will get around to supporting it natively. It works well with the IPhone, but just isn’t really supported with NVDA without a lot of headache.</p><p class=MsoNormal>Thanks for all your help, but I think this wasn’t a good option. The NLS Ereader is just too new, and I’m not really getting support for it from the users nor from the NVDA community. The driver is impossible to find, and your driver gets flagged by Windows so I’m blocked from installing it, as drivers from small companies and developers tend to do.</p><p class=MsoNormal>The Ereader doesn’t run a serial com port service for Bluetooth, so it’s not possible to designate a com port number for it in Windows.</p><p class=MsoNormal>Shawn Klein</p><p class=MsoNormal>Sent from <a href="https://go.microsoft.com/fwlink/?LinkId=550986">Mail</a> for Windows</p><p class=MsoNormal><o:p> </o:p></p><div style='mso-element:para-border-div;border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal style='border:none;padding:0in'><b>From: </b><a href="mailto:samuel.thibault@ens-lyon.org">Samuel Thibault</a><br><b>Sent: </b>Tuesday, October 5, 2021 4:33 PM<br><b>To: </b><a href="mailto:brltty@brltty.app">Informal discussion between users and developers of BRLTTY.</a><br><b>Subject: </b>Re: [BRLTTY] Windows, Can't run Brlapi-0.8.3.win32.exe even though I've installed Python 3.1 64-bit and 3.8 32-bit</p></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>shawn klein, le mar. 05 oct. 2021 16:22:19 -0500, a ecrit:</p><p class=MsoNormal>> Hi, it wasn’t running, I thought NVDA would just initialize it.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>In the case when Brltty is installed, NVDA could trigger a start of the</p><p class=MsoNormal>BrlAPI service, when using the portable version of Brltty, NVDA can't</p><p class=MsoNormal>divine when Brltty is. The rule could be that Brltty be unpacked just</p><p class=MsoNormal>within the NVDA directory or something like that. It'd be useful that</p><p class=MsoNormal>some people could contribute this kind of support to NVDA.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>> 2021-10-05@16:03:34.583 libusb_open error 40: Function not implemented</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Which windows version of brltty did you use? Depending on your</p><p class=MsoNormal>situation, you'd need the libusb or libusb-1.0 version, and install the</p><p class=MsoNormal>filter or the driver, see the README.txt file.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Samuel</p><p class=MsoNormal>_______________________________________________</p><p class=MsoNormal>This message was sent via the BRLTTY mailing list.</p><p class=MsoNormal>To post a message, send an e-mail to: BRLTTY@brltty.app</p><p class=MsoNormal>For general information, go to: http://brltty.app/mailman/listinfo/brltty</p><p class=MsoNormal><o:p> </o:p></p></div></body></html>