L.D wrote:
>First BOOTP doesn't support DHCP; DHCP supports BOOTP ... protocol says
>it has to be backwards compatible with BOOTP.  The change(s) made must
>have been to bring BOOTP up to last standards before everything switched
>to DHCP.  Independent programs report that BOOTP was being used [not
>DHCP].

Independent programs can not see what Arachne uses AFAIK.

>IP_Address BOOTP
>;IP_Address BOOTP    ... WatTcp attepmts to use BOOTP protocol

Aha! So you do use WatTcp (as I already knew and stated).

>Note that it file itself says it is for use with Klos PPP.

I have never stated that this was the correct file to open and read.

>     If we are using Waterloo TCP, it's either invisible [not part of
>     the installation package] or has been included in its entirety
>     within Core.exe

Yes it's included in Arachne.

>#       The following are options specific to Arachne Waterloo TCP for LAN.

So it's for Arachne :)

>#       DO NOT USE THE DEFAULT VALUES OF THESE OPTIONS.
>#       Never guess IP numbers.  If you are unsure, contact you local network
>#               administrator.

So ?.?.?.? isn't a good netmask to use (255.255.255.0 is often better).
What this says is that you should not guess the numbers but ask whoever is
responsible for the connection - in your case the cable company.

>## Don't write IP address to this file, if you are using Arachne - WWW
browser
>## for DOS. Write it to ARACHNE.CFG.

So we shouldn't add the netmask (and the other IP (xxx.xxx.xxx.xxx)
adresses to this file).

But these two

>sockdelay=40
>mss=1024

Are still used by Arachne.

>Thank heavens the EtherNet Wizard made RTFM unnecessary [Well, that and
>the help I got here.]  If I'd actually had to READ [and follow what was
>written] the funny manual, I *still* wouldn't be up and running on cable.

So the information isn't easy to understand for everyone. If I had to use
the Wizard and not read these files I wouldn't have got Arachne to work in
school.

>You tryin' to get rid of me?  Just for that I will, to see what happens!

Try it in lantcp.cfg and I might succeed ;-)
//Bernie
http://bernie.arachne.cz/ DOS programs, Star Wars ...

Reply via email to