Hello again,
I've found what I think is a bug.
I'am using the WMP skin layout. The Reports menu opens up automatically
when you hover your mouse over it when one of the other menus on the top
row are open, like Filters LoTW or another one.
Please take care of this so it only opens up when you
I am unable to get the software connected with my ICOM 7300, regardless of baud
rate or com port. All my other software works fine. When I try to directly
enter a frequency for the radio in DX4WIN, I can see the secondary VFO is
reading fine but the primary frequency readout is 2237,434.70.
Zoran,
We make an attempt to filter 'old' prefixes that can no longer be used.
This list is visible and not hidden from view and can be edited as a plain
ASCII file. You will find the file dx4win.wpx in the save sub-directory.
--Paul, KK4HD
On Sun, Mar 29, 2015 at 10:10 PM, WA7AA
On Mon, Mar 30, 2015 at 11:35 AM, Paul van der Eijk
pvandere...@gmail.com wrote:
We make an attempt to filter 'old' prefixes that can no longer be used.
This list is visible and not hidden from view and can be edited as a plain
ASCII file. You will find the file dx4win.wpx in the save
On 30-Mar-15 12:57 PM, Jim Reisert AD1C wrote:
On Mon, Mar 30, 2015 at 11:35 AM, Paul van der Eijk
pvandere...@gmail.com wrote:
We make an attempt to filter 'old' prefixes that can no longer be used.
This list is visible and not hidden from view and can be edited as a plain
ASCII file. You
On Mon, Mar 30, 2015 at 9:24 PM, WA7AA wa...@comcast.net wrote:
Since keeping track of expired prefixes for WPX sounds almost like a full
time job, I'd say don't even bother, Jim. I'll just wipe out all the entries
in dx4win.wpx and count them all.
My recollection is the list changes only
Hi, Paul et al.
A minor bug report:
Some prefixes worked in my log show status in the WPX window as
deleted and have a blank entry in that window. An example of such
prefixes is AJ7 and AC0. No matter how many QSOs with such callsigns one
has, the WPX window is blank and they don't count
Hello!
If stations from Russia has added their oblast in LOTW, those from
Moscow (MA) or Moscow region (MO) will in DX4WIN sometimes be added as
MA zone 5 or MO zone 4, respectively. Thus it seems like if there is
an abrevation that is the same as an US state it will be entered in
the state field
That's correctly formatted ADIF - the Russian Oblast code is put into the
STATE field, which is overloaded for entities like Canada (province
codes), Russia (Oblasts), Mexico (States), Argentina, Brazil, etc.
STATE:n is used for all of those. See
I'm running DX4WIN V8.05 with Yaesu FT-5000.
Works as expected, except for an anomaly I just noticed.
DX4WIN tracks all the radio's modes (CW, SSB, etc) correctly EXCEPT when
operating PKT mode.
If the radio is placed in PKT LSB, DX4WIN enters PSK-31 as the mode. I can
accept that, as
If you havent yet recieved a confirmation by this time dx4win ignores the
worked or mailed status
Sent from my Samsung Galaxy Tab 10.1ON4AOI on4...@skynet.be wrote:Hi Dan
What are the worked and mailed cutoff values in the preferences ?
Guy ON4AOI
Van: ON5UE [mailto:on...@skynet.be]
Hi Danny,
When showing the DXCC status Window, the intersection of band and mode
shows the
highest level for the combination of band and mode for that country.
The status goes
like: blank (not worked) W = Worked, L = Label , M = mailed and C =
Confirmed
When you double-click on a C, you filter
Message -
From: Paul van der Eijk pvandere...@cox.net
To: dx4win@mailman.qth.net
Cc: on...@skynet.be
Sent: Monday, August 13, 2012 7:54 AM
Subject: Re: [Dx4win] Bug in dxcc window filters.
Hi Danny,
When showing the DXCC status Window, the intersection of band and mode
shows the
highest
- From: Paul van der Eijk
pvandere...@cox.net
To: dx4win@mailman.qth.net
Cc: on...@skynet.be
Sent: Monday, August 13, 2012 7:54 AM
Subject: Re: [Dx4win] Bug in dxcc window filters.
Hi Danny,
When showing the DXCC status Window, the intersection of band and mode
shows the
highest level
Hi Dan
What are the worked and mailed cutoff values in the preferences ?
Guy ON4AOI
Van: ON5UE [mailto:on...@skynet.be]
Verzonden: zaterdag 11 augustus 2012 10:09
Aan: supp...@dx4win.com
CC: on4...@skynet.be
Onderwerp: Bug in dxcc window filters.
Hello;
I found a bug in
Is there somewhere an up to date list of identified bugs in the current
version of DX4WIN that are going to be remedied in the next version release?
73 John ZL1BYZ
__
Dx4win mailing list
Home:
Hello
I use the dx4win version 8.01
And now the reports DXCC summary don't work well
It's ok if the bands is all bands and the modes is all bands.
But If you change bands for example to 14MHz the result not change !
It's the same if you change mode for example to CW
Best 73
F5NBU -
On 8/28/2009 3:34 AM, Yann wrote:
I use the dx4win version 8.01
And now the reports DXCC summary don't work well
It's ok if the bands is all bands and the modes is all bands.
But If you change bands for example to 14MHz the result not change !
It's the same if you change mode for example to
Importing from a ver 8 DXQ file truncates the mode to 5 characters.
This precludes cleaning up data in an editor, sometimes necessary with
the conversion... so it is a semi-serious bug but should be easy to fix.
Work-around... not tried yet: re-export to ADIF and fix broken modes
with an
Is it possible to do all your cleanup in DXWIN 7.0x, then open the final
log in 8.01?
- Jim
On 8/6/2009 8:17 AM, Mel wrote:
Importing from a ver 8 DXQ file truncates the mode to 5 characters.
This precludes cleaning up data in an editor, sometimes necessary with
the conversion... so it is
Hi Paul...
I had mentioned this in the discussion we had on spot levels.
I realize it is by design... but my reasoning is as follows...
At present, if the spot is outside the filter zone it's grey. Correct.
If a spot arrives from inside the filter, indicating it is being heard
in the area of
Mel,
Now if another spot arrives withing a couple of minutes from outside the
geographic area it turns grey again... indicating it isn't being heard
in the area of interest? Wrong. It's probably still being heard.
Correct but if it would colored then it would be a BUG
A filter is a filter, no
Mel, try sorting spots by Arrival instead of by Time. Then both the
colored and gray spots will be in the Spots window.
73 - Jim AD1C
On Sun, Mar 15, 2009 at 4:03 AM, Mel Martin ve...@videotron.ca wrote:
Hi Paul...
I had mentioned this in the discussion we had on spot levels.
I realize it
You seem to miss the point completely Guy... perhaps you are confused by
the word bug in the subject which started the discussion...
We are not discussing a bug at this point, but whether it is desirable
for a grey spot to overwrite a colored spot. The issue doesn't arise
when the grey spots
That's true... but I actually prefer the way it works when sorting by
time... except for the alert color being overwritten. Most of the time
I have the grey spots filtered out so its usually not an issue... it's
only a minor inconvenience anyway.
Jim Reisert AD1C wrote:
Mel, try sorting
Today TO2T was coming up as a GREY spot on dxspots on 28 mhz even though I
have not worked them on 28mhz.
I did a F8 for TO2T and it comes up only on 14 mhz.Why?
Any other condition would cause this?
73 N8DX
__
Dx4win mailing list
If your country file didn't have an exception record for them, (you can
tell by entering TO2T in the qso window and looking to see if it pulls
up an entity), I'm guessing that DX4WIN simply thinks it's nothing
special so it comes up greyed out.
On 3/14/2009 5:03 PM, Jack Shirley wrote:
Today
Grey means either:
1. You have worked them
2. You have the band or mode disabled
3. The spot is from outside the geographic area you are filtering on.
I suspect #3
BTW, one unwanted feature I have noticed. If you have a colored spot and
grey spots are enabled... if a spot from outside your
Mel,
Your point #3 is by design; see the description in the on-line help. I'm
not sure why you say it is an unwanted feature.
--Paul, KK4HD
Mel Martin wrote:
Grey means either:
1. You have worked them
2. You have the band or mode disabled
3. The spot is from outside the geographic area
Is it me or is it a bug?
I have VE and K placed in the spotters box in packet 1 under preferences.
This is supposed to limit packet spots to those originated in VE and K land.
I am however, getting spots from all countries. I do not have Paul's e-mail
address so could somebody relay this (if
Not a bug. Operator error. I was looking at wrong window.
de Vic, N5YY
- Original Message -
From: Victor West [EMAIL PROTECTED]
To: Dx4win@mailman.qth.net
Sent: Tuesday, May 20, 2008 12:50 PM
Subject: [Dx4win] BUG IN 4.04?
Is it me or is it a bug?
I have VE and K placed
When saving the log and exiting the program got the following exception
error:
Errror at 004D8FA8, read of address 0278
Error continued multiple time until I killed the process.
Jeff N7YG
Paul KK4HD found the problem and fixed it. This is apparently a really old bug
that no one ever caught before!
73 - Jim AD1C
--- Jim Reisert AD1C [EMAIL PROTECTED] wrote:
Hi Paul/Steve,
DX4WIN on both of my computers froze today at the same time. I had to kill
the program from the task
Just tried in v 6.03 and there it is ok .States flag is resetted when
logging a new US station (never wkd)
not ok in 6.04
marc on4ma
- Original Message -
From: Marc Wullaert [EMAIL PROTECTED]
To: DX4WIN List dx4win@mailman.qth.net
Sent: Saturday, February 05, 2005 7:34 AM
Subject: [Dx4win
Happy New Year!
I reported a bug in (v6.03) the Logbook view this weekend. It
seems that my use of Uploazd Confirm as a field in
my Logbook view gets set to and populated with the
Upload Date when I start DX4WIN. If I go into the
Report Editor and simply click OK, it gets set properly
to the
As in 0100 UTC on the 30th
Mike / W8DN
- Original Message -
From: ARS NZ3O (Byron) FM29fx [EMAIL PROTECTED]
To: dx4win@mailman.qth.net
Sent: Saturday, May 29, 2004 8:49 PM
Subject: [Dx4win] BUG? Date/Timestamp on QSLs
At 9:00 PM EDT on 05/29/2004 I printed 100 QSLs.
When I
--- ARS NZ3O (Byron) FM29fx [EMAIL PROTECTED] wrote:
At 9:00 PM EDT on 05/29/2004 I printed 100 QSLs.
When I approved the printouts, cleared the print flags
and set the QSL date, all QSLs were dated 05/30/2004.
I saw this the first time I printed under 603 but thought
I'd imagined it. Not
Could it have anything to do with the difference between Zulu (GMT,
etc.) time and your local time? Is your DX4WIN set to Zulu time?
2100 your local time (9:00 p.m.) would be the next day in Zulu time if
you are in the USA.
ARS NZ3O (Byron) FM29fx wrote:
At 9:00 PM EDT on 05/29/2004 I
I guess it COULD, but I'm not aware of any setting for that
in DX4WIN. Is that new?
At 10:40 PM 5/30/2004, Alan C. Zack wrote:
Could it have anything to do with the difference between Zulu (GMT,
etc.) time and your local time? Is your DX4WIN set to Zulu time?
2100 your local time (9:00 p.m.)
Well, not a real problem, as long as you know it's wrong,
since I mail things locally, not in someplace UTC.
At 04:58 PM 5/30/2004, [EMAIL PROTECTED] wrote:
At 9:00 PM EDT on 05/29/2004 I printed 100 QSLs.
When I approved the printouts, cleared the print flags
and set the QSL date, all QSLs
My workaround is to use Adobe Acrobat as my printer,
and then print it on my printer from Adobe,
which probably isn't an option for most folks. But Adobe
forces a wider margin, so some of the right end of the
report can be lost.
At 04:58 PM 5/30/2004, AD1C wrote:
Am I missing something? Under
Michaels, MD
- Original Message -
From: ARS NZ3O (Byron) FM29fx [EMAIL PROTECTED]
To: dx4win@mailman.qth.net
Sent: Sunday, May 30, 2004 9:46 PM
Subject: [Dx4win] BUG? Report Output Overrides Landscape?
My workaround is to use Adobe Acrobat as my printer,
and then print it on my printer from
Fallen off the meds tonight, Malcolm?
At 09:53 PM 5/30/2004, Malcolm Ringel wrote:
Good grief guys .I mean sheesh !
Get a grip somewhere/somehow.
Good luck to all and may your seemingly endless problems resolve in some
comprehensible manner so that you can get back to ham radio, should
At 9:00 PM EDT on 05/29/2004 I printed 100 QSLs.
When I approved the printouts, cleared the print flags
and set the QSL date, all QSLs were dated 05/30/2004.
I saw this the first time I printed under 603 but thought
I'd imagined it. Not this time, though.
73, Byron
: Jim Reisert AD1C [EMAIL PROTECTED]
To: DX4WIN dx4win@mailman.qth.net
Sent: Thursday, May 27, 2004 6:32 PM
Subject: [Dx4win] Bug setting QSL method on multiple QSOs
In my log, I selected only QSOs with the QSL Method = Ignore. There were
about
7000+ such QSOs.
Then using Multiple QSO
You need to do a manual edit:
BAND:41.2m should change to BAND:51.25m
The number after the colon is the field with. [1.2m] is 4
letters. [1.25m] is 5 letters.
You'll have to edit the ADIF file after exporting it. Paul will need to
fix this in DX4WIN.
73 - Jim AD1C
At 07:32 AM 5/26/2004,
Hello all
Firstb i want to tell i am very happy with the new update.
Its now also a complete program for the vhf dxer, with the new rst
possibilities.
601 is a mayer update for all vhf dxers. Thanks to Paul and his crew!
I thimk this will open the european vhf market for the program!
One
47 matches
Mail list logo
