Tom,

I tried the same thing with 3 different file types: .doc, .kwt, and .txt with 
the  same results as you described.

The body of the message came before the data which was apparently the 
attachment.  The actual message text was more or less readible and it really 
looks 
as though the file is simply not being decoded properly when received for some 
reason.

If I read this same message and attachment with the pc, the attachment comes 
through just fine and is a separate attached file as it should be.  

If I send the message and attachment from the pc, the braillenote receives it 
and handles it properly and it is a separate file as it should be.  No 
undecoded 
information is present.  

So, at least in my tests, the problem only occurs when you are sending from a 
braillenote running 6.11 to a braillenote running 6.11 although the problem may 
occur when sending to someone with a pk or an older version of keysoft.  Since 
I have neither here, I can't test for that one.  

Dean has all the information including the poplog.txt files and it has been 
passed to the developers to try and sort it all out.  

I'm certain we will hear something from hw when the problem has been resolved 
and tested.

Don





Reply via email to