Strange issue on real HW
I had the same result disabling the code in the isr for vblank
so the issue has to be on line interrupt code
I'll try it asap. Awesome smooth scroll for screen8 BTW.
Checked it on Turbo R st and HB-F1XDJ.
Turbo R crashed as expected.
HB-F1XDJ played music on a black screen.
Can try on FS-A1WX and NMS 8250 (with and without 2+ and other expansions) if you want to. Have to do some moving for that...
Thanks for testing
I would like to know what does the rom do on a plain msx2 with v9938 even if I do not expect anything different. ..
I still am clueless
On my bluemsx 2.8.2 it crashes on all setups I've tried. TurboR seems to get a few frames further but still hangs, MSX2+, MSX2 (several models selectable like german / japanese) all crash after about 1 second. I'm not sure what exact type each default BlueMSX type emulates though.
You shoul re-install blueMSX, because it should work without any problem in the emulator. Anyway, as Artrag has precised it, the problem happens only on real hardware, so it means that something is not yet emulated.
BlueMSX is a magic emulator. It runs the games that should not work.
This is a real problem for debugging.
In this case submitted by Artrag, openMSX is also a magic emulator !
@mars2000you
I don't install BlueMSX, I just use the ZIP file, and have it on a share to be able to run from more clients. I found the issue in my case though. I have BlueMSX emulation configured at 60Hz. That makes it crash. When set to auto or 50Hz it works fine. That might be the issue with TR as well, aren't they always running at 60Hz?
@Rataplan : on my system, it does not crash on MSX2+ or TurboR and I use the emulation in Auto Mode for the VDP frequency (automatically 60 Hz for Japanese machines). As you use the ZIP version (unzipped, I guess), I recommand to clean the SRAM sub-directory (delete all files) and to delete the bluemsx.ini file before starting again the emulator.
Besides, as indicated in the manual, using 50 Hz or 60 Hz modes in stead of Auto mode can have unexpected effects. So, it's not recommended, but sometimes useful (example : the IO demo, because the internal switcher to 50 Hz of the demo does not work on blueMSX).
