@PrzemasIII, post #1
@RadoslawF, post #2
Before installing the carrier board, the two clock jumpers labelled INT and EXT on the main board under the CPU
board (see Picture 4.3) must be set to the correct position. They should be set to position a) for a synchronous
CYBERSTORM 68040/25 MHz or CYBERSTORM 68060/50 MHz on EXT and to b) for an asynchronous
CYBERSTORM 68040/40 MHz on INT. Depending on whether you are installing the CYBERSTORM in an
AMIGA 4000/030 or AMIGA 4000/040, these jumpers must be set to the INT or EXT position. Please note that it is
not possible to operate the CYBERSTORM with these jumpers set in the incorrect position and the computer will
not boot up.
Jumpers:
IPEND enabled, if no processor on the main board
CBR enabled, if processor on the main board
DIAG Enable
1 and 2 connected to switch on the DiagROM;
2 and 3 connected if the DiagROM is not available or will not be used
ROM size
1 and 2 connected for 16 bit ROMs;
2 and 3 connected for 8 bit ROMs (ROM 0)
ROM Cnt
1 and 2 connected if two ROMs are installed;
2 and 3 connected if one ROM is installed
@PrzemasIII, post #4
Jumper Settings For an 040@25Mhz, the jumper marked INT on the A4000 motherboard needs to be set for the Internal Clock Signal. For an 040@40Mhz and 060@50Mhz the jumper needs to be set to EXT for an external Clock Signal.
@RadoslawF, post #12
@PrzemasIII, post #15
@Nightmare777, post #16
@PrzemasIII, post #19
Before installing the carrier board, the two clock jumpers labelled INT and EXT on the main board under the CPU
board (see Picture 4.3) must be set to the correct position. They should be set to position
a) for a synchronous CYBERSTORM 68040/25 MHz or CYBERSTORM 68060/50 MHz on EXT and to
b) for an asynchronous CYBERSTORM 68040/40 MHz on INT.
Depending on whether you are installing the CYBERSTORM in an
AMIGA 4000/030 or AMIGA 4000/040, these jumpers must be set to the INT or EXT position. Please note that it is
not possible to operate the CYBERSTORM with these jumpers set in the incorrect position and the computer will
not boot up.
@stachu100, post #22