>>>"...I guess it time to plant some bomb in my code. :)...."
>>
>>Be carefull how you do this - you can put some code in there to disable your application - but be sure it doesnt do anything else to the computer or destroy any data - otherwise it could cause you a legal problem.
>
>Thanks for the warning.
>Haven't done it yet... don't know if I will because you may be right, it may cause more trouble then it's worth. But you do bring up an interesting point.
>If someone uses a PIRATED software and that software causes them problems that affect their business, who's fault is it? My logic says tough sh!t to the illegal user. They should get a legal copy.

I don't know if you could still be blamed if someone was using a pirated version of your software, but my gut says yes. I recall reading a story about a guy who injured himself while robbing a house, and sucussfully sued the owner of the house! Plus - why take the risk? I mean what if some bozo at a hosptial installs it and next thing you know a bunch of machines at the hospital have problems and someone dies as a result of it?
I've done the 'bomb' thing before, but what it did was just disable our software. Here's a good example - we had some software that did auto-insurance pricing - people leased the software and we went updates out every couple of weeks (rates change a lot). Anyway problem was that you had a few idiots who wouldn't pay the monthly fee. Ok - so a few months go by and they don't pay - so I had a little built in bomb - I would call them up - act like a customer wanting a rate quote - so for a certain car, certain age, certian zip-code, etc - if all those details were just right...then there machine would beep. (I could even hear the beep over the phone). Well then they've got 3 more quotes they can run - then poooof! Only thing the app would do after that is display a message saying to call us...hehe. Funny but they always seemed to call right away. I'd send them a new disk and they'd be back in action - no lost data or anything.