Karl Larsen was manually quoted as saying:
>       Hi Nate. Another example is the DX Cluster. A Ham made his money
> selling the software with the buyer's callsign inbedded into the binary.
> That way no sharing software. Well after a few years it stopped selling so
> he announced it will no longer be supported. But no source code. Nothing. 

But, the protocol for DXCluster was included in the manual that came with the
software allowing clones to be written, and anyway its an easy protocol to
reverse engineer. A few hours watching a DXCluster backbone link will
provide enough protocol to write a basic cluster yourself. That is why I included
DXCluster in my list of public protocols.

>       Happy to say France came up and re-wrote the DX Cluster code for
> both DOS and Linux. Germany came up with Clix for Linux. But again the
> source code is not available from France. Just a binary. Wonder what will
> happen when F6FBB dies or looses interest?

Firstly F6FBB didn't write DXNet, he just ported it to Linux.

CLX (not Clix) is without source code and should be registered before use.

Secondly there is source code for (a) Clusse, and (b) DX Spider. So running an
open source DX Cluster is quite possible if that is what you wish. I have no
problem with not having source for cluster software since the protocol is in the
public domain. Most people are complaining about not having the protocol in the
first place making the writing of an open source version difficult, if not
impossible.

Jonathan  HB9/G4KLX

Reply via email to