shevek <[EMAIL PROTECTED]> wrote:
> The only thing you need to expect is that writing the data you read from
> the mapperport will set it back to the state it was in when you read it.
> All other info about the mapper can be obtained by writing to the port and
> reading and writing the memory.
If the mapperports are write-only (possible), or reading back
doesn't work good (possible), reading back will get you "undefined",
usually FFh. Writing that to restore, would select always FFh = not
the same as previous state.
I consider this issue like this:
-You ARE allowed to read these ports (why not?).
-When you do, there's no telling what you'll get.
So you can read these ports, but what you read, should be considered
as useless.
>> You also have to take care that some people have more then 1
>> mapper (however this is technically not allowed , but who cares)
Multiple mappers not allowed? Says who? Says what? Why not?
There are some machines that have a hardware-problem with it, but
that's more like a mistake in the design of those machines (like the
Turbo-R with >512K external mapper).
Greetings,
Alwin Henseler ([EMAIL PROTECTED])
http://huizen.dds.nl/~alwinh/msx MSX Tech Doc page
****
MSX Mailinglist. To unsubscribe, send an email to [EMAIL PROTECTED] and put
in the body (not subject) "unsubscribe msx [EMAIL PROTECTED]" (without the
quotes :-) Problems? contact [EMAIL PROTECTED] (www.stack.nl/~wiebe/mailinglist/)
****
