Analyze components on a running Build

  • Thread starter Thread starter KM
  • Start date Start date
K

KM

Yaron,

There is no such log you are looking for.
All info about the installed components you get on XPe run time image is the following:
- registry entries & files (e.g., existence of user32.dll tells you that "Win32 API - User" component was included). You can
also analyze file datetime stamps and version info.
- FBAlog.txt
- setupapi.log
- application specific logs (like DUA or IIS)

The point is that it is not easy (if not say very hard) to reverse engineering an XPE run time.
 
Yaron,
During FBA your machine creates a directory in the Windows directory called
FBA and inside that directory a file is created called FBALog. All you have
to do is create an app or script to parse the file.

Regards,

Sean Gahan
 
Hi,

I am trying to compare a few different beta-builds we develop,
and for debug purposes, I need to be able to recognize which component were
used in creating the image. in other words, is there a way/tool that I can
use to run on a working XPe build that will summarize which components are
installed? is there a log saved somewhere that I can use?

thanks,

YaronM
 
bad news, but thanks for your help.

YaronM


KM said:
Yaron,

There is no such log you are looking for.
All info about the installed components you get on XPe run time image is
the following:
- registry entries & files (e.g., existence of user32.dll tells you
that "Win32 API - User" component was included). You can
also analyze file datetime stamps and version info.
- FBAlog.txt
- setupapi.log
- application specific logs (like DUA or IIS)

The point is that it is not easy (if not say very hard) to reverse
engineering an XPE run time.
Click to expand...
 
Back
Top