Re: [Freedos-user] ntool help
hello, I reinstalled freedos to get a fresh start. I just now have been fooling around with ntool and mTCP. just now I got dhcp under mTCP to work. but now it isn't working. I can't get ntool to work either? when I run dhcp through mTCP I get an error: failure to get dhcp address. check your cabling and packet driver settings. I have tcp.cfg, edited and I have the packet driver that I need. and the packet driver is loaded via autoexec.bat. and I just got dhcp to work. when I run ntool I get bootp/dhcp failed. like I said I reinstalled freedos, one reason I did reinstall was to try to figure anything about wattcp.cfg. as far as I know I have wattcp.cfg in c:\fdos\bin\wattcp.cfg I edited wattcp.cfg to just have the line my_ip=dhcp when I run ntool and it fails, I then look at wattcp.cfg and it is empty? like the my_ip=dhcp is gone. mtcp's dhcp doesn't do this. I just renamed wattcp.cfg to wattold.cfg and ran ntool again it ran without any error and wrote nothing to the screen. this makes me think that these programs are like you said getting a fixed ip somewhere. but I am not sure. like I said I reinstalled freedos. any help would be appreciated Sent from my iPhone On Mar 17, 2011, at 6:20 PM, Willi Wasser wiw...@web.de wrote: i just tried to run ntool and i got back an ip address of: MY_IP=0.0.0.0 NTOOL is a WATTCP application itself, one that is linked to a relatively recent version of the WATTCP library that does support dhcp properly. That means, it will try to get its ip parameters from dhcp if the WATTCP.CFG file it finds at program start tells it to do so by specifying MY_IP=DHCP or if it doesn't find a WATTCP.CFG file at all. In this case it will write something like Configuring through BOOTP/DHCP to the screen. If on the other hand it finds a WATTCP.CFG file that defines a static ip address, then it will simply accept this setting, assuming that you know what you are doing. Nevertheless NTOOL -g will output the actual ip parameters that are in effect in this moment. So if NTOOL just tells you MY_IP=0.0.0.0 without any message about using dhcp, then you probably have a WATTCP.CFG file somwhere which defined that address. Probably you just copied that file from somewhere and failed to adjust it to your personal needs. Try to find that file and make it invisible to the program, by re-naming it or by deleting it completely. If that helps, you could even try whether you need NTOOL (or any other external dhcp client) at all. Perhaps lynx just has the very same problem? If the lynx version you use, is also linked to a more recent version of WATTCP, then it could do this all by itself. It not, you could still use NTOOL. ___ 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 -- 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
Re: [Freedos-user] ntool help
First, it was not necessary to re-install FreeDOS. Lynx, Ntool, and all other WATTCP programs are applications, not part of the operating system. The only OS related thing to consider is whether the packet driver is loaded. It sounds like now that your virtual machine settings may have changed such that DHCP is not working. But back to your original problem - how to know if you are accessing the right WATTCP.CFG file? You can add a line to WATTCP.CFG using the PRINT directive. So create a WATTCP.CFG file which contains only the following line: PRINT = James WATTCP.CFG file has been accessed Or whatever text you want. When you run either NTOOL or LYNX if you see this line printed out during initialization then you know that your config file and not that of some evil genius, has been accessed. WATTCP will access one and only one config file. First it looks at the environment variable WATTCP.CFG which represents a directory (not a file name!) if this environment variable does not exist it uses the current directory. It looks first for the file name WATTCP.CFG and if not found for the file name TCP.CFG. I recommend playing around with different config files using the PRINT directive to completely understand which file the applications will access. You could have one file in directory c:\tmp with PRINT = config file in TMP and another file in C:\BIN with PRINT = config file in BIN and try to access these files by being in the current directory and using the WATTCP.CFG environment variable. In any case your applications will access one and only one WATTCP.CFG file (unless that config file has the INCLUDE directive). So that will eliminate a mystery config file setting some strange IP address and get you to the point where you completely understand which config file is being used. Regarding DHCP not working anymore that sounds like an incorrect packet driver for your VM or a setting on the VM or a virtual bridge misconfiguration. -Original Message- From: James Collins james.collin...@yahoo.com To: freedos-user freedos-user@lists.sourceforge.net Sent: Sat, Mar 19, 2011 11:15 am Subject: Re: [Freedos-user] ntool help hello, I reinstalled freedos to get a fresh start. I just now have been fooling around with ntool and mTCP. just now I got dhcp under mTCP to work. but now it isn't working. I can't get ntool to work either? when I run dhcp through mTCP I get an error: failure to get dhcp address. check your cabling and packet driver settings. I have tcp.cfg, edited and I have the packet driver that I need. and the packet driver is loaded via autoexec.bat. and I just got dhcp to work. when I run ntool I get bootp/dhcp failed. like I said I reinstalled freedos, one reason I did reinstall was to try to figure anything about wattcp.cfg. as far as I know I have wattcp.cfg in c:\fdos\bin\wattcp.cfg I edited wattcp.cfg to just have the line my_ip=dhcp when I run ntool and it fails, I then look at wattcp.cfg and it is empty? like the my_ip=dhcp is gone. mtcp's dhcp doesn't do this. I just renamed wattcp.cfg to wattold.cfg and ran ntool again it ran without any error and wrote nothing to the screen. this makes me think that these programs are like you said getting a fixed ip somewhere. but I am not sure. like I said I reinstalled freedos. any help would be appreciated Sent from my iPhone On Mar 17, 2011, at 6:20 PM, Willi Wasser wiw...@web.de wrote: i just tried to run ntool and i got back an ip address of: MY_IP=0.0.0.0 NTOOL is a WATTCP application itself, one that is linked to a relatively recent version of the WATTCP library that does support dhcp properly. That means, it will try to get its ip parameters from dhcp if the WATTCP.CFG file it finds at program start tells it to do so by specifying MY_IP=DHCP or if it doesn't find a WATTCP.CFG file at all. In this case it will write something like Configuring through BOOTP/DHCP to the screen. If on the other hand it finds a WATTCP.CFG file that defines a static ip address, then it will simply accept this setting, assuming that you know what you are doing. Nevertheless NTOOL -g will output the actual ip parameters that are in effect in this moment. So if NTOOL just tells you MY_IP=0.0.0.0 without any message about using dhcp, then you probably have a WATTCP.CFG file somwhere which defined that address. Probably you just copied that file from somewhere and failed to adjust it to your personal needs. Try to find that file and make it invisible to the program, by re-naming it or by deleting it completely. If that helps, you could even try whether you need NTOOL (or any other external dhcp client) at all. Perhaps lynx just has the very same problem? If the lynx version you use, is also linked to a more recent version of WATTCP, then it could do this all by itself. It not, you could still use
Re: [Freedos-user] ntool help
If NTOOL tells you bootp/dhcp failed it means exactly what it says. But this can have two different reasons. Either your packet driver is OK, but no dhcp server answered NTOOL's request. In this case there must be a problem with the dhcp server. Or your packet driver did not load properly, possibly because it is misconfigured or invoked with incorrect parameters. Watch carefully the messages the packet driver issues while loading. Sometimes it helps in debugging to load the packet driver manually as it is easier this way to read all the messages. Usually the packet driver reports the ehternet address of the card it found. Does it look reasonable? And mTCP's DHCP message failure to get dhcp address. check your cabling and packet driver settings means the very same thing. If you failed to load the packet driver completely, then NTOOL would tell you NO PACKET DRIVER FOUND while mTCP's DHCP would write Could not access packet driver. ___ 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
Re: [Freedos-user] ntool help
Sent from my iPhone On Mar 19, 2011, at 1:00 PM, cordat...@aol.com wrote: First, it was not necessary to re-install FreeDOS. Lynx, Ntool, and all other WATTCP programs are applications, not part of the operating system. The only OS related thing to consider is whether the packet driver is loaded. It sounds like now that your virtual machine settings may have changed such that DHCP is not working. But back to your original problem - how to know if you are accessing the right WATTCP.CFG file? You can add a line to WATTCP.CFG using the PRINT directive. So create a WATTCP.CFG file which contains only the following line: PRINT = James WATTCP.CFG file has been accessed Or whatever text you want. When you run either NTOOL or LYNX if you see this line printed out during initialization then you know that your config file and not that of some evil genius, has been accessed. I added the print line, and when I ran ntool it displayed the print statement and then bootp/dhcp failed WATTCP will access one and only one config file. First it looks at the environment variable WATTCP.CFG which represents a directory (not a file name!) if this environment variable does not exist it uses the current directory. It looks first for the file name WATTCP.CFG and if not found for the file name TCP.CFG. I have under the set command set wattcp.cfg=c:\fdos\bin so should that be a directory? I have been assuming that is a file? Ntool is seeing it because it printed the line I used in the print statement? Maybe why dhcp is working through dhcp is because it is using tcp.cfg. Because dhcp is working now when I run it through mTCP. I just ran it again and now it isn't working. I do have dhcp set up to run a trace maybe someone would like to look at it? I recommend playing around with different config files using the PRINT directive to completely understand which file the applications will access. You could have one file in directory c:\tmp with PRINT = config file in TMP and another file in C:\BIN with PRINT = config file in BIN and try to access these files by being in the current directory and using the WATTCP.CFG environment variable. In any case your applications will access one and only one WATTCP.CFG file (unless that config file has the INCLUDE directive). So that will eliminate a mystery config file setting some strange IP address and get you to the point where you completely understand which config file is being used. Regarding DHCP not working anymore that sounds like an incorrect packet driver for your VM or a setting on the VM or a virtual bridge misconfiguration. -Original Message- From: James Collins james.collin...@yahoo.com To: freedos-user freedos-user@lists.sourceforge.net Sent: Sat, Mar 19, 2011 11:15 am Subject: Re: [Freedos-user] ntool help hello, I reinstalled freedos to get a fresh start. I just now have been fooling around with ntool and mTCP. just now I got dhcp under mTCP to work. but now it isn't working. I can't get ntool to work either? when I run dhcp through mTCP I get an error: failure to get dhcp address. check your cabling and packet driver settings. I have tcp.cfg, edited and I have the packet driver that I need. and the packet driver is loaded via autoexec.bat. and I just got dhcp to work. when I run ntool I get bootp/dhcp failed. like I said I reinstalled freedos, one reason I did reinstall was to try to figure anything about wattcp.cfg. as far as I know I have wattcp.cfg in c:\fdos\bin\wattcp.cfg I edited wattcp.cfg to just have the line my_ip=dhcp when I run ntool and it fails, I then look at wattcp.cfg and it is empty? like the my_ip=dhcp is gone. mtcp's dhcp doesn't do this. I just renamed wattcp.cfg to wattold.cfg and ran ntool again it ran without any error and wrote nothing to the screen. this makes me think that these programs are like you said getting a fixed ip somewhere. but I am not sure. like I said I reinstalled freedos. any help would be appreciated Sent from my iPhone On Mar 17, 2011, at 6:20 PM, Willi Wasser wiw...@web.de wrote: i just tried to run ntool and i got back an ip address of: MY_IP=0.0.0.0 NTOOL is a WATTCP application itself, one that is linked to a relatively recent version of the WATTCP library that does support dhcp properly. That means, it will try to get its ip parameters from dhcp if the WATTCP.CFG file it finds at program start tells it to do so by specifying MY_IP=DHCP or if it doesn't find a WATTCP.CFG file at all. In this case it will write something like Configuring through BOOTP/DHCP to the screen. If on the other hand it finds
Re: [Freedos-user] ntool help
My advice ... Your problem reports are confusing. You say that something is not working, but it had been working before. If that is the case, what are you changing? If you can't remember what you changed then it is time to slow down and take some notes. The general method for getting a DHCP address is: [1] Load the packet driver. Check the packet driver messages to ensure that it actually loaded and that it found the Ethernet card. It should report the MAC address of the Ethernet card and any IO port or IRQ settings that it is using. [2] Wait a few seconds. Sometimes the cards take a few seconds to initialize. If you are using a batch file that loads the packet driver and then runs the DHCP client this is very important. (Probably not as important if you are on VirtualBox or some other machine emulator.) [3] Run the DHCP client. In the case of mTCP that program is DHCP.EXE. WATTCP varies, but NTOOL is a nice, self contained solution that has been discussed here in detail. If the packet driver is not loaded the DHCP client will probably tell you that it could not find the packet driver in memory. If the packet driver is found the DHCP client will send a DHCP request to your cable modem, DSL modem, or whatever DHCP server device is on your network. That request can fail because of packet loss or timeout - if it fails, try it again. Things you can do to help you debug: [1] Run with a minimum amount of 'stuff' in your CONFIG.SYS and AUTOEXEC.BAT files until you figure out a combination of steps that works correctly every time. You might be loading a device driver or program that is causing problems. [2] Make sure your network cabling is good and well connected. I have had cables go bad before. Substitute known good cables if you are in doubt. Read the lights on your Ethernet adapter and understand what they mean. Do the same on the router or switch that it is connected to. [3] Check the lights on your router or switch when the DHCP client is running. Packets will cause the lights to blink. [4] Check the DHCP server logs if you can. And lastly, I already mentioned that all of the mTCP applications include a debug trace that you can turn on. Read the DEBUG.TXT file for instructions on how to turn it on. 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
Re: [Freedos-user] ntool help
How do I load the packet driver manually? I have been running autoxec.bat via reboot to load the packet driver. Sent from my iPhone On Mar 19, 2011, at 3:09 PM, Willi Wasser wiw...@web.de wrote: If NTOOL tells you bootp/dhcp failed it means exactly what it says. But this can have two different reasons. Either your packet driver is OK, but no dhcp server answered NTOOL's request. In this case there must be a problem with the dhcp server. Or your packet driver did not load properly, possibly because it is misconfigured or invoked with incorrect parameters. Watch carefully the messages the packet driver issues while loading. Sometimes it helps in debugging to load the packet driver manually as it is easier this way to read all the messages. Usually the packet driver reports the ehternet address of the card it found. Does it look reasonable? And mTCP's DHCP message failure to get dhcp address. check your cabling and packet driver settings means the very same thing. If you failed to load the packet driver completely, then NTOOL would tell you NO PACKET DRIVER FOUND while mTCP's DHCP would write Could not access packet driver. ___ 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 -- 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
Re: [Freedos-user] ntool help
How do I load the packet driver manually? I have been running autoxec.bat via reboot to load the packet driver. You may need to step back and try reading up a little on DOS. If you don't understand what a batch file is or how to run commands from a given batch file manually you will find life much less frustrating if you study a little and get familiar. In any case in autoexec.bat there will be a line which loads the packet driver. This like will look like RTSPKT 0x60 or maybe PCNTPK int=0x60 It may or may not be either of those but it will likely have an 0x60. You can execute this command manually by entering it from the DOS prompt.This 0x60 is the interrupt number on which the packet driver will be installed. Note that WATTCP applications will find this number out manually while mTCP has to have the same number written into its config file. The point of the exercise, as Mike points out, is to verify that when the packet driver is loaded that it detects a valid Ethernet MAC address. Most packet drivers will print out the detected MAC address when the driver loads. If the packet driver prints out 00:00:00:00:00:00 or FF:FF:FF:FF:FF:FF then that is not a valid MAC address and something didn't work. (ie wrong packet driver or VM set up wrong) So if the packet driver prints out something interesting with several digits that are not 0's or F's then it is highly likely that the packet driver loaded correctly. You can test this even by *not* loading it manually provided it does not scroll off your screen when you reboot. Just look for this information when you reboot the VM. So as a minimum we now know from the previous email that the file you think is the WATTCP config file is truly the config file via the PRINT statement. Once you check the MAC on the packet driver load then we know that the packet driver is (probably) OK. If this is true then the problem is not likely in DOS - it is more likely to be in your VM. You also need to understand how your VM does networking ... but that's another issue. -Original Message- From: James Collins james.collin...@yahoo.com To: freedos-user freedos-user@lists.sourceforge.net Sent: Sat, Mar 19, 2011 2:43 pm Subject: Re: [Freedos-user] ntool help How do I load the packet driver manually? I have been running autoxec.bat via reboot to load the packet driver. Sent from my iPhone On Mar 19, 2011, at 3:09 PM, Willi Wasser wiw...@web.de wrote: If NTOOL tells you bootp/dhcp failed it means exactly what it says. But this can have two different reasons. Either your packet driver is OK, but no dhcp server answered NTOOL's request. In this case there must be a problem with the dhcp server. Or your packet driver did not load properly, possibly because it is misconfigured or invoked with incorrect parameters. Watch carefully the messages the packet driver issues while loading. Sometimes it helps in debugging to load the packet driver manually as it is easier this way to read all the messages. Usually the packet driver reports the ehternet address of the card it found. Does it look reasonable? And mTCP's DHCP message failure to get dhcp address. check your cabling and packet driver settings means the very same thing. If you failed to load the packet driver completely, then NTOOL would tell you NO PACKET DRIVER FOUND while mTCP's DHCP would write Could not access packet driver. ___ 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 -- 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 -- 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
Re: [Freedos-user] ntool help
Note that WATTCP applications will find this number out manually while mTCP has to have the same number written into its config file. Note that manually should be automatically in the above. -Original Message- From: cordata02 cordat...@aol.com To: freedos-user freedos-user@lists.sourceforge.net Sent: Sat, Mar 19, 2011 3:30 pm Subject: Re: [Freedos-user] ntool help How do I load the packet driver manually? I have been running autoxec.bat via reboot to load the packet driver. You may need to step back and try reading up a little on DOS. If you don't understand what a batch file is or how to run commands from a given batch file manually you will find life much less frustrating if you study a little and get familiar. In any case in autoexec.bat there will be a line which loads the packet driver. This like will look like RTSPKT 0x60 or maybe PCNTPK int=0x60 It may or may not be either of those but it will likely have an 0x60. You can execute this command manually by entering it from the DOS prompt.This 0x60 is the interrupt number on which the packet driver will be installed. Note that WATTCP applications will find this number out manually while mTCP has to have the same number written into its config file. The point of the exercise, as Mike points out, is to verify that when the packet driver is loaded that it detects a valid Ethernet MAC address. Most packet drivers will print out the detected MAC address when the driver loads. If the packet driver prints out 00:00:00:00:00:00 or FF:FF:FF:FF:FF:FF then that is not a valid MAC address and something didn't work. (ie wrong packet driver or VM set up wrong) So if the packet driver prints out something interesting with several digits that are not 0's or F's then it is highly likely that the packet driver loaded correctly. You can test this even by *not* loading it manually provided it does not scroll off your screen when you reboot. Just look for this information when you reboot the VM. So as a minimum we now know from the previous email that the file you think is the WATTCP config file is truly the config file via the PRINT statement. Once you check the MAC on the packet driver load then we know that the packet driver is (probably) OK. If this is true then the problem is not likely in DOS - it is more likely to be in your VM. You also need to understand how your VM does networking ... but that's another issue. -Original Message- From: James Collins james.collin...@yahoo.com To: freedos-user freedos-user@lists.sourceforge.net Sent: Sat, Mar 19, 2011 2:43 pm Subject: Re: [Freedos-user] ntool help How do I load the packet driver manually? I have been running autoxec.bat via reboot to load the packet driver. Sent from my iPhone On Mar 19, 2011, at 3:09 PM, Willi Wasser wiw...@web.de wrote: If NTOOL tells you bootp/dhcp failed it means exactly what it says. But this can have two different reasons. Either your packet driver is OK, but no dhcp server answered NTOOL's request. In this case there must be a problem with the dhcp server. Or your packet driver did not load properly, possibly because it is misconfigured or invoked with incorrect parameters. Watch carefully the messages the packet driver issues while loading. Sometimes it helps in debugging to load the packet driver manually as it is easier this way to read all the messages. Usually the packet driver reports the ehternet address of the card it found. Does it look reasonable? And mTCP's DHCP message failure to get dhcp address. check your cabling and packet driver settings means the very same thing. If you failed to load the packet driver completely, then NTOOL would tell you NO PACKET DRIVER FOUND while mTCP's DHCP would write Could not access packet driver. ___ 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 -- 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
Re: [Freedos-user] ntool help
I downloaded VirtualBox and got FreeDOS running on it with networking (WATTCP clients) using a Windows host. (Sorry, no macs here) It looks like a correct packet driver is in fact PCNTPK.COM, so check if that is in your autoexec.bat file. I also tested and verified that it is possible to load this driver twice on two different interrupts and things get screwed up pretty bad. So it would be good to somehow get a clean AUTOEXEC.BAT with no packet drivers in it, then install the packet driver via PCNTPK INT=0x60 and test. You can also use the command MEM /U to show you if the packet driver is loaded and perhaps multiple drivers or multiple copies of the same driver. -- 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
Re: [Freedos-user] ntool help
From: Willi Wasser wiw...@web.de To: freedos-user@lists.sourceforge.net Sent: Wed, March 16, 2011 4:12:27 PM Subject: Re: [Freedos-user] ntool help hello, I want to use ntool to redirect output of dhcp to wattcp.cfg. I am confused by the -g command line option. what does str mean? does anyone know what I would enter, using ntool to redirect output of dhcp to wattcp.cfh? The short answer is: NTOOL -gWATTCP.CFG Use one (or more) space characters enclosed in a pair of quotatation marks for str. This would give you something like: MY_IP=192.168.1.1 NETMASK=255.255.255.0 GATEWAY=192.168.1.254 NAMESERVER=192.76.23.54 i just tried to run ntool and i got back an ip address of: MY_IP=0.0.0.0 i am trying to run lynx, and when i try to start lynx i get an error saying all attempts at getting an ip address have failed. the ntool command i used was ntool -gC:\FDOS\LYNX\WATTCP.CFG i have typed out the wattcp.cfg file after running ntool and it says my ip as alll zeroes. another question, when using ntool to get info for wattcp.cfg i first am running ntool with the -g command line option, then i use the set command to set wattcp.cfg to where i had ntool redirect the info to, and then i try to start lynx. i am just wondering, in regards to my info should that work, i was thinking like you suggested of somehow writing some batch files if i could get lynx up and running. but i havent been able to start it yet. btw i used mTCP to get my network info. and that seems to be working. thanks for the help. which is exactly what you need as a (minimal) WATTCP.CFG file. If you need a more sohisticated WATTCP.CFG set-up, you could write a second file (say WATTCP0.CFG), that holds all those entries not provided by NTOOL. e.g. like this: TXBUFSIZE=8196 RXBUFSIZE=8196 PRINTER1NAME=LPT1 you would then add some lines like the following ones to your start-up batch file: NTOOL -g WATTCP.CFG TYPE WATTCP0.CFG WATTCP.CFG please observe the double chevrons in the second line, they cause the content of the second file to be appended to the first one. Otherwise you would just clobber it. Now, what is the purpose of str at all? The long answer is: It gives you more flexibility. If it is anything but a string that consists only of blanks, then str will be prepended to each line of NTOOL's output. If you try e.g. NTOOL -g SET (mind the space between the T and the closing quotation mark) then you would get something like this: SET MY_IP=192.168.1.1 SET NETMASK=255.255.255.0 SET GATEWAY=192.168.1.254 SET NAMESERVER=192.76.23.54 re-directing this into a batch file and then calling that (secondary) batchfile from the primary one like this: NTOOL -g SETSETPARM.BAT @CALL SETPARM.BAT will cause environment variables to be set with the respective values. These variables can then be further processed (used) in many ways. Or you try NTOOL -g ECHO IPCONFIG.BAT which would mimic the IPCONFIG commmand known from other TCP/IP implementations. The reason for the somewhat confusing character of str is that the routine within NTOOL that parses the command line only supports command line switches (like -g) that have either allways an argument or never. Optional arguments are not supported. Therefore the dummy string is required, even if you actually don't want to prepend anything. But i think, this is just an inconvenience, not a real problem. BTW, do you know the meaning of the acronym RTFM? :-) no. maybe rich text something? i dont know? ___ Schon gehört? WEB.DE hat einen genialen Phishing-Filter in die Toolbar eingebaut! http://produkte.web.de/go/toolbar -- 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 -- 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
Re: [Freedos-user] ntool help
i just tried to run ntool and i got back an ip address of: MY_IP=0.0.0.0 NTOOL is a WATTCP application itself, one that is linked to a relatively recent version of the WATTCP library that does support dhcp properly. That means, it will try to get its ip parameters from dhcp if the WATTCP.CFG file it finds at program start tells it to do so by specifying MY_IP=DHCP or if it doesn't find a WATTCP.CFG file at all. In this case it will write something like Configuring through BOOTP/DHCP to the screen. If on the other hand it finds a WATTCP.CFG file that defines a static ip address, then it will simply accept this setting, assuming that you know what you are doing. Nevertheless NTOOL -g will output the actual ip parameters that are in effect in this moment. So if NTOOL just tells you MY_IP=0.0.0.0 without any message about using dhcp, then you probably have a WATTCP.CFG file somwhere which defined that address. Probably you just copied that file from somewhere and failed to adjust it to your personal needs. Try to find that file and make it invisible to the program, by re-naming it or by deleting it completely. If that helps, you could even try whether you need NTOOL (or any other external dhcp client) at all. Perhaps lynx just has the very same problem? If the lynx version you use, is also linked to a more recent version of WATTCP, then it could do this all by itself. It not, you could still use NTOOL. ___ 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
Re: [Freedos-user] ntool help
hello, I want to use ntool to redirect output of dhcp to wattcp.cfg. I am confused by the -g command line option. what does str mean? does anyone know what I would enter, using ntool to redirect output of dhcp to wattcp.cfh? The short answer is: NTOOL -gWATTCP.CFG Use one (or more) space characters enclosed in a pair of quotatation marks for str. This would give you something like: MY_IP=192.168.1.1 NETMASK=255.255.255.0 GATEWAY=192.168.1.254 NAMESERVER=192.76.23.54 which is exactly what you need as a (minimal) WATTCP.CFG file. If you need a more sohisticated WATTCP.CFG set-up, you could write a second file (say WATTCP0.CFG), that holds all those entries not provided by NTOOL. e.g. like this: TXBUFSIZE=8196 RXBUFSIZE=8196 PRINTER1NAME=LPT1 you would then add some lines like the following ones to your start-up batch file: NTOOL -g WATTCP.CFG TYPE WATTCP0.CFG WATTCP.CFG please observe the double chevrons in the second line, they cause the content of the second file to be appended to the first one. Otherwise you would just clobber it. Now, what is the purpose of str at all? The long answer is: It gives you more flexibility. If it is anything but a string that consists only of blanks, then str will be prepended to each line of NTOOL's output. If you try e.g. NTOOL -g SET (mind the space between the T and the closing quotation mark) then you would get something like this: SET MY_IP=192.168.1.1 SET NETMASK=255.255.255.0 SET GATEWAY=192.168.1.254 SET NAMESERVER=192.76.23.54 re-directing this into a batch file and then calling that (secondary) batchfile from the primary one like this: NTOOL -g SETSETPARM.BAT @CALL SETPARM.BAT will cause environment variables to be set with the respective values. These variables can then be further processed (used) in many ways. Or you try NTOOL -g ECHO IPCONFIG.BAT which would mimic the IPCONFIG commmand known from other TCP/IP implementations. The reason for the somewhat confusing character of str is that the routine within NTOOL that parses the command line only supports command line switches (like -g) that have either allways an argument or never. Optional arguments are not supported. Therefore the dummy string is required, even if you actually don't want to prepend anything. But i think, this is just an inconvenience, not a real problem. BTW, do you know the meaning of the acronym RTFM? :-) ___ Schon gehört? WEB.DE hat einen genialen Phishing-Filter in die Toolbar eingebaut! http://produkte.web.de/go/toolbar -- 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
[Freedos-user] ntool help
hello, I want to use ntool to redirect output of dhcp to wattcp.cfg. I am confused by the -g command line option. what does str mean? does anyone know what I would enter, using ntool to redirect output of dhcp to wattcp.cfh? Sent from my iPhone -- 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
