C. Brouerius van Nidek wrote:
>
> Steven, I am planning to use it with an ethernetcard.

Do you know what kind of card it is?  To use it for DOS
you will need the correct packetdrive.  For example, if
your card is NE2000 compatible, you will need the ne2000
packetdriver (this is similar to the ne module in Linux).
If the IRQ is 10 and the IO address is 0x320, then you
install the packetdriver like this:
--------------------
ne2000 0x60 10 0x320
--------------------
This is similar to "insmod ne 0x320" in Linux.

Once the packetdriver is installed, it is ready to communicate
via TCP/IP; however, before it can do this it requires an
address and a route to the network.  In Linux, the "ifconfig"
and "route" commands are used to do this.  However, DOS does
not have any commands like these, so the address/route data
is normally set by the application.  For example, when you
configure SOSS, you define address/route and SOSS sets them
up when it runs.  Or, when you use NCSA telnet (which requires
a completely different configuration of address/route), it sets
up the connection.  This works fine as long as the application
is running, but as soon as it stops, the network connection
disappears.  The packetdriver is still functioning, but without
an address/route, it is deaf and
dumb.

> But you have to explain to me TCP/IP and NCSA.

TCP/IP is the network protocol.  It's the protocol used for
the Internet and in Linux.  Windows networking has its own
protocol (NetBUI or something like that), but it uses TCP/IP
too.  Novelle networking has it's own protocol.

NCSA is simply the name of a particular version of telnet
(for DOS).

Cheers,
Steven

To unsubscribe from SURVPC send a message to [EMAIL PROTECTED] with 
unsubscribe SURVPC in the body of the message.
Also, trim this footer from any quoted replies.
More info can be found at;
http://www.softcon.com/archives/SURVPC.html

Reply via email to