[The message I posted earlier seems to make its whole thread become unreadable, so this is a copy of it, without any attachment etc.]

I had a look at the effect of the MTU (maximum transfer size) on the  performance issue, and found that it is very important!  See the attached chart.  It shows the transfer time for a ~1MB file from XP over both IrDA and Bluetooth, and from the Belkin (Broadcom?) stack on Windows 2000.

[image at http://32feet.net/files/folders/2575/download.aspx]

It is clear that a buffer size of at least 16KB is best for performance.  (By the way I got an error when sending from the XP "Bluetooth File Transfer Wizard" to the server when using a 64KB buffer).

I'll post a new release sometime soon, in the new year probably, until then you should change the buffer size in CmdlineRunner.PutToDiskServer.CreateHost(System.Net.Sockets.NetworkStream, ObexServer.IObexServer).  It currently is 2048; change it to 16384 or greater.

Some receive buffer sizes seen on other server types are as follows:

        \    IrDA        Bluetooth
Win XP    32672    65535
Win 2k    9983    16384—Belkin
PalmOS    4090    2660
Nokia6210    123        n/a

Andy