Onguard Error App Compiling error

[eldonfsr]

Hi I start to lear about Onguard but when compile the app send error and also don;t show codegenform...

[Soner]

Look at the error message:
"Invalid value for property.".

It means there is a property or properties it doesn't more exist in your compiler or lazarus like Ctl3D in Delphi.
Open the forms in lazarus, switch to formdesigner, it shows you which property it is. When the property is not essential then you can choose ignore and continue loading or cancel loading and solve the problem.

When the property was not essential and you loaded the form then you must change something on the form to save the new version. Then recompile it.

[Thaddy]

Are you compiling for 64 bit? Then you have a problem. A 64 bit version is known to be flawed.
Anyway, such old software is not really relevant anymore.
It is extremely easy to create a patch.
Basically the easiest way is to create a diff between full version and demo version and that works all the time:
Onguard does not leave out code....and where it tries to, the above circumvents this.
To a hacker, it is therefor useless. I used to use OllyDbg to determine what OnGuard does many moons ago and, for sure even the other possibilities are worthless.
Best way to circumvent this is simply to leave out code...(save file etc) and even then the patch option will work.

[wp]

Some forms of the OnGuard demos set the Font.Color to clText - this is not defined in Lazarus any more (maybe it once was, there are left-overs in unit Graphics). So, the solution is: Open the offending lfm file in an external editor, find "clText" and delete this line (Font.Color = clText) - you may want to delete alsothe other lines around this one because the forms use hard-coded windows fonts (usually the ugly "MS Sans-serif").

Or wait a bit, I am looking over the sample project and am trying to modernize them.

[Thaddy]

That is strange to remove the font.color := clText;
Of course then you also remove Delphi compatibility.
Who did that?

Anyway, as I explained, OnGuard has seen better days and maybe that should be removed...
It was really good while it lasted, though.
Nowadays it puts people on the wrong foot. That is not what you want.
Obfuscators are really evil and do not have a function. There are better ways to protect software.

[eldonfsr]

Ok Thanks all for replay e, Tadd thanks i wait a lite for you changes...

[wp]

Cannot find a clText in the Delphi graphics sources. Anyway, it is removed from the lfm file only - Delphi cannot read lfm... And there are no dfm files at all in the ccr version. So, I don't care much about Delphi compatibility here anyway.

[dsiders]

Cannot find a clText in the Delphi graphics sources. Anyway, it is removed from the lfm file only - Delphi cannot read lfm... And there are no dfm files at all in the ccr version. So, I don't care much about Delphi compatibility here anyway.

clText was from the aborted clx architecture.

[Thaddy]

clText was from the aborted clx architecture.

No! it was also at least in D7. clx was in that way cross-compatible. Actually quite good at the time. (I was a beta tester)

[wp]

Or wait a bit, I am looking over the sample project and am trying to modernize them.

Done. Fixed sample projects and uploaded to CCR. Either get the new version by means of svn, or download the zipped snapshot from https://sourceforge.net/p/lazarus-ccr/svn/HEAD/tree/components/onguard/.

Did this on Laz/main+FPC3.2.2 on Win11 (32bit). However, the package does not compile with the 64-bit IDEs of Laz/main or Laz 2.2.4 (due to some 16-bit-like assembler code). And it does not compile either on Linux (64bit). So, this package really is of little use.

Then I tried Graeme's version (https://github.com/graemeg/onguard), and it is better, the 64-bit version on Windows now is working as well as the Linux version. (The sample projects must be taken from the CCR version, though). Maybe I should take the time to copy Graeme's code over to CCR?

[wp]

clText was from the aborted clx architecture.

No! it was also at least in D7. clx was in that way cross-compatible. Actually quite good at the time. (I was a beta tester)

Can't find "clText" in D7 either. In the OnGuard units "clText" is used only in the demo projects. Even if Delphi compatibility would be an aim, removing clText from the demo forms would not be a problem because Delphi would use the default propery value then.

[eldonfsr]

Thanks i know you work hard and I appreciate your effort but when compile package send this error

ogutil.pas(357,3) Error: Unrecognized opcode LES

could be for 64 bits...
Thanks so much...and sorry for that..

[wp]

The new version on CCR now works for 64-bit Windows and for Linux. It does not work for macOS (Graeme's version doesn't either).

[Thaddy]

pointless.

[rvk]

pointless.

Yep, just as pointless as you locking your house every night 

(Good for the casual passersby)