Email: Password: Remember Me | Create Account (Free)

Back to Subject List

Old thread has been locked -- no new posts accepted in this thread
???
07/31/01 09:14
Read: times


 
#13686 - RE: The problem with the Triscend E5
Thanks to Steven Knapp for his interesting, clear and concise (yes, very clear and concise) description of the IP protection methods. I could not stop reading it. And I have learnt a lot.
But this information reveals the tricks to the copiers :-)

After reading S.K.'s post I think that the best protection for many applications is the use of an auxiliary non-readable device.

An additional idea: Writting the SW in a high level language makes the dissassembled code a little difficult to understand. Therefore the copier can easily make identical copies but not improvements or further development.

Alfredo del Rio.


List of 6 messages in thread
TopicAuthorDate
The problem with the Triscend E5            01/01/70 00:00      
RE: The problem with the Triscend E5            01/01/70 00:00      
RE: The problem with the Triscend E5            01/01/70 00:00      
RE: The problem with the Triscend E5            01/01/70 00:00      
RE: The problem with the Triscend E5            01/01/70 00:00      
RE: The problem with the Triscend E5            01/01/70 00:00      

Back to Subject List