I also tried in MSX1 mode, and then it shows '23430 bytes free', whether I press CTRL while booting or not. I guess with CTRL it should be somewhere between 24000 and 25000.

I just tried this on my E70 and the CTRL works just fine, 24990 bytes free in BASIC.

One possibility *might* be that you have the phone key which you are using for MSX Ctrl key mapped to several MSX keys and the Disk ROM might not accept this because for the MSX it would look like you would be pressing Ctrl and some other keys at the same time.

This is how I tested it: first I reset the controls to defaults, then I went to keyboard configuration, removed the keymapping for the MSX '0' key (by default this is mapped to the phone's '0' key). There are two Ctrl key mappings in the emulator so in fact it is possible to define two separate keys that both look like Ctrl for MSX. By default these mappings are mapped to Symbian OS left ctrl and right ctrl keys, which of course do not exist on most phones at all. I changed one of these to the phone's '0' key, the other mapping I left as it was. Now with this mapping, the phone's '0' key should have only one meaning and that is the MSX Ctrl key. I launched the emulator with an empty DSK file (MSX1/60Hz config with no other options enabled and no cartridges inserted) and kept '0' pressed until I reached BASIC and got 24990 bytes free.

Thanks for your reply!
I think I didn't have double key mappings, but just to be sure I followed exactly what you did.
The strange thing is that if I reset the controls and map the phone's 0 key like you described, fmsx/60 crashes. Really weird...
So I tried the same with another key (the 1 key), and it didn't crash anymore, but CTRL still didn't work. Even tried another disk rom, but still no success...

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?

Ah yes, I wasn't very clear. It crashes as soon as I press the 0 button while in the emulator, not in the front end.

hi,
the first thing: i am german, so don't matter, if my sentences doesn't make sense^^

my problem: i made a sis-file with the game metalgear1.rom. i transfered it to my nokia 7650 and opened it. now i can listen to the sounds of the game, but the graphic is "strange" have a look: http://img250.imageshack.us/img250/3453/msx1metalgeariw1.jpg
i can't recognise anything but some coloured squares and rectangles...
my preferences:
machine type: msx1
cartridge a: metalgear
rom mapper a: generic/8kb (i also used the others e.g. konami5/8kb etc...)
the other preferences i didn't change.

i have also tried the emulator with the game metal gear 2 and msx2 but then the game doesn't even start. i can just watch the msx2 animation twice and then i can write in the bluesreen whatever i want...but i can't play
maybe i did a mistake with the creation of the install packet (.sis) here you can see the code: http://xup.raidrush.to/ndl_432797e9e974956a8cbebbf95bf86/

in the 2nd and last line you can see that i have changed the ",1,10,0," to "1,07,0" because i could't even install the emu until i changed that.


...so i hope
you could understood my problem^^
&
somebody can help me

gr33tz

hakunamatata

// maybe somebody else had the same problem as i but there about 47 pages in this thread and english is my 2nd language....so it is a bit difficult to me to read through all these posts...

Metal Gear is an MSX2 game, so you need to set the machine type to MSX2.
As for Metal Gear 2, try to use the ROM version instead of the DSK version (if you didn't already). I found that many DSK images don't work with the emulator (although I'm not sure if Metal Gear 2 is one of them). For me, Metal Gear 2 works fine (tried the english translated ROM version myself).
Maybe you could also try the latest version of fmsx/s60.

thx for reply
metalgear is running now with msx2 but mgs2 isn't and i'm already using the rom-version.
do you use "fmsxs60_107a" that's only for symbian handys 1st edition. if you do, could you give me your sis-file?
or the pkg-file would be even better, then i could see where i made a mistake...

That's strange.. MG/MG2 should work fine with fMSX/S60 v1.07a. At least when the ROMs are ok.
Your pkg file looks just fine. Nevertheless, try to repackage the files and reinstall it. And to be 100% sure, check the files in a PC emulator.

If you want, I'll grab my 7650 and try it on my phone.

Hakunamatata: I use 1.13d on an N73. If I were you, I'd upgrade to the latest version of fmsx/s60 for your phone and see if that solves it. In any way, it will be much easier for the author of the emulator to track down bugs if you report problems against the latest version.

It seems Hakunamatata uses wrong mapper type.

Could be. When I set the mapper type to automatic, Metal Gear 2 works just fine.

Quote:

Could be. When I set the mapper type to automatic, Metal Gear 2 works just fine.

that's it.
i had to set the mapper to "auto detect". now it works *yeahaaa*

i cannot install the latest version on my 7650...but i'm happy, now *g*

thx for help

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?