| |
PA2AGA > HDDIG 01.06.00 15:14l 193 Lines 7348 Bytes #-9461 (0) @ EU
BID : HD_2000_152G
Read: GUEST
Subj: HamDigitalDigest 2000/152G
Path: DB0AAB<DB0ZKA<DB0GPP<DB0OFI<DB0LEL<DB0LX<DB0RBS<DB0PSC<DB0ACH<DB0PKE<
DB0SM<PI8DAZ<PI8GCB<PI8HGL
Sent: 000601/0004Z @:PI8HGL.#ZH1.NLD.EU #:46287 [Den Haag] FBB $:HD_2000_152G
From: PA2AGA@PI8HGL.#ZH1.NLD.EU
To : HDDIG@EU
Date: Thu, 01 Jun 00 00:21:22 MET
Message-Id: <hd_2000_152G>
From: pa2aga@pe1mvx.ampr.org
To: hd_broadcast@pa2aga.ampr.org
X-BBS-Msg-Type: B
> > send and receive Internet EMAIL. I guess it was really designed for more
> > permanent portable stations (like Marine Mobile). What a PITY!
> >
> > 73's
> > Rob
> >
> > Perhaps
> > "Jerry Flanders" <jflanders2@home.com> wrote in message
> > news:39333958.373843085@news...
> > > 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&m
> > sg_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: Wed, 31 May 2000 01:41:33 -0400
From: "Rob" <Pse@NoEmail.Com>
Subject: N0ZO no longer supports Keyboard inputs!
Hi Rick,
I appreciate that the WRU feature implemented in the PK-232/900 in Pactor
was a "design decision" made by AEA (not by Timewave). I am just
questioning whether this design decision makes any sense.
I have never seen the WRU feature implemented by any other TNC manufacturer
for Pactor. The WRU feature is typically only implemented for AMTOR. But I
am sure there may be some commercial users who may find the WRU feature
useful in Pactor (if they want more than just than callsign provided by the
Pactor protocol) in the ASCII mode.
But from my perspective, the WRU feature does not make any sense when
receiving binary files in the transparent mode or host mode (especially if
the PK-232 and PK-900 simply sends the serial number of the EPROM as the WRU
text).
I don't think it is fair to point fingers at the F6FBB protocol. In my
view, PACTOR was designed to send and receive the FULL ASCII character set
including graphics characters etc in the binary or transparent mode. It was
designed to be a replacement to H.F. packet.
Until I read the posts in this thread and on the WINLINK reflector archive,
I always thought I could receive (and send) any binary file in the PK-900
Pactor TRANSPARENT mode (just like receiving a binary file in the Packet
Transparent mode) using a SIMPLE DUMB TERMINAL program.
But the PK-900 manual does mention that you can turn off the WRU feature for
BOTH AMTOR and PACTOR at the same time using one of the Usebits. But I
don't think the USEBIT setting has any effect when the PK-900 is receiving
binary files in the Pactor transparent mode. From my perspective, this is
very strange and makes little sense. If I am wrong, please correct me.
I would prefer to see separate USEBITS to turn on and off the WRU features
independently for AMTOR and PACTOR. (i.e. Turn on the WRU feature for
AMTOR and turn off the WRU feature for Pactor).
I agree that most HAM's probably won't want to pay $50 just for an
"improved" or properly implemented WRU feature in Pactor and AMTOR (if their
PK-232 or PK-900 already has the Pactor upgrade EPROM).
I am very glad to hear that Timewave will consider improving the WRU feature
if they decide to release a newer version of firmware for the PK-232 and
PK-900 in the future.
But Timewave still receives orders from Hams for your excellent DSP upgrade
(or even the simple PACTOR non DSP upgrade) for the PK-232 and PK-900. If
it is not too difficult, why not supply a newer version of firmware with an
"improved" WRU feature in Pactor for these customers? I am sure these
customers who are just purchasing your DSP or firmware upgrade for the
PK-232 and PK-900 would appreciate it. You may also get some customers
purchasing the firmware upgrade just for this feature (especially if they
want to send binary files using Winlink or even a simple terminal program).
I wouldn't think it would be very difficult to release new firmware that
provides an option (e.g. USEBIT) to completely turn off WRU in the Pactor
Transparent mode (or host mode) in the PK-232 or PK-900.
73's
Rob
"Rick Ruhl" <ricker@cssincorp.com> wrote in message
news:cp0Z4.139437$681.2553896@news-east.usenetserver.com...
Rob,
One of the things that you have to watch out for, is not to break something
since it wasn't a bug, but a design decision. I do know that WLO and Globe
Wireless do use the WRU for their ID. As I said, it's very sketchy why it
was put it (it was during the Rod Proctor days at AEA), and I'm sure even
Mike Lamb (former owner of AEA) doesn't know the whole story on why Rod
mandated it be put in.
One of the things Randy and John (Douglas) did acknowledge in the
conversation with the Winlink people, is that if there is a future revision
of the firmware, then they'll look into putting in an option for turning it
off. This has been acknowledged from the very beginning and I know they are
people of their word.
However, I don't think many hams or mariners would be willing to spend $50
for a firmware upgrade just to work around an issue that can be worked
around in software. The installed base is what is important, and personally
I feel that since Winlink is free, it's silly for someone to have to pay for
To be continued in digest: hd_2000_152H
Read previous mail | Read next mail
| |
