Hi,
On 01/06/2016 01:24 AM, Douglas Little wrote:
Looks like an IKBD overflow or other unhandled ACIA event. It goes
into an
infinite border-strobey-loop when that happens. Do you have MIDI data
being
streamed inwards by any chance?
Not in, I've just connected MIDI out.
Not seen it occur before in Hatari - odd.
If it's MIDI related, Nicolas did some fixes
for Hatari v1.9, to fix issues listed here:
http://www.atari-forum.com/viewtopic.php?f=51&t=27649&hilit=midi+hatari&start=25#p273237
Btw. At least few of the times I had enabled FPS reporting
with the '0' key, can that cause issues?
- Eero
D.
On 5 January 2016 at 23:17, Eero Tamminen <oak@xxxxxxxxxxxxxx> wrote:
Hi,
Douglas' latest Bad Mood version [1] also requires
disabling cycle accurate mode, or the game doesn't start.
[1] bm030.ttp, with NatFeats enabled so that BM knows
it's running under Hatari.
Then after playing for a while the Doom I level,
it freezes to this:
$0006dc28 : 46b8 9800 not.l $ffff9800.w
$0006dc2c : 60fa bra.s $6dc28
Douglas, what BM is expecting to happen to the Falcon
palette register value?
I was able to reproduce this freeze both with and
without MMU being enabled, e.g:
hatari --machine falcon --tos tos404.img -s 14 --natfeats yes
--fpu-type
68882 --cpu-exact no --mmu on --midi-out /dev/snd/midiC1D0 ./bm030.ttp
- Eero