Re: mapperports (was MegaRAM)

1999-03-22 Thread shevek
On Sun, 21 Mar 1999, Erik wrote: > So that rumor is solved , you are allowed to read them. > The only problem is that the unused bit's of the registers can return > unexpected data.( always 1 or 0 or the data you did write to it or maybe crap) > You first have to calculate the amount of memory an

Re: mapperports (was MegaRAM)

1999-03-21 Thread Laurens Holst
>Here i have the msx technical databook , micro$oft 5 feb. 1986 rel.6.0 >It says on MSX2 memory mapper specification chapter 1 line 4 > >- The mapping registers are at FCH to FFH of I/O address. The are both read and >write addresses. - > >So that rumor is solved , you are allowed to read them. >T

Re: mapperports (was MegaRAM)

1999-03-21 Thread Erik
Jon De Schrijder schreef: > Laurens Holst wrote: > > ... > > !!! GRUWEL GRUWEL !!! > > --> for non-Dutch readers: !!! HORRIFYING HORRIFYING !!! > > > > > Issuing an IN on the mapper-ports is against the MSX-standard!!! > > NEVER >>IN<< the Mapper-ports. The result is ABSOLUTELY unreliable and >

Re: mapperports (was MegaRAM)

1999-03-20 Thread Jon De Schrijder
Laurens Holst wrote: > ... > !!! GRUWEL GRUWEL !!! --> for non-Dutch readers: !!! HORRIFYING HORRIFYING !!! > > Issuing an IN on the mapper-ports is against the MSX-standard!!! > NEVER >>IN<< the Mapper-ports. The result is ABSOLUTELY unreliable and > machine/mapper-dependant. One computer inv