Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
  1. Home
  2. General Programming
  3. C / C++ / MFC
  4. Trapping Interrupts in Windows

Trapping Interrupts in Windows

Scheduled Pinned Locked Moved C / C++ / MFC
questionc++asp-netjsontutorial
3 Posts 2 Posters 0 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • R Offline
    R Offline
    Rane
    wrote on last edited by
    #1

    How to trap the interrupts produced in Windows Environment,by establishing a system wide monitor/hook. What is the core API to be used? (_dos_getvect & _dos_setvect cannot be used in MS VC++ programs) Any one having any intresting Idea?? -Rane :rose: Rane

    G 1 Reply Last reply
    0
    • R Rane

      How to trap the interrupts produced in Windows Environment,by establishing a system wide monitor/hook. What is the core API to be used? (_dos_getvect & _dos_setvect cannot be used in MS VC++ programs) Any one having any intresting Idea?? -Rane :rose: Rane

      G Offline
      G Offline
      Gary R Wheeler
      wrote on last edited by
      #2

      Under Windows NT, 2000, XP, and Server 2003, applications can not handle interrupts. Interrupt handling is reserved for device drivers. Typically, a device driver will handle an interrupt and then signal an event. An application will have a worker thread waiting on that event. It isn't real-time, but it is safer than allowing applications direct access to hardware.


      Software Zen: delete this;

      Fold With Us![^]

      R 1 Reply Last reply
      0
      • G Gary R Wheeler

        Under Windows NT, 2000, XP, and Server 2003, applications can not handle interrupts. Interrupt handling is reserved for device drivers. Typically, a device driver will handle an interrupt and then signal an event. An application will have a worker thread waiting on that event. It isn't real-time, but it is safer than allowing applications direct access to hardware.


        Software Zen: delete this;

        Fold With Us![^]

        R Offline
        R Offline
        Rane
        wrote on last edited by
        #3

        Is it possible to write a universal driver to trap the software interrupts alone. (Any class/API supporting it?) :rose: Rane

        1 Reply Last reply
        0
        Reply
        • Reply as topic
        Log in to reply
        • Oldest to Newest
        • Newest to Oldest
        • Most Votes


        • Login

        • Don't have an account? Register

        • Login or register to search.
        • First post
          Last post
        0
        • Categories
        • Recent
        • Tags
        • Popular
        • World
        • Users
        • Groups