DOS ain't dead

Juan Manuel Guerrero released this port on 12 November 2021.

Summary of ANNOUNCE: DJGPP port of Lynx 2.9.0dev.10 uploaded.

* LFN support
* default code page: cp850 (instead of iso-8859-1)
* supports HOME environment variable
* with BZIP2, ZIP and PDCURSES support
* without NLS (Native Language Support) support enabled
* with IDN (Internationalized Domain Names) support
* with OPENSSL support (requires WATT-32, which requires a DOS packet driver)

Excerpt:
   Lynx is a fully-featured World Wide Web (WWW) client for users running
   cursor-addressable, character-cell display devices such as vt100 terminals
   and 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.
   =======================
   This port is based on the current develop code of lynx (aka lynx2.9.0dev.10)
   available as:
     https://invisible-mirror.net/archives/lynx/tarballs/lynx-cur.tar.bz2

   ...

   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.

   Please note that lynx does _NOT_ support javascr*** at all.  So nothing will
   work that requires this feature.  If you need this, look for a different
   text web browser.

   It is important to realize that this port is a _PURE_ DOS port.  If for some
   reason you want to use lynx under Windows, you should download a windows
   port of lynx.

   ...

   When connecting to a site via https, lynx will require that a file of
   trusted certificates is available.  It is your's responsability to create
   such a file and the port will _NEVER_ provide one.  This .PEM file is
   created using openssl tools.  Read the openssl documentation.  A working
   linux installation provides always one.  It may be found by the name
   "ca-bundle.pem" or similar.  In the end it must be a file in PEM format.
   Store it where you like and point to it by setting the corresponding lynx
   environment variable like this:
     set SSL_CERT_FILE=/dev/env/DJDIR/share/ssl/certs/ca-bundle.pem
   Of course the value propossed is arbitrary and reflects the way I do it
   for my own installation of lynx.  A starting point for reading about how
   to create your own PEM files is:
     https://lists.gnu.org/archive/html/lynx-dev/2002-12/msg00043.html

---
Forum admin

I spent some time searching for direct download links as they weren't linked in the announcement. Here they are:

Binaries:
http://ftp.delorie.com/pub/djgpp/current/v2tk/lx290d10b.zip

Development libraries and headers:
http://ftp.delorie.com/pub/djgpp/current/v2tk/lx290d10d.zip

Source code:
http://ftp.delorie.com/pub/djgpp/current/v2tk/lx290d10b.zip

I also tried accessing FTP server directly, but the anonymous login didn't work for some reason.

The links have been changed. The original links were 9.3 instead of 8.3. The new links are here:

Binaries:
http://ftp.delorie.com/pub/djgpp/current/v2tk/l290d10b.zip

Development libraries and headers:
http://ftp.delorie.com/pub/djgpp/current/v2tk/l290d10d.zip

Source code:
http://ftp.delorie.com/pub/djgpp/current/v2tk/l290d10b.zip

In May 2026 was released Lynx 2.9.3
It was mentioned in the DOS community but the DOS binary was not available.
Few days ago I found and downloaded the Lynx 2.9.3 package from one of the GitHub forks (I do not remember the URL, because I did it more or less accidentaly on one of the computers in my work)
However now I realized that it contains the awaited DOS/DJGPP binary.
I uploaded the binary here
(only temporary, after few months I'll delete it)

---
DOS-u-akbar!