Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!think.com!zaphod.mps.ohio-state.edu!sdd.hp.com!spool.mu.edu!munnari.oz.au!csource!david
From: david@csource.oz.au (david nugent)
Newsgroups: comp.os.msdos.desqview
Subject: Re: Communication programs
Message-ID: <1880@csource.oz.au>
Date: 21 May 91 08:41:23 GMT
Article-I.D.: csource.1880
References: <1991May19.113245.19970@cs.umu.se> <13127@pt.cs.cmu.edu>
Organization: Unique Computing Pty Ltd, Melb, Aust.
Lines: 23

> In article <1991May19.113245.19970@cs.umu.se> dvldbg@cs.umu.se (Daniel Brahneborg) writes:
>
> }I read somewhere in the manual that you shouldn't let com-progs be
> }swapped out. Is there any workaround for this? The problem is
>
> Not unless you want your system to crash the next time a character comes
> in the serial port after the program has been swapped out.

This shouldn't be the case.  DV revectors the IRQ and manages the hardware
interrupts.  I can't believe that it wouldn't also know which particular 
task "owns" an IRQ vector and has enough intelligence to know that a task
is swapped or not.

In fact, that statement is contrary to my direct experience.  When DV sees
that a particular task owns an IRQ, it tends not to allow swapping of the
program at all.

I could be wrong, since I've never investigated it in any depth, but those
are the assumptions I've made by direct experience.
-- 
 David Nugent                                      Unique Computing Pty Limited
 Communications/PC/Unix Consulting           3:632/348@fidonet 28:4100/1@signet
 Internet/ACSnet: david@csource.oz.au      Uucp: ..!uunet!munnari!csource!david