Onguard Win64

[Graeme]

Seems to be time to make a donation instead of buying another version of Delphi

We gave up Delphi back in 2006 - never looked back and never regretted it either. Free Pascal is a fantastic compiler, and Lazarus IDE is a great development tool.  The amount of money we saved is incredible, and the flexibility open-source development tools give is just amazing. I can't imagine anything different.

[tatamata]

Hi, Graeme!
There are two packages here: tponguard.lpk and tponguard_design.lpk.
tpongurad.lpk is run-time only? No installation needed?
Which-one to use normally?
 Compilation of run-time tponguard - no problem, but when trying to compile and install tponguard_design.lpk, I get error:

tponguard_design.pas(10,5) Fatal: Can not find unit ogreg used by tponguard_design. Check if package tponguard_design is in the dependencies.

[Graeme]

There are two packages here: tponguard.lpk and tponguard_design.lpk.
tpongurad.lpk is run-time only? No installation needed?
Which-one to use normally?

tponguard.lpk Is a runtime only package which means it is not dependent on any GUI toolkit etc, so can be used in web pages, console apps, other non-LCL programs etc.

tionguard_design.lpk Is a design time package, which is used to install and register components on the Lazarus IDE component palette. Thus it has a Lazarus LCL/IDE dependency.

I normally use the runtime-only package only. Simply add it as a dependency to any project. It will be compiled by Lazarus IDE when required, but will not be installed on the component palette toolbar.

I'll take a look at the error you get on the design time package. I restructured the directory layout, so might have broken the paths to some files. Should be a quick and easy fix.  Thanks for bringing this to my attention.

[tatamata]

There are two packages here: tponguard.lpk and tponguard_design.lpk.
tpongurad.lpk is run-time only? No installation needed?
Which-one to use normally?

tponguard.lpk Is a runtime only package which means it is not dependent on any GUI toolkit etc, so can be used in web pages, console apps, other non-LCL programs etc.

tionguard_design.lpk Is a design time package, which is used to install and register components on the Lazarus IDE component palette. Thus it has a Lazarus LCL/IDE dependency.

I normally use the runtime-only package only. Simply add it as a dependency to any project. It will be compiled by Lazarus IDE when required, but will not be installed on the component palette toolbar.

I'll take a look at the error you get on the design time package. I restructured the directory layout, so might have broken the paths to some files. Should be a quick and easy fix.  Thanks for bringing this to my attention.

ok, please note, this is CodeTyphon Lazarus distribution, version 4.70.

[Graeme]

ok, please note, this is CodeTyphon Lazarus distribution, version 4.70.

Shouldn't make any difference. As far as I know CodeTyphon is just a rebranded Lazarus and with some mods and lots more 3rd party components.

[BigChimp]

The version of OnGuard you used is out of date. For the purposed of my work and customers, I started to maintain my own version of OnGuard. It can be found here:
  https://github.com/graemeg/onguard

I can confirm that it does work on 32-bit and 64-bit Windows,Linux and FreeBSD.

Updated the wiki at
http://wiki.lazarus.freepascal.org/OnGuard#Alternative_version
of course, please feel free to correct the article etc.

Thanks.

[Graeme]

I updated the design time package (Github repository), so the source paths now point to the correct source locations. The package now compiles and installs without problems into Lazarus IDE and the component palette.

Sorry about the inconvenience. I reorganised the directories a while back, but forgot to amend the paths in the design time package.

https://github.com/graemeg/onguard

[tatamata]

Hi, Grame!
I think you should add Include path in the package general options. That's for onguard.inc file...

Anyway,
I wanted to make a customized code generator for my program, in the way it is done in CODEGEN example. For instance, I'd like to open CodeGenerateFrm with serial number page sheet, my program's key set, machine modifier chek box checked etc.

For some reason, I can't change any of the CodeGenerateFrm properties in runtime?
Why I can't change properties of the  CodeGenerateFrm after it is created by executing OgMakeCodes1.Execute?

Code: [Select]

procedure TCodeGenFrm.GenerateBtnClick(Sender: TObject);
const

  CKey:TKey=(..Here is Some Key...);

var
  Work : TCode;
begin
  {set default key to use}

  OgMakeCodes1.SetKey(CKey); //this works
  OgMakeCodes1.CodeType:=ctSerialNumber;//this works

  if OgMakeCodes1.Execute then begin
    //Set some properties to the code-generation form
    //Nothing happens when properties changed in the generated form?
    CodeGenerateFrm.TabSheet1.TabVisible:=False;
    CodeGenerateFrm.CodesNbk.ActivePage:=CodeGenerateFrm.TabSheet2;
    CodeGenerateFrm.NoModifierCb.Checked:=False;
    CodeGenerateFrm.MachineModifierCb.Checked:=True;
    CodeGenerateFrm.Caption:='trlababalan';

    {get the code}
    OgMakeCodes1.GetCode(Work);
    {display the code}
    CodeEd.Text := OgUtil.BufferToHex(Work, SizeOf(Work));
  end;

end;                                               

[tatamata]

I couldn't figure-out why I can't customize design package forms after calling OgMakeCodes Execute method, so I made my own form for code generator....

Anyway, thanks to Graeme, I successfully integrated tponguard into my program. Grame, thank you for keeping this package alive.

However, I would point to some minor issues which I came accross:
1. I'm working in Linux, but cross-compile program for Windows. When I wanted to cross-compile, an error appeared about missing idesn unit. This unit is required only in Windows. So I had to add it to the package. However, when going back to Linux compilation, now error appears because of idesn unit, which is only for Windows, so I had to remove it from package again...Well, not very convinient...Since I don't have Windows machine, I don't know how it behaves when installed in Windows...
2. ogfirst unit for single-instance application is not included. Is this intentionally? I mean, there is LuiControls with its UniqueInstance component, which is working very good, but, still, it would be good to have alternative...

Regards

[Fred vS]

This unit is required only in Windows.

Why dont you use : ?

Code: [Select]

uses
{$ifdef windows}
idesn,
 {$endif}

[tatamata]

This unit is required only in Windows.

Why dont you use : ?

Code: [Select]

uses
{$ifdef windows}
idesn,
 {$endif}

Hi! It's already in onguard.pas ifedefed:

Code: [Select]

{$IFDEF WIN32}
  ,idesn
{$ENDIF} I have just finished a program in Linux and tried to cross-compile it for Windows.
I addend idesn.pas to the tponguard package as last time, recompiled package, but this time I can't compile the project...
What ever I do, I get error: "

unit10.pas(0,0) Fatal: Can not find idesn used by onguard, ppu=/usr/lib/codetyphon/typhon/components/onguard-master/packages/lib/i386-win32/Idesn.ppu, package tponguard

"
I don't understand this...How it can't find the unit when the unit is added to the package?

[tatamata]

This unit is required only in Windows.

Why dont you use : ?

Code: [Select]

uses
{$ifdef windows}
idesn,
 {$endif}

Hi! It's already in onguard.pas ifedefed:

Code: [Select]

{$IFDEF WIN32}
  ,idesn
{$ENDIF} I have just finished a program in Linux and tried to cross-compile it for Windows.
I addend idesn.pas to the tponguard package as last time, recompiled package, but this time I can't compile the project...
What ever I do, I get error: "

unit10.pas(0,0) Fatal: Can not find idesn used by onguard, ppu=/usr/lib/codetyphon/typhon/components/onguard-master/packages/lib/i386-win32/Idesn.ppu, package tponguard

"
I don't understand this...How it can't find the unit when the unit is added to the package?

Oh, when I renamed "Idesn.ppu" to "idesn.ppu", now it seems it is working...

[stoppok]

Hi Graeme,

I'm now integrating OnGuard source from your repository into my project and found a problem with TOgDaysCode (and possibly TOgDateCode): It's very simple to fool the check because the implementation of  "InvalidCount" is not correct. I found the source of the problem in IsDaysCodeValid:

...
  if (not Result) and (Work.InvalidCount >0) then Result := true;
...

If somebody can manipulate the Code (e.g. in Ini-file)  then Work.InvalidCount will get some other value then expected and it will be > 0 very very often.

I'd recommend to remove this feature, makes not much sense to me.

[tatamata]

Hi Graeme,

I'm now integrating OnGuard source from your repository into my project and found a problem with TOgDaysCode (and possibly TOgDateCode): It's very simple to fool the check because the implementation of  "InvalidCount" is not correct. I found the source of the problem in IsDaysCodeValid:

...
  if (not Result) and (Work.InvalidCount >0) then Result := true;
...

If somebody can manipulate the Code (e.g. in Ini-file)  then Work.InvalidCount will get some other value then expected and it will be > 0 very very often.

I'd recommend to remove this feature, makes not much sense to me.

Hi, stoppok!

Many thanks posting this! I think you are right.
I was just twitching my hair - I was tested trial release code (days code) previous days and everything seemed to be OK, so I didn't look at it again. But, when I looked at it now, suddenly the program's log said: "Trial release code is valid!
Trial release code is: A97AD6950BC9BAA2FD19
Trial period is valid!
--> Trial days left: 35343
--> Trial expiration date: 01.01.9999", although trial period should have ended few days ago !

When I commented the code in IsDaysCodeValid, as you suggested, now it seems to be OK again.

Brrr...very dangerous!

Can somebody else confirm this bug? Graeme?

[Graeme]

If somebody can manipulate the Code (e.g. in Ini-file)  then Work.InvalidCount will get some other value then expected and it will be > 0 very very often.

I'd recommend to remove this feature, makes not much sense to me.

I see what you mean. Thanks for pointing this out. I have modified the OnGuard code to not check the Work.InvalidCount any more. That was a silly feature/idea to start with.

Github repository has been updated.