Path: utzoo!news-server.csri.toronto.edu!cs.utexas.edu!sun-barr!newstop!grapevine!flowzone!g-man From: g-man@flowzone.EBay.Sun.COM (Luis Navarro) Newsgroups: comp.windows.ms.programmer Subject: windows & assembly level interrupt handlers Keywords: midi, assembly, interrupts, help! Message-ID: <972@grapevine.EBay.Sun.COM> Date: 4 Mar 91 09:43:24 GMT Sender: news@grapevine.EBay.Sun.COM Reply-To: g-man@EBay.Sun.COM (Luis Navarro) Distribution: na Organization: Sun Microsystems Federal, Inc., Milpitas, CA, USA Lines: 31 I am trying to write a Windows 3.0 application that uses an assembly level interrupt handler to handle MIDI (musical instrument digital interface) input/output and am having some serious problems with the data interfacing. Please read on if you are familar with all or any of the following as they relate to windows programming: 1. MIDI 2. interrupt handlers 3. assembly level routines communicating with Windows C code The following are some more details regarding what I'm trying to do, as well as the problems I'm experiencing: I have obtained some C/assembly code originally written for interrupt driven MIDI communcations in DOS. The assembly level stuff consists of the interrupt handler (an interrupt is generated for every MIDI byte that arrives at the MIDI interface) and the data i/o. The C code uses the assembly routines to do the rest. Now I am trying to use this assembly code in a relative simple windows program and am having some great difficulties. My main objective is to modify the already existing assembly/C code so that the interrupt handler will post a windows message (encapsulating the current MIDI data byte in the message). How does one go about doing this? Furthermore, the interrupt handler appears to work in real mode, but not in standard or 386 as if the data buffer (created and declared in the assembly code) was empty or if interrupts suddenly weren't being generated at all. Any ideas, advice, or general pointers would be greatly appreciated. --Luis (g-man@EBay.Sun.COM)