Newsgroups: comp.sys.ibm.pc
Path: utzoo!utgpu!jarvis.csri.toronto.edu!me!rwh
From: rwh@me.utoronto.ca (Russell Herman)
Subject: Re: Desqview + comm program = trouble?
Message-ID: <89Aug6.095332edt.18674@me.utoronto.ca>
Organization: U of T Mechanical Engineering
References: <27016@agate.BERKELEY.EDU>
Date: Sun, 6 Aug 89 09:53:29 EDT

In article <27016@agate.BERKELEY.EDU> marquis@qal.qal.berkeley.edu (Roger Marquis) writes:
>  I have the same problem with DV background communications i.e.,
>unreliability, even with the 'optimize communications' parameter on,
>Telix loaded first, 'swap out?' set to NO and the background clock set
>to 10 (fg to 2). With a 20mhz 386 you wouldn't thing there would be a
>problem but Telix will frequently lose packets (ZMODEM) or lock up.
>Even when it does work it will usually lock-up when I exit DV (though
>this may be caused by my running DV from a batch file which reloads my
>TSRs upon exit). While I don't use QEMM.SYS there are still 100K out of
>640 left for other things like text editing.
>  Do other DV users have this problem?
>
>	marquis@qal.berkeley  

I'm running DV386/QEMM on a noname and Telix3.11.  Works beautifully EXCEPT
for the following, and only during ZMODEM file transfers:

	1. long floppy accesses occasionally make TELIX lock up.
	2. the washing machine is on the same circuit.  The valve solenoid
	   will cause it to scramble a packet and time out.  Inserting a
	   power-line/modem-line conditioner DIDN'T help, to my surprise.

Make sure you have the latest/greatest DV.  I've heard rumours of problems
with 2.21-2.23.

Russ Herman
INTERNET: rwh@me.utoronto.ca  UUCP: ..uunet!utai!me!rwh