Hi, Please don't panic. There are better things to worry about. Just to clarify:
- The source for the 2013-05-23 version is available and always will be. That particular release was probably near perfect because very few people ever ask for more features or send bug reports. - The source for my latest version is not released yet. That makes the current version effectively "closed source" for now. As the website says "Note: The current version of mTCP is not available as open source yet." I'd like to emphasize that last word. Calling it a "license change" is probably too strong; it is not like I have announced a licensing change or said that I will never release source again. - The current version adds two new programs and fixes a bunch of small bugs in the previous versions, only one of which is serious. (The FTP server forgets to remove the Ctrl-Break handler on exit so you might have an unstable system after exiting the server. Please upgrade to the current version or reboot after running the older versions of FTP server.) - The current source code is actually much better structured in the current version than in the previous versions. A lot of the restructuring/refactoring was to make bugs like the one described above less likely. Some of the restructuring was required to allow pkttool to use the lowest level packet driver interface code. - Rest assured that I have not lost interest in mTCP. You can see from the new pkttool program that I'm starting to inch toward IPv6 support. The HTTP server was a major piece of work too. The rewrite of the documentation was very time consuming but it should make mTCP much more usable. (If you have not seen it please look at the PDF file: http://www.brutman.com/mTCP/mTCP_2015-07-05.pdf ) I have many ideas for enhancements and new programs. I still want your bug reports and your feature enhancements. And I am still actively helping people who email me for help. - mTCP programs are generally smaller, more standards compliant, more stable, and far faster than equivalent programs using other TCP/IP stacks. I put a great deal of work into making sure that stays true from release to release. mTCP programs work on all machines, 16 or 32 bits. mTCP is actively maintained. I think that whether it is open source or not it is still a great solution for DOS networking. If the lack of source code prevents you from using mTCP I regret that and I encourage you to question your assumption that without source code it is not "clean" or "good" enough for you. Mike
------------------------------------------------------------------------------
_______________________________________________ Freedos-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/freedos-devel
