<div dir="auto"><div>Okay, so after manually editing the configuration file, (uncommented two lines, changed COM1 to COM3...) now we're getting a lot of</div><div dir="auto"><br></div><div dir="auto">libusb_open error 40: Function not implemented<br></div><div dir="auto"><br></div><div dir="auto">full log here:</div><div dir="auto"><a href="https://www.dropbox.com/s/b4jgrz5zvuwdg8l/1572082041966_debug.log?dl=0">https://www.dropbox.com/s/b4jgrz5zvuwdg8l/1572082041966_debug.log?dl=0</a><br></div><div dir="auto"><br></div><div dir="auto"><div class="gmail_quote" dir="auto"><div dir="ltr" class="gmail_attr">On Fri, Oct 25, 2019, 3:13 PM Dave Mielke <Dave@mielke.cc> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">[quoted lines by Oriana Neulinger on 2019/10/25 at 14:24 -0400]<br>
<br>
>I had her run the 'debug app' as administrator, and got an log. <br>
<br>
Okay, good. I was assuming that she already was. I'll continue to look into how<br>
to script the elevating of privileges in a way that works well when using a<br>
console.<br>
<br>
>The configuration we did last time was to set the port to COM3 and set the<br>
>manufacturer to Alva, so why is it still scanning all of the USB options?<br>
<br>
Her log says:<br>
<br>
2019-10-25@11:01:16.259 checking braille device: USB:<br>
<br>
The braille device, therefore, is clearly set to USB:. How did you set the<br>
configuration? If you ran brltty's .exe installer and used its configurator<br>
then we'll need someone else's advice since I've never used it and have no easy<br>
way to do so. If you did then, again, maybe not being administrator was getting<br>
in the way.<br>
<br>
Check for the file brltty.conf (which I think should be within brltty's etc\<br>
folder). Look for the braille-device line. If there's more than one then it's<br>
the last one that matters. If the Alva is on COM3 then it should say:<br>
<br>
braille-device serial:COM3<br>
<br>
Also check for the braille-driver line. It should say:<br>
<br>
braille-driver al<br>
<br>
In both cases, if the line is missing or commented out then add/uncomment it.<br>
<br>
>I'll make some suggestions for the documentation on a new email. <br>
<br>
Thanks.<br>
<br>
>For one, the documentation suggests that the folder, or at least the<br>
>executable, was supposed to have been added to %PATH% this whole time haha<br>
<br>
:-) As is the case with a lot of documentation, there's usually too much to<br>
absorb all at once. That's why my personal opinion is that those who rudely<br>
order others to go away and just read the manual are, for whatever reason,<br>
lacking empathy.<br>
<br>
-- <br>
I believe the Bible to be the very Word of God: <a href="http://Mielke.cc/bible/" rel="noreferrer noreferrer" target="_blank">http://Mielke.cc/bible/</a><br>
Dave Mielke | 2213 Fox Crescent | WebHome: <a href="http://Mielke.cc/" rel="noreferrer noreferrer" target="_blank">http://Mielke.cc/</a><br>
EMail: Dave@Mielke.cc | Ottawa, Ontario | Twitter: @Dave_Mielke<br>
Phone: +1 613 726 0014 | Canada K2A 1H7 |<br>
_______________________________________________<br>
This message was sent via the BRLTTY mailing list.<br>
To post a message, send an e-mail to: BRLTTY@brltty.app<br>
For general information, go to: <a href="http://brltty.app/mailman/listinfo/brltty" rel="noreferrer noreferrer" target="_blank">http://brltty.app/mailman/listinfo/brltty</a><br>
</blockquote></div></div></div>