ObexFTP aborts file transfer at character 26

Anonymous
2007-07-04
2013-05-01
  • Anonymous - 2007-07-04

      Hi!  ObexFTP is a great program!  However, I noticed a serious problem with the precompiled Windows version from this page: http://dev.zuckschwerdt.org/openobex/wiki/ObexDownloads

      I am using the following command to transfer binary files (images, etc.) from Windows Vista to Nokia N70:
    obexftp -b 00:17:4b:15:00:2e -B 12 -c E:/ -p image.jpg

      ObexFTP aborts the file transfer as soon as it encounters a byte with a decimal value of 26.  No error is displayed.  It seems that the ASCII 26 is used as an end-of-file character in some arcane systems.  So in all probability, ObexFTP believes that it arrived at the end of the source file when it bumps into this character, and does not read any further.

      Could this be a bug?  Many thanks in advance for any directions.

     
    • Christian W. Zuckschwerdt

      Hi Karen,

      that is a very precise and useful bug report. I'll look into it right away.

      Thank you very much!

       
    • Christian W. Zuckschwerdt

      It seems we we need to open all files on win32 with an additional _O_BINARY flag.
      Can you please try the patched exe and check if the problem is gone?
      http://triq.net/obexftp/obexftp-r161-win32-static.zip

       
    • Anonymous - 2007-07-06

        Hi!
        This new exe works like a charm, both for text and binary files.  Thank you very much for the quick response, now ObexFTP is the perfect tool for all my scripted Bluetooth transfers.

         Cheers!

       

Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

JavaScript is required for this form.





No, thanks