Re: 2 identical projects ---> 2 compiled exec causing Vista different response

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

Bingo!
I have discovered the source of the problem but I do not
understand the mechanism behind it.
I need some heavy guns in this forum to pitch in.
The problem appears to be the underscore in the saved project file's name.
Originally, the project was created and saved as Project1.vbp.
The compiled executive runs fine from within Inno Setup in Vista
environment.
I have several apps I am workin on setup now.
To distinquish between each app I renamed Project1.vbp to ADP_setup.vbp, and
the exe file compiled started having problem in Vista.
Removing the underscore, and using only ADP.vbp removes the problem.
How that simple underscore can influance the compiler output and as a
consequence Vista UAC response?
Your comments deeply appreciated,
Jack

"Jack" <replyto@it> wrote in message
news:uXj89JrQJHA.144@xxxxxxxxxxxxxxxxxxxxxxx
Hello,
I have posted that question in Inno Setup newsgroup before
realizing that it is vbasic problem not Inno's.
I created Project1 a few days ago. The compiled exec1.exe file is used
with
Inno Setup.
I am testing the Inno setup under Vista Ultimate running in VPC, as a
standard user with UAC turned on.
When I start the setup, User Account Control kicks in and gives me an
option
to continue as Administrator.
There are not other choices except 'Cancel' setup.When I select to
continue
the setup program runs in elevated state.

All was running fine, until I modifed Project1 (nothing significant, and I
do not even remember what the modification). Now, each time running Inno
Setup UAC in Vista kicks in with the following error:
"
Unable to execute file:
...\adp_inno.exe
CreateProcess failed: code 740
The requested operation requires elevation.
"
That message appears BEFORE exec1.exe run. The breakpoint set as the first
line of code in Sub Main() is never triggered.
But I tested that it is not the code problem or Inno script problem.
I have created a new Project2, copied ALL code from Project1 and created
the
new exec1.exe.
That file does not cause any problem.

What I need is your help to find out, why the executable compiled in
Project1 causes Vista UAC problem, but the same code compiled in Project 2
does not. Both project properties are the same (set at default).
I am using vbasic5 and I can repeat both compilation many times with
exactly
the same end result.
Thanks,
Jack






.

Relevant Pages