I had problems with networking in dos for a few users, a short time ago. 
After a lot of headache, I discovered that those were conections via 
ADSL that used PPPoE, which has a 28 bytes overhead.

So now I use
   MTU=1472
and I had no more problems ever since. I recommend to anyone, use 1472 
to avoid problems.

:)
Alain

Em 05-10-2011 20:45, Michael B. Brutman escreveu:
>
> Excellent, and you are welcome!  I am glad it is working this time
> around - I get embarrassed when I let broken code out.  Some questions:
>
> For best performance the following should be set in the mTCP config file:
>
>       MTU 1500
>       FTPSRV_FILEBUFFER_SIZE 16
>       FTPSRV_TCPBUFFER_SIZE 16
>       FTPSRV_PACKETS_PER_POLL 10
>
> The default for the buffer sizes is 8; 16 makes it noticeably better.
> I'm assuming you can use MTU 1500 on your network - if it is pure
> Ethernet that would be safe and optimal.  FTPSRV_PACKETS_PER_POLL has a
> very low default and it could be restricting performance.  Your machine
> is fast enough so setting it to 10 should be fine.
>
> What settings do you have at the moment, and can you try these settings
> and send me new numbers?
>
> You are correct - Datalight Sockets is at a disadvantage because of the
> TSR approach, but you can still use your machine while it is running.
> :-)  WATT32 should have the advantage of being able to use more memory
> for buffering, but it clearly can't run on an 8088.  Most people don't
> want to use an 8088 anyway ..
>
>
> Mike

------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2dcopy1
_______________________________________________
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Reply via email to