>> I recently took a look (- :) -) at the BIOS, and I saw that it only looks
at
>> the Keyboard when the keyscan-counter SCNCNT reaches 0.
>
>What computer was that? I looked into the bios of my NMS 8250 (not
>recently, ok) and I'm pretty sure it reads the keyboard every
>vdp-interrupt. Hey, I just found the solution! I'll just switch off the
>interrupts, using vdp(1). When my program returns from the dos-call, I can
>switch them on again. :-)
Nope... it doesn't read it every interrupt. Every 3rd interrupt (in the
normal case). Check it out! Here, this is what the BIOS does:
ld hl,#F3F6 ;SCNCNT
dec (hl)
jp nz,#0D02 ;END_INT
blahblah...
My solution ALWAYS works, yours only in a specially adapted
Assembly-program. Imagine: Someone has written a great Tetris-like game
which is extremely fit for use with JoyNet. One problem: he already finished
the program, which still uses the BIOS-interrupt, and he doesn't want to
have too much work on it (ie. he doesn't want to write a complete new
interrupt). Then it's useful to have such a driver ready.
But, as I understand now, you're not writing a universal driver... *snif*...
>> Hey, you got that??? Now you don't even have to do difficult things to a
>> *complete new* interrupt-routine, you can still use your own, and IT
WORKS
>> UNDER BASIC!!! And Basic is cool because you can then easily program
little
>> test-progs or small games etc... Good idea of me, eh???
>
>The idea is good for small things. But actually, I was planning to make
>big things. Sorry, I mean BIG, or even HUGE. And well, I have my own
>page-0 routines already anyway. Including memory manager, device manager
>and string handling routines. I want to add my joynet routines in it. I
>also will add a multitasker soon. Those are not the kind of things you
>want to run under BASIC, or with BASIC switched in memory...
Yeah ok but I was talking about a universal driver. Using this trick you can
easily implement it in other programs; you don't need to write an entire new
interrupt.
>But thanks for the help. Now I do have the answer anyway :-)
Indeed, switching off the interrupts is a good idea too. Hey, you know what?
I'll add those triks to the JoyNet-page... Now I'm going to do that, has
anybody else written (but not yet programmed) (or programmed, even better!)
some "protocols" for JoyNet??? I have made a comm-protocol for 2 computers
using JoyNet, and a ring connected-protocol which detects if the ring is
closed. However, I still haven't made up a protocol which determines how
many computers there are and which assigns the computers a number...
~Grauw
****
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/)
****
