[Dx4win] i am the happier user of DX4WIN

Kostas SV1DPI sv1dpi at otenet.gr
Mon Jan 7 00:46:34 EST 2008


I believe the strongest point of dx4win is this what you are talking about. 
We write a call and we all have the right country and the right zone. I am 
tha cq checker in Greece and a friend was asking me what is this zone 2, 
never worked. I asked his log because i was sure he has worked the zone as 
he participates in contests very often and dx4win found 2-3 stations worked. 
He used logger. Also same results with other programs. What is the more 
important from a logging program. These two: 1. Keep the log right  2. shows 
the right country file.
You say that your log is not right because a call xxx is not mapped or my 
manager is not in there.
i have solved this sometime ago. I have written in relfector also and i 
asked everyone to do the same. Sent your country files to Jim AD1C. He will 
have them included in next release and you have not worried abt your dxcc 
totals. I write every mngr i want to add in a piece of paper and send them 
to Jim also. Why you don't do the same?
I hadn't ever a problem with the log.
Kostas sv1dpi
PS1: I agree there is a need for a utility or something like that to help 
anyone with a problem with his counties, even i hadn't any problem (probably 
lucky or good computer practice). And of course was a problem this damned 
bug for eveyone because this way is not served the reason 1 but this is the 
way every bug works... But at least we must make everything we can to keep 
our log ok and the way i described is the right one.





----- Original Message ----- 
From: "Mike Mellinger WA0SXV" <wa0sxv at mellinger.com>
To: <dx4win at mailman.qth.net>
Sent: Monday, January 07, 2008 5:25 AM
Subject: RE: [Dx4win] Unhappy with DX4WIN


> Yes, the file is corrupt.  DUH.
>
> If you have country mappings that aren't in the official country file, 
> they
> get screwed up every time you update the country file.
>
> The hard drive is not only perfect -- it is shadowed -- instantaneous 
> copy.
> It is also scanned daily and backed up daily.  I can tell you precisely 
> when
> the data went to pieces -- it was when I added FJ per the instructions on
> here.  Unfortunately the instructions were written before the bug was
> discovered.
>
> And my hard drive has nothing to do with the design that does not keep the
> log file intact in and of itself.  Any time the integrity of the log 
> depends
> on the integrity of multiple other files you are set up for problems.
>
> As for the lost states -- look in the archives.  There is a bug in the new
> country entry that messes it up.
>
> 73
> Mike WA0SXV
>
> -----Original Message-----
> From: dx4win-bounces at mailman.qth.net 
> [mailto:dx4win-bounces at mailman.qth.net]
> On Behalf Of Robert Naumann
> Sent: Sunday, January 06, 2008 17:25
> To: dx4win at mailman.qth.net
> Subject: RE: [Dx4win] Unhappy with DX4WIN
>
> Mike,
>
> It sounds like you may have a file corruption problem.
>
> I have never seen any of the errors you are reporting in well over 10 
> years
> of using DX4win - since version 1.12. When you add a new country, no DXCC
> counts ever change - unless you have qsos with that country after the 
> start
> date of the country. For example, when I added FJ, no qso I had ever made
> counted for that country, so nothing changed. I suppose that it is also
> possible that you may not have added FJ in properly which could cause
> problems.
>
> Check your hard drive for problems. It's not DX4win.
>
> 73,
>
> Bob W5OV
>
>
> _______________________________________________
> Dx4win mailing list
> Dx4win at mailman.qth.net
> http://mailman.qth.net/mailman/listinfo/dx4win
>
> 




More information about the Dx4win mailing list