MSX1 Memory Mapper

صفحة 12/20
5 | 6 | 7 | 8 | 9 | 10 | 11 | | 13 | 14 | 15 | 16 | 17

بواسطة madscient

Master (193)

صورة madscient

23-02-2016, 06:52

This is my point of view and what I meant:
I don't mind that an application uses mapper exclusively with direct register writing .
Even though it uses mapper thus, it is not allowed to read register in any case.
Regardless whether the mapper was implemented internally or externally.

In other words, an application using mapper should suppose to be run on multiple mapper environment, to avoid hardware fault and malfunction itself.

بواسطة gdx

Enlighted (6071)

صورة gdx

23-02-2016, 09:24

tvalenca wrote:

3) Make your memory mapper registers readable because no one is going to fix all the legacy programs.

If we make all mapper with memory mapper registers readable then we must remove the additional cartridges when more than one Mapper are inserted to use programs that read the registers. Otherwise it is most likely that any program can not find the corresponding Mapped.

بواسطة Grauw

Ascended (10699)

صورة Grauw

23-02-2016, 10:29

gdx wrote:

If we make all mapper with memory mapper registers readable then we must remove the additional cartridges when more than one Mapper are inserted to use programs that read the registers. Otherwise it is most likely that any program can not find the corresponding Mapped.

Most likely? Are you sure? I’ve never had problems using my 2 MB mapper with readback into my Philips NMS 8245 with 128K RAM with readback.

I don’t think there’s any such problem providing readback in external memory mappers.

بواسطة gdx

Enlighted (6071)

صورة gdx

23-02-2016, 11:02

This is just a translation issue. "Most likely". Everything depends on the configuration.

بواسطة madscient

Master (193)

صورة madscient

23-02-2016, 11:24

The mapper segment is configured at booting up as below:
Page0: Segment 03
Page1: Segment 02
Page2: Segment 01
Page3: Segment 00

This configuration is defined as the spec, so an application useing mapper can suppose this condition at the start time.
As has been mentioned repeatedly, there is no need to read mapper register in any case.

بواسطة gdx

Enlighted (6071)

صورة gdx

23-02-2016, 11:46

Yes of course. We only speak for the case of existing programs that read the registers.

بواسطة tvalenca

Paladin (747)

صورة tvalenca

23-02-2016, 11:58

madscient wrote:

(...) This configuration is defined as the spec, so an application useing mapper can suppose this condition at the start time.
As has been mentioned repeatedly, there is no need to read mapper register in any case.

This way we're going to allow new programs reading mapper registers to be written. If you don't create new programs, even if you don't fix the old ones, they tend to "disappear" because we'll replace them overtime. So, I don't think that's the case.

بواسطة madscient

Master (193)

صورة madscient

23-02-2016, 12:46

gdx wrote:

Yes of course. We only speak for the case of existing programs that read the registers.

I think such a faulty software will be abandoned.
Of course I don't inhibit anyone who want to correct the fault as safe and compliantly.

بواسطة madscient

Master (193)

صورة madscient

23-02-2016, 12:59

tvalenca wrote:

This way we're going to allow new programs reading mapper registers to be written.

Are you sure?
I think the new software which doesn't comply with the spec should not be written.
At least, should not be distributed public.
Such a software should be noticed like as "THIS DANGEROUS SOFTWARE MAY CAUSE CRITICAL DAMAGE ON YOUR COMPUTER", I think.

بواسطة l_oliveira

Hero (534)

صورة l_oliveira

23-02-2016, 13:19

madscient wrote:

"THIS DANGEROUS SOFTWARE MAY CAUSE CRITICAL DAMAGE ON YOUR COMPUTER"

Exaggeration... Maybe something like this:

"CONTINUED USE OF THIS SOFTWARE MIGHT RESULT IN SEVERE USER FRUSTATION."

صفحة 12/20
5 | 6 | 7 | 8 | 9 | 10 | 11 | | 13 | 14 | 15 | 16 | 17