The mTCP DHCP client writes output to STDOUT and to the MTCPCFG file, which is pointed to by an environment variable. It's a simple matter of programming/scripting to convert the output from either one into something that looks like a static WATTCP configuration. I've tested my DHCP client fairly widely and have not had any bug reports on it (yet).
If you have trouble with mTCP getting a configuration from the DHCP server, I have a debug trace built into it. Turning the trace on is easy (see DEBUG.TXT) and from the trace I can help you figure out if you have a more generic problem that is preventing the WATTCP applications from getting an address. (As a side note, all of the mTCP apps include a trace mode. It makes debugging network problems like this much easier.) Mike ------------------------------------------------------------------------------ Colocation vs. Managed Hosting A question and answer guide to determining the best fit for your organization - today and in the future. http://p.sf.net/sfu/internap-sfd2d _______________________________________________ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
