From: blockedofcourse@foo.invalid   
      
   On 1/20/2026 5:08 PM, Nioclás Pól Caileán de Ghloucester wrote:   
   > Don Y  wrote:   
   > |-----------------------------------------------------------|   
   > |"- TELNET/SSH console                                      |   
   > |- FTP client                                               |   
   > |                                                           |   
   > |[. . .]                                                    |   
   > |                                                           |   
   > |I can use PuTTY for SSH/TELNET; not as nice of an interface|   
   > |but it seems very reliable."                               |   
   > |-----------------------------------------------------------|   
   >   
   > I use PuTTY a lot without a problem. A recent version of Microsoft   
   > Windows has its own SSh implementation. I do not use it a lot.   
      
   I don't rely on MS for any "legacy" protocols.  Their UI is (deliberately?)   
   crippled to hide capabilities of the underlying filesystem, etc.   
   (filename case sensitivity, MAXPATH, SMB issues with huge numbers   
   of transfers).   
      
   You can use other tools to work around these -- but, when you   
   return to the Windows GUI, you're screwed!  (How do I   
   access ReadMe when README, readme and ReAdMe all coexist in   
   the same context?)   
      
   > I do not use FTP a lot on new versions of Windows. Even old versions   
   > of Windows used to come with their own implementations. Corrupted big   
   > files were risks, but probably more because big downloads via FTP   
   > (instead of e.g. SFTP or BitTorrent) are risky than because of   
   > Microsoft ineptness. Wget supports FTP, but I do not use it a lot for   
   > FTP to Windows.   
      
   MS has issues trying to transfer large numbers of files via SMB.   
   And, MAXPATHLEN issues.   
      
   So, if you want to confine yourself solely to the MS world,   
   you *might* be able to avoid them (try unzipping a file   
   with a/really/long/internal/path/name/to/a/specific/file to   
   a folder that is/located/pretty/far/down/in/the/file/system.   
      
   > Apple MacOS comes with an SSh client.   
      
   PuTTY works though has a bit "dated" interface.  The fact that   
   each session is a separate window is, IMO, a win.  Other clients   
   want to use MDI -- which sucks if you want to exploit lots of screen   
   space to see multiple sessions concurrently.   
      
   NCDware was my go-to X server in ages past.  The NetSarang product   
   is "adequate" and manages to coexist with my triple headed   
   workstations without complaining.   
      
   The FTP product was the killer.  It would become unresponsive   
   (just the GUI side; transfers kept running).  It would reconnect   
   a disconnected session and forget to reinvoke all of the   
   options that were in effect from the disconnected session   
   (BIN being the most consequential).  At times, it would just "stop"   
   and act as if it was still running.  etc.   
      
   I don't want to fight my tools -- they are supposed to work for me!   
      
   Beyond Compare is a workaround but not the ideal solution (for   
   file transfer).   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)