mbbrutmanMar 12

Greetings fans of DOS networking! I'm working on bug fixes for mTCP. If you have a bug report or a feature request now would be a great time to let me know. Send it by email or ping me here.

So far I've done a lot of "code golfing" (making things smaller and faster). Telnet will have SIXEL graphics enabled and a few bug fixes. TCP has a flow control improvement to help with the occasional stall. And there are a few other small fixes so far too.

#retrocomputing #mtcp

Show threadWilliam B PeckhamMar 12
@mbbrutman I am not a big fan of DOS networking in that it is still, after all this time, too manual. But if I'm going to install 3DOS, as I certainly will, over and over again, I want networking to work. And I heartily approve of everything that makes it easier, better, or faster.
Show threadmbbrutman

@wbpeckham You probably already know this, but DOS didn't start with networking so everything is grafted on.

I'm a big fan of the "packet driver" approach, which loads a small device driver for your card as a TSR and enables the higher level applications using a published API.

Besides the packet driver, my code needs one-time configuration. After that run EXEs for what you need. That's pretty simple.

#retrocomputing #mtcp

Mar 12 at 4:33pmWeb
Show threadWilliam B PeckhamMar 12
@mbbrutman Yup. Knew that. Been networking DOS since "the $25 network" was new. Finding a packet driver for a lot of the newer network cards is a whole lot more fun because back in the day you used to get a NIC install disc that had a whole bunch of different kinds of drivers and interfaces and at least one of them would be a packet driver. Now, the right one can be a heck of a lot harder to find if you can even be sure one exists.