On 5/28/2011 3:57 AM, Bernd Blaauw wrote:
hi Michael, congratulations on possibly having the first GPL3 DOS program ^^
I seem to recall you needing permission from your employer to do this so
thanks go out to them as well.
I think that honor was claimed already. I solved the permission problem
by changing employers. ;-0
Hopefully this will make people come up faster with crazy stuff like:
* a WGET (and/or CURL) program based on your TCP/IP stack
* an email client
* a twitter client
* support for Wattcp.cfg from your DHCP program, or some batchmode which
would mean returning parameters rather than writing to mtcp.cfg
As you've got a 2011 TCP/IP stack, I guess IP6 support is next? :)
I can see a simple version of WGET - I promised it to somebody almost a
year ago. I had taken a look at the existing WGET and it was a lot of
code - too much to fit into a 16 bit program. But a stripped down
version is very possible.
I have not thought too much about email. I can already send email using
netcat and a text file with the email contents in it. That is good for
sending notifications from a DOS system. Reading and storing email
without corrupting anything is a much more difficult problem.
Dave Dunfield already has a DHCP client that can write the configuration
files in either mTCP or WATTCP format. Check out his collection of DOS
networking utilities over at http://www.dunfield.com/doswid/index.htm .
His version does not include my extensive tracing support, so I am
hesitant to drop my version. (The tracing used to be important for
debugging my code - now I use it almost exclusively debug other people's
networks.) Adding WATTCP support to my DHCP would be fine as well -
they are so close it makes sense.
Better round trip timing (RTT) estimates for TCP packets and improved
retransmit code based on those times is next on my TODO list. IPv6
should not be difficult but I think I have a few years before most
people are needing that.
even without all of the above, thanks for releasing your work. Hopefully
it will inspire people.
I realized that after the base library was done and applications were
needed that I had become the bottleneck. In the middle of 2008 there
was IRCjr, DHCP, and Netcat. In the last two years I have done FTP,
Telnet, SNTP, PING, the FTP server and a lot of functional and
performance changes to the base library. I can't keep up the pace ...
If we are going to continue to spread the joy of DOS networking I am
going to need help.
I am kind of pleased that I just gave away 30,000 lines of reasonably
good code. The hard part now is transitioning to become a project
maintainer. Up until this point I basically did what I wanted to, at my
schedule. I am going to have to find a way to give up some of that
absolutely control, otherwise this will go nowhere.
Will you add the binary distribution to the same website or prefer to
keep that to your own site?
That is some of the administrative work that I still need to get done.
I am also trying to decide if the time is right to start using SVN or if
I should defer that until I see how many changes are actually going to
go in. SVN is nice from a legal standpoint because it shows who changed
what and when, so I think it will be coming sooner rather than later.
I've still gotta experiment to see if larger MTU sizes make that much of
a difference, but detest writing FTP scripts for each download :)
I use the larger MTU sizes almost exclusively, and yes, it made a big
difference. You have that much less packet processing overhead to deal
with and fewer interrupts to process. MTU 576 should be safe on nearly
any network except those based on slower serial links; those often use
smaller MTUs.
With my ISP and the way things are setup in the US I never see fragments
in the real world. I had to go through great lengths on my internal
network to test the fragment handling code and it is still probably not
well enough tested.
FTP is a little flawed for testing performance because you are including
the speed of the disk subsystem too. So for testing absolute raw TCP/IP
sockets performance take a look at the SPDTEST utility in the
distribution. For real world performance use FTP, but note that the
disk has a significant impact. For comparison testing of MTU sizes it
will be fine.
Mike
--
vRanger cuts backup time in half-while increasing security.
With the market-leading solution for virtual backup and recovery,
you get blazing-fast, flexible, and affordable data protection.
Download your free trial now.
http://p.sf.net/sfu/quest-d2dcopy1
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user
