Announcement

Collapse
No announcement yet.

INP(&H60)

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Mel Bishop
    replied
    Sorry but the last paragraph should start with 10h instead of 12h
    My appologies.


    ------------------

    Leave a comment:


  • Mel Bishop
    replied
    I don't know if this will help but if you have any documentation
    that explains DOS interrupts, you may want to take a look at
    int16h sub-functions 11h and 10h (in that order).

    11h looks at the keyboard buffer, returns a result and moves on.

    12h will remove a keystroke if it is available. If not available
    it will freeze until one becomes available.



    ------------------

    Leave a comment:


  • Walt Decker
    replied
    Thanks, Lance.

    I'd try it myself, but I don't have all the toys other folks have. If I did, I would not have asked the question in the first place.

    ------------------

    Leave a comment:


  • Lance Edmonds
    replied
    It is the tight loop without releasing time-slices to the O/S, rather than the specific statements inside the loop. Try it out for yourself...


    ------------------
    Lance
    PowerBASIC Support
    mailto:[email protected][email protected]</A>

    Leave a comment:


  • Walt Decker
    started a topic INP(&H60)

    INP(&H60)

    The INKEY$ topic is quite informative. I'm wondering if INP(&H60) has the same effect on the CPU as does a tight INKEY$ loop?


    ------------------
Working...
X