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]

> 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

[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]

> 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,

I can still run this is you want me to - but as I have indicated in my most
recent newsgroup posting:

"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 project files were based on Product Scope 7 installs.

So it would seem, I have a problem with a * particular * Product Scope 7 SB
project, and I can send you the one that failed if need be.

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,

> I can still run this is you want me to - but as I have indicated in my
> most recent newsgroup posting:

Yes, please run it. Both SB69 and SB7 make use of the SAME run
functionality. There were only modifications in the SB7 CreateProcess call,
but you said that both CreateProcess and ShellExecuteEx failed -- so it's
caused by anothere thing. ShellExecuteEx did not change from SB69 to SB70.

Always check the return codes in such a case (here: %_SB_ERRORCODE and
%_SB_RETURNEX%). It's possible that this gives more information.

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

SetupBuilder is installation -- "point. click. ship"

-- Official Comodo Code Signing and SSL Certificate Partner

[NewsArchive]

> David,
>
>> I can still run this is you want me to - but as I have indicated in my
>> most recent newsgroup posting:
>
> Yes, please run it. Both SB69 and SB7 make use of the SAME run
> functionality. There were only modifications in the SB7 CreateProcess call,
> but you said that both CreateProcess and ShellExecuteEx failed -- so it's
> caused by anothere thing. ShellExecuteEx did not change from SB69 to SB70.
>
> Always check the return codes in such a case (here: %_SB_ERRORCODE and
> %_SB_RETURNEX%). It's possible that this gives more information.

Friedrich,

OK, ran the test you sent within Vista 64 with results in screen shot.

The failed SB7 project (run program within install) did go through
different versions of SB69 - through pre-release SB7 and finally gold SB7 -
so that might have made a difference.

I know you advise making a CLEAN project install with the latest SB when
there are problems.

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,

> OK, ran the test you sent within Vista 64 with results in screen shot.

Yes, that's the expected results! Thanks for testing it.

> The failed SB7 project (run program within install) did go through
> different versions of SB69 - through pre-release SB7 and finally gold
> SB7 -
> so that might have made a difference.

This should not make a difference. The "conversion" process from any
SB5/SB6 project to the SB7 "format" just adds some new properties -- it does
not change anything in the script. It should even be possible to open the
"SB7 converted" project in your SB6 IDE and compile/run it. Not
recommended, but should work <g>. Just for fun, I opened the RunTest.sb7 in
the old SB6 IDE and compiled/executed it. Worked without any problem on
Vista and Windows 7 (64-bit Ultimate).

Friedrich

[NewsArchive]

> David,
>
>> OK, ran the test you sent within Vista 64 with results in screen shot.
>
> Yes, that's the expected results! Thanks for testing it.
>
>> The failed SB7 project (run program within install) did go through
>> different versions of SB69 - through pre-release SB7 and finally gold
>> SB7 -
>> so that might have made a difference.
>
> This should not make a difference. The "conversion" process from any
> SB5/SB6 project to the SB7 "format" just adds some new properties -- it does
> not change anything in the script. It should even be possible to open the
> "SB7 converted" project in your SB6 IDE and compile/run it. Not
> recommended, but should work <g>. Just for fun, I opened the RunTest.sb7 in
> the old SB6 IDE and compiled/executed it. Worked without any problem on
> Vista and Windows 7 (64-bit Ultimate).

Friedrich,

Thanks for your help in this - when I started this Armadillo STUB EXE
venture - I had read from several on making it work - I thought originally
I had missed a step in the process.

Then at one stage, it looked more like an SB7 problem (yes, mine).

However, but as it turns out, it was a single SB7 project that was not
handling the RUN program in install correctly.

However, starting with another previous SB project very similar to the one
I was using, and now my latest (unreleased) install for Product Scope 7
DOES works correctly in Vista 64

(demo always worked in Vista 64, just a problem getting the registration
key to work properly with resorting to something like - right click desktop
shortcut and run as Administrator one time only).

So, I won't spend any more time tracking down what essentially happened to
a single SB7 project file.

Thanks again.

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,

> So, I won't spend any more time tracking down what essentially happened
> to a single SB7 project file.

I hate unsolved problems <g> If you are interested, you can send me the
project that does not work and a project that works. I'll then compare the
underlying script structure to see if there is a difference in the run
commands.

Friedrich

[NewsArchive]

> David,
>
>> So, I won't spend any more time tracking down what essentially happened
>> to a single SB7 project file.
>
> I hate unsolved problems <g>

Friedrich,

I understand...

> If you are interested, you can send me the
> project that does not work and a project that works. I'll then compare the
> underlying script structure to see if there is a difference in the run
> commands.

I just finished recompiling each project again - reset the Virtual Machine
snapshot - and confirmed one works, and the other does not.

I just sent the projects by email to you.

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]

>
> I just sent the projects by email to you.
>

Not received yet...

Friedrich

[NewsArchive]

>> I just sent the projects by email to you.
>>
>
> Not received yet...

Friedrich,

Well, possibly a web hosting email problem (on my side) - sent them by
alternate email method using Road Runner Broadband Cable modem email.

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]

Hi David,

> Well, possibly a web hosting email problem (on my side) - sent them by
> alternate email method using Road Runner Broadband Cable modem email.

Received!

In the "converted SB6 to SB7" project, you have QUIETREGISTER as "Command
Line" Run Parameter. In the "new" SB7 project, this parameter is missing.
Is it possible that this QUIETREGISTER causes the problem?

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

SetupBuilder is installation -- "point. click. ship"

-- Official Comodo Code Signing and SSL Certificate Partner

[NewsArchive]

> Hi David,
>
>> Well, possibly a web hosting email problem (on my side) - sent them by
>> alternate email method using Road Runner Broadband Cable modem email.
>
> Received!
>
> In the "converted SB6 to SB7" project, you have QUIETREGISTER as "Command
> Line" Run Parameter. In the "new" SB7 project, this parameter is missing.
> Is it possible that this QUIETREGISTER causes the problem?

Friedrich,

No, that particular command line parameter makes no difference - it's
specific to Armadillo use, and will display a registration form during the
install when included on the command line as shown in this screen shot.

The latest SB7 project file you received (one that works with RUN program
in install) was actually tested without that command line option - after
reading the Armadillo docs a bit more, in one of my updated tests - I added
that option.

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]

Hi David,

> No, that particular command line parameter makes no difference - it's
> specific to Armadillo use, and will display a registration form during the
> install when included on the command line as shown in this screen shot.
>
> The latest SB7 project file you received (one that works with RUN program
> in install) was actually tested without that command line option - after
> reading the Armadillo docs a bit more, in one of my updated tests - I
> added that option.

I checked the script internal parameters and the "Run Program" functions
have the same parameters in the SB6 and SB7 projects (except for the OS
Conditions, but this should not make a difference). It's an absolute
mystery to me.

It would be interesting to know what happens if you copy the "Run Program"
function from the SB6 project to the SB7 project. You can do this by
opening the SB6 and SB7 project in two SB7 IDE instances.

Friedrich

[NewsArchive]

Glad you got it figured out, David... and that my fabulous article hadn't
led you astray <g>

Jane

[NewsArchive]

> Glad you got it figured out, David... and that my fabulous article hadn't
> led you astray <g>

Jane,

Thanks for the article and some pointers - actually re-reading the article
really helped me understand the whole process a bit better -

I misinterpreted one of my tests AND thought I had it working - but I had
installed ANOTHER program that used STUB EXE method, and your article
helped me greatly in that area.

BTW, with Virtual Machine snapshots - we have come a LONG way from
re-installing OSs from 5 CD's - multiple times!

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,

> So it would seem, I have a problem with a * particular * Product Scope 7
> SB project, and I can send you the one that failed if need be.

Both projects (.sb6 and .sb7) have the same format, so it does not have
anything to do with the project per-se. You can even open the .sb7 project
back in the SB6 IDE and compile it.

I would suggest to check both %_SB_ERRORCODE and %_SB_RETURNEX% variables.
If the call to ShellExecuteEx/CreateProcess failed, this should give more
information.

Friedrich

[NewsArchive]

> Hi David,
>
>> No, that particular command line parameter makes no difference - it's
>> specific to Armadillo use, and will display a registration form during the
>> install when included on the command line as shown in this screen shot.
>>
>> The latest SB7 project file you received (one that works with RUN program
>> in install) was actually tested without that command line option - after
>> reading the Armadillo docs a bit more, in one of my updated tests - I
>> added that option.
>
> I checked the script internal parameters and the "Run Program" functions
> have the same parameters in the SB6 and SB7 projects (except for the OS
> Conditions, but this should not make a difference).

Friedrich,

Well, at least in my SB7 project - the OS conditions DOES make a
difference!

It was something I changed when I went back to the another SB project, not
realizing that it WAS the critical difference.

Using the failed RUN program within install SB7 project - I copied as you
requested - of course that RUN Program HAD the OS Independent condition
checkboxed.

Recompiled - successful!

OK, working with SAME project - Conditions - W2K - W7

Recompiled - NOT successful

Same project again - changed to OS Independent

Recompiled - Successful!

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,

> Using the failed RUN program within install SB7 project - I copied as you
> requested - of course that RUN Program HAD the OS Independent condition
> checkboxed.
>
> Recompiled - successful!
>
> OK, working with SAME project - Conditions - W2K - W7
>
> Recompiled - NOT successful
>
> Same project again - changed to OS Independent
>
> Recompiled - Successful!

I can't reproduce this here :-( If you change the Conditions in my
previously posted "RunTest.sb7" to W2K - W7, does this also not work?

Friedrich

[NewsArchive]

> David,
>
>> OK, I changed the conditions in your RunTest - it displays same results.
>>
>> This might be the difference though.
>>
>> OK, even though the install ITSELF is Run as Administrator - that alone is
>> not enough to make Armadillo write to the registry first time so that key
>> registration is accepted.
>>
>> The psverify.exe or Armadillo STUB EXE must be Vista - Windows 7
>> manifested as RequireAdministrator.
>
> This was just to test if the external application is executed or not.
>
> If the installer is running elevated and you start psverify.exe, then the
> elevated privileges are carried over to that application. Only if you have
> "Launch non-elevated under UAC" enabled, the app is started in the context
> of the "original" Standard User. So if the installer runs elevated and
> executes an external program, that program does not have any registry write
> access restrictions.

Friedrich,

Of course, you're the expert in this area, and you're right - the elevated
privileges carry over and what I did is not needed (STUB exe manifested as
RequireAdministrator). Just retested, and found that to be true.

However, the OS independent (OS conditions TAB) for the STUB EXE (Run
program from within install) is the only factor that remains consistent -
use it, Armadillo is written to registry and accepts keys - do not use it,
and the Armadillo process fails.

>
> IMO, the only way to find out what is going on is to check the
> %_SB_ERRORCODE and %_SB_RETURNEX% values. I can't reproduce this issue in
> any of our test application nor did we receive any similar report. I took
> your original project and copied the "Run Program" line (Conditions - W2K -
> W7) over to the RunTest.sb7 project. It executed a "dummy" psverify.exe
> without any problem. I am lost -- no way to reproduce it nor is there any
> logical explanation :-(

I did a display box with your code:

I am back from psverify.exe

Error Code: %_SB_ERRORCODE%

FOR the failed SB project

and the screen shot shows no error.

As far as reproducing it, would you not have to have the exact same
conditions as mine - Armadillo protect a software program (they use the
term STUB EXE because it doesn't really do anything, and is usually there
for a silent (no interaction result),

install it with at least one other Armadillo protected progam, and then
register one key to test on a FRESH Install of Vista or Window 7 64 so no
other software programs influenced the Armadillo process.

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,

> However, the OS independent (OS conditions TAB) for the STUB EXE (Run
> program from within install) is the only factor that remains consistent -
> use it, Armadillo is written to registry and accepts keys - do not use it,
> and the Armadillo process fails.

Would it be possible to add a simple debug message to the STUB EXE that
displays a "Hello, I am the STUB EXE" to see if it is really not executed in
this project.

BTW, and please check for both %_SB_ERRORCODE and %_SB_RETURNEX%

Friedrich

[NewsArchive]

> David,
>
>> However, the OS independent (OS conditions TAB) for the STUB EXE (Run
>> program from within install) is the only factor that remains consistent -
>> use it, Armadillo is written to registry and accepts keys - do not use it,
>> and the Armadillo process fails.
>
> Would it be possible to add a simple debug message to the STUB EXE that
> displays a "Hello, I am the STUB EXE" to see if it is really not executed in
> this project.
>
> BTW, and please check for both %_SB_ERRORCODE and %_SB_RETURNEX%

Friedrich,

Will do.

It might have to wait til tonight's overnight shift, though.

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,
>
>> Using the failed RUN program within install SB7 project - I copied as you
>> requested - of course that RUN Program HAD the OS Independent condition
>> checkboxed.
>>
>> Recompiled - successful!
>>
>> OK, working with SAME project - Conditions - W2K - W7
>>
>> Recompiled - NOT successful
>>
>> Same project again - changed to OS Independent
>>
>> Recompiled - Successful!
>
> I can't reproduce this here :-( If you change the Conditions in my
> previously posted "RunTest.sb7" to W2K - W7, does this also not work?

Friedich,

OK, I changed the conditions in your RunTest - it displays same results.

This might be the difference though.

OK, even though the install ITSELF is Run as Administrator - that alone is
not enough to make Armadillo write to the registry first time so that key
registration is accepted.

The psverify.exe or Armadillo STUB EXE must be Vista - Windows 7 manifested
as RequireAdministrator.

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,

> OK, I changed the conditions in your RunTest - it displays same results.
>
> This might be the difference though.
>
> OK, even though the install ITSELF is Run as Administrator - that alone is
> not enough to make Armadillo write to the registry first time so that key
> registration is accepted.
>
> The psverify.exe or Armadillo STUB EXE must be Vista - Windows 7
> manifested as RequireAdministrator.

This was just to test if the external application is executed or not.

If the installer is running elevated and you start psverify.exe, then the
elevated privileges are carried over to that application. Only if you have
"Launch non-elevated under UAC" enabled, the app is started in the context
of the "original" Standard User. So if the installer runs elevated and
executes an external program, that program does not have any registry write
access restrictions.

IMO, the only way to find out what is going on is to check the
%_SB_ERRORCODE and %_SB_RETURNEX% values. I can't reproduce this issue in
any of our test application nor did we receive any similar report. I took
your original project and copied the "Run Program" line (Conditions - W2K -
W7) over to the RunTest.sb7 project. It executed a "dummy" psverify.exe
without any problem. I am lost -- no way to reproduce it nor is there any
logical explanation :-(

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

SetupBuilder is installation -- "point. click. ship"

-- Official Comodo Code Signing and SSL Certificate Partner

[NewsArchive]

>> David,
>>
>>> Using the failed RUN program within install SB7 project - I copied as you
>>> requested - of course that RUN Program HAD the OS Independent condition
>>> checkboxed.
>>>
>>> Recompiled - successful!
>>>
>>> OK, working with SAME project - Conditions - W2K - W7
>>>
>>> Recompiled - NOT successful
>>>
>>> Same project again - changed to OS Independent
>>>
>>> Recompiled - Successful!
>>
>> I can't reproduce this here :-( If you change the Conditions in my
>> previously posted "RunTest.sb7" to W2K - W7, does this also not work?

Friedrich,

OK, back to testing (delayed til I finished major releases of Product Scope
7 and EZChangeLog Reporter)

This was tested in Windows 7 RTM x86 virtual machine. Compiled with latest
SB7.

I took your runtest.zip - as shipped in your zip - the run program
dummy.exe script was OS independent.

Copied the project to a run program dummy.exe script - w2k - windows server
2008 R2 (images say win7 but I included ALL OSs from w2K to end of OS
condition list)

I displayed a message box with basically this code on ALL tests after RUN
program

I am back from dummy.exe.

Error Code: %_SB_ERRORCODE%

Error Code: %_SB_RETURNEX%

The OS independent condition with RUN program was successful - the W2K -
Windows Server 2008 R2 WAS NOT as indicated in the attached images.

This happened with your runtest.zip and my special Product Scope 7
clipboard test (with Armadillo protected program was RUN Program script
included during install - successful if OS independent, NOT successful if
w2k - Windows Server 2008 R2).

My special Product Scope 7 Clipboard test was a FULLY working PS7 Clipboard
install (it installed ps7clipb.exe and all necessary DLLs to make the
program actually work).

David

--
From David Troxell - Product Scope 7.9 - 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]

Hi David,

> The OS independent condition with RUN program was successful - the W2K -
> Windows Server 2008 R2 WAS NOT as indicated in the attached images.

Thanks for the test results. Unfortunately, we can't reproduce this on any
of our Win7/Server7 machines :-( During the last few days, we tested and
debugged this scenario on a Win7 Ultimate x86, 3 different Win7 Ultimate x64
and one Win2008 R2 machine. It always displayed the "Hello world" message
in our tests :-(

Friedrich

[NewsArchive]

> Hi David,
>
>> The OS independent condition with RUN program was successful - the W2K -
>> Windows Server 2008 R2 WAS NOT as indicated in the attached images.
>
> Thanks for the test results. Unfortunately, we can't reproduce this on any
> of our Win7/Server7 machines :-( During the last few days, we tested and
> debugged this scenario on a Win7 Ultimate x86, 3 different Win7 Ultimate x64
> and one Win2008 R2 machine. It always displayed the "Hello world" message
> in our tests :-(

Friedrich,

I have tried this on 2 fresh installs (only Avast Anti-virus was installed)
of Windows 7 RTM Ultimate x86 virtual machine and Windows 7 RTM Ultimate
x64 virtual machine.

The w2k-windows-server2008-r2 RUN program OS conditions failed on both.

Attached in an EMAIL to you is zip of my actual install file for
w2k-windows-server2008-r2 and SB7 project file.

David

--
From David Troxell - Product Scope 7.9 - 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]

Hi David,

> Attached in an EMAIL to you is zip of my actual install file for
> w2k-windows-server2008-r2 and SB7 project file.

I can reproduce this with your w2k-windows-server2008-r2 on Win7 Ultimate
64-bit. There is definitely something going wrong here. Not sure if it is
compiler side or runtime side. Item in review. I'll post back when I have
some news.

Thanks,
Friedrich

[NewsArchive]

Compiler bug :-( This happens for ODBC and RUN functions if "OS
Independent" is not used on Server 2008, Windows 7, and Server 2008 R2!

Thank you for bringing this to my attention. Very tricky bug.

Friedrich

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

SetupBuilder is Windows installation -- "point. click. ship"

-- Official Comodo Code Signing and SSL Certificate Partner

[NewsArchive]

Very tricky.

This post's time stamp shows 3:41 AM
Your "I'll look into it" post shows 3:36 AM

It took you 5 whole minutes to find!!!!
Tricky indeed... very tricky <g>

Jane

[NewsArchive]

No kidding. Usually takes under 2 minutes.

--
Russell B. Eggen
www.radfusion.com
Clarion developers: www.radfusion.com/devs.htm

[NewsArchive]

> Very tricky.
>
> This post's time stamp shows 3:41 AM
> Your "I'll look into it" post shows 3:36 AM
>
> It took you 5 whole minutes to find!!!!
> Tricky indeed... very tricky <g>

<ROFL>

Friedrich

[NewsArchive]

> Well, documented, David.
>
> As the Ching says... "persistence furthers" <g>

Jane,

Thanks for the comment.

Just curious, as one of the noted and recognized experts in SetupBuilder
and other PC technical areas.

> "Stumbling" is not always appreciated as an appropriate technique for
> discoveries and inventions - BUT, it does have it's place from time to
> time! :-D

Have you ever applied the Stumbling technique to some of your own
solutions! :-D

David

--
From David Troxell - Product Scope 7.9 - 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]

> Compiler bug :-( This happens for ODBC and RUN functions if "OS
> Independent" is not used on Server 2008, Windows 7, and Server 2008 R2!
>
> Thank you for bringing this to my attention. Very tricky bug.

Friedrich,

Well, kinda of a fluke on my part to have even asked about it in the first
place in the newsgroup.

Between Jane Fleming's Clarion Magazine article and instructions from
someone else on creating Armadillo STUB.EXE to include in install - I HAD
all the answers I needed -

BUT - because I was a "fanatic" about OS requirements in the install -
starting minimally at W2K - as I looked at the General Installer Function -
Run Program and the various tabs - I decided to do a checkbox starting at
W2K - AND, of course, that revealed the "bug".

SO, the question to Jane to start this whole thread! :-D

BUT, when I used two SIMILAR SB projects to do some testing, not realizing
in one of the projects, I DID NOT OS condition it, and of course, stumbled
onto the answer I needed.

"Stumbling" is not always appreciated as an appropriate technique for
discoveries and inventions - BUT, it does have it's place from time to
time! :-D

David

--
From David Troxell - Product Scope 7.9 - 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]

Hi David,

> "Stumbling" is not always appreciated as an appropriate technique for
> discoveries and inventions - BUT, it does have it's place from time to
> time! :-D

Absolutely :-)

BTW, this compiler bug is in both SB6 and SB7! Build 2481 introduced it on
January 19, 2009 when we added built-in support for Windows 7 and Windows
Server 2008 R2).

Thanks again for the very good bug report!

Friedrich

[NewsArchive]

Well, documented, David.

As the Ching says... "persistence furthers" <g>

Jane

[NewsArchive]

"ex spurt"... as in a steady drip, David??? LOL...

Actually, as far as inventions and innovations go, I think "stumbling" has a
huge place. After all, if something were already known it wouldn't be much
of an innovation, would it?

As far as my own forays in the world of technology.... I'd rather be lucky
than good any day :-)

jf

[NewsArchive]

> "ex spurt"... as in a steady drip, David??? LOL...

Jane,

OK, I'll be careful with THAT phrase from now one :-D - but truth is - WHEN
we hit the "brick wall", there are a few we turn to - and you happen to be
"ONE" of them.

> Actually, as far as inventions and innovations go, I think "stumbling" has a
> huge place. After all, if something were already known it wouldn't be much
> of an innovation, would it?
>
> As far as my own forays in the world of technology.... I'd rather be lucky
> than good any day :-)

AND another phrase that seems to fit as well.

To quote Susan Pichotta of icons-icons.com -

"Done is better than perfect!"

David

--
From David Troxell - Product Scope 7.9 - 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]

To quote Mae West...

"Goodness had nothing to do with it" <g>

Jane Fleming