Re: [hatari-devel] VDI mode broken (memvalid settings again)

[Thomas Huth <th.huth@xxxxxx>]

Am Fri, 23 Dec 2011 11:32:14 +0100
schrieb Nicolas Pomarède <npomarede@xxxxxxxxxxxx>:

> On 23/12/2011 00:14, Thomas Huth wrote:
> >
[...]
> > I think we should maybe reconsider the fast-boot / memvalid
> > settings. Maybe we should leave them enabled by default for now
> > until all problems are fixed?
> 
> In order to keep games such as yolanda working, maybe we could force 
> memvalid as before if :
>   - cpu is not 68000, or freq is not 8 MHz
>   - or tos is >= 3 or Emutos
>   - or vdi mode is enabled
>   - or machine is not STF or STE

Sounds ok, but I think we could omit the first item on your list ...
for Falcon and TT mode, the CPU has to be >= 68020 anyway (and TOS
version is also >= 3.0)

> The idea would be that a config with 68000 + tos 1.xx or 2.xx would
> not do to the memvalid in fastboot mode (which should cover the case
> of a user only wanting to play games/demos).
> 
> This would leave the gemdos hd problem ; in my case it's always
> enabled, even if I just run demos or games. Some demos already
> require to turn hd emul off, so it could be the same for yolanda.
> 
> I don't know if this would cover all the cases.
> Else, we can revert  the patch from stMemory.c and see what can be
> done after 1.6 is released (as yolanda is quite a piece of crap, I
> don't think it deserve to ruin the rest of the emulation :) )

Maybe we should at least have a possibility for the user to turn on the
memvalid patching again in case there are other circumstances where
this is needed ... ? So either another configuration option or revert
the fast-boot patch? What do you think?

 Thomas