Image Map Image Map
Page 1 of 4 1234 LastLast
Results 1 to 10 of 39

Thread: mTCP updates coming soon: Send me your bug reports

  1. #1

    Default mTCP updates coming soon: Send me your bug reports

    I have not released an updated mTCP since July 2015. I've got a few bug fixes that I want to distribute, so I'm overdue for for another release. If you have any bug reports or feature requests, now would be the time to let me know.

    So far I have the following changes:

    • All: Warn about white space on the end of configuration file lines
    • HTGet properly handles chunked encoding
    • HTGet error checking on file writes is vastly improved.
    • HTGet gets a "quiet mode" option
    • HTGet HTTP 0.9 support and misc bug fixes.
    • Telnet outgoing packet handling improvements. (Bug tripped by a telnet BBS sending small packets.)
    • Telnet: Provide a setting to eliminate CGA snow and add a CGA_MONO color palette.
    • IRCjr: Provide a setting to eliminate CGA snow.
    • FTP Server: fix bug when using a sandbox on a whole drive, not just a directory.
    • DHCP: More robust error checking when reading and writing the config files.


    HTGet had the most work done; the lack of chunked encoding support was a major screw-up on my part.

    I don't have any new programs or big changes planned. SSH and other programs that require SSL are kind of out of scope; they require too many libraries to be back ported and the libraries are too big to re-implement on my own, even if the 4.77Mhz machines that I target could handle the code. I started a Gopher client years ago but there has not been a huge demand for Gopher. ;-0

    Here are some of things I am thinking about long term:

    • IPv6 is partially in place but that's going to take a while to fully implement.
    • FTP client: A warning when it thinks you are transferring a binary file using ASCII mode.
    • Possible more optional features in the FTP client and server.
    • A program that can image a hard disk over the network. (Think Ghost, but it runs on an XT class machine.)
    • A telnet BBS. I started this years ago and I really should pick it up again.
    • A demo program that plays "8088 Corruption" style video over the network.
    • A stripped down HTTP server that is simpler and smaller.
    • Multiple IRCjr profiles so you can use a different configuration for each IRC network.
    • HTGet cookie support.


    Cheers,
    Mike

  2. #2

    Default

    Quote Originally Posted by mbbrutman View Post
    [*]A program that can image a hard disk over the network. (Think Ghost, but it runs on an XT class machine.)
    that sounds amazing, maybe also imaging for floppies as well?

  3. #3
    Join Date
    Jan 2010
    Location
    New Zealand
    Posts
    4,072
    Blog Entries
    4

    Default

    Awesome Mike. Thank you very much.
    Thomas Byers (DRI)- "You'll have a million people using the A> [MS-DOS prompt] forever. You'll have five million using [nongraphic] menu systems such as Topview, Concurrent PC-DOS, Desq, and those types. But there'll be 50 to 100 million using the iconic-based interfaces."

  4. #4

    Default

    Quote Originally Posted by maxtherabbit View Post
    that sounds amazing, maybe also imaging for floppies as well?
    No, sorry, just BIOS supported hard drives.

    The intent is to allow one to image a hard drive in a machine without having to move the hard drive. Moving an MFM controller and a 20MB hard drive pair to a more modern machine to try to image it is a pain. Doing it over the network is much easier, especially if you have something like a Xircom PE3 adapter that allows you to add Ethernet temporarily without opening the case.

    There are plenty of solutions for imaging floppy diskettes already, and floppy diskettes can have copy protection on them or legitimate errors so that is not a problem that I want to try to solve.


    Mike

  5. #5

    Default

    Quote Originally Posted by mbbrutman View Post
    There are plenty of solutions for imaging floppy diskettes already...
    Yes, I agree, but there is one specific exception to this capability. In the case of a standalone PC or XT with either one or two 360k floppy drives and no hard drive it would not be possible to image a floppy disk unless there is some other storage device available.
    PM me if you're looking for 3" or 5" floppy disks. EMail For everything else, Take Another Step

  6. #6

    Default

    Hi,

    Quote Originally Posted by mbbrutman View Post
    All: Warn about white space on the end of configuration file lines
    Some editors (such as EDIT) make it very easy to leave whitespace around. Whitespace shouldn't matter, so a warning might be more annoying than helpful.

    Quote Originally Posted by mbbrutman View Post
    SSH and other programs that require SSL are kind of out of scope; they require too many libraries to be back ported and the libraries are too big to re-implement on my own, even if the 4.77Mhz machines that I target could handle the code.
    I tried SSH2DOS on a 286/12 a while ago and it would time out computing the key. So... probably not worth it yet.

    Quote Originally Posted by mbbrutman View Post
    FTP client: A warning when it thinks you are transferring a binary file using ASCII mode.
    Hmm. Is there a good reason to use ASCII mode nowadays? I only use it by accident, so simply defaulting to binary (and warn for any ASCII transfers) might be a smarter approach.

    Quote Originally Posted by mbbrutman View Post
    A program that can image a hard disk over the network.
    Do you plan on adding write support? The ability to simply write raw hard disk or floppy images in the target machine would be very useful; even more when considering 360 KB drives or drives with alignment issues (which can't be written on a different machine).

  7. #7

    Default

    Quote Originally Posted by Svenska View Post
    Do you plan on adding write support? The ability to simply write raw hard disk or floppy images in the target machine would be very useful; even more when considering 360 KB drives or drives with alignment issues (which can't be written on a different machine).
    that's actually what I had in mind, although transferring the floppy image to the target machine and running rawrite is trivial I suppose

  8. #8

    Default

    Quote Originally Posted by maxtherabbit View Post
    although transferring the floppy image to the target machine and running rawrite is trivial I suppose
    Only if you have a hard drive. I actually had that issue (single-drive machine, drive slightly out of alignment) and resorted to writing an XMODEM disk image writer to get the machine to reliably boot...

  9. #9

    Default

    Batching several replies:


    [Stone] Archiving floppies over the network:

    I posit that most people have a "tweener" box to read and write diskettes with, and that tweener box has multiple floppy drives, a hard drive, and probably networking on it too. And there are other solutions, such as temporarily attaching storage via the parallel port (Backpack floppy drives, IDE hard drives, Zip drives, Compact Flash readers).

    The case of a person with a lone machine without a tweener or add-ons they can use is pretty unusual.

    If I write the program it won't care - it will just want a BIOS supported device. So floppies will work and I wouldn't do anything to disable that. But it's not something I expect people to take advantage of.


    [Svenska]

    Agreed, the whitespace warning is just a warning. None of my code cares about whitespace but somebody pointed out that it can be a problem on some of the fields so I added the warning.

    FTP ASCII mode is still part of the spec and I want my FTP client to be as widely compatible as possible. Some modern FTP clients (lftp) just always transfer in BINARY mode, but I'm not willing to go that far. (They have to stuff a 'BIN' command in the command stream to do that.) For that matter no modern client supports the traditional FTP mode of opening a data connection where incoming connections could just be expected to go to the default port. But vintage FTP servers don't know anything else, so I have this support in the client even though nobody in their right mind will use it, unless they have a vintage FTP server.

    Network archiving: Write support makes me a little worried; the potential for disaster is pretty high. I'd hate for somebody to wipe out their hard drive by accident, especially since I might have to require people to specifically enter their geometry.

  10. #10
    Join Date
    Jun 2013
    Location
    Montevideo, Uruguay
    Posts
    391
    Blog Entries
    1

    Default

    it could be cool to add a ssh client to it

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •