And while you're munching on this thought, what I want most re:TCP
function is for the program to automatically try to connect to my
default, first, preferred, you name it node even if that is at
127.0.0.1 (which a great many people are now doing ala ARUser).

I don't know how many time's I've forgotten to restart the connection
after bringing up the program and realizing 10 or 15 munutes later
when I noticed no spots coming through...

Anything in the .tcp file to make that happen Paul??

73, Tom W1TJL

PS and so that this does not sound like a complaint, I still thik
DX4Win is the best GP logging program out there...  Great job!

On 4/9/07, n4dsp <[EMAIL PROTECTED]> wrote:
> Paul,
> I no longer have the email you forwarded to me since it was 3 years ago.  I
> asked you if something could be incorporated into the dx4win program that
> when a node drops the connection the dx4win program will sense that and will
> automatically try and connect you once again to that node. I did not mean in
> my email to you to have a "keep alive" function on the node and I was clear
> about that. This was putting the burden on the owner of the node.
> So can something be incorporated into the dx4win program to automatically
> sense that the node connection has terminated and the dx4win program to
> automatically connect back to that node?
>
> john-n4dsp
>
> ----- Original Message -----
> From: "Paul van der Eijk" <[EMAIL PROTECTED]>
> To: "n4dsp" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>; "dx4win"
> <[email protected]>
> Sent: Monday, April 09, 2007 10:23 AM
> Subject: Re: [Dx4win] (no subject)
>
>
> > John,
> >
> > You are misinterpreting what was said. A while ago, we checked with a
> > number of
> > node operators, and found that a 'keep alive' ability was no longer an
> > issue. Before that,
> > keeping a connection alive was seen as bad practice.
> >
> > Since version 7.02, DX4WIN has a keep alive feature  (not well
> > documented):
> >
> > In the dx4win.tcp file, add a vertical bar at the end of the line followed
> > by an integer.
> > The integer field is the number of minutes set for the timer. When the
> > user types
> > a character in the packet window, the timer is reset to start over again.
> >
> > From the dx4win.tcp file, the following entry:
> > 25 spots OH2AQ,http://oh2aq.kolumbus.com/dxs/dx25.html?|3
> >
> > This download the last 25 spots every 3 minutes.
> > Same field can be added to telnet addresses.
> >
> > --Paul
> >
> > At 08:06 AM 4/9/2007, n4dsp wrote:
> >>He has addressed this. About three years ago I asked about this and was
> >>told this was not considered an important issue!
> >>
> >>john-n4dsp
> >>
> >>>How many years have users been complaining about this Jim? (rhetorical
> >>>question) It's strange that Paul never addressed it...
> >>>Mel...
> >>>VE2DC
> >>
> >>_______________________________________________
> >>Dx4win mailing list
> >>[email protected]
> >>http://mailman.qth.net/mailman/listinfo/dx4win
> >
> > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> > Paul van der Eijk (KK4HD)
> > [EMAIL PROTECTED]
> > http://www.dx4win.com
> >
>
> _______________________________________________
> Dx4win mailing list
> [email protected]
> http://mailman.qth.net/mailman/listinfo/dx4win
>


-- 
Tom LeClerc, Amateur Radio Station W1TJL
 (past calls WB1CBY, /VE8,XL8,VO1)

          LeClerc Consulting
         email: [EMAIL PROTECTED]
        PC/Network Consulting
From [EMAIL PROTECTED]  Mon Apr  9 11:28:02 2007
From: [EMAIL PROTECTED] (Jim Reisert AD1C)
Date: Mon Apr  9 11:32:18 2007
Subject: [Dx4win] How to order nodes in DX4WIN.TCP file
Message-ID: <[EMAIL PROTECTED]>

How should I order the nodes in the DX4WIN.TCP file?

- Sorted first by DXCC entity prefix, then by callsign. Within Australia,
  Canada and the United States, the nodes are sorted first by state or
  province, then by callsign.

  For reference, see:

  http://www.dxcluster.info/telnet.shtml

- in straight alphabetical order by callsign, regardless of QTH

- some other way

Thanks & 73 - Jim AD1C


--
Jim Reisert AD1C, 7 Charlemont Court, North Chelmsford, MA 01863
USA +978-251-9933, <[EMAIL PROTECTED]>, http://www.ad1c.us
From [EMAIL PROTECTED]  Mon Apr  9 12:06:48 2007
From: [EMAIL PROTECTED] (wo2n)
Date: Mon Apr  9 12:11:06 2007
Subject: [Dx4win] How to order nodes in DX4WIN.TCP file
References: <[EMAIL PROTECTED]>
Message-ID: <[EMAIL PROTECTED]>

I would say Callbook format, conventional and practical.
73 Bernie/WO2N.>
----- Original Message ----- 
From: "Jim Reisert AD1C" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Monday, April 09, 2007 11:28 AM
Subject: [Dx4win] How to order nodes in DX4WIN.TCP file


> How should I order the nodes in the DX4WIN.TCP file?
> 
> - Sorted first by DXCC entity prefix, then by callsign. Within Australia,
>  Canada and the United States, the nodes are sorted first by state or
>  province, then by callsign.
> 
>  For reference, see:
> 
>  http://www.dxcluster.info/telnet.shtml
> 
> - in straight alphabetical order by callsign, regardless of QTH
> 
> - some other way
> 
> Thanks & 73 - Jim AD1C
> 
> 
> --
> Jim Reisert AD1C, 7 Charlemont Court, North Chelmsford, MA 01863
> USA +978-251-9933, <[EMAIL PROTECTED]>, http://www.ad1c.us
> _______________________________________________
> Dx4win mailing list
> [email protected]
> http://mailman.qth.net/mailman/listinfo/dx4win
From [EMAIL PROTECTED]  Mon Apr  9 13:32:50 2007
From: [EMAIL PROTECTED] (Alan Zack)
Date: Mon Apr  9 13:37:08 2007
Subject: [Dx4win] Nodes
References: <[EMAIL PROTECTED]><[EMAIL PROTECTED]>
        <[EMAIL PROTECTED]>
Message-ID: <[EMAIL PROTECTED]>

Along this line, how can I find a Node near Las Vegas, NV?
In my drop down internet address list I only find N7OD in Hemet, CA, as 
being the closet to me but still some distance away.  Next would be N7TR in 
Reno, NV, but that is about twice as far away as Hemet, CA.  I also find 
N7US in Mesa, AZ, but it is no longer in use.  Looks like N7US moved to Ill.

I really like this feature and have just started using it with the N8S 
operation.  It shows me where N8S is working.  I go to his freq and if I 
work him he is added to the log by just clicking on his spot.  I hadn't used 
it before because I could not find a node closer to Las Vegas.

TIA & 73
______________________________________
Alan Zack
Amateur Radio Station K7ACZ
Official USCG Auxiliary Comm Station
Las Vegas, Nevada, USA
Delta Rocket Quality Engineer, The Boeing Company, Retired
Aviation Chief Warrant Officer,  U.S. Coast Guard, Retired

----- Original Message ----- 
From: "Paul van der Eijk" <[EMAIL PROTECTED]>
To: "n4dsp" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>; "dx4win" 
<[email protected]>
Sent: Monday, April 09, 2007 7:23 AM
Subject: Re: [Dx4win] (no subject)


> John,
>
> You are misinterpreting what was said. A while ago, we checked with a 
> number of
> node operators, and found that a 'keep alive' ability was no longer an 
> issue. Before that,
> keeping a connection alive was seen as bad practice.
>
> Since version 7.02, DX4WIN has a keep alive feature  (not well 
> documented):
>
> In the dx4win.tcp file, add a vertical bar at the end of the line followed 
> by an integer.
> The integer field is the number of minutes set for the timer. When the 
> user types
> a character in the packet window, the timer is reset to start over again.
>
> From the dx4win.tcp file, the following entry:
> 25 spots OH2AQ,http://oh2aq.kolumbus.com/dxs/dx25.html?|3
>
> This download the last 25 spots every 3 minutes.
> Same field can be added to telnet addresses.
>
> --Paul
>
> At 08:06 AM 4/9/2007, n4dsp wrote:
>>He has addressed this. About three years ago I asked about this and was 
>>told this was not considered an important issue!
>>
>>john-n4dsp
>>
>>>How many years have users been complaining about this Jim? (rhetorical
>>>question) It's strange that Paul never addressed it...
>>>Mel...
>>>VE2DC
>>
>>_______________________________________________
>>Dx4win mailing list
>>[email protected]
>>http://mailman.qth.net/mailman/listinfo/dx4win
>
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> Paul van der Eijk (KK4HD)
> [EMAIL PROTECTED]
> http://www.dx4win.com
>
> _______________________________________________
> Dx4win mailing list
> [email protected]
> http://mailman.qth.net/mailman/listinfo/dx4win
> 

Reply via email to