[BRLTTY] BrlTTY Braille freezes on Windows7 64-bit with NVDA

[Michael Whapples]

Hello,
Here is a debug.log file (attached) from running the debug batch file, a freeze of the Braille did occur. Also please note that while I have BrlTTY set to auto detect for the Braille driver in that debug file, I have also had the issue when having it set specifically to the ALVA driver.

Michael Whapples

From: Anders Holmberg 
Sent: Sunday, January 08, 2012 6:31 PM
To: Informal discussion between users and developers of BRLTTY. 
Subject: Re: [BRLTTY] BrlTTY Braille freezes on Windows7 64-bit with NVDA

Hi!
Try to send a brltty log by running the debug batch file.
Then send the log to the list.
I guess this will help the devs to resolve the problem.
/A

Michael Whapples skrev 2012-01-08 19:17: 
  Hello,
  At this point I cannot work out whether this issue is a BrlTTY or NVDA issue.

  I am using NVDA with BrlTTY 4.3-2 on Windows7 64-bit and from time to time Braille output on my ALVA 544T freezes. When the Braille freezes the only way to get NVDA to produce new Braille on the display is to quit NVDA (at this point the display still shows what was on the display when Braille froze), unplug my ALVA display from the USB port and plug it back in (I plug it back in to the same USB port) and then restart NVDA.

  I have not found a single cause of the issue, however it seems to be most likely to happen when the Braille is updated frequently and quickly (eg. when I am typing in a text field, however it is not restricted to just typing).

  As I said I am running this on a Windows7 64-bit system and can only test it with an ALVA 544T display through USB (the Windows7 system has no serial port). I have not got any other screen reader or software which will use the Braille display installed and also do not have the libusb filter driver installed (as recommended in the BrlTTY installer). I have the BrlTTY service installed so that BrlTTY starts when windows starts.

  I have taken a NVDA log file of when the freeze of Braille occurs but I am unable to find anything unusual going on in that. However I am not yet ruling it out as a NVDA bug. Could anyone give me suggestions on how to try and find the source of this bug.

  Michael Whapples

   

_______________________________________________
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 --------------
An HTML attachment was scrubbed...
URL: <http://mielke.cc/pipermail/brltty/attachments/20120109/f6f02626/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: debug.log
Type: application/octet-stream
Size: 54270 bytes
Desc: not available
URL: <http://mielke.cc/pipermail/brltty/attachments/20120109/f6f02626/attachment.obj>