blueMSX status

Pagina 6/6
1 | 2 | 3 | 4 | 5 |

Van sdsnatcher73

Paladin (808)

afbeelding van sdsnatcher73

25-09-2019, 06:22

ducasp wrote:
gdx wrote:
ducasp wrote:

This is about the ram memory of the console, the real one initializes even bytes of internal console ram to 00 and odd bytes to 0xff? Is that all needed?

From what I remember, I saw that in an emulator but I do not remember which one. I would like to know how OpenMSX initializes the RAM of Coleco.

A quick look at it (really quick), it doesn't seem to be anything special, it seems to just use RAM the same way it uses MSX RAM, doesn't seem to be a distinction of any kind. I'll confirm tomorrow using the debugger of OpenMSX...

I think you have to look in the machine XML to see if there is a initial RAM content defined. I remember Manuel did it for the Yamaha CX-7/128, so you can look at that machine XML for how it is done.

I do wonder how the RAM gets initialized on these machines (Coleco and MSXs). It is not done by the BIOS apparently as otherwise it would be done by the emulator when it goes through the BIOS start up routines.

Van gdx

Prophet (3321)

afbeelding van gdx

25-09-2019, 09:57

I verified. OpenMSX fills the RAM with FFh to initialize it. So I re-tried Threshold with the RAM filled with FFh and it worked this time. I have probably done a bad handling last time.

Van Manuel

Ascended (16152)

afbeelding van Manuel

25-09-2019, 09:55

Yes, by default, openMSX initializes all RAM with 0xFF and if another pattern is needed, it can be specified in the hardware configuration XML file, as sdsnatcher73 already indicated.

Is it known what the initial RAM pattern is of the ColecoVision?

Van ducasp

Master (232)

afbeelding van ducasp

25-09-2019, 15:19

gdx wrote:

I verified. OpenMSX fills the RAM with FFh to initialize it. So I re-tried Threshold with the RAM filled with FFh and it worked this time. I have probably done a bad handling last time.

Try this:

https://github.com/ducasp/blueMSX/tree/master/Compiled%20Exe...

Just rename your original blueMSX executable to back it up and use the one in there instead (Release usually is the best).

I've changed the code so board initialization of ColecoVision type or Coleco Adam type will make sure all ram is initialized as 0xFF instead of not being initialized (meaning its value is 0x00). Worked fine on Smurf, and I really can't afford playing more of it.... oO Please check on other games to make sure it doesn't break anything.

Van ducasp

Master (232)

afbeelding van ducasp

25-09-2019, 16:06

sdsnatcher73 wrote:
ducasp wrote:
gdx wrote:
ducasp wrote:

This is about the ram memory of the console, the real one initializes even bytes of internal console ram to 00 and odd bytes to 0xff? Is that all needed?

From what I remember, I saw that in an emulator but I do not remember which one. I would like to know how OpenMSX initializes the RAM of Coleco.

A quick look at it (really quick), it doesn't seem to be anything special, it seems to just use RAM the same way it uses MSX RAM, doesn't seem to be a distinction of any kind. I'll confirm tomorrow using the debugger of OpenMSX...

I think you have to look in the machine XML to see if there is a initial RAM content defined. I remember Manuel did it for the Yamaha CX-7/128, so you can look at that machine XML for how it is done.

I do wonder how the RAM gets initialized on these machines (Coleco and MSXs). It is not done by the BIOS apparently as otherwise it would be done by the emulator when it goes through the BIOS start up routines.

Yeah, had done that and checked the ram code, but it was late night, so just did not want to tell it was like that for sure. Fun thing, edited my openmsx coleco machine to initialize ram with 00 and boom, there we have the ghost sprite in the second time visiting the Castle. So, it is in fact the ram initialization to 00 (or not initialization) that created this effect, as it was reproducible on OpenMSX as well. Cool

Van gdx

Prophet (3321)

afbeelding van gdx

28-09-2019, 09:31

Thanks ducasp. I tried thirty games they work well.

BlueMSX has a limit of 255 files in its folders. Above, it bugs. This is especialy problematic for the folder /Machines. Do you think it's possible to fix that?

Van ducasp

Master (232)

afbeelding van ducasp

28-09-2019, 17:05

Can't guarantee that'll do that right away, but you can open an issue on my bluemsx repository in github so this is not forgotten, and whenever I have some time or need to "breath" a little doing something else, I can look at it (or perhaps someone else look at it and decide to fix and make a pull request, help is always welcome as I'm working on it mostly for my needs and in my spare time). Smile

Pagina 6/6
1 | 2 | 3 | 4 | 5 |