Azami wrote on 2026-02-13, 12:54:

It should print help if you enter 'help'. I made a few cosmetic changes yesterday but nothing should change the help text behavi […]
Show full quote

It should print help if you enter 'help'.
I made a few cosmetic changes yesterday but nothing should change the help text behavior.

Just tested on Windows 3.1/NT 3.51/10/wine with no issue.

The attachment winsftp.png is no longer available

alright just found the problem in my side. some object files are compiled with old defines, and recompiling them works now.

and plink in NT 3.1 works, but there is no ansicon for NT 3.1, and you need to wrap with k95 for better ANSI escape code decoding.

save this as "k95plink.bat" and run `k95plink remotehost` in cmd window will help, unless your remote-host doesn't emit any ANSI escape codes then you can use plink directly.

1@k95 -C "set terminal color terminal-screen white black , set terminal statusline off , pipe plink %1 , exit"

Nice to know 🙂

just created an issue about enhancing winsftp: https://github.com/Toyoyo/putty-win32s/issues/5
what do you think?

It might be useful, so I (well, mostly AI) added support for a local command set and SCP support.
Also fixed a bug where the client would not reset properly in case the server closed the connection early (for example, if sftp subsystem was set to /bin/false)

I should publish a new binary release soon if everything works solidly (I tested a bit on my side, seems to be working fine)

Azami wrote on 2026-02-14, 15:03:

It might be useful, so I (well, mostly AI) added support for a local command set and SCP support.
Also fixed a bug where the client would not reset properly in case the server closed the connection early (for example, if sftp subsystem was set to /bin/false)

I should publish a new binary release soon if everything works solidly (I tested a bit on my side, seems to be working fine)

thats cool, thanks.

BTW I wonder why they are compiled with `-od` switch?
I tried to use `-ox` instead of `-od` to compile and it produces smaller and faster binary.

I had this issue on 0.76, where any optimization level would make puttygen crash on key generation, at least when compiled with the then-latest OpenWatcome 2.0 beta.

Edit: seems to work fine now, so maybe the optimization can be re-enabled 😀

Did some further testings in NT 3.1, winsftp.exe can work when winsftp.exe's subsystem version is changed to 3.10.
puttygen.exe uses some APIs that is unavailable in NT 3.1: CheckMenuRadioItem, DrawEdge
putty.exe of course won't run in NT 3.1 due to missing OLE32 and COMCTL32.dll is too old to support TreeView, and some missing APIs: GetCharacterPlacementW, GetLocaleInfoA, DrawEdge, DrawIconEx, GetKeyboardLayout, GetSysColorBrush, LoadImageA

if you want to use a poor man's listbox to present a treeview, there is a sample in win32sdk: https://github.com/joncampbell123/windows_sdk … /filer/expdir.c

Tried the latest version from github but unfortunately it does not work for me. Getting the error from the screenshot. Tried it a couple of times with reboots between them. Also one time it was hanging Windows.

Tried in the past version 0.76 and that version worked okay. Winsftp is starting correctly btw.

If you need more information let me know.

EDIT: This is on WfW 3.11 with WIN32S on MS DOS 6.22. Network is working correctly (tested with Netscape etc).

Since I can't reproduce this I don't know what I can do, when does this happens?
At startup? Opening a connection?
Just in case, does this happen in puttytel.exe too?

Azami wrote on Yesterday, 22:33:

Since I can't reproduce this I don't know what I can do, when does this happens?
At startup? Opening a connection?
Just in case, does this happen in puttytel.exe too?

I happens immediately at startup. So before any (connection) window is shown.

Will try puttytel tomorrow. I guess I don't need to install any (UTF8) libraries?

There's no UTF8 libraries for windows 3.1 anyway 😀
But make Win32s *1.30c* is correctly installed, and especially COMCTL32.DLL is "up to date" (it's loaded unconditionally on startup).

Puttytel is showing a window. Couldn't test it more as I don't have telnet servers. Win32s is installed correctly and this also includes COMCTL32.DLL (=latest version for WfW 3.11 as far as I know). Don't have a lot of Win32s applications but the included game is working correctly.

when you say "A window", do you talk about the initial configuration dialog, or a terminal window after the configuration dialog?

The main window where you can make a connection. Tried to make a connection as well but it failed obviously as I don't have a telnet server.

And on putty, it crashes before displaying this window, right?

Azami wrote on Today, 13:02:

And on putty, it crashes before displaying this window, right?

Yes.

Could you test both of the attached executables?
- The puttytl.exe one includes a change in the THREADLOCAL usage which *might* be the issue.
- The puttytld.exe is the same but built without optimizations (which caused problems in the 0.76 build).

Now to be honest, I just tested on 2 "clean" dosbox-x setups (one WfW311 + mstcp32, one Win3.1 + packet driver + trumpet), I still can't reproduce your crash.

I'm running it on retro pc's btw. Did a lot of testing today. I did a win32s install on another pc (386/40) and the latest putty is running without errors. But it's so slow that it never gets a connection. After several minutes it gives a connection error on the client (all while the terminal screen is black). The error from sshd deamon on the server: sshd[1733]: Timeout before authentication for connection from 192.168.1.1 to 192.168.1.2. But it never gets to the login prompt.

On the original pc (486/66) the latest version of putty still gives an error even after a win32s reinstall. All other versions work (above 2 test versions). But only with puttytl.exe I get sometimes a successful connection. It is (with all versions) so slow that even on this pc I sometimes get timeout issues. And with enough unsuccessful connections sshd will lock you out for some time. 😀