nelson@sun.soe.clarkson.edu (Russ Nelson) (02/27/91)
In article <9102260625.aa04895@louie.udel.edu> ICH211@DJUKFA11.BITNET (Thomas Heil) writes:
I have encountered the following problem: When I load the packet drivers,
start a mouse-supporting application (Norton Commander or Windows 3.0)
and then, inside of those, call a network program like NCSA Telnet, the
mouse is no longer recognized afterwards. When I leave and re-enter the
mouse driven program, it works again ... till the next Telnet. Where can
be the conflict? I'm using a Microsoft serial mouse with MOUSE.SYS V.7.0
and a WD8003EBT board with IRQ 3, I/O at 0x280, MemBase 0xD000. I tried,
several software interrupt addresses from 0x60 up to no avail.
And I'll bet that your serial mouse is using COM2. COM2 uses IRQ 3. The
way the ISA bus drives the interrupt lines, you can't share interrupt lines.
You should move the WD8003EBT interrupt to something other than IRQ 3.
--
--russ <nelson@clutx.clarkson.edu> I'm proud to be a humble Quaker.
It's better to get mugged than to live a life of fear -- Freeman Dyson
I joined the League for Programming Freedom, and I hope you'll join too.