trying to install Roadshow to work with Xsurf 500

[source]

I have just recently dusted off my a500 and I am trying to get it set up.

I have a n amiga 500 with OS 3.2.1 with the ACA500 (not the plus) with an aca 1232 accelerator. Attached to the ACA500 is the subway USB controller as well as the xsurf500.

I just recently purchased roadshow and have just installed it. I have looked for the Xsurf 500 device in net work device storage but can only find the xsurf and the xsurf 100 device file. I do not see one for the xsurf 500.

I cant seem to figure out how to get it to work.

Any help would be greatly appreciated.

[utri007]

I thing that XSurf 500 has a included TCP/IP stack?

https://icomp.de/shop-icomp/en/shop/...logged-in.html

This disk is already included with the X-Surf-500 card. If you have already purchased that, there is no need to buy it again.

I can recommend it, it works nicely, has nice easy gui and most important has a app icon which shows a status of connection.

[source]

The disk is corrupt and I don't have a backup for it. I can't seem to download form the Icomp site. When I ordered it I did it as a guest (in 2019).

[patrik]

Device drivers are not included with Roadshow, only NetInterface files which contains settings for an interface - points to a sana2 device driver for the network card and has settings like IP address etc.

You need the sana2 device driver from IComp for the X-Surf-500. I think it is named "x-surf-500-plus.device". I would presume it is included somewhere in the firmware, or else someone on the forum can help you if your disks are corrupted?

When you have sourced x-surf-500-plus.device, copy it to directory DEVS:Networks/ and if DEVS:Networks/ does not exist, create it.

I am pretty sure Roadshow is missing a pre-prepared X-Surf-500 NetInterface file, so you have to create it yourself, which is very easy:
From the Roadshow installation, you should in your system partition have a Storage/NetInterfaces/X-Surf-100 NetInterface file. Make a copy of this file and name it X-Surf-500 , open it in a text editor and change the row "device=x-surf-100.device" to "device=x-surf-500-plus.device".

Now you have done the X-Surf-500 specific part. Do any other configuration you might need, like if you use static IP address in that file and when you are done, move it to Devs/NetInterfaces/ to enable the network on every boot.

[source]

I finally got it working. It was mmulibs. I did a fresh install with out it. I had to edit some of the startup sequence not to check for it. And it is now connecting to the network. Now I just have to install everything again

[Olaf Barthel]

Originally Posted by patrik

I am pretty sure Roadshow is missing a pre-prepared X-Surf-500 NetInterface file, so you have to create it yourself

I would like to add a configuration file for the next Roadshow version, which is in the works and which I did not manage to ship in December last year.

For this I need a little help with regard to the name of the device driver. Apparently, it is part of the firmware, so it won't show up in "DEVS:Networks".

Please use the attached "devlist" command, which comes from the NDK 3.1, to list all the currently active devices in your system. One of these will be the X-Surf 500 device driver.

Here is how the output of the "devlist" command can look like, if used on a WinUAE system:

Devices currently in system:
 $400095dc  v40.1       OpenCnt=1       gameport.device
 $40009774  v39.4       OpenCnt=36      timer.device
 $40009914  v40.1       OpenCnt=2       keyboard.device
 $40009a8c  v40.1       OpenCnt=21      input.device
 $4000ae68  v39.35      OpenCnt=1       ramdrive.device
 $4000aeec  v40.1       OpenCnt=1       trackdisk.device
 $4000cc38  v40.2       OpenCnt=2       console.device
 $4000df9c  v50.1       OpenCnt=7       uaehf.device
 $405efd14  v50.4       OpenCnt=1       audio.device

Could you report which driver you found which is responsible for the X-Surf 500?

[source]

Will do.
I will do it tonight when I get home.
Thanks

PS are you the author to roadshow?

[source]

Here is the Devs list for my amiga 500. I currently have an aca 500 (not plus) with an ACA1232. Attached to it I have a subway usb and the xsurf500. In the computer I have the 2 meg chip ram and an indivisionECS. All the hardware is Icomp except for the subway.
A500DevList.txt

Thanks

[Olaf Barthel]

Originally Posted by source

Will do.
I will do it tonight when I get home.
Thanks

PS are you the author to roadshow?

Guilty as charged

[Olaf Barthel]

Originally Posted by source

Here is the Devs list for my amiga 500. I currently have an aca 500 (not plus) with an ACA1232. Attached to it I have a subway usb and the xsurf500. In the computer I have the 2 meg chip ram and an indivisionECS. All the hardware is Icomp except for the subway.
Attachment 77733

Thanks

Thank you very much! So it is "x-surf-500.device". Here is how the corresponding "X-Surf-500" network interface file would look like:

# $VER: X-Surf-500 1.1 (10.1.2023)
#
# Configuration for the Individual Computers "X-Surf 500"
# Ethernet card for the ACA500 and ACA500plus.
#
# Please note that this is not the same article as the "X-Surf"
# or "X-Surf 100" Ethernet cards, because each type requires its
# own special driver.

# The device name is mandatory
device=x-surf-500.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.1
#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

[source]

Thanks
I will give it a try.

[source]

Thanks. I am now online. I am currently backing up workbench and am going to try installing mmulibs. The install from icomp crashes with mmulibs running. I don't know if it the .device or amitcp.

[source]

I tried roadshow with mmulibs. It crashed. It seems to be an issue with the xsurf500.device and mmulibs.