[hatari-devel] Hatari interrupts still assert, if VDI mode is used

[Eero Tamminen]

Hi,

On Monday 10 August 2009, npomarede at corp.free.fr wrote:
> >>>> Fix committed, no more crash for me.
> >>>
> >>> Does this work also:
> >>>  hatari --machine falcon --tos tos404.img -s 14 --vdi-planes 1
> >>> --vdi-width 800 --vdi-height 600
> >>> ?
> >>>
> >>> (I had a crash, I'll look tomorrow whether I somehow messed something
> >>> up in my source update.)
> >>
> >> falcon mode creates a crash for me too (some kind of loop I guess, as
> >> the gui becomes unresponsive). I will try to see what is different
> >> with falcon mode.
> >>
> > OK, I saw the problem, a timer B int could be repositionned when
> > changing the MFP AER reg,
> >
> > I need to remove this part in vdi mode. I will commit a fix for this, I
> > need to see it doesn't break 7 gates of jambala.
> >
> Change is committed, I don't have the crash in falcon + vdi + tos 404
> anymore.

I verified that Hatari doesn't assert anymore, but the VDI mode doesn't
work properly.

If I try something that I'm sure that worked earlier:
hatari --machine tt --tos etos512k.img -s 14 --vdi-planes 1 --vdi-width 
1024 --vdi-height 768

Or try just some more normal screen size:
  hatari --machine st -s 4 --vdi-planes 1--vdi-width 640 --vdi-height 400

The colors are inversed.

If I start things with "--vdi-planes 4" the whole screen is black.


I quickly tested and this worked fine at least with Hatari v1.0.1.

(When using regular TOS instead of EmuTOS the Atari bootup logo looks
crappy, but they work otherwise.)


	- Eero