[Dx4win] filter problem V 5.03
To elaborate on my earlier post, if I have multiple qsos with thge same station, and try to read from one bamd qso to another, double clicking gets me a pop up screen that THE QSO DOES NOT MATCH THE CURRENT FILTER. I have gone into the filter options screen and tried to change the filter there to DX4WIN V4 OR HIGHER without any success. It will not allow me to make other changes, and to be honest, I am not sure that it has accepted tha one either. Is there any other place that will allow a filter to be changed or any idea of how to clear this problem? I need to be be able to page through the QSOs from time to time to log in cards etc, and this can be a real pain in the lobotomus.. Also, I usually save the SAVE file in another location. If I save the log files, does that mean I saved the problem with it? Would deleting the file after saving my last few QSOS and then reloading using my old SAVE file solve the problem or merely move it around some? Does anyone have any ideas? TIA Tom N4TJ
[Dx4win] Duplicate Spots
At 09:42 PM 9/2/2003, ARS NZ3O (Byron) FM29fx wrote: >When I spot a station, my spot appears (without the >sending station callsign) immediately and doesn't >disappear when the packetcluster spot arrives. So >each one of my spots appears twice if I don't work >the station and log it. I don't think I ever changed any >config items related to this. Hi Byron, If you sort by arrival, this will happen. If you sort by time, it won't, DX4WIN will only keep the latest spot. 73 - Jim AD1C -- Jim Reisert AD1C, 7 Charlemont Court, North Chelmsford, MA 01863 USA +978-251-9933, <[EMAIL PROTECTED]>, http://www.ad1c.com PGP Fingerprint: D8E2 3D78 339F A7F1 8C13 1193 B5D1 4FB6 79D1 70DC
[Dx4win] Re:filter problem V 5.03
Hi Tom I'm also running v5.03 here. I've often wished that any Q listed in the "Same Call" window could be selected. The way it works now is that you can only select Q's from there if they satisfy the current filter you have set. For example, I can set a filter for 3V8BB on 20m. Alll my Q's with him on 20m show up in the "Log Report" window. Every Q I have with 3V8BB (whether 20m or not) shows up in the "Same Call" window. If I try to select a 10m Q from there, I get the "QSO DOES NOT MATCH THE CURRENT FILTER" message. Right now, the solution is to set the filter to JUST the call. Then all are selectable. Also, what is this "filter options screen" you say you're trying to modify? I sure don't see it in my program. 73, Ron - N9QQK
[Dx4win] dx4win.ini
Using 6.02: While helping a friend who had screwed up his .ini file I noticed that I don't have one in the save directory of 6.02. I do have one in 6.01 which I have never deleted from my computer. Is it possible that my 6.02 is using the .ini file of 6.01? The are both in the Program Files folder. Program is working great just really surprised me to find I had no .ini file. Rod WC7N [EMAIL PROTECTED]
[Dx4win] dx4win.ini
you can easely write a new one.go to Preferences and File/write ini file . you can change the path where the file have to be written ! 73 marc on4ma - Original Message - From: "WC7N" <[EMAIL PROTECTED]> To: "DX4WIN Group" Sent: Wednesday, September 03, 2003 7:15 PM Subject: [Dx4win] dx4win.ini > Using 6.02: > > While helping a friend who had screwed up his .ini file I noticed that I > don't have one in the save directory of 6.02. I do have one in 6.01 which I > have never deleted from my computer. > > Is it possible that my 6.02 is using the .ini file of 6.01? The are both in > the Program Files folder. > > Program is working great just really surprised me to find I had no .ini > file. > > Rod WC7N > [EMAIL PROTECTED] > > ___ > Dx4win mailing list > Dx4win@mailman.qth.net > http://mailman.qth.net/mailman/listinfo/dx4win > >
[Dx4win] DX spot colors revisited
As others have said, I might want to swap 2 and 3, 4 and 5. So, it must be a preference setting. Also, I might not want to see even black spots, much less gray, so would want to hide them as I do the gray ones. John, K2CIB - Original Message - From: "Jim Reisert AD1C" <[EMAIL PROTECTED]> To: Sent: Tuesday, September 02, 2003 4:23 PM Subject: Re: [Dx4win] DX spot colors revisited > I think I boiled the priorities down to three simple rules: > > 1. All-time never worked has the highest priority. > > 2. When both entities are unworked or both entities are > worked but not confirmed, mode has priority over band. > > 3. When one entity is unworked and the other is worked > but not confirmed, the unworked entity has priority > over the worked entity. > > The priorities I suggested earlier seem to embody these requirements: > >1 = never worked >2 = never worked mode >3 = never worked band >4 = unconfirmed mode >5 = unconfirmed band > > Does this make sense to everyone? > > 73 - Jim AD1C > > -- > Jim Reisert AD1C, 7 Charlemont Court, North Chelmsford, MA 01863 > USA +978-251-9933, <[EMAIL PROTECTED]>, http://www.ad1c.com > PGP Fingerprint: D8E2 3D78 339F A7F1 8C13 1193 B5D1 4FB6 79D1 70DC > > ___ > Dx4win mailing list > Dx4win@mailman.qth.net > http://mailman.qth.net/mailman/listinfo/dx4win >
[Dx4win] dx4win.ini
DX4WIN doesn't directly use the .INI file. It's used to export/import configuration across different releases. DX4WIN uses the DX4WIN.CFG file which contains data imported from a DX4WIN.INI file. 73 - Jim AD1C = Jim Reisert AD1C, 7 Charlemont Court, North Chelmsford, MA 01863 USA +978-251-9933, <[EMAIL PROTECTED]>, http://www.ad1c.com PGP Fingerprint: D8E2 3D78 339F A7F1 8C13 1193 B5D1 4FB6 79D1 70DC
[Dx4win] DX spot colors revisited
I doubt that Paul will ever make these colors user programmable for the priorities. I think the order you laid out for 1) never worked 2) never worked mode 3) never worked band will satisfy 90% of the DX community. The unconfirmed mode and band are neat touches, also. Paul spent a period of several months getting the never worked band as a reality, and that has helped me more than any other improvement in DX4WIN as getting bands worked for anyone chasing MIXED, PHONE, and CW (or RTTY) takes a lot of work without this improvement working properly. After a while there are not many never worked left. The logic used by DX4WIN is pretty straightforward and as best I can sort it out, depends on the priority order for the searches to be very quick (and it is). Yes, I agree with your order. I confirm DX to the ARRL requirements and do not care for having to work every band in all modes as that requires working Dxepeditions too many times, but there are those that want to work every band on both CW and Phone and RTTY. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Jim Reisert AD1C Sent: Tuesday, September 02, 2003 3:23 PM To: dx4win@mailman.qth.net Subject: Re: [Dx4win] DX spot colors revisited I think I boiled the priorities down to three simple rules: 1. All-time never worked has the highest priority. 2. When both entities are unworked or both entities are worked but not confirmed, mode has priority over band. 3. When one entity is unworked and the other is worked but not confirmed, the unworked entity has priority over the worked entity. The priorities I suggested earlier seem to embody these requirements: 1 = never worked 2 = never worked mode 3 = never worked band 4 = unconfirmed mode 5 = unconfirmed band Does this make sense to everyone? 73 - Jim AD1C -- Jim Reisert AD1C, 7 Charlemont Court, North Chelmsford, MA 01863 USA +978-251-9933, <[EMAIL PROTECTED]>, http://www.ad1c.com PGP Fingerprint: D8E2 3D78 339F A7F1 8C13 1193 B5D1 4FB6 79D1 70DC ___ Dx4win mailing list Dx4win@mailman.qth.net http://mailman.qth.net/mailman/listinfo/dx4win
[Dx4win] DX spot colors revisited
Thanks for the feedback. My prior analysis is included at the end for those who can't remember. I think it was Mel VE2DC who pointed out that there is an option to highlight unconfirmed new entities as if they are unworked, so #1 changes a little. Would it be nice to be fully configurable? Sure! Is it likely to happen? Probably not. The most requested switch seems to be to choose whether band spots have priority over mode spots, or vice versa (default right now is mode over band). So I hope Paul can fix the priority 3/4 problem (unworked band entity should have priority over worked mode entity), as well as add this new switch. This should satisfy 95% of the users. If you don't care about band or mode awards, go into your DXCC prefernces and turn these awards off. 73 - Jim AD1C I think I boiled the priorities down to three simple rules: 1. All-time never worked has the highest priority. 2. When both entities are unworked or both entities are worked but not confirmed, mode has priority over band. 3. When one entity is unworked and the other is worked but not confirmed, the unworked entity has priority over the worked entity. The priorities I suggested earlier seem to embody these requirements: 1 = never worked 2 = never worked mode 3 = never worked band 4 = unconfirmed mode 5 = unconfirmed band = Jim Reisert AD1C, 7 Charlemont Court, North Chelmsford, MA 01863 USA +978-251-9933, <[EMAIL PROTECTED]>, http://www.ad1c.com PGP Fingerprint: D8E2 3D78 339F A7F1 8C13 1193 B5D1 4FB6 79D1 70DC
[Dx4win] DX spot colors revisited
The message seems to be that one size doesn't fit all. I know that I have seen similar things to those reported here. Possibly it is because I didn't understand the details of how it actually works, but I found stations I wanted to work way low down in the priorities (i.e. my priorities did not match those which 6.02 has build in). 73 Stan, N3HS -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jim Reisert AD1C Sent: Wednesday, September 03, 2003 4:43 PM To: dx4win@mailman.qth.net Subject: RE: [Dx4win] DX spot colors revisited Thanks for the feedback. My prior analysis is included at the end for those who can't remember. I think it was Mel VE2DC who pointed out that there is an option to highlight unconfirmed new entities as if they are unworked, so #1 changes a little. Would it be nice to be fully configurable? Sure! Is it likely to happen? Probably not. The most requested switch seems to be to choose whether band spots have priority over mode spots, or vice versa (default right now is mode over band). So I hope Paul can fix the priority 3/4 problem (unworked band entity should have priority over worked mode entity), as well as add this new switch. This should satisfy 95% of the users. If you don't care about band or mode awards, go into your DXCC prefernces and turn these awards off. 73 - Jim AD1C I think I boiled the priorities down to three simple rules: 1. All-time never worked has the highest priority. 2. When both entities are unworked or both entities are worked but not confirmed, mode has priority over band. 3. When one entity is unworked and the other is worked but not confirmed, the unworked entity has priority over the worked entity. The priorities I suggested earlier seem to embody these requirements: 1 =3D never worked 2 =3D never worked mode 3 =3D never worked band 4 =3D unconfirmed mode 5 =3D unconfirmed band =3D=3D=3D=3D=3D Jim Reisert AD1C, 7 Charlemont Court, North Chelmsford, MA 01863 USA +978-251-9933, <[EMAIL PROTECTED]>, http://www.ad1c.com PGP Fingerprint: D8E2 3D78 339F A7F1 8C13 1193 B5D1 4FB6 79D1 70DC ___ Dx4win mailing list Dx4win@mailman.qth.net http://mailman.qth.net/mailman/listinfo/dx4win
[Dx4win] Priorities.
I'm good with this. At 04:02 AM 9/3/2003 -0400, you wrote: >The priorities I suggested earlier seem to embody these requirements: > >1 = never worked >2 = never worked mode >3 = never worked band >4 = unconfirmed mode >5 = unconfirmed band > >Does this make sense to everyone?
[Dx4win] Bad QRG & flip flopping Band window with IC-756 Pro II
When using a 756 Pro II the information in the Band window jumps between = SAT and the Band the radio is on. Also the frequency read when I key = control R sometimes is correct and sometimes it is in error. Occurs on = all bands. For example it read 2,129,440 KHz when the true frequency was = 21,294.40 KHz. I have the 756 Pro selected as the radio. Does this = require a Pro II radio file? Or am I missing something? It worked great = with my IC-761 and IC-910H. I am using version 5.03 but the same occurs = in version 6. Help --- StripMime Report -- processed MIME parts --- multipart/alternative text/plain (text body -- kept) text/html The reason this message is shown is because the post was in HTML or had an attachment. Attachments are not allowed. To learn how to post in Plain-Text go to: http://www.expita.com/nomime.html ---
[Dx4win] Bad QRG & flip flopping Band window with IC-756 Pro II
Go into your transceiver settings and set CT-17 TRANSCEIVE to OFF. 73 - Jim AD1C At 05:53 PM 9/3/2003, Edgar Brown, N6OU wrote: >When using a 756 Pro II the information in the Band window jumps between >SAT and the Band the radio is on. Also the frequency read when I key >control R sometimes is correct and sometimes it is in error. Occurs on all >bands. For example it read 2,129,440 KHz when the true frequency was >21,294.40 KHz. I have the 756 Pro selected as the radio. Does this >require a Pro II radio file? Or am I missing something? It worked great >with my IC-761 and IC-910H. I am using version 5.03 but the same occurs in >version 6. Help -- Jim Reisert AD1C, 7 Charlemont Court, North Chelmsford, MA 01863 USA +978-251-9933, <[EMAIL PROTECTED]>, http://www.ad1c.com PGP Fingerprint: D8E2 3D78 339F A7F1 8C13 1193 B5D1 4FB6 79D1 70DC
[Dx4win] filter problem V 5.03
Tom, After you see the message that 'The QSO does not match the current filter' , click the OK button followed by an Escape. This cancels the current filter and lets you select any QSO shown. If a 'Selection' is active, this does not work, because only QSOs that are in the current selection will be shown. When DX4WIN starts, the selection is 'ALL QSOs', so I don't think that is the problem. Paul At 03:16 AM 9/3/03 +, Tom Johnson wrote: >To elaborate on my earlier post, if I have multiple qsos with thge same >station, and try to read from one bamd qso to another, double clicking gets >me a pop up screen that THE QSO DOES NOT MATCH THE CURRENT FILTER. I have >gone into the filter options screen and tried to change the filter there to >DX4WIN V4 OR HIGHER without any success. It will not allow me to make other >changes, and to be honest, I am not sure that it has accepted tha one >either. Is there any other place that will allow a filter to be changed or >any idea of how to clear this problem? I need to be be able to page through >the QSOs from time to time to log in cards etc, and this can be a real pain >in the lobotomus.. > >Also, I usually save the SAVE file in another location. If I save the log >files, does that mean I saved the problem with it? Would deleting the file >after saving my last few QSOS and then reloading using my old SAVE file >solve the problem or merely move it around some? > >Does anyone have any ideas? TIA > >Tom > >N4TJ > > >___ >Dx4win mailing list >Dx4win@mailman.qth.net >http://mailman.qth.net/mailman/listinfo/dx4win Paul van der Eijk (KK4HD) [EMAIL PROTECTED] http://www.dx4win.com
[Dx4win] DX spot colors revisited
Jim, The next release has an extra priority added, so I can deal with the band / mode combinations too. The rest is as you suggested, with priority given to the 'mode'. This stuff gets complicated! Paul At 01:43 PM 9/3/03 -0700, Jim Reisert AD1C wrote: >Thanks for the feedback. My prior analysis is included at the end for those >who can't remember. I think it was Mel VE2DC who pointed out that there is an >option to highlight unconfirmed new entities as if they are unworked, so #1 >changes a little. > >Would it be nice to be fully configurable? Sure! Is it likely to happen? >Probably not. The most requested switch seems to be to choose whether band >spots have priority over mode spots, or vice versa (default right now is mode >over band). > >So I hope Paul can fix the priority 3/4 problem (unworked band entity should >have priority over worked mode entity), as well as add this new switch. This >should satisfy 95% of the users. If you don't care about band or mode awards, >go into your DXCC prefernces and turn these awards off. > >73 - Jim AD1C > >I think I boiled the priorities down to three simple rules: > >1. All-time never worked has the highest priority. > >2. When both entities are unworked or both entities are > worked but not confirmed, mode has priority over band. > >3. When one entity is unworked and the other is worked > but not confirmed, the unworked entity has priority > over the worked entity. > >The priorities I suggested earlier seem to embody these requirements: > > 1 = never worked > 2 = never worked mode > 3 = never worked band > 4 = unconfirmed mode > 5 = unconfirmed band > > >= >Jim Reisert AD1C, 7 Charlemont Court, North Chelmsford, MA 01863 >USA +978-251-9933, <[EMAIL PROTECTED]>, http://www.ad1c.com >PGP Fingerprint: D8E2 3D78 339F A7F1 8C13 1193 B5D1 4FB6 79D1 70DC >___ >Dx4win mailing list >Dx4win@mailman.qth.net >http://mailman.qth.net/mailman/listinfo/dx4win Paul van der Eijk (KK4HD) [EMAIL PROTECTED] http://www.dx4win.com
