For MSX1 cartridge games, you need only one system ROM ("msx.rom" or "msx.rom.gz" if it's compressed). Just make sure you have that and it is installed under "/system/apps/fmsx/rom" directory on your phone. Cartridge files should be installed under "/system/apps/fmsx/data" directory. You can check that the paths are correct in the .pkg file that comes with the tools. The .pkg file is basically a layout for the .sis file and it lists what files to install and where. If you can successfully create a .sis file with the system and game ROMs you want, and the emulator is still not working after you install your .sis file, it most probably means you have a wrong system rom file or it's in the wrong place. The correct MSX1 system ROM is 32kB uncompressed.

Sousuke's GUI tool should be easier to use, if the links worked :/

thnx man, it works,

Quote:

Sousuke's GUI tool should be easier to use, if the links worked :/

Sorry, had some problems with my old provider. Will be fixed soon (I hope), until then, I've set up a mirror on: www.Sousuke.org

Or here's a direct link to the GUI: Here

Thank you so much jr for this fantastic emulator! There are two major problems still, though:

1. Could you implement a text input? Like where you get to type a string and then send it to the emulator (I want to summon the guardians in Maze of Galious!)

2. The new version, 1.04a, seems to lose save states somehow. First I kept copying save states to different dirs when I wanted to play some other game, and then copy them back and it worked ok. But now it looks like especially MSX2 save states can suddenly cease to work Maybe it doesn't like that somebody switches to MSX2, MSX1 and back to MSX2?

Shocky, I'm glad you've found the emulator useful. The text input (or keyboard macros) has been on my to-do list for a long time... maybe it would be time to implement it finally. I'll give it a try for v1.05.

When a save state is created, the emulator calculates a checksum of all system and cartridge ROMs currently loaded. This checksum is also generated when you try to load a save state, and if it's not the same as in the save state file, loading fails. So it's not just the MSX system (1/2/2+) and the game ROM(s) that you need to have set up correctly, but also all other system ROMs must be similar (and RAM/VRAM sizes, since the save state contains RAM and VRAM contents). One trick is to make sure you have the same disk settings active as well - this is because Disk ROM is only loaded if you have "inserted" a disk, but having Disk ROM obviously has an effect on the save state checksum even if you are playing a cartridge game. Furthermore, disk and tape "autorun" options also have an effect. Basically all settings (except for keyboard/joystick configuration) should be exactly like they were when creating the save state in order to be able to load it again. So... what I'm saying is that maybe you have altered some other settings in between and that's what making the save state "unloadable".

Perhaps I could remove the ROM check and just see if RAM/VRAM sizes are correct. That would then enable you to load a save state created when playing Penguin Adventure while playing some other game. I'll think about that.

Anyway, I might implement an option in v1.05 to use game specific save states. Initially I left this out to save space on the phone, but having it as an option could be useful. The only problem is that the save states would be left sitting on your phone until you delete them manually using some file manager software unless I create a separate UI in the emulator for managing the save states...

I suggest you do implement that ^_^... A friend of mine has a Nokia 6600 with a 512MB memory card, so that will do the trick ... 2bad I still own a crappy motorolie V150

Allright, v1.05 has been uploaded. Note that the keyboard macros only support ASCII characters 32-126, and if you're using a ROM with other than US keyboard layout, prepare for problems I didn't test the macro system on any game, just in the BASIC prompt - BTW, a "nice" way to run BASIC oneliners, lol. even if I set the maximum length for a macro to 100 characters. Hopefully the speed at which the "macro cannon" writes is not too fast for games.

Don't be alarmed if you're using the multiple save states option and when starting with a game that has a save state, a new dialog pops up asking if you want to restore the saved state while the regular emulator UI in the background disappears (probably showing up application icons or something). I will fix that later in v1.06, it's just a cosmetic obscurity.

Hmm... what else... right, I removed the ROM checksum from the save states, perhaps it helps someone. It then also makes it possible to load a save state that was created with different carts/disk/tape inserted.

Have fun, hopefully I didn't put too many new bugs in

I don't know if it's a bug, but whatever i do, i don't get sound to work on my Sendo X. Version1.04 crashed when i enabled sound support. Good thing is, it doesn't crash anymore when i enable it

I didn't even know it works on Sendo X

According to the fMSX/S60 website, it does. Sendo X is stated in the list of gsm's.

Well, I have to honest with you. I haven't really tested the emulator with all the devices I'm listing on my web page. At the moment I'm only testing the A version on a Nokia 7650 and the B version on a Nokia 6600. But since Series 60 is a platform, the emulator should run on any phone running Series 60.

I only recently added the device lists, based mostly on device specifications and other information I've heard about the devices. So some devices COULD be in the wrong category, but I tried to be careful. The main purpose of adding the lists was to aid in choosing the right version of the emulator. Otherwise everybody tried the B version (because b > a, I think), which doesn't work in most devices (so far). There might even be more Series 60 compatible devices out there that I haven't listed because I might not have heard of them all But it also means I haven't seen it work on all the listed devices, sorry.

Anyway, the fact that it runs on your Sendo X is already great news to me The sound emulation is the most picky part of the emulator, it assumes things about the hardware and only supports one configuration. This is mainly because I wanted to optimize the playback routines, the other reason is I was too lazy to write support for several configurations...

I just changed the sound initialization routine in v1.05 as I noticed there was a race condition between two threads that could cause a crash. Apparently this was useful if it was crashing with your phone before.

Currently the emulator requires that for display, your phone has a 12bit (4096) or 16bit (65536) color depth screen mode available, and for sound, that 16bit mono PCM audio output at 8kHz sampling rate is supported. If sound is not working, my first guess would be that Sendo X does not support the above mentioned parameters.

Would it be possible to generate the audio at 16kHz? Getting nicer sound from the emulation, jr?
But guess it won't make that big difference, because the audio output of these phones isn't meant for HiFi-sound Unless you use a headset..
Is it possible to implement a small detection routine for headsets? Plugging in a headset, and then disabling the main speaker. Sometimes I don't want to disturb others while playing on my 'mobile' MSX

Btw, I'm thinking about getting a newer phone soon. Do you or does anybode here perhaps know whether the CPU will also be the same? Or are they a bit faster?

Ah yes, nearly forgot, unfortunately have to bug you with another new issue in the emulator: When I insert a (compressed) 720k disk-image, the emulator crashes when I try to start the emulation.

Well, you know what, there seems to be a fatal bug in the MSX ROM management code that I rewrote recently. The reason for your crash is that the disk ROM loading fails. I fixed the bug and since this really is a critical one I'm releasing v1.06 today to fix this.

And yes, it would be possible to generate sound at 16kHz (on devices that support it, of course). I'll put that on my to-do list for something to consider in the future. I'll take a look at your request about the headset support, but if I recall right, audio routing is automatically done by the operating system and I shouldn't be doing anything preventing that.

http://www.peroon.co.il/s2u.html O