Page 1 of 1

Atari ST core does not work with up to date MiSTer executable [Solved]

Posted: Sat Jun 06, 2020 2:46 pm
by vanfanel
HI there,

Since I updated the MiSTer executable and menu, the AtariST core won't boot: it seems to be in a loop trying to change video mode, but boot and desktop is never shown.

Is this known / expected?


EDIT: Made it to work by deleting core config files. Sorry!

Re: Atari ST core does not work with up to date MiSTer executable [Solved]

Posted: Sat Jun 06, 2020 3:55 pm
by ExCyber
I'm also seeing failure to boot, with a previously booting config using a 512K EmuTOS ROM and no disks. I've played with the various RAM/chipset options to no avail.

Re: Atari ST core does not work with up to date MiSTer executable [Solved]

Posted: Sat Jun 06, 2020 5:02 pm
by remowilliams
It's still working for me with the latest updates with my default config. TOS 1.02 and floppies working as well.

capture Screenshot 2020-06-06 12-57-14.png
capture Screenshot 2020-06-06 12-57-14.png (225.13 KiB) Viewed 5300 times

Re: Atari ST core does not work with up to date MiSTer executable [Solved]

Posted: Sat Jun 06, 2020 5:25 pm
by kubbie
Working here as well. Just tested.

Re: Atari ST core does not work with up to date MiSTer executable [Solved]

Posted: Sat Jun 06, 2020 6:34 pm
by desin24
Use EmuTOS 256k or TOS 2.06
for really old titles UK TOS 1.62 (the real one)
switch from BW to colour (typo ?) or vice vesa

Re: Atari ST core does not work with up to date MiSTer executable [Solved]

Posted: Sat Jun 06, 2020 8:51 pm
by vanfanel
EDIT: Got it working again by deleting all AtariST core config files in /config. Sorry... It was that easy. No need to annoy you guys. But thanks to those who answered :)

Re: Atari ST core does not work with up to date MiSTer executable [Solved]

Posted: Sun Jun 07, 2020 1:57 am
by ExCyber
After fiddling with my EmuTOS images, it's consistently working here, too, including with what seems to be the same configuration that I was using in the first place. I'm not sure what actually changed, but I guess I'm generally joining the chorus of this being some kind of transient weirdness rather than serious breakage.