Matthew Bevan wrote:
I have a resource editor -on my handheld- which can disassemble and
modify individual opcodes in both m68k ('code') and ARM ('armc')
compiled code. Insert a NOP here, change a branch instruction there,
and in some cases it would be trivially easy to bypass registration
systems. I've done this to my own applications. I was very
dis-heartened and have switched to having two branches of my code. A
limited "demo" version (where code really does not exist to perform
"registered" actions), and a fully registered version that cripples
itself when beamed.
Limiting your registration system to ARM would leave a large percentage
of PalmOS users who use PalmOS 4 (and even 3!) in the lurch. Is
limiting yourself to new devices worth it? If you rely upon other
PalmOS 5 features (new sound manager, other ARM code, etc.) then
nevermind.
thanks for the nice directions Matthew,
regards
Erico
--
For information on using the PalmSource Developer Forums, or to unsubscribe,
please see http://www.palmos.com/dev/support/forums/
