] Here we need to establish some extra rules; is the following allowed for a
] mapper?
] 4-bit 128kB mapper:
] 0,1,2,3=ram
] 4,5,6,7=nothing (no ram, databus high-imped)
] 8,9,a,b=ram (other memory than blocks 0,1,2,3)
] c,d,e,f=nothing
]
] I think we should not allow such mapperconstructions (we can allow them,
As far as I know, non-consecutive mappers do not exist. Though, the MSX turbo
R in R800-DRAM mode is missing the highest for pages. E.g., on the GT in
R800-DRAM mode:
0..27 : Mapper ram
28..31: 'Empty' (read from those blocks returns FF)
32..59: First 28 blocks of mapper ram again
60..63: 'Empty'
Etc.
Anyway, just something to keep in mind when determining the mapper size...
Kind regards,
Alex Wulms
--
Alex Wulms/XelaSoft - MSX of anders NIX - Linux 4 ever
See my homepage for info on the *** XSA *** format
http://www.inter.nl.net/users/A.P.Wulms
****
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/)
****
