> > The IM mode 2 is used very often on MSX (though
> not
> > supported by any hardware). A lot of programs
> running
> > in the Basic memory-layout (with BIOS on page 0),
> but
> > still wanting to have their own interrupt routines
> use
> > IM 2 to achieve that.
>
> I don't think IM2 is used that often. For example, I
> used it only once.
Sonyc, for example, uses it.
And Track also does. And a lot of other stuff.
Even if it were only 10% of the programs which have
their own interruptroutines... it would still be too
much.
> > The problem with I/O registers is also unsolvable,
> > remapping or any other trick won't work because
> the
> > problem is INSIDE the processor. The only solution
> is
> > to debug the programs not working, and there are
> just
> > too much.
>
> The internal I/O ports take up #40 port numbers.
> There are very few MSX I/O
> devices that use ports in the range #00..#3F. So I
> don't think there will
> be that many programs not working.
I do think there will be.
For RS232-interfaces won't work, and if I remember
correctly the BERT interface also uses ports in that
range. There will be quite a lot.
> You can try to
> convince me otherwise by
> naming the programs and the reasons they need to do
> I/O in the #00..#3F
> range...
Well I've got the docs at home, but since I will go on
holidays (to Sweden) as soon as I get home I have no
time to look it up.
I hope others will.
~Grauw
__________________________________________________
Do You Yahoo!?
Talk to your friends online and get email alerts with Yahoo! Messenger.
http://im.yahoo.com/
****
MSX Mailinglist. To unsubscribe, send an email to [EMAIL PROTECTED]
and put "unsubscribe msx [EMAIL PROTECTED]" (without the quotes) in
the body (not the subject) of the message.
Problems? contact [EMAIL PROTECTED]
More information on MSX can be found in the following places:
The MSX faq: http://www.faq.msxnet.org/
The MSX newsgroup: comp.sys.msx
The MSX IRC channel: #MSX on Undernet
****
