From: Roger B. <rfb...@ym...> - 2015-01-16 02:44:21
|
On 15 Jan 2015 at 23:07, Vincent Rivière wrote: > On 10/01/2015 21:47, Roger Burrows wrote: > > I just tried this on 0.9.15 non-JIT and can't reproduce it. I think it > will > > take a lot to find this one ... > > That's crazy! > I can reproduce this bug everytime, but only if the desktop is saved with an > ST video mode!! > (instructions to create bug omitted) > > I can reproduce the bug with any ARAnyM version on Windows XP. > I'm using Aranym 0.9.15 on Linux, and I can't reproduce this with your instructions. I've tried about a dozen times, both with etos512k.img & emutos-aranym.img. BTW, I guess I *am* using JIT, at least I have JIT = Yes in the [JIT] section of config. > Furthermore, with my freshly built ARAnym-JIT from git, when the bug > happens, there is an additional message in the ARAnyM console: > > VDI video mode = 640x400 1-bit > keycode: 13 (0xd), scancode 0 (0x0), keysym 'return' is not mapped > > The first line is issued by EmuTOS when the AES initializes the VDI. > > The second one is totally unexpected. Something complains about the keyboard > long after the key has been handled in the EmuTOS welcome screen... > I never get a keycode message after the video mode message. > Why does this happen only with ST video modes? > Maybe some tricky timing due to the video RAM size? > > Anyway, even if I have discovered this bug recently, that's not a new > problem. > It looks like it might be a problem with Aranym versions other than 0.9.15, or a problem with Windows versions of Aranym. Roger |