How can I successfully write my stand-alone application made by MMF2 to CD so that it will be playable on all machines in a way that the users wont be able to copy the CD to hard disk or to copy the CD itself? I know that there are some 3rd party softwares out there to do so but which one is compatible in my case? anyone have experience in this regard?
I can't understand very well your ask (sorry, my english is poor :/). Do you like create a application that runs only in origin CD, but not runs in other CD or when copied in hard disk?
Maybe that will work too. but what I asked was that I want to make the CD locked for example when you open the content of CD and you select something and then right click>copy to drive c,d,.. you get error can not copy. same when you put empty writable CD to your CD-writer drive to copy the original CD you should get error: can not write CD. But if it is impossible, it's ok if they can copy it as long as it wont play or run.
so what you are asking for is DRM protection.
Yes, you have something in mind?
Ah... Well, I don't know if is possible using only MMFusion, but create an application that runs only in a specific CD is possible. Maybe not in MMF2, because the example that I had was for the 1.5 :/
theres no special trick or physical way you can stop someone from copying your CD's using only the CD-rom itself. CD's are just memory, a long string of bits, and you can copy and paste that memory all you want and set it up as a virtual cd to emulate a drive, and a computer can't know the difference.
There are forms of DRM you can use to lock down your application to hinder piracy, like using CD-keys that would be shipped alongside or on the CD, which would contact a central server and restrict installation usage, and these are usually sufficient to stop most people from bothering, so long as its really a server-based approach- using an offline "verify on startup" cdkey that doesn't restrict itself is totally pointless and people will just post the cdkeys with the image files, and even a secure server verifying product keys is able to be defeated, whether through abuse of limitations or cryptographic attack- and every single form of DRM you could use has the drawback of being a hindrance to the legitimate user, whether its pulling a false positive and preventing them from using your software, or just being a big burden of typing in a key, or that key being lost, or so on.
Thank you guys, I'll see what I can do.
Posting Permissions
Reply With Quote