cordat...@aol.com wrote: > An alternative is to use Mike Brutman's mTCP DHCP program.
This is of course true, but there is another alternative . . . > So to sum up: if your application program uses the right > version of WATTCP then you don't need to do anything, > run the program and it will tell you if DHCP fails. This option might not always be available. If you download "legacy" WATTCP applications from just somewhere on the net, you often have no choice, you must take them as they are. Many times you don't even know which version of WATTCP was linked to them and many of these programs, especially older versions do not support dhcp or even worse, their dhcp support is buggy. So, the above mentioned alternative to Mike Brutman's DHCP program is a program named NTOOL which i wrote. Even though it is essentially an incarnation of netcat, well known from UNIX/LINUX, i also added a sub-function ( NTOOL -g " " ) to inquire a dhcp server and output the results to stdout, because i once faced the very same problem. Re-directing this output to a file, could give you a (basic) WATTCP.CFG file which every WATTCP program will understand. NTOOL can be downloaded from here: http://www.bttr-software.de/products/jhoffmann/ ___________________________________________________________ Empfehlen Sie WEB.DE DSL Ihren Freunden und Bekannten und wir belohnen Sie mit bis zu 100,- Euro! https://freundschaftswerbung.web.de ------------------------------------------------------------------------------ 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
