HRD 6 finally released

[AE1PT]

Get it while you can at $80. It jumps to $100 on Monday...

The sycophants and apologists are licking each other's backsides over in the swamp about it.

[XE1/N5AL]

I sure hope strong copy protection is built into program, lest some of the more "thrifty" hams will turn the release into a pirate-fest.

[KA9MOT]

Get it while you can at $80. It jumps to $100 on Monday...

The sycophants and apologists are licking each other's backsides over in the swamp about it.

And you did such a nice job of pointing the short comings out. I swear Pat, I wish I were as eloquent as you. You've become my new hero. I think old Dr. Bob got his panties all knotted up.

http://forums.qrz.com/showthread.php...24#post2768524

When you get it up and running, let us know how it is. I looked on YouTube for some videos and with the little I could find it looks like a warmed over version 5.

[KA9MOT]

I sure hope strong copy protection is built into program, lest some of the more "thrifty" hams will turn the release into a pirate-fest.

Do you honestly believe folks will need to steal it? Is it worth stealing? I don't think it's worth paying for, why go to the trouble of stealing it?

[n6hcm]

is the old version (HRD 5) being kept as the "freeware" version? i don't see any reason to pay $80 (or $100) for what is essentially HRD5 with a few more features

[N8YX]

It's time for an enterprising group of hams/software engineers to write a replacement...a portable replacement which can run on multiple platforms. Make it Java or Python based, modular and extensible: You install only those features which you need.

Legacy (true TTY) support for RTTY terminals such as the ST6000, ST8000 and anything else with an RS232 port attached.

Standardize the device driver modules which feed the main program itself - in classes of, say: rigs, rotors, TTY, TNC, network and so forth...document the upper level API and let the community at large get to work.

I can write drivers for a few rigs which I have on hand as well as the Timewave DSP599 (native TTY), KAM Plus, KPC3, KPC9612 and Universal M7000 (all in host mode).

[N8YX]

And you did such a nice job of pointing the short comings out. I swear Pat, I wish I were as eloquent as you. You've become my new hero. I think old Dr. Bob got his panties all knotted up.

Let's take one comment into consideration:

"A lot of the controversy here has to do with what honestly are amateurish marketing methodologies."

A lot more of the controversy has to do with the apparently non-existent product support. As in: "Stupid user ought to be able to figure things out themselves."

I guarantee that if the support engineers of any number of SaaS/software systems vendors whom I'm familiar with were to express a similar attitude towards their major customers, they would be out on their asses at the end of the week...if not the day.

[KC2UGV]

It's time for an enterprising group of hams/software engineers to write a replacement...a portable replacement which can run on multiple platforms. Make it Java or Python based, modular and extensible: You install only those features which you need.

Legacy (true TTY) support for RTTY terminals such as the ST6000, ST8000 and anything else with an RS232 port attached.

Standardize the device driver modules which feed the main program itself - in classes of, say: rigs, rotors, TTY, TNC, network and so forth...document the upper level API and let the community at large get to work.

I can write drivers for a few rigs which I have on hand as well as the Timewave DSP599 (native TTY), KAM Plus, KPC3, KPC9612 and Universal M7000 (all in host mode).

You do realize, FLDigi is open source, and includes most of what you are asking for, right?

[W4GPL]

It's time for an enterprising group of hams/software engineers to write a replacement...a portable replacement which can run on multiple platforms. Make it Java or Python based, modular and extensible: You install only those features which you need.

Legacy (true TTY) support for RTTY terminals such as the ST6000, ST8000 and anything else with an RS232 port attached.

Standardize the device driver modules which feed the main program itself - in classes of, say: rigs, rotors, TTY, TNC, network and so forth...document the upper level API and let the community at large get to work.

I can write drivers for a few rigs which I have on hand as well as the Timewave DSP599 (native TTY), KAM Plus, KPC3, KPC9612 and Universal M7000 (all in host mode).

Fldigi isn't too shabby.. and the hamlib database is growing everyday.

[N8YX]

You do realize, FLDigi is open source, and includes most of what you are asking for, right?

Fldigi isn't too shabby.. and the hamlib database is growing everyday.

I just rebuilt the shack controller computer - dual-boot with Linux Mint 14. Once I get the interfaces proofed under XP and all is up and running I'll look into FLDigi and see what it has to offer.

Right now there's a requirement for a Signalink USB interface, a Timewave DSP599 (RS232; native Baudot TX/RX), an Icom CT17 (RS232) and USB CAT cable support for the nearest FT-980. I have two serial and two USB ports on the rear of the Shuttle Micro which is going to be used for the purpose so there should be enough I/O on hand.

More on the shack PC in the Computers area. Off to start another thread...