The ST TF536 software compatibility list.

[PhilC]

In this topic I'd like to share a lost of what works, what doesn't and what's faster whilst using games, utilities etc with the ST Version of the TF536.

Hopefully there will be enough interest in this section to compile a comprehensive list of what works and what doesn't.

[PhilC]

Compatible Tos Versions

Tested versions of TOS known to be compatible with the TF536 are:

TOS2.06, requires a twisted IDE cable to byte swap the IDE interface and make it Atari compatible. Recommended to disable caches by jumpering the CDIS jumper on the TF536.

EmuTOS, tested by myself from version 0.9.1.12 and includes the current version 1.0. Will work with a twisted or untwisted IDE cable. Standard TOS build disables the blitter when an 030 is present (please verify).

TOS1.04 is not currently TF536 compatible due to lack of 68030 support as standard. TOS1.04 uses a self modifying code routine (the routine is copied from ROM to RAM) in the F-Line handler. This causes trouble for the 030 because the 030 has separate instruction and data caches.

[PhilC]

Useful software to burn in your TF536

Pretty much any software that runs in fast ram and is math intensive will be good for testing out your new TF536 and testing whether the CPU you've chosen is up to the task of running at 50mhz.

For benchmarking and general system stress testing I use Gembench.

https://www.exxosforum.co.uk/atari/last/GB6/index.htm

Most 3d games will gain a boost with an 030. A typical example is Frontier. There are versions available that run very well from fast ram on the TF536. A good stress test is to leave the intro demo running continuously.

For testing your new fastram I would recommend the TT version of YAART.

http://www.chzsoft.de/site/hardware/div ... ware-yaart

[terriblefire]

TOS1.04 is not currently TF536 compatible due to lack of 68030 support as standard.

TOS1.04 uses a self modifying code routine (the routine is copied from ROM to RAM) in the F-Line handler. This causes heck because the 030 has separate instruction and data caches.

[PhilC]

TOS1.04 is not currently TF536 compatible due to lack of 68030 support as standard.

TOS1.04 uses a self modifying code routine (the routine is copied from ROM to RAM) in the F-Line handler. This causes heck because the 030 has separate instruction and data caches.

Will edit the above, thanks

[exxos]

TOS1.04 is not currently TF536 compatible due to lack of 68030 support as standard.

TOS1.04 uses a self modifying code routine (the routine is copied from ROM to RAM) in the F-Line handler. This causes heck because the 030 has separate instruction and data caches.

I think theres some issues with stack frame sizes as well.

[stephen_usher]

I do wonder if instead of using TOS 2.06 as a starting point 3.06 may be better. I'm not sure if it'll just ignore the lack of a second MFP, SCSI and serial chip. I know it doesn't care about the serial chip as I ran my TT without one for a couple of years.

[PhilC]

I do wonder if instead of using TOS 2.06 as a starting point 3.06 may be better. I'm not sure if it'll just ignore the lack of a second MFP, SCSI and serial chip. I know it doesn't care about the serial chip as I ran my TT without one for a couple of years.

3.06 was patched for use with the Pak68/3 so its possible.

[agranlund]

TOS1.04 uses a self modifying code routine (the routine is copied from ROM to RAM) in the F-Line handler. This causes heck because the 030 has separate instruction and data caches.

I think theres some issues with stack frame sizes as well.

KAOS TOS 1.04 does run, and maprom can put it in fastram but it’s more of a novelty than anything I think :)
Tos itself is quite snappy with maprom but since 1.04 doesn’t have the concept of altram then no programs will be loaded into (or allocate from) the fastram so no big gains for applications.

[derkom]

I do wonder if instead of using TOS 2.06 as a starting point 3.06 may be better. I'm not sure if it'll just ignore the lack of a second MFP, SCSI and serial chip. I know it doesn't care about the serial chip as I ran my TT without one for a couple of years.

I attempted to load an image of stock 3.06 using TTRAMTOS on mine, and it did not work. I didn't do any further investigation, because I have too many other things to worry about. :)

Would be interesting to try it out using an image of the Pak TOS, but I haven't looked into this.