Frank said:
Hi Heidi and Nick,
thank you for this tip. I used the Dependency Walker.
I added few dlls to system32 folder.
The Dependency Walker showed no errors.
The msinfo32 main windows is to see, but the contents of windows
is white and empty, no system information to see.
I don't understand the Problem!
Which services or components shows the information?
Thanks.
Ok - I'm intrigued. What did you add? I did a quick run of MSINFO32.EXE
using FILEMON on my XP Pro system to see what it's bringing in when it
works.
It seems to use:
comctrl32.dll
ntdll.dll
kernel32.dll
unicode.nls
locale.nls
mfc42u.dll
msvcrt.dll
gdi32.dll
user32.dll
ole32.dll
advapi32.dll
rpcrt4.dll
oleaut32.dll
shell32.dll
shlwapi.dll
ctype.nls
sortkey.nls
entapi.dll
psapi.dll
netapi32.dll
rpcss.dll
uxtheme.dll
syntpfcs.dll
version.dll
msctf.dll
imm32.dll
setupapi.dll
clbcatq.dll
comres.dll
urlmon.dll
secur32.dll
apphelp.dll
etc.
Also quite a few things under
\windows\pchealth\helpctr\system\sysinfo
and
\windows\pchealth\helpctr\binaries\helpctr.exe
That last one would help "Help and Support Services" needs to be added.
Various other components can be implied from the list above (which isn't
complete - rather than typing EVERYTHING found in the filemon log, I stopped
after a while). For example: "Primitive: Clbcatq" is most likely needed.
I've listed a lot of stuff (and there is more in the filemon log). The next
step would be to see if FILEMON itself runs on the XPE image and trace using
it to see where the msinfo app fails. Most likely, there will be some
DLL/EXE lookup, etc. that fails on the XPE build.