a35@mindlink.UUCP (Bruce Atherton) (05/31/90)
Help! I've lost my multitasking!
I am using Desqview on a 386 machine. I have COMMO and TELIX set up so that
when I use them on COM1: they work perfectly. I can download and edit and
compile all at the same time.
Then I had to change my modem over to COM2:. I switched the programs over and
they work fine, except for the fact that if I try to switch out of the
communications window while information is coming in the communications program
locks up. I can switch when nothing is coming in without a problem. If
something comes in, though, I have to exit out of my Terminal program and
reload it. Also, all the information that came in is lost.
I've tried changing the desqview settings to specify that these programs use
COM2: (as well as just saying they use a comm port). The settings work fine on
COM1:. Does anyone have any suggestions as to what I should be doing? Can I
prevent Desqview from swapping the interrupt for COM2:?
BTW, I recommend anyone using Desqview consider getting COMMO. It fits into a
tiny window so that you get more room for other programs. Highly recommended.
Bruce_Atherton@mindlink.UUCP or| "Don't look so perplexed. Why must you be
uunet!van-bc!rsoft!mindlink!a35| vexed. Can't you see you're next? Yes,
| you're next, you're so next." - Bugs Bunnyboyer@iuvax.cs.indiana.edu (Charles David Boyer) (06/03/90)
a35@mindlink.UUCP (Bruce Atherton) writes: ... >I am using Desqview on a 386 machine. I have COMMO and TELIX set up so that >when I use them on COM1: they work perfectly. I can download and edit and >compile all at the same time. >Then I had to change my modem over to COM2:. I switched the programs over and >they work fine, except for the fact that if I try to switch out of the >communications window while information is coming in the communications program >locks up. I can switch when nothing is coming in without a problem. If >something comes in, though, I have to exit out of my Terminal program and >reload it. Also, all the information that came in is lost. ... Is it possible that you have a conflict between your modem and something else, such as a mouse, or an ethernet card etc.? This might cause the behavior you describe. Also, have you tried setting the protection level higher on both the comm program (presumably window 1) and the other window? Perhaps this would generate an exception indicating that one program is using something that it shouldn't. I don't know if protected mode covers the serial ports. 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. David Boyer
david@csource.OZ.AU (david nugent) (06/04/90)
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
root@kesher.UUCP (Aaron_Schmiedel) (06/04/90)
> global "optimise communications" switch fools around with interrupt priorities. > I haven't had much luck with DESQview handling the com ports. Once I set DV to NOT optimize com ports it seems to handle things better.