Yes, but it took longer than 30-90 seconds. More like about 5 minutes.
Zack W9SZ
On Sun, 16 Feb 2003, TPL III wrote:
> Has anybody gotten a response from this yet?
>
>
> As promised subscribers of The Daily DX and The Weekly DX are the
> first to know and try out the AH3D log search. I woul
> Has anybody gotten a response from this yet?
No problem on this end either. Clever way of handling it.
George K. Watson
K0IW
---
Subscribe/unsubscribe, feedback, FAQ, problems, etc
DX-NEWS http://njdxa.org/dx-news
DX-CHAT: http://njdxa.org
Worked fine for me.
Casey/KQ4YI
TPL III wrote:
> Has anybody gotten a response from this yet?
>
> As promised subscribers of The Daily DX and The Weekly DX are the
> first to know and try out the AH3D log search. I would personally
> like to thank N4GN, Tim, for helping out with this process.
>
Yes, I tried it last night and it works great, although as the message says
you have to give it the right callsign. My RTTY QSO was under "KLØS/4" and
my SSB and CW contacts under "KLØS/W4". Took just a few seconds to return
the results.
Good Hunting!
Dino KLØS/4
--
Has anybody gotten a response from this yet?
As promised subscribers of The Daily DX and The Weekly DX are the
first to know and try out the AH3D log search. I would personally
like to thank N4GN, Tim, for helping out with this process.
In order to check the AH3D log search you must do the fo
Forwarded with permission
--- Forwarded message follows ---
Date forwarded: Sat, 15 Feb 2003 11:16:08 -0500
Date sent: Sat, 15 Feb 2003 16:01:58 +
From: "Bernie McClenny, W3UR" <[EMAIL PROTECTED]>
Subject:AH3D log search now up an
