DOS ain't dead

Problem reports - send me a TRACE! (Announce)

posted by mbbrutman , Washington, USA, 24.10.2010, 16:15

> Ways more useful than DOG-BOX

I like DOSBox a lot. It gives me most of what I need for testing without the overhead of a full blown virtual machine. Have anything better to use?


> Test:
>
> * problems with bad performance and lost packets are still there (depends
> heavily from sever)

Bad performance is a side effect of lost packets. If you are losing packets you need to debug that first. I can help you with some of that, but it's not sufficient to say 'bad performance and lost packets'. A trace would be nice, and running the pktstat.com program (from the Crynwr packet driver collection) to give me statistics on packet driver reported errors would be a start. I also have a file called 'DEBUG.TXT' while gives you the two environment variables you need to collect a trace from mTCP; that would help a lot. And my email address is plastered all over the code and docs if you want to send email directly. I've still never seen a trace from you.


> * [ESC] doesn't work to abort transfer

It's not advertised as aborting a transfer, nor is it supposed to. Try Ctrl-Break. FTP.TXT says this clearly.


> * commandline history sometimes displays garbage (FreeCOM has similar
> problems ...)

I'll have to investigate this, but it's the first time I've seen or heard of this problem after two months of usage. I wrote my own code for this so it's probably not related in any way to what you are reporting with FreeCOM.


> * problems with saving are still there (it should check & fix the name
> automatically rather than miserably fail with saving)

What problems with saving? If you give it an invalid filename it fails - that's really simple. If you are giving it a valid filename and it fails then I'd like to hear about it.

In general it's a bad thing to just fix things automatically. That implies that the program knows more than it's user. It might be true in some cases though.

---
mTCP - TCP/IP apps for vintage DOS machines!
http://www.brutman.com/mTCP

Complete thread:

• mTCP 2010-09-16 Version - mbbrutman, 17.09.2010, 02:16 (Announce)
  • mTCP 2010-09-16 Version - 60-Bytes-BUG fixed - DOS386, 13.10.2010, 03:43
    • mTCP 2010-09-16 Version - 60-Bytes-BUG fixed - mbbrutman, 13.10.2010, 06:16
      • mTCP 2010-10-20 Version - IP Fragments! - mbbrutman, 21.10.2010, 05:59
        • mTCP 2010-10-20 Version - IP Fragments! - ecm, 21.10.2010, 06:06
        • mTCP 2010-10-20 Version - IP Fragments! - Rugxulo, 21.10.2010, 08:21
          • mTCP 2010-10-20 Version - IP Fragments! - mbbrutman, 21.10.2010, 15:23
        • mTCP 2010-10-20 Version - IP Fragments! - ecm, 22.10.2010, 18:48
          • mTCP 2010-10-20 Version - IP Fragments! - mbbrutman, 22.10.2010, 20:40
            • mTCP 2010-10-20 Version - IP Fragments! - ecm, 22.10.2010, 21:59
              • License choice? - mbbrutman, 23.10.2010, 23:36
                • License choice? - Rugxulo, 24.10.2010, 00:55
                  • License choice? - mbbrutman, 24.10.2010, 16:19
                • License choice? | TEST | not DOG-BOX - DOS386, 24.10.2010, 04:05
                  • Problem reports - send me a TRACE! - mbbrutman, 24.10.2010, 16:15
                • License choice? - ecm, 28.10.2010, 23:02
                  • License choice? - mbbrutman, 29.10.2010, 01:33
                    • License choice? - ecm, 29.10.2010, 14:02
            • mTCP 2010-10-20 Version - IP Fragments! - Rugxulo, 22.10.2010, 22:24
              • License choice? - mbbrutman, 23.10.2010, 23:42
        • mTCP 2010-10-20 Version - IP Fragments! - Laaca, 29.10.2010, 07:51
          • mTCP 2010-10-20 Version - IP Fragments! - mbbrutman, 29.10.2010, 17:32
            • mTCP - TSR? - ecm, 29.10.2010, 23:31
              • mTCP - TSR? - mbbrutman, 29.10.2010, 23:50
                • mTCP - TSR? - ecm, 30.10.2010, 00:04