I've just tested the latest version here on Philips_NMS_8245 with MFRSCC+ SD and it works.
I have this launch message:
Mapper type: Konami
ROM boot address: 4010
Device: MegaFlashROM SDD+ SD
Device slot: 1-1
Device capacity: 2048KB
All settings are set to defaults (nothing changed).
Just ensure that all your SofaRun options (including the "global" ones) are set to default, and send me your launch message if it does not work (maybe be sure to use the latest version for the ROM, maybe some fixes have happened ?).
I've just tested the latest version here on Philips_NMS_8245 with MFRSCC+ SD and it works.
I have this launch message:
Mapper type: Konami
ROM boot address: 4010
Device: MegaFlashROM SDD+ SD
Device slot: 1-1
Device capacity: 2048KB
All settings are set to defaults (nothing changed).
Just ensure that all your SofaRun options (including the "global" ones) are set to default, and send me your launch message if it does not work (maybe be sure to use the latest version for the ROM, maybe some fixes have happened ?).
Sorry I forgot to mention, I tried it in Zemmix FPGA, so probably the error is that the game needs a real flash cartridge like MFR or C2, right? Some fix that could be done to load on OCM devices?
Hello, the OCM flash device works, it seems that the problem could be the mapper itself. Just tried Knightmare, if I load with default options it identifies it with Linear mapper. Works fine with OCM flashing device. If I force to Konami mapper, it doesn't work. Same test done with TwinBee with the same result.
I've seen one thing. You said that the initial address should be 4010? It always try to boot in 40B1 (linear or Konami), but in Linear mapper mode it works and in Konami mapper mode it doesn't.
I have a Carnivore2 and together with SofaRun it's just an amazing experience. A question I couldn't find yet (probably search didn't want me to find it): I have an 8GB CF card, which has one 4GB partition on which I run SR and have my roms. I use ZIP files with maybe 100 files in it. The thing is, when I press enter on such zip, I see the CF-read-led light up for about 5 seconds, before SF shows 'opening zip file'. The zip-opening itself is pretty quick, but I wonder why it takes so long to 'start' opening it?
I more or less see the same in MSX-DOS, when I dir, it's fast but when it reads the free disk space it takes several long seconds.
So, is this due to maybe a too large partition, ie. should I better make 2 2GB partitions? Nextor FDISK auto-suggests a 4GB partition, which is why I created that. Or is it just what's to be expected from a stock 3.57Mhz NMS8250?
[edit]
never mind. There seems to be an issue with my main CF card. I took an identical CF, created a 4GB partition on that as well, copied the exact content over and that one works way faster. Solved!
Nice one! But while the function works (reporting 32MB free) it doesn't speed it up anything at all. It still hangs seconds on 'reading' the free disk space.
Nice one! But while the function works (reporting 32MB free) it doesn't speed it up anything at all. It still hangs seconds on 'reading' the free disk space.
Hmm... Usually it helps at least a little... How about if you try SET ZALLOC = ON ?
