[hatari-devel] Problem with NVDI and latest hatari sources
Eero Tamminen
oak at helsinkinet.fi
Thu Dec 30 20:50:51 CET 2010
Hi,
On torstai 30 joulukuu 2010, Uwe Seimet wrote:
>> It shouldn't change anything unless you're using either extended VDI
>> resolution or VDI or AES tracing though. Are you?
>
> Yes, I am. My extended VDI resolution is 1280x960x2 (TT high).
Just to make sure, you're using the (default) UAE CPU core instead
of the new WinUAE CPU core, right?
I guess the issue isn't reproducible if you disable extended VDI resolution
and e.g. use TT TOS and TT high resolution?
Could you try switching ENABLE_TRACING to "OFF" from cmake configuration,
rebuild Hatari and see whether anything changes?
> When I
> switch off the extended resolution in the "Atari screen" settings and
> then reset the machine I get a segmentation fault, by the way.
I'm not able to reproduce the segfault. I did:
hatari -s 4 --machine ste --tos etos512k.img --vdi-width 1280 --vdi-height
960 --vdi-planes 1 -d .
And after TOS desktop was ready, pressed F12 and from "Atari screen" options
disabled VDI mode and in main options screen selected reset & pressed OK.
This worked fine with two different TOS versions. Valgrind doesn't report
anything either.
Could you send your hatari.cfg file so that I can try whether I can
reproduce the issue with that? Can you reproduce it if you don't
have anything started when the emulated machine boots?
What Hatari outputs when the emulation is reseted?
- Eero
More information about the hatari-devel
mailing list