The "Made in Spain" game.
These are tape to ROM conversions...
The nice thing about these conversions is that they actually work on 2+ and TR machines, unlike their tape versions.
I check Abu Simbel using openMSX debugger and MFR SCC+ SD emulation. It seems that the problem is in the RAM selection rutine.
On turbo R the main RAM selected by default is the internal RAM. The conversion searchs for RAM and tries to set that slot on all pages. When it tries to change the RAM slot on page 3 (it is the internal RAM slot by default), the code changes first the main slot (so ROM is set on page 3, where the rutine is) and then it would try to set the subslot, but it hangs since the code is not visible anymore.
Probably on non turbo R machines you will not have this problem.
You can check it using BlueMSX. Set Abu Simbel ROM in slot 1, set RAM expansion (i.e.: 512K RAM) in slot 2. The game will not run on turbo R.
If you want to play the game on real hardware just load the game using /U and disable the RAM expansion fron recovery.
Thanks for taking a look, Guillian.
I tested the following configurations in openMSX with an emulated A1ST:
1. Abu Simbel in openMSX slot 1, ram512k expansion selected (presumably in slot 2). The machine boots with 768kB, but the game boots and works fine.
2. Abu Simbel flashed with opfxsd /u using an emulated MFRSCC+SD w/ 512kB RAM. The machine boots with 768kB, but the game hangs on the splash screen (although the red/green colors do still twitch when I unthrottle, which is odd).
3. Abu Simbel flashed with opfxsd /u using an emulated MFRSCC+SD and no RAM. The machine boots with 256kB, but the game hangs in the same way.
I then tested these three configuration on openMSX in an NMS-8250 and saw exactly the same results.
So I guess I'm not seeing what you're seeing?
So I guess I'm not seeing what you're seeing?
What version of openMSX are you using?
I'm using: openmsx-0.12.0-146
Latest official release.
O:\Games\Emulate\MSX\openmsx>filever openmsx.exe
--a-- W32x64 APP - 0.12.0.1 shp 6,806,016 09-15-2015 openmsx.exe
I can upgrade to a more recent build, if that would help.
@Guillian:
Okay, with the build you mention, I'm now seeing what you're seeing. And when I try it in a real ST, both the Profanation and Mad Mix 2 roms work fine (my MFRSCC+SD has no RAM). So I think I was seeing some old openMSX bug, and everything is working fine with opfxsd.
That said, one last question: when a PlaySoniq is installed in slot 2 (adding an external memory expansion) even flashing with /U doesn't allow Profanation to run. Is that expected?
(Aside: Profanation in R800 mode is _hard_.)
That said, one last question: when a PlaySoniq is installed in slot 2 (adding an external memory expansion) even flashing with /U doesn't allow Profanation to run. Is that expected?
Yes, because the problem is in Profanation RAM selection rutine.
If you insert a memory expansion on a turbo R the game will not work.
Just try it on BlueMSX emulating a turbo R (openMSX does not seems to reproduce the bug)
Insert Profanation in slot 1, run the game and it works.
Insert Profanation in slot 1, insert memory expansion in slot 2 and run the game and it does not work.
That's weird...! Any idea what's going wrong in openMSX?
Did you also try with an emulated MFR SCC+ (SD)? Perhaps the case is just a bit different.
Hmm, I just tried and it works fine in openMSX. Any help to debug why this is happening is highly appreciated.