| |
F8BOE > AGWPE 24.02.04 22:21l 157 Lines 5863 Bytes #999 (0) @ WW
BID : O24DB0FBB06F
Read: GUEST
Subj: AGWPE test report
Path: ON0AR<F6KMO<ON0BEL<ON0AR<ON0AR<DB0GOS<DB0FBB
Sent: 040224/2117z @:DB0FBB.#NRW.DEU.EU [Dortmund, JO31RM, OP:DK1DO] BCM1.42
From: F8BOE @ DB0FBB.#NRW.DEU.EU (Olivier)
To: AGWPE @ WW
Reply-To: F8BOE @ F6KDL.FCAL.FRA.EU
X-Info: No login password
AGWPE TEST REPORT
AGWPE addons (http://www.elcom.gr/sv2agw/agwbay.htm)
Well, these addons are a good idea to begin with packet radio when you don't
know anything about it.
Very simple utilities to chat over packet radio or to read the mails you
receive on your favourite BBS. But when it comes to send messages it can get
messy, or even near to impossible for real file transfert (uncomplicated up-
and download).
The digipeater addons are too difficult for the novice to configure or to
make work properly.
For real packet trafic, the best way is to step up for a more complete packet
terminal program like Winpack (for the challengers) or more efficient and of
course uncomplicated programs such as Paxon or WPP if you don't want to take
your Prozac every day.
AGWPE Pro (PEPRO) (http://www.elcom.gr/sv2agw/agwbay.htm)
I tested this "new" version which should "work better" with the Win XP, NT,
Pro series.
The only differences with the standart AGWPE are an added "configuration
interface" for those who like little windows with cute icons and a 49$
expensive payware bill to have an "unrestricted" driver.
I tested the "all new" Baycom modem driver which didn't work and didn't fare
very well.
So there's nothing really new about it!
Paxon 2.00.1114B (http://paxon.de/)
This version of Paxon was tested with AGWPE, giving poor results in file
transfer quantity whereas the link quality was constantly at 100% but
demanding up to four times more acc packets, and so lowering the file
transfer bitrate!
It seems to be the same case with other terminal programs tested such as
Winpack and WPP.
But other problems occcured first
- Firewall options: access to i-net must be granted to AGWPE with no
restriction in order to communicate with Paxon
- AGWPE users: "localhost" must be included in AGWPE's users list with the
right port number (8000 default)
- AGWPE's Winsock interface must be activated
Connection to Digis
- The first Digi can be connected with no problem
- When trying to connect a second Digi from the connected port (Mailbox for
example) AGWPE looses itself; no hops are possible with successive
connections.You must connect directly the right Digi or enter the complete
path to it!
- When trying to connect several Digis on several terminal windows, a
different port number must be manually allocated at each connection, whereas
it is automaticaly done when using Flex32 or the TNC's Hostmode.
- When connected to a DXCluster, if the DXC's call changes to "local" (on
HB9W-8) after entering a command line the connection is no more recognised by
AGWPE and you cannot diconnect it properly nor enter any other command
line. Adding "local" in AGWPE's users list does not cure the problem.
WPP (http://www.dh3ww.de/wpp/index.htm)
A good german packet program more in the old Baycom 1.6 philosophy, working
as Paxon, with Flex32/PCFlexnet, AGWPE and TNC2 hostmodes.
There were less configuration subtilities than with Paxon to make it work
with AGWPE. But the tranfer bitrates were as poor as when using Paxon.
Winpack (http://www.ui-view.com/winpack/index.shtml)
Well, as this program really sucks me (sorry but I really hate it) I was not
able to make real data transfer, it was much more like a "get the data file
read on the BBS or from the PC" and compare the elapsed times needed to get
the whole file sent.
But it was sufficient to test the linking to Winlog32 with and without AGWPE.
UI-View (http://www.ui-view.com/winpack/index.shtml)
This application is perhaps the one that works best with AGWPE. Not only with
the soundcard but also with the other default hardware drivers included in
the AGWPE program. The Added drivers DO NOT WORK under any XP/NT/Pro Windows
versions (only with Win 95 not pro and Win 98). The problem with the added
drivers seem to be the same with PEPRO (AGWPE Pro).
Windows XP and USB com ports
I'm using a laptop computer running under Win XP for my radio applications
(log, digimodes) and the different hardwares (TNC2, Souncard interfaces) used
are built with serial port connectors.
To connect them on my laptop, I use an UC232A type USB to serial adaptors
(only for USB 1.1 and 2.0 not 1.0).
I tried to use my old TCM3105 based Baycom modem with AGWPE with no success.
AGWPE's added drivers do not work with Windows XP, NT or Pro series!
I tried with the high$$$ Payware AGWPE-PRO (known as PEPRO) but it didn't
work better. The only thing I got was a superb Windows crashdown with disk
error reports after the scandisk!
Winlog 32 (http://www.winlog.pwp.blueyonder.co.uk/winlog/dl_wl32.htm)
Winlog 32 (tested from v.1.7 to 2.0) can sort and display DXC informations
thru a Winpack or AGWPE linked connection to the local DXC server. Good job,
G0CUZ!
This option seems to run well when using directly Winpack but When linked to
AGWPE (with Paxon and WPP it was the same), the delay between the DXC
information arrival on the terminal's screen and it's displaying on Winlog's
DXC window grows up to 30 minutes, especially when file transfers are done
with the terminal program. All I can say is that it's not a firewall problem
nor a terminal program problem.
If you are, as I am, not really convinced by AGWPE, you can always test some
of these applications using Flexnet or Flex32.
You can get all you need at:
http://www.afthd.tu-darmstadt.de/~flexnet/
http://www.uspacket.net/
http://www.bythebays.com/neflexnet/sw.htm
http://www.afthd.tu-darmstadt.de/~flexnet/modules.html
http://f4dyx.free.fr/ to get the kiss.ini files for Kenwood's integrated TNCs
Winlog32 and UI-View will not work under Flex but it's worth trying the
packet terminal programs.
73 de F8BOE Olivier...-.-
Read previous mail | Read next mail
| |
