Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

"__<Component>" in Windows Installer Log file

16 views
Skip to first unread message

Gerben

unread,
Sep 24, 2003, 9:46:24 AM9/24/03
to
Could somebody explain the following entries from a Windows Installer log
file:

MSI (s) (9C:90) : Component: __WINZIP32.EXE66; Installed: Null; Request:
Local; Action: Local
MSI (s) (9C:90) : Component: __WZ.COM65; Installed: Null; Request: Local;
Action: Local
MSI (s) (9C:90) : Component: WINZIP32.EXE; Installed: Local; Request:
Local; Action: Local
MSI (s) (9C:90) : Component: WZ.COM; Installed: Local; Request: Local;
Action: Local

I'm wondering what the "__<Component>" means. The components with the "__"
are not my winzip.msi. __Winzip32.exe66 looks very much like Winzip32.exe
which is indeed in the MSI package. But the "Installed" property is not the
same. Confusing!

TIA,
Gerben


Phil Wilson

unread,
Sep 24, 2003, 8:57:29 PM9/24/03
to
Resending:
Are there any other references to those components in the log? When you say
those components are not in your MSI file, how do you know? Where did you look?
Did you look at the Component table with Orca? I suspect your tool is creating
installer Component names based on the file names.
--
Phil Wilson [MVP Windows Installer]
----
"Gerben" <tui...@hotmail.com> wrote in message
news:ezvfCJqg...@TK2MSFTNGP11.phx.gbl...

Gerben

unread,
Sep 25, 2003, 2:12:30 AM9/25/03
to
The MSI package is created with with Wise Package Studio 4.61. I searched
through all the tables to find the strange components, but I could not
locate them. There are no other references to these components in the log
file. And Wise is indeed creating components with the name of the keypath
file. What do you think?


Stefan Krueger [MVP]

unread,
Sep 25, 2003, 5:27:02 AM9/25/03
to
> I searched through all the tables to find the strange components

Did you do this with Orca?

--
Stefan Krueger
Microsoft Windows Installer MVP

Please post your questions in the newsgroup or vist one of these web sites:

Windows Installer FAQ
http://www.msifaq.com - http://www.msifaq.de

InstallSite - Resources for Setup Developers
http://www.installsite.org
http://www.installsite.de (GERMAN)


JKHemker

unread,
Sep 25, 2003, 6:48:57 AM9/25/03
to
Stefan,
The __components are not there and thus cannot be found even using Orca:-)

I always found that log entries for __<Components> are created for exactly
those components containing MSI entry points (e.g. MSI-shortcuts; extension
or class registrations). The names of the "dummy" components seem to be
built based on the original component using a "__" prefix and a postfix with
a number starting at 65. (so if the log file refers to __WINZIP32.EXE66, I
am sure that there IS a component named WINZIP32.EXE containing MSI entry
points - in this case probably a shortcut and extensions/verbs).

Using the idea of dummy __components = sub-components for those resources
of a real component being MSI entry points always appeared reasonable to me
and consistent with my log files, BUT:
Unfortunately, I could not find any official MS source or developer
confirming the relation to MSI entry points, so I may completely be wrong.

Josef Hemker
MCSE


"Stefan Krueger [MVP]" <ms0...@nwsgrp.REMOVETHIS.installsite.net> schrieb im
Newsbeitrag news:u#EZEd0gD...@tk2msftngp13.phx.gbl...

Friedrich Muecke

unread,
Sep 27, 2003, 3:38:09 PM9/27/03
to
samesame

"JKHemker" <josef....@onlinehome.de> wrote in message
news:bkuh5q$2dr$1...@online.de...

0 new messages