7 replies to this topic

[AdamE]

Hello,
I'm developing an addin which I need to protect from copying attempts using the USB cable or another, so is there any way to do that?
Many thanks.

[flyingfisch]

I dont think there is. Maybe you could do a serial code?

[Forty-Two]

Hello,
I'm developing an addin which I need to protect from copying attempts using the USB cable or another, so is there any way to do that?
Many thanks.

Overwrite the USB code in the OS.

[helder7]

For other calculators there a way to block the transfer add-ins between 2 calcs (for exemple clock for prizm by ahelper is protected against transfer by serial cable), For ClassPad I do not know...i never tested classpad sdk

The best way, you can create a input box in int main() for write serial key, and then when users submit it this is compared with the serial predefined and if this 2 serials match, addin run, if not You can call a wrong serial message

If you have knowledge to make an add-in, I think it will be easy doing this

[scout]

submit it this is compared

With a disassembler, it is extremely trivial to make this comparison always return true.

Overwrite the USB code in the OS.

How does one do this?

[Forty-Two]

With a disassembler, it is extremely trivial to make this comparison always return true.



How does one do this?

1. Find the USB transfer code in the OS
2. Erase
3. Compute a new checksum
4. Transfer the new OS

Just make sure that you have a cable that works with the 2.5" jack, otherwise you will be unable to transfer a new OS to the calc if you screw up.

[MicroPro]

There is no built-in feature for this, sorry.

Overwrite the USB code in the OS.

This is what I call an "anti-solution" :-) How about writing an OS that only includes the written add-in and without transferring ability at all?

[scout]

How about writing an OS that only includes the written add-in and without transferring ability at all?

You said that in jest, but that might not be a bad idea at all for the OP!