101010.pl

Wintermute_BBSOkay, I guess a video says more than words. Here's the <a href="https://oldbytes.space/tags/MSX" class="mention hashtag" rel="nofollow noopener" target="_blank">#MSX</a> <a href="https://oldbytes.space/tags/ROM" class="mention hashtag" rel="nofollow noopener" target="_blank">#ROM</a> of <a href="https://oldbytes.space/tags/PacMan" class="mention hashtag" rel="nofollow noopener" target="_blank">#PacMan</a> running on my <a href="https://oldbytes.space/tags/rc2014" class="mention hashtag" rel="nofollow noopener" target="_blank">#rc2014</a> - it's a <a href="https://oldbytes.space/tags/RomWBW" class="mention hashtag" rel="nofollow noopener" target="_blank">#RomWBW</a> machine with a <a href="https://oldbytes.space/tags/TynemouthSoftware" class="mention hashtag" rel="nofollow noopener" target="_blank">#TynemouthSoftware</a> <a href="https://oldbytes.space/tags/Joystick" class="mention hashtag" rel="nofollow noopener" target="_blank">#Joystick</a> module and the latest <a href="https://oldbytes.space/tags/TMSemu" class="mention hashtag" rel="nofollow noopener" target="_blank">#TMSemu</a> by <a href="https://oldbytes.space/@shieladixon" class="u-url mention" rel="nofollow noopener" target="_blank">@shieladixon</a> - no other MSX-related or otherwise "non-common" modules on the system.What the video shows is that <a href="https://oldbytes.space/tags/MSX8" class="mention hashtag" rel="nofollow noopener" target="_blank">#MSX8</a> is actually doing its stuff, running the original MSX game. But as you can also see, the player (Pac Man) is always moving up. I can make it go down, but as as soon as I release the stick, it goes up again. Also, I can only move up and down and this is done by moving the Joystick to either the left or the right.I have checked the MSX8 bios.asm code for the MSX8CPMRC2014 build of MSX8 BIOS and while it should be working, it isn't.I did hard-code the address of my joystick module ($01) at line 4848 in bios.asm to get the input from it, but somehow the mapping of the MSX specific "keys" or "inputs" like Up/Down/Left/Right is not properly working. Oh, and it seems that Fire Button 1 is always pressed as well.So, long story short: it should be possible to make MSX8 work without the need for special modules, but right now I'm a little lost as to how to modify the code to get proper input readings.P.S.: you can modify the bios.asm code to use W/A/S/D instead of a joystick jumping to KBDJSTK instead of JSTK. But even then the controls behave in the same insane way as explained above.Any help or even cooperation is welcome, let's make MSX games rock on RC2014 !!

Wintermute_BBSIs there anyone in the <a href="https://oldbytes.space/tags/RC2014" class="mention hashtag" rel="nofollow noopener" target="_blank">#RC2014</a> community who got <a href="https://oldbytes.space/tags/MSX8" class="mention hashtag" rel="nofollow noopener" target="_blank">#MSX8</a> up and running?

Wintermute_BBSOkay, so I tired this new program for <a href="https://oldbytes.space/tags/rc2014" class="mention hashtag" rel="nofollow noopener" target="_blank">#rc2014</a> which is called <a href="https://oldbytes.space/tags/msx8" class="mention hashtag" rel="nofollow noopener" target="_blank">#msx8</a> and will allow you to run a selection of <a href="https://oldbytes.space/tags/MSX" class="mention hashtag" rel="nofollow noopener" target="_blank">#MSX</a> <a href="https://oldbytes.space/tags/Game" class="mention hashtag" rel="nofollow noopener" target="_blank">#Game</a> <a href="https://oldbytes.space/tags/ROMs" class="mention hashtag" rel="nofollow noopener" target="_blank">#ROMs</a> on your system if you have a <a href="https://oldbytes.space/tags/TMS9918A" class="mention hashtag" rel="nofollow noopener" target="_blank">#TMS9918A</a> video module and a <a href="https://oldbytes.space/tags/AY38910" class="mention hashtag" rel="nofollow noopener" target="_blank">#AY38910</a> sound module.So I fetched the latest sources and built a set of fresh binaries for my system, including the dummy MSX-US.ROM file you need where I adjusted the IO port address of my AY38910 module ($D8).Now, the initial screen loads but then the system freezes. No sound, not reacting to keypresses.Anyone got an idea?!EDIT: I may have found a possible answer here (<a href="https://hackaday.io/project/190408/instructions" rel="nofollow noopener" translate="no" target="_blank">https://hackaday.io/project/190408/instructions</a>) which states that a Rev. 6 <a href="https://oldbytes.space/tags/AY38910" class="mention hashtag" rel="nofollow noopener" target="_blank">#AY38910</a> <a href="https://oldbytes.space/tags/module" class="mention hashtag" rel="nofollow noopener" target="_blank">#module</a> is required, which allows for MSX <a href="https://oldbytes.space/tags/IO" class="mention hashtag" rel="nofollow noopener" target="_blank">#IO</a> <a href="https://oldbytes.space/tags/Ports" class="mention hashtag" rel="nofollow noopener" target="_blank">#Ports</a> - Rev. 5 boards (like the one I have) do not support these.p.s.: I'm running a <a href="https://oldbytes.space/tags/RomWBW" class="mention hashtag" rel="nofollow noopener" target="_blank">#RomWBW</a> system here.p.p.s.: project repo is here -> <a href="https://github.com/lesbird/MSX8/tree/main?mc_cid=e127d99778" rel="nofollow noopener" translate="no" target="_blank">https://github.com/lesbird/MSX8/tree/main?mc_cid=e127d99778</a>

Recent searches

Search options

Administered by:

Server stats:

#msx8