| |
PA2AGA > HDDIG 01.06.00 15:25l 222 Lines 7358 Bytes #-9461 (0) @ EU
BID : HD_2000_152E
Read: GUEST
Subj: HamDigitalDigest 2000/152E
Path: DB0AAB<DB0SL<DB0RGB<DB0MRW<DB0ERF<DB0SAW<DB0OCA<DB0FC<DB0CL<DB0PDF<
DB0SM<PI8DAZ<PI8GCB<PI8HGL
Sent: 000531/2343Z @:PI8HGL.#ZH1.NLD.EU #:46285 [Den Haag] FBB $:HD_2000_152E
From: PA2AGA@PI8HGL.#ZH1.NLD.EU
To : HDDIG@EU
Date: Thu, 01 Jun 00 00:21:18 MET
Message-Id: <hd_2000_152E>
From: pa2aga@pe1mvx.ampr.org
To: hd_broadcast@pa2aga.ampr.org
X-BBS-Msg-Type: B
sent (it's something that was put in during the last days of AEA and no one
seems to know why). We gave them the method that is used in PakRatt to avoid
this issue and I assume they decided not to support that, but just the ASCII
mode transfers.
PcPakRatt has been doing YAPP binary tranfers for years with the PK-232, as
well as the next version of PKTerm, which will support YAPP in Pactor.
--
Rick Ruhl
President, Creative Services Software
http://www.cssincorp.com
"Rob" <Pse@NoEmail.Com> wrote in message news:vdSY4.3580$qS3.9230@tor-
nn1.netcom.ca...
> Hi Jerry,
>
> I always thought that the PK-232 could send and receive binary files in
> PACTOR. The PK-900 can send and receive binary files in PACTOR using either
> a terminal mode program or a host mode program.
>
> Surely, the PK-232 can at least send and receive binary files using a host
> mode program?? Is my understanding wrong?
>
> Perhaps the problem is with AIRMAIL. It sounds like AIRMAIL does not
> support the PK-232's hostmode.
>
> I agree with others that I don't like the idea of FORCING Hams to use
> particular client software to link up with a BBS. In my view, the WINLINK
> BBS's should continue to accept simple commands using ANY TNC with ANY
> client software. (I have no problems with HAM's who want to use AIRMAIL.
> But it should be an option)
>
> For portable use, I like using a small portable dumb terminal that runs on a
> couple of AA batteries. These terminal are very inexpensive these days and
> are VERY durable with NO moving parts like hard drives etc.
>
> You also don't have to worry about damaging an expensive laptop when hiking,
> camping etc. Unfortunately, I can't access some of the WINLINK BBS's with
> this dumb terminal NO MATTER what TNC I am using.
>
> I am not going to buy a second hand laptop for my hiking and camping trips
> etc. They are simply not very durable.
>
> I thought one of the purposes of WINLINK was to allow portable stations to
> 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 04:05:17 GMT
From: "Hank Oredson" <horedson@att.net>
Subject: N0ZO no longer supports Keyboard inputs!
"Steve Sampson" <ssampson@usa-site.net> wrote in message
news:sj8i9g5o5pj135@corp.supernews.com...
> "Hank Oredson" wrote
> >
> > "Steve Sampson" wrote
> >>
> > > I think when Hams finally accept high speed data pipes as
> > > carrying pure data, it will be the day they enter the 20th Century.
> >
> > As opposed to "impure data"?
>
> No. Right now we have Hams who sit by their consoles, monitor
> the contents, and then shut off the node, or jam the person off the
> air. "We don't allow BBS data on our Nodes." or, "We don't
> allow keyboard to keyboard on our nodes." These type of silly
> antics.
>
> By "pure data" I mean, it's all just data, not denoted by content.
Like the nodes in Southern Oregon that have an ID string that says
something like "No TCP/IP allowed on this frequency!".
Idiots.
--
... Hank
http://horedson.home.att.net
------------------------------
Date: Tue, 30 May 2000 23:22:14 -0500
From: "Steve Sampson" <ssampson@usa-site.net>
Subject: N0ZO no longer supports Keyboard inputs!
As a former prisoner of Klamath Falls, that sounds pretty
much like something they would do.
I always wondered where the Falls were in Klamath. Turns
out they were referring to the rock falls which kill tourists
every year in their campers and motor homes on Highway 97...
"Hank Oredson" wrote
> > By "pure data" I mean, it's all just data, not denoted by content.
>
> Like the nodes in Southern Oregon that have an ID string that says
> something like "No TCP/IP allowed on this frequency!".
>
> Idiots.
------------------------------
Date: Tue, 30 May 2000 23:19:12 -0500
From: "Rick Ruhl" <ricker@cssincorp.com>
Subject: N0ZO no longer supports Keyboard inputs!
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
To be continued in digest: hd_2000_152F
Read previous mail | Read next mail
| |
