|
locked
Re: : JT65-HF & WSJT-X log files
rjferland
Laurie,
With JT65HF ver. 1.0.9.3 and JTAlert 2.8.7, I use the standard ADIF file which writes to a file I named JT65log.adi. With WSJTX ver. 1.6.0 and JTAlertX ver. 1.6.0, I again use the standard ADIF file which writes to a file I named JT9_log.adi.
I have 2 separate log adi files one for all the JT65HF contacts and one for all my WSJTX JT9 contacts. Both these adi log files are in my DXBase logging program directory. I have a bridge that as I log the contact it adds them to my DXBase log book.
Now I wish only to use WSJTX which can do both JT65 and JT9.
How can I get WSJTX to read both adif files? Do I import the JT65HF adi file into the WSJTX adi file?
If so how do I accomplish this?
Thank you Russ
|
|
|
|
locked
Re: : HRD V6 Logging abandonment - A brief explanation.
Rick Johnson
WSJT-X / JTAlertX 2.8.7 / DXKeeper 13.8.5 FLDIGI 73,
On Fri, Dec 30, 2016 at 11:15 AM, nealix@... [HamApps] <HamApps@...> wrote:
|
|
|
|
locked
Re: HRD V6 Logging abandonment - A brief explanation.
@Daveq
I am one affected by the HRD logging issue. I can either move on from HRD or abandon JTAlert. Last evening I downloaded the DXLab Commander and DXKeeper. I was able to set it up in under an hour and logging contacts with the support of JTAlert. Uploaded to LoTW and also downloaded from them. Still have some configs to do but the move was almost seamless. Have moved on from HRD. Can't wait for JTAlert 2.9. 73 Dave W3DLQ
|
|
|
|
locked
Re: : HRD V6 Logging abandonment - A brief explanation.
Dave (NK7Z)
I would wait until the end of today, and see what the "announcement" is, I suspect it will change things.
73s and thanks, Dave NK7Z http://www.nk7z.net
|
|
|
|
locked
Re: : HRD V6 Logging abandonment - A brief explanation.
chas cartmel
I use version 5.24.0.38, the final free version as written by Simon Brown G4ELI and ‘updated’ by HRDLLC prior to the release of version 6.t All the functionality you speak of is in that version also.
73 Charlie www.G4EST.me.uk Twitter:@ccartmel
From: HamApps@... [mailto:HamApps@...]
Sent: 30 December 2016 16:15 To: HamApps@... Subject: [HamApps] Re:: HRD V6 Logging abandonment - A brief explanation.
Laurie: You have my vote.
While I purchased and use HRD (before I found out about this stuff), I completely agree with you. Living in America, the basic foundation of our system is that you have guaranteed rights to freedom of speech, without fear of consequence. It is illegal for any company to take back a product you have paid for. That is basically theft. When they do it because of a customer voicing an opinion, they are also violating our constitutional rights, a federal law.
Even though I like the functionality of HRD and it's logbook, I will study and find a new alternative. After reading all of this, I too refuse to support these bastards.
I see an alarming trend in our hobby that I don't see so much in others; There are several companies that are behaving like HRD. LDG tuners is another one. I received a brand new unit with a manufacturing quality control defect. I went to the public support forums on Yahoo Groups and noticed another person had the same issue. I posted that this is what happened to my unit also, so they must be missing something in manufacturing inspection.
Suddenly, I was banned from the groups. I received an email from Dwayne at LDG disagreeing with my post. When I tried to reply and inquire what was going on, I found that my email was blacklisted also. Great customer support. I paid money, had an immediate problem on receipt of the shipment, and was banned for talking about it. If that is how LDG, or HRD for that fact, think they will find happy paying customers, well, SCREW THEM! They deserve to die, which makes room for new vendors with better ethics.
I will watch this thread for suggestions on new logging programs. What I liked about HRD logbook was the ability to upload to almost every online log, including LOTW, QRZ.com, and eQSL.cc Hopefully one of the other logging programs can do that also. Then I can switch and flip the birdie at HRD
Cheers,
Neal N6YFM
|
|
|
|
locked
Re: : HRD V6 Logging abandonment - A brief explanation.
Dan Malcolm <dmalcolm24@...>
Neal, I am on the same search and for the same reasons. The main recommendation I have received from this forum are: ACLog, Log4OM, and DXKeeper. So far Log4OM looks to be the winner but DXKeeper is still in the running. Log4OM will upload to eQSL, LoTW, and QRZ, all of which I use. It will also upload to ClubLog and HamQTH. I use QRZ lookup and Log4OM will make use of that also. There is a learning curve with both.
Good luck, 73, & HPYNY.
_____________________________ Dan Malcolm CFI/II K4SHQ
From: HamApps@... [mailto:HamApps@...]
Sent: Friday, December 30, 2016 10:15 AM To: HamApps@... Subject: [HamApps] Re:: HRD V6 Logging abandonment - A brief explanation.
Laurie: You have my vote.
While I purchased and use HRD (before I found out about this stuff), I completely agree with you. Living in America, the basic foundation of our system is that you have guaranteed rights to freedom of speech, without fear of consequence. It is illegal for any company to take back a product you have paid for. That is basically theft. When they do it because of a customer voicing an opinion, they are also violating our constitutional rights, a federal law.
Even though I like the functionality of HRD and it's logbook, I will study and find a new alternative. After reading all of this, I too refuse to support these bastards.
I see an alarming trend in our hobby that I don't see so much in others; There are several companies that are behaving like HRD. LDG tuners is another one. I received a brand new unit with a manufacturing quality control defect. I went to the public support forums on Yahoo Groups and noticed another person had the same issue. I posted that this is what happened to my unit also, so they must be missing something in manufacturing inspection.
Suddenly, I was banned from the groups. I received an email from Dwayne at LDG disagreeing with my post. When I tried to reply and inquire what was going on, I found that my email was blacklisted also. Great customer support. I paid money, had an immediate problem on receipt of the shipment, and was banned for talking about it. If that is how LDG, or HRD for that fact, think they will find happy paying customers, well, SCREW THEM! They deserve to die, which makes room for new vendors with better ethics.
I will watch this thread for suggestions on new logging programs. What I liked about HRD logbook was the ability to upload to almost every online log, including LOTW, QRZ.com, and eQSL.cc Hopefully one of the other logging programs can do that also. Then I can switch and flip the birdie at HRD
Cheers,
Neal N6YFM
|
|
|
|
locked
Re: Announcement: Next release of JTAlert (2.9.0) will no logger support HRD V6 Logging.
chas cartmel
Ok Dan, all understood.
All the best to you and yours for 2017.
73 Charlie www.G4EST.me.uk Twitter:@ccartmel
From: HamApps@... [mailto:HamApps@...]
Sent: 30 December 2016 13:49 To: HamApps@... Subject: RE: [HamApps] Announcement: Next release of JTAlert (2.9.0) will no logger support HRD V6 Logging.
Charlie, Thanks for the offer. I should perhaps clarify. While I have done a lot of work with Access, the vast majority of it is using PHP against an Access database. I do have one application I wrote years ago in Access VBA but that’s all. Since you have gotten this far with your application, you may be better suited to coding a third party data transfer application.
For me, I really do like HRD. But HRDLLC folks have gotten on my nerves more than once. I am ready to use something else. I am currently trying Log4OM, and I am also going to try DXKeeper. I loaded up ACLog but it wouldn’t allow me to play more with it due to an expired trial some months ago. I am not opposed to paying for it, but I want to make sure it fits my needs first. Not their fault but there it is. My efforts at least initially will be to change my summary app to work with whatever log program I settle on.
Good luck and Happy New Year Charlie (good name – Charlie was also my dad’s name).
_____________________________ Dan Malcolm CFI/II K4SHQ
From: HamApps@... [mailto:HamApps@...]
Dan I have written a custom front end for HRD (database version 5.24.0.38) for the worked all Britain logging. It is specific to my needs but depending on what is needed could send you the code for ‘manipulation’ Written in VBA, it logs contacts from the entered data. The HRD database is basically a flat file and breaks many data design rules (I am a former data / database manager), but that simplifies the insert process. Not saying it is a superb bit of coding (it is not) but it may save ‘reinventing the wheel’. I am still using the free version of HRD as it still does all I want and after a run-in with HRDLLC myself will never subscribe.
I have a part completed video on the front end I use which I could also post if anybody wants to see the functionality.
If people want to use HRD you could still interface through ADIF or downgrade to version 5 which has NEVER failed on me.
From: HamApps@... [mailto:HamApps@...]
Hmmm maybe. I’ve done a good deal of work (before retirement) with MS Access and just a little with SQL. Since Access is queried by SQL I am familiar with that language, but not an expert. I’ll give it some thought, but no promises.
_____________________________ Dan Malcolm CFI/II K4SHQ
From: HamApps@... [mailto:HamApps@...]
Somebody could write a companion application that takes the JTAlert log message and relays to other loggers that aren't directly supported. Sounds like you may have the credentials to do that.
de Mike W9MDB
From: "'Dan Malcolm' dmalcolm24@... [HamApps]" <HamApps@...>
Laurie, No discussion necessary. Your decision has however created a real problem for me. I love JTAlert, but I also have some software I’ve written around HRD Logbook. My problem is not your problem however. I just assume your reasons are valid. Now I have decisions of my own to make.
_____________________________ Dan Malcolm CFI/II K4SHQ
From: HamApps@... [mailto:HamApps@...]
To all JTAlert / HRD V6 users.
|
|
|
|
locked
Re: : HRD V6 Logging abandonment - A brief explanation.
'DGB' <ns9i2016@...>
73 Dwight NS9I
|
|
|
|
locked
Re: : HRD V6 Logging abandonment - A brief explanation.
Laurie: You have my vote. While I purchased and use HRD (before I found out about this stuff), I completely agree with you. Living in America, the basic foundation of our system is that you have guaranteed rights to freedom of speech, without fear of consequence. It is illegal for any company to take back a product you have paid for. That is basically theft. When they do it because of a customer voicing an opinion, they are also violating our constitutional rights, a federal law. Even though I like the functionality of HRD and it's logbook, I will study and find a new alternative. After reading all of this, I too refuse to support these bastards. I see an alarming trend in our hobby that I don't see so much in others; There are several companies that are behaving like HRD. LDG tuners is another one. I received a brand new unit with a manufacturing quality control defect. I went to the public support forums on Yahoo Groups and noticed another person had the same issue. I posted that this is what happened to my unit also, so they must be missing something in manufacturing inspection. Suddenly, I was banned from the groups. I received an email from Dwayne at LDG disagreeing with my post. When I tried to reply and inquire what was going on, I found that my email was blacklisted also. Great customer support. I paid money, had an immediate problem on receipt of the shipment, and was banned for talking about it. If that is how LDG, or HRD for that fact, think they will find happy paying customers, well, SCREW THEM! They deserve to die, which makes room for new vendors with better ethics. I will watch this thread for suggestions on new logging programs. What I liked about HRD logbook was the ability to upload to almost every online log, including LOTW, QRZ.com, and eQSL.cc Hopefully one of the other logging programs can do that also. Then I can switch and flip the birdie at HRD Cheers, Neal N6YFM
|
|
|
|
locked
Re: : HRD V6 Logging abandonment - A brief explanation.
Bruce,
<< Oh, I thought it was just a technical issue you had with the HRD software Laurie, but it is obviously it is more a personal issue.>>
Judging by my run in with HRD, I knew it would not be anything else but an issue with the company/its owners. You should spot my posting in the ‘other’ HRD thread with more info.
I would not use HRD for free.
73 de Guy G4DWV/4X1LT
|
|
|
|
locked
Re: HRD V6 Logging abandonment - A brief explanation.
JTAlert dropping support for HRD V6 hits me hard. I have used both programs
almost from day one and the operation of both is totally transparent to my hamming activities. They are there and provide the functionality that allows me to enjoy ham radio more fully. Having been a long-time user of both software sets and peripherally dealing with said developers, my decision will be to abandon HRD and look elsewhere for WSJT logging programs. At this point I do not plan to renew my HRD support (never been as helpful as the HRD forum, anyway). Guess I will be exploring DX Labs and similar programs. Great opportunity for a new start-up outfit to "fill the gap". Laurie - keep on with your excellent support and development process. You provide a great service to the ham radio community and are a shining example of amateur radio spirit. __________ 73, Jim - N4ST From: HamApps@yahoogroups.com.au [mailto:HamApps@yahoogroups.com.au] Sent: Thursday, December 29, 2016 15:32 To: HamApps@yahoogroups.com.au Subject: [HamApps] HRD V6 Logging abandonment - A brief explanation. After some "soul-searching", I now feel I owe the community an explanation, even if brief, regarding my decision to abandon HRD V6 logging support in JTAlert, especially to those users directly affected by this decision. "Bottom-Line", I don't want myself or my software to have any sort of association with HRDLLC the company, their policies or their products. This decision was a long time coming. The draft for the announcement had been sitting in my email draft folder for over 12 months. I came close to making the announcement on two other occasions in that time, but chose to "back-off", primarily because I knew this would affect a large number of JTAlert users and I felt uncomfortable with that. The "die was cast" when HRDLLC released HRD ver 6.3.0.435 in October 2015. That release contained malicious code that deliberately shutdown JTAlert on a users PC without warning or message to the user that HRD had performed this unauthorised act. Details of this are publicly available within this groups message archives. There have been several other events and interactions with HRDLLC over that time that are not publicly known, contributing to this decision, and I will not be discussing them here or privately. While the association with HRDLLC was simply that my software had a feature that extended the functionality of HRD in providing a JT65/JT9 logging bridge, I am no longer comfortable supporting (by association) HRDLLC the Company, their policies or their products. Again, I sincerely apologise to the affected HRD users. de Laurie VK3AMA
|
|
|
|
locked
Re: : Announcement: Next release of JTAlert (2.9.0) will no logger s
Hasan,
<< Amen..Laurie doesn't owe us a darn thing. He has provided a wonderful tool With all due respect, Laurie does not seem to be the type of freeware developer that has the attitude of many, viz “if you don’t like it you can sod off”. I would suggest that you keep such helpful comments to yourself. I am sure laurie can speak for himself should he feel the need, and a lot more politely at that.
73 de Guy G4DWV/4X1LT
|
|
|
|
locked
Re: : Announcement: Next release of JTAlert (2.9.0) will no logger suppo
Hi,
I have got an even better story for you on this topic. I have been an amateur radio operator for over 41 years.
I have been off work ill for nearly 2 years (over 22 out of the past 24 months). I gave a lot more detail than that. Basically, I am a dentist and have had four back surgeries as well as osteomyelitis which almost saw me off. A side effect of osteomyelitis is extreme fatigue.
I asked for a discount on that basis and was offered a 15% discount. A very short time later I noticed that my trial licence would no longer work. It had been cancelled by their support worker on the basis that he was disabled too and could work. A further ‘appeal’ email was ignored. I managed to get the personal email address of one of the owners, and all he would do is re-instate the offer. AFAIAA, there is only one member of support staff so would not have bought a licence on the basis that I would have to deal with that chap again and do not wish to do business with a company that can cripple the software on a whim. I would not touch HRD for free.
A PDF of the ticket is here http://www.g4dwv.co.uk/hrd/. All of the things that were “quoted” were done so completely out of context.
Also, that chap must have thought he was able to do what he did. I cannot believe that the owners were unaware of this as anybody so treated would complain to them.
TBH, with the sort of people that are behind HRD, Laurie is well shut of them (as we say in the North of England).
Happy New Year es 73,
Guy G4DWV/4X1LT
|
|
|
|
locked
Re: Announcement: Next release of JTAlert (2.9.0) will no logger support HRD V6 Logging.
Dan Malcolm <dmalcolm24@...>
Thanks Tom. I am working with it. Just got it installed and imported my log. It’s still new to me as is Log4OM, but so far I like the latter a bit better. However, both are still new to me, so I’m giving both some more time.
I have to say thanks to all who responded to my request for advice. It has been very helpful.
I’d like to wish all of the list members a happy and prosperous new year.
_____________________________ Dan Malcolm CFI/II K4SHQ
From: HamApps@... [mailto:HamApps@...]
Sent: Friday, December 30, 2016 8:04 AM To: HamApps@... Subject: Re: [HamApps] Announcement: Next release of JTAlert (2.9.0) will no logger support HRD V6 Logging.
Give DXLabs a try and join the Yahoo group. Work with it a little and I think you will be pleased. 73, Tom - KQ5S
On Fri, Dec 30, 2016 at 7:49 AM, 'Dan Malcolm' dmalcolm24@... [HamApps] <HamApps@...> wrote:
|
|
|
|
locked
Re: Announcement: Next release of JTAlert (2.9.0) will no logger support HRD V6 Logging.
Tom <nineback@...>
Give DXLabs a try and join the Yahoo group. Work with it a little and I think you will be pleased. 73, Tom - KQ5S
On Fri, Dec 30, 2016 at 7:49 AM, 'Dan Malcolm' dmalcolm24@... [HamApps] <HamApps@...> wrote:
|
|
|
|
locked
Re: Announcement: Next release of JTAlert (2.9.0) will no logger support HRD V6 Logging.
Dan Malcolm <dmalcolm24@...>
Charlie, Thanks for the offer. I should perhaps clarify. While I have done a lot of work with Access, the vast majority of it is using PHP against an Access database. I do have one application I wrote years ago in Access VBA but that’s all. Since you have gotten this far with your application, you may be better suited to coding a third party data transfer application.
For me, I really do like HRD. But HRDLLC folks have gotten on my nerves more than once. I am ready to use something else. I am currently trying Log4OM, and I am also going to try DXKeeper. I loaded up ACLog but it wouldn’t allow me to play more with it due to an expired trial some months ago. I am not opposed to paying for it, but I want to make sure it fits my needs first. Not their fault but there it is. My efforts at least initially will be to change my summary app to work with whatever log program I settle on.
Good luck and Happy New Year Charlie (good name – Charlie was also my dad’s name).
_____________________________ Dan Malcolm CFI/II K4SHQ
From: HamApps@... [mailto:HamApps@...]
Sent: Friday, December 30, 2016 5:12 AM To: HamApps@... Subject: RE: [HamApps] Announcement: Next release of JTAlert (2.9.0) will no logger support HRD V6 Logging.
Dan I have written a custom front end for HRD (database version 5.24.0.38) for the worked all Britain logging. It is specific to my needs but depending on what is needed could send you the code for ‘manipulation’ Written in VBA, it logs contacts from the entered data. The HRD database is basically a flat file and breaks many data design rules (I am a former data / database manager), but that simplifies the insert process. Not saying it is a superb bit of coding (it is not) but it may save ‘reinventing the wheel’. I am still using the free version of HRD as it still does all I want and after a run-in with HRDLLC myself will never subscribe.
I have a part completed video on the front end I use which I could also post if anybody wants to see the functionality.
If people want to use HRD you could still interface through ADIF or downgrade to version 5 which has NEVER failed on me.
From: HamApps@... [mailto:HamApps@...]
Hmmm maybe. I’ve done a good deal of work (before retirement) with MS Access and just a little with SQL. Since Access is queried by SQL I am familiar with that language, but not an expert. I’ll give it some thought, but no promises.
_____________________________ Dan Malcolm CFI/II K4SHQ
From: HamApps@... [mailto:HamApps@...]
Somebody could write a companion application that takes the JTAlert log message and relays to other loggers that aren't directly supported. Sounds like you may have the credentials to do that.
de Mike W9MDB
From: "'Dan Malcolm' dmalcolm24@... [HamApps]" <HamApps@...>
Laurie, No discussion necessary. Your decision has however created a real problem for me. I love JTAlert, but I also have some software I’ve written around HRD Logbook. My problem is not your problem however. I just assume your reasons are valid. Now I have decisions of my own to make.
_____________________________ Dan Malcolm CFI/II K4SHQ
From: HamApps@... [mailto:HamApps@...]
To all JTAlert / HRD V6 users.
|
|
|
|
locked
Re: HRD V6 Logging abandonment - A brief explanation.
chas cartmel
Laurie You have my backing 100%. I have been subject to gross intrusion myself. When I stated that I could see no value added in upgrading from version 5 to version 6 one of their owners emailed me advising that as I was a Private pilot (past hobby) I could afford to buy their software. I responded that they had no right to tell me how to spend my money but was blocked on their forum.
Obnoxious is the word that comes to mind here.
I just wish more people would vote with their feet or wallets.
73 Charlie www.G4EST.me.uk Twitter:@ccartmel
From: HamApps@... [mailto:HamApps@...]
Sent: 29 December 2016 20:32 To: HamApps@... Subject: [HamApps] HRD V6 Logging abandonment - A brief explanation.
After some "soul-searching", I now feel I owe the community an explanation, even if brief, regarding my decision to abandon HRD V6 logging support in JTAlert, especially to those users directly affected by this decision.
|
|
|
|
locked
Re: Announcement: Next release of JTAlert (2.9.0) will no logger support HRD V6 Logging.
chas cartmel
Dan I have written a custom front end for HRD (database version 5.24.0.38) for the worked all Britain logging. It is specific to my needs but depending on what is needed could send you the code for ‘manipulation’ Written in VBA, it logs contacts from the entered data. The HRD database is basically a flat file and breaks many data design rules (I am a former data / database manager), but that simplifies the insert process. Not saying it is a superb bit of coding (it is not) but it may save ‘reinventing the wheel’. I am still using the free version of HRD as it still does all I want and after a run-in with HRDLLC myself will never subscribe.
I have a part completed video on the front end I use which I could also post if anybody wants to see the functionality.
If people want to use HRD you could still interface through ADIF or downgrade to version 5 which has NEVER failed on me.
73 Charlie www.G4EST.me.uk Twitter:@ccartmel
From: HamApps@... [mailto:HamApps@...]
Sent: 29 December 2016 17:11 To: HamApps@... Subject: RE: [HamApps] Announcement: Next release of JTAlert (2.9.0) will no logger support HRD V6 Logging.
Hmmm maybe. I’ve done a good deal of work (before retirement) with MS Access and just a little with SQL. Since Access is queried by SQL I am familiar with that language, but not an expert. I’ll give it some thought, but no promises.
_____________________________ Dan Malcolm CFI/II K4SHQ
From: HamApps@... [mailto:HamApps@...]
Somebody could write a companion application that takes the JTAlert log message and relays to other loggers that aren't directly supported. Sounds like you may have the credentials to do that.
de Mike W9MDB
From: "'Dan Malcolm' dmalcolm24@... [HamApps]" <HamApps@...>
Laurie, No discussion necessary. Your decision has however created a real problem for me. I love JTAlert, but I also have some software I’ve written around HRD Logbook. My problem is not your problem however. I just assume your reasons are valid. Now I have decisions of my own to make.
_____________________________ Dan Malcolm CFI/II K4SHQ
From: HamApps@... [mailto:HamApps@...]
To all JTAlert / HRD V6 users.
|
|
|
|
locked
Re: HRD V6 Logging abandonment - A brief explanation.
Laurie, VK3AMA <groups08@...>
On 30/12/2016 7:44 PM, Liz & Tony Buckland buckland@scorch.co.nz [HamApps] wrote:
Hi Laurie,Hi Tony, Sorry, Logger32 is not supported. I made a couple of attempts in the past, but the propriety format of the database used for its log requires the purchase a very expensive license from the database vendor, and then it is not practical as the engine doesn't support concurrent access to the data tables, the log is opened exclusively by Logger32 while it is running so JTAlert would not be able to run queries against the log even if a license was purchased. The DXLab suite is supported. DXKeeper was the first logger supported by JTAlert. There are several JTAlert functions that are unique to DXLab. It is what I use for my Logging/DX activities. I have been using it for at least a decade. The support by its author (Dave AA6YQ) is superb. You will never get an unanswered question from the Dave, regardless of how trivial or how often previously asked. DXKeeper, Log4om and ACLog are all good products and their respective authors all provide excellent end-user support. From a JTAlert perspective, all three are relatively easy to work with due to their use of industry standard and popular database formats which makes my coding activities working with their logs rather painless ;-) Cheers from across the ditch. de Laurie VK3AMA
|
|
|
|
locked
Re: HRD V6 Logging abandonment - A brief explanation.
Liz & Tony Buckland
Hi Laurie,
Firstly, many thanks for all your sterling work with JTAlert, it's a fantastic program and much appreciated. Secondly, if I ditch HRD for Logger32 would it work OK with JTAlert or would DXLog Suite be the better option? Thanks again. HNY to you and all our readers. 73 Tony ZL3HAM
|
|
|