[hatari-devel] EmuTOS screen

[Eero Tamminen]

Hi,

Thomas, could you comment on what would be the correct thing
to do with this?


On Friday 25 June 2010, Eero Tamminen wrote:
> On Saturday 19 June 2010, Vincent Rivière wrote:
> > I have noticed 2 problems with Hatari in ST mode and EmuTOS:
> > - The EmuTOS welcome screen never appears
> > - Ctrl+Alt+Shift+Del crashes with a double bus error
> >
> > However, the same rom works well on Steem.
> >
> > Also, everything works well with Hatari in Falcon mode.
>
> Reproduced the welcome screen issue.
>
> (my WM catches the keyboard shortcut so I cannot try that now)
>
> > Starting from EmuTOS 0.8.5, the welcome screen is only displayed on
> > cold boots. It is detected like this:
> >
> > coldboot = (memvalid!=0x752019f3 || memval2!=0x237698aa ||
> > memval3!=0x5555aaaa);
>
> Ok, EmuTOS bios.c sets these values after coldboot...
>
> > It looks like the problem comes from Hatari... but who knows.
>
> Hatari stMemory.c does following in STMemory_SetDefaultConfig()
> which is called after TOS is loaded[1]:
> --------
>         /* Fill in magic numbers, so TOS does not try to reference MMU */
>         STMemory_WriteLong(0x420, 0x752019f3);            /* memvalid -
> configuration is valid */
>         STMemory_WriteLong(0x43a, 0x237698aa);            /* another
> magic # */
>         STMemory_WriteLong(0x51a, 0x5555aaaa);            /* and another
> */ --------
>
> There's a "bIsEmuTOS" variable which could be used here, but I wonder
> which TOS versions do MMU checks depending on these variables and do
> they do these checks always?
>
> Also, to me it seemed that these are set also with Falcon emulation, so
> I don't understand why there's a difference based on what Hatari
> emulates...


	- Eero