Symbian emulator?

Yep, I'm not building new versions of the emulator for S60 1st edition anymore so version 1.07a of the emulator is the latest version for those devices. I'm also seriously thinking to stop building for 2nd edition devices (the "b" and "c" versions of the emulator) as well since not all the stuff I have implemented lately would have any meaning for the 2nd edition devices because of the small screens and also because some of the new stuff actually causes some performance penalties in the emulator which might not be that big of an issue with new, fast phones but with a little bit older models the impact might be bigger.

erikd, I've changed the memory layout for the MSX1 machine in the emulator for the upcoming version (1.14d) so that the machine does not have any subslots. This should help with a lot of (cracked) disk games because many of those tend to assume things about the RAM subslots. With the new setup RAM is in a primary slot so these poke-1 things aren't first of all needed and secondly also don't have any side effects so a "wrong" poke-1 command doesn't harm you.

About the Disk ROM issue, does the amount of free RAM change at all whether you keep the Ctrl pressed or not?

About the problems with the save states -- does the problem appear when you launch the emulation with a save state or when you pause the emulator and load a save state from the pause menu or in both cases?
Both cases for me (not 110% percent sure about when launching the emulator though, only about 99).

About the Disk ROM issue, does the amount of free RAM change at all whether you keep the Ctrl pressed or not?
No, for me it doesn't. However, I did notice that the CTRL key works in basic (I think CTRL+M or something makes the cursor jump to the lower right corner, just like on MSX), so I'm kind of stumped with this.

When does it crash? When you press the 0 key when doing the keyboard mapping or when you launch the emulation or at some other point?
It seems the crash is related to resetting the controls somehow as it always and only happened when I reset the controls and remapped a key before starting emulation. But my setup seemed to have been screwed because fmsx/s60 compained at one point about a corrupt config. I reinstalled and I didn't experience the crashes anymore. But still, booting with CTRL doesn't work for me...

As far as I can recall all this: save state lock ups always happened when initially loading a game/save state. So it didn't lock up when I paused the emulator.

Ok I just uploaded v1.14d to my web page. I believe I implemented all recently suggested features except for the multiple save state slots per game, I'll see about that in the next version. But state quick save&load is there, alternate keyboard/joystick mapping quick swapping, phone memory / memory card selection and of course support for E61 via display double buffering. I also fixed a bug in the state loading routine when launching the emulator directly with a saved state, it should work better now so I hope it addresses some of the issues you've had with the save states.

Some new stuff which wasn't asked for but I thought would be nice: support for .zip file format and "archive as disk" virtual disk image format support for .zip archives, i.e. you can just drop the MSX files as is on a .zip file (named blabla.dsk.zip) and the emulator will automatically construct a disk image in RAM containing the files in the zip. I was about to include support for lzh/lha file format as there are quite many games floating around in lzh archives but decided to postpone that to the next version to get this version out now...

Remember that MSX2+ emulation now requires that the msx2pext.rom has both the MSX2+ sub ROM and Kanji BASIC concatenated together forming a single 48kB ROM image.

I've also rewritten some 50,000 lines of code for the display emulation so watch out for bugs But when it works at least the MSX1 VDP emulation should be faster than before. Also a little bit more complete V9938 and V9958 emulation.

The SIS tools on my page don't work for the 3rd edition of S60 (i.e. the "d" version of the emulator) due to the added level of security in the OS. This is also the main reason I changed the location of the data files in the "d" version of the emulator. You should be able to put all system ROMs and game files to your phone without any special tools since the emulator's data files are located under a folder which is visible through the phone's PC Suite software or USB mass storage. In other words, you don't need to create separate SIS files for the system ROMs and MSX game files -- instead, just copy the necessary files directly to your phone to the correct location. I'll try to outline what, where and how below:

- An example of what to do if you're using Bluetooth and PC Suite:
1. Connect your phone to the PC Suite over Bluetooth normally
2. Open Windows Explorer and navigate to your mobile phone, open either Phone memory or Memory card depending on which location you wish to use for storing the MSX files
3. Locate a folder called "Games" and inside you should find a folder named "fmsx" if you have launched the emulator at least once
4. Copy all your system ROMs to a folder named "systemroms" inside the "fmsx" folder (create the subfolder if it does not already exist)
5. Copy all your MSX game files to the "fmsx" folder
6. Now you're all set, just launch the emulator on your phone

- Another example of what to do if you're using USB without PC Suite:
1. Connect your phone to your PC with the USB cable
2. Select USB mass storage from your phone when it asks for connection type
3. You should now have your phone's memory card visible in Windows Explorer as a removable drive, just navigate there and follow the instructions above from point 3 onwards

I'll try to put up a new version (1.15d) of the emulator for download soon with some new features and a bug fix for a nasty fault in the V9938/V9958 search command emulation.