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
GVP Impact A2000-HC+8 Series II su A2000
Moderators: terriblefire, Terriblefire Moderator
GVP Impact A2000-HC+8 Series II su A2000
A2000 - MC68000 - KS3.1 - WB 3.1 - 2MB ChipRAM - Impact A2000-HC+8 Series II - 8 MB FastRAM - SD2SCSI 16GB - Indivision ECS
-
- Moderator Team
- Posts: 5362
- Joined: Mon Aug 28, 2017 10:56 pm
- Location: Glasgow, UK
Re: GVP Impact A2000-HC+8 Series II su A2000
At a guess they'll be the SCSI address. Those are usually 3 bit addresses.
———
"It is not necessarily a supply voltage at no load, but the amount of current it can provide when touched that
indicates how much hurting you shall receive."
"It is not necessarily a supply voltage at no load, but the amount of current it can provide when touched that
indicates how much hurting you shall receive."
Re: GVP Impact A2000-HC+8 Series II su A2000
Si ma io vorrei conoscere come vanno settati.terriblefire wrote: ↑Sun Nov 08, 2020 10:24 pmAt a guess they'll be the SCSI address. Those are usually 3 bit addresses.
A2000 - MC68000 - KS3.1 - WB 3.1 - 2MB ChipRAM - Impact A2000-HC+8 Series II - 8 MB FastRAM - SD2SCSI 16GB - Indivision ECS
-
- Moderator Team
- Posts: 5362
- Joined: Mon Aug 28, 2017 10:56 pm
- Location: Glasgow, UK
Re: GVP Impact A2000-HC+8 Series II su A2000
Please keep it in English!GianDO wrote: ↑Sun Nov 08, 2020 11:07 pmSi ma io vorrei conoscere come vanno settati.terriblefire wrote: ↑Sun Nov 08, 2020 10:24 pm
At a guess they'll be the SCSI address. Those are usually 3 bit addresses.
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 is not necessarily a supply voltage at no load, but the amount of current it can provide when touched that
indicates how much hurting you shall receive."
"It is not necessarily a supply voltage at no load, but the amount of current it can provide when touched that
indicates how much hurting you shall receive."
Re: GVP Impact A2000-HC+8 Series II su A2000
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: ↑Sun Nov 08, 2020 11:44 pmPlease 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.
A2000 - MC68000 - KS3.1 - WB 3.1 - 2MB ChipRAM - Impact A2000-HC+8 Series II - 8 MB FastRAM - SD2SCSI 16GB - Indivision ECS
-
- Moderator Team
- Posts: 5362
- Joined: Mon Aug 28, 2017 10:56 pm
- Location: Glasgow, UK
Re: GVP Impact A2000-HC+8 Series II su A2000
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: ↑Mon Nov 09, 2020 9:33 amBut 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: ↑Sun Nov 08, 2020 11:44 pm
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.
Applications where you have multiple controllers on a chain include IP over SCSI etc.
———
"It is not necessarily a supply voltage at no load, but the amount of current it can provide when touched that
indicates how much hurting you shall receive."
"It is not necessarily a supply voltage at no load, but the amount of current it can provide when touched that
indicates how much hurting you shall receive."
Re: GVP Impact A2000-HC+8 Series II su A2000
And it doesn't (or shouldn't) take long to scan the chain anyway. It should take a matter of seconds.
Re: GVP Impact A2000-HC+8 Series II su A2000
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.
A2000 - MC68000 - KS3.1 - WB 3.1 - 2MB ChipRAM - Impact A2000-HC+8 Series II - 8 MB FastRAM - SD2SCSI 16GB - Indivision ECS
-
- Moderator Team
- Posts: 5362
- Joined: Mon Aug 28, 2017 10:56 pm
- Location: Glasgow, UK
Re: GVP Impact A2000-HC+8 Series II su A2000
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: ↑Mon Nov 09, 2020 12:37 pm
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.
———
"It is not necessarily a supply voltage at no load, but the amount of current it can provide when touched that
indicates how much hurting you shall receive."
"It is not necessarily a supply voltage at no load, but the amount of current it can provide when touched that
indicates how much hurting you shall receive."
Re: GVP Impact A2000-HC+8 Series II su A2000
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: ↑Mon Nov 09, 2020 2:13 pmWhich 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: ↑Mon Nov 09, 2020 12:37 pm
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.
A2000 - MC68000 - KS3.1 - WB 3.1 - 2MB ChipRAM - Impact A2000-HC+8 Series II - 8 MB FastRAM - SD2SCSI 16GB - Indivision ECS