>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
_______________________________________________
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
