home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.os.ms-windows.setup
- Path: sparky!uunet!zaphod.mps.ohio-state.edu!cs.utexas.edu!csc.ti.com!tilde.csc.ti.com!mksol!mccall
- From: mccall@mksol.dseg.ti.com (fred j mccall 575-3539)
- Subject: Re: IRQ 2 and Windows 3.1
- Message-ID: <1992Dec17.175228.27476@mksol.dseg.ti.com>
- Organization: Texas Instruments Inc
- References: <BzDC80.2nw@NeoSoft.com>
- Distribution: usa
- Date: Thu, 17 Dec 1992 17:52:28 GMT
- Lines: 31
-
- In <BzDC80.2nw@NeoSoft.com> dbradley@NeoSoft.com (Dennis Bradley) writes:
-
- >Could someone tell me if it is ok to use IRQ 2 with
- >devices (sound cards , network boards , etc) with
- >windows 3.1 ? I understand that windows 3.0 had some
- >problems using IRQ 2. I don;t know if they have been
- >solved in 3.1 or not.
-
- There are two potential 'problems' with IRQ2. First, you may have to
- call it IRQ9 instead of IRQ2. IRQ2 is really remapped to IRQ9, sinc
- the first 8259 uses IRQ2 as the cascade.
-
- Secondly, some video cards may give you problems with conflicts with
- IRQ2. 'Standard' EGA boards use IRQ2 (but I'm not sure what for).
-
- Anyway, I'm currently using IRQ2 for one of my serial ports under
- Windows 3.1. Right now, I don't remember if I had to call it IRQ2 or
- IRQ9 when I set it up in the Ports setup. I also had to pull a jumper
- on my Diamond Speedstar, since it wanted to have IRQ2 so as to do 100%
- EGA compatability.
-
- >This would be on a 386/486 class machine with a
- >cascaded 8259.
-
- Mine is a 486-50 EISA using ISA comm boards. Works fine.
-
- --
- "Insisting on perfect safety is for people who don't have the balls to live
- in the real world." -- Mary Shafer, NASA Ames Dryden
- ------------------------------------------------------------------------------
- Fred.McCall@dseg.ti.com - I don't speak for others and they don't speak for me.
-