Hello again,
I saw this message (in fact many occurences of this message)in the
setupapi
file after first bootup during fbreseal. What does it mean? Could this be
the
reason why problems occur after bootup?
#W389 No [STRINGS.0409] or [STRINGS.0009] section in
C:\WINDOWS\inf\oem3.inf, using [STRINGS] instead.
Here's a part of the entire file.
[2006/02/02 13:17:54 544.3 Driver Install]
#-019 Searching for hardware ID(s):
pci\ven_8086&dev_2449&subsys_30138086&rev_03,pci\ven_8086&dev_2449&subsys_30138086,pci\ven_8086&dev_2449&cc_020000,pci\ven_8086&dev_2449&cc_0200
#-018 Searching for compatible ID(s):
pci\ven_8086&dev_2449&rev_03,pci\ven_8086&dev_2449,pci\ven_8086&cc_020000,pci\ven_8086&cc_0200,pci\ven_8086,pci\cc_020000,pci\cc_0200
#-198 Command line processed: C:\WINDOWS\system32\services.exe
#I393 Modified INF cache "C:\WINDOWS\inf\INFCACHE.1".
#W389 No [STRINGS.0409] or [STRINGS.0009] section in
C:\WINDOWS\inf\oem3.inf, using [STRINGS] instead.
#I022 Found "PCI\VEN_8086&DEV_2449" in C:\WINDOWS\inf\oem3.inf; Device:
"Intel(R) PRO/100 Network Connection"; Driver: "Intel(R) PRO/100 Network
Connection"; Provider: "Intel"; Mfg: "Intel"; Section name:
"XP_D110K.ndi".
#I023 Actual install section: [XP_D110K.ndi.NTx86]. Rank: 0x00002001.
Effective driver date: 03/04/2003.
#I022 Found "PCI\VEN_8086&DEV_2449&SUBSYS_30138086" in
C:\WINDOWS\inf\oem3.inf; Device: "Intel(R) PRO/100 VE Network Connection";
Driver: "Intel(R) PRO/100 VE Network Connection"; Provider: "Intel"; Mfg:
"Intel"; Section name: "XP_D110K.ndi".
#I023 Actual install section: [XP_D110K.ndi.NTx86]. Rank: 0x00000001.
Effective driver date: 03/04/2003.
#I022 Found "PCI\VEN_8086&DEV_2449&SUBSYS_30138086&REV_03" in
C:\WINDOWS\inf\oem3.inf; Device: "Intel(R) PRO/100 VE Network Connection";
Driver: "Intel(R) PRO/100 VE Network Connection"; Provider: "Intel"; Mfg:
"Intel"; Section name: "XP_D110K.ndi".
#I023 Actual install section: [XP_D110K.ndi.NTx86]. Rank: 0x00000000.
Effective driver date: 03/04/2003.
#I022 Found "PCI\VEN_8086&DEV_2449&SUBSYS_30138086" in
C:\WINDOWS\inf\net557.inf; Device: "Intel(R) PRO/100 VE Network
Connection";
Driver: "Intel(R) PRO/100 VE Network Connection"; Provider: "Microsoft";
Mfg:
"Intel"; Section name: "D110K.ndi".
#I023 Actual install section: [D110K.ndi.NTx86]. Rank: 0x00000001.
Effective
driver date: 07/01/2001.
#I022 Found "PCI\VEN_8086&DEV_2449&SUBSYS_30138086&REV_03" in
C:\WINDOWS\inf\net557.inf; Device: "Intel(R) PRO/100 VE Network
Connection";
Driver: "Intel(R) PRO/100 VE Network Connection"; Provider: "Microsoft";
Mfg:
"Intel"; Section name: "D110K.ndi".
#I023 Actual install section: [D110K.ndi.NTx86]. Rank: 0x00000000.
Effective
driver date: 07/01/2001.
#I022 Found "PCI\VEN_8086&DEV_2449&SUBSYS_30138086&REV_03" in
C:\WINDOWS\inf\net557.inf; Device: "Intel(R) PRO/100 VE Network
Connection";
Driver: "Intel(R) PRO/100 VE Network Connection"; Provider: "Microsoft";
Mfg:
"Intel"; Section name: "D110KMP.ndi".
#I023 Actual install section: [D110KMP.ndi.NTx86]. Rank: 0x00000000.
Effective driver date: 07/01/2001.
#-166 Device install function: DIF_SELECTBESTCOMPATDRV.
#I063 Selected driver installs from section [XP_D110K.ndi] in
"c:\windows\inf\oem3.inf".
#I320 Class GUID of device remains:
{4D36E972-E325-11CE-BFC1-08002BE10318}.
#I060 Set selected driver.
#I058 Selected best compatible driver.
#-166 Device install function: DIF_ALLOW_INSTALL.
#W389 No [STRINGS.0409] or [STRINGS.0009] section in
c:\windows\inf\oem3.inf, using [STRINGS] instead.
#-166 Device install function: DIF_INSTALLDEVICEFILES.
#I124 Doing copy-only install of
"PCI\VEN_8086&DEV_2449&SUBSYS_30138086&REV_03\4&1351887D&0&40F0".
#W389 No [STRINGS.0409] or [STRINGS.0009] section in
c:\windows\inf\oem3.inf, using [STRINGS] instead.
#-011 Installing section [XP_D110K.ndi.NTx86] from
"c:\windows\inf\oem3.inf".
#W389 No [STRINGS.0409] or [STRINGS.0009] section in
c:\windows\inf\oem3.inf, using [STRINGS] instead.
#-166 Device install function: DIF_REGISTER_COINSTALLERS.
#W389 No [STRINGS.0409] or [STRINGS.0009] section in
c:\windows\inf\oem3.inf, using [STRINGS] instead.
#I056 Coinstallers registered.
#-166 Device install function: DIF_INSTALLINTERFACES.
#W389 No [STRINGS.0409] or [STRINGS.0009] section in
c:\windows\inf\oem3.inf, using [STRINGS] instead.
#-011 Installing section [XP_D110K.ndi.NTx86.Interfaces] from
"c:\windows\inf\oem3.inf".
#I054 Interfaces installed.
#-166 Device install function: DIF_INSTALLDEVICE.
#W389 No [STRINGS.0409] or [STRINGS.0009] section in
c:\windows\inf\oem3.inf, using [STRINGS] instead.
#I123 Doing full install of
"PCI\VEN_8086&DEV_2449&SUBSYS_30138086&REV_03\4&1351887D&0&40F0".
#W389 No [STRINGS.0409] or [STRINGS.0009] section in
c:\windows\inf\oem3.inf, using [STRINGS] instead.
#I121 Device install of
"PCI\VEN_8086&DEV_2449&SUBSYS_30138086&REV_03\4&1351887D&0&40F0" finished
successfully.
#I292 Changing device properties of
"PCI\VEN_8086&DEV_2449&SUBSYS_30138086&REV_03\4&1351887D&0&40F0".
Many thanks!
Rei said:
Hello,
If I have already added a driver for say, my LAN adapter, in the image
via a
component during the image build, and later, after FBA, I update this
driver
say to version x+1. (So that I do not have to rebuild another image)
During this time, I also install an application that has performs some
checks on the LAN adapter (maybe it queries the LAN adapter for its
status)
every bootup.
I then run fbreseal on this image. Will the update of the LAN driver
cause
any problems, since there was an earlier version of the driver in the
image
before my manual update. Does the first bootup after fbreseal reinstall
the
LAN driver?
Sorry if my question sounds silly. I don't really understand the workings
of
fbreseal. Is it a good idea to update drivers after FBA run, and then
reseal
the image?
Also, is it normal for XPE to ask the user to reboot after the first
bootup
after fbreseal, due to "New devices found and drivers installed?", even
though the image had been created from the same hardware?
Thank you!
