On 4/26/2012 10:18 PM, jasse...@itelefonica.com.br wrote:
My wishes:
1) Support for class 6 packet drivers
2) TCP/IP packet logging capability
3) A TSR version
Best regards,
JAS
1) mTCP does not support serial (class 6) directly. But DOSPPP can be
used with mTCP and I have used one
Hi Michael Brutman, others,
A network drive letter similar to the Microsoft LAN client would
be great, but that is a major undertaking - far larger in
effort than the FTP server, which was the last major addition.
That is not coming any time soon - it might as well be a
separate project
Michael B. Brutman mbbrut...@brutman.com said:
If you have an idea let me know. I can't get to everything,
but if the idea is good it will definitely get priority.
Small tweaks to the existing code are always possible to.
My wishes:
1) Support for class 6 packet drivers
2) TCP/IP packet
On 4/21/2012 5:44 AM, Marcos Favero Florence de Barros wrote:
snip
Also, it would be nice if mTCP became FDAPM-aware.
Regards *and* thanks,
Marcos
Marcos,
I'm testing this now. With FDAPM set to APMDOS VirtualBox is idling.
Before I made the change it was chewing up an entire CPU.
I
Op 21-4-2012 5:51, Michael B. Brutman schreef:
If you have an idea let me know. I can't get to everything, but if the
idea is good it will definitely get priority. Small tweaks to the
existing code are always possible to.
* DHCP client that also writes WATTCP.CFG, so 1 dhcp-request keeps both
Marcos,
A network drive letter similar to the Microsoft LAN client would be
great, but that is a major undertaking - far larger in effort than the
FTP server, which was the last major addition. That is not coming any
time soon - it might as well be a separate project for the amount of
work
Hi,
On Sat, Apr 21, 2012 at 8:13 AM, Michael B. Brutman
mbbrut...@brutman.com wrote:
Making mTCP more CPU power aware - I went down this path and there are
#defines in the code for some of it. I chose not to implement it
because there was confusion on how to do it across all of the platforms
I am looking for wish lists items, bug reports, and ideas for the next
release of mTCP.
The current version is about six months old now. I haven't had too many
bug reports so there has not been a great need to update it. That is
also the release that FreeDOS 1.1 chose to use, so it has seen
