| |
ZL1ABS > WINPAC 30.05.09 03:57l 42 Lines 1579 Bytes #999 (0) @ WW
BID : B62658ZL1ABS
Read: GUEST
Subj: Re: Longstanding problem
Path: IZ3LSV<IK2XDE<DB0RES<ON0AR<ZL2BAU<ZL1AB
Sent: 090530/0145Z @:ZL1AB.#06.NZL.OC #:29052 [AUCKLAND] FBB7.00i $:B62658ZL1AB
From: ZL1ABS@ZL1AB.#06.NZL.OC
To : WINPAC@WW
Hi Ray,
Thanks for the report on what BBS Prompt your users get.
If they get
(1) VK2TV BBS>
(note I'm putting an extra (space) between TV & BB to avoid it going wrong
with a properly configured Winpack reader at your end) the number would
change depending on the number of users currently connected.
So according to G4IDE's BBS PRMPT.TXT file the appropriate initial Winpack
BBS Prompt would be
VK2TV(space)BBS
Replace (space) with a single space character. The prompt is case
sensitive, so must be entered in upper case. No chevron required.
If messages & bulletins arrive with the words
VK2TV(space)BBS
in the body of the text, it might be necessary to go as far as using a BBS
Prompt in Winpack of
) VK2TV(space)BBS
just to have something that doesn't occur in the text so Winpack can get
the best chance of sorting out a real BBS prompt from an erronious one in
the text body.
Interestingly the file says that the chevron doesn't need to be specified
as Winpack assumes it is always there. So I've learned something too and
I'll have to take the chevron out of my own BBS Prompt box.
I don't know how many years I've been doing it wrong but I'm not afraid to
learn how to fix it.
In my case I'll need to use ZL1AB(space)BBS (H for help) with no chevron
on the end. Luckily the (H for help) bit doesn't occur in the body of any
text messages & with the callsign & "BBS" makes a good "code-word" for a
BBS Prompt so Winpack ought never get it wrong, HI.
73 - Michael, ZL1ABS @ ZL1AB
Message timed: 13:18 on 2009-May-30
Read previous mail | Read next mail
| |
