Amiga.org
Amiga News and Community Announcements => Amiga News and Community Announcements => Amiga Software News => Topic started by: AndreasM on May 02, 2017, 07:39:21 AM
-
The Roadshow TCP/IP stack for the Amiga has been updated to version 1.13 and is available immediately. An updated demonstration version is available, too, as well as the updated software development kit.
A free update is available for customers who are using Roadshow version 1.12, upgrading it to version 1.13. Note: if you are still using Roadshow versions 1.8 or 1.11 then you will need to upgrade to version 1.12 first before you can upgrade it to version 1.13.
The changes in Roadshow 1.13 are as follows:
1. Polish localization files were contributed by Tomasz Potrykus,
which can be installed as part of the update process.
2. The "ping" command has been updated to support new options, which can
be used limit the number of test packets sent, either by
time or count. The time interval measurements taken and displayed
were upgraded and are now much more accurate than they were before.
3. The "traceroute" command shares the same time interval measurement
improvements with the "ping" command.
4. The "wget" command no longer crashes if too little stack memory
is available in the shell. Also, the data throughput rate calculation
now works correctly, which both affects the display of the estimated
remaining transmission time and the data rate limiting feature of
the "wget" command. Finally, the short form command line options (e.g.
"-q" for "--quiet") never worked correctly. This has been fixed.
5. Several related bugs were fixed within "bsdsocket.library",
the "SampleNetSpeed" and "ppp_sample" programs, which could
lead to memory corruption or seemingly random crashes.
6. The "ConfigureNetInterface" did not process the DHCPUNICAST
parameter correctly. This has been fixed.
7. The specially optimized versions of "bsdsocket.library",
"ppp-serial.device" and "ppp-ethernet.device" for use on Amigas with
CPUs other than the MC68000 and MC68010 can no longer result in crashes
if they are used on systems for which they are not suited.
8. The "TCP:" handler leaked memory whenever it was opened. This
has been fixed.
9. How much memory "bsdsocket.library" will use for incoming network traffic
can now be tweaked. This is helpful for applications which keep
running for day or weeks on end. Previously, "bsdsocket.library" could
end up allocating much more memory than strictly necessary, causing other
active software to run out of free memory. Because the choice to
spend as little memory as possible comes with a cost (slightly lower
data throughput), this option is not enabled by default.
10. The software development kit has been updated, fixing bugs in the example
source code, the "wget" command, as well as replacing the inline header
files for the GCC 68k compiler.
11. The reference documentation has been updated.
The "ReadMe" file of the "Roadshow" update archive contains more detailed information about the contributors who helped to make this update possible, as well as more detailed descriptions of the changes.
The update archive does not contain the updated documentation or source code. Please download the demonstration version and/or the software development kit, respectively, to find the new material.
http://roadshow.apc-tcp.de
http://www.apc-tcp.de
-
Do these updated commands, like ping, require Roadshow? Or do they work with any of the available TCP/IP stacks?
-
Do these updated commands, like ping, require Roadshow? Or do they work with any of the available TCP/IP stacks?
The "wget" command should work with any AmiTCP API compatible Amiga TCP/IP stack, but "ping" and "traceroute" might not work with AmiTCP because the kernel APIs are significantly different in the BSD Unix versions which AmiTCP and Roadshow are based upon, respectively. This is why, for example, the AmiTCP "route" command does not work with Roadshow.
It's possible that the use of ICMP sockets on Roadshow is sufficiently different for both Roadshow's updated "ping" and "traceroute" commands that they might not work with AmiTCP. I haven't checked...
But, no harm done, you could download the new Roadshow demo version and give these commands a spin on your AmiTCP API compatible TCP/IP stack of choice. I don't mind, and neither do these commands ;)
-
Thanks for the update!
-
Great!! In order to update from the previous version do you only need to replace the files in your current install? I seem to remember only having to do that last time.
-
Awesome, thanks! I could never get Roadshow to work on my system, perhaps will have to give it another try one of these days. :D
Any progress on a GUI? ;)
-
Hmmm... I forgot how to get to the download section of the purchases I made in the past at amigashop.org site.
EDIT: Found it, but still showing as 1.12
-
Hmmm... I forgot how to get to the download section of the purchases I made in the past at amigashop.org site.
EDIT: Found it, but still showing as 1.12
You need to download the update archive from http://www.amigafuture.de/downloads.php?view=detail&df_id=5208
I personally find this a bit annoying, since I need to use 4 archives, the main archive, and the 3 update archives.
-
You need to download the update archive from http://www.amigafuture.de/downloads.php?view=detail&df_id=5208
I personally find this a bit annoying, since I need to use 4 archives, the main archive, and the 3 update archives.
I hear you. Building the updated updated script, the updated patch files, etc. is a very time consuming exercise. It's one of the reasons why this update took so long to prepare.
Right now I don't have any good idea to make this a less arduous task, the "Installer" language offering not much in the way of creating a more compact patching procedure. It literally comes down to copy & pasting the same set of lines for each patch to apply, changing the names of the files, the checksums, etc. It's ugly at sixteen files already.
You have every right to be dissatisfied about the complications of applying the update. It is a sad byproduct of what I went through in making the update happen. Things cannot stay the way they are.
-
It's an IP stack, it should be able to check for updates and update itself.
-
awesome! Roadshow is hands down quicker than any other TCP/IP stack I've ever tried on my miggies and much easier to setup:hammer:
-
It's an IP stack, it should be able to check for updates and update itself.
Getting this to work robustly, with a safety net so as not to knock out the TCP/IP stack itself by mistake, requires a lot of work which I'm currently not convinced I could make time for.