Demo simple writing of data in the EXE itself.

These data are in the area of initialized variables, where you can book almost as much space as you want.



Established from the following remarks:

- You can rename the EXE current (and it does not care)

- Can not write in the current file name or ANY (Windows XP uses a "pointer" on the disk and not the name, to block access)

- You can make a copy of the EXE current (therefore changeable writing)



So:

1 - BAK is renamed EXE (we still can not write in this BAK)

2 - it makes a copy of BAK in EXE (you can write in this EXE !!!!)

3 - we write everything you want in this EXE (he will be launched next call!)

4 - it erases any BAK (in fact FormCreate ())



Written in Delphi 5 Pro.

Tested Windows XP.



TESTING OUT OF IDE (of course since it resets the zone by creating a new EXE)

-Demo simple writing of data in the EXE itself.

These data are in the area of initialized variables, where you can book almost as much space as you want.



Established from the following remarks:

　- You can rename the EXE current (and it does not care)

　- Can not write in the current file name or ANY (Windows XP uses a "pointer" on the disk and not the name, to block access)

　- You can make a copy of the EXE current (therefore changeable writing)



So:

1 - BAK is renamed EXE (we still can not write in this BAK)

2 - it makes a copy of BAK in EXE (you can write in this EXE !!!!)

3 - we write everything you want in this EXE (he will be launched next call!)

4 - it erases any BAK (in fact FormCreate ())



Written in Delphi 5 Pro.

Tested Windows XP.

　　　　　　　　　　　　　　　　　　　

　　　　 TESTING OUT OF IDE (of course since it resets the zone by creating a new EXE)