How to make trial programs which can keep trial information after reinstalling windows

Question

1.44/5 (2 votes)

See more:

Hi! I'm always thank you for your help.

Well, I wanna make a program which can work only few days! So, I've searched method of making trial programs on Internet and have made it.

Trial Information which contain limited using days is written on MBR's code area(Of course error message area in MBR's code area).

With this, program can keep it's trial information after it has been re-installed. It's well done, I think. But it has a problem!

When user reinstall Windows, trial information in MBR's code area is erased and users can use program when it's date is expired!

It's very serious for me! Please help me.

Could anybody know how to keep trial information after windows has been reinstalled?
Hope your answers.

Posted 28-Aug-14 22:12pm

WuRunZhe

Add a Solution

Comments

Mehdi Gholam 29-Aug-14 4:21am

Messing with the MBR is *not recommended*

WuRunZhe 29-Aug-14 4:23am

Yes, you're right. Messing with MBR is very dangerous.
However, when user reinstall Windows, MBR code area is reinstalled also. So trial information on it has been removed.

Mehdi Gholam 29-Aug-14 4:35am

By definition if someone has installed a product on one machine then they have the right to reinstall and use it on that same machine regardless of reformatting that computer.

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

OriginalGriff · Answer 1 · 2014-08-28T22:27:00

Solution 1

Don't even try: writing anything to the MBR is a poor idea as it is very likely to get you tagged as a virus.

And the MBR is not "Protectable" over operating system installs - any OS install will overwrite the MBR as it does not know what the previous OS was - and it doesn't care.

If you want a "fool proof" system (or close to, any protection can be defeated) you are looking at connecting to a computer under your control and yours only: connection to a server via the internet and approve / disapprove there.

But frankly, I wouldn't spend too much time on this: compare the value of your time with the amount of sales you won't get if there is no protection and it doesn't take long before you are costing yourself money to add it!

And remember: if your app is "Popular" or "expensive" then it's more of a target for hackers: Adobe spend a lot of money easy year protecting Photoshop - and "cracked" version appear on the torrent sites pretty much the same day as they release a new version...

Posted 28-Aug-14 22:27pm

OriginalGriff

Comments

WuRunZhe 29-Aug-14 4:34am

Thank you for advice!
I also know online approve is the best way. But my program is used in offline states so it's not fix answers. Thank you.

WuRunZhe 29-Aug-14 4:46am

Well, What about Storing trial information on the last raw sector on Hard Disk?

OriginalGriff 29-Aug-14 4:53am

1) A format will destroy it.
2) How do you know it isn't in use?

WuRunZhe 29-Aug-14 4:58am

Well, original format didn't erase every sectors, it only rewrite FAT table.

"What about Storing trial information on the last raw sector on Hard Disk", last raw sector means the final sector of the hard disk.

I think it could be written before user store data full of hard disk.

OriginalGriff 29-Aug-14 5:01am

A "Quick format" only re-writes the FAT.
A full format checks eveything.

And a defrag can move data around...

WuRunZhe 29-Aug-14 5:15am

Yes, you're right.
So what is the answer of question? What is your opinion?

OriginalGriff 29-Aug-14 5:39am

Sometimes, you have to put your hands up and say "That can't be done" and move on.
This is one of those times.
Even if you could write anywhere you wanted on the disk, you can't prevent people from "getting round it" - and it isn't difficult to do even with a re-install of anything: a VM can be "reset" in seconds and it's "hard drive" reverted to before the install. My local public Library has PC that do that every single time they are booked by a new user! :laugh:

Seriously: think about how much time you have spent on this already, and how much money it will save you in terms of people who would buy your product if they couldn't bypass the security instead of looking at similar products. It generally isn't many individuals, and you have to ensure that the cost of adding the protection doesn't exceed the profit you would have made from them and them only. And when you factor in any possible inconvenience to legitimate users, you will almost certainly lose money by trying to protect your software too vigorously. (There are companies I will not use because their protection caused me too much hassle as a legitimate user).

I'd just add a licence file in a GUID folder and check that:
http://www.codeproject.com/Tips/370232/Where-should-I-store-my-data
Don't make the file name obvious and it'll cover the greedy without costing you too much to implement.