Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!mailrus!uwmcsd1!nic.MR.NET!umn-cs!ns!ddb
From: ddb@ns.UUCP (David Dyer-Bennet)
Newsgroups: comp.sys.ibm.pc
Subject: Re: Background Communications under Desqview
Keywords: comm desqview
Message-ID: <675@ns.UUCP>
Date: 29 Jul 88 17:12:13 GMT
References: <595@unh.UUCP>
Distribution: na
Organization: Network Systems Corp. Mpls MN
Lines: 23

To make a program run in the background under desqview, you need to do one
thing: you need to set the "runs in foreground only" to no on the second
program setup page.  In most of the cases where you want to run something
in the background, you also want to set the "cannot be swapped out" field.
(a swapped out program does not run under desqview; this isn't like timesharing
swapping, where you come in and out as your time-slice runs by.)

If you set the cannot be swapped field, then the memory occupied by that
program is not available for any other use.  If you want to run more things
than will fit in memory at once, you need more memory.  Desqview 2.01 can use
EEMS (hardware lim 4.0) memory, so you can have lots more than 640 k of
stuff running at once if you need to.

(In the bbs world, we frequently run 2 or 3-line bbs systems by running
2 or 3 copies of Opus under desqview on 286's with eems or 386's with
qemm.  One gentleman run an 8-line board that way.  Background communications
under desqview definitely work.)

-- 
	-- David Dyer-Bennet
	...!{rutgers!dayton | amdahl!ems | uunet!rosevax}!umn-cs!ns!ddb
	ddb@Lynx.MN.Org, ...{amdahl,hpda}!bungia!viper!ddb
	Fidonet 1:282/341.0, (612) 721-8967 hst/2400/1200/300