ZL1ABS > WINPAC 13.04.10 23:18l 63 Lines 991 Bytes #999 (0) @ WW
BID : 7A3596ZL1ABS
Read: GUEST
Subj: Winpack CMD prompt Script
Path: IZ3LSV<IK2XDE<DB0RES<DK0WUE<7M3TJZ<ZL2BAU<ZL1AB
Sent: 100413/2206Z @:ZL1AB.#06.NZL.OC #:43165 [AUCKLAND] FBB7.00i $:7A3596ZL1AB
From: ZL1ABS@ZL1AB.#06.NZL.OC
To : WINPAC@WW
14/04/2010 ZL1ABS
I've been working on the problem
of my Winpack Scripts
"stalling" on the screen showing
the blue box
sitting at a WAITFOR or WAITCON
because the TNC wasn't in CMD
mode to begin with
(it was in CONV mode at the
time).
CTRL-C IS HEX03
CTRL-M CR IS HEX0D
WINPACK SCRIPT INFORMATION
WINPACK USES CTRL-M THIS WAY
SEND ^M
WINPACK USES CTRL-C THIS WAY
SEND ^C
lOOK IN MFJ 1270C TNC 2 DATA
CONTROLLER MANUAL PAGE 50 FOR A
TABLE OF ASCII CODES CONTROL
CHARACTERS IN HEX FORMAT.
This might need to be added to
your DXCLUSTER script file at the
begining
or any other script file that
won't work at times.
Winpack TXT file stored in the
Scripts folder
;To wake up the TNC automatically
;when Winpack needs to send
;a script to make the TNC work
;I often have to manually
;type CTRL-C
;My winpack scripts fail to work
unless
;the TNC is in CMD: mode
;so add this line
;SEND A ctrl-c COMMAND PROMPT
SEND ^c
Read previous mail | Read next mail
| 
