Amiga.org
Amiga News and Community Announcements => Amiga News and Community Announcements => Topic started by: AndreasM on January 16, 2013, 01:01:01 PM
-
Since today there is an update available, so roadshow can also be used on MorphOS.
Roadshow is much faster than the internal TCP / IP stack for MorphOS.
Please note, that with MorphOS a manual installation of roadshow is required. The supplied installation script will not run under MorphOS. The user should therefore familiar with the operating system.
The manually installed Roadshow is now directly usable and requires no further intervention to boot.
New sample files for the network usage on the Pegasos / Pegasos II, and for Apple hardware are also included.
The update can be downloaded for free on the Support homepage Roadshow.
About Roadshow
Roadshow is an Amiga TCP/IP stack, that allows you to connect to the Internet, to access your e-mail, web pages, chat, etc. It can also be used to access and exchange files within your local home network.
Roadshow is one of the fastest, if not THE fastest Amiga TCP/IP stacks.
Some features include:
- Amiga-ised configuration utilities rather than the terse and somewhat cryptic Unix legacy tools
- DHCP configuration for Ethernet devices
- "TCP:" device support, for use with, for example, ARexx scripts
- Enhanced & cleaned-up software development kit, that includes the complete source code to all the configuration tools and sample programs
and ... much more ...
http://roadshow.apc-tcp.de
http://www.apc-tcp.de
-
the addnetinterface fix for bringing the device driver online still doesnt work
Ram Disk:> AddNetInterface DEVS:NetInterfaces/~(#?.info)
Interface "SunGEM" added.
Interface "SunGEM" configured, address = 192.168.0.55, network mask = 255.255.255.0.
Ram Disk:> ping google.com
ping: unknown host google.com
Ram Disk:> online sungem_eth.device unit 0
Ram Disk:> ping google.com
PING google.com (173.194.32.37): 56 data bytes
64 bytes from 173.194.32.37: icmp_seq=0 ttl=54 time=17.487 ms
64 bytes from 173.194.32.37: icmp_seq=1 ttl=54 time=17.047 ms
64 bytes from 173.194.32.37: icmp_seq=2 ttl=54 time=17.291 ms
64 bytes from 173.194.32.37: icmp_seq=3 ttl=54 time=17.105 ms
64 bytes from 173.194.32.37: icmp_seq=4 ttl=54 time=17.078 ms
64 bytes from 173.194.32.37: icmp_seq=5 ttl=54 time=16.872 ms
64 bytes from 173.194.32.37: icmp_seq=6 ttl=54 time=16.965 ms
--- google.com ping statistics ---
7 packets transmitted, 7 packets received, 0% packet loss
round-trip min/avg/max = 16.872/17.120/17.487 ms
Ram Disk:> version c:AddNetInterface
AddNetInterface 4.52
Ram Disk:>
-
the addnetinterface fix for bringing the device driver online still doesnt work
Ram Disk:> AddNetInterface DEVS:NetInterfaces/~(#?.info)
Interface "SunGEM" added.
Interface "SunGEM" configured, address = 192.168.0.55, network mask = 255.255.255.0.
Ram Disk:> ping google.com
ping: unknown host google.com
Ram Disk:> online sungem_eth.device unit 0
Ram Disk:> ping google.com
PING google.com (173.194.32.37): 56 data bytes
64 bytes from 173.194.32.37: icmp_seq=0 ttl=54 time=17.487 ms
64 bytes from 173.194.32.37: icmp_seq=1 ttl=54 time=17.047 ms
64 bytes from 173.194.32.37: icmp_seq=2 ttl=54 time=17.291 ms
64 bytes from 173.194.32.37: icmp_seq=3 ttl=54 time=17.105 ms
64 bytes from 173.194.32.37: icmp_seq=4 ttl=54 time=17.078 ms
64 bytes from 173.194.32.37: icmp_seq=5 ttl=54 time=16.872 ms
64 bytes from 173.194.32.37: icmp_seq=6 ttl=54 time=16.965 ms
--- google.com ping statistics ---
7 packets transmitted, 7 packets received, 0% packet loss
round-trip min/avg/max = 16.872/17.120/17.487 ms
Ram Disk:> version c:AddNetInterface
AddNetInterface 4.52
Ram Disk:>
You probably have to copy the sungem_eth.device file from mossys:devs/networks to sys:devs/networks... it shouldn't make a difference but...
not sure if this would work tho.
Cheers,
Dragster
-
the addnetinterface fix for bringing the device driver online still doesnt work
Ram Disk:> AddNetInterface DEVS:NetInterfaces/~(#?.info)
Interface "SunGEM" added.
Interface "SunGEM" configured, address = 192.168.0.55, network mask = 255.255.255.0.
Ram Disk:> ping google.com
ping: unknown host google.com
Ram Disk:> online sungem_eth.device unit 0
Ram Disk:> ping google.com
PING google.com (173.194.32.37): 56 data bytes
64 bytes from 173.194.32.37: icmp_seq=0 ttl=54 time=17.487 ms
64 bytes from 173.194.32.37: icmp_seq=1 ttl=54 time=17.047 ms
64 bytes from 173.194.32.37: icmp_seq=2 ttl=54 time=17.291 ms
64 bytes from 173.194.32.37: icmp_seq=3 ttl=54 time=17.105 ms
64 bytes from 173.194.32.37: icmp_seq=4 ttl=54 time=17.078 ms
64 bytes from 173.194.32.37: icmp_seq=5 ttl=54 time=16.872 ms
64 bytes from 173.194.32.37: icmp_seq=6 ttl=54 time=16.965 ms
--- google.com ping statistics ---
7 packets transmitted, 7 packets received, 0% packet loss
round-trip min/avg/max = 16.872/17.120/17.487 ms
Ram Disk:> version c:AddNetInterface
AddNetInterface 4.52
Ram Disk:>
Or... add full path to the device name in the netinterfaces/ config file... since it might be that the device is not yet in memory when the addnetinterfaces command is executed...
Cheers,
Dragster
-
so doing these steps (adding full path, copying to devs:networks) worked for you ?
if full path to sungem_eth.device was required, then 'online sungem_eth.device unit 0' would fail too i guess
-
This new stack can solve the misterious slow ethernet speed on some mac minis?
-
This new stack can solve the misterious slow ethernet speed on some mac minis?
samba transfers on my macmini goes upto 11.8MB/s on its 100mbit ethernet port with Roadshow
-
@cato
I dont use local net for make tests, my problem is download at ridiculous speed.
ps: sorry for the offtopic
-
so doing these steps (adding full path, copying to devs:networks) worked for you ?
if full path to sungem_eth.device was required, then 'online sungem_eth.device unit 0' would fail too i guess
I haven't tried this version myself... I probably won't bother as I already have two morphos setups working just fine with the previous version...
-
@kickstart
downloaded a ubuntu iso in win7/chrome and got 5MB/s
on morphos macmini/owb it was 1.6MB/s
morphos wget 1.9.1 got 1.3MB/s
morphos curl 7.19.5 got 1.5MB/s
however when downloading 3 instances of the same iso, all 3 files was downloading at 1.4MB/s each
maybe not impressive, i havent tried tuning Roadshow so much, the tcp.sendspace and tcp.recvspace env variables can improve that speed(or worsen it)
(its currently 78870 on both)
-
the addnetinterface fix for bringing the device driver online still doesnt work
Oh well.. downloaded the new version, commented the online via_rhine.device unit 0 line in my user-startup, replaced the addnetinterface binary, rebooted and it worked...
Not sure what can be wrong in your setup.. wil try the same in my Powerbook later on and will report back.
Cheers,
Dragster
**EDIT: Tried in my Powerbook with sungem_eth.device... it works fine.
-
Did you guys know that "Roadshow" was supposed to be the original tcp stack for Morphos? I wont go into why it didnt happen but thats why we ended up with nutsack , er, i mean "netstack" ;)
-
@dragster
well, its probably something here i've forgotten then, good to know it works
@magnetic
piru reported (mz) a download rate of 40MB/s when he wgets a 1gig iso from his local apache server with the new fixed Netstack...
Its always funny how these things work, we have been complaining of the performance of
the stack for years, and nearly every time a morphos-dev replys and says its fine, and works at full speed on his setup..
Then something comes along from the other 'camp' and better, then suddenly the problem gets high priority and gets fixed promtly (atleast thats my impression) :)
-
So what do one need the slightly improved speed for? I wish there was more focus on bringing the tcp-stacks up to date, almost all of them are 20 years old in terms of features.
-
So what do one need the slightly improved speed for?
In many cases there is a lot more than "slightly improved" speed.
I wish there was more focus on bringing the tcp-stacks up to date, almost all of them are 20 years old in terms of features.
It so happens that (http://www.morphzone.org/modules/newbb_plus/viewtopic.php?forum=9&topic_id=8962&post_id=97689&viewmode=flat&sortorder=0&showonepost=1) "I spent some time in December to update the MorphOS NetStack (using a newer FreeBSD code base)".
This would be "the new netstack" Piru is talking about here (http://www.morphzone.org/modules/newbb_plus/viewtopic.php?topic_id=9002&forum=9&start=4), with an average speed of 40-45MB/s, peeking at ~50MB/s.
I hope "a newer FreeBSD code base" also means "bringing the tcp-stack up to date". We'll see in MorphOS 3.2!
:)
-
the addnetinterface fix for bringing the device driver online still doesnt work
Ram Disk:> AddNetInterface DEVS:NetInterfaces/~(#?.info)
Interface "SunGEM" added.
Interface "SunGEM" configured, address = 192.168.0.55, network mask = 255.255.255.0.
Ram Disk:> ping google.com
ping: unknown host google.com
Ram Disk:> online sungem_eth.device unit 0
Ram Disk:> ping google.com
PING google.com (173.194.32.37): 56 data bytes
64 bytes from 173.194.32.37: icmp_seq=0 ttl=54 time=17.487 ms
64 bytes from 173.194.32.37: icmp_seq=1 ttl=54 time=17.047 ms
64 bytes from 173.194.32.37: icmp_seq=2 ttl=54 time=17.291 ms
64 bytes from 173.194.32.37: icmp_seq=3 ttl=54 time=17.105 ms
64 bytes from 173.194.32.37: icmp_seq=4 ttl=54 time=17.078 ms
64 bytes from 173.194.32.37: icmp_seq=5 ttl=54 time=16.872 ms
64 bytes from 173.194.32.37: icmp_seq=6 ttl=54 time=16.965 ms
--- google.com ping statistics ---
7 packets transmitted, 7 packets received, 0% packet loss
round-trip min/avg/max = 16.872/17.120/17.487 ms
Ram Disk:> version c:AddNetInterface
AddNetInterface 4.52
Ram Disk:>
Something's wrong. I'm currently looking into it, but by the looks of it there won't be a better solution until this weekend. This is somewhat embarrassing :(
AddNetInterface 4.52 will bring the underlying network device driver online if DHCP is used to set up the interface's IPv4 address, routing, etc.
However, if your network interface uses a static IPv4/netmask configuration (and no DHCP), then you must add the line "state=online" to the configuration file. Otherwise, the device will not be switched into online mode and cannot send or receive data.
I'm wondering: how does your network interface configuration file look like?
-
@cato
I dont use local net for make tests, my problem is download at ridiculous speed.
How do you access the internet from your machine? Specifically, is there a gateway router (talks Ethernet to your local network, talks ATM or Carrier Ethernet with your ISP) or cable modem involved?
Some of these devices are rather simplistic. They can pass traffic between the internet and your local network, but they are not necessarily willing or able to rewrite or reshape the data traffic. This can be problematic if the TCP/IP stack used in your local network does not have certain features which were introduced in the early 1990'ies. AmiTCP and Roadshow are among these, but Roadshow has one or two features which AmiTCP lacks.
If such features are lacking, and your gateway router/cable modem is smart enough to rewrite or reshape the data traffic that passes through it, then you might still get decent data throughput, since this device can (up to a point) make up for the deficiencies of the TCP/IP stack.
But if both your TCP/IP stack and your gateway router/cable modem are unable to compensate for each other's weaknesses, then the results may be disappointing.
-
Did you guys know that "Roadshow" was supposed to be the original tcp stack for Morphos? I wont go into why it didnt happen but thats why we ended up with nutsack , er, i mean "netstack" ;)
You are correct. This is not an urban legend.
-
I'm wondering: how does your network interface configuration file look like?
on my macmini where I installed the update :
# $VER: SunGEM 1.1 (10.1.2013)
#
# Configuration for the MorphOS "sungem_eth.device", on Apple hardware
# The device name is mandatory
device=sungem_eth.device
# If not provided, unit number 0 will be used. You may
# have to change this if there are multiple cards of the
# same type installed in your machine, or if your network
# hardware supports several independent connections
#unit=0
# You must either pick a fixed (static) IPv4 address and
# a corresponding subnet mask, or request DHCP (dynamic)
# network address configuration.
# You can combine address/netmask/dhcp, which has the effect
# of asking the DHCP server to assign the requested IPv4
# address and subnet mask to this interface, if possible.
address=192.168.0.55
netmask=255.255.255.0
#configure=dhcp
# If no DHCP server is present in your network, you can
# use automatic interface IPv4 address assignment through
# the ZeroConf protocol. Note that this will not set up
# default route and DNS servers for you, only the interface
# address is configured.
#configure=auto
# This variant of automatic IPv4 address assignment should
# be used in a wireless network instead of 'configure=auto'
#configure=fastauto
# You can enable diagnostic messages which can be helpful in
# tracking down configuration errors.
debug=yes
# You can choose how much memory will be used when handling
# incoming and outgoing network traffic for this device.
# The default is to reserve 32 buffers of 1500 byte each, both
# inbound and outbound traffic. Larger values may provide
# better performance.
#iprequests=32
#writerequests=32
# For diagnostic and monitoring purposes it can be helpful to
# capture network traffic that flows through this interface.
# To enable this option, select one of filter=local,
# filter=ipandarp or filter=everything
#filter=local
#filter=ipandarp
#filter=everything
# This option disables a workaround required for the Ariadne
# network hardware, which, if enabled, would otherwise cause
# the interface setup procedure to take longer than really
# necessary.
requiresinitdelay=no
-
on my macmini where I installed the update :
Thank you. You are indeed using a static IPv4 address and a corresponding network mask. This will completely bypass the online switch logic which I put into the AddNetInterface 4.52 command. The online switch only kicks in if DHCP is enabled (which in your case is disabled). This should explain why you still need to use the "online" shell command.
Could you please add "state=online" (without the double-quotes, of course) to this configuration file, then enter "netshutdown" and "addnetinterface SunGEM"? The "state=online" addition should make AddNetInterface switch the "sungem_eth.device" online, as if you had used the "online" shell command before.
The change would look something like this:
-- 8< --
# Bring "sungem_eth.device" online; never omit this line, as
# "sungem_eth.device" may otherwise refuse to receive or send
# any network traffic at all.
state=online
-- 8< --
If this should do the trick, I will update the documentation, fix the sample SunGEM and VIA-Rhine configuration files, and get new archives online.
-
adding "state=online" to Devs:NetworkInterfaces/SunGEM worked.
-
@kickstart
downloaded a ubuntu iso in win7/chrome and got 5MB/s
on morphos macmini/owb it was 1.6MB/s
morphos wget 1.9.1 got 1.3MB/s
morphos curl 7.19.5 got 1.5MB/s
however when downloading 3 instances of the same iso, all 3 files was downloading at 1.4MB/s each
I can download the same file on the very same router
windows 7 firefox 10mb/s
morphos 20, 30, 50kb/s
-
How do you access the internet from your machine? Specifically, is there a gateway router (talks Ethernet to your local network, talks ATM or Carrier Ethernet with your ISP) or cable modem involved?
Some of these devices are rather simplistic. They can pass traffic between the internet and your local network, but they are not necessarily willing or able to rewrite or reshape the data traffic. This can be problematic if the TCP/IP stack used in your local network does not have certain features which were introduced in the early 1990'ies. AmiTCP and Roadshow are among these, but Roadshow has one or two features which AmiTCP lacks.
If such features are lacking, and your gateway router/cable modem is smart enough to rewrite or reshape the data traffic that passes through it, then you might still get decent data throughput, since this device can (up to a point) make up for the deficiencies of the TCP/IP stack.
But if both your TCP/IP stack and your gateway router/cable modem are unable to compensate for each other's weaknesses, then the results may be disappointing.
My tests are made with the same router without any switch and speed between my pc and the morphos machine is abismal, there some more people with same problem/bug, theres a thread on morphzone with this topic and no solution at all.
-
I can download the same file on the very same router
windows 7 firefox 10mb/s
morphos 20, 30, 50kb/s
the 20-50kb/s on Morphos would most certainly be fixed with roadshow, i have downloaded with 50kb/s myself from aminet...try the demo and download again, install doesnt touch your morphos system or settings so you can enable/disable either roadshow or internal netstack as you please.
-
@cato
Ill try it, now im trying to make a dual boot with debian+morphos (osx is not very usefull for me)... thanks.
-
I know this thread is pointed at Roadshow on MorphOS, but I was wondering how well it works compared to MiamiDX? It's what I have right now it works well enough, but if Roadshow has better handling and an easier (read understandable) setup, I'd be interested in buy and supporting the software.
I did read the description on the website BTW, but I have a mediator with a 100base-T card, not the older 10base-T.
Thanks in advance!
-
adding "state=online" to Devs:NetworkInterfaces/SunGEM worked.
Thank you. This sounds like it will be easy to fix the update archives and the rest :)
-
just a quick question, i've noticed if i edit and save config files, and do a typo then log window pops up reporting an error so the stack monitors any change on the fly.
So yesterday tried with roadshowcontrol to change tcp.recv/sendspace and windowscaling on/of while downloading an ubuntu iso, to see if there was any difference, but the difference didnt happen before i've aborted the download and redownloaded.
So i made this quick little arexx script that monitors keys and put a tcp.sendspace and tcp.recvspace increase/decrease with c:RoadshowControl to better find the sweetspot,
and seemed to work, but was wondering if such a live autotuning existed already in the stack ?
-
I hope "a newer FreeBSD code base" also means "bringing the tcp-stack up to date". We'll see in MorphOS 3.2!
:)
We are working on NetStack and the 3.2 release will bring some improvement compared to current MorphOS. However, do not expect miracles as it will take some time catch up after all these years...
/Nicholai
-
just a quick question, i've noticed if i edit and save config files, and do a typo then log window pops up reporting an error so the stack monitors any change on the fly.
That is correct. Except for the network interface configuration files and the text database files (services, networks, etc.) every other configuration file is tracked and reread whenever its contents change.
So yesterday tried with roadshowcontrol to change tcp.recv/sendspace and windowscaling on/of while downloading an ubuntu iso, to see if there was any difference, but the difference didnt happen before i've aborted the download and redownloaded.
So i made this quick little arexx script that monitors keys and put a tcp.sendspace and tcp.recvspace increase/decrease with c:RoadshowControl to better find the sweetspot,
and seemed to work, but was wondering if such a live autotuning existed already in the stack ?
It exists, but I do not know the details. The TCP protocol is largely auto-calibrating, optimizing throughput according to how fast the receiver can process incoming data, how many segments have to be retransmitted, how much memory is available for assembling segments which were received out of order, etc.
-
Today we release the MorphOS Update 2 for Roadshow
-
Today we release the MorphOS Update 2 for Roadshow
I must say that I'm quite positively surprised by the MorphOS support shown here!
Great! :D
:)
-
Name: Roadshow MorphOS Update 2
Last file modification: 16.01.2013 - 13:47 (today's date 19.01.2013)
+ identical filename
+ identical readme file inside archive (no new changelog)
Was there any change? And if so, what?
:confused:
-
Today we release the MorphOS Update 2 for Roadshow
The update 2 file is still the same as the previous one?
Also how can customers of the full version get a newer archive? just redownload through the customer portal? tbh I didn't try that yet, since there's a download limit it seems?
-
Name: Roadshow MorphOS Update 2
Last file modification: 16.01.2013 - 13:47 (today's date 19.01.2013)
+ identical filename
+ identical readme file inside archive (no new changelog)
Was there any change? And if so, what?
:confused:
I didnt see a change either, there should be a 'state=online' in the SunGEM
and VIA_Rhine files
-
I made an installer for Roadshow on Morphos, since the orginal installer doesnt work and if it worked it would install lots of config files for amiga hardware.
It also lets you skip to install the firewall and ppp/ppoe stuff for adsl users
It doesnt touch anything in your existing Morphos system or network config so if you install you have to manually disable internal netstack and run Roadshow 68K manually (s:Network-Startup is renamed Network-Startup.off) Doubleclick from Ambient to start or rename to Net-Startup to let Roadshow start at next boot.
It also let you tune internal Roadshow settings based on calulations you enter
to better find settings spesific to transfer rates and more suited to system with more memory and not low-mem 68k classic systems, as this stack is aimed at... might boost you browsing speed...
After tuning I got tripple transfer rates in OWB downloads, compared with orginal unaltered Roadshow settings.
you need a working arexx tho...
https://github.com/catohagen/morphos-roadshow-installer
-
The update 2 file is still the same as the previous one?
Also how can customers of the full version get a newer archive? just redownload through the customer portal? tbh I didn't try that yet, since there's a download limit it seems?
+1
-
Make it Grunch compatible!
:)
-
I must say that I'm quite positively surprised by the MorphOS support shown here!
Great! :D
:)
You asked for it, didn't you? ;)
-
Name: Roadshow MorphOS Update 2
Last file modification: 16.01.2013 - 13:47 (today's date 19.01.2013)
+ identical filename
+ identical readme file inside archive (no new changelog)
Was there any change? And if so, what?
:confused:
As of this writing the archive files which I updated yesterday are not available yet. I don't know what happened, but the new archive files are bound to show up soon.
As for the changes, I updated the ReadMe files in all archives (MorphOS update, demo version, full version) to briefly show what's new.
In this case, the network interface configuration files for MorphOS were all updated to allow them to be used with static IPv4 addresses.
Also, three new MorphOS network interface configuration files have been added for the older "mpc52xx_eth.device", "mv6436x_eth.device" and "rtl_8139pci.device" network device drivers. That should (hopefully) cover everything.
-
The update 2 file is still the same as the previous one?
Also how can customers of the full version get a newer archive? just redownload through the customer portal? tbh I didn't try that yet, since there's a download limit it seems?
In truth, I haven't figured out yet how to make patch files available yet... I'm open to suggestions, since I haven't quite found the time yet to plan ahead this far.
The recent changes only affected one shell command and a set of two (now five) network configuration files. These files are identical in both the full version and the demo version.
Hence, you could download either the demo version and copy the respective files manually, or you could pick the MorphOS update archive and copy the files from that archive. The recent changes and additions were for the benefit of MorphOS users only, and you're not missing anything if you run Roadshow on a 68k Amiga and have not installed the updated files yet.
The "core" of Roadshow, namely the bsdsocket.library (which is different in the full version and the demo version) has not needed updating yet.
-
How do registered users obtain updates?
[EDIT] Ok, Thanks!
-
I made an installer for Roadshow on Morphos, since the orginal installer doesnt work and if it worked it would install lots of config files for amiga hardware.
It also lets you skip to install the firewall and ppp/ppoe stuff for adsl users
It doesnt touch anything in your existing Morphos system or network config so if you install you have to manually disable internal netstack and run Roadshow 68K manually (s:Network-Startup is renamed Network-Startup.off) Doubleclick from Ambient to start or rename to Net-Startup to let Roadshow start at next boot.
It also let you tune internal Roadshow settings based on calulations you enter
to better find settings spesific to transfer rates and more suited to system with more memory and not low-mem 68k classic systems, as this stack is aimed at... might boost you browsing speed...
After tuning I got tripple transfer rates in OWB downloads, compared with orginal unaltered Roadshow settings.
you need a working arexx tho...
Cool! I'll have a good look at it. Maybe I can fix the existing installer script for Roadshow myself, so that it works better with MorphOS.
-
Sorry, i upload the wrong file. Now are the correct Update online.
SORRY
-
@AndreasM
Still the old archive here at http://www.amigafuture.de/downloads.php?view=detail&df_id=3662.
Edit: Ah, nevermind, so the files are to be extracted from the full demo archive 1.9
-
Hi Andreas, the file at http://www.amigafuture.de/downloads.php?view=detail&df_id=3662
is still unchanged.
-
but now. sorry, dont know why the fiel dont change :/
-
I've updated the Roadshow morphos installer to include the new config files for added hardware that came in update 1.8
After every ethernet spesific config files you install, it also asks to open up the file with ed (mossys:c/ed) so you can
change to static ip and netmask or just skip this to stay with default DHCP.
Added option to automatic import the host entries and nameserver/dns from your existing Netstack config files and replaces
the commented out lines with # char as Roadshow requires for comments (Netstack uses ; for comments)
Added switching of Roadshow / Netstack on or off , by renaming SYS:S/network-startup(Roadshow) / MOSSYS:S/network-startup(Netstack)
Whatever stack you enable is displayed visually in the main menu.
Makes installing Roadshow as easy as tapping a few keystrokes, as most of your existing network configuration can be imported into Roadshow.
https://github.com/catohagen/morphos-roadshow-installer
-
Does this installer work with MOS 3.3?
I bought Roadshow months ago, I think my version is 1.9. Do I need to download a newer version or the MorphOS update archive too?