Hi Liam, > There is no modern browser for DOS -- but more to the point, there > never will be.
There is for example Dillo, which is not bad, but graphical: https://sourceforge.net/projects/fltk-dos/ > A DOS app can be a maximum of about 620-630k of memory. This is not true for apps which use DOS extenders. Those can use several gigabytes of memory. There even are some proof of concept extenders which let you use more than 4 GB of RAM. You can use text oriented browsers such as LYNX, LINKS, W3M, ELINKS and similar. The problem often is that they do not support javascript or modern HTTPS protocols. > There is no wireless LAN support for DOS that I know of. Only some ancient PCMCIA WiFi cards have DOS drivers, but you can use an external bridge box to connect to your WiFi by LAN cable. You could of course also use Linux, which also has some screen reader and Braille friendly distros, but as the question is about DOS, the real question is which text oriented DOS web browser supports tunein.com As expected, it relies heavily on javascript, but you could probably write a parser to extract the actual stream locations. I believe such things have been done as Arachne plugins for youtube, but they are chronically outdated, which probably makes them non-functioning on current youtube? Arachne is a graphical web browser for DOS. https://tunein.com/radio/home/ According to https://www.ssllabs.com/ssltest/ about tunein.com, the site does not support SSL 2 or 3 any more (which is good, those are old and insecure) but it supports TLS 1.0 to 1.2, although sites SHOULD not support TLS 1.0 or 1.1 (also too old) and SHOULD have support for TLS 1.3 already. Supported modern ciphers‌: ECDHE RSA with AES256 or AES128 GCM, ECDHE + CHACHA20 POLY1305, all with either SHA256 or SHA384. Supported outdated cipher components: AES128 or AES256 CBC, RSA without ECDHE. The site would use TLS 1.0 on the following old software: Android 2.3 to 4.3, Baidu 2015, (MSIE 7 to 10 on old Windows: Firefox or Chrome on Windows XP would already use TLS 1.2), Java 6 or 7, any OPENSSL 0.9 based software, Safari 5 and some 6. So a browser for DOS which wants to be able to use the site at all via HTTPS will have to use OPENSSL 1.0 or newer or another SSL/TLS library which supports at least TLS 1.0 but preferably TLS 1.2 or even TLS 1.3 to be future-proof. Can some DOS browser users here tell me how modern the HTTPS compatibility of their preferred DOS web browsers is at the moment? Note that "Retrozilla" can give you TLS 1.2 HTTPS and HTML5 even on ancient Windows 98, 95 and NT (!) based on a fork of SeaMonkey 1.1.19, but even that is not modern enough in terms of multimedia codecs and javascript compatibility to view Youtube clips. Regards, Eric _______________________________________________ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
