MIME-Version: 1.0
Path: h6ni15353igv.0!nntp.google.com!news.glorb.com!Xl.tags.giganews.com!border1.nntp.dca1.giganews.com!nntp.giganews.com!local2.nntp.dca.giganews.com!news.giganews.com.POSTED!not-for-mail
NNTP-Posting-Date: Fri, 02 Jan 2015 18:36:59 -0600
Message-Id: <201501030036.t030aEw1023005@delorie.com>
Date: Sat, 03 Jan 2015 01:10:01 +0100
From: Juan Manuel Guerrero <juan.g...@gmx.de>
To: djgpp-a...@delorie.com
Subject: ANNOUNCE: DJGPP port of Lynx 2.8.8 uploaded.
Precedence: bulk
Reply-To: dj...@delorie.com
Errors-To: nob...@delorie.com
Precedence: bulk
Newsgroups: comp.os.msdos.djgpp
Organization: None provided
DJ-Gateway: from mailing list dj...@delorie.com
Lines: 136
Content-Type: text/plain; charset=ISO-8859-15; format=flowed

This is a port of Lynx 2.8.8 to MSDOS/DJGPP.


   Lynx is a fully-featured World Wide Web (WWW) client for users running
   cursor-addressable, character-cell display devices such as vt100 terminals,
   vt100 emulators running on character-cell display.  It will display Hypertext
   Markup Language (HTML) documents containing links to files on the local system,
   as well as files on remote systems running http, gopher, ftp, wais, nntp,
   finger, or cso/ph/qi servers, and services accessible via logins to telnet,
   tn3270 or rlogin accounts.


   DJGPP specific changes.
   =======================

   The only DJGPP specific changes where those required to get the current version
   of lynx configured and compiled with DJGPP 2.04.  Using 204 only requires very
   little fixing but when 2.03 is used more fixes are required because the lynx
   code expects that certain headers like stdint.h and others shall be available.
   All this can certainly be fixed but I do not have neither the time nor the
   interest to do it.  DJGPP 2.03 is simply to old.  This port has been configured
   to work when installed into a DJGPP installation tree.  This means that all
   default paths to directories assume the DJDIR prefix.

   The port has been configured using the configure script provided by the source
   package.  This means that no old DJGPP specific scripts or makefiles distributed
   by the package have been used.  Most of the porting work has been invested in
   the DJGPP specific configuration scripts.

   This port has been configured to be compiled with BZIP2, ZIP and PDCURSE support.
   This means that if you want to recompile the preconfigured sources you must
   have installed the following ports:
     ftp://ftp.delorie.com/pub/djgpp/beta/v2apps/bz2-106a.zip
     ftp://ftp.delorie.com/pub/djgpp/beta/v2tk/zlib128b.zip
     ftp://ftp.delorie.com/pub/djgpp/beta/v2tk/pdcur34a.zip

   Building with stock djdev204 is no longer supported due to bugs in different
   LFN functions that makes the port useless on plain DOS together with LFN
   drivers that do not implement the full set of 0x71NN functions. Instead of
   using the libc.a provided djdev204, a libc version compiled from the repository
   code has been used.  The repository code has been patched with the memory patch
   as provided by Andris Pavenis in:
     http://ap1.pp.fi/djgpp/djdev/djgpp/20140421/use_nmalloc.diff
   The goal is to test how well the new memory system and the current libc
   code works.  The repository code can be downloaded from Martin Stromberg's
   site as:
     http://www.ludd.luth.se/~ams/djgpp/cvs/djgpp.cvs.tar.gz

   The port has been configured and compiled with NLS support enabled using
   the latest ports of libiconv and gettext:
     ftp://ftp.delorie.com/pub/djgpp/beta/v2gnu/licv114br2.zip
     ftp://ftp.delorie.com/pub/djgpp/beta/v2gnu/gtxt192b.zip
   These are DXE3 modules and _MUST_ be installed or the program will abort
   every time it is started.
   If you prefer no NLS, then reconfigure the sources passing the no-nls flag
   to the config.bat file.

   The port has been configured with OPENSSL support.  OpenSSL support requires
   installing the WATT-32 port.  The following ports have been used:
     ftp://ftp.delorie.com/pub/djgpp/beta/v2tk/ssl101jb.zip
     ftp://ftp.delorie.com/pub/djgpp/beta/v2tk/wat3222br3.zip
   No other versions have tested.  To be able to use this program compiled with
   OpenSSL and WATT-32 a noise source must be installed.  A noise source can be
   obtained as:
     http://www.rahul.net/dkaufman/noise063a2.zip

   To be able to run the program, configuration files are expected to be found
   in their canonical place.  This is the /dev/env/DJDIR/etc directory.  The
   configuration files lynx.cfg and lynx.css are stored in the /etc directory
   and reflect the conditions during the configuration and compilation process
   of this port.  You may need to adjust the entries to fit your requirements.
   To run the program, a working version of wattcp.cfg is required. This file
   is __NOT__ distributed with this port.  That file will reflect your network
   environment and hardware.  It is the user's job write one that matches his
   environment.  As a starting point you can use the one distributed with the
   WATT-32 port.  Please note that the location of wattcp.cfg must be specified
   by setting the WATTCP.CFG environment variable.  This can be done either in
   the environment, in autoexec.bat or in djgpp.env.

   To be able to run the program, a DOS packet driver (PKTDRVR) is required.
   This may be obtained from the card manufacturer or from one of the archives
   of packet drivers (such as "http://www.lanet.lv/simtel.net/msdos/pktdrvr-pre.html"
   or "http://ftp.freenet.de/pub/ftp.simtel.net/pub/simtelnet/msdos/pktdrvr/").
   Even when only browsing local files, a NULLPKT packet driver is required like
   nullpkt.zip.  The zip file can be downloaded as:
http://www.jumpjet.info/Application-Software/DOS/Hardware/2/NULLPKT/NULLPKT.zip

   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.  In this case a port of kermit may be required.

   It is important to realize that this port to be used on __PLAIN__ DOS only.
   If for some reason you think that lynx must be used under Windows, you should
   download a windows port of lynx.

   If you decide to use this port as stand alone program then you __MUST__
   set at least the following environment variables to point to the required
   configuration files:
     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
     SSL_CERT_FILE Set to the full path and filename for your file of trusted
                   certificates
   There is a batch file stored in the /share/lynx_doc/samples directory that
   shows how to run lynx as a stand alone application.

   Please note that I am neither a lynx user nor a DJGPP/DOS network expert.
   This port shall only be a test for the OpenSSL and WATT-32 ports.

   As usual, all djgpp specific files (config.bat, diffs, readme files, etc.)
   are located in the /djgpp directory.

   Please read the docs very __CAREFULLY__ to become familiar with the product.



   The port has been compiled using a libc.a version compiled from current
   repository code and patched with the new malloc code.  This package is
   available at ftp.delorie.com and mirrors as (times tamp 2015-01-02):

     Lynx 2.8.8 binaries, scripts and man format documentation:
     ftp://ftp.delorie.com/pub/djgpp/beta/v2tk/lynx288b.zip

     Lynx 2.8.8 source:
     ftp://ftp.delorie.com/pub/djgpp/beta/v2tk/lynx288s.zip


   Send lynx utils specific bug reports to <lynx...@nongnu.org>.
   Send suggestions and bug reports concerning the DJGPP port to
   comp.os.msdos.djgpp or <dj...@delorie.com>.


Enjoy.

         Guerrero, Juan Manuel <juan.g...@gmx.de>