DOS ain't dead

After many request a new version of links with js enabled it's out

I uploaded a version of Links for DOS with javascr*** here:

(from Mikulas's mail)

http://www.jikos.cz/~mikulas/links/links-2.15-js.exe

BUT:
* there are unfixed bugs in the javascr*** engine, so it is not secure
(though, no one would probably bother writing exploits for it)
* the javascr*** engine was written in the era of Netscape 3 and 4 and
it supports features of those browsers. It doesn't run javascr*** on the
current internet

Mikulas

Links 215 is up and running just fine.

---
AUSREG Consultancy http://www.ausreg.com
Tadpole Tunes http://www.tadpoletunes.com
Sna Keo Il http://www.tadpoletunes.com/sna_keo_il/

Thanks!

---
Visit my personal blog at https://www.javiergutierrezchamorro.com

> After many request a new version of links with js enabled it's out
>
> I uploaded a version of Links for DOS with javascr*** here:
>
> (from Mikulas's mail)
>
> http://www.jikos.cz/~mikulas/links/links-2.15-js.exe

Regular binaries are available from: http://links.twibright.com/download/binaries/

I dunno the difference between links-2.15-lite.exe and links-2.15.exe. Maybe "lite" means text-mode only.

---
Forum admin

> Regular binaries are available from:
> http://links.twibright.com/download/binaries/
>
> I dunno the difference between links-2.15-lite.exe and
> links-2.15.exe. Maybe "lite" means text-mode only.

I haven't tried the latest version yet. But, in older versions, yes, "lite" was text only (and also no HTTPS/SSL).

Hi,

someone can load this special version on IBIBLIO or freedos repository?

thanks

Roberto

> someone can load this special version on IBIBLIO or freedos repository?

Where are the sources? Are they the same as vanilla 2.15? Binaries and sources (for exact same version) must both be available (GPLv2+).

> > someone can load this special version on IBIBLIO or freedos repository?
>
> Where are the sources? Are they the same as vanilla 2.15? Binaries and
> sources (for exact same version) must both be available (GPLv2+).

i suppose it's a special version of 2.15 created by author under request.

The source it's not provided, only the binaries (from personal site of authors, not from project site..)

> i suppose it's a special version of 2.15 created by author under request.
>
> The source it's not provided, only the binaries (from personal site of
> authors, not from project site..)

Probably meant only provisionally as a test version. But what to test it on? One sore point of contention has been Google Groups, which has required Javascript since a few years. Maybe we should test there? (But I'll have to do it later.)

> > Where are the sources? Are they the same as vanilla 2.15? Binaries and
> > sources (for exact same version) must both be available (GPLv2+).
>

from Mikulas :

You can get the source (including javascr***) from
git://leontynka.twibright.com/links.git

You can use the --enable-javascr*** parameter to ./configure to enable
javascr***.

I used these djgpp packages when compiling links for DOS. If you download
them, you'll get the same build as me.

bc106b.zip bz2106b2.zip djtzn204.zip gcc730b.zip grx249b2.zip
jpeg9cb.zip man13br2.zip shl20112.zip txi413b2.zip xz-508a.zip
bnu230b.zip csdpmi7b.zip ed-1142b.zip gdb72br4.zip gwk420b.zip
lss481b.zip pcre841b.zip ssl102kb.zip txt20br2.zip xz-508b.zip
bsh204b.zip dif36b.zip fil41br2.zip gmp612b.zip gzip18b.zip
lzlib18a.zip png1634b.zip tar112ab.zip zlb1211b.zip
bz2106a2.zip djdev204.zip fnd42335.zip grep29b.zip jbig21b2.zip
mak421b.zip sed44b.zip tiff409b.zip wh220br2.zip

the wattcp I use is wat3222br6.zip

Previous versions of the library contained a bug that caused crashes if
the server sent too much data, over the window advertised by the client.

> After many request a new version of links with js enabled it's out
>
> I uploaded a version of Links for DOS with javascr*** here:
>
> (from Mikulas's mail)
>
> http://www.jikos.cz/~mikulas/links/links-2.15-js.exe
>
> BUT:
> * there are unfixed bugs in the javascr*** engine, so it is not secure
> (though, no one would probably bother writing exploits for it)
> * the javascr*** engine was written in the era of Netscape 3 and 4 and
> it supports features of those browsers. It doesn't run javascr*** on the
> current internet
>
> Mikulas


Great News!
Has anyone tested the new version yet? Particularly the javascr***... I know it's way too old, but does it actually improved anything? Are there any basic things Links used NOT to do that it does now via javascr***?
Right now I cannot use my DOS machine connected to the internet.
Thanks.

> Great News!
> Has anyone tested the new version yet? Particularly the javascr***... I
> know it's way too old, but does it actually improved anything? Are there
> any basic things Links used NOT to do that it does now via javascr***?
> Right now I cannot use my DOS machine connected to the internet.
> Thanks.

Not really. A brief try (a week or so ago) of Google Groups didn't show any effect. I'm not really surprised.

On a different note, the old 2008 DJGPP build of Wget seems to have recently stopped working on some sites (notably, SourceForge.net and Github.com) due to SSL problems. Even Kostylev's 2017 Curl build doesn't really seem to work. (Fiddling a bit with switches didn't really help.)

But Links2 does seem to still work on such sites, so that's good.

I would still like some kind of automated tool. (Can Links2 download without prompt? Bah, need to read the manual closer.) Kostylev did build a newer Wget (2017), but I haven't tested it much (and the config file is different, or at least different location). Maybe I need to try rebuilding Curl myself.

> > Great News!
> > Has anyone tested the new version yet? Particularly the javascr***... I
> > know it's way too old, but does it actually improved anything? Are there
> > any basic things Links used NOT to do that it does now via javascr***?
> > Right now I cannot use my DOS machine connected to the internet.
> > Thanks.
>
> Not really. A brief try (a week or so ago) of Google Groups didn't show any
> effect. I'm not really surprised.
>
> On a different note, the old 2008 DJGPP build of Wget seems to have
> recently stopped working on some sites (notably, SourceForge.net and
> Github.com) due to SSL problems. Even Kostylev's 2017 Curl build doesn't
> really seem to work. (Fiddling a bit with switches didn't really help.)
>
> But Links2 does seem to still work on such sites, so that's good.
>
> I would still like some kind of automated tool. (Can Links2 download
> without prompt? Bah, need to read the manual closer.) Kostylev did build a
> newer Wget (2017), but I haven't tested it much (and the config file is
> different, or at least different location). Maybe I need to try rebuilding
> Curl myself.

because github stopped supporting TLS 1.0/1.1. You need a SSL/TLS support backend that supports TLS 1.2.

Ahoj Roberto,

Where You have JS enable??? 2.15 sources are without JS :(
Option in configure has not JS :(

david


> > > Where are the sources? Are they the same as vanilla 2.15? Binaries and
> > > sources (for exact same version) must both be available (GPLv2+).
> >
>
> from Mikulas :
>
> You can get the source (including javascr***) from
> git://leontynka.twibright.com/links.git
>
> You can use the --enable-javascr*** parameter to ./configure to enable
> javascr***.
>
> I used these djgpp packages when compiling links for DOS. If you download
> them, you'll get the same build as me.
>
> bc106b.zip bz2106b2.zip djtzn204.zip gcc730b.zip grx249b2.zip
> jpeg9cb.zip man13br2.zip shl20112.zip txi413b2.zip xz-508a.zip
> bnu230b.zip csdpmi7b.zip ed-1142b.zip gdb72br4.zip gwk420b.zip
> lss481b.zip pcre841b.zip ssl102kb.zip txt20br2.zip xz-508b.zip
> bsh204b.zip dif36b.zip fil41br2.zip gmp612b.zip gzip18b.zip
> lzlib18a.zip png1634b.zip tar112ab.zip zlb1211b.zip
> bz2106a2.zip djdev204.zip fnd42335.zip grep29b.zip jbig21b2.zip
> mak421b.zip sed44b.zip tiff409b.zip wh220br2.zip
>
> the wattcp I use is wat3222br6.zip
>
> Previous versions of the library contained a bug that caused crashes if
> the server sent too much data, over the window advertised by the client.

Ahoj David,

download right source from
git://leontynka.twibright.com/links.git

use

https://git-scm.com/

https://git-scm.com/downloads

Ahoj Roberto,

OK, git has upcomming version 216 with javascr***.c ....
I have tested with http://www.isjavascr***enabled.com/

and links crashes to freezy computer :(((

David

https://javatester.org/javascr***.html

this partly supported :)

there You have tested 2.16 links >

https://uloz.to/!LV1JC5U2cyNy/links-exe

dave

> there You have tested 2.16 links

Oh, apparently final 2.16 was released like two days ago. But I haven't mirrored it for FreeDOS yet.

> > the old 2008 DJGPP build of Wget seems to have recently stopped working
> > on some sites (notably, SourceForge.net and Github.com) due to SSL
> > problems. Even Kostylev's 2017 Curl build doesn't really seem to work.
> > (Fiddling a bit with switches didn't really help.)
> >
> > But Links2 does seem to still work on such sites, so that's good.
> >
> > Kostylev did build a newer Wget (2017), but I haven't tested it much
> > (and the config file is different, or at least different location).
>
> because github stopped supporting TLS 1.0/1.1. You need a SSL/TLS support
> backend that supports TLS 1.2.

His newer Wget build (1.19) seems to work fine on those two (important) sites, though I do have to manually "set WGETRC=g:/utils/wgetrc" first.

the 2.16 could be with minimal JS support, yes, or not?
because "configure" still doesn`t offer JS!

the 2.16 final version is still without JS!

> the 2.16 could be with minimal JS support, yes, or not?
> because "configure" still doesn`t offer JS!

> Oh, apparently final [Links] 2.16 was released like two days ago. But I haven't mirrored it for FreeDOS yet.

Done!

Thank you, it's a very cool one :) As I experience it is faster then 2.14 and 2.15

There is only one problem: The Turkish 'dotless i' character's normal and bold forms are a little bit mixed up, especially in the monospace typeface.

---
DOS isn't about why. It's about why not.