jdredd87
commented
1 year ago I lowered the MTU and other buffer values to basically half. And now things seem to be much better now. I assume in this case, buffers were to big for the speed of this thing maybe. It is good enough I have the HTTP server running now and it works pretty well.
Using an IBM Model 30 - 8086 system.
mTCP - March 31st 2023 version.
NEC V30 CPU Upgraded 8087-2 FPU Lo-Tech 2mb EMS Card Trident TVGA8900D 1mb VGA Card PS2XT2SD - HDD , SSD replacement.
XIRCOM PE3-10BT
Running MS-DOS 6.22
I have the XIRCOM on Polling mode. This allows it to get an IP via DHCP.exe every single time, first try. If I don't and use interrupt, DHCP.exe fails alot. Where it may take 3 to 100+ times to retry before it gets an IP. Polling, 1st time, every time.
When using FTP client ( or as a server ) it disconnects a lot. Fails to connect. Ect. Ala ,very touchy and high failure rate.
The XIRCOM is running in Non-Bidirectional mode, which it seems the system says it can do? but the driver doesn't like it.
So not sure if just down the XIRCOM on this system is just not a good fit, or if some thing in the mTCP.CFG file I can tweak to help with issues.
I also have similar issues with trying to do TELNET.
Possibly A case of needing to LOWER buffers maybe?
Is there A program available to kind of do A "stress test" that spits out some kind of reporting?
Doing FTP Download for example, it seems that every ~5 seconds, it gets 32,768 bytes. So 6,553 bytes per second.
To be honest.... I am not sure if this is "good" or "bad" in this case. But I did see on FreeDos page that they were getting 32k per second on the same Xircom on a 4mhz system.