If you are setting up lynx for DOS for the first time, please see the separate file "FIRSTIME.TXT". If updating from a previous version, note that this version is compiled with "Color Styles". You will need to configure a file called "lynx.lss", specifying how different html directives will be displayed. Please see the sample lynx.lss file in the package and the other ".lss" files in the SAMPLES directory. This is version 2.8.5rel.1 of lynx ported to DOS. This version runs in DOS and requires a 386 or higher and some sort of packet driver. If you have a network card installed, use the packet driver specific for that card. If using a dialup connection, use a ppp packet driver that simulates a network card. One ppp packet driver that is known to work is dosppp. The 0.6 pre-beta version is available from: "http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/net/dosppp/dosppp06.zip" "http://www.ncf.carleton.ca/ncf/pda/computer/dos/net/dosppp06.zip" "http://mvmpc200.ciw.uni-karlsruhe.de/~mvmpc9/user/TONI/dosppp/dosppp06.zip" For help in setting up dosppp on your system, see the setup program developed by Alfredo Cole, available at: "ftp://ftp.oldskool.org/pub/tvdog/internet/setup.zip" Sample configuration files MYPPP.CFG and CHAT.SCR are included. Be sure to customize them for your system. Another ppp packet driver that has been used by some is LSppp. You can get it at: "http://members.tripod.com/~ladsoft/lsppp/" If you just want to run lynx on local files (e.g. to read the help files), you can run nullpkt.com (usage: "nullpkt 0x60", to unload from memory: "nullpkt -u"). Don't use this for internet connections. You can't use bootp for my_ip in WATTCP.CFG when trying to read local files with nullpkt. See the sample batch file, LYNXLOCA.BAT, for an example of how to do this. Like all DJGPP programs, lynx is a protected mode program and needs a protected mode interface. You may need to place CWSDPMI.EXE in your path. Math coprocessor emulation (387) is built into the executable and should be used automatically if you don't have a math coprocessor. On occasion, you may need to set "387=N" in your environment to make this function. Proxies or external applications can be used if you wish to set them up and configure them. To use external applications, list them at the end of lynx.cfg (at "EXTERNAL"). To activate the external application for a link, place the cursor at the link and press ".", rather than or . Similarly, "," activates the external application for the current page. Your mileage may vary. If you always want to use the external application, this can also be set in lynx.cfg, so that the external application will run when you press or . To use proxies, enter the proxy address in the proxy section of lynx.cfg. Don't forget to enter the paths for your local copies of the STARTFILE and HELPFILE in LYNX.CFG. To use telnet, you need a file in your path "telnet.bat", which calls a program such as MSKERMIT or CUTCP, which can do telnet. The appropriate initialization files need to be configured for your IP address, nameserver, etc. For MSKERMIT, this is the file MSCUSTOM.INI. For CUTCP it is CONFIG.TEL. Note that MSKERMIT will not work with epppd.exe from dosppp05.zip, but will work with the version in dosppp06.zip. It will work with pppd.exe from dosppp05.zip. The current mskermit version is 3.15. It is distributed as an update file to be unzipped on top of version 3.14. You can get it from "http://www.columbia.edu/kermit/mskorder.html" "ftp://kermit.columbia.edu/kermit/archives/msvibm.zip" (version 3.14) "ftp://kermit.columbia.edu/kermit/archives/msk315.zip" The final version of mskermit 3.16 is available from: "ftp://netlab1.usu.edu/pub/kermit" CUTCP which can also interface with tn3270, is available from "ftp://ftp.cc.umanitoba.ca/software/pc_network/cutcp-b.zip" To be able to send email from lynx you must create a directory for your mail-sending files. In general it should NOT be in your PATH. Put TCPPORT.EXE, X_MAILN.EXE, and MAIL.CFG in that directory. Put WATTCP.MAI there also, then rename it to WATTCP.CFG. Create a directory under the mail-sending directory called "spool". Put SENDMAIL.BAT in your path. MV.EXE is used for changing bookmark files. It should be in your PATH. CP.EXE should no longer be needed to copy files from your temp directory to their final path, but is used by the SENDMAIL batch file. Pushdir and popdir are used in several of the batch files. These can be commented out, or you can use the pushdir/popdir utilities of your choice. If you use a TSR pushdir, be sure to put it in your memory before running lynx, so as to avoid memory conflicts when you try to close lynx. If you use the batch-file pushdir, be sure to change "pushdir" to "call pushdir" and do the same for popdir. TSR pushdir/popdir utilities used to be available from PC Magazine as v5n10.zip. They are no longer readily available, as PC Magazine has requested that they be removed from the archive sites, but a search may find a copy. Non-TSR utilities can be obtained from garbo as tsbat79b.zip. "ftp://garbo.uwasa.fi/pc/ts/tsbat79b.zip" For mouse function with lynx, you must have a DOS mouse driver loaded and run the TSR "mousekeys" before running lynx. See lynxbat.bat for suggested parameters to use with mousekeys. With these parameters, the left key acts as "ENTER" and the right key acts as "LEFT ARROW". Mousekeys can be obtained from simtel or the author's site as: "ftp://ftp.simtel.net/pub/simtelnet/msdos/mouse/mousk305.zip" "ftp://members.aol.com/bretjohn/programs/mousk305.zip" Local file access looks like this: file:///c:/ file:///c:/dos file:///c:/dos/command.com file:///dev/c/dos/command.com file://localhost/c:/ file://localhost/c:/dos file://localhost/c:/dos/command.com file://localhost/dev/c/dos/command.com Here are some environment variables that should be set, usually in a batch file that runs the lynx executable. Make sure that you have enough room left in your environment. You may need to change your "SHELL=" setting in config.sys. In addition, lynx looks for a "SHELL" environment variable when shelling to DOS. If you wish to preserve the environment space when shelling, put a line like this in your AUTOEXEC.BAT file also "SET SHELL=C:\COMMAND.COM /E:4096". It should match CONFIG.SYS, which should have a line like: "SHELL=C:\COMMAND.COM /E:4096 /P" HOME Where to keep the bookmark file and personal config files. TEMP or TMP Bookmarks are kept here with no HOME. Temp files here. USER Set to your login name LYNX_CFG Set to the full path and filename for lynx.cfg LYNX_LSS Set to the full path and filename for lynx.lss WATTCP.CFG Set to the full path for the WATTCP.CFG directory PWD Set to the directory from which you are running lynx. This is the default directory in which downloaded and printed files are saved. RL_CLCOPY_CMD Command to copy a URL to a "clipboard" file RL_PASTE_CMD Command to go to a URL in your "clipboard" file SSL_CERT_FILE Set to the full path and filename for your file of trusted certificates DJDIR Set to the full path for the directory under which special files are located. See LYNXBAT.BAT for sample RL_CLCOPY_CMD and RL_PASTE_CMD commands. The default command to copy a URL to the clipboard file is "CTRL-S". The default to copy the URL from the clipboard file is "CTRL-Y". Either of these can be changed by a KEYMAP line in lynx.cfg. The file LYNXBAT.BAT is a sample batch file to run lynx and to configure kermit, cutcp, and your wattcp.cfg files using dosppp. Be sure to modify it for your pathnames and the programs that you are actually using. Note where forward slashes and backslashes are used (some paths may work with either). You must also modify SENDMAIL.BAT. This file is compiled with the wmemu library for 387 emulation. This is distributed under the GNU license. Source code can be obtained from any of the DJGPP mirror sites, such as "http://www.delorie.com/pub/djgpp/current/". Source code for cwsdpmi and redir is also available from any DJGPP mirror site. The executables gecho, cp, mv, pwd, and tee are GNU programs with source code available from any of the GNU archive mirrors such as ftp.gnu.org or the from the DJGPP mirror sites. Running the executable with the "--version" flag will tell you which package to get for the source code. To obtain lynx source code go to "http://lynx.isc.org/" by http and follow the links. The file is also compiled with the PDCurses library version 2.6 , with the zlib library, version 1.1.4 and with the bzip2 library, version 1.0.2. The copyright notice for zlib is in the file "zlib.txt" and the notice for bzip2 is in "bzip2.txt". PDCurses is in the public domain. The lynx executable is compressed with UPX version 1.22. X_MAILN.EXE comes from the UKA_PPP distribution by Karl-Heinz Weiss. UKA_PPP is free for non-commercial use. X_MAILN.EXE is specially licensed free for commercial or non-commercial use when used in conjunction with lynx. See the file UKA_PPP.TXT for more details. TCPPORT.EXE is from the WATTCP distribution by Erick Engelke. It was made available in compiled form by Karl-Heinz Weiss. This version is also compiled with openssl-0.9.7d-dev (Dec 10, 2003), enabling support for https:// URLs. In order to avoid patent problems, the idea, mdc2, and rc5 algorithms are not used. The copyright notice for openssl is in the file "openssl.txt". Because this enables strong encryption, be sure to comply with regulations of the Bureau of Export Administration if redistributing this from the US. If you are in another country, please check your laws on use and distribution of cryptography before using or redistributing this file. The source code for openssl can be obtained from "http://www.openssl.org/". In order to make a secure connection, the openssl code needs to be able to verify a certificate presented by a web site by comparison with a know "trusted" certificate. The connection is no more secure than the validity of the "trusted certificates". Be sure to obtain these from a trusted source. You can extract certificates from the database of another browser (if you believe that it has not been compromised). To extract from Internet Explorer, first update the certificate database from the Windows Update web site, then go to "Internet Options/Content/Certificates/Trusted Root Certification Authorities", select all (or those you trust), and then export as a PKCS#7 file. You can then use "openssl pkcs7" to print the certificates using the "-print_certs" and possibly the "-text" options. If you are willing to accept less security, you can get a preassembled file of trusted (by someone) certificates from a well-known web site. For example, the mod_ssl package contains a file of "trusted certificates" called ca-bundle.crt in the pkg.sslcfg directory which was extracted from Netscape Communicator (in March 2000). You can also get a set of certificates from my website ("http://www.rahul.net/dkaufman/"), but note that this is not a secure web site, so use these only if security is not very important. The default file for the file of certificates is called "cert.pem", located in the subdirectory "ssl" of your "DJDIR" directory. If you have the DJGPP development system on your computer, DJDIR is set in the environment by the DJGPP.ENV file. If you don't have DJGPP installed, you can set the DJDIR environment variable yourself. Setting DJDIR is also necessary if you want to use the alternate language files (see the file "interntl.txt"). If you don't want to set the DJDIR environment variable and place the file appropriately, you can tell lynx where to find it by setting the environment variable "SSL_CERT_FILE" to the full path and filename of the file of certificates. The default location of the lynx.cfg and lynx.lss files (if the environment variables are not set) is the "lib" directory under the directory specified in the DJDIR environment variable. Special keys, such as ALT keys and function keys can be mapped to functions in lynx.cfg with KEYMAP statements. Use the numerical value for the key found in the file PDCURSES.KEY. If you prefer screen writes via BIOS (significantly slower), set "PDCURSES_BIOS=TRUE" in your environment. This version is also compiled with EXEC_LINKS, so that local links to lynxprog: and lynxexec: URL's can be honored. This is set off by default, but can be turned on in the option menu and saved to lynx.rc. It can also be turned on in lynx.cfg by setting: LOCAL_EXECUTION_LINKS_ON_BUT_NOT_REMOTE:TRUE This version is compiled with the port of the "DIRED" code to DOS, allowing local file manipulation. This still has some bugs and may occasionally freeze the computer, requiring a reboot (occasionally seen when unzipping an archive if some of the files already exist). Renaming and moving files should work as is. Compressing and uncompressing files requires that you have the proper external programs in your path (i.e. zip, unzip, gzip, tar, compress, zcat, uudecode). Please report problems with this code to me. The dired menu is accessed by the "f" key. Internationalization is supported in this version via the "gettext" method. To use a language other than English, see the separate file, INTERNTL.TXT. If you use English as your language, you can ignore this paragraph. Support for internationalization entails a larger binary and a larger amount of memory needed to run lynx. This probably will not run well if you have less than 4 Meg of memory. For machines with 3 Meg or less of memory, consider an alternate, smaller binary with internationalization support removed. You can now frequently break out of a stuck nameserver lookup or attempted connection without exiting lynx by using the "z" key. If you need to immediately break out of a stuck lynx session, use the CTRL-C, CTRL-BREAK, or ALT-X key combinations to end the lynx session. This version is compiled with the WATT-32 tcp library, version 2.2 dev.rel.6. Debugging of packets via the WATTCP debugging code is enabled. See the enclosed sample WATTCP.CFG for details of syntax. To turn on debugging, invoke lynx with the command-line option "-wdebug". Please note that "PERSISTENT_COOKIES" (i.e., keeping cookies between sessions) is now off by default. Change this in lynx.cfg if you want to keep cookies. This version is compiled using DJGPP version 2.03 and GCC version 3.3.2. This lynx executable compiled by and the package prepared by Doug Kaufman (dkaufman@rahul.net). For questions about lynx please send email to lynx-dev@sig.net. For questions or comments about the batch files or the other content of this package send email to dkaufman@rahul.net.