Norton Commander should be able to do this :

https://pc1mh-weblog.blogspot.com/2019/05/nor … os-and.html?m=1

Interlink/Interserve from DOS 6 or Laplink might be other options.
Any Terminal emulation able to tranfer files should work as well.

Thank you for all the info. I'll try them as soom as my cable arrives from Jeff Bezos.

My preferred method (which I do a lot) is via my own DDLINK software.
It's a 16-bit DOS program, which can do file transfers over serial,
parallel and network. Very small (17k), nice screen interface, doesn't have
to be installed...

Serial and network work everywhere, parallel under Windows in not reliable.
If you are using Win64 (most "modern" versions) - 16-bit DOS software
doesn't run directly, but DDLINK can run in DosBox and serial/network
work very well.

For serial, all you need is a "null modem" cable. For network you need
a "packet driver" for your DOS network card, and WinPcap for Windows.
DosBox emulates a NE2000 NIC which is dead easy to get a packet driver for.

I have a collection of hundreds of packet drivers on my site, you can
also refer to the official site: crymwr.com

There's a thread about DDLINK with more information, screenshots
etc: DDLINK: Easily move files between/To/From DOS systems

Dave ::: https://dunfield.themindfactory.com ::: "Daves Old Computers"->Personal

MrSzalonna wrote on 2025-02-26, 22:55:

Hi!
I need to transfer files from Windows to DOS with a serial port. Is there any software for this?
Both of my PCs support serial.

You haven't said which Windows version which can affect your options a little.

Using the Kermit protocol is an option - there are open-source implementations of this for just about everything. MS-DOS Kermit is the standard and fully-featured implementation on DOS, and I maintain the native Windows and OS/2 implementation (Kermit 95). These tools aren't GUI/menu driven so there is a bit of a learning curve, but it also means its all scriptable and pretty flexible and fast to use once you know the commands. I wrote some notes a few weeks a go which may help.

If the DOS computer is able to have a network card installed, its worth considering a network though - it will be much faster and it isn't really any more difficult. It also opens up other options which may be easier in the long run, like network drives. This is my preferred solution where ever possible as it means I don't have to copy files on to and off of vintage machines.

I use Windows 11 64 bit and DOS 6.22.

MrSzalonna wrote on 2025-02-28, 12:52:

I use Windows 11 64 bit and DOS 6.22.

I've not tried Win11 yet - but DosBox works well in Win10 (at least the one I've posted on my
site does), and DDLINK will work there as well as in DOS 6.22

Dave ::: https://dunfield.themindfactory.com ::: "Daves Old Computers"->Personal

Ok,I got everything, but I can't know how to use DDLink. Can you give me some examples?

MrSzalonna wrote on 2025-03-04, 20:07:

Ok,I got everything, but I can't know how to use DDLink. Can you give me some examples?

There is DDLINK.TXT which has a LOT of information about using
it, as well a DDLHLP.EXE (interactive help - invoked by pressing
'?' within DDLINK.

Just run it with: DDLINK ?
Will get you this command summary:

1DavesDataLINK - move/manipulate files via: serial, parallel or network
2
3Use: DDLINK options
4
5opts:   /B              Bootstrap remote (via com)
6        /M              force Monochrome video
7        /S              Server mode
8        P=[ii][,tttt]   specify Packet int,type                   [60-80,DD11]
9        C=1-4[,speed]   specify Com port        ?C  for          [none,115200]
10        L=1-3|addr      specify Lpt port        ?L  more                [none]
11        K=keys          automate Keycodes       ?K  help                [none]
12        B=128-4096      specify Blocksize                               [1024]
13        T=factor        specify Timeout factor                             [5]
14        E=1-255         cause server to End (errorlevel)                [none]
15            Server causes end AFTER one session \ useful in
16            Client  ""    ""    "" immediately  / automated scripts
17        V=n             override protocol Version                       [none]
18            may let different versions perform basic transfers (other feature
19             limitations) useful to update one system from another.
20
21Start SERVER (/S) before CLIENT (no /S)             [interaction is on CLIENT]

Basically you need ONE of C=, L= or P=
(for P= you need to have installed a Crynwr packet driver)

Also you need to start the server end first:
> DDLINK c=1 /S
Then on the client:
> DDLINK c=1
This will bring up split screen directory displays, local (client) on
left, remote (server) on right.
Use left<>right to select side
Use up<>dowm to select file
- available commands are shown on bottom line - eg:

1 'C' will Copy selected file to the other side
2 'V' will View selected file
3 'E' will Erase  "" ""
4 'R' will Rename "" ""
5 'D' will select a different Drive on selected side
6 <ENTER> will CD to selected directory (use ".." to go up)

.. see DDLINK.TXT for details on the other comamnds ..

Dave ::: https://dunfield.themindfactory.com ::: "Daves Old Computers"->Personal

Thank you for your respsonse, but it doesn't work. It says that it's unable to connect. Can you help?

I had a similar problem: I had a DOS laptop at my mother's house that had no hard drive, so I used a network software to simulate some hard drives via a connection to another computer, and at the time, I was using NSLAN to provide the connection. You can find it at http://www.retroarchive.org/garbo/pc/net/index.html. I heard that Easy-Lan can do the job and is more efficient, but before I can try it, the laptop's floppy drive broke. It is at the same location.

MrSzalonna wrote on 2025-03-06, 16:55:

Thank you for your respsonse, but it doesn't work. It says that it's unable to connect. Can you help?

Both systems have to have working COM ports (obviously) and you have to have a properly wired
"NULL MODEM" serial cable - you can see the wiring for one with: DDLINK ?C

To test the connection, you can use the included SDT.COM (Serial Debug Terminal)
If both ports are working, you have the right COM ports selected and the cable is wired/connected
correctly : you should be able to see what you type on one system/SDT appear on the other.

You can also toggle DTR/RTS high/low and their state should appear as DSR/CTS (shown on
bottom line right) on the other (Null modem cable should swap TXD<>RXD DTR<>DSR RTS<>CTS)

Btw, I don't have it in front of me right now (powers off here), but IIRC SDT being only serial uses
P=1-4 to select the serial Port .. DDLINK uses C=1-4 (Com port) because it uses P= for (network/Packer driver)

Dave ::: https://dunfield.themindfactory.com ::: "Daves Old Computers"->Personal

Yeah I might've just bought the wrong cable. All the apologies. When I'll have free time and money, I'll buy another one.