Easy Language allows you to use your program only once on a computer

The following is the source code:

The subroutine Startup Window is created.

If (take the text registration entry ( root class, "tsctlt spesxca", a")).

End () otherwise.

Write the registration entry (root class, "tsctlt spesxca", a") if it ends.

Version 2 Assembly Window Assembly 1

Assembly variables, event handles, integer.

The subroutine Startup Window is created.

If open Event Sync Object (2031619, False, "myappname") 0).' "myappname"It can be any text, but it's best to be longer to ensure that it doesn't conflict with the names of other event objects already in the system.

Destroy () otherwise.

If it ends. The subroutine Startup Window will be destroyed.

Close the synchronization event object (event handle).

DLLs: Version 2

dll command to create an event synchronization object, integer, ,"createeventa"

Parameter lpeventattributes, integer type.

Parameter bmanualreset, logical.

Parameter binitialstate, logical.

Parameter lpname, textual.

The dll command opens the event synchronization object, integer, ,"openeventa"

Parameter dwdesiredaccess, integer type.

Parameter binherithandle, logical.

Parameter lpname, textual.

dll command to turn off the synchronization event object, integer, ,"closehandle"

Parameter hobject, integer.

Go to the official forums and find a suicide routine. The program automatically deletes itself when it exits. How about this.

Leave a mark on the registry.

Take the machine code, one machine one machine code, and then add a judgment or something.

.Version 2The subroutine Startup Window is created.

If true (the file exists ("c:

If true (read the configuration item ("c: ,x", x1", to text (take the hard disk feature word ()1)).

Destroy () if it really ends.

If it's really over.

The subroutine Startup Window is activated for the first time.

Write the CI item ("c: ,x", x1", to text (take the hard disk feature word ()).

The subroutine Startup Window will be destroyed.

Write the CI item ("c: ,x", x1", to text (take the hard disk feature word ()1)).

Delete the file (fetch the running directory () fetch the executable file name ()exe)<).

Is it not possible to run it repeatedly, or it will be automatically deleted after running it once? Prohibition of repeated runs() is written after the window is created and deleted after the run can be deleted after the window will be destroyed, add a delete self, or delete after restarting.

I'll have a simple method, it's relatively rudimentary, don't ask me if it's more advanced, I don't understand, I'm also a novice.

You first insert a new dll command, it's called api find window, the return value is an integer, the dll library file name, the corresponding name is findwindowa, pay attention to the case, there are two parameters, both are textual, the first one is called the window class name, the second is called the window text, you just like this after the new command is completed, add the following ** in the startup window after the creation is completed.

Version 2 Subroutine Startup Subroutine, Integer.

Judgment Start (0≠ API lookup window ("wtwindow", test")).

End () Default load ( Startup window, , true).

End of judgment. Return (0).

Sorry to say a little less, not to add ** to the startup window created.

Instead, add it to the starter, you select Start with the starter in the system configuration, and then add ** to the starter.

.Version 2

Support for the library EAPI

Assemblies Window Assembly 1

Number of assembly variables, integer.

The subroutine Startup Window is created.

Local variables Process, Process Info, ,"0"

The local variable i, an integer.

Processes Fetch the list of system processes ().

The first of the counting cycle (take the number of array members (process), i).If true (i 1).

If true (process [i].).Process Name Take the name of the execution file () Quantity Quantity 1

If it's really over.

If it's really over.

Counting cycle tail ().

If true (quantity 2).

Infobox ("The program already exists. No need to repeat the run! ",0, )End ()

If it's really over.

You can get the ID number of this computer hard disk, bind it when it runs, and once you have it, you can't run it again.

.Version 2

Support library shells

Assemblies Window Assembly 1

The subroutine Startup Window is created.

Local variable wjh

Local variable cs

It is possible to write the number of runs in multiple places and compare them with each other, such as writing to the registry and appending information to the program at the same time.

If the file exists (take a specific directory (10) false).

Copy the file (take a specific directory (10) and take a specific directory (10).)

Otherwise. If it ends.

wjh opens the file (fetch a specific directory (10).)

Move the read/write location (wjh, 1, fetch file length (wjh) 1).

cs to numeric value (to text (read into the byte set (wjh, 1))).

If (CS 9).

Infobox ("The trial has expired, please sign up!") ", warning icon, "Registration information:")

End () otherwise move to the end of file (wjh).

Title: Number of times limit routine: Number of runs: "To text (cs) Number of times remaining:" To text (9 cs).

Insert a byte set (wjh, to a byte set (to text (cs 1))).

Close File (WJH).

You can set the number of times you use yourself, I only provide ideas, you can see and study for yourself!

You can use the hard disk serial number as the keyword to take a few digits in the md5 value as the system preset registration code, the user registration code can be saved in the configuration file, and the registration code value of the configuration file can be read first when loading the program and the registration code of the system is compared, briefly as follows:

Can give you an idea:

Add a field to the database that records login information.

After the customer logs in, write to the database every once in a while, write to the current time, so that when logging in, you can verify whether the same customer login has exceeded the interval, and if not, you cannot log in.

The solutions are all figured out by people, and it depends on whether you make full use of them.

I have a solution, but it's a bit of trouble.

1. Put the server and customer components on the startup window, the server port = 02, when running, the customer connects to the server (you can use the domain name), the connected port 13, if the connection is successful, it means that someone has logged in. If the connection fails, update the IP address of the domain name to the local public IP address.

This way, when you log in to someone else, they can't log in.

We hope you will adopt it!

I used to write the chat software to do this: use an array to record the login account name, including the customer handle, used to judge the disconnection of the login record account, when an account wants to log in to detect whether there is this account in the array, if there is a duplicate login command and disconnect the client! It's simple.

Is it so simple to ask? I personally feel that the command of delay is not used, because if you use delay, this ten-second realm seems to be inoperable... My idea is to use a clock,Write a ten seconds in,The clock starts after the startup window is created,The clock event is written to load the window 1 and then the clock cycle is changed to 0 so that ten seconds your startup window can also be operated and will not be a suspended death phenomenon (other methods think about it yourself) If you prohibit multiple runs, you need to call the api, If you are idle and troublesome, you can find the relevant modules, many modules should have this function,createeventa:

Create an event object ,,, look it up specifically: create a new handle for an already named event object. closehandle:

Close a kernel object.

Click once to add the number once, then write to the file or registry, and when this number is equal to 3, the lock screen will pop up!