>We have seen a number of statements posted in recent days, whose authors devote their precious time and
>energy to spreading twisted and untrue information on Elbox and our products. We are presenting here our
>official position in reference to their falsification of the truth."
OK, so this letter basically says that the truth is that, indeed there was such RDB trashing code in their driver and pci library. Isn't this what the previous posters were saying??
Now, sure, Elbox has a right to protect their work. But there is no such thing as fault-proof software, especially when run on an unprotected OS. Some non-hack, non-virus code from someone else could have a weird bug that just happens to jump into this piracy protection code and set it off. Don't say it's impossible, as that is wrong. Unlikely perhaps, but NOT _impossible_. Even without any mischievous intent involved. Nothing even needs to hack into or decrypt the driver file, as it gets decrypted into RAM in order to function, as my 68K does not have a decryption engine built into it, code must be decrypted before trying to run.
So, there is fully decrypted driver code laying around in RAM that can accidentally be jumped into. We'd hope a developer would test for bugs, and fix them before release, but sometimes crap happens. What if this same developer was testing his new code on a machine equipped with this USB card that he paid for and is legit licensed for, but his new code has a bug, and during the debug phase it goes off and frags his hard drive? Was he lucky enough to have backed up his RDBs? Is it really that easy to recreate the RDSK sector without trashing other RDB data? I dunno, but I've found disk recovery is never an easy 5 minute job. This innocent software developer could struggle for quite a while trying to figure out why his program that may not even access disk data is trashing his hard drive.
Such destructive code cannot be fault-proof in AmigaOS. This makes it even more of a bad idea than it would be on a memory protected OS. It's just plain wrong, even if it would rarely go bad when not intended to do so. Please, Elbox, find non-destructive ways to deal with piracy, as this most certainly can _possibly_ hurt legitimate users.