Roadshow 1.12 released

[kolla]

(well, there's a set of patches for the ppp ethernet/serial device drivers, but I reckon you aren't using them - hardly anybody does).

Well, I am - serial port is still the most universally available option for all Amiga systems, and these days I build ARM systems (pi zero) inside all my Amiga computers, Roadshow works great with PPP over serial

(look at the respective file modification times first, but you can also use "version c:ftp full" and "version libs:bsdsocket.library file full").

It is not at all obvious what version of bsdsocket.library etc that belong to what version of Roadshow - it would be nice if all files, in addition to their own revisions numbers, could have "version full" strings that say something about version of Roadshow they belong to.

[LoadWB]

I thought that as registered buyers, we have free access to download registered versions? Oh well, guess I must store my copy somewhere safe.

I went back to APC-TCP and was able to get my registered download fixed.  But, yeah, keep your download safe.  I wound up creating a special directory for purchased software.

[paul1981]

All went smoothly.

After running the 1.11 update installer it yields:

ftp 1.8
bdsocket.library 4.310
ppp_connector 52.2
ppp_dialer 52.2
ppp_sample 52.2
ppp-ethernet.device 52.4
ppp-serial.device 52.10

Then, after running the 1.12 update installer it yields:

ftp 1.9
bdsocket.library 4.321
AddNetInterface 4.53
ConfigureNetInterface 4.36

I think I'm all up to date now. If something looks wrong then please let me know. Thanks for your help. ;-)

(Posting this on my super A1200, aka Carl!)

[olsen]

Well, I am - serial port is still the most universally available option for all Amiga systems, and these days I build ARM systems (pi zero) inside all my Amiga computers, Roadshow works great with PPP over serial

I'm glad that the PPP drivers are still useful

Writing them turned out to be both easier and harder than expected. The PPP design is well-documented, but in the early 2000's so many different "server-side" PPP implementations were in use that you were in for a lot of surprises writing an implementation from scratch.

I bought James Carlson's book "PPP design, implementation and debugging" in November 2001 because it seemed to be the right thing to do, and it was: it shows in painful detail how many PPP implementation options were deployed and discarded during the IETF standardization process. Features which were only briefly used in-house, or showed up in an RFC which was quickly "obsoleted" by a newer RFC document were still in use around 2001-2002. PPP "client-side" code had to be aware of these "quirks".

It is not at all obvious what version of bsdsocket.library etc that belong to what version of Roadshow - it would be nice if all files, in addition to their own revisions numbers, could have "version full" strings that say something about version of Roadshow they belong to.

Good point. Roadshow is still very much what it was (except with fewer bugs) when it became a stand-alone product in 2013.

The library version of "bsdsocket.library" as the central core of the TCP/IP stack cannot be conveniently changed during each Roadshow release, with each Roadshow file (commands, scripts, configuration files) then getting bumped to use the same version. This worked for Commodore (V37 = Workbench/Kickstart 2.04, V38 = Workbench 2.1, V39 = Workbench/Kickstart 3.0, V40 = Workbench/Kickstart 3.1), but I can't use the same approach.

I'll likely have to go with adding extra information to the version text embedded in each file.