[Dx4win] version 7.02 build 13

dx4w702.exe is back as build 13. The import is fixed (strange we never saw that problem before) Latest dx4win.awd file from Jim, AD1C, with additional prefixes fixed Gitmo prefixes are adjusted for calls like kg44xx I did not touch updating the band for incoming spots when a radio is not

FW: [Dx4win] version 7.02 build 13

-Original Message- From: John Shaw [mailto:[EMAIL PROTECTED] Sent: Tuesday, 16 May 2006 6:20 p.m. To: 'Paul van der Eijk' Subject: RE: [Dx4win] version 7.02 build 13 Hi Again, Well you have me stumped this time. Yes the import works and the program doesn't fall over. BUT! If I do

[Dx4win] 7.02 available

Typo error my callsign is G8DQZ NOT G9DQZ!! -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Tony Lord Sent: 15 May 2006 18:36 To: 'Jim Reisert AD1C'; dx4win@mailman.qth.net Subject: RE: [Dx4win] 7.02 available Jim, Thanks to you and the boys from

[Dx4win] QSL print in Dx4Win 7.02.13

When I print some QSL cards, QSL method is always check and I must uncheck it every time I print. It wasn't the case in previous versions and it was better because if I forget to uncheck I waste a label. But, I test many computer logbooks and, for me, Dx4Win is definitively THE BEST. Alain, F5LIW

[Dx4win] version 7.02 build 13 (DX4WIN.AWD)

At 12:19 AM 5/16/2006, Paul van der Eijk wrote: dx4w702.exe is back as build 13. The import is fixed (strange we never saw that problem before) Latest dx4win.awd file from Jim, AD1C, with additional prefixes fixed The latest DX4WIN.AWD did NOT make it into this release. You can download the

[Dx4win] version 7.02 build 13 (DX4WIN.AWD)

Jim, Are you saying this should be downloaded and added to save dic of V7.02?? 73's de Tony G8DQZ -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jim Reisert AD1C Sent: 16 May 2006 12:13 To: Paul van der Eijk; dx4win@mailman.qth.net Subject: Re:

[Dx4win] version 7.02 build 13 (DX4WIN.AWD)

At 07:22 AM 5/16/2006, Tony Lord G8DQZ asked: Are you saying this should be downloaded and added to save dir of V7.02?? Yes. I put out a new release in late April/early May but had not converted all the prefixes properly. This one is correct. 73 - Jim AD1C The latest DX4WIN.AWD did NOT make

[Dx4win] UPFIOTA export

The UPFIOTA format is used for importing data into the IOTAMEM4WIN program: http://www.rsgbiota.org/downloads.php4 Unfortunately, the format in DX4WIN 7.02 is not quite correct. If you want to export your IOTA from DX4WIN into this program, please contact me. I can put a conversion

[Dx4win] dx4win 702 download questions

1. I downloaded once. I must download agn to get the dx4win 702 build 13? How can i found which i have dowloaded? 2. Jim the awd file has included the additions for Japanese prefectures (from 9k2hn)? Is it a more complete or just a change form the previous original? Kostas sv1dpi

[Dx4win] dx4win 702 download questions

At 07:38 AM 5/16/2006, Kostas Stamatis wrote: 1. I downloaded once. I must download agn to get the dx4win 702 build 13? How can i found which i have dowloaded? When DX4WIN is running, you can see the full version number in the main program, or using Help - About 73 - Jim AD1C -- Jim

[Dx4win] DX4WIN.AWD - call for custom awards

At 07:38 AM 5/16/2006, Kostas Stamatis SV1DPI wrote: 2. Jim the awd file has included the additions for Japanese prefectures (from 9k2hn)? Is it a more complete or just a change form the previous original? It is just a prefix change from the original. I0MWI sent me a large file that I have

[Dx4win] Which build number

Just downloaded and installed 7.02.12 in time to find out there is a 7.02.13??? Is there any way to tell the build number short of installing and seeing the help file?? Would like to be sure of installing the latest version. THANKS BILL-W5VW ___

[Dx4win] version 7.02 build 13

It would be nice if the file name would include the build number, i.e. dx4w702b13.exe. If one isn't a member of this list there is no way to see that a new build with fixes has been released. 73, Alan N5NA Paul van der Eijk wrote: dx4w702.exe is back as build 13. The import is fixed

[Dx4win] version 7.02 build 13

Bill and other users you can see the number On top of DX4WIN just before your license DX4WIN 7.02.13 ON4AOI Guy Dewaelhens 73 Guy ON4AOI BAND DECODER and related stuff at http://www.on4aoi.be/banddecoder.htm DX4WIN soft and related stuff at http://www.on4aoi.be/dx4win.htm DX4WIN,

[Dx4win] version 7.02 build 13

Yes, I and others are aware of that. However, you should be able to tell what build is on the web site before downloading and installing it. If I just check the website and see version 7.02 is available I don't know if that is the build I am currently running or if that is a later build that

[Dx4win] version 7.02 build 13

So I just upgraded over the weekend with no issues but I have 7.02 build 12. Does this mean I have to upgrade again? Les ON4AOI wrote: Bill and other users you can see the number On top of DX4WIN just before your license DX4WIN 7.02.13 ON4AOI Guy Dewaelhens 73 Guy ON4AOI BAND DECODER

[Dx4win] version 7.02 build 13 (DX4WIN.AWD)

There are two small errors in the file in the web site: 230c230 SY/A=Mt Athos --- SV/A=Mt Athos 2214c2214 IS0=Iasi --- IS=Iasi You can fix them with a plain text editor, or wait for me to release the files again. 73 - Jim AD1C --- Jim Reisert AD1C [EMAIL PROTECTED] wrote: At 12:19 AM

[Dx4win] DX4W702 build 13 EXE file is downloadable from my webpage

Hi All, For those who have installed DX4W702 build 12 You only need to download @ my webpage the new DX4WIN.EXE build 13 And replace in your DX4WIN directory. And not reinstall all 73 Guy ON4AOI BAND DECODER and related stuff at http://www.on4aoi.be/banddecoder.htm DX4WIN soft and related

[Dx4win] version 7.02 build 13

Ok Alan, I understand, Normally Paul announces when there is a new release available Or in this case another build when there is a problem we didn't notice or a bug fix. And shortly or even @ the same moment my webpage is also updated with this latest release. Without a announce of Paul or Steve

[Dx4win] DX4W702 build 13 EXE file is downloadable from my webpage

Guy, Thanks for the info, I have now changed my exe file to v13 from v12 off your site. I may have missed the thread, but out of interest, what's the difference between 12 13?? Thanks Tony G8DQZ -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of ON4AOI

[Dx4win] DX4W702 build 13 EXE file is downloadable from my webpage

--- Tony Lord [EMAIL PROTECTED] wrote: Thanks for the info, I have now changed my exe file to v13 from v12 off your site. I may have missed the thread, but out of interest, what's the difference between 12 13?? It's in the archives:

[Dx4win] DX4Win 7.02.13 - MMTTY/FSK - MicroHam Keyer?

Is there anybody who could walk me through the settings? MMTTY works fine on FSK as a stand-alone, but I am not able to find settings to key the FSK or PTT through MK and DX4Win. I am using COM7 for FSK. If I check the PTT box in the MK COM7 setting, I get a steady PTT signal. However, no FSK

[Dx4win] version 702 build 14

Website has now build 14 of version 702 The only difference with version 13 is the updated dx4win.awd file that I unzipped in the wrong location yesterday. --Paul Paul van der Eijk (KK4HD) Hi, think its better to wait for version 7.03 instead uploading

[Dx4win] DX4Win 7.02.13 - MMTTY/FSK - MicroHam Keyer?

I'm not in front of the radio, but I do have a copy of DX4WIN here. First, make sure that MMTTY works stand-alone with microKeyer. In DX4WIN preferences - RTTY: - Type should be None - COM Port is your PTT port (might not be used) - MMTTY Executable is full path to, and including, mmtty.exe

[Dx4win] version 702 build 14

Akira, When did you download ? I have the 702 build 14 from Paul My webpage and WWW.DX4WIN.COM have both Version 702 build 14 73 Guy ON4AOI BAND DECODER and related stuff at http://www.on4aoi.be/banddecoder.htm DX4WIN soft and related stuff at http://www.on4aoi.be/dx4win.htm DX4WIN,

[Dx4win] version 7.02 build 13

For those of us who have installed build 12 and wish not to re-import, re-merge and/or rebuild the support files, should we install build 13 to a new folder and then copy dx4win.exe to the current folder? Garry, NI6T -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]

[Dx4win] version 702 build 14

--- Akira Iizuka [EMAIL PROTECTED] wrote: 7.02-14 was installed. However DX4WIN displays 7.04-12. You must exit DX4WIN before installing the update. It looks correct here, make sure you have this .EXE file: 5/16/2006 11:55 2,835,968 dx4win.exe 73 - Jim AD1C -- Jim Reisert AD1C, 7

[Dx4win] Telnet to AD1C DX cluster

DX4WIN users are invited to connect to my DX Spider node: dxc.ad1c.us (standard Telnet port 23) There's already an entry in dx4win.tcp for this node. Worldwide spots, SH/QRZ, satellite params, etc. 73 - Jim AD1C -- Jim Reisert AD1C, 7 Charlemont Court, North Chelmsford, MA 01863 USA

[Dx4win] DX4WIN

Hello All, Since I don't have one of these rigs, I need to ask. Which Yaesu rig driver works with the FT-840. Think I used to have the answer, but Email stuff so 'hosed up', I can't find any reference to it in my archives. You can just email me directly. Thanks. 73 de Steve, NR4M Rapidan

[Dx4win] Be very carefull 7.02 13 or 7.02 14

Just a heads up, and I am not trying to poor cold water on Paul's efforts he has responded well when an error has been found, BUT. Be very careful when running a lotwreport.Adi download into your log. Make sure you have a safe backup so that if you don't like the results you can go back. I don't

[Dx4win] Odd deal !!!

Noticed another oddity with build 13. I always keep the packet window on top of rtty unless I'm running rtty. Now, with the packet window on top, if I happen to maximize my home page on top of Dx4win for e-mail or whatever, it always pops the rtty window on top of the packet window. Back to

[Dx4win] version 702 build 14

Hi Jim and all, Solved it. Thank you. Aki Jim Reisert AD1C wrote: --- Akira Iizuka [EMAIL PROTECTED] wrote: 7.02-14 was installed. However DX4WIN displays 7.04-12. You must exit DX4WIN before installing the update. It looks correct here, make sure you have this .EXE file: 5/16/2006