[BRLTTY] Use BRLTTY under Windows 7 with Virtual Braille device

[D&J Renaldo]

Hello,
In addition to my previous e-mail, you will find the log file here-attached.
I have modified the brltty.conf file as advised by Samuel (release-device off).
In debug mode, a display is shown and stable (previously it was blinking - probably due to multiple release) 
It indicates  : "no attachable console".
For BrlAPI, there is no change: the service is started and running but nothing is visible. It looks idle.
Your advices are welcome.
Best regards
Denis
-----Message d'origine-----
De : brltty-bounces at mielke.cc [mailto:brltty-bounces at mielke.cc] De la part de Jeanine & Denis Renaldo
Envoyé : mardi 25 novembre 2014 21:44
À : Informal discussion between users and developers of BRLTTY.
Objet : Re: [BRLTTY] Use BRLTTY under Windows 7 with Virtual Braille device

Hello,
Many thanks to Samuel and Dave for their answers.
About the admin rights, I noticed that BRLTTY in debug mode is writing a log file in C:/Program Files/BRLTTY. That is the reason why it does not work properly under W7 without admin rights.
Regarding BrlAPI, the service is properly launched and run under W7 but nothing happens (no window, nothing, it looks idle). I don't know what commands/parameters are necessary to make it working and interacting with Chatty Infty application.
Thanks for your help.
Best regards
Denis


> Le 25 nov. 2014 à 20:14, Samuel Thibault <samuel.thibault at ens-lyon.org> a écrit :
> 
> Hello,
> 
> As Dave said, you most probably want to use the xw driver. Also, it's 
> expected that it doesn't show a braille device by default, just 
> because on windows we enable auto-driver-release by default, to let 
> other screen readers take the braille device when they want to.  You 
> can modify brltty.conf by hand (yes, the configurator doesn't show all 
> options, only a few ones, but you can modify the .conf file, it's a 
> mere text file.), to uncomment
> 
> release-device off
> 
> to disable that auto-release.
> 
> But that's only to get the device always shown.  Your actual issue is 
> getting brlapi running (and getting that fixed would *also* make the 
> braille device show up). Dave, did you have really apply the 
> defauth.patch when building the zipball?
> 
> D&J Renaldo, le Mon 24 Nov 2014 18:24:23 +0100, a écrit :
>> I only saw something when using BRLTTY in the debug mode and run it 
>> as administrator but it's not manageable.
> 
> What happens when you try to run BRLTTY not as administrator?
> 
> Unfortunately none of us really has a win7 box, so we have next to no 
> idea what is happening.
> 
>> It seems that the Brl API has not the rights to work properly but I 
>> don't know how to provide those rights.
> 
> What makes you think this?  Which message appears, exactly?  We need 
> the exact message so we can know exactly which right is missing.  
> Otherwise we can only try to divine, which is a hard exercice.
> 
>> This is a change due to Windows 7 where you cannot access to 
>> C:/Program Files without "admin" rights.
> 
> Well, I do hope that normal users can still read files there, can't 
> they?
> 
> Another way to go could be to just unpack the .zip version somewhere 
> that the user has full access to.
> 
>> But I thought that the xw driver could emulate those devices and give 
>> me enough flexibility to test BRLTTY-CI interface.
> 
> Yes, it should.
> 
> Samuel
> _______________________________________________
> This message was sent via the BRLTTY mailing list.
> To post a message, send an e-mail to: BRLTTY at mielke.cc For general 
> information, go to: http://mielke.cc/mailman/listinfo/brltty
_______________________________________________
This message was sent via the BRLTTY mailing list.
To post a message, send an e-mail to: BRLTTY at mielke.cc For general information, go to: http://mielke.cc/mailman/listinfo/brltty
-------------- next part --------------
A non-text attachment was scrubbed...
Name: debug.log
Type: application/octet-stream
Size: 10216 bytes
Desc: not available
URL: <http://mielke.cc/pipermail/brltty/attachments/20141126/c738d1ad/attachment.obj>