08 January 2023, 18:27 | #1 |
Zone Friend
Join Date: Jul 2005
Location: Toronto, Canada
Posts: 734
|
trying to install Roadshow to work with Xsurf 500
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. |
08 January 2023, 18:32 | #2 | |
mä vaan
Join Date: Nov 2001
Location: Finland
Posts: 1,688
|
I thing that XSurf 500 has a included TCP/IP stack?
https://icomp.de/shop-icomp/en/shop/...logged-in.html Quote:
|
|
08 January 2023, 18:56 | #3 |
Zone Friend
Join Date: Jul 2005
Location: Toronto, Canada
Posts: 734
|
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).
|
09 January 2023, 01:18 | #4 |
Registered User
Join Date: Jan 2005
Location: Umeå
Age: 44
Posts: 954
|
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. |
09 January 2023, 06:02 | #5 |
Zone Friend
Join Date: Jul 2005
Location: Toronto, Canada
Posts: 734
|
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
|
09 January 2023, 09:01 | #6 | |
Registered User
Join Date: Aug 2010
Location: Germany
Posts: 537
|
Quote:
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: Code:
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 |
|
09 January 2023, 23:53 | #7 |
Zone Friend
Join Date: Jul 2005
Location: Toronto, Canada
Posts: 734
|
Will do.
I will do it tonight when I get home. Thanks PS are you the author to roadshow? |
10 January 2023, 06:28 | #8 |
Zone Friend
Join Date: Jul 2005
Location: Toronto, Canada
Posts: 734
|
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 |
10 January 2023, 08:07 | #9 |
Registered User
Join Date: Aug 2010
Location: Germany
Posts: 537
|
|
10 January 2023, 08:12 | #10 | |
Registered User
Join Date: Aug 2010
Location: Germany
Posts: 537
|
Quote:
Code:
# $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 |
|
10 January 2023, 14:00 | #11 |
Zone Friend
Join Date: Jul 2005
Location: Toronto, Canada
Posts: 734
|
Thanks
I will give it a try. |
15 January 2023, 21:35 | #12 |
Zone Friend
Join Date: Jul 2005
Location: Toronto, Canada
Posts: 734
|
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.
|
19 January 2023, 14:09 | #13 |
Zone Friend
Join Date: Jul 2005
Location: Toronto, Canada
Posts: 734
|
I tried roadshow with mmulibs. It crashed. It seems to be an issue with the xsurf500.device and mmulibs.
|
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
Thread Tools | |
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
PCB replacement membrane for Amiga 500/500+ keyboards - work in progress | RetroBox | Hardware mods | 15 | 22 April 2024 10:25 |
3.1.4 and unable to install xsurf-500 via ACA500+ | gurth | support.Hardware | 6 | 23 October 2021 14:19 |
ACA500 and XSurf 500 Pin headers | source | Hardware mods | 0 | 06 March 2021 18:40 |
Roadshow incompatibility, AmiTCP, Poseidon and AmigaExplorer... does it work for you | McTrinsic | support.Apps | 15 | 18 February 2018 20:14 |
Xsurf II Clock ports | Zetr0 | support.Hardware | 8 | 24 June 2007 12:21 |
|
|