Kompx.com or Compmiscellanea.com

Web browsers for DOS

Operating systems : MS-DOS 6.0+, FreeDOS 1.0+

Arachne : Dillo : DOSLYNX : Lynx : Links : ELinks

Web browsers for DOS may be looked at as existing roughly in two categories. Web browsers which can be installed without excessive efforts + work stably within their capability. And the rest of the web browsers of functionality more or less limited or problematic.

The major web browsers for DOS include applications with GUI and text-based browsers. The graphical web browsers for DOS are several versions of Arachne - GPL version, Arachne Labs version, Ray Andrews version - and Dillo. As well as DR-WebSpyder based on Arachne and WebSpyder's variation - Lineo Embrowser. Text-based web browsers for DOS are a little bit more numerous: DOSLYNX, lynx, links, elinks.

The graphical web browsers for DOS even if being prominent among DOS web browsers for their capabilities are definitely inferior in comparison with major web browsers for Windows, Linux or Mac OS X due to the restrictions of the DOS nature, small user and developer base, some other reasons. The capabilities of the text-based web browsers for DOS differ less from the ones of text-based web browsers for other operating systems.

Arachne - / home page /

Graphical web browser for DOS ( More )

HTML, CSS1 ( More )

Arachne 1.95:

glennmcc.org

[ Image ] : Arachne - 1

Arachne 1.95:

freedos.org

[ Image ] : Arachne - 2

Arachne 1.95:

ebay.org

[ Image ] : Arachne - 3

Arachne 1.95:

wikipedia.org

[ Image ] : Arachne - 4

Arachne 1.95:

arachne.cz

[ Image ] : Arachne - 5

Arachne 1.95:

slackware.com

[ Image ] : Arachne - 6

Dillo - / home page /

Graphical web browser ported to DOS. Originally created for Linux and some other *nix systems, ported later to Windows and now DOS. There are versions for some handheld computers, for PlayStation2, Atari-based 68k-systems running MiNT, RISC OS.

HTML. CSS (?)

DOSLYNX - / home page /

Text-based web browser for DOS. Based on Lynx, but differs considerably in interface, keyboard shortcuts, the way web pages are displayed. All in all, DOSLYNX is less capable than Lynx or Links and ELinks.

HTML

DOSLYNX 0.41b:

users.ohiohills.com/fmacall

[ Image ] : DOSLYNX - 1

DOSLYNX 0.41b:

freedos.org

[ Image ] : DOSLYNX - 2

DOSLYNX 0.41b:

ebay.com

[ Image ] : DOSLYNX - 3

DOSLYNX 0.41b:

wikipedia.org

[ Image ] : DOSLYNX - 4

DOSLYNX 0.41b:

arachne.cz

[ Image ] : DOSLYNX - 5

DOSLYNX 0.41b:

slackware.com

[ Image ] : DOSLYNX - 6

Lynx - / home page /

Text-based web browser for DOS. A DOS version of one the most common web browsers with text user interface. There are ports to most various operating systems from Windows, Linux and Mac OS X to AmigaOS, OpenVMS and classic Mac OS.

HTML ( More )

Lynx 2.8.2:

lynx.isc.org

[ Image ] : Lynx - 1

Lynx 2.8.2:

freedos.org

[ Image ] : Lynx - 2

Lynx 2.8.2:

ebay.com

[ Image ] : Lynx - 3

Lynx 2.8.2:

wikipedia.org

[ Image ] : Lynx - 4

Lynx 2.8.2:

arachne.cz

[ Image ] : Lynx - 5

Lynx 2.8.2:

slackware.com

[ Image ] : Lynx - 6

Links - / home page /

Text-based web browser for DOS. A DOS version of one the most common web browsers with text user interface. There are ports to various operating systems, for instance, Windows and Linux.

HTML ( including tables and frames )

Links 2.1pre36:

jikos.cz/~mikulas/links

[ Image ] : Links - 1

Links 2.1pre36:

freedos.org

[ Image ] : Links - 2

Links 2.1pre36:

ebay.com

[ Image ] : Links - 3

Links 2.1pre36:

wikipedia.org

[ Image ] : Links - 4

Links 2.1pre36:

arachne.cz

[ Image ] : Links - 5

Links 2.1pre36:

slackware.com

[ Image ] : Links - 6

ELinks - / home page /

Text-based web browser for DOS. An enhanced version of Links. It is less common, than Lynx or Links, but it is the most capable of text-based web browsers for DOS. There are ports to various operating systems, for example, Windows and Linux.

HTML ( including tables and frames ). Meagre support for CSS

ELinks 0.13b:

elinks.cz

[ Image ] : ELinks - 1

ELinks 0.13b:

freedos.org

[ Image ] : ELinks - 2

ELinks 0.13b:

ebay.com

[ Image ] : ELinks - 3

ELinks 0.13b:

wikipedia.org

[ Image ] : ELinks - 4

ELinks 0.13b:

arachne.cz

[ Image ] : ELinks - 5

ELinks 0.13b:

slackware.com

[ Image ] : ELinks - 6

Besides major web browsers for DOS, there are others, which are by now either well outdated, or using them is accompanied by various complications, or they have been intentionally created for a limited range of task. Graphical web browsers: Webboy, SPIN and Skipper. Text-based web browsers: Bobcat, NetTamer, Minuet. Browsers for viewing off-line web pages: Knots, Open World Navigator, IntraDOS.


Aliosque subditos et thema

 

Windows console applications. Multimedia

 

MPlayer : FFmpeg Media players appeared long ago, but their heyday began with the mass spread of personal computers powerful enough to play video files. This coincided with the mass spread of operating systems and other software with graphical user interface. However, a program with a graphical user interface is dualistic in its nature: there is a code responsible for graphical user interface, for the appearance and there is a code - for performing the task the given application has been created for in the first place. Both code complexes consume system resources, their response time to user actions makes up certain amount of waiting time. And in cases or concepts when appearance is taken as less important - less important to the point of sparing or almost sparing to employ it - console applications, among others, appear. Moreover, the segmentation of the GUI and of the engine makes it easier to change the graphical user interface or perform complex automated operations. The scheme is implemented for media players for Windows as well. MPlayer, for instance, in its usual form is a console application, starting up quickly, having fast response to user actions, consuming system resources almost entirely for its immediate task. And on this basis if desired, one or another graphical interface may be added for creating, all in all, a new application. MPlayer - / home page / Console media player for Windows. Basis for SMPlayer and UMPlayer. There are versions for Linux, FreeBSD, NetBSD, OpenBSD, Apple Darwin, Mac OS X, QNX, OpenSolaris/Solaris, Irix, HP-UX, AIX, some other *nix system, BeOS, Syllable, AmigaOS, AROS, MorphOS, DOS, Windows. Supported video, audio formats, static images, subtitles, etc. ( List and More extensive list of video and audio codecs ). MPlayer: "Dead Man" MPlayer: "Sky Captain and the World of Tomorrow" MPlayer: "10,000 BC" MPlayer: "13 Tzameti" MPlayer: "The Draughtsman's Contract" MPlayer: "Balzaminov's Marriage" FFmpeg - / home page / Pack of utilities and libraries for work with video and audio files. Created in and for Linux, but there is a Windows variant. Source code may be compiled for some other operating systems. Supported file formats and codecs: ( List ). Also, VLC media player can be run in text mode, ncurses using.

HTTPS to HTTP redirect for a single page

 

Redirecting a single page with HTTPS to the page with HTTP. Server configuration: Apache + nginx. SSL is enabled for the whole web site, so all pages are served with HTTPS. But there is a need to make just one single page to be with HTTP. Directives for .htaccess file: RewriteEngine On RewriteCond %{HTTP:HTTPS} on [NV] RewriteRule ^(page\.html)$ http://%{HTTP_HOST}/$1 [R=301,L,QSA] HTTPS to HTTP redirect for a single page in detail -- Enable runtime rewriting engine RewriteEngine On -- If HTTPS is present RewriteCond %{HTTP:HTTPS} on [NV] -- Then, when a page name and extension correspond to the search group in parentheses, form for it a URI with HTTP RewriteRule ^(page\.html)$ http://%{HTTP_HOST}/$1 [R=301,L,QSA] Notes RewriteCond %{HTTP:HTTPS} on [NV] is not the only way to detect if HTTPS is present. Moreover, for some server configurations other directives may be more suitable, like RewriteCond %{SERVER_PORT} 443 for example. The point is to find out somehow if HTTPS is on. So it should probably be checked by practice what is going to work in a particular case. QSA is used to keep the existing query string, if there is any, when the replacement URI also contains a query string. So that in the end both query strings are to be combined. More on the subject: http://httpd.apache.org/docs/2.2/rewrite/flags.html#flag_qsa