Setupai.log errors

Martin Spence · Guest

Looking for the benefit of some experience here. I see many errors in the
setupai.log and was wondering if I should worry about them. Typical errors
are:

OLE Control "C:\Program Files\Common Files\Microsoft Shared\DAO\dao360.dll".
Error 126: The specified module could not be found.
#E291 Failed to register OLE server "C:\Program Files\Common Files\Microsoft
Shared\DAO\dao360.dll". Error 126: The specified module could not be found.
#E089 Failed to load the OLE Control "C:\WINDOWS\system32\licwmi.dll". Error
126: The specified module could not be found.
#E291 Failed to register OLE server "C:\WINDOWS\system32\licwmi.dll". Error
126: The specified module could not be found.

Any words of wisdom would be very much appreciated.

Martin

Google · Sponsor

KM · Guest

Martin,

You should only worry about those errors if you care to have DAO (Data Access Objects) working at run time.

You also didn't include some of the dependencies of the licwmi library (did you do the auto-resolve dependencies?) but that should
not affect the XPe runtime. (IIRC, licwmi is used for WInodws Activation process during regular XP setup)

--
=========
Regards,
KM

Martin Spence · Guest

Thanks KM. That is what is weird. I do the auto-resolve and still have all
these dependencies missing in the setupapi.log. I see probably over 40-50
of these related to OLE Server registration. Am I doing somthing wrong? My
image works fine. But now I have time to dig into the logs and look to see
what is going on.

Martin
"KM" <konstmor@nospam_yahoo.com> wrote in message
news:eta1zsDPIHA.4688@TK2MSFTNGP06.phx.gbl...

KM · Guest

Martin,

In general, it is ok to see a bunch of errors in the log files on XPe images. Simply because the componentization there has been
done on the binary level (vs XP Pro), not at the source code level in XP tree. In other words, some dynamic dependencies may not get
included in your image and hence you see the errors but it doesn't mean you don't get the functionality you are up to.
I guess you start to worry when something you wanted doesn't work. Then you dig more into the logs to see what's going on there.
Often, preventive care approach doesn't work well on XPe or otherwise it's a big effort for any XPe project you do.

--
=========
Regards,
KM

"Martin Spence" <martinspence@charter.net> wrote in message news:475f0e31$0$5717$c3e8da3@news.astraweb.com...