Char_Use issue in Mode 8 - JS ROM

[Andrew]

Hardware used: real QL + Tetroid ROM switcher + Tetroid QUBIDE with 512k RAM extension and TK2 v2.23 + vMap + vDrive
The issue: Char_use doesn't work if ROM is JS

Code: Select all

10 TK2_EXT
20 x=ALCHP(2000)
30 LBYTES win1_bold_fnt,x
40 CHAR_USE x,0
50 PRINT "This is a TEST"
60 CHAR_USE 0,0
70 RECHP x

The program works in QEmulator (Minerva ROM and JS ROM) and on real QL with JM, MG, Spanish MG and Minerva ROMs
But with JS ROM is not working correctly:
- In mode 4 - the font is not set, the text is written with standard font
- In mode 8 - the font is not set, the text is written with standard font AND flashing!!

Removing the QUBIDE + RAM extension makes no difference.
I suspect that there might be a hardware issue, either with the QL or the ROM switcher.

Please, can someone run the above program on a real QL with JS Rom and tell me if it works?

[t0nyt]

Was going to try it, but don't have "bold_fnt" sorry

[Andrew]

Was going to try it, but don't have "bold_fnt" sorry

You can use any other font file, it doesn't matter.
You can also find Bold_fnt in QSTAR or Pitman

[dilwyn]

Does it work with a channel number, CHAR_USE #channel_number,x,0 on JS (I only have a JS on QemuLator with a TK2 v2.34, which works as you said)?

The TK2 manual doesn't say the channel number is optional, it only lists CHAR_USE 0,0 for resetting the fonts. So, without channel number, I guess the CHAR_USE just happens to work on some ROMs.

Since CHAR_USE is a TK2 extension, not impossible it might vary from version to version of TK2, possibly.

[t0nyt]

Works fine for me on JS

System 1: JS (Chr$ board) + Trump 768K + QIMSI + Hermes + Vmap + Vdrive + TK2 2.36

System 2: JS (Original) + 512KB QuintupLer + QIMSI + Vmap + Vdrive + TK2 2.36

Can post screenshots if required

[Andrew]

Works fine for me on JS

System 1: JS (Chr$ board) + Trump 768K + QIMSI + Hermes + Vmap + Vdrive + TK2 2.36

System 2: JS (Original) + 512KB QuintupLer + QIMSI + Vmap + Vdrive + TK2 2.36

Can post screenshots if required

Thank you!
That means that my JS QL is fucked up, technically speaking.
I have no idea what how to test it and find out what component is not working properly. Any suggestions, anyone?

[t0nyt]

You could try loading TK2 2.36 in RAM (seems to override version in ROM on my Trump system at least) to see if it’s the TK2 version as per Dilwyns comment

[Andrew]

You could try loading TK2 2.36 in RAM (seems to override version in ROM on my Trump system at least) to see if it’s the TK2 version as per Dilwyns comment

It makes no difference.
TK2 2.23 works with all ROMS except JS
I removed the QUBIDE + Ram + TK and loaded TK2 2.36 in RAM and still the same issue.

[t0nyt]

You could try loading TK2 2.36 in RAM (seems to override version in ROM on my Trump system at least) to see if it’s the TK2 version as per Dilwyns comment

It makes no difference.
TK2 2.23 works with all ROMS except JS
I removed the QUBIDE + Ram + TK and loaded TK2 2.36 in RAM and still the same issue.

I just tried with TK2 2.11 (from Trump) and it works ok still

So, as you say, not TK2 version

[tofro]

Is the Pointer Interface loaded in any of these cases? That shifts the variables in the channel definition block and might possibly confuse non-aware Toolkit versions.