The Sinclair QL Forum

Hi all,

Is it normal for the Trump card's second ROM block (normally TKII) to initialize twice on systems fitted with Minerva?

If so is there an easy way to detect Minerva so that I can patch the Trumpcard ROM, not to initialize it's second bank if it's running on a Minerva equipped machine?

I guess the reason for this is that Minerva scans for roms including $10000 and $14000 whereas the older versions of the ROM only scan $0c000, and then $c0000 and above.

Cheers.

Phill.

Don't You have second TKII inside the computer (64 kB Minerva ROM with TKII included)?
If so, turn off this one (usually using a jumper on the Minerva board), as the Trump Card has its own TKII built-in.

dex wrote:Don't You have second TKII inside the computer (64 kB Minerva ROM with TKII included)?
If so, turn off this one (usually using a jumper on the Minerva board), as the Trump Card has its own TKII built-in.

No Actually this is a self built Minerva board, so TKII is only on the Trumpcard.

Cheers.

Phill.

Hi all,

It seems that the Trump Card rom version 1.31 on Dilwyn's site doesn't have this problem because the Toolkit II image starts at offset $3C90 so address $13c90, so Minerva doesn't see it and initialize twice as it's not on a $4000 byte boundary. The Trump rom still checks for the standard $4afb001 signature so
it's possible to replace it with a different rom image.

I see no reasons why other Trump card images could not be patched to be like this though the brief test of 1.31 I have done it seems to be compatible. Not sure what the changes from version to version where, are they documented anywhere?

Cheers.

Phill.