| |
PA2AGA > HDDIG 31.05.00 02:16l 170 Lines 5465 Bytes #-9463 (0) @ EU
BID : HD_2000_151C
Read: GUEST
Subj: HamDigitalDigest 2000/151C
Path: DB0AAB<DB0SL<DB0RGB<DB0MRW<DB0ERF<DB0FBB<DB0GOS<DB0PKE<DB0ACH<PI8JOP<
PI8ZAA<PI8GCB<PI8HGL
Sent: 000530/1846Z @:PI8HGL.#ZH1.NLD.EU #:45634 [Den Haag] FBB $:HD_2000_151C
From: PA2AGA@PI8HGL.#ZH1.NLD.EU
To : HDDIG@EU
Date: Tue, 30 May 00 19:47:46 MET
Message-Id: <hd_2000_151C>
From: pa2aga@pe1mvx.ampr.org
To: hd_broadcast@pa2aga.ampr.org
X-BBS-Msg-Type: B
Subject: N0ZO no longer supports Keyboard inputs!
On April 23, k4cjx announced that WL2K will now work in the ASCII
mode, which allows cheapie PACTOR-enabled PK-232 (or the MFJ ????
model) controllers to work. See:
http://www.listbot.com/cgi-
bin/subscriber?Act=view_message&list_id=winnnet&msg_num=741&start_num=758
for his announcement posted to the WinLink/NetLink mailing list
Binary transfers are apparently not a requirement. I had put my old
PK-232 on the shelf and obtained a KAM+ in order to use WinLink, not
realizing that PK-232 support was imminent. Wish I had waited a bit!
Jerry W4UK
On Mon, 29 May 2000 21:23:08 -0500, Seth Miller
<sethmiller73@email.com> wrote:
>
>Mike,
>
>It was not SCS that made the decision to support only binary mode transfers,
>rather it was the WinLink 2000 authors.
>
>It is unfortunate that PacComm didn't implement a binary transfer mode (which
is
>the problem in your case, and not Pactor I vs. Pactor II issue). Other
>manufacturer's Pactor I TNC's (Kantronics, AEA, etc.) are supported by
>AirMail/WinLink. This issue has no relationship to SCS and/or the PTC-II
series
>- if you want to be bitter at least aim it at the right manufacturer.
>
>- Seth
>
>
>
>Mike Pupeza wrote:
>
>> Well Gang;
>>
>> I said it would happen! My favorite Pactor WinLink BBS N0ZO in Lady Lake,
>> Florida will no longer talk to me.
>> Reason! I don't run the AirMail 2000 program!
>> I want to, but CAN'T!
>> My TNC - a PacComm PacTOR CONTROLLER, which is totally PTC-1 Compliant -
the
>> ORIGINAL and STARTER of the whole Pactor scene, is INCOMPATIBLE, and NOT
>> SUPPORTED by the AirMail 2000 program!
>> Guys, I bought this NEW in February of 1999 - it's not OLD!
>>
>> Also, I have a Mac I-book, for which there is no support! And I know people
>> who run Linux!
>>
>> So here I go again, bitching! But, c'mon!
>>
>> I hope that there are some changes in PSK-31 that'll allow error checking
>> and correction that'll make these PTC-II and IIe controllers as useful as
>> Commodore 64's, in todays world!
>>
>> Off my chest! Thanks!
>> --
>> Mike Pupeza VE3EQP
>
------------------------------
Date: Tue, 30 May 2000 10:03:01 +0200
From: Markus Lenggenhager <Markus.Lenggenhager@philips.com>
Subject: N0ZO no longer supports Keyboard inputs!
Hi all
My personal opinion is that this WinLink2000-AirMail alliance is
definitely going in the wrong direction. Ham BBSs should be accessible
using any commonly available client software. Furthermore, all
WinLink2000 BBSs are interconnected via Internet, which means it becomes
obvious their main purpose is to act as a cheap e-mail replacement. The
fact that all tfc is compressed (unreadable by thirds) makes it very
difficult to check if this network is not misused by pirates of all
kinds.
It's a pity that PACTOR-II has been kind of devaluated and is being used
almost entirely as a workhorse to carry binary BBS tfc. It's getting
more and more difficult to find a live QSO partner amidst all these
signals produced by unattended systems. No wonder PSK31 has become so
popular: Behind every signal you monitor there's a human being!
73, Markus HB9BRJ
------------------------------
Date: Mon, 29 May 2000 15:28:20 GMT
From: Dick Hughes <ragoldhughes@worldwingnet.att.net>
Subject: PSK31 Audio Connection
I'm planning on using DigiPan.
Dick - W6CCD
On Sun, 28 May 2000 22:36:12 -0700, "David McCallum"
<wa1onp@prodigy.net> wrote:
>
>Dick which PSK31 program are going to use. I noticed you have an ICOM so
>thouht I'd ask. Thanks
------------------------------
Date: Tue, 30 May 2000 04:35:44 -0500
From: Mark Harger <mark@fairwoodsales.com>
Subject: RTTY with Pegasus/PK-232
In the Pegasus settings window select "transmitter" and be sure that you
have "accessory input" NOT MICROPHONE selected. You have to do this
everytime you launch the rig software.
Hope this helps.
73 Mark K4VO
------------------------------
Date: Mon, 29 May 2000 12:57:36 -0400
From: "Greg Carey" <gandicarey@erolc.com>
Subject: Using Digipan 1.1 to Key Kenwood Radio
De Greg, KN4EL
I've been enjoying the fascinating world of PSK31 for all of 2 weeks. I use
RCP (Kenwood's Radio Control Program) to control a Kenwood 570S. This
program works flawlessly, but after setting Digipan up to use the same com
port that works for RCP (I don't use the two programs concurrently),
Digipan still does not switch the radio over to transmit. My guess is that
Digipan does not use scripting (e.g., reg4=0;if(tx) rx; else tx;) for
transmitting?
Currently, I'm using audio from PC speakers and VOX on radio to transmit
PSK31. High pitched worbles used to sound nice, but the novelty has worn
off with self, XYL and harmonics. :-). Using the ACC plug at the back of
radio for audio (I/O) and getting Digipan to switch TXing would be bliss!
Looking forward to hear from anyone who has been able to use Digipan to key
similar Kenwood radios, especially via serial port, PC side to DB9
connector, radio side.
Tnx, 73
Greg, Silver Spring MD
------------------------------
End of Ham-Digital Digest V2000 #151
******************************
You can send in your contribution to this digest by
sending an e-mail to: hd-group@pa2aga.ampr.org
or (via BBS-net) to: hdaga@pi8vnw.#zh2.nld.eu
Read previous mail | Read next mail
| |
