Path: utzoo!attcan!uunet!zaphod.mps.ohio-state.edu!rpi!rpitsmts!forumexp
From: Barry Bailey
Newsgroups: comp.windows.ms
Subject: WINQVT
Message-ID: <9848.6384.forumexp@mts.rpi.edu>
Date: 26 Oct 90 15:34:00 GMT
Lines: 36


 
   I have attempted to perform a KERMIT file transfer with WINQVT over
   our 9600 baud PBX/IBX dataline. On our mainframe I run KERMIT and
   initiate a SEND filename command. I then select TRANSFER DOWNLOAD
   KERMIT RECEIVE from the WINQVT pull down menu (also tried the KERMIT
   GET option). Regardless of the FLOW CONTROL or PARITY setting the
   transfer times out. Whether it times out or I select the ABORT option
   under WINQVT I successfully return to my VT100 terminal session (if I
   ABORT, the mainframe KERMIT displays the USER ABORT message,
   indicating that is received a KERMIT FINISH escape sequence).
 
   While using MSKERMIT for file transfers I have to set PARITY EVEN
   (even though to connect I have to SET PARITY NONE). Typically before
   the file transfer will commence I have to press the ENTER key one to
   three times after MSKERMIT has displayed its file transfer status
   screen. The ENTER key increments the RETRY COUNT by one for each time
   I press it. Usually by the third time MSKERMIT and the mainframe
   KERMIT begin file transfer.
 
   Does anyone have experience transferring files using WINQVT and
   KERMIT over PBX datalines? How might I send an ENTER key code under
   WINQVT (sort of a kick in the pants to the mainframe KERMIT)? Is
   there another solution?
 
   barry
 
   ps
 
   I suspect that the reason WINQVT works over a PBX at all is its
   support of both SOFTWARE and HARDWARE hangup. HARDWARE hangup entails
   dropping DTR (which is something MSKERMIT also is capable of doing).
 
   Others developing WIN3 communications packages would do well by a
   somewhat small community of users by including DTR control
   capabilities (WINCOMM?, WINKER?, etc.).