[Dx4win] Clusters
At 10:51 PM 2/8/2003 -0600, Guillermo Vazquez C XE1ZW wrote: When I work with clusters I choose Internet Conexion, there are a long list of options in order to take one of them Who can I erase them in order to have only 5 that I use Edit the DX4WIN.TCP file in the SAVE directory using a plain text editor. 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:: Greeting Message on Labels - sorted now
OK, I forgot ot check the 'Print group names' box. Doh! - Original Message -=20 From: G4IRN=20 To: [EMAIL PROTECTED] Sent: Sunday, February 09, 2003 9:20 AM Subject: Greeting Message on Labels Hi I have upgraded to version 6.02. In File | Preferences | Rep/Lab I have '@@, 73 de %%' entered as the QSL = label greeting. The @@ prints as Pse or Tns QSL, as it should, on the label. The %% prints lierally and doesn't pick up the group name assigned to = that QSO. Am I doing something wrong? Thanks John G4IRN --- 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] Packet Window
If I remember correctly, in the 5.x version if I made the send part (bottom) of the Packet Window smaller it stayed that way when I exited and restarted DX4Win. But, in the 6.x version, I have to resize it every time. Anyone else seeing this? 73 - Ted - W8TTS
[Dx4win] PSK31 and SSTV scores - how?
Dear DX4WIN users, I would like to know, how get my PSK31 and my SSTV score. (The DXCC style). I'm still missing this in the Report column. The way thru Report Editor or via Custom Report seems be very impractical. Using DX4WIN 6.02. 73 Milan, OK1FM Milan GÜTTER http://www.ok1fm.com E-mail: [EMAIL PROTECTED]
[Dx4win] Packet Window
At 07:07 AM 2/9/2003 -0500, Ted Sarah - W8TTS wrote: If I remember correctly, in the 5.x version if I made the send part (bottom) of the Packet Window smaller it stayed that way when I exited and restarted DX4Win. But, in the 6.x version, I have to resize it every time. Anyone else seeing this? Paul knows that it's broken, but has not been able to come up with a fix. 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] Packet Window
Yes, that is the way it used to work. In fact, the size of the send window is also lost if you click on Maximize and then Restore. I liked it the old way, and wonder if there is some new functionality that is tied to this behavior. If not, perhaps it can be either restored to the previous behavior, which I prefer over the current way. 73 - Dave N3RD On 9 Feb 2003 at 7:07, Ted Sarah - W8TTS wrote: If I remember correctly, in the 5.x version if I made the send part (bottom) of the Packet Window smaller it stayed that way when I exited and restarted DX4Win. But, in the 6.x version, I have to resize it every time. Anyone else seeing this? 73 - Ted - W8TTS ___ Dx4win mailing list Dx4win@mailman.qth.net http://mailman.qth.net/mailman/listinfo/dx4win
[Dx4win] 6.02 failure - Exception on startup
OK, now I have not only reinstalled 6.02 over the first install, but then uninstalled it, ran Norton to clean up the registry, rebooted run Norton again, rebooted and reinstalled what should have been a clean install. Moved the N3HS.KEY File over, merged the INI file, etc. and it all seemed right in that I couldn't change my name or callsign in preferences, BUT it still is in demo mode and will not allow me to save my log. As of right now 6.02 is COMPLETELY UNUSABLE. 73 Stan, N3HS -Original Message- From: Stan Staten [mailto:[EMAIL PROTECTED] Sent: Saturday, February 08, 2003 7:33 PM To: 'dx4win@mailman.qth.net' Subject: RE: [Dx4win] Problem in 6.02 - Exception on startup Well, I thought that I had everything working right. The N3HS.KEY file is in the right place and the usual things like radio, packet, etc seem to work. Merging the 5.03 *.INI file went smooth although not everything came over right - CW and rotator for example had to be reset. I cannot save the log as it still thinks it is in the DEMO mode and the exception happens each time I start DX4WIN. Had to re-do the rotator a couple of times and the CW keying when that didn't come over with the INI file. Now both rotator and CW seem to work and the radio and packet worked right off. I have not tried setting the packet spots to see if the country worked but not confirmed is there as I had hoped since I wanted to make sure that the basics were working OK. I just re-installed 6.02 to see if that fixed it and it didn't. The reinstall noted as it went along that the N3HS.KEY file was there and I had hoped that all was well. I have been suspicious of it being my fault as I re-arranged the shack over the holidays and although everything seemed to work, when I have had 6.02 problems like with the rotator, I went to Writelog to confirm that my interface was set up and working. I am using XP Pro and have been so for some number of months and that didn't seem to be a problem with 5.03. 73 Stan, N3HS -Original Message- From: Mel Martin (VE2DC) [mailto:[EMAIL PROTECTED] Sent: Saturday, February 08, 2003 4:56 PM To: [EMAIL PROTECTED] Subject: RE: [Dx4win] Problem in 6.02 I've been watching pretty carefully Stan... And I haven' seen anything similar to what you are describing. Do you get the error every time you start? I would verify setting for LTP and COM ports as there have been a number of changes in this area. You might try disabling some stuff to see if the exception is coupled to a particular feature... -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Stan Staten Sent: February 8, 2003 4:18 PM To: DX4WIN Subject: [Dx4win] Problem in 6.02 I've been gone for the last few weeks and just got back and around to updating 5.03 to 6.02. When I start DXWIN I get an exception error in the form of an access violation at 00515d07. Also so far, rotor control doesn't work. (I checked it in 5.03 just to make sure that I hadn't messed things up in the upgrade. Since I have been gone I have missed the chatter on the issues when 6.01 and am looking for suggestions. I did search the archive for error or exception and found nothing so I guess I don't mind bothering the assembled group. Thanks Stan, N3HS ___ Dx4win mailing list Dx4win@mailman.qth.net http://mailman.qth.net/mailman/listinfo/dx4win
[Dx4win] Vers. 6.02
Hi Paul, Can You modify the V.603 to fix these problems? - 1st - Just installed V.602 and migrated .INI file from my V.503. On it there are a couple of labeled items about the custom 1 and 2 label definitions, as you can see: [CustLab1] LabelID=Custom1 Metric=1 SpacingTop=0.039 SpacingLeft=0.039 SpacingHeight=1.169 SpacingWidth=2.756 LabelHeight=1.091 LabelWidth=2.717 RightShift=0.000 DownShift=0.000 PageWidth=8.268 PageHeight=12.028 NumAcross=3 NumDown=10 PaperName=Custom Portrait=1 [CustLab2] LabelID=Custom2 Metric=1 SpacingTop=0.787 SpacingLeft=0.315 SpacingHeight=3.189 SpacingWidth=3.327 LabelHeight=3.110 LabelWidth=3.307 RightShift=0.000 DownShift=0.000 PageWidth=4.134 PageHeight=5.315 NumAcross=1 NumDown=1 PaperName=Custom Portrait=1 After merging the .ini file, all the custom label fields are setting to zero, and I must insert all the custom label definitions manually. I already made You aware of this problem also on V.503 - 2nd - Editing Custom Labels: The MaxQSO size field is common to both custom1 and custom2 labels record. Changing the custom1 label value You change also the custom2 label value and viceversa. But I need to set the Custom1 to 3 max qso, and the Custom2 to max 10 qso or more (printing directly on the card). I'm very disappointed to change this datum all the time when I change label size! I already made You aware of this problem also on V.503 - 3rd - Accessing to R.A.C.: When I press F3 to read the RAC info, I can read the data correctly. But switching to other qso, the RAC window rest inactive, showing the previus data. I must press F3 any time I want a new info. (Very tedious!!) On V.503 it runs well, showing itself a new info on any new qso selected. - 4th - In V.602 the SSB reports changed to 3 digits - I am not happy about it. I have never used 3 and I wish there was a small radio button in preferences that allowed me to pick either 2 or 3 digits. Better yet the 3rd digit of the report could be listed under DISABLED FIELDS!! (requested also by tonno/es5tv). - 5th - Manager database: After an importing qsl manager file (.txt), I found wrong dates on its database!! Urgent to fix!!! - 6th - Filter selection: As qsl manager I appreciate very much the dx4win facility to load several logs on the same file, selecting each time the one to up to date. Unfortunately sometimes (adding, merging or importing new qsos) I have a mishop, because I forget to change the PREFERENCE|QSO|GROUP|# after making the QSO|FILTER|SELECTION of the specified log group (for instance the #5). The result is that all qsos I want added on the selected log #5 are added on the log #1 (as predisposed on FILE|PREFERENCES|QSO|GROUP|#), with hard problems to restore the right situation (re-install the backup file and repeat the qso adding). I should like that the QSO|GROUP|# in the QSO window have an automatic change, according to the QSO|FILTER|SELECTION activated. In fact, if I select a specified group, I want to work on it only!!! Why not improve an automatic QSO|GROUP|# change, in presence of the QSO|FILTER|SELECTION switched NOT ZERO? In short, I should like the QSO|GROUP will be fixed: - equal to PREFERENCE|DEFAULT FOR NEW QSO|GROUP if the FILTER|SELECTION is not activated (set to zero). - equal to FILTER|SELECTION|# if the FILTER|SELECTION is activated (not zero). Only few lines of code needed, I think, as: IF [QSO|FILTER|SELECTION] == 0 [QSO|GROUP|#] == [FILE|PREFERENCES|QSO|GROUP|#] ELSE [QSO|GROUP|#] == [QSO|FILTER|SELECTION|#] ENDIF I already made You aware of this problem also on V.503 - 7th - When importing QSL Managers or Managers' Addresses would like to see which entries were changed!! Not just Replaced 55 and Added 32. There could be messages the same way as when merging CTY files! (Maybe I need to restore some data!!) (requested also by tonno/es5tv). That is all for the moment. I'm testing I hope it is of help! Ciao Steve Stefano Cipriani / IØMWI http://www.qsl.net/i0mwi e-mail: [EMAIL PROTECTED] - In and outgoing mail scanned with NAV 2002
[Dx4win] Packet Window
At 08:43 AM 2/9/03 -0500, W8TTS wrote: Something else that I noted, is that now if you exit the program and restart, the DX spots window is cleared. 5.x didn't do this. I would prefer to see the spots remain in that window unless cleared. There are times when you close and restart the programs, i.e. a hard computer lock, oops I clicked on the [x], etc., and want to see the spots that were there remain when I restart. This doesn't happen to me. The packet window is empty, but the old spots remain till cleared. 73, Pete N4ZR The World HF Contest Station Database was updated 1 Feb 03. Are you current? www.pvrc.org/wcsd/wcsdsearch.htm
[Dx4win] Packet Window
Interesting. I've been working on the awards file, so have been ending and starting the program over and over. And, every time with 6.02 the spots have been cleared. Have I missed setting an option some place? 73 - Ted - W8TTS Jim Reisert AD1C wrote: Not here. Works the same as 5.03. At 08:43 AM 2/9/2003 -0500, you wrote: Something else that I noted, is that now if you exit the program and restart, the DX spots window is cleared. 5.x didn't do this. I would prefer to see the spots remain in that window unless cleared. There are times when you close and restart the programs, i.e. a hard computer lock, oops I clicked on the [x], etc., and want to see the spots that were there remain when I restart. 73 - Ted - W8TTS -- 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] DX4WIN-WRITELOG-W5XD KEYER
Hello, With all the current dialogue concerning release 6.xx this may not get a look-in, but if you a DX4WIN and Writelog W5XD Multi-Keyer user then please read on. I am currently using release 5.03 of DX4WIN, and have just installed the W5XD keyer for use under Writelog. However, in doing this I can not key (CW) either rig (1000MP or TS440) when using DX4WIN. I have been reliably informed that this is to do with a driver issue and not specifically related to the keyer itself.I need to key on the serial port, which in my case is COM2. Does anyone know of a driver that I can download that will overcome this and permit me to run DX4WIN alongside the W5XD unit? oh, and if for some reason this has been addressed with release 6.xx then I'll be certain to upgrade. In fact I will do so anyway, but just need to get this sorted first! 73 and thanks for assistance Steve GW4BLE
[Dx4win] Vers. 6.02
For the RAC lookup... Right click on the window and check Automatic Update ... He knows about the QSL manager date problem The 3 digit reports are to accommodate modes other than SSB... But I agree about making a preference on this... I've asked Paul the same thing... -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Stefano Cipriani Sent: February 9, 2003 9:11 AM To: KK4HD Paul (dx4win); dx4win/reflector Cc: NR4M Steve (dx4win) Subject: [Dx4win] Vers. 6.02 Hi Paul, Can You modify the V.603 to fix these problems? - 1st - Just installed V.602 and migrated .INI file from my V.503. On it there are a couple of labeled items about the custom 1 and 2 label definitions, as you can see: [CustLab1] LabelID=3DCustom1 Metric=3D1 SpacingTop=3D0.039 SpacingLeft=3D0.039 SpacingHeight=3D1.169 SpacingWidth=3D2.756 LabelHeight=3D1.091 LabelWidth=3D2.717 RightShift=3D0.000 DownShift=3D0.000 PageWidth=3D8.268 PageHeight=3D12.028 NumAcross=3D3 NumDown=3D10 PaperName=3DCustom Portrait=3D1 [CustLab2] LabelID=3DCustom2 Metric=3D1 SpacingTop=3D0.787 SpacingLeft=3D0.315 SpacingHeight=3D3.189 SpacingWidth=3D3.327 LabelHeight=3D3.110 LabelWidth=3D3.307 RightShift=3D0.000 DownShift=3D0.000 PageWidth=3D4.134 PageHeight=3D5.315 NumAcross=3D1 NumDown=3D1 PaperName=3DCustom Portrait=3D1 After merging the .ini file, all the custom label fields are setting to zero, and I must insert all the custom label definitions manually. I already made You aware of this problem also on V.503 - 2nd - Editing Custom Labels: The MaxQSO size field is common to both custom1 and custom2 labels record. Changing the custom1 label value You change also the custom2 label value and viceversa. But I need to set the Custom1 to 3 max qso, and the Custom2 to max 10 qso or more (printing directly on the card). I'm very disappointed to change this datum all the time when I change label size! I already made You aware of this problem also on V.503 - 3rd - Accessing to R.A.C.: When I press F3 to read the RAC info, I can read the data correctly. But switching to other qso, the RAC window rest inactive, showing the previus data. I must press F3 any time I want a new info. (Very tedious!!) On V.503 it runs well, showing itself a new info on any new qso selected. - 4th - In V.602 the SSB reports changed to 3 digits - I am not happy about it. I have never used 3 and I wish there was a small radio button in preferences that allowed me to pick either 2 or 3 digits. Better yet the 3rd digit of the report could be listed under DISABLED FIELDS!! (requested also by tonno/es5tv). - 5th - Manager database: After an importing qsl manager file (.txt), I found wrong dates on its database!! Urgent to fix!!! - 6th - Filter selection: As qsl manager I appreciate very much the dx4win facility to load several logs on the same file, selecting each time the one to up to date. Unfortunately sometimes (adding, merging or importing new qsos) I have a mishop, because I forget to change the PREFERENCE|QSO|GROUP|# after making the QSO|FILTER|SELECTION of the specified log group (for instance the #5). The result is that all qsos I want added on the selected log #5 are added on the log #1 (as predisposed on FILE|PREFERENCES|QSO|GROUP|#), with hard problems to restore the right situation (re-install the backup file and repeat the qso adding). I should like that the QSO|GROUP|# in the QSO window have an automatic change, according to the QSO|FILTER|SELECTION activated. In fact, if I select a specified group, I want to work on it only!!! Why not improve an automatic QSO|GROUP|# change, in presence of the QSO|FILTER|SELECTION switched NOT ZERO? In short, I should like the QSO|GROUP will be fixed: - equal to PREFERENCE|DEFAULT FOR NEW QSO|GROUP if the FILTER|SELECTION is not activated (set to zero). - equal to FILTER|SELECTION|# if the FILTER|SELECTION is activated (not zero). Only few lines of code needed, I think, as: IF [QSO|FILTER|SELECTION] =3D=3D 0 [QSO|GROUP|#] =3D=3D [FILE|PREFERENCES|QSO|GROUP|#] ELSE [QSO|GROUP|#] =3D=3D [QSO|FILTER|SELECTION|#] ENDIF I already made You aware of this problem also on V.503 - 7th - When importing QSL Managers or Managers' Addresses would like to see which entries were changed!! Not just Replaced 55 and Added 32. There could be messages the same way as when merging CTY files! (Maybe I need to restore some data!!) (requested also by tonno/es5tv). That is all for the moment. I'm testing I hope it is of help! Ciao Steve Stefano Cipriani / I=D8MWI http://www.qsl.net/i0mwi e-mail: [EMAIL PROTECTED] - In and outgoing mail scanned with NAV 2002 ___ Dx4win mailing list Dx4win@mailman.qth.net http://mailman.qth.net/mailman/listinfo/dx4win
[Dx4win] Flying Horse Info
When I hit the F3 key in the main log I get Flying Horse Error: 3 What am I doing wrong? Tnx, Roger, W7VV --- 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] Packet Window
I'm not having that problem here. Running Windows XP, 6.02, FAT32. The only option in the packet window that I use is 'Ignore Grayed out spots'. In the screen portion of preferences, I do not have 'Leave all windows in their original position' checked. Don't know if the above makes a difference or not! 73 de Don W0DJC At 07:07 AM 2/9/2003 -0500, you wrote: If I remember correctly, in the 5.x version if I made the send part (bottom) of the Packet Window smaller it stayed that way when I exited and restarted DX4Win. But, in the 6.x version, I have to resize it every time. Anyone else seeing this? 73 - Ted - W8TTS ___ Dx4win mailing list Dx4win@mailman.qth.net http://mailman.qth.net/mailman/listinfo/dx4win
[Dx4win] V 6.02
The DX4WIN exe file is actually around 2.8Mb; I used an EXE packer to reduce the size of the program to about 900K. I guess that on relatively slow computers the unpacking time is the delay you notice. The program I used for this is called UPX, and it is a free program. I downloaded mine from: http://upx.sourceforge.net/download/upx124w.zip I mention this, because the packer can also unpack the executable, and give you the original large dx4win.exe file. On the command line, in the dx4w602 directory, do: upx -d dx4win.exe Paul At 02:01 PM 2/8/03 -0500, Benjamin Diaz Jr wrote: I just got this new version and I find it very slow to load(it takes 12 secs). Does anybody have this problem? 73 de k4ben ___ 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] V 6.02
Ben, It depends on your file size. I have 18k QSOs and it opens in less than a second. 73 de Tom, K4NR - Original Message - From: Benjamin Diaz Jr [EMAIL PROTECTED] To: dx4win@mailman.qth.net Sent: Saturday, February 08, 2003 1:01 PM Subject: [Dx4win] V 6.02 I just got this new version and I find it very slow to load(it takes 12 secs). Does anybody have this problem?
[Dx4win] Flying Horse Info
Roger, How have you set up the preferences for the CD? Tom - Original Message - From: Roger Huntley [EMAIL PROTECTED] To: Dx4win@mailman.qth.net Sent: Sunday, February 09, 2003 11:46 AM Subject: [Dx4win] Flying Horse Info When I hit the F3 key in the main log I get Flying Horse Error: 3 What am I doing wrong? Tnx, Roger, W7VV --- 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 mailing list Dx4win@mailman.qth.net http://mailman.qth.net/mailman/listinfo/dx4win
[Dx4win] Packet Window
Hi Ted, Just mark : PREFERENCES=PACKET1=BACKUP DX SPOTS. And the spots will remain. 73, Jaime EA6NB. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Ted Sarah - W8TTS Sent: Sunday, February 09, 2003 13:44 To: [EMAIL PROTECTED] Cc: DX4Win Reflector Subject: Re: [Dx4win] Packet Window Something else that I noted, is that now if you exit the program and restart, the DX spots window is cleared. 5.x didn't do this. I would prefer to see the spots remain in that window unless cleared. There are times when you close and restart the programs, i.e. a hard computer lock, oops I clicked on the [x], etc., and want to see the spots that were there remain when I restart. 73 - Ted - W8TTS Dave Hawes wrote: Yes, that is the way it used to work. In fact, the size of the send window is also lost if you click on Maximize and then Restore. I liked it the old way, and wonder if there is some new functionality that is tied to this behavior. If not, perhaps it can be either restored to the previous behavior, which I prefer over the current way. 73 - Dave N3RD On 9 Feb 2003 at 7:07, Ted Sarah - W8TTS wrote: If I remember correctly, in the 5.x version if I made the send part (bottom) of the Packet Window smaller it stayed that way when I exited and restarted DX4Win. But, in the 6.x version, I have to resize it every time. Anyone else seeing this? 73 - Ted - W8TTS ___ Dx4win mailing list Dx4win@mailman.qth.net http://mailman.qth.net/mailman/listinfo/dx4win ___ Dx4win mailing list Dx4win@mailman.qth.net http://mailman.qth.net/mailman/listinfo/dx4win ___ Dx4win mailing list Dx4win@mailman.qth.net http://mailman.qth.net/mailman/listinfo/dx4win
[Dx4win] Packet Window
Jaime, That is not related. I wonder if the dx4win.put in the save sub-directory is read-only. Paul At 06:27 PM 2/9/03 +, Jaime P.Ull=EDvarri wrote: Hi Ted, Just mark : PREFERENCES=3DPACKET1=3DBACKUP DX SPOTS. And the spots will remain. 73, Jaime EA6NB. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Ted Sarah - W8TTS Sent: Sunday, February 09, 2003 13:44 To: [EMAIL PROTECTED] Cc: DX4Win Reflector Subject: Re: [Dx4win] Packet Window Something else that I noted, is that now if you exit the program and restart, the DX spots window is cleared. 5.x didn't do this. I would prefer to see the spots remain in that window unless cleared. There are times when you close and restart the programs, i.e. a hard computer lock, oops I clicked on the [x], etc., and want to see the spots that were there remain when I restart. 73 - Ted - W8TTS Dave Hawes wrote: Yes, that is the way it used to work. In fact, the size of the send window is also lost if you click on Maximize and then Restore. I liked it the old way, and wonder if there is some new functionality= that is tied to this behavior. If not, perhaps it can be either restored to the previous behavior, which I prefer over the current way. 73 - Dave N3RD On 9 Feb 2003 at 7:07, Ted Sarah - W8TTS wrote: If I remember correctly, in the 5.x version if I made the send part (bottom) of the Packet Window smaller it stayed that way when I exited and restarted DX4Win. But, in the 6.x version, I have to resize it every time. Anyone else seeing this? 73 - Ted - W8TTS ___ Dx4win mailing list Dx4win@mailman.qth.net http://mailman.qth.net/mailman/listinfo/dx4win ___ Dx4win mailing list Dx4win@mailman.qth.net http://mailman.qth.net/mailman/listinfo/dx4win ___ Dx4win mailing list Dx4win@mailman.qth.net http://mailman.qth.net/mailman/listinfo/dx4win ___ Dx4win mailing list Dx4win@mailman.qth.net http://mailman.qth.net/mailman/listinfo/dx4win=20 Paul van der Eijk (KK4HD) [EMAIL PROTECTED] http://www.dx4win.com
[Dx4win] Packet Window
Interesting. I didn't have that checked in the 5.x version, but I just tried it in the 6.x version, and now the spots stay in the DX Spots window. 73 - Ted - W8TTS Jaime P.Ullívarri wrote: Hi Ted, Just mark : PREFERENCES=PACKET1=BACKUP DX SPOTS. And the spots will remain. 73, Jaime EA6NB. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Ted Sarah - W8TTS Sent: Sunday, February 09, 2003 13:44 To: [EMAIL PROTECTED] Cc: DX4Win Reflector Subject: Re: [Dx4win] Packet Window Something else that I noted, is that now if you exit the program and restart, the DX spots window is cleared. 5.x didn't do this. I would prefer to see the spots remain in that window unless cleared. There are times when you close and restart the programs, i.e. a hard computer lock, oops I clicked on the [x], etc., and want to see the spots that were there remain when I restart. 73 - Ted - W8TTS Dave Hawes wrote: Yes, that is the way it used to work. In fact, the size of the send window is also lost if you click on Maximize and then Restore. I liked it the old way, and wonder if there is some new functionality that is tied to this behavior. If not, perhaps it can be either restored to the previous behavior, which I prefer over the current way. 73 - Dave N3RD On 9 Feb 2003 at 7:07, Ted Sarah - W8TTS wrote: If I remember correctly, in the 5.x version if I made the send part (bottom) of the Packet Window smaller it stayed that way when I exited and restarted DX4Win. But, in the 6.x version, I have to resize it every time. Anyone else seeing this? 73 - Ted - W8TTS ___ Dx4win mailing list Dx4win@mailman.qth.net http://mailman.qth.net/mailman/listinfo/dx4win ___ Dx4win mailing list Dx4win@mailman.qth.net http://mailman.qth.net/mailman/listinfo/dx4win ___ Dx4win mailing list Dx4win@mailman.qth.net http://mailman.qth.net/mailman/listinfo/dx4win ___ Dx4win mailing list Dx4win@mailman.qth.net http://mailman.qth.net/mailman/listinfo/dx4win
[Dx4win] Packet Window
It just worked for me, after crossing Backup spots they remain I did think it was a normal behavior of the program. Jaime -Original Message- From: Paul van der Eijk [mailto:[EMAIL PROTECTED] Sent: Sunday, February 09, 2003 18:41 To: Jaime P.Ullívarri; Dx4win@mailman.qth.net Cc: DX4Win Reflector Subject: RE: [Dx4win] Packet Window Jaime, That is not related. I wonder if the dx4win.put in the save sub-directory is read-only. Paul At 06:27 PM 2/9/03 +, Jaime P.Ullívarri wrote: Hi Ted, Just mark : PREFERENCES=PACKET1=BACKUP DX SPOTS. And the spots will remain. 73, Jaime EA6NB. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Ted Sarah - W8TTS Sent: Sunday, February 09, 2003 13:44 To: [EMAIL PROTECTED] Cc: DX4Win Reflector Subject: Re: [Dx4win] Packet Window Something else that I noted, is that now if you exit the program and restart, the DX spots window is cleared. 5.x didn't do this. I would prefer to see the spots remain in that window unless cleared. There are times when you close and restart the programs, i.e. a hard computer lock, oops I clicked on the [x], etc., and want to see the spots that were there remain when I restart. 73 - Ted - W8TTS Dave Hawes wrote: Yes, that is the way it used to work. In fact, the size of the send window is also lost if you click on Maximize and then Restore. I liked it the old way, and wonder if there is some new functionality that is tied to this behavior. If not, perhaps it can be either restored to the previous behavior, which I prefer over the current way. 73 - Dave N3RD On 9 Feb 2003 at 7:07, Ted Sarah - W8TTS wrote: If I remember correctly, in the 5.x version if I made the send part (bottom) of the Packet Window smaller it stayed that way when I exited and restarted DX4Win. But, in the 6.x version, I have to resize it every time. Anyone else seeing this? 73 - Ted - W8TTS ___ Dx4win mailing list Dx4win@mailman.qth.net http://mailman.qth.net/mailman/listinfo/dx4win ___ Dx4win mailing list Dx4win@mailman.qth.net http://mailman.qth.net/mailman/listinfo/dx4win ___ Dx4win mailing list Dx4win@mailman.qth.net http://mailman.qth.net/mailman/listinfo/dx4win ___ 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] importing Contest files
Can I import CTWIN contest logs to DX4WIN? If so How. Thanks Lee N5PO
[Dx4win] Where can I get 5.03
I can't get 6.03 to work in other than demo mode and am reverting back to 5.03. Where can I get the install package (dx4win503.zip presumably)? Thanks 73 Stan, N3HS
[Dx4win] Green on white spots
Gray is nice, then you turn off gray spots, and work someone else! -Original Message- From: Mel Martin (VE2DC) [mailto:[EMAIL PROTECTED] Sent: Thursday, February 06, 2003 8:39 PM To: [EMAIL PROTECTED]; [EMAIL PROTECTED]; 'Dave Jaksa'; 'Wendell Wyly W5FL'; dx4win@mailman.qth.net Subject: RE: [Dx4win] Green on white spots Actually it's grey once you work it... Something I'm not sure I agree with... Think it should be black... Grey should be just those spots you have indicated you don't want to see at all... -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Mel Martin (VE2DC) Sent: February 6, 2003 7:30 PM To: [EMAIL PROTECTED]; 'Dave Jaksa'; 'Wendell Wyly W5FL'; dx4win@mailman.qth.net Subject: RE: [Dx4win] Green on white spots If the same station is spotted that you've worked before... It should be black... If it's a different station it should be red... But I'm not sure which way DX4Win works... I'll have to test it... -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jim Reisert AD1C Sent: February 6, 2003 5:22 PM To: Dave Jaksa; 'Wendell Wyly W5FL'; dx4win@mailman.qth.net Subject: RE: [Dx4win] Green on white spots It's hard to explain, but there are those of us who like to work every country on every possible band/mode combination. It's a sickness, I'll admit it. Here's how I think of the colors (sorry, no priority numbers for me): DU9RG is spotted on 40 meter CW. I have never worked DU on 40 meters, so the spot is bright red. So I work him for a new one. Now if DU9/N0NM is later spotted on 40 meter CW, the spot will be light red (worked but not confirmed on this band). Doesn't matter if it's spotted on SSB, same will apply, since it's not confirmed on this band. ___ Dx4win mailing list Dx4win@mailman.qth.net http://mailman.qth.net/mailman/listinfo/dx4win
[Dx4win] IMPORTANT: Country file maintenance
Just wanted to post an update: Thanks to the following hams who sent me their country file: DL1AMQ ES5TV GM3POI I0MWI K0CA K2CIB K2TK K3WC K4NR K6MMC K9EL K9RB N2VW N2WK N3SL N4IG N4ZR OH6NIO ON4AOI PY2YP SM4WGB W0DJC W0QE W2UP W5FL W8TTS Including the DX4W602 default and my own file, that's 28 country files! Merging all the callsign exception data together resulted in 6910 unique exceptions (duplicates are not counted). Many of these are quite similar, i.e. a DXpedition was logged one day earlier by someone than by someone else. For reference, the file that comes with 6.02 has only 841 callsign exceptions. After almost 1000 lines of 'C' code, the combined data has been automatically processed down to 2602 good callsign exceptions. I still need to hand-audit this list, there are some mistakes that need to be corrected which will reduce the size of the file somewhat. Along the way I encountered a number of issues: - busted calls - calls logged with the wrong prefix - calls logged with the wrong zone (i.e. 9M2 in zone 22) - calls that otherwise resolve properly with the existing prefix maps - tons of stateside exceptions, usually the result of importing CQWW logs where the logged zone does not match the default The data is looking good so far. I hope to put out a trial database this week to the people above so they can inform me if there are any remaining problems. I'm still accepting country files if you want to pass yours along. 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] Rick Schwartz, K8HEF
Rick, Your ISP is bouncing my Emails as 'user unknown'. I did a 'reply' so am using the address you provided. 73 de Steve, NR4M - -Steve Bookout, NR4M (ex NJ4F) Rapidan Data Systems 'DX4WIN...The way logging programs should be!' Free demo at http://www.dx4win.com
