Waris / CDM - out of band - CP Tool vs simple hex edit?
Posted: Sat Sep 02, 2017 9:35 am
I have previously used a hex editor to extend the band edges of my Maxtrac and other radios.
With the Waris / CDM line, the old Batlabs pages says to hex edit the original GP300.exe file by finding the original band edge in hex and then replacing with it the extended band edge and then to make sure that that the checksum is correct.
The various Batboard postings recommend using the codeplug tool (or cptool).
Is the cptool doing something different? I think it might involve using a default (non-original) CP so the tuning values are not correct (tuning values are held in the codeplug)...so you have to save the original tuning values and then upload them.
Do I need to use the cptool because extending the band edge in a CDM/Waris involves more than just changing to a new band edge in hex (so Batlabs is wrong)? Or can I just edit the original GP300.exe file like it says on Batlabs?
With the Waris / CDM line, the old Batlabs pages says to hex edit the original GP300.exe file by finding the original band edge in hex and then replacing with it the extended band edge and then to make sure that that the checksum is correct.
The various Batboard postings recommend using the codeplug tool (or cptool).
Is the cptool doing something different? I think it might involve using a default (non-original) CP so the tuning values are not correct (tuning values are held in the codeplug)...so you have to save the original tuning values and then upload them.
Do I need to use the cptool because extending the band edge in a CDM/Waris involves more than just changing to a new band edge in hex (so Batlabs is wrong)? Or can I just edit the original GP300.exe file like it says on Batlabs?