References: uV9qF2v$CHA.3008@TK2MSFTNGP11.phx.gbl,
uS6ubz4$CHA.2100@TK2MSFTNGP12.phx.gbl

See the original conversation below:

I now have 2 systems, running windows XP. They are both running EXACTLY the
same code, both running as a service. They try to install a device driver.
Both systems have their driver signing policy to "Ignore". One node
generates:

[2005/09/26 16:17:33 568.217 Driver Install]
#-019 Searching for hardware ID(s): *windrvr6
#-198 Command line processed: C:\SHOUT\SHOUTip.exe
#I022 Found "*WINDRVR6" in c:\shout\sysfiles\windrvr\redist\windrvr6.inf;
Device: "WinDriver"; Driver: "WinDriver"; Provider: "Jungo"; Mfg: "Jungo";
Section name: "DriverInstall".
#I023 Actual install section: [DriverInstall.NT]. Rank: 0x00000000.
Effective driver date: 12/29/2004.
#I063 Selected driver installs from section [DriverInstall] in
"c:\shout\sysfiles\windrvr\redist\windrvr6.inf ".
#I320 Class GUID of device remains: {4D36E97D-E325-11CE-BFC1-08002BE10318}.
#I060 Set selected driver.
#-124 Doing copy-only install of "ROOT\SYSTEM\0002".
#E360 An unsigned or incorrectly signed file
"c:\shout\sysfiles\windrvr\redist\windrvr6.inf " for driver "WinDriver" will
be installed (Policy=Ignore). Error 0xe000022f: The third-party INF does not
contain digital signature information.

And the other:

[2005/09/26 23:03:17 1264.204 Driver Install]
#-019 Searching for hardware ID(s): *windrvr6
#-198 Command line processed: C:\SHOUT\SHOUTIP.exe
#I022 Found "*WINDRVR6" in c:\shout\sysfiles\windrvr\redist\windrvr6.inf;
Device: "WinDriver"; Driver: "WinDriver"; Provider: "Jungo"; Mfg: "Jungo";
Section name: "DriverInstall".
#I023 Actual install section: [DriverInstall.NT]. Rank: 0x00000000.
Effective driver date: 12/29/2004.
#I063 Selected driver installs from section [DriverInstall] in
"c:\shout\sysfiles\windrvr\redist\windrvr6.inf ".
#I320 Class GUID of device remains: {4D36E97D-E325-11CE-BFC1-08002BE10318}.
#I060 Set selected driver.
#-124 Doing copy-only install of "ROOT\SYSTEM\0002".
#E358 An unsigned or incorrectly signed file
"c:\shout\sysfiles\windrvr\redist\windrvr6.inf " for driver "WinDriver"
blocked (server install). Error 0xe000022f: The third-party INF does not
contain digital signature information.

Why does one block, and the other allow?!

On Wed, 9 Apr 2003 18:08:40 -0700, "Terry Hardie" wrote:



And on Thu, 10 Apr 2003 11:13:12 -0700, "Eliyas Yakub [MSFT]" replied:

Eliyas is correct. See the discussion at
http://msdn.microsoft.com/library/de...us/install/hh/
install/install-over_5f5ab2fb-a9a8-403f-a03b-372a16bb2223.xml.asp and
client-side v server-side installations.

Bryan S. Burgin
bburgin@online.microsoft.com

This posting is provided "AS IS" with no warranties, and confers no rights.

According to:

http://msdn.microsoft.com/library/de...bb2223.xml.asp
(Device Installation Types), our application fits the description of a
"client". Therefore, when our application (C:\SHOUT\SHOUTip.exe, as shown in
the log below), calls into SetupAPI, why does it think we are a server
install?!

Also, why do I get 2 different behaviours on 2 identical machines?

I have also tried to install it on a clean windows XP service pack 2
machine, and have reproduced the same "Blocked" problem.



"Terry Hardie" <TerryHardie@newsgroup.nospam> wrote in message
news:%23odmNYvwFHA.2932@TK2MSFTNGP10.phx.gbl...

Here is a description of "client-side" and "server-side" installations. In
one of your examples, it was a server-side installation and the other was a
client-side. You should be able to go through the descriptions to
determine what item is triggering the installation to be either client-side
or server-side.

http://msdn.microsoft.com/library/de...us/install/hh/
install/install-over_5f5ab2fb-a9a8-403f-a03b-372a16bb2223.xml.asp

Bryan S. Burgin
bburgin@online.microsoft.com

This posting is provided "AS IS" with no warranties, and confers no rights.

Bryan,

I'm starting to get a little frustrated here. What part of "2 identical
machines" did you miss? These are 2 systems, both running exactly the same
code, as a service, and 1 gives "client" behaviour and the other gives
"server" behaviour. There seems to be a bug in SetupAPI's ability to
determine if our application is a "server" or a "client".

Terry

""Bryan S. Burgin [MSFT]"" <bburgin@online.microsoft.com> wrote in message
news:y5TwSoexFHA.2396@TK2MSFTNGXA01.phx.gbl...

What is
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\Curr entVersion\Setup\LogLevel
set to (if it's present at all). Something is making setup believe that it
needs to be in server-side mode. Setting that value to 0x00006060 will
provide the most verbose output to the log and you can re-run the
server-side test.

Bryan S. Burgin
bburgin@online.microsoft.com

This posting is provided "AS IS" with no warranties, and confers no rights.