Paging Jane or alternative Armadillo - Setupbuilder Expert

[NewsArchive]

Jane,

I am using latest SetupBuilder Developer SB7 and latest Armadillo.

Trying to incorporate the STUB EXE method in a SB7 install.

Standalone - outside the install - the STUB EXE DOES work, but when I
execute it during install, it does not work.

Of course, the STUB EXE is requireAdministrator manifested, Armadillo
protected by the same ARM file used for other protected programs in the
install AND I have tried both Vista and Windows 7 manifest.

David

--
From David Troxell - Product Scope 7.8 - Encourager Software
Product Scope 7 Viewer - NO Registration Fee! Free to Use!
http://www.encouragersoftware.com/
Clarion Third Party Profile Exchange Online
http://encouragersoftware.com/profile/clarlinks.html
http://www.profileexchanges.com/blog/

[NewsArchive]

Rattle my synapses, please, David...

The "stub exe" method meaning exactly what...?? using the EXE to preset
Armadillo stuff for the project while the installer is running elevated? Or
something else?

Jane

[NewsArchive]

> Rattle my synapses, please, David...
>
> The "stub exe" method meaning exactly what...?? using the EXE to preset
> Armadillo stuff for the project while the installer is running elevated? Or
> something else?

Jane,

I'm sorry, maybe that term STUB EXE is another person's invention, but the
concept you explained in this article (sub required)

http://www.clarionmag.com/cmag/v9/v9n05vista3b.html

under the section

Lest We Forget Armadillo...

"Once you've run one Armadillo-protected app once with elevated
permissions, it sets up the areas of the registry it needs"

David

--
From David Troxell - Product Scope 7.8 - Encourager Software
Product Scope 7 Viewer - NO Registration Fee! Free to Use!
http://www.encouragersoftware.com/
Clarion Third Party Profile Exchange Online
http://encouragersoftware.com/profile/clarlinks.html
http://www.profileexchanges.com/blog/

[NewsArchive]

OK, I thought that might be it.

First, though I've upgraded my license to Armadillo 6 I'm still using 4.66
for most of my projects. I tried 6.x on one project that's stored on a
server. A Dell Vista laptop took more than 10 seconds to load and unpack
the program (which is fairly small), versus about a second and a half when
the same program was protected with 4.66.

That's probably neither here nor there.

What is the symptom that tells you that the stub didn't work?

And are you SURE it's actually running?

Even though your stub is presumably silent, for testing I'd put a "hello I'm
here and I ran" window into it and try your installer again.

Are you including it as a support file or as an installed file?

Are you using SB's %TMPDIR% as the path to it or something else?

Jane

[NewsArchive]

> OK, I thought that might be it.
>
> First, though I've upgraded my license to Armadillo 6 I'm still using 4.66
> for most of my projects. I tried 6.x on one project that's stored on a
> server. A Dell Vista laptop took more than 10 seconds to load and unpack
> the program (which is fairly small), versus about a second and a half when
> the same program was protected with 4.66.
>
> That's probably neither here nor there.
>
> What is the symptom that tells you that the stub didn't work?
>
> And are you SURE it's actually running?
>
> Even though your stub is presumably silent, for testing I'd put a "hello I'm
> here and I ran" window into it and try your installer again.

Jane,

Thanks for the help.

No, it does not appear to be running. I put a window in the STUB EXE and
ran it both ways - From the Run Program general installer function

run within the install and checkbox run after the install. The window never
appears during the install, and the STUB EXE did NOT run after the install
with checkbox checked on Finish Dialog text.

I also tried various combinations - run while in install - wait for program
and wait for program and use ShellExecuteEx

>
> Are you including it as a support file or as an installed file?

For now, I have included it as installed file.

>
> Are you using SB's %TMPDIR% as the path to it or something else?

Not sure, whatever SB uses for Run program and installed file combination.

David

--
From David Troxell - Product Scope 7.8 - Encourager Software
Product Scope 7 Viewer - NO Registration Fee! Free to Use!
http://www.encouragersoftware.com/
Clarion Third Party Profile Exchange Online
http://encouragersoftware.com/profile/clarlinks.html
http://www.profileexchanges.com/blog/

[NewsArchive]

>> OK, I thought that might be it.
>>
>> First, though I've upgraded my license to Armadillo 6 I'm still using 4.66
>> for most of my projects. I tried 6.x on one project that's stored on a
>> server. A Dell Vista laptop took more than 10 seconds to load and unpack
>> the program (which is fairly small), versus about a second and a half when
>> the same program was protected with 4.66.
>>
>> That's probably neither here nor there.
>>
>> What is the symptom that tells you that the stub didn't work?
>>
>> And are you SURE it's actually running?
>>
>> Even though your stub is presumably silent, for testing I'd put a "hello I'm
>> here and I ran" window into it and try your installer again.
>
> Jane,
>
> Thanks for the help.
>
> No, it does not appear to be running. I put a window in the STUB EXE and
> ran it both ways - From the Run Program general installer function
>
> run within the install and checkbox run after the install. The window never
> appears during the install, and the STUB EXE did NOT run after the install
> with checkbox checked on Finish Dialog text.
>
> I also tried various combinations - run while in install - wait for program
> and wait for program and use ShellExecuteEx

Jane,

I am testing this under Vista 64.

David

--
From David Troxell - Product Scope 7.8 - Encourager Software
Product Scope 7 Viewer - NO Registration Fee! Free to Use!
http://www.encouragersoftware.com/
Clarion Third Party Profile Exchange Online
http://encouragersoftware.com/profile/clarlinks.html
http://www.profileexchanges.com/blog/

[NewsArchive]

David,

> No, it does not appear to be running.

What error code does "Run Program" return? Perhaps this will give us more
information?

Friedrich

[NewsArchive]

> David,
>
>> No, it does not appear to be running.
>
> What error code does "Run Program" return? Perhaps this will give us more
> information?

Friedrich,

I'll need to reset my VMware Virtual snapshot and run the one that failed
(and copy the log), since I reset it and ran a successful one with the SB69
compile.

However, since I last reported, I have found an SB69 project file that
worked (RUN program in install) in BOTH SB69 and then when converted to
latest SB7, worked as well in RUN program in install as well.

All of the SB6 project files were based on installations for Product Scope
7. Of course, they have been upgraded through various versions.

So, it will take a bit of time before I can reconfigure the VM snapshots
and get a log from the SB7 converted project that failed.

Also, the only major difference (that I am aware of) between the

failed (did NOT RUN program within install) SB7 project and the

successful (did Run program within install) SB7 project is that the:

successful one was a SB6 file, converted to SB7 (but the extension remained
..SB6) -

and the failed one - started as SB69, converted to SB7 (still .SB6
extension), then I did a save AS of that project and saved as .SB7.

David

--
From David Troxell - Product Scope 7.8 - Encourager Software
Product Scope 7 Viewer - NO Registration Fee! Free to Use!
http://www.encouragersoftware.com/
Clarion Third Party Profile Exchange Online
http://encouragersoftware.com/profile/clarlinks.html
http://www.profileexchanges.com/blog/

[NewsArchive]

> OK, I thought that might be it.
>
> First, though I've upgraded my license to Armadillo 6 I'm still using 4.66
> for most of my projects. I tried 6.x on one project that's stored on a
> server. A Dell Vista laptop took more than 10 seconds to load and unpack
> the program (which is fairly small), versus about a second and a half when
> the same program was protected with 4.66.
>
> That's probably neither here nor there.
>
> What is the symptom that tells you that the stub didn't work?
>
> And are you SURE it's actually running?

Jane,

Testing under Vista 64 - Ultimate

AS an update to my tests - SAME install BUT compiled in SB6.9.2581, it
WORKS correctly - the STUB EXE IS run within the install, Armadillo can
write to the registry - and my keys are successfully accepted.

I used Run program - in [Execute Programs] area of script, and checked the
Wait for Program and Use ShellExecuteEx checkboxes as indicated in screen
shot AND it DOES work in SB6.9.2581.

BUT - using exact same method in RUN program in SB7 7.0.2680, in my tests,
is NOT working.

NOTE: I used the SAME .SB6 project file - compiled in SB6.9.2581 - and the
RUN program works within the install - copied the project file to another
folder - let SB7 7.0.2680 convert it, compiled in SB7 7.0.2680 AND the RUN
Program within the install DOES NOT work in SB7 7.0.2680.

Can anyone else confirm this - or am I the only one having a Run Program
problem in SB7 7.0.2680?

David

--
From David Troxell - Product Scope 7.8 - Encourager Software
Product Scope 7 Viewer - NO Registration Fee! Free to Use!
http://www.encouragersoftware.com/
Clarion Third Party Profile Exchange Online
http://encouragersoftware.com/profile/clarlinks.html
http://www.profileexchanges.com/blog/

[NewsArchive]

David,

>
> Testing under Vista 64 - Ultimate
>

I have uploaded a test project.

http://www.lindersoft.com/projects/runtest.zip

Please download, unzip and compile/run.

The RunTest.sb7 project installs and executes (and waits) a dummy.exe which
displays a "Hello, world!" text. It then returns to the installer and
displays the error code (should be 0). I have tested this on four different
x64 Windows versions (including Windows 7) and it works fine here.

BTW, this will install a dummy.exe so please run the "RunTest Uninstall" to
remove it.

Friedrich