Path: utzoo!utgpu!watserv1!watmath!att!att!linac!pacific.mps.ohio-state.edu!zaphod.mps.ohio-state.edu!think.com!mintaka!bloom-beacon!eru!hagbard!sunic!mcsun!ukc!harrier.ukc.ac.uk!zodiac.ukc.ac.uk!spr003
From: spr003%cluster@ukc.ac.uk (Jim Mansell)
Newsgroups: comp.windows.ms
Subject: Procomm disables Com2 under Windows 3
Message-ID: <21234.2745b144@cluster@ukc.ac.uk>
Date: 17 Nov 90 21:53:08 GMT
Organization: Computing Lab, University of Kent at Canterbury, UK.
Lines: 18

When I run Procomm (using a PIF file) under Windows 3 on my 386 Viglen AT, the
first attempt works OK but all subsequent attempts fail: the Procomm screen
comes up OK but there is no answer from the mainframe connection. Any attempt
to use a comms programme (Windows Terminal, WinQVT, Kermit-PC) also calls up 
the screen display but gets no answer. A hard reset allows any of these
programs to work, but once Procomm is used once the same problem occurs again.

Procomm is configured to use Com2; other software can be configured to use
Com2 without problems, so the port itself seems OK.

The computer has Com1 to Com4 installed, with the 386 Enhanced options
in Control Panel set to 'always warn'. 

Any ideas as to what might be the problem? Procomm is such as useful program
I would like to run it in preference to Terminal or WinQVT.


Jim Mansell