TT Boot Logo

News,announcements,programming,fixes,game patches & discussions.

Moderator: troed

User avatar
frank.lukas
Posts: 157
Joined: Fri Jan 19, 2018 11:52 am

Re: TT Boot Logo

Post by frank.lukas » Thu Mar 14, 2019 3:08 pm

Can someone build a patcher Program to change the boot Logo from TOS 2.06 and TOS 3.06 ?

Back in these days there was such a program from Rainer Rosin but I can not find it ...

User avatar
alienkidmj12
Posts: 37
Joined: Tue Aug 22, 2017 1:39 pm

Re: TT Boot Logo

Post by alienkidmj12 » Sun Mar 17, 2019 12:08 pm

really nice logo that, wouldnt mind it myself, i take it you need to flash a new rom ?

User avatar
Icky
Moderator
Moderator
Posts: 2081
Joined: Sun Sep 03, 2017 10:57 am
Location: UK
Contact:

Re: TT Boot Logo

Post by Icky » Thu Dec 26, 2019 11:43 am

Atarian Computing wrote:
Sun Mar 10, 2019 9:03 am
The offset where the logo begins in TOS3.06 is 35FF4
For reference in TOS2.06 UK image the offset for the logo is 3257E and ends at 32985

User avatar
thorsten.otto
Posts: 48
Joined: Mon Nov 04, 2019 2:20 am

Re: TT Boot Logo

Post by thorsten.otto » Tue Dec 31, 2019 4:16 am

The offset is not quite right, and also depends on the language of the TOS. For TOS 3.06(us), the logo starts already at $35fe8.

The table below should give the absolute address for all (official) tos versions (subtract $e00000 to get the file offset):

Code: Select all

306us: e35fe8
306de: e36018
306fr: e36036
306uk: e35fe8
306es: e36044
306it: e36026
306sv: e36036
306sf: e36044
306sg: e36044

206us: e3257e
206de: e325ae
206fr: e325cc
206uk: e3257e
206es: e325da
206it: e325bc
206sv: e325ae
206sf: e325da
206sg: e325da

Most patched TOS versions that are floating around (like CZ and PL) are based on the german version.

The routine that displays the logo is located at $e0074a in TOS 3.06, and $e00762 in TOS 2.06 (for all language versions).

As already mentioned above, the logo is 96x86 pixels, thus 1032 bytes of data.

Atarian Computing
Posts: 365
Joined: Tue Aug 22, 2017 4:27 am

Re: TT Boot Logo

Post by Atarian Computing » Tue Dec 31, 2019 8:36 am

thorsten.otto wrote:
Tue Dec 31, 2019 4:16 am
The offset is not quite right, and also depends on the language of the TOS. For TOS 3.06(us), the logo starts already at $35fe8.

The table below should give the absolute address for all (official) tos versions (subtract $e00000 to get the file offset):

Code: Select all

306us: e35fe8
306de: e36018
306fr: e36036
306uk: e35fe8
306es: e36044
306it: e36026
306sv: e36036
306sf: e36044
306sg: e36044

206us: e3257e
206de: e325ae
206fr: e325cc
206uk: e3257e
206es: e325da
206it: e325bc
206sv: e325ae
206sf: e325da
206sg: e325da

Most patched TOS versions that are floating around (like CZ and PL) are based on the german version.

The routine that displays the logo is located at $e0074a in TOS 3.06, and $e00762 in TOS 2.06 (for all language versions).

As already mentioned above, the logo is 96x86 pixels, thus 1032 bytes of data.
Now that you mentioned patched TOS versions, it occurred to me that since this is the ThunderStorm patched 3.06 TOS version (for obvious reasons), the offset might not be the same. Also, mine was the US version which I then changed to UK keyboard layout. So yeah, probably best to disregard my offset figures.

User avatar
Icky
Moderator
Moderator
Posts: 2081
Joined: Sun Sep 03, 2017 10:57 am
Location: UK
Contact:

Re: TT Boot Logo

Post by Icky » Tue Dec 31, 2019 9:01 am

Thanks @thorsten.otto this is helpful information

User avatar
thorsten.otto
Posts: 48
Joined: Mon Nov 04, 2019 2:20 am

Re: TT Boot Logo

Post by thorsten.otto » Tue Dec 31, 2019 9:30 am

Atarian Computing wrote:
Tue Dec 31, 2019 8:36 am
since this is the ThunderStorm patched 3.06 TOS version (for obvious reasons), the offset might not be the same.
The thunderstorm is only a patched TOS, i doubt that they changed all the addresses (although it would theoretically be possible if they used my source to recompile it). But you should be able to check it by disassembling it, the routine looks like

Code: Select all

[00e0074a] 207c 00e3 5fe8            movea.l   #$00E35FE8,a0
[00e00750] 2278 044e                 movea.l   ($0000044E).w,a1
[00e00754] 1038 044c                 move.b    ($0000044C).w,d0
[00e00758] b03c 0002                 cmp.b     #$02,d0
[00e0075c] 6728                      beq.s     $00E00786
[00e0075e] b03c 0006                 cmp.b     #$06,d0
[00e00762] 6722                      beq.s     $00E00786
[00e00764] d2fc 0500                 adda.w    #$0500,a1
[00e00768] 303c 0055                 move.w    #$0055,d0
[00e0076c] 7205                      moveq.l   #5,d1
[00e0076e] 3418                      move.w    (a0)+,d2
[00e00770] 32c2                      move.w    d2,(a1)+
[00e00772] 32c2                      move.w    d2,(a1)+
[00e00774] 32c2                      move.w    d2,(a1)+
[00e00776] 32c2                      move.w    d2,(a1)+
[00e00778] 51c9 fff4                 dbf       d1,$00E0076E
[00e0077c] d2fc 0110                 adda.w    #$0110,a1
[00e00780] 51c8 ffea                 dbf       d0,$00E0076C
[00e00784] 6018                      bra.s     $00E0079E
[00e00786] d2fc 0280                 adda.w    #$0280,a1
[00e0078a] 303c 0055                 move.w    #$0055,d0
[00e0078e] 720b                      moveq.l   #11,d1
[00e00790] 12d8                      move.b    (a0)+,(a1)+
[00e00792] 51c9 fffc                 dbf       d1,$00E00790
[00e00796] d2fc 0094                 adda.w    #$0094,a1
[00e0079a] 51c8 fff2                 dbf       d0,$00E0078E
[00e0079e] 7e27                      moveq.l   #39,d7
In the first instruction you will see the address of the data. You may also notice that the routine only handles resolutions 6 (TT-High) and 2 (ST-High), and assumes ST-Low otherwise, so any patched tos versions with support for eg. NOVA cards may have that routine replaced by something else.

BTW there is an (quite old) program named TOSPATCH that is able to do such patches , if you know how to use it. The original archives can't handle all language versions, but german and us/uk should work.

Post Reply

Return to “SOFTWARE PROGRAMMING & DISCUSSION”