PDA

View Full Version : Strange problem with Comodo and WinXP



NewsArchive
11-07-2008, 03:25 AM
Hi there
After having put a Comodo certificate on my app (c6.3, ABC single EXE), i
have had 3 customers who cannot start the program anymore. They all use
WinXP Pro. The error message is 'Faktura.exe has found an error ant close
down. We are sorry about the trouble' (It does say it in Danish, so it must
be a windows message). One customer say 'if i dont press any buttons, the
message disappears and i can use the program'. I have never seen this
myself, and AFIK many others are using my program on WinXP.
From Setupbuilder i do (in the script, before create folders):
Lock program to 1 processor (imagecfg.exe)
Copyprotect with armadillio
Codesign the exe

I codesign the installer too (project definitions).

After reinstalling the last version before Comodo, everything works fine
again.
Have anyone seen something like this ?

--
Kind regards / Med Venlig Hilsen
Viggo Poulsen
Vipilon ApS
www.vipilon.dk

NewsArchive
11-07-2008, 03:26 AM
Viggo,

I know nothing about locking to processor but :
is it really necessary ?
are you locking to your processor ? (then if the user has two and you one or
the contrary...)

--
Thank you

Cordialement - Best regards
Jean-Pierre GUTSATZ

CGF

DMC - Data Management Center - A tool to let you Migrate Import Export
Transfer all your Data very easily
www.dmc-fr.com
Certified by Microsoft : "Works with Vista" & "Works with Windows Server
2008"

NewsArchive
11-07-2008, 03:26 AM
Hi
What i do is to tell the exe file that if you have two processors (or a
multicore processor), then it may only run on the least loaded processor (or
core).

Kind regards
Viggo Poulsen

NewsArchive
11-07-2008, 03:28 AM
Hi,

Maybe ..... try doing a special installer without this just for that client
and get him to test
Like this at least you will be sure that it is NOT this 'thingy' (personnaly
I never see any one cpu from my 4 being always less used it varies too much
to be always the number x etc ..... but only _my_ opinion)

--
Thank you

Cordialement - Best regards
Jean-Pierre GUTSATZ

CGF

DMC - Data Management Center - A tool to let you Migrate Import Export
Transfer all your Data very easily
www.dmc-fr.com
Certified by Microsoft : "Works with Vista" & "Works with Windows Server
2008"

NewsArchive
11-07-2008, 03:49 AM
Hi
The version that works do have the processor binding too, so I dont think
that the problem is there. This is the scenario:
Works:
Lock program to 1 processor (imagecfg.exe)
Copyprotect with armadillio

Works Not:
Lock program to 1 processor (imagecfg.exe)
Copyprotect with armadillio
Codesign the exe

That is why i suspect the codesigning.
The processor binding check at programstartup wich processor/core has the
least load, and then desides wich one to use.

Kind regards
Viggo Poulsen

NewsArchive
11-08-2008, 01:51 AM
One sec Viggo ..I think remembering there is an ORDER to use for armadillo
with code signing.....
Check the calrionmag ..... think there is an article there

--
Thank you

Cordialement - Best regards
Jean-Pierre GUTSATZ

CGF

DMC - Data Management Center - A tool to let you Migrate Import Export
Transfer all your Data very easily
www.dmc-fr.com
Certified by Microsoft : "Works with Vista" & "Works with Windows Server
2008"

NewsArchive
11-08-2008, 01:52 AM
Thank you for the tip. According to Janes excellent article i do it in the
right order. I do, though, leave it to Setupbuilder to do the Armadillo and
codesigning stuff in the right order. Maby it is better to do it during
compile time instead ?

Kind regards
Viggo Poulsen

NewsArchive
11-08-2008, 01:52 AM
> Thank you for the tip. According to Janes excellent article i do it in the
> right order. I do, though, leave it to Setupbuilder to do the Armadillo
> and codesigning stuff in the right order. Maby it is better to do it
> during compile time instead ?

Do you have the "Permanent" option enabled in the #code-sign compiler
directive?

Friedrich

NewsArchive
11-08-2008, 01:53 AM
Yes, it is checked.
Kind regards
Viggo Poulsen

NewsArchive
11-08-2008, 01:53 AM
> Yes, it is checked.

Hmm, then it's correct. There must be another reason for it. From the
techical point of view, there is no difference between doing it at
(application) compile time and (installation) compile time.

Friedrich

NewsArchive
11-08-2008, 01:54 AM
Can it be because i first codesign my program and then, immediately after
that, codesign a little dummy exe wich are being run at the end of the
installation (ensures Armadillo registers in System) ? The strange thing is,
that i have no problem with Vista but with some WinXp installations.

Viggo

NewsArchive
11-08-2008, 01:54 AM
> Can it be because i first codesign my program and then, immediately after
> that, codesign a little dummy exe wich are being run at the end of the
> installation (ensures Armadillo registers in System) ? The strange thing
> is, that i have no problem with Vista but with some WinXp installations.

No, this is absolutely no problem. You can code-sign as many applications
as you want from the SetupBuilder pre-compiler system.

Are you using the very latest Armadillo stuff?

Friedrich

NewsArchive
11-08-2008, 01:55 AM
Hi
I used V6.04 in both installations (both with and without codesigning). As
it works fine without codesigning i thougth it could not be an Armadillo
problem. I have just upgraded to V6.22 . I'll try to make a new build and
ask my costumers install this.

Viggo

NewsArchive
11-09-2008, 03:40 AM
Hi
Upgrading Armadillo solved the problem !!
So it must be the combination of Armadillio V6.04 and codesigning that gave
the problem. Oh, well. The customer is happy so I am happy too.

Kind regards
Viggo Poulsen

NewsArchive
11-09-2008, 03:41 AM
Hi Viggo,

> Upgrading Armadillo solved the problem !!
> So it must be the combination of Armadillio V6.04 and codesigning that
> gave the problem. Oh, well. The customer is happy so I am happy too.

Perfect! Thanks for the update.

Friedrich