Just released fMSX-Symbian 3.3. Get it free at this site:

http://fms.komkon.org/EmuSymbian/

Main features:
* Optimized for S60 platform using ARM assembly.
* Native S60 user interface (settings, dialogs, etc.).
* Scaled display with three different modes.
* Configurable display orientation.
* Color-blended pixel rendering.
* On-screen keyboard for single or multiple key input.
* Saving gameplay at any moment.
* Recording music into ringtones.
* Configurable key mappings.
* TV scanlines simulation.
* Framerate display.

The new version does not have problems installing alongside fMSX/S60 by Juha Riihimaki. Give it a try and let me know if there is anything to fix or add.

Nice Perhaps I don't need to be updating my emulator so much anymore...

For some reason fMSX-Symbian 3.3 is not working on my Nokia 6290. I just get a blank white screen after selecting a ROM image and the application stops responding (only way to kill it is to boot the device).

Quote:

Nice Perhaps I don't need to be updating my emulator so much anymore...

I guess yours may now be significantly different to develop it alongside.

Quote:

For some reason fMSX-Symbian 3.3 is not working on my Nokia 6290. I just get a blank white screen after selecting a ROM image and the application stops responding (only way to kill it is to boot the device).

Umgh... Let's see... Does it react to the green [SEND] key?

No, but if I press the red (END) key, the device goes back to idle screen -- with a long menu key press I can see fMSX in the task list but it cannot be killed with clear (C) key.

Quote:

No, but if I press the red (END) key, the device goes back to idle screen -- with a long menu key press I can see fMSX in the task list but it cannot be killed with clear (C) key.

Ok. I have a suspicion why it may be happening. Could you give me your email address so that I could send you a test version to try out?

Yep, I've now made one available on the user profile here at MRC. So just login to MRC and check my user info for the email address.

Quote:

Yep, I've now made one available on the user profile here at MRC. So just login to MRC and check my user info for the email address.

Done. Sent you a version with a fix in the suspicious spot and also some printf()s. If the emulation runs now, then I have fixed the right spot. Otherwise, just let me know what the printf()s say. Thanks!

Still doesn't work The console says:

AppView=00708B30
AppVideo=00708BE8
AppAudio=0070A208
AppInput=00713010
Thr=00700EA0
Stop=0

But now when I try to kill both the stdout and fmsx processes from the task list, I get a couple of system errors: first "application closed: fmsx" and then "application closed: EMULibThread" and finally "application closed: STDOUT".

Quote:

Still doesn't work The console says: AppView=00708B30, AppVideo=00708BE8,...

All right. This means that all the application objects have been allocated successfully, and the thread is waiting to get started. So, there is nothing wrong in the top level initialization. I have sent you another binary with different debugging messages. Could you tell me its output?

PS: Sorry for bothering you with debugging, but I do not have a 6290 phone to try these things on =(

No problem, I'm happy to help. The output with the latest version says:

Creating DSB...
DSA=00708C58, DSB=007094F0, Timer=0070A8D8

Here I get the file prompt, and choose a ROM image. After this it prints:

Restarting DSA...
Recreating DSB...
Restart done
Restarting DSA...
Recreating DSB...
Restart done
Restarting DSA...
Recreating DSB...
Restart done

Some of those repeated messages could be caused by me switching the active window back to the STDOUT process after the fMSX window gets stuck.

Quote:

Creating DSB... DSA=00708C58, DSB=007094F0, Timer=0070A8D8

These are CDirectScreenAccess and CDirectScreenBitmap objects. And the timer, of course.

Quote:

Here I get the file prompt, and choose a ROM image. After this it prints: Restarting DSA... Recreating DSB... Restart done ... Some of those repeated messages could be caused by me switching the active window back to the STDOUT process after the fMSX window gets stuck.

Yes, this is DSA shutting down and restarting as you focus in and out of the main AppView. Nothing suspicious here - it prints the same on my E70.

What I find unusual is that the printf() in the actual display update routine is not being executed. This makes me think that things crash when it wants to update the display. The next test version will have printf()s concentrated around the update code. And I am also going to enable fMSX Verbose variable just to see what the emulator thread is doing.

Let's continue via email, others are probably not interested in the details

I'm facing the same problem in fMSX (as well as the speccy emulator). The screen is extremely dark, I can barely read whats written... There's a way how to configure that? I was not able to find nothing.
My cell phone is a nokia e62.

Best Regards,

Quote:

I'm facing the same problem in fMSX (as well as the speccy emulator). The screen is extremely dark, I can barely read whats written... There's a way how to configure that? I was not able to find nothing. My cell phone is a nokia e62.

As far as I know, it is a firmware bug in E62. The phone tends to switch off the backlight for applications using direct screen access. Same problem has been reported with other applications. No fix so far, although upgrading firmware may help.

Well... When I saw your post at Google Groups, about updating the firmware, I downloaded everything from Nokia and the result was that I was already running the latest firmware...
There isn't a command or something to manually turn on the backlight?
like
if modelImRunning()=76 //e62
{
forcebacklight(1); //Here`s the light!
enablebacklightoptionmenu();
}