We welcome retro users & hardware gurus alike! Come and join the party :)
https://www.exxosforum.co.uk/forum/
At a guess they'll be the SCSI address. Those are usually 3 bit addresses.GianDO wrote: 08 Nov 2020 22:07 On this card there are also jumpers for SCSI IDs, there are 3 jumpers J10, J11 and J12. The manual explains only the position of the jumpers for the RAM, but not that for the SCSI IDs. Do you to know the settings of these jumpers?
Thanks
Si ma io vorrei conoscere come vanno settati.terriblefire wrote: 08 Nov 2020 22:24At a guess they'll be the SCSI address. Those are usually 3 bit addresses.GianDO wrote: 08 Nov 2020 22:07 On this card there are also jumpers for SCSI IDs, there are 3 jumpers J10, J11 and J12. The manual explains only the position of the jumpers for the RAM, but not that for the SCSI IDs. Do you to know the settings of these jumpers?
Thanks
Please keep it in English!GianDO wrote: 08 Nov 2020 23:07Si ma io vorrei conoscere come vanno settati.terriblefire wrote: 08 Nov 2020 22:24
At a guess they'll be the SCSI address. Those are usually 3 bit addresses.
But I don't have 7 devices attached and I wouldn't want to wait for the system to check if all are present. This slows me down the boot.terriblefire wrote: 08 Nov 2020 23:44Please keep it in English!
SCSI address setting is a rather large user land subject. My guess is you are setting the controller ID there and unless you know what you are doing leave it alone as you found it. The controller is usually ID7 so all jumpers set.
It doesnt usually matter. The controller will scan all devices unless you ask it not to in software. I dont think this setting does what you think it does. Its there for when you have 2 controllers on a SCSI chain. Leave it alone.GianDO wrote: 09 Nov 2020 09:33But I don't have 7 devices attached and I wouldn't want to wait for the system to check if all are present. This slows me down the boot.terriblefire wrote: 08 Nov 2020 23:44
Please keep it in English!
SCSI address setting is a rather large user land subject. My guess is you are setting the controller ID there and unless you know what you are doing leave it alone as you found it. The controller is usually ID7 so all jumpers set.
matt020 wrote: 09 Nov 2020 10:52 And it doesn't (or shouldn't) take long to scan the chain anyway. It should take a matter of seconds.
Which kickstart? That is a known issue in KS3.0 i think? 1 min 36 seconds is the known time some drivers will wait for all disks to spin up.GianDO wrote: 09 Nov 2020 12:37matt020 wrote: 09 Nov 2020 10:52 And it doesn't (or shouldn't) take long to scan the chain anyway. It should take a matter of seconds.
1 minute and 36 seconds pass from when I turn on the computer until the WB screen appears. They seem a little too many. I noticed that during the boot there are some initial stall phases with the hard disk LED that seems to be on steady, then after a minute it flashes and loads the WB even if the floppy click has already been heard for at least 30 seconds.
The kickstart is 3.1, but it seems slow to me. 1 minute and 36 seconds is too long. I also have an A1200 and A4000 with the same kickstart and they don't take long to boot ..terriblefire wrote: 09 Nov 2020 14:13Which kickstart? That is a known issue in KS3.0 i think? 1 min 36 seconds is the known time some drivers will wait for all disks to spin up.GianDO wrote: 09 Nov 2020 12:37
1 minute and 36 seconds pass from when I turn on the computer until the WB screen appears. They seem a little too many. I noticed that during the boot there are some initial stall phases with the hard disk LED that seems to be on steady, then after a minute it flashes and loads the WB even if the floppy click has already been heard for at least 30 seconds.