weirdr.net is a Fediverse instance that uses the ActivityPub protocol. In other words, users at this host can communicate with people that use software like Mastodon, Pleroma, Friendica, etc. all around the world.

This server runs the snac software and there is no automatic sign-up process.

Site description
This is a dual Pentium Pro running NetBSD.
Check out the floppy museum for hints on how to get in touch. Or, you know, ping me on the fediverse. :)
Admin account
@ltning@weirdr.net

Search results for tag #mtcp

[?]mbbrutman » 🌐
@mbbrutman@mastodon.sdf.org

I spent two long days coding streaming writes for mTCP NetDrive. I have some early results.

The test: Copy a large file (1.7MB) from a 386-40 with an NE2000 card to a Linux server about 1800 miles away.

Old code: 18KB/sec
New code: 214KB/sec

The new code is about 350 bytes larger and uses no additional memory on the client side. On the server side I just had to increase buffer sizes.

And DOS is none the wiser .. the remote server just looks like a drive letter.

    [?]mbbrutman » 🌐
    @mbbrutman@mastodon.sdf.org

    @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.

      [?]mbbrutman » 🌐
      @mbbrutman@mastodon.sdf.org

      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.

        9 ★ 4 ↺

        [?]Ltning » 🌐
        @ltning@weirdr.net

        Despite all the things IBM did right with OS/2, there were some absolutely mind-boggling decisions made. Today's example: Using Java (version 1.11 or better, mind you) and a Netscape browser plug-in to install TCP/IP. Other than the chicken-and-egg-problem (which is solved by installing the transport services - NIC and protocol drivers - first), there's the fact that they had a perfectly good software installation framework which ran fine on like 6-8MB of RAM (total!). This variant swaps until my CF card starts sweating with 16MB, and is s-l-o-w!

        I mean yeah, great, I get a proper BSD-4.4, 32-bit TCP/IP stack and tools. But it's taken me half a day. Getting the installation files over involved loading packet drivers and using in a DOS session. Which works .. surprisingly well. But still .. FixPak43, reboot. MPTS, reboot. Netscape 2.02, reboot. Java 1.18, reboot. Feature Installer plug-in (no reboot). Then, finally, TCP/IP.

        All this to have a machine to play with at .


          ltning boosted

          [?]mbbrutman » 🌐
          @mbbrutman@mastodon.sdf.org

          The latest mTCP for DOS is available!

          This version includes some changes to improve TCP reliability on long running (but idle) connections, black & white Sixel graphics in Telnet, a Telnet emulation bug fix, and other small fixes sprinkled around.

          The source code to NetDrive (network attached storage) is also published now - enjoy reading an unholy mix of x86 assembly code talking to Golang over UDP!

          Spread the word! Friends don't let friends run old code ...

            about this site - powered by snac/2.91