Re: LYNX-DEV More patches for ac-0.98

[Doug Kaufman]

On Mon, 15 Dec 1997, Nelson Henry Eric wrote:

> > I have revised a README.DOS file, originally  written by Wayne, aimed at
> > the user of a precompiled DOS binary.  Does anyone think that such a
> > file belongs in the general distribution?  If so, I can post it for review
> 
> Yes, it would be welcome in the /docs subdirectory.  It needs to be bundled
> up with the lynx.exe file to be really useful, however.  Anyone working on

The following is the README.DOS that I included in a binary package that
I made available to a few users. I don't know how long it will be there,
but the package is at
"ftp://ftp.rahul.net/pub/dkaufman/lynx2.7.1ac-0.98-DOS.zip";. Any
comments about the makeup of the package and ease of use for someone not
familiar with using lynx_386 would be appreciated. I put in a lynx.cfg
with some settings for a DOS machine. The text files were converted to
DOS EOL's.

                               README.DOS

This version runs in DOS and requires a 386 or higher and some sort
of packet driver. It does not work in a dos window under Windows 3.x.
One packet driver that is known to work is dosppp, available from
"http://www.simtel.net/pub/simtelnet/msdos/pktdrvr/dosppp05.zip";.
If you just want to run lynx on local files (e.g. to read the help
files), you can run slip8250.com (slip8250 0x60). This defaults to
COM1 and IRQ4. If your modem isn't on COM1, do "slip8250 -?" for
syntax information. The default will conflict with a mouse on COM1.
For a modem on COM2 this would be "slip8250 0x60 6 3 0x2f8".
Don't use this for internet connections. 

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 (available from
"http://www.simtel.net/pub/simtelnet/gnu/djgpp/v2misc/csdpmi3b.zip";).
You might also need emu387.dxe if you get Coprocessor not available.
This version doesn't work with ftp://, news://, or nntp:// URL's.
External applications can be used, however, 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
<RETURN> or <RIGHT ARROW>. Your mileage may vary. Don't forget to alter
wattcp.cfg with your TCP settings.

To use telnet, you need a file in your path "telnet.bat", which calls a
program such as MSKERMIT, that 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.

Lynx uses cp.exe to make a copy of a temp file when you download and then
choose a destination.  Don't delete it.

File access looks like this:

file:///c:/
file:///c:/dos
file:///c:/dos/command.com
file://localhost/c:/
file://localhost/c:/dos
file://localhost/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.

HOME         Where to keep the bookmark file and personal config files.
TEMP or TMP  Bookmarks are kept here with no HOME.  Temp files here.
TERM         Set TERM=vt100 to stop that annoying terminal type message.
USER         Set to your login name
LYNX_CFG     Set to the full path and filename for lynx.cfg
WATTCP.CFG   Set to the full path for the WATTCP.CFG directory
__
Doug Kaufman
Internet: address@hidden (preferred)
          address@hidden