This file is for first time users of the DOS port of lynx. The initial
setup may be complicated, but can be done step-by-step. I believe that
the files in this package give the most flexibility. Other packages
have an automated setup which is easier when they work, but which may
be harder to troubleshoot. If you decide to try one of the automated
setup packages, I recommend that by John Lewis, "Bobcat386". It can be
obtained from "http://www.qsl.net/ve3lgs/index.html".

This program is not for use in a DOS window under Windows. If you have
Windows 9x, WindowNT, WindowsMe, Windows2000, or WindowsXP, please get a
Windows port of lynx instead. If for some reason, you need to run this
in a DOS box under Windows, you will need to install Dan Lanciani's
virtual packet driver "ndis3pkt", which can be obtained from his web
site "http://www.danlan.com/".

In order to decrease the size of the package for those updating
from a previous installation, not all necessary files are in this
package. Lynx works over either a direct network connection or
a PPP or SLIP connection. If you have a network card installed,
you will need a DOS packet driver for it. This may be obtained
from the card manufacturer or from one of the archives of
packet drivers (such as "ftp://ftp.crynwr.com/drivers" or
"ftp://kermit.columbia.edu/pub/packet-drivers"). If you don't have a
network connection, you need software to dial your ISP and make a PPP
or SLIP connection. Most have had good luck with the DOSPPP packeage
by Antonio Lopez. Make sure to get the 0.6 version. See README.DOS
for locations. Note that you must configure this, depending on the
authentication methods and login procedures at your ISP. The KLOS driver
is also known to work well with lynx. It is not free (but is very
inexpensive), and is complicated to set up.

The lynx executable itself handles http:, https:, ftp:, file:, news:,
nntp:, and gopher: protocols. You will need external programs if you
want to access telnet:, tn3270:, or mailto: URLs. I would suggest
getting lynx, itself, working first before adding the external protocol
support.

Various environment variables need to be set before running the lynx
executable. You need to be sure that you have enough environmment
space to hold these variables. This can be accomplished by modifying
your CONFIG.SYS file. See README.DOS for details. The sample file
"LYNXBAT.BAT" sets the environment variables and runs lynx. You need to
edit it, putting in the appropriate paths for your setup. If you don't
already have a HOME variable, pick a HOME directory where lynx.cfg,
LYNX.RC, and WATTCP.CFG will reside. If you don't have CUTCP installed,
you can remove the lines relating to CUTCP and CONFIGTEL. Otherwise
set CONFIGTEL to point to your CONFIG.TEL file. The MOUSKEYS program
allows use of the mouse for lynx. You must have a mouse driver installed
first. If you don't need mouse support, just remove the lines related
to MOUSKEYS. The files GECHO.EXE, REDIR.EXE, TEE.EXE and PWD.EXE are
supplied with this package. Make sure that the path to them is correct
in LYNXBAT.BAT.

Lynx ALWAYS needs a packet driver installed, even when just browsing
local files. To browse locally, you can use the NULLPKT packet driver,
which is included in this package. The file "LYNXLOCA.BAT" shows how to
run lynx for local browsing. Note that MYIP and NETMASK must be set.

Like all DJGPP programs, lynx needs a DOS protected mode interface. This
is provided by the enclosed CWSDPMI program. Put it in a directory in
your path. You do not have to run it - it runs automatically when you
run lynx.

If you have a network set up, I will presume that you know how to
install the packet driver. For those doing dial-up, DOSPPP can dial, log
in, then establish the PPP connection. Sample MYPPP.CFG and CHAT.SCR
files are provided. These must be customized with the phone number of
your ISP, your user name, and password. If your ISP supports CHAP or PAP
authentication, put your username and password in MYPPP.CFG and use the
CHAT1.SCR file. If you need to login through a script, put the login
name and password in CHAT.SCR. Be sure to use the modem initialization
string appropriate to your modem and your ISP's phone number in the
CHAT.SCR file. If you use the CHAT1.SCR file, be sure to rename it to
CHAT.SCR or edit MYPPP.CFG to reflect the name of the file. Further
details are in the PPPD.MAN and CHAT.MAN files, included with the DOSPPP
package.

In addition to the packet driver, lynx needs the WATTCP.CFG and the
LYNX.CFG files in order to function. The WATTCP.CFG file needs to be
customized with the IP address(es) of your nameserver(s). You shouldn't
have to change any other settings in that file initially. LYNX.CFG
controls how lynx functions and contains lots of information about
how lynx works. You will want to read through the file once you get
lynx going, to see how to modify it to your taste. Initially, you
should edit the STARTFILE and HELPFILE lines. I would advise using
a local STARTFILE and the local help files. Note that local files
can be addressed either as "file://localhost/c:/path/filename" or as
"file://localhost/dev/c/path/filename". These both point to the file
at C:\path\filename. Don't use backslashes when entering the paths in
LYNX.CFG.

Once you have lynx working, you should go to the options page and set
the basic options the way you want. If you check the box to save to
file, lynx will write a "LYNX.RC" file in your HOME directory. To get to
the options page, type "O" from within lynx.

Further information about lynx can be found in the LYNX USERS GUIDE and
the other help files. Type "H" from within lynx to access this.

When you are ready to set up telnet: URLs, I suggest using MSKERMIT
as your telnet program. CUTCP is an alternative. See the sample
MSCUSTOM.INI file to use with MSKERMIT. Note that you need to customize
this with your nameserver IP addresses. This file is set to use the
MYIP, REMIP, and NETMASK environment variables set by DOSPPP when
IP-UP.BAT is run. MSKERMIT does not use the WATTCP.CFG file. If you
decide to also use MSKERMIT to dial out directly through your modem, you
will need to set port, speed, and modem type.
