[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
shawn klein
kb7clx at yahoo.com
Tue Oct 5 17:22:19 EDT 2021
Hi, it wasn’t running, I thought NVDA would just initialize it.
I ran run-brltty.bat, restarted NVDA, and now no error message from NVDA. But now the E-Reader will not connect, connection failed. I have brltty-win-6.4-0-libusb-1.0.zip and NVDA 2021.2.
Here’s the BRLTTY log from my last attempt.
-----------------------------
2021-10-05 at 16:03:34.300 BRLTTY 6.4 rev BRLTTY-6.4M [https://brltty.app/]
2021-10-05 at 16:03:34.329 Log Level: info
2021-10-05 at 16:03:34.329 Messages Locale: en_US
2021-10-05 at 16:03:34.329 Messages Domain: brltty
2021-10-05 at 16:03:34.329 Messages Directory: C:/Users/HP PAVILION AMD/Downloads/brltty-win-6.4-0-libusb-1.0/brltty-win-6.4-0-libusb-1.0/bin/../share/locale
2021-10-05 at 16:03:34.329 Working Directory: C:\Windows\system32
2021-10-05 at 16:03:34.329 Configuration File: C:/Users/HP PAVILION AMD/Downloads/brltty-win-6.4-0-libusb-1.0/brltty-win-6.4-0-libusb-1.0/bin/../etc/brltty.conf
2021-10-05 at 16:03:34.329 Preferences File: brltty.prefs
2021-10-05 at 16:03:34.331 Updatable Directory: C:/Users/HP PAVILION AMD/Downloads/brltty-win-6.4-0-libusb-1.0/brltty-win-6.4-0-libusb-1.0/bin/../var/lib/brltty
2021-10-05 at 16:03:34.331 Writable Directory: C:/Users/HP PAVILION AMD/Downloads/brltty-win-6.4-0-libusb-1.0/brltty-win-6.4-0-libusb-1.0/bin/../run/brltty
2021-10-05 at 16:03:34.331 Drivers Directory: C:/Users/HP PAVILION AMD/Downloads/brltty-win-6.4-0-libusb-1.0/brltty-win-6.4-0-libusb-1.0/bin/../lib/brltty
2021-10-05 at 16:03:34.331 Tables Directory: C:/Users/HP PAVILION AMD/Downloads/brltty-win-6.4-0-libusb-1.0/brltty-win-6.4-0-libusb-1.0/bin/../etc/brltty
2021-10-05 at 16:03:34.348 Text Table: en_US
2021-10-05 at 16:03:34.353 CLDR data can't be loaded - no supported XML parser
2021-10-05 at 16:03:34.383 emoji substitutiion won't be performed
2021-10-05 at 16:03:34.411 Contraction Table: en_US
2021-10-05 at 16:03:34.411 Attributes Table: left_right
2021-10-05 at 16:03:34.411 Keyboard Property: type=
2021-10-05 at 16:03:34.411 Keyboard Property: vendor=
2021-10-05 at 16:03:34.411 Keyboard Property: product=
2021-10-05 at 16:03:34.411 Keyboard Table: off
2021-10-05 at 16:03:34.411 BrlAPI Server: release 0.8.3
2021-10-05 at 16:03:34.434 API Parameter: auth=
2021-10-05 at 16:03:34.434 API Parameter: host=
2021-10-05 at 16:03:34.434 API Parameter: stacksize=
2021-10-05 at 16:03:34.434 feature not supported: service ready notification
2021-10-05 at 16:03:34.508 Screen Driver: wn [Windows]
2021-10-05 at 16:03:34.508 Windows Screen Driver:
2021-10-05 at 16:03:34.508 Screen Parameter: root=
2021-10-05 at 16:03:34.508 Screen Parameter: followfocus=
2021-10-05 at 16:03:34.583 libusb_open error 40: Function not implemented
2021-10-05 at 16:03:34.583 libusb_open error 40: Function not implemented
2021-10-05 at 16:03:34.583 libusb_open error 40: Function not implemented
2021-10-05 at 16:03:34.583 libusb_open error 40: Function not implemented
2021-10-05 at 16:03:34.583 libusb_open error 40: Function not implemented
2021-10-05 at 16:03:34.583 libusb_open error 40: Function not implemented
2021-10-05 at 16:03:34.583 libusb_open error 40: Function not implemented
2021-10-05 at 16:03:46.743 WSALookupServiceBegin error 10108: No such service is known. The service cannot be found in the specified name space.
2021-10-05 at 16:04:01.757 RFCOMM connect error 10060: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
2021-10-05 at 16:04:01.827 libusb_open error 40: Function not implemented
2021-10-05 at 16:04:01.827 libusb_open error 40: Function not implemented
2021-10-05 at 16:04:01.827 libusb_open error 40: Function not implemented
2021-10-05 at 16:04:01.827 libusb_open error 40: Function not implemented
2021-10-05 at 16:04:01.827 libusb_open error 40: Function not implemented
2021-10-05 at 16:04:01.827 libusb_open error 40: Function not implemented
2021-10-05 at 16:04:01.827 libusb_open error 40: Function not implemented
2021-10-05 at 16:04:16.832 WSALookupServiceBegin error 10108: No such service is known. The service cannot be found in the specified name space.
2021-10-05 at 16:04:31.842 RFCOMM connect error 10060: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
2021-10-05 at 16:04:31.887 libusb_open error 40: Function not implemented
2021-10-05 at 16:04:31.887 libusb_open error 40: Function not implemented
2021-10-05 at 16:04:31.887 libusb_open error 40: Function not implemented
2021-10-05 at 16:04:31.887 libusb_open error 40: Function not implemented
2021-10-05 at 16:04:31.887 libusb_open error 40: Function not implemented
2021-10-05 at 16:04:31.887 libusb_open error 40: Function not implemented
2021-10-05 at 16:04:31.887 libusb_open error 40: Function not implemented
2021-10-05 at 16:04:46.902 WSALookupServiceBegin error 10108: No such service is known. The service cannot be found in the specified name space.
2021-10-05 at 16:03:46.743 WSALookupServiceBegin error 10108: No such service is known. The service cannot be found in the specified name space.
2021-10-05 at 16:04:01.757 RFCOMM connect error 10060: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
2021-10-05 at 16:04:16.832 WSALookupServiceBegin error 10108: No such service is known. The service cannot be found in the specified name space.
2021-10-05 at 16:04:31.842 RFCOMM connect error 10060: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
2021-10-05 at 16:04:46.902 WSALookupServiceBegin error 10108: No such service is known. The service cannot be found in the specified name space.
Sent from Mail for Windows
From: Samuel Thibault
Sent: Tuesday, October 5, 2021 3:21 PM
To: Informal discussion between users and developers of BRLTTY.
Subject: 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
Hello,
shawn klein, le mar. 05 oct. 2021 14:16:26 -0500, a ecrit:
> NVDA doesn’t seem to recognize the BRLTTY package.
Is Brltty running before you start NVDA?
> I find things you’re supposed to do to use it with Window Eyes,
> but nothing for NVDA.
NVDA includes its BrlAPI bits to be able to connect to the existing
BRLTTY.
> brlapi.ConnectionError: couldn't connect to b':0' with key b'none':
> b'CreateFile: Result too large'
I'm a bit baffled by such error message.
Which versions of NVDA and Brltty are you running?
Samuel
_______________________________________________
This message was sent via the BRLTTY mailing list.
To post a message, send an e-mail to: BRLTTY at brltty.app
For general information, go to: http://brltty.app/mailman/listinfo/brltty
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://brltty.app/pipermail/brltty/attachments/20211005/0419f4e0/attachment-0001.html>
More information about the BRLTTY
mailing list