Tales of Popolon (new MSXDev'17 entry)

Página 5/20
1 | 2 | 3 | 4 | | 6 | 7 | 8 | 9 | 10

Por santiontanon

Paragon (1486)

Imagen del santiontanon

22-03-2017, 13:21

@ARTRAG no, I haven't tried it! Added to my "to do"! will check it out over the weekend, thanks for the link! Big smile

@journey, @wyrdwad: sorry to hear that! I have not done much testing with computers other than MSX1, but I'll do some testing over the weekend. It might be the RAM. The game uses RAM all the way to address 0xED6D, which has been safe in all MSX computers I've tried so far, but might be too high for an MSX2 or higher. Let me experiment and if this is the problem, let me see if there is any way to reduce RAM usage Smile

Por Louthrax

Prophet (2406)

Imagen del Louthrax

22-03-2017, 14:03

journey wrote:

Hi all,

with OCM via ROMLOAD, the game runs correctly, but with MSX TurboR+MFRSCC+SD via SOFARUN i'm not able to run the game...

someones could help me? Louthrax?

Got a black screen here too, checking that. Maybe because the ROM is in a RAM slot...

EDIT: Ok, I've found the problem: the stack pointer is not set at the beginning of the game (it's not always at F37F or whatever address). Santiontanon, you should maybe set it explicitely at the beginning of the ROM ?

Por santiontanon

Paragon (1486)

Imagen del santiontanon

22-03-2017, 16:20

oh! really? is it necessary to set the stack pointer? didn't know that! Added to the to-do list! Thanks!

Por Louthrax

Prophet (2406)

Imagen del Louthrax

22-03-2017, 16:34

Yes, I'm sure the problem mentioned by Wyrdwad will be solved too. If another cartridge boots before your game, it might allocate upper-RAM for its use, and decrease the stack pointer accordingly. You can set the stack pointer at a higher value if you need it, but you should not use non standard BIOS features, like accessing disks. Normal strict-BIOS RAM starts at 0F380h IIRC, so the instruction to add should be "ld sp,0F380h".

Por ARTRAG

Enlighted (6543)

Imagen del ARTRAG

22-03-2017, 17:03

If you set manually the stack at f380h and do not use disks or other bios functions except for vdp and psg access you should be safe

Por Louthrax

Prophet (2406)

Imagen del Louthrax

22-03-2017, 17:19

I guess most (all ?) MSX1 BIOS functions (tape, keyboard, joysticks, etc...) should work, no ?

Talking about joysticks, that's something I really like, I mean, if there still a few bytes left for it Smile

Por santiontanon

Paragon (1486)

Imagen del santiontanon

22-03-2017, 17:23

Ok! then I'll add that stack initialization. I have a couple other changes that I want to finish today, if I can get all done, I'll upload a new version with this fixed, turbo R support and a "pause" key.

About joysticks, that should be already supported (let me know if it does not work). The only things you cannot do with joystick is switch weapons/armors (for that you still need to use the "1", "2" and "3" keys in the keyboard).

Por Daemos

Paragon (1952)

Imagen del Daemos

22-03-2017, 19:07

Beware. Relocating the stack on a sony hf500p will cause the machine to go nuts. This happens on the daewoo cpc as well. If it doesn't in your situation please let me know how you did it.

Por Louthrax

Prophet (2406)

Imagen del Louthrax

22-03-2017, 19:33

Daemos wrote:

Beware. Relocating the stack on a sony hf500p will cause the machine to go nuts. This happens on the daewoo cpc as well. If it doesn't in your situation please let me know how you did it.

Even if you just use standard MSX 1 BIOS functions?

Por santiontanon

Paragon (1486)

Imagen del santiontanon

23-03-2017, 03:19

I just tried in a Sony HB F500P in OpenMSX, and Daemos is right, I just get a blue screen if I reset the stack! It does work if you hold SHIFT while booting though...

Página 5/20
1 | 2 | 3 | 4 | | 6 | 7 | 8 | 9 | 10