Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!ukma!rex!samsung!noose.ecn.purdue.edu!mentor.cc.purdue.edu!sage.cc.purdue.edu!bainbrrw
From: bainbrrw@sage.cc.purdue.edu (Robert Bainbridge)
Newsgroups: comp.binaries.ibm.pc.d
Subject: Re: Windows 3.0 and Telix lockup upon connect.
Message-ID: <4899@mentor.cc.purdue.edu>
Date: 31 Jan 91 15:08:26 GMT
References: <1991Jan30.040701.5013@hoss.unl.edu> <1991Jan31.051023.23016@cec1.wustl.edu>
Sender: news@mentor.cc.purdue.edu
Distribution: usa
Lines: 20

In article <1991Jan31.051023.23016@cec1.wustl.edu>, scs2635@cec1.wustl.edu (Sean Starkey) writes:
> In article <1991Jan30.040701.5013@hoss.unl.edu> vandevek@fergvax.unl.edu (James M. VandeVegt) writes:
> >I have had a recuring problem with Windows 3.0 and Telix.
> >When telix connects, the computer locks up and even Ctrl-Alt-Del
> >will reset it. 
> 
> I get a similiar problem.  Sometimes when I call my school's mainframe, using
> Telix, I get a bad line.  When I get this bad line, my computer locks up,
> and I need to do a cold reboot.
> 

I am also having the same problems with Telix and Windows 3.0. I am using a
DOV ( a connection device for connecting to the Purdue mainframe without
using the incoming line.) As soon as I change the com port to the DOV
everything locks up. I think it is a hardware problem as some of the above 
might be. I know others that use Telix over the DOV and have no problems, so
I would say there is something funny with the hardware. Any other sugestions?


Walrus