Subj : RE: qwk  DOVE-NET
To   : All
From : GREG YOUNGBLOOD
Date : Thu Jan 31 2019 19:12:12

Date: Wed, 16 Apr 2014 12:25:34 -0400
From: GREG YOUNGBLOOD
To: MICHAEL PURDY
Subject: RE: qwk  DOVE-NET
Newsgroups: win.server.program
Message-ID: <1397665534.32.1397522226@winserver.com>
References:  <1397522226.32.1397505947@winserver.com>
X-WcMsg-Attr: Rcvd
X-Mailer: Wildcat! Interactive Net Server v7.0.454.5
Lines: 49

Hello Mike

I'll look into it, thanks for the info!

Greg



On 4/14/2014 8:37 PM, MICHAEL PURDY wrote to GREG YOUNGBLOOD:

-> If you just want to be a Node connecting to a particular Wildcat! host 
to
-> Upload REP and Download QWK Packets then you can use Telnet scripting 
which
-> is made easier if you use the Wildcat! fast login option [!] and 
enhanced
-> scripting prompts.
-> 
-> The problem is that Telnet scripting works on the basis of
-> 
->   Read Data
->     Write Data
->   Read Data
->     Write Data
->   ...
->  
-> So if a Wildcat host has modified their screens/prompts you need to 
match
-> your script to work with the site specific customization.
-> 
-> In the real world the Read Write Data equates to scripting in the form 
of:
-> 
->   expect [wait x]
->     output
->     
-> Within established private Wildcat! QWK Networks FTP is used to overcome
-> the Telnet scripting limitations.
-> 
-> You can use any Telnet scripting language you want.  Netterm is probably
-> the most popular.
-> 
-> http://www.securenetterm.com/
-> 
-> Again just keep in mind that FTP and Telnet scripting is a non-compliant
-> basic method suited to simple Node to Hub requirements, its not 
suitable as
-> a model for running a QWK Network.
 
--- Platinum Xpress/Win/WINServer v3.1
 * Origin: Prison Board BBS Mesquite Tx  //telnet.RDFIG.NET www. (1:124/5013)

.