Assistance please

[NewsArchive]

did the manifest, installed it, went in same directory as exe, is there
anything else todo? still program won't run, .


--
Andy <<Cowboy>> Stapleton
www.forexmgr.com
www.BlueCollarTradingSociety.com

[NewsArchive]

Gday Andy

>did the manifest, installed it, went in same directory as exe, is there
>anything else todo? still program won't run, .

1: Did you compile the manifest INTO your exe using the project settings...

i.e. add andys.manifest under the "Library, object and resource files" in project
settings

2: Did you buy a code signing certificate and sign the exe.

3: I guess you are using some copy protection in your app. Perhaps the files
containing the security stuff are not where you think they are AT RUN TIME (It's a
Vista thing, - uses various shadow folders)

These are just a few things that will give you a Vista headache. Perhaps a couple of
shots of Tequilla might help at this stage ;-)

Look for a lot of help on this problem on Dave's ClarionMag.

JohnG

[NewsArchive]

Hi Andy,

>did the manifest, installed it, went in same directory as exe, is there
>anything else todo? still program won't run, .

You need to do the manifest in SetupBuilder, NOT in Clarion. Check
the "Generate Manifest" in Clarion, but do NOT distribute that
manifest with the exe. Everything else needs to be done in
SetupBuilder.

In SetupBuilder, use the #embed Vista Manifest statement to add a
Vista manifest to the exe and use "asInvoker" This creates and links
in a vista enabled manifest into the exe file. I do this as the first
thing in my SB scripts, right after the #include script "Common
definitions.sbi".

The next thing I do is add the code signing to the exe - it must be
done AFTER the manifest is linked in.

If you distribute the manifest from Clarion with your app, I think it
will override the embedded manifest from SB (not 100% sure, but I seem
to recall it did when I started doing this last year)

Best regards,

Arnór Baldvinsson
Icetips Creative, Inc.
San Antonio, Texas, USA
www.icetips.com


Subscribe to information from Icetips.com:
http://www.icetips.com/subscribe.php

[NewsArchive]

Andy,

If you are using any exe protection systems (such as Armadillo) you need to
make certain you embed the manifest using SetupBuilder first, and THEN
protect your exe. After it is protected, then it needs to be code signed. It
needs to be done in that sequence.

HTH

--
Regards,

Lee
http://www.cya2day.com

[NewsArchive]

I don't use any copy protection, so do I still need the code signing?

I removed the CW manifest and generated the one from SB. we shall see<g>


--
Andy <<Cowboy>> Stapleton
www.forexmgr.com
www.BlueCollarTradingSociety.com

[NewsArchive]

Yes, you really should code-sign the main application file and, of course,
the installer.

--
Friedrich Linder
Lindersoft
www.lindersoft.com
+1.954.252.3910

"point. click. ship" - that's SetupBuilder 6.7
Create Windows Vista ready installations in minutes

-- Official Comodo Code Signing and SSL Certificate Partner

[NewsArchive]

Hi Andy,

>I don't use any copy protection, so do I still need the code signing?

I would do it. Both the exe and the installer. I don't like it when
I run something on Vista or XP and it pops up a security warning
telling me "Unknown Publisher"<g> It just doesn't look pro to me.

Best regards,

Arnór Baldvinsson
Icetips Creative, Inc.
San Antonio, Texas, USA
www.icetips.com


Subscribe to information from Icetips.com:
http://www.icetips.com/subscribe.php