I have seen both approaches protection and not. The only direct threat
is from someone that clones the full product. Protected or not these
folks will do it. Secondary protections are the only defence with these
guys. Simple undocumented features that can identify the code was
yours. Or a features that extends the amount of time it takes before
the software protection becomes apparent.

My personal favourite was an box that had door opening detection
that made the unit apparently fail until 24 hours after the box was
closed. This was part of a anticlone measure. The most interesting
door open detections is using an led as a light sensor.

w..





Andre Abelian wrote:

> This is my second company I worked in last 2 years that they do not
> enable CP at all and once I asked them about it the answer was
> if some is smart enough to break the code protection then should
> be able to make entire project from the scratch.
> Then I told them why do you lock your car doors? any way
> I have to go.
>
> Andre


-- 
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist