| |
PA2AGA > HDDIG 01.06.00 15:06l 213 Lines 7336 Bytes #-9461 (0) @ EU
BID : HD_2000_152D
Read: GUEST
Subj: HamDigitalDigest 2000/152D
Path: DB0AAB<DB0SL<DB0RGB<DB0MRW<DB0ERF<DB0SHG<DB0SM<PI8DAZ<PI8GCB<PI8HGL
Sent: 000531/2333Z @:PI8HGL.#ZH1.NLD.EU #:46284 [Den Haag] FBB $:HD_2000_152D
From: PA2AGA@PI8HGL.#ZH1.NLD.EU
To : HDDIG@EU
Date: Thu, 01 Jun 00 00:21:17 MET
Message-Id: <hd_2000_152D>
From: pa2aga@pe1mvx.ampr.org
To: hd_broadcast@pa2aga.ampr.org
X-BBS-Msg-Type: B
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 20:02:51 GMT
From: "Hank Oredson" <horedson@att.net>
Subject: N0ZO no longer supports Keyboard inputs!
"Steve Sampson" <ssampson@usa-site.net> wrote in message
news:sj7a95rl5pj146@corp.supernews.com...
> The purpose of a BBS is to collect and distribute messages of
> a public nature. The purpose of an electronic mail node, is to
> collect and distribute both public and private messages.
WinLink stations CAN do both, but normally only handle private messages.
> I propose that you want to do that at the highest speed, thus
> you want to compress the data on the transport frequency.
> By allowing non-compressed users on the same frequency, you
> defeat the whole purpose of achieving maximum through-put.
The WinLink "transport frequency" is the internet. All RF use of WinLink
in it's "AirMail" incarnation is from user to host. i.e. it's a bunch of
RF email drops hanging off the internet.
> We have to trust fellow Hams to do the right thing. We trust
> them every day to not commercialize the spectrum, using modes
> that can't be monitored directly.
Har!
> 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"?
> If you don't want people to send "data" over your data system,
> then don't put up a node. If all you want is to be a limit on
> what Hams can transport, you're in the wrong hobby.
You failed to understand the main point below:
> "Markus Lenggenhager" wrote
> > 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.
Ever since the original author of WinLink allowed someone else to
take over development of the system, it has moved more and more
toward a closed, proprietary system. Forcing (or attempting to force)
the use of WinLink-specific clients appears to just be part of the
strategy: to lock out competing software. Keep in mind that the commercial
use of WinLink and similar systems can produce a good deal of income.
You only need to "beat" Inmarsat on price, which is probably not hard.
> > 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.
Exactly.
> > 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!
Well ... the value of bulk transfer protocols like PACTOR-II and CLOVER
is that they work very well for BBS-BBS movement of messages. This allows
hams to time-shift: i.e. carry on QSOs with other hams who are not on the
air at the same time, etc. It's real convenient. PSK31 is not useful for this
mode,
so all use will, by the nature of the protocol, require a human to interpolate
the errors out of the datastream.
> > 73, Markus HB9BRJ
--
... Hank
http://horedson.home.att.net
------------------------------
Date: Tue, 30 May 2000 19:26:07 GMT
From: jflanders2@home.com (Jerry Flanders)
Subject: N0ZO no longer supports Keyboard inputs!
Follow the listbot link below and click on "Winlink/Netlink Home
Page", then join the list. The comments you post to the list will
probably be read by the Winlink crew.
Jerry W4UK
On Tue, 30 May 2000 12:43:57 -0400, "Rob" <Pse@NoEmail.Com> wrote:
>SNIP
>
>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
>>
------------------------------
Date: Tue, 30 May 2000 18:04:27 -0500
From: "Steve Sampson" <ssampson@usa-site.net>
Subject: N0ZO no longer supports Keyboard inputs!
"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.
------------------------------
Date: Tue, 30 May 2000 20:14:42 -0500
From: "Rick Ruhl" <ricker@cssincorp.com>
Subject: N0ZO no longer supports Keyboard inputs!
Rob,
Both Randy Gawtry and I worked with Hans Kessler and Jim Coreman on how to do
the binary transfer modes in Pactor with the PK-232/900/2232/232. One of the
issues was that the PK-232/900/2232 sends out a serial number when a WRU is
To be continued in digest: hd_2000_152E
Read previous mail | Read next mail
| |
