Xref: utzoo comp.os.msdos.apps:1099 comp.os.msdos.programmer:3449
Path: utzoo!mnetor!tmsoft!torsqnt!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!ns-mx!iowasp.physics.uiowa.edu!maverick.ksu.ksu.edu!ux1.cso.uiuc.edu!news.iastate.edu!sharkey!umich!caen!
 sdd.hp.com!wuarchive!mit-eddie!uw-beaver!rice!uupsi!rpi!fechuny
From: fechuny@itsgw.rpi.edu (felix chung yau)
Newsgroups: comp.os.msdos.apps,comp.os.msdos.programmer
Subject: <None>
Message-ID: <C8-&}B_@rpi.edu>
Date: 17 Feb 91 18:23:16 GMT
Lines: 23
Nntp-Posting-Host: jec405.its.rpi.edu


Subject: Re: Procomm + 2.0 Script execution problems
Summary: Script file does not drop DTR when switching com ports
Expires: 
References: <1991Feb13.030916.10963@novell.com> <5605@bwdls58.UUCP> <91047.222138IO92203@MAINE.BITNET>
Sender: 
Followup-To: 
Distribution: 
Organization: Rensselaer Polytechnic Institute, Troy NY
Keywords: 


   I recently upgraded to Procomm+ 2.0.  While the new features in version
2.0 are nice, I have encountered a problem when running a script file.  The 
script file switches from com3 to com1 and then connects to the data link I 
have setup.  The problem is that procomm does not drop the DTR signal on the
com3 port and as a result the script does not work.  The same is true when
going from com1 to com3. I thought it could be something in my setup but
no change in the setup fixed it.  I did notice, however, that doing a manual
port switch by using Alt-P does drop the DTR properly.  Since the script
file scheme to switch ports worked on version 1.1b I can't help but wonder
if it is the software.
   Can anyone help me with this problem?  Thanks.