Re: [hatari-devel] VDI resolution

[Cocoa Pod <cocoa.pod@xxxxxxx>]

Ok, when i'll be at home I'll try to increase memory (I'm in mountain)

- Miguel


> Hi,
> 
> On 03/16/2017 12:02 AM, Cocoa Pod wrote:
>> Below, my last trials:
>> STE,     68000,  8 MHz,  tos162, 4 MiB, VDI 640x480 16 colors -> Blank window (idem emutos94)
>> STE,     68000,  8 MHz,  tos162, 4 MiB,      Mono or RGB      -> Run
>> STE,     68000,  8 MHz,  tos206, 4 MiB, VDI 640x480 16 colors -> Blank window (idem emutos94)
>> STE,     68000,  8 MHz,  tos206, 4 MiB,      Mono or RGB      -> Run
>> STE,     68000,  8 MHz, etos097, 4 MiB, VDI 640x480 16 colors -> Blank window (idem emutos94)
>> STE,     68000,  8 MHz, etos097, 4 MiB,      Mono or RGB      -> Run
>> 
>> MegaSTE, 68000,  8 MHz,  tos206, 4 MiB, VDI 640x480 16 colors -> Blank window (idem emutos94)
>> MegaSTE, 68000,  8 MHz,  tos206, 4 MiB,      Mono or RGB      -> Run
>> MegaSTE, 68000, 16 MHz, etos097, 4 MiB, VDI 640x480 16 colors -> Blank window (idem emutos94)
>> MegaSTE, 68000, 16 MHz, etos097, 4 MiB,      Mono or RGB      -> Run
> 
> Same problem even with monochrome VDI, that's same size
> as normal TOS monochrome screen.
> 
> If you use "--trace os_base", it will show:
> ----------------------------------------
> $hatari --trace os_base --vdi-planes 1 --vdi-width 640 --vdi-height 400 -s 4 --tos etos512k.img --machine ste
> ...
> VDI mode memtop: 0x3f8000, phystop: 0x400000 (screensize: 32 kB, memtop->phystop: 32 kB)
> ...
> M68000 Bus Error reading at address $0 PC=$0.
> Bus Error at address $0, PC=$0 addr_e3=2 op_e3=4e73
> 
> Panic: Exception number -29072
> sr=48f9 pc=48f948f9
> 
> D0-3: 00000000 08000800 08000800 08000800
> D4-7: 08000800 08000800 08000800 08000800
> A0-3: 08000800 08000800 08000800 00000000
> A4-7: 00000000 00000000 003f7fc6 003f7fea
> USP: 301e301e
> 
> basepage=00014754
> text=00e4c430 data=00000000 bss=00000000
> ----------------------------------------
> 
> -> EmuTOS crashes to some kind of NULL pointer error.
> 
> 
> However, if you increase memory amount to 8MB, it works fine
> even with 16 colors mode.
> ----------------------------------------
> $ hatari --trace os_base --vdi-planes 4 --vdi-width 640 --vdi-height 480 -s 8 --tos emutos-512k-20170307/etos512k.img --machine ste
> ...
> VDI mode memtop: 0x7da800, phystop: 0x7e2800 (screensize: 150 kB, memtop->phystop: 32 kB)
> ----------------------------------------
> 
> 
> Things work also fine if one uses Hatari v2.0 instead of latest
> Mercurial version.  I.e. it's some change in Hatari that triggers
> this.
> 
> If I use "--fast-boot on" option with the Mercurial version of
> Hatari so that Hatari patches TOS memory detection routines,
> things work again fine.
> 
> -> I guess there's some issue in what VDI mode does, and how
> the new memory bank support and EmuTOS memory detection work
> 
> -> you can use "--fast-boot on" as workaround for now
> 
> 
> 	- Eero
> 
> 
>> TT, NEVER RUN !!!!!
>> 
>> Falcon,  68030, 32 MHZ, etos097, 8 MiB,       Mono or RGB      -> Run
>> Falcon,  68030, 32 MHZ, etos097, 8 MiB, VDI  640x480 16 colors -> RUN (idem emutos94)
>> Falcon,  68030, 32 MHZ, etos097, 8 MiB, VDI  800x600 16 colors -> RUN (idem emutos94)
>> Falcon,  68030, 32 MHZ, etos097, 8 MiB, VDI 1024x768 16 colors -> RUN (idem emutos94)
>> 
>> I have tout see why 68881 or 2 is never registered
>> for TT may I have a .cfg file with setup 68020, 68881, tos306, VDI any resolution. Thanks
>> Tomorrow I'll have many thing to verify !!
>> Good evening
>>   Miguel
>> 
>> 
>> Cocoa Pod
>> http://cocoa.pod.free.fr/
>> http://www.aconit.org/
> 
> 

Cocoa Pod
http://cocoa.pod.free.fr/
http://www.aconit.org/