[BRLTTY] Windows First Run

[Chevelle]

     I don't have Windows 7 any more.  I think one problem with Windows 
10 is that the device driver fails to install even if you log in as 
administrator.  I got around it by using run command prompt as 
Administrator.  Maybe that should be added to the README file.  For 
example, one way is to tap the windows key, then type comm to find 
Command Prompt.  Then tap the applications key and arrow up and down to 
Run As Administrator and press enter.  Make sure you hear the chime and 
the User Account control Dialogue comes up, and answer yes.  Then run 
the install.bat file.

There is another common method to change the permissions on the Brltty 
directory, but I didn't try that.


I still don't have it working.  The message

BRLTTY 6.0 rev unknown comes up if you run 'brltty' manually.  n.  I don't know if that is harmless or not.
I may try more experiments later this week.


On 10/6/2019 5:27 PM, Dave Mielke wrote:
> [quoted lines by Chevelle on 2019/10/06 at 17:01 -0400]
>
>>      I had an older version, perhaps 5.2 working on Windows 7. Since the other
>> person was asking about it, I decided to try it on Windows 10.
> We need to separate the two issues. One issue is what works on Windows 7 versus
> what works on Windows 10, and the other is does any of this change when using
> an older release of brltty versus when using a newer one. I'd appreciate it if
> these two transitions could be tested separately rather than both at once.
>
>> If you look at the README file it says
>>
>> "This is an unofficial build of BRLTTY 6.0 which also includes a few fixes
>> for Windows"
> Yes, there are a coulpe of special patchdes for the Windows build, but the
> build is official. The wording about it being an unofficial build is old and
> will be fixed.
>
>> When I run the install.bat, I get these errors:
>>
>> BRLTTY 6.0 rev unknown [http://brltty.app/]
>> brltty.exe: OpenSCManager error 5: Access is denied.
>> The service name is invalid.
>> The first error comes from the batch file running "brltty -I".
> As mentioned above, we need to know if it works with 5.2 on Windows 10 and/or
> if it fails with 6.0 on Windows 7. In other words, did Windows introduce a new
> restriction or did we introduce a bug.
>