I have been working with a Windows Power Basic programmer to 
write a Windows interface to a DOS program.  The DOS program, 
NFB Trans, translates grade II braille to text and text to 
grade II braille.

When the interface is run with Windows XP it works correctly. 
 When it is run with Windows 98 SE there is a problem.  Below 
is the author's explanation of the problem.  Window-Eyes or 
W.E is screen reading software used by a blind person to 
access a computer.  Any suggestions on what might be the 
cause of this problem would be greatly appreciated.

Thank you,

Tom Dimeo


Hello,

I am writing a GUI for the NfbTrans braille translator.  The 
program works with Window-Eyes under XP.  It also works under 
98 SE without speech.  But it does not work with W.E under 98 SE.

The trouble comes when translating multiple braille volumes.  
I'm shelling to command.com and running nfbTrans within a 
for/next loop.  The statement looks like this:
command.com /C nfbtrans.exe parmsList InputFile >OutputFile

The /C switch tells command.com to run the appended command 
line and terminate.
I have tried executing the above via the shell statement in 
the language as well as the shellExecute windows api call 
with similar results.

When things work right, the NfbTrans icon appears on the task 
bar.  Sighted assistants reveal that it "flickers" every time 
there's a volume change and that it disappears from the task 
bar when the for/next loop terminates.

When we run it under W.E, the first iteration works but the 
minimized command window does not terminate.  If we move the 
actual mouse a bit, the windows closes and the next iteration 
occurs.  If you keep doing that, eventually all volumes are 
translated, the loop terminates and focus and speech return 
to my GUI front end.

My question is, have you encountered anything like this 
before?  and if so, can you suggest how I might shell to this 
dos app and get command.com to terminate?
============= PCWorks Mailing List =================
Don't see your post? Check our posting guidelines &
make sure you've followed proper posting procedures,
http://pcworkers.com/rules.htm
Contact list owner <[EMAIL PROTECTED]>
Unsubscribing and other changes: http://pcworkers.com
=====================================================

Reply via email to