Symbian emulator?

And yes, I could speed up the disk access with the cost of memory. Now I'm not loading the dsk file into RAM at all and that's why it's slow - for every MSX disk access it will open/seek/read/close the Symbian OS file... stupid but saves memory Furthermore, if you use gzipped dsk files it's even worse as you can probably guess...

How many RAM has the Nokia 7650/3650 phones? Do they use the internal phone memory as system RAM?

Humm, I think that not so many people have read my posts in this thread... Nokia 7650 and 3650 are based on a StrongARM Risc Processor at 104 Mhz.

IMHO it's not a StrongARM, because it supports the ARM THUMB instruction set -- which StrongARM does not support....

Because on a phone the keyboard is rather limited I was thinking of adding a menu in the emulator that allows the user to select a file from the disk image to be launched from BASIC since not all games run automatically. I know this can be fixed by using a real MSX or some other emulator to first create a disk that contains autoexec.bas that would give the user a menu of the games on the disk but it would be easier if you wouldn't have to do it. Also, this would be handy with tape images...

So, I was wondering if someone would know which address in the BASIC ROM I could trap or if there is some other way of detecting when the system has reached the BASIC ok prompt. Also, is there a nice way to feed the BASIC interpreter the command tokens other than simulating actual keypresses from the PPI?

Indeed, I guess that it would be so nice if the package of the emulator come with C-BIOS as MSX rom. The bad part is that C-BIOS is only MSX 1 rom, right?

Oh, and btw, I guess that everybody has noticed about the keyboard buffer problem on the 7650/3650, that make the response of the phone keyboard so slow, and our keystrikes are saved on a internal buffer that is executed maybe one second later... Because of that, most of shot'em up are unplayable...

Is there anything that you can do Jr? Or is it a hardware problem as I suspect?

keystrikes are saved on a internal buffer that is executed maybe one second later... Because of that, most of shot'em up are unplayable...

Is there anything that you can do Jr? Or is it a hardware problem as I suspect?

I would say the problem is that I'm running the emulation in its own thread which uses 100% CPU time and the keyboard input is fed by the OS via another thread (the OS event handler).

Since I don't know of any way to "scan" the keyboard matrix on the phone I have to rely on the event driven approach which is of course slower. This added to the fact that all the CPU time is being used up by the emulation thread makes the response slowish.

I can try to find and use some tricks but cannot promise an improvement...