Running winetest on Vista

[Paul Vriens]

Hi,

I've started to run our winetest executable on Vista. The current output
is 7.8 MB or so, so we will never be able to sent it out just yet (1.5MB
limit).

I will start reducing the number of test failures on Vista (if I can of
course).

One thing that struck me and most likely it's due to Vista security is
that when I run winetest.exe it tells me that it couldn't retrieve the
list for the setupapi tests.

While investigating that (several hours up to now) I found (not 100%
sure though) that if an executable (like our setupapi_test.exe) has the
word setup in it and is not properly signed, Vista starts
complaining !!!

Just copying our setupapi_test.exe to paul.exe makes it possible to run
'paul.exe --list'.

Any ideas about the latter?

Cheers,

Paul.

[Dmitry Timoshkov]

"Paul Vriens"  wrote:
> While investigating that (several hours up to now) I found (not 100%
> sure though) that if an executable (like our setupapi_test.exe) has the
> word setup in it and is not properly signed, Vista starts
> complaining !!!
>
> Just copying our setupapi_test.exe to paul.exe makes it possible to run
> 'paul.exe --list'.
>
> Any ideas about the latter?

Does it help if you rename it to test_setupapi.exe?

[Paul Vriens]

On Mon, 2006-12-18 at 00:12 +0800, Dmitry Timoshkov wrote:
> "Paul Vriens"  wrote:
> > While investigating that (several hours up to now) I found (not 100%
> > sure though) that if an executable (like our setupapi_test.exe) has the
> > word setup in it and is not properly signed, Vista starts
> > complaining !!!
> >
> > Just copying our setupapi_test.exe to paul.exe makes it possible to run
> > 'paul.exe --list'.
> >
> > Any ideas about the latter?
>
> Does it help if you rename it to test_setupapi.exe?

No :-( As soon as setup is contained in the name it doesn't run. The
link that Kevin showed makes sense now.

Any idea how we can approach this? Do we indeed need to start adding
manifests to some of our tests? I'm afraid this is not the only thing
we're going to run into. IE7 and Vista already show some major changes
in things like advpack/crypt32/wintrust.

Cheers,

Paul.

[Dmitry Timoshkov]

"Paul Vriens"  wrote:
> > Does it help if you rename it to test_setupapi.exe?
>
> No :-( As soon as setup is contained in the name it doesn't run. The
> link that Kevin showed makes sense now.
>
> Any idea how we can approach this? Do we indeed need to start adding
> manifests to some of our tests? I'm afraid this is not the only thing
> we're going to run into. IE7 and Vista already show some major changes
> in things like advpack/crypt32/wintrust.

Well, a manifest is just an text (.xml) file with the resource type set
to RT_MANIFEST. Adding it into the resources is easy, the problem is that
wrc doesn't support that kind of a resource, so that support should be
added to wrc first.

[Frank Richter]

On 18.12.2006 16:50, Dmitry Timoshkov wrote:
> Well, a manifest is just an text (.xml) file with the resource type set
> to RT_MANIFEST. Adding it into the resources is easy, the problem is that
> wrc doesn't support that kind of a resource, so that support should be
> added to wrc first.

RT_MANIFEST is 24. Adding a resource of type 24, ID 1, should suffice;
no special handling in wrc should be needed.

E.g.:
    1 24 "myapplication.manifest"
or:
    1 24
    {
      "<assembly ..."
      "</assembly>"
    }

f-r-

[Kevin Koltzau]

On Sunday 17 December 2006 10:46 am, Paul Vriens wrote:
> While investigating that (several hours up to now) I found (not 100%
> sure though) that if an executable (like our setupapi_test.exe) has the
> word setup in it and is not properly signed, Vista starts
> complaining !!!
>
> Just copying our setupapi_test.exe to paul.exe makes it possible to run
> 'paul.exe --list'.
>
> Any ideas about the latter?

http://technet2.microsoft.com/WindowsVista/en/library/00d04415-2b2f-422c-b70...
Search for "Installer Detection Technology"

one of the criteria is 'Filename includes keywords like "install," "setup," "update," etc.'

The solution appears to involve adding a manifest to the setupapi_test.exe containing
<requestedExecutionLevel
   level="asInvoker"
   uiAccess="false"/>
which will prevent vistas installer detection heuristics from kicking in