My understanding from various sources is that Sorcerer also had a reverse
engineered Pactor decoder, and that got the developer in trouble with SCS.
Matthew Pitts
N8OHU
On August 16, 2016 3:54:15 PM EDT, Ron Kolarik <rkolarik@neb.rr.com> wrote:
>Be very careful with Sorcerer, it's a cracked commercial product and
>not
>always malware
>free. It will decode callsigns of P2-3 but the message remains hidden.
>I
>think one of the
>Hoka products works on P3 but the price is more than an SCS modem. I
>don't have either,
>had a borrowed P3 modem when I was chasing something, caught but no
>official response to
>the complaint.
>
>Ron K0IDT
>
>
>On 8/16/2016 2:42 PM, Michael Adams wrote:
>> Pactor 3 and 4 use Pactor 1 for the initial call; moving to faster
>waveforms once the modems negotiate capabilities, etc. If you catch
>the initial call, you should be able to decode it using free
>software....although luck, practice working with recordings, and/or
>obsessive watching and waiting might be required to make that happen.
>>
>> Winlink Express' Pactor module has the capability to identify in
>Pactor 1 FEC (freely decodable) at the end of a connection, but it is a
>user-selectable option. The practice is discouraged in some
>non-amateur uses of Winlink, and I wouldn't be surprised if most
>amateur users don't bother to check the box.
>>
>> I understand that there is one hobbyist program out there that claims
>to be able to decode Pactor 3 (Sorcerer; haven't tried it, and don't
>know much more beyond that it exists)
>>
>
>_______________________________________________
>RTTY mailing list
>RTTY@contesting.com
>http://lists.contesting.com/mailman/listinfo/rtty
_______________________________________________
RTTY mailing list
RTTY@contesting.com
http://lists.contesting.com/mailman/listinfo/rtty
|