Path: utzoo!utgpu!watserv1!watmath!att!pacbell!pacbell.com!ames!rex!samsung!munnari.oz.au!csource!david
From: david@csource.OZ.AU (david nugent)
Newsgroups: comp.sys.ibm.pc
Subject: Re: Desqview with COM2:
Message-ID: <6@csource.OZ.AU>
Date: 4 Jun 90 03:50:51 GMT
References: <1966@mindlink.UUCP> <46521@iuvax.cs.indiana.edu>
Organization: Unique Computing Pty Ltd, Melb, Aust.
Lines: 13

In article <46521@iuvax.cs.indiana.edu>, boyer@iuvax.cs.indiana.edu (Charles David Boyer) writes:

> As an aside, you should be running the mouse on com1 and the modem on com2
> since com2 is on interrupt 3 and com1 is on interrupt 4, thus giving the
> modem higher priority than the mouse.

DESQview's (which was mentioned in the original posting to which you replied)
global "optimise communications" switch fools around with interrupt priorities.

You can even select which specific IRQ to make a higher priority than all
others.

david