> ] Hmmm... well, then adapt your mouseroutine for R800 use (if R800 is
enabled,
> ] wait a little longer).
> I'm not going to hack pre-MSX turbo R program's from other people that
don't
> run on my MSX turbo R, just because those people used non-standard
> programming practices in stead of following the MSX standard!
Well I was not talking about you but about the programmers of Illusion City.
> ] I was talking about using a BIOS routine on the interrupt, which is a
crime.
>
> I don't agree. Making incompatible programs is a crime. Making compatible
> programs is not a crime. Even if making compatible programs does cost a
> little bit performance. In the end, the overhead of calling one single
BIOS
> routine on the interrupt is not that large.
It definately DOES cost a lot of performance when called every 1/60th
second, and this can be critical on MSX-computers at 3.5MHz, which need all
the speed they can get (for example I can't afford it to use the BIOS calls
in Strategic Army...).
By the way, don't forget this single BIOS routine has to be called three
times!!! It can be called with a variable deciding which interface should be
used from 0-20... Even the detection of which device is ment by the calling
machine takes unnessacary time.
And besides, aren't the mouse-routines in the SubROM??? Hell, do you know
how SLOW slotswitching is???
~Grauw
--
>>>>>>>>>>>>>>>>>>>>>>>>><<<<<<<<<<<<<<<<<<<<<<<<<
email me: [EMAIL PROTECTED] or ICQ: 10196372
visit the Datax homepage at http://datax.cjb.net/
MSX fair Bussum / MSX Marathon homepage: http://msxfair.cjb.net/
>>>>>>>>>>>>>>>>>>>>>>>>><<<<<<<<<<<<<<<<<<<<<<<<<
****
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/)
****
