Cyprian

It is not mine, I tole this link from BigPemu discord

Checkered Flag on the latest BigPemu: https://www.youtube.com/watch?v=ikbna9kIKx4

some useful links: Hardware: https://www.temlib.org/AtariForumWiki/index.php/Atari_ST/STe/MSTe/TT/F030_Hardware_Register_Listing OS: https://freemint.github.io/tos.hyp/en/index.html Nice FAQ about STE Hardware specific registers https://github.com/Number0000009/atari-wiki/blob/master/Atari STE FAQ compiled by The Paranoid Paradox.txt ST Synclock demosystem v1.0: https://dhs.nu/files.php?t=democreation Coding forum (more active than here on AA): https://atari-forum.com/viewforum.php?f=16

no, different pin layout STE: 5200:

obviously 120fps is better than 60 but in retro computer world we have used to live with 25 and less fps.

and?

why 60? Iron Soldier and Doom are playable at lower frame rate

anyway, GPU can handle 3D - e.g. Doom, Cybermorph or Iron Soldier

1400XL had PBI, FREDDIE chip, internal modem, and Votrax SC-01 speech synthesis chip

I would not blame 68000 for that, because 68000 13MHz in Jaguar is superior to SNES 65c816 3,58 MHz. I would say that the key to the failure was the lack of money, which resulted in a poor development kit and the lack of large development studios

or instead slow 68000 or not so cheap 68030 Atari could add a third JRisc processor

nice idea, I wonder if also Mickey's registers could be addressed externally. The CPU is inside it, but who knows.

it sounds cool, btw, I've never heard of this tracker before

Attached you can find "emutos.map" file generated by the make. There you can find more info about the low memory variables like: 0x00000000000005a0 _p_cookies = 0x5a0 0x00000000000005a4 _ramtop = 0x5a4 0x00000000000005a8 _ramvalid = 0x5a8 0x00000000000005ac _bell_hook = 0x5ac 0x00000000000005b0 _kcl_hook = 0x5b0 0x0000000000000800 . = 0x800 *fill* 0x0000000000000000 0x800 0x0000000000000800 sysvars_end = . .stack 0x0000000000000800 0x800 0x0000000000000800 _stkbot = . 0x0000000000001000 . = (. + 0x800) *fill* 0x0000000000000800 0x800 0x0000000000001000 _stktop = . .low_stram 0x0000000000001000 0x1140 0x0000000000001000 __low_stram_start = . obj/lowstram.o(.bss COMMON) .bss 0x0000000000001000 0xd38 obj/lowstram.o 0x0000000000001000 _shifty 0x0000000000001001 _dskbuf_alignment 0x0000000000001004 _dskbuf 0x0000000000001c04 _phys_work obj/lineavars.o(.bss COMMON) .bss 0x0000000000001d38 0x408 obj/lineavars.o 0x0000000000001d3c _CUR_FONT 0x0000000000001d6e _mouse_cdb 0x0000000000001d6e _m_pos_hx 0x0000000000001d70 _m_pos_hy 0x0000000000001d74 _m_cdb_bg 0x0000000000001d76 _m_cdb_fg 0x0000000000001d78 _mask_form For more details I would suggest to you to ask either on the EmuTOS list or Atari-Forum.com where the EmuTOS visits more often. emutos.zip

ok, from the EmuTOS you can read what i where located in the low RAM. e.g. there: https://github.com/emutos/emutos/blob/master/tosvars.ld