Vista - Armadillo - Command line and SetupBuilder 6.5 - Dev Edition

[NewsArchive]

Vista - Armadillo - Command line and SetupBuilder 6.5 - Dev Edition

Could someone working with Armadillo/SoftwarePassport Professional in Vista
give me some hints on using a command line to Armadillo protect a program
while using SetupBuilder 6.5 - Dev Edition to create an install.

In SetupBuilder 6.5, I think this is the correct sequence...

Embed the Vista Manifest
Call Armadillo to then protect the EXE
THEN do code sign

I installed SoftwarePassport to \Program Files\SoftwarePassport\ (default),
is that causing command line use problems?

David

--
From David Troxell - Product Scope 32 PRO - Encourager Software
Clarion Third Party Profile Exchange Online
http://encouragersoftware.com/profile/clarlinks.html
http://www.encouragersoftware.com/
http://www.encouragersoftware.com/blog/

[NewsArchive]

David,
I haven't done it within SB.
I link in the manifest at compile-time, then run a batch file at the end of
my compilation to invoke Armadillo if that app uses it and then use the
batch file to sign the app.

Yes, your order of things (manifest, Arm, sign) is correct.

If you're using the #run script item in SB, maybe try enclosing the File
Name and Command Line entries in quotation marks. And be sure to tick the
"Wait for Program" box.
My batch file I use to run Arm looks something like the following (it will
wrap here, but all on one line of course):

"D:\program files\softwarepassport\armadillo.exe" "D:\program
files\softwarepassport\MyArmProjectFile.arm" /P

Look in ARMHELP.CHM in the "Automating Protection" topic for command-line
syntax.

HTH

Jane

[NewsArchive]

> My batch file I use to run Arm looks something like the following (it will
> wrap here, but all on one line of course):
>
> "D:\program files\softwarepassport\armadillo.exe" "D:\program
> files\softwarepassport\MyArmProjectFile.arm" /P

You can do it without the batch file in SB - the #run allows you to set the
parameter there.

I do it all inside.

;-)

Charles


--
-------------------------------------------------------------------------------------------------------
Charles Edmonds

www.clarionproseries.com - "Serious imaging tools for Clarion Developers"
www.ezround.com - "Round Corner HTML tables with matching Banners, Buttons
and Forms!"
www.lansrad.com - "Intelligent Solutions for Universal Problems"
www.fotokiss.com - "World's Best Auction Photo Editor"
-------------------------------------------------------------------------------------------------------

[NewsArchive]

> David,
> I haven't done it within SB.
> I link in the manifest at compile-time, then run a batch file at the end of
> my compilation to invoke Armadillo if that app uses it and then use the
> batch file to sign the app.

Jane,

Thanks for your help - first, I am just trying to get the command line
option to work either from a batch file or within the command prompt before
I test it with the #run script within SB65.

I have followed your example, the batch file in the CHM help, and also a
Forum message example.

I have the ARM file located in C:\program files\softwarepassport\ and using
the CHM help batch file example (AND either made sure the current directory
is C:\program files\softwarepassport\ in the command prompt or clicking
directly on the batch file in File Explorer - C:\program
files\softwarepassport\ folder)

I modified this example with my ARM file to create my batch file.

start /wait Armadillo YourProject.arm /P

if errorlevel 1 goto armadillo_error

But so far, no joy - I am using Vista Home Premium - hope that it's not
command prompt brain dead for anything other than dir

BUT I'll keep experimenting and report back! Thanks!

David

--
From David Troxell - Product Scope 32 PRO - Encourager Software
Clarion Third Party Profile Exchange Online
http://encouragersoftware.com/profile/clarlinks.html
http://www.encouragersoftware.com/
http://www.encouragersoftware.com/blog/

[NewsArchive]

> Vista - Armadillo - Command line and SetupBuilder 6.5 - Dev Edition
>
> Could someone working with Armadillo/SoftwarePassport Professional in Vista
> give me some hints on using a command line to Armadillo protect a program
> while using SetupBuilder 6.5 - Dev Edition to create an install.

What - you don't even read or look at the screen shots in the email I sent
you when you asked me about that?

;-)

Charles


--
-------------------------------------------------------------------------------------------------------
Charles Edmonds

www.clarionproseries.com - "Serious imaging tools for Clarion Developers"
www.ezround.com - "Round Corner HTML tables with matching Banners, Buttons
and Forms!"
www.lansrad.com - "Intelligent Solutions for Universal Problems"
www.fotokiss.com - "World's Best Auction Photo Editor"
----------------------------------------------------------

[NewsArchive]

> On 29 May 2007 17:08:42 -0400, David Troxell - Encourager Software wrote:
>
>> Vista - Armadillo - Command line and SetupBuilder 6.5 - Dev Edition
>>
>> Could someone working with Armadillo/SoftwarePassport Professional in Vista
>> give me some hints on using a command line to Armadillo protect a program
>> while using SetupBuilder 6.5 - Dev Edition to create an install.
>
> What - you don't even read or look at the screen shots in the email I sent
> you when you asked me about that?

Charles,

You will LOVE this - it's looks like it's a VISTA problem (OR A David
Troxell problem OR a Vista AND David Troxell problem)! So far in Vista Home
Premium, NONE of the command line examples or batch examples are working.

It has nothing to do with your excellent examples!

Before I create the SB #run script, I decided to get it working from the
command prompt or batch files (outside of SB65) - so far, not working for
me.

David

--
From David Troxell - Product Scope 32 PRO - Encourager Software
Clarion Third Party Profile Exchange Online
http://encouragersoftware.com/profile/clarlinks.html
http://www.encouragersoftware.com/
http://www.encouragersoftware.com/blog/

[NewsArchive]

> You will LOVE this - it's looks like it's a VISTA problem (OR A David
> Troxell problem OR a Vista AND David Troxell problem)! So far in Vista Home
> Premium, NONE of the command line examples or batch examples are working.
>
> It has nothing to do with your excellent examples!
>
> Before I create the SB #run script, I decided to get it working from the
> command prompt or batch files (outside of SB65) - so far, not working for
> me.

You might check on the PRIVATE Armadillo newsgroups and see if you can find
a relevant post there.

If you don't, then drop an email to support@siliconrealms.com and you
should hear back from them tomorrow.

HTH,

Charles


--
-------------------------------------------------------------------------------------------------------
Charles Edmonds

www.clarionproseries.com - "Serious imaging tools for Clarion Developers"
www.ezround.com - "Round Corner HTML tables with matching Banners, Buttons
and Forms!"
www.lansrad.com - "Intelligent Solutions for Universal Problems"
www.fotokiss.com - "World's Best Auction Photo Editor"
-------------------------------------------------------------------------------------------------------

[NewsArchive]

David,

I let C6 (9056) link the Vista compliant manifest into my app, then I
have the following .BAT file that I run under "Programs to Execute" in
the project editor...

-----
start /wait Armadillo c:\clarion6\projects\LM\LM.ARM /P
if errorlevel 1 goto armadillo_error
goto end

:armadillo_error
rem Armadillo Error!!!
rem Armadillo Error!!!
rem Armadillo Error!!!
pause

:end
-----

If I recall correctly I needed to have the Armadillo directory in the
system environment path to get it to work even if I fully qualified
the path to it in the bat file.

So when I make my project it links in the manifest and calls Armadillo
to protect the .EXE. Then I have SB code sign the .EXE when I create
the installer.

This is just how I chose but the bottom line is...

1) Link in manifest
2) Protect with Armadillo
3) Code sign

As long as you go with that order it doesn't really matter if you
choose to use a combination of C6/SB like I do or do it all in SB.

- Kelly

[NewsArchive]

On 30 May 2007 13:20:20 -0400, Kelly E Major wrote:

> David,
>
> I let C6 (9056) link the Vista compliant manifest into my app, then I
> have the following .BAT file that I run under "Programs to Execute" in
> the project editor...

Kelly,

Thanks for these suggestions -

> If I recall correctly I needed to have the Armadillo directory in the
> system environment path to get it to work even if I fully qualified
> the path to it in the bat file.

Mine wasn't, but I modified the path to include the Armadillo folder, and
that didn't make a difference for me.

Running Windows Vista Home Premium, and I have followed all the examples
suggested both here, SoftwarePassport Forum, etc

But so far, the command line, batch solutions are not working for me yet.

ONCE I do get the batch method working, I'll use that in a #run script in
SB65 dev edition - others have vista manifest, armadillo protect and code
signed within SB65, and that is what I prefer.

David

--
From David Troxell - Product Scope 32 PRO - Encourager Software
Clarion Third Party Profile Exchange Online
http://encouragersoftware.com/profile/clarlinks.html
http://www.encouragersoftware.com/
http://www.encouragersoftware.com/blog/

[NewsArchive]

David,

Unfortunately I'm out of suggestions but I do have the method I
described working in Windows XP and Vista Business (UAC on).

- Kelly

[NewsArchive]

On 30 May 2007 14:38:03 -0400, Kelly E Major wrote:

> David,
>
> Unfortunately I'm out of suggestions but I do have the method I
> described working in Windows XP and Vista Business (UAC on).

Kelly,

Thanks for the help (and Jane too!)

HOWEVER, I now have successfully used Batch Files AND SB script to
Armadillo protect (using a combination of all ideas supplied).

Here is the standard batch file suggested in the ARMHELP.chm - command line
options help topic with a few specific pathed alterations (first line wraps
in newsgroup message)


start /wait Armadillo C:\devapps\SoftwarePassport\sample.arm
/file=C:\devfolder\program.exe /P

if errorlevel 1 goto armadillo_error


I made these basic changes on my computer -

installed SoftwarePassport to a folder other than \Program Files\

Since there are problems writing to the \Program Files\ area, I avoid it
with this change.

changed path to include - C:\devapps\SoftwarePassport\

saved my arm files to C:\devapps\SoftwarePassport\

use the /file=
with the specific path to it's location

Not sure if all these changes were necessary, but most of them were done
one step at a time without results.

Setupbuilder - Simply added a #run script after the Vista Embed - both
before Create Folders

file Name:
nameofbatchfile.bat

Command Line:
(left blank)

Default Directory:
C:\devapps\SoftwarePassport\

Checked - Wait for Program

Now, my batch files work with Armadillo-SoftwarePassport AND SetupBuilder
6.5 Developer Edition

David

--
From David Troxell - Product Scope 32 PRO - Encourager Software
Clarion Third Party Profile Exchange Online
http://encouragersoftware.com/profile/clarlinks.html
http://www.encouragersoftware.com/
http://www.encouragersoftware.com/blog/

[NewsArchive]

David,

The following sequence in your script should work fine:

1. Freshly created application .exe
2. #embed Vista manifest (Permanent option ENABLED)
3. Call to Armadillo protection
4. #code-sign application (NOT permanent)

Friedrich

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

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

-- Official Comodo Code Signing and SSL Certificate Partner

[NewsArchive]

> David,
>
> The following sequence in your script should work fine:

Friedrich,

Thanks for the response!

>
> 1. Freshly created application .exe
> 2. #embed Vista manifest (Permanent option ENABLED)
> 3. Call to Armadillo protection

This is where I was having my problem (NOT a SetupBuilder problem) - I
could not get Armadillo batch files (command line) to work properly -
outside SetupBuilder.

I have detailed in another newsgroup message how I resolved that issue, and
now I can successfully run Armadillo batch files within SetupBuilder.

Again thanks to you and your development team for giving
Armadillo/SoftwarePassport Professional users the options we need to
include three critical areas (#2, 3, and 4) - ALL under the SetupBuilder
umbrella!

David

> 4. #code-sign application (NOT permanent)
>
> Friedrich


--
From David Troxell - Product Scope 32 PRO - Encourager Software
Clarion Third Party Profile Exchange Online
http://encouragersoftware.com/profile/clarlinks.html
http://www.encouragersoftware.com/
http://www.encouragersoftware.com/blog/