XPost: alt.comp.os.windows-11   
   From: nospam@needed.invalid   
      
   On Mon, 1/26/2026 9:52 PM, micky wrote:   
   > In alt.comp.os.windows-11, on Mon, 26 Jan 2026 21:26:46 -0500, micky   
   >  wrote:   
   >   
   >> mOSTLY SOLVED:   
   >>   
   >> It turns out, for all but one chat so far, the problem was in Windows.   
   >> For each transfer, I have to click on the arrow in the systray to open   
   >> up all the miscellaneous overflow icons, click on the Bluetooth icon,   
   >> then chnose Receive a file.  Each time. I didn't expect that.   
   >   
   > I guess since it said "Receive *A* file" I should have thought of this.   
   > LOL   
   >>   
   >> One important one continues to balk.  There is a strange blue large   
   >> capital T in the name of the other party to the chat.  Could that be the   
   >> problem?  That's the only anomaly I see.   
   >>   
   >> Anyhow, thanks for all the help.  Nothing on the web mentioned this   
   >> either.   It's a Dell Latitude 5510 but it's hard to believe the make or   
   >> model makes a difference.  Windows 11 Pro fully updated.   
   >>   
      
   The Bluetooth Fsquirt (which is apparently FTP based?), does   
   things one at a time. And it disconnects things after the transfer   
   is done. Presumably this is a "security feature". FSquirt is available   
   on Linux, Windows, and on phones. A transfer does not get more crude   
   than this. It's one step short of two tomato tins and a piece of string.   
      
   In Windows, they finally have a TCP/IP stack for Bluetooth, such   
   that one machine (with Internet) can be a Bluetooth hotspot, and   
   the other machine can get a connection to the Internet over Bluetooth.   
   This could also allow things like file sharing... as long as you   
   have an App loaded on the end that does not normally have File Sharing.   
   That's not important for your current situation, but is just for future   
   reference. I was surprised, that the latest version   
   could achieve a transfer rate higher than 75KB/sec, by a little bit.   
   This means they might be using compression on the link (like in some   
   old modem days). For movies, don't expect those to transfer   
   faster than 75KB/sec (as they are not compressible).   
      
   When I first started trying to get the TCP/IP stack running over   
   Bluetooth, I got a grand total of two packets across before it   
   seized up. And they've finally got it to the point, you might   
   consider the feature to be "finished". Now, it's not a total waste   
   of time (if you can stomach 75KB/sec as a baseline).   
      
      Paul   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)