home *** CD-ROM | disk | FTP | other *** search
- Xref: sparky alt.msdos.programmer:3135 comp.msdos.programmer:116 comp.os.msdos.programmer:11997 comp.sys.ibm.pc.programmer:771
- Newsgroups: alt.msdos.programmer,comp.msdos.programmer,comp.os.msdos.programmer,comp.sys.ibm.pc.programmer
- Path: sparky!uunet!timbuk.cray.com!walter.cray.com!spyro!kelly
- From: kelly@spyro.cray.com (Matt Kelly)
- Subject: Re: IRQ2 or IRQ5
- Message-ID: <1993Jan11.130205.27179@walter.cray.com>
- Lines: 25
- Sender: kelly@spyro (Matt Kelly)
- Nntp-Posting-Host: spyro.cray.com
- References: <1993Jan7.122713.17450@walter.cray.com> <1993Jan9.124633.19036@mnemosyne.cs.du.edu>
- Date: 11 Jan 93 13:02:04 CST
-
-
- Fellow bit-twiddlers,
-
- I'd like to thank everyone who replied to my post, both on the net
- and via e-mail. The information was most helpful.
-
- I solved my problem. I am using IRQ5. The reason it didn't work
- when I tried it before is that the interface I built is now connected
- to a new synthesizer which sends periodic "active sensing" bytes.
- My interface received these and set the INT bit. By ignoring these
- sense bytes in my interface code, I was never clearing the INT bit,
- which caused subsequent bytes to generate overrun errors, etc.
-
- I inserted code to read these sense bytes, acknowledge them, and keep
- the input channel clear. This fixed it!!!!
-
- FYI, I have discovered AT-class machines pretty much use IRQ interrupts
- for whatever reason they want -- there is no real "standard". Some use
- IRQ5 for the floppy drive, some for LPT2, some for LPT1, some for VGA,
- etc. This is unfortunate, but a fact of life.
-
-
- May your bit buckets always be empty!!!
-
- Matt
-