zett, I presume you mean the key on the left side of space? That's a colon (":") on my 9300 and pushing Chr with that key normally launches the internal help on the phone (there is a blue question mark on the key as well). I tried that while MSX80 was running, it doesn't crash the emu on my phone, it simply pauses the emulation and the emulator goes to background allowing the phone's help application to pop up. If you want to return to the emulator, press the Menu key and go to the task list (the left most item in the menu bar) and you should see MSX80 on the list, still running, so just choose that and you'll be thrown back to the emulator (in the MSX80 pause menu).
Do you have some specific games that don't work? Note that as the emulator uses a fixed memory slot layout some games refuse to work because the games have originally been programmed poorly (i.e. not adapting to different memory slot layouts). Also some games using some of the more seldomly used features of the VDP might not work because not all VDP features are supported by the emulator -- in the next version which is due to be released in the next few weeks hopefully some improvement in this area could happen as I have improved the VDP emulation a bit (still far from perfect though).
NYYRIKKI, I didn't mean you'd compile the emu but doing this would help me get started:
1. Create a directory for the SDK (let's call that C:\SDK for now)
2. Substitute a drive letter for the directory you just created (e.g. say "subst x: c:\sdk" in the command prompt)
3. Install the SDK on the substituted drive (x:\ in this example)
4. After installation has finished, make a zip (or whatever archive format) of the whole x:\ drive
5. Send the archived SDK to me 
The SDK will probably install stuff on your C: drive as well and make changes in your system registry and environment settings but I won't need that stuff, the contents of the substituted drive would be enough.
This way I don't have to install the SDK but I would still get the main contents of it. I understand if you don't want to get involved with the SDK installation, I don't like it messing up my system either
Yes, I can do that. Could you send me a link to the SDK. If something goes wrong I can always use system restore to get rid of the useless stuff.
Umm... not really, no. You could send it to my gmail account if you split it up to 5MB pieces or so BTW what does your system say when you say "devices" in the command prompt? Perhaps all that crap was only added later on and the first SDKs don't mess things up too badly... in which case I could install it myself.
It seems I easily end up refactoring lots of code whenever I touch something... I've been lately rewriting lots of stuff to improve MSX1 emulation speed while trying to keep MSX2 emulation speed at the level it was before adding the V9958 horizontal scroll support for MSX2+. I think I'm about to finish the refactoring but I'd like to get a lead on why the OS sometimes (read: often) deletes files from the emulator's data directory -- really annoying thing (this is MSX80 specific stuff). Now, I have to wonder if all this means the code is too low quality in the first place so I end up improving lots and lots over and over again, or, am I just never satisfied with anything?
Anyways, if I end up compiling a 92x0 version of MSX80, you'll probably have to try it out without me doing ANY testing as I don't have a phone to test that on and I can only see if it runs on the phone emulator on PC.
Umm... not really, no. You could send it to my gmail account if you split it up to 5MB pieces or so BTW what does your system say when you say "devices" in the command prompt? Perhaps all that crap was only added later on and the first SDKs don't mess things up too badly... in which case I could install it myself.
When I say devices, my computer says:
"devides ei tunnistettu sisäiseksi tai ulkoiseksi komennoksi,
suoritettavaksi ohjelmaksi tai komentojonotiedostoksi."
Hmm... I just took a look inside the directory stucture where the installation was made... It seems that there is some Zipped installation package together with some java stuff and documentation. How many times I'm expected to install this? I'll try to take a deeper look some day soon.
Anyways, if I end up compiling a 92x0 version of MSX80, you'll probably have to try it out without me doing ANY testing as I don't have a phone to test that on and I can only see if it runs on the phone emulator on PC.
I remember, that I sent you a suggestion in email to help you with this issue already long time ago. 
Thanks for the info and link, mars2k! I have added support for the 30/64/80-in-1 and 126-in-1 MegaROM mappers in the emulator although I couldn't test if they work as I don't have the ROM images of those to test the emulator...
NYYRIKKI, I think you didn't complete the installation yet. I downloaded & installed the SDK myself today and it's not the most clever thing I've come across. When you run the toplevel installer it just gives you a ZIP in the end, which, after the installer is done, you need to unpack yourself and once you've done that you'll notice that you have yet another installer which you need to run to actually get the stuff properly installed. But nevermind, I did all that already so I'll probably take a look at porting the MSX80 for 92xx phones later on when I get the next version of fMSX/S60 out -- which may take some time.
zett, the 9300 does not have a minus key on the keyboard at all, that's why you cannot get it in the emulator. But you can reconfigure the emulator's keyboard map if you need the minus key. Just go to control configuration menu, keyboard configuration and scroll down until you see the minus key. By default that is mapped to the phone's minus key but like I said, 9300 does not actually have a physical key for it eventhough the OS supports that key event. So you need to change that to some other key. Also note that when you do this you probably have to remove some other default key mapping as all the phone keys are by default already mapped to some MSX key and if you don't remove the duplicate key mapping for the MSX it will seem like you are pressing two keys simultaneously. To remove the duplicate mapping, just look through the list and find the duplicate mapping, go over it and press backspace on the phone. This will remove the key mapping for that MSX key. Perhaps I need to change this behavior in a future release so that duplicate mappings are automatically removed and thus it wouldn't be possible to define duplicate mappings at all.
Anyway I just put up the download for MSX80 release 2 today, it has a lot of internal changes, some of which are also visible Perhaps one of the most important things to notice is that for proper MSX2+ emulation you now need to have a 48kB sub ROM image instead of the old 16kB one. In practice this means that the sub ROM image needs to include both the actual MSX2+ sub rom and Kanji BASIC concatenated together. So don't try running MSX2+ emulation with the old 16kB MSX2+ sub ROM image, the emulator will probably crash if it doesn't first create some other havoc in the phone. See my MSX80 web page for a more complete list of changes http://personal.inet.fi/private/riihimaki/s80/