Quote:

Please don't do that. It's better to send a KILL command via the arexx port

rx "address AMITCP; KILL"

Let me know if you get any peformance improvements out of RoadShow compared to the NetStack in 3.2. I did a lot of tests and always had worse performance in RoadShow but every network setup differs so your mileage may vary.

/Nicholai

>> For testing purposes you can simply stop the NetStack task after boot
>> (e.g. SYS:Utilities/TaskManager).

> Please don't do that. It's better to send a KILL command via the arexx port
> rx "address AMITCP; KILL"

Yes, that's a better way. Thanks.

What is the best/official speed measurement tool for this kind of speed test?

Want to be sure to do it right form the start.

[ Edited by JohnFante 21.07.2013 - 19:28 ]

Quote:

There's isn't anything "official". I used tcpspeed between my MorphOS system and a Linux box for my tests.
I had to make a couple of minor changes to make it to compile as far as I remember.
An alternative is ftp but that's less robust.

I am having some problems installing Roadshow on 3.2.

Since the installer does not work on MorphOS I have tried using this script by catohagen with Roadshow 1.9:

https://github.com/catohagen/morphos-roadshow-installer

It looks like it works as it should but when I reboot I get an error saying that TCP is already running. And Roadshow does not work.

The same happens when I install manually. The script is written to 3.1 so there is probably some conflict with the new stack in 3.2.

I will fiddle some more with it and see what happens.

Unless 3.2 changed file locations or changed startup, the script should most probably work, installer does no changes/remove/delete files from internal netstack other that rename that network-startup to network-startup.off (afair)

what problems do you have ?

check MOSSYS:S/network-startup and see if that file exists, if not roadshow will conflict as both stacks gets started, if installer script disabled Netstack in 3.2 correct, you should find MOSSYS:S/network-startup.off

if you find sys:S/network-startup, then Roadshow should be enabled

[ Edited by catohagen 24.07.2013 - 15:12 ]

I get an error saying that "Error: Device TCP is allready mounted" when I reboot after enabling Roadshow. And there is no network connection.

The script alters the two files you mention.

MOSSYS:S/network-startup gets changed to off when I enable Roadshow and that is removed when I go back Netstack.

sys:S/network-startup gets to off when I disable Roadshow.

There is one thing that does now work in the script. At least so it seems.

When I try to configure Roadshows internal settings (the S option) it goes thru the different settings fine but when I come back to the main menu it says that it is "not done".

Maybe it is a stupid question but how does Roadshow knows it has to start when there is nothing in the user-startup sequence?

I have checked manually that the correct files are present (it does not copy the 020 versions but that is probably as it should be). I am using version 1.9 of Roadshow so I am not using the 1.8 update 2 for MorphOS. Should I do that not that I am using 1.9?

[ Edited by JohnFante 24.07.2013 - 19:00 ]

> how does Roadshow knows it has to start when there is nothing in the
> user-startup sequence?

TCP/IP stack is started from network-startup.

Aha. Now I see. Thank you Andreas_Wolf