Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!usc!cs.utexas.edu!uunet!mcsun!ukc!acorn!unipalm!ian
From: ian@unipalm.uucp (Ian Phillipps)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Re: Running PC/TCP under DESQview
Message-ID: <1991Mar27.150130.6233@unipalm.uucp>
Date: 27 Mar 91 15:01:30 GMT
References: <9103232155.aa03475@louie.udel.edu>
Organization: Unipalm Ltd., Cambridge, England
Lines: 29

A01DGU1@MVS.CSO.NIU.EDU (Dave Ulrick) writes:

>I have recently installed PC/TCP v2.07 on my 80386 PC.  I'm trying
>to run it in a DESQview window under DESQview v2.26 and MS-DOS v4.01.
>Additionally, I'm trying to run a 3270 emulation program (Attachmate
>Extra! v1.41) in another window.  Doing this seems to work for a
>while, but sometimes things in the PC/TCP window just die.

>I'd be interested in hearing about
>anything that you folks have found successful in coaxing PC/TCP
>to run properly under DESQview.  As it is, it looks like I'm not
>going to be able to run it there.

I  use DESQview and PC/TCP most of the time. It's not ideal, but survives
most of the time.

An application in one DESQview window which calls the Kernel concurrently
with another will get an error decodeable as "kernel re-entered". Some
applications (the latest TN, Interdrive) treat this as a recoverable error,
and retry. The result is that things work slowly (presumably there's some
serious busy-looping going on in there).  Other applications, e.g. FTP's own
domain-name-service lookups in TN; Century Software's Tiny Term, treat this
as a hard error. TN's DNS reports the "kernel re-entered"; Tiny Term exits.

I'm not sure what happens if an application sets up a call-back. If someone
at FTP can tell me one of theirs that does, I'll try it and see if I can
break the combination.

Presumably all will be well when Desqview X arrives.