| |
PA2AGA > HDDIG 20.09.00 23:22l 209 Lines 7134 Bytes #999 (0) @ EU
BID : HD_2000_255C
Read: DC1TMA GUEST
Subj: HamDigitalDigest 2000/255C
Path: DB0AAB<DB0SL<DB0RGB<DB0MRW<DB0ERF<DB0BRI<DB0HAG<DB0ACH<DB0OVN<PI8JOP<
PI8ZAA<PI8HGL
Sent: 000920/1902Z @:PI8HGL.#ZH1.NLD.EU #:16260 [Den Haag] FBB $:HD_2000_255C
From: PA2AGA@PI8HGL.#ZH1.NLD.EU
To : HDDIG@EU
Date: Tue, 19 Sep 00 00:12:24 MET
Message-Id: <hd_2000_255C>
From: pa2aga@pe1mvx.ampr.org
To: hd_broadcast@pa2aga.ampr.org
X-BBS-Msg-Type: B
system??
It worked on my old PC which was a 486 and has original w95, but an having a
H*** of a time trying to get it right on this new PC......AMD k6-166...old
shack machuine died, so replaced it with the older big machine.....that way
the kids get this shiny new HP.....
Either that or a suggestion for new dual port software.......
de N3DDY
------------------------------
Date: Sun, 17 Sep 2000 19:25:53 -0500
From: "Rick Ruhl" <ricker@cssincorp.com>
Subject: PakRatt for Windows??
PakRatt 2.0 has Y2k issues as well as it wasn't 32 bit aware. We purchased
the source code to it back in March of 1999 and made the fixes.
You can update to Pakratt 2.1 for $30 or up to Pkterm '99 from PakRatt for
$50. Pkterm '99 is full 32 bit and will run on all 32 bit version of
Windows, include Windows Me and 2000
http://www.cssincorp.com/pkterm
Rick - N4GDO
"Timmins" <timmins@penn.NOSPAM.com> wrote in message
news:V3dx5.2695$JV3.7807@newsfeed.slurp.net...
> Has anyone successfully convinced PakRatt 2.0 for Windows to ru on a
w95osr2
> system??
> It worked on my old PC which was a 486 and has original w95, but an having
a
> H*** of a time trying to get it right on this new PC......AMD k6-166...old
> shack machuine died, so replaced it with the older big machine.....that
way
> the kids get this shiny new HP.....
>
> Either that or a suggestion for new dual port software.......
>
> de N3DDY
>
>
------------------------------
Date: Mon, 18 Sep 2000 20:28:37 +1100
From: Chris Maxwell <vk3vsw@iprimus.com.au>
Subject: Satupdat.exe v1.85e Wanted.
Hi All,
I'm a Fbb7.00g (dos) sysop and I'm looking for the latest satupdat.exe
utility version 1.85e. The version that comes with Fbb7.00g is NOT y2k
compliant.
I've looked everywhere...............comments appreciated.
Regards Chris, VK3VSW.
vk3vsw@iprimus.com.au
------------------------------
Date: Sun, 17 Sep 2000 15:42:17 GMT
From: "Hank Oredson" <horedson@att.net>
Subject: TCP/IP Address
"Rob Janssen" <nomail@rob.knoware.nl> wrote in message
news:slrn8s90e6.qv.nomail@linux.pe1chl.ampr.org...
> Hank Oredson <horedson@att.net> wrote:
>
> [Hank has something to add to every claim, but does not carefully read them
> before he replied]
Nonesense.
> I am not going to play this game with you, Hank. But I only want to add
> that a solution that needs multiple machines is not going to make it when
> you want many packet radio amateurs as users of your system. That is
> only for the nerds.
> Rob
Rob,
I think my observations are right on target. There are perhaps
several reasons tcp/ip over ham radio has not become popular.
The fact that the usual (e.g. Windows, Mac) applications could
not be used is one reason. The difficulty of getting *NOS setup
and running properly is another. A Linux solution is not of
interest to most hams. The applications embeded into the various
*NOS executables are either not easy to use, don't work well,
or do not exist at all. One expects, for example, to click on
a file and attach it to an email message.
A different architecture is needed.
Win95 and Win98 with both run virtual DOS machines.
They work just as well as real DOS machines to run NOS as an
interface/gateway etc. Just takes a second ethernet controller.
This machine is running that configuration. Ethernet controller cost me
$7 at Frys a few months back. Now I don't have the problem of
"all applications must be bound into the NOS memory image."
All the usual Windows applictions work over ham radio tcp/ip
AND over ham radio BBS links.
Your comment applies to Unix solutions as well: very few hams
are interested in running Unix, other than a few nerds.
To get hams to use tcp/ip there needs to be a better solution than either
of these. It must be simple to install and simple to configure and simple
to use. It must run in Windows. SNOS is an experiment in that direction.
Are there any other solutions available?
--
... Hank
http://horedson.home.att.net
------------------------------
Date: Sun, 17 Sep 2000 16:30:39 GMT
From: nomail@rob.knoware.nl (Rob Janssen)
Subject: TCP/IP Address
Hank Oredson <horedson@att.net> wrote:
>To get hams to use tcp/ip there needs to be a better solution than either
>of these. It must be simple to install and simple to configure and simple
>to use. It must run in Windows. SNOS is an experiment in that direction.
>Are there any other solutions available?
Yes, at least two of them. From SV1AGW and from the Flexnet group.
These don't need the hackery you propose, they just implement a network
interface that runs packet protocols (just like the Linux solution).
They are available for about two years now, but they came too late to
leverage (popular buzzword) the initial developments in amateur TCP/IP into
the average-ham shack.
There was a painful gap between the introduction of Windows 95 and the
usability of its TCP/IP networking on amateur packet radio. One would
have expected the TNC manufacturers to step in with a TNC with modified
firmware to provide a PPP interface on the ASYNC end while running IP over
AX.25 on the radio. Then, it would have been possible to use the standard
dialup networking of Windows 95 with amateur radio, with the addition of
only a small control-panel program to perform some settings of the TNC.
But no, they all seemed to be glued to KISS and Hostmode.
Rob
--
+----------------------------------+--------------------------------------+
| Rob Janssen pe1chl@amsat.org | WWW: http://www.knoware.nl/users/rob |
| AMPRnet: rob@pe1chl.ampr.org | AX.25 BBS: PE1CHL@PI8WNO.#UTR.NLD.EU |
+----------------------------------+--------------------------------------+
------------------------------
Date: Sun, 17 Sep 2000 17:34:15 GMT
From: "Hank Oredson" <horedson@att.net>
Subject: TCP/IP Address
"Rob Janssen" <nomail@rob.knoware.nl> wrote in message
news:slrn8s9sdf.qv.nomail@linux.pe1chl.ampr.org...
> Hank Oredson <horedson@att.net> wrote:
>
> >To get hams to use tcp/ip there needs to be a better solution than either
> >of these. It must be simple to install and simple to configure and simple
> >to use. It must run in Windows. SNOS is an experiment in that direction.
>
> >Are there any other solutions available?
>
> Yes, at least two of them. From SV1AGW and from the Flexnet group.
> These don't need the hackery you propose, they just implement a network
> interface that runs packet protocols (just like the Linux solution).
Have looked at both.
Did not see how they handled the nntp <-> bulletin
and smtp/pop3 <-> personal message translations.
Perhaps I missed this. Will check them out again, it has been a year
or so since I last looked at them. Flexnet was not an option for me
since I have no TNCs that could support 6PACK. I could not figure out
how to make the SV1AGW stuff do what is needed.
One $7 ethernet controller is a lot cheaper than replacing a half-dozen TNCs.
To be continued in digest: hd_2000_255D
Read previous mail | Read next mail
| |
