Hi All,
I have a plain unexpanded QL, I wish to use toolkit TK2, I have a standard CARE cartridge and EPROM 16K.
I plan to program it with TK2, what version would you recommend for me?
My QL is JS ROM, one of the late SAMSUNG models.
Under uQLx emulator, I have tested these versions
V 2.12 - gives boot mesage CARE / QJUMP Toolkit
V 2.13 - seems not to recognize MDV2_
V 2.20 - gives boot message QJUMP Toolkit
I cannot really tell the difference, can you please advise?
Many thanks
TCAT
Which TK2 version to use
Re: which TK2 version to use
Tcat,
I haven't seen any release notes (i.e. list of bugs fixed) beyond version 2.13 - TK2 has always been a pretty stable piece of software (with no known severe bugs or really new features), so I wouldn't care too much what exact version to use.
I'd probably use 2.20. (And I think that's the one I use on uqlx, too)
Tobias
I haven't seen any release notes (i.e. list of bugs fixed) beyond version 2.13 - TK2 has always been a pretty stable piece of software (with no known severe bugs or really new features), so I wouldn't care too much what exact version to use.
I'd probably use 2.20. (And I think that's the one I use on uqlx, too)
Tobias
ʎɐqǝ ɯoɹɟ ǝq oʇ ƃuᴉoƃ ʇou sᴉ pɹɐoqʎǝʞ ʇxǝu ʎɯ 'ɹɐǝp ɥO
Re: which TK2 version to use
Tobias,
I see, the same file of my choice I use under uQLx, I can burn to EPROM, no tricks need to applied to the binary, correct?
Many thanks
Tom
I see, the same file of my choice I use under uQLx, I can burn to EPROM, no tricks need to applied to the binary, correct?
Many thanks
Tom
Re: which TK2 version to use
Tom,
to be on the safe side, check the first 4 Bytes - They should be $4afb0001 - The start of a Standard QL ROM Header. If not, you probably have the RAM Version. (But if you're using the same thing in uqlx as a ROM - and not LRESPRing it, you should be all right.). Provided that's all right, it can directly be burnt into an EPROM.
Tobias
to be on the safe side, check the first 4 Bytes - They should be $4afb0001 - The start of a Standard QL ROM Header. If not, you probably have the RAM Version. (But if you're using the same thing in uqlx as a ROM - and not LRESPRing it, you should be all right.). Provided that's all right, it can directly be burnt into an EPROM.
Tobias
ʎɐqǝ ɯoɹɟ ǝq oʇ ƃuᴉoƃ ʇou sᴉ pɹɐoqʎǝʞ ʇxǝu ʎɯ 'ɹɐǝp ɥO
Re: which TK2 version to use
All,
Hex dump shows $4afb0001 in all three files, I have freedom of choice, good.
It's a pity RAM disk is not part of TK2, but of floppy disk firmware, correct?
I use it as a separate extension.
Tom
Hex dump shows $4afb0001 in all three files, I have freedom of choice, good.
It's a pity RAM disk is not part of TK2, but of floppy disk firmware, correct?
I use it as a separate extension.
Tom
Re: which TK2 version to use
Hi,
TCAT
Just realised V 2.13 will only becomes active after TK2_EXT command is issued.V 2.12 - gives boot mesage CARE / QJUMP Toolkit
V 2.13 - seems not to recognize MDV2_
V 2.20 - gives boot message QJUMP Toolkit
TCAT
Re: which TK2 version to use
Hi,
Just saved Lightning ROM code from EPROM, I bought with CARE cartridge, and put version 2.20 of TK2 in place and it works.
QJUMP message appears in the initial screen after the boot.
Many thanks so far.
Tom TCAT
Just saved Lightning ROM code from EPROM, I bought with CARE cartridge, and put version 2.20 of TK2 in place and it works.
QJUMP message appears in the initial screen after the boot.
Many thanks so far.
Tom TCAT
Re: which TK2 version to use
Hi,
I have a new observation.
I compared V 2.12 and V 2.20 roms, and in fact they differ only in a single byte (except having different version header), specifying, default DATA_USE and PROG_USE.
V 2.12 flp1_, flp1_
V 2.20 flp1_, flp2_
V 2.13 and V 2.12 as well as V 2.13 and V 2.20
differ in some 15767 bytes.
V 2.13 appears possibly a later version compared to V 2.20
Tom
I have a new observation.
I compared V 2.12 and V 2.20 roms, and in fact they differ only in a single byte (except having different version header), specifying, default DATA_USE and PROG_USE.
V 2.12 flp1_, flp1_
V 2.20 flp1_, flp2_
V 2.13 and V 2.12 as well as V 2.13 and V 2.20
differ in some 15767 bytes.
V 2.13 appears possibly a later version compared to V 2.20
Tom