OpenBCM V1.13 (Linux)

Packet Radio Mailbox

DB0FHN

[JN59NK Nuernberg]

 Login: GUEST





  
ZL3AI  > APRS     15.11.00 13:44l 208 Lines 6409 Bytes #999 (0) @ WW
BID : 34436_ZL3AI
Read: GUEST
Subj: TAPR Digest, Nov 12, 3/3
Path: DB0MRW<DB0SON<DB0ERF<DB0HOT<OK0PKL<OK0PPR<OK0PPL<OK0POK<9A0YRB<PP5BLU<
      HA3PG<WB0TAX<KP4IG<EA3RKU<EA3CWZ<EA3URS<ZS6RO<ZL3VML
Sent: 001113/1032Z @:ZL3VML.#80.NZL.OC #:47178 [Chch-NZ] FBB7.00g25 $:34436_ZL3
From: ZL3AI@ZL3VML.#80.NZL.OC
To  : APRS@WW


I believe these features are in the 8.42 version. If not, I downloaded 8.46
from TAPR's site which now has 8.47 as well.

73,
Wayne KE6DZD
EN21ad




----------------------------------------------------------------------

Subject: Re: Client connection to WinAPRS v 247
From: "Jeff Brenton" <jeffb@espi.com>
Date: Sun, 12 Nov 2000 13:14:00 -0600
X-Message-Number: 13

> "Callbook Info Not Found".

Are you getting this message on your server machine, or the client? Client's
can't access the callbook on a server - they have to have a local copy.
Server will need to make sure the callbook index is current; rebuild it to
be sure.

Jeff Brenton, Amateur Radio call sign KA9VNV
http://espi.com
Questionable web page: http://dididahdahdidit.com
That strange feeling that you've never
done this before: http://uvajed.espi.com

"Modern Liberalism: The embodiment of an irrational fear of
letting other people run their own lives."



----------------------------------------------------------------------

Subject: Re: WinAPRS Problems/Questions. Brothers Sproul are you still 
alive?????
From: "Jeff Brenton" <jeffb@espi.com>
Date: Sun, 12 Nov 2000 13:12:05 -0600
X-Message-Number: 14

> can't connect to www.aprs.net

I think you need to edit your APRSERVE.TXT file and change "www.aprs.net" to
"first.aprs.net".

Jeff Brenton, Amateur Radio call sign KA9VNV
http://espi.com
Questionable web page: http://dididahdahdidit.com
That strange feeling that you've never
done this before: http://uvajed.espi.com

"Modern Liberalism: The embodiment of an irrational fear of
letting other people run their own lives."



----------------------------------------------------------------------

Subject: Re:  Help with setting up APRS digi.
From: "Jeff Brenton" <jeffb@espi.com>
Date: Sun, 12 Nov 2000 13:18:46 -0600
X-Message-Number: 15

What TNC and software do you have available, Ken? Check out my Questionable
web page for leads to a number of digipeater solutions, including detailed
set-up information for Kantronics TNCs with v8.2 and later software.

Other solutions available are uidigi, a ROM image available for TNC-2 and
clones that does MUCH better than the KPC-3 at providing optimized-for-APRS
features, and several computer-assisted digipeater packages, which will use
any KISS-capable TNC. Links to the home pages of these are on my page.

In general, a minimul digi for APRS supports the aliases RELAY and WIDE, but
better ones support WIDEn-n forwarding. Explanations of these terms are also
found on the Questionable page, under the APRS/DOS documentation's DIGIS.TXT
file.

Jeff Brenton, Amateur Radio call sign KA9VNV
http://espi.com
Questionable web page: http://dididahdahdidit.com
That strange feeling that you've never
done this before: http://uvajed.espi.com

"Modern Liberalism: The embodiment of an irrational fear of
letting other people run their own lives."



----------------------------------------------------------------------

Subject: test-please ignore
From: "bob" <w2g3zfj@optonline.net>
Date: Sun, 12 Nov 2000 14:28:13 -0500
X-Message-Number: 16

test from new account


----------------------------------------------------------------------

Subject: Re: Client connection to WinAPRS v 247
From: "ke4slc" <ke4slc@midusa.net>
Date: Sun, 12 Nov 2000 14:07:19 -0600
X-Message-Number: 17

I can't speak for a "REAL NETWORK" however on my local peer to peer network,
I access the callbook database from a separate machine. The database is on
computer  #1 and WinAprs accesses that info from computer #2. I simply map
the remote drive in Win98 and point WinAprs to that drive letter under
settings/callbook database.
73 de Dan

----- Original Message -----
From: Jeff Brenton <jeffb@espi.com>
To: TAPR APRS Special Interest Group <aprssig@lists.tapr.org>
Cc: aprssig <aprssig@tapr.org>
Sent: Sunday, November 12, 2000 1:14 PM
Subject: [aprssig] Re: Client connection to WinAPRS v 247


> > "Callbook Info Not Found".
>
> Are you getting this message on your server machine, or the client?
Client's
> can't access the callbook on a server - they have to have a local copy.
> Server will need to make sure the callbook index is current; rebuild it to
> be sure.
>
> Jeff Brenton, Amateur Radio call sign KA9VNV




----------------------------------------------------------------------

Subject: Re: Client connection to WinAPRS v 247
From: "Jeff Brenton" <jeffb@espi.com>
Date: Sun, 12 Nov 2000 14:16:48 -0600
X-Message-Number: 18

> I access the callbook database from a separate machine.

That's a special case; you've mapped the remote drive to what WinAPRS THINKS
is a local drive. The context I got from the original message, however, was
that it was expected that WinAPRS (as a client) would query the WinAPRS
server that had the callbook for call information, which is not the case.

So long as the client machine maps the WinAPRS server's drive as a local
drive, AND that mapped drive is listed as the source of callbook information
in WinAPRS, then yes, the callbook interface will work just fine on the
client...

Jeff Brenton, Amateur Radio call sign KA9VNV
http://espi.com
Questionable web page: http://dididahdahdidit.com
That strange feeling that you've never
done this before: http://uvajed.espi.com

"Modern Liberalism: The embodiment of an irrational fear of
letting other people run their own lives."



----------------------------------------------------------------------

Subject: Re: Client connection to WinAPRS v 247
From: Jonathan Kaplan <jonk@jskent.com>
Date: Sun, 12 Nov 2000 13:41:34 -0800
X-Message-Number: 19

At 01:14 PM 11/12/00 -0600, Jeff Brenton wrote:
> > "Callbook Info Not Found".
>
>Are you getting this message on your server machine, or the client? Client's
>can't access the callbook on a server - they have to have a local copy.
>Server will need to make sure the callbook index is current; rebuild it to
>be sure.

I get this on the server machine. I've tried rebuilding the index file 
several times.
The info always comes up the same on the database window--the information and
the column labels don't coincide. And the error message is the same.

BTW, I also mapped the sever's copy of the callbook to a local drive letter 
on the client
and didn't get any results either.

73

Jonathan KO6XS




---

END OF DIGEST


{Mensaje distribuido por: EANET (Gracias U.R.E. por el reglamentazo.)}


Read previous mail | Read next mail


 16.11.2026 23:31:05lGo back Go up