I've now confirmed that the drivers do work. Tested with DosBox on two computers.
*Edit*
Description of the drivers.
The first driver, NAMEDEV.SYS, is some kind of server name-dictionary & buffer.
The second driver, SERIAL.SYS, is an I/O device for the Serial port, taking use of NAMEDEV.SYS.
Both drivers are pretty small; Both drivers installed takes about 4Kb, whitch shouldn't be a too great deal in a PC. Each of them can be used with parameters, but their default values are compatible with Sopwith.
You can even play over a modem (dial your friend on the other side of the countery and play multiplayer realtime)! but remember to set the modem to 300 Baud.
Nore: NAMEDEV.SYS must be loaded before SERIAL.SYS!
I am sorry to resurrect such an old thread, but how exactly did you get this working in dosbox?
In dosbox I tried devload, dtload, loadsys, and a few other programs to load NAMEDEV.SYS and SERIAL.SYS. Even though a few seemed to return decent feedback, once I ran the game I got a "error opening NAMEDEV dictionary device error).
I then created a bootimage with MS-DOS 6.2 loaded to it. I loaded the two sys files in the config sys and booted the game from there. This time it actually states it is "waiting for other player", which tells me the sys files loaded fine. But.... I am unaware of how to use dosbox's serial commands through a virtual drive load.
For typical nullmodem games in dosbox I am using the command:
serial1 nullmodem port:5000 (for the host)
serial1 nullmodem server:%IP% port:5000 (for the client)
This generally works for most games loaded via dosbox. However, when booting two virtual images in two different instances of dosbox, I was unable to get them to see eachother. Presumably dosbox isn't passing the connected ports through to the MS-DOS boot.
So, to circle back around. May I ask how you tested this? Thank you.