Re: KM come in pls:FBA hangs at installing components...

As you said, I switched to very minimal configuration (English,
Minlogon,CMD) and removed hardware as possible as I could, but I got only
one result:FBA hangs at registering components and FBAlog.txt is the same as
the first time I post and FBALaunch does not be executed at all.

Would it possible that it is caused by SP1? Would it be better to switch to
SP2?

"KM" <konstmor@xxxxxxxxxxxxxxxx> дÈëÓʼþ
news:OexuGxaTFHA.3544@xxxxxxxxxxxxxxxxxxxxxxx
> Maverick,
>
> Hmmm.. If Minlogon image showed the same problem it still could be the
hardware.
> Then there is no need to debug the issue with such heavy image you sent
the SetupApi.log and Fbalog.txt for.
>
> You should switch to very minimal configuration (English, Minlogon,CMD),
remove everything you can remove from that configuration
> and deploy it to repro the problem.
>
> From hardware side you should also remove any removable storages,
disconnect any peripherals.
>
> Regards,
> KM
>
> > I've tried using MinLogon and Command Shell, the lest configuration in
my
> > image, but got the same result: hangs at Installing components.
> >
> > I'll try Kernel Debugger later.
> >
> > "KM" <konstmor@xxxxxxxxxxxxxxxx> дÈëÓʼþ
> > news:O19bzZOTFHA.2756@xxxxxxxxxxxxxxxxxxxxxxx
> >> Maverick,
> >>
> >> Well... I still see the Terminal Services Core being included.
> >>
> >> Although the problem doesn't seem to be related to the
hardware/drivers.
> > Rather some software layer is the cause.
> >> I only wonder why nothing in the FBALog.
> >>
> >> You can have a very hard-to-proceed-with approach of making a small
image
> > that would work fine on the target (as less software
> >> component as possible) and then adding component by component and
> > re-deploying the image to see what component makes the continuous
> >> reboots during FBA.
> >>
> >> One more "debugging" thing you could implement in your image. Add a few
> > FBA Generic command to the image that will launch CMD.EXE
> >> (and wait for it to finish) at various FBA phases (something like 2000,
> > 3000, 4000, etc.). Having the CMD launched would interrupt
> >> the FBA process and you would be able to explore the image a little bit
to
> > see what's going on there. For instance, launch regedit
> >> from the CMD prompt and copy/save the
> > [HKLM\Test\CurrentControlSet\Control\WindowsEmbedded\FBA] key content.
Then
> > you compare the
> >> .reg files and see what happened at the different phases.
> >> Btw, it may also help if you analyze the key with your current deployed
> > image that continuously reboots or hangs.
> >>
> >> After all, you can hook up with KD (Kernel Debugger) to see if anything
> > useful is printed during FBA that may help you to understand
> >> why the hang or reboot happens.
> >>
> >> --
> >> Regards,
> >> KM, BSquare Corp.
> >>
> >>
> >> > Hi, KM
> >> >
> >> > After I change my image's language from Chinese to English, after
> > Installing
> >> > PnP devices, FBA would hang at Installing components...
> >> >
> >> > Here is my FBALog.txt. Attached is SetupApi.log.
> >> >
> >> >
> >> > Saturday, April 30, 2005
> >> >
> >> > 10:18:46 AM - [FBASetProgressText] Setting PNP Flag...
> >> > 10:19:10 AM - [FBASetProgressText] Initializing...
> >> > 10:19:10 AM - [CallEntryPointThread] C:\WINDOWS\FBA\FBALIB.DLL,
> >> > FBAInitialize
> >> > 10:19:10 AM - [FBASetProgressText] Setting SystemPrefix...
> >> > 10:19:11 AM - [FBASetProductKey] Evaluation product key
> >> > 10:19:11 AM - [FBASetProgressText] Initializing User Profiles...
> >> > 10:19:14 AM - [CallEntryPointThread] C:\WINDOWS\FBA\FBALIB.DLL,
> > FBAStep1
> >> > 10:19:14 AM - [CallEntryPointThread] C:\WINDOWS\FBA\FBALIB.DLL,
> >> > FBASetSetupInfo
> >> > 10:19:14 AM - [FBASetProgressText] Installing System Security...
> >> > 10:19:41 AM - [FBAInstallSecurity] Successfully set security!
> >> > 10:19:41 AM - [CallEntryPointThread] C:\WINDOWS\FBA\FBASEC.DLL,
> >> > FBAInstallSecurityPhase1
> >> > 10:19:41 AM - [FBASetProgressText] Registering Components...
> >> > 10:19:41 AM - [CallEntryPointThread] C:\WINDOWS\system32\atl.dll,
> >> > DllRegisterServer
> >> > 10:19:42 AM - [CallEntryPointThread]
C:\WINDOWS\system32\netcfgx.dll,
> >> > DllRegisterServer
> >> > 10:19:43 AM - [CallEntryPointThread]
C:\WINDOWS\system32\netman.dll,
> >> > DllRegisterServer
> >> > 10:19:44 AM - [CallEntryPointThread] C:\WINDOWS\system32\msctf.dll,
> >> > DllRegisterServer
> >> > 10:19:44 AM - [CallEntryPointThread]
C:\WINDOWS\system32\rsaenh.dll,
> >> > DllRegisterServer
> >> > 10:19:45 AM - [CallEntryPointThread]
C:\WINDOWS\system32\dssenh.dll,
> >> > DllRegisterServer
> >> > 10:19:45 AM - [CallEntryPointThread]
C:\WINDOWS\system32\initpki.dll,
> >> > DllInstall, z CertificateUIServices
> >> > 10:19:47 AM - [CallEntryPointThread]
C:\WINDOWS\system32\initpki.dll,
> >> > DllInstall, z CoreCertificateServices
> >> > 10:19:47 AM - [CallEntryPointThread]
C:\WINDOWS\system32\initpki.dll,
> >> > DllInstall, z CryptographicNetworkServices
> >> > 10:19:47 AM - [CallEntryPointThread] C:\WINDOWS\FBA\FBAREG.DLL,
> >> > FBARegisterDLLsPhase1
> >> > 10:19:47 AM - [FBASetProgressText] Installing Components...
> >> > 10:19:47 AM - [FBASetProgressText] Registering Class Installers...
> >> > 10:19:48 AM - [FBAStartService] PlugPlay -> Waiting...
> >> > 10:19:49 AM - [FBAStartService] PlugPlay -> Running
> >> > 10:19:49 AM - [FBAStartService] PlugPlay -> Finished Waiting
> >> > 10:19:51 AM - [ScanQueue: File Exists]
> > C:\WINDOWS\System32\storprop.dll
> >> > 10:19:51 AM - [FBAInstallPnpClassInstallers] Class Files Present:
> >> > cdrom.inf
> >> > 10:19:52 AM - [ScanQueue: File Exists]
> > C:\WINDOWS\System32\storprop.dll
> >> > 10:19:52 AM - [FBAInstallPnpClassInstallers] Class Files Present:
> > disk.inf
> >> > 10:19:53 AM - [FBAInstallPnpClassInstallers] Class Files Present:
> >> > display.inf
> >> > 10:19:54 AM - [FBAInstallPnpClassInstallers] Class Files Present:
> > fdc.inf
> >> > 10:19:55 AM - [FBAInstallPnpClassInstallers] Class Files Present:
> > hal.inf
> >> > 10:19:56 AM - [FBAInstallPnpClassInstallers] Class Files Present:
> >> > input.inf
> >> > 10:19:57 AM - [FBAInstallPnpClassInstallers] Class Files Present:
> >> > keyboard.inf
> >> > 10:19:58 AM - [FBAInstallPnpClassInstallers] Class Files Present:
> >> > machine.inf
> >> > 10:19:58 AM - [FBAInstallPnpClassInstallers] Class Files Present:
> >> > monitor.inf
> >> > 10:19:59 AM - [FBAInstallPnpClassInstallers] Class Files Present:
> >> > mshdc.inf
> >> > 10:20:00 AM - [FBAInstallPnpClassInstallers] Class Files Present:
> >> > msmouse.inf
> >> > 10:20:01 AM - [FBAInstallPnpClassInstallers] Class Files Present:
> >> > msports.inf
> >> > 10:20:02 AM - [FBAInstallPnpClassInstallers] Class Files Present:
> >> > ntapm.inf
> >> > 10:20:03 AM - [FBAInstallPnpClassInstallers] Class Files Present:
> >> > netclass.inf
> >> > 10:20:04 AM - [FBAInstallPnpClassInstallers] Class Files Present:
> > usb.inf
> >> > 10:20:05 AM - [FBAInstallPnpClassInstallers] Class Files Present:
> >> > wdmaudio.inf
> >> > 10:20:06 AM - [FBAInstallPnpClassInstallers] Class Files Present:
> >> > volume.inf
> >> > 10:20:06 AM - [CallEntryPointThread] C:\WINDOWS\FBA\FBAPNP.DLL,
> >> > FBAInstallPnpClassInstallers
> >> > 10:20:07 AM - [FBAStartService] PlugPlay -> Already Running
> >> > 10:20:07 AM - [FBASetProgressText] Installing PNP Devices...
> >> > 10:20:10 AM - [FBAAddDevInstanceId] ROOT\LEGACY_RDPWD\0000
> >> > 10:20:11 AM - [FBAInstallNullDriver] ROOT\LEGACY_RDPWD\0000
> >> > 10:20:11 AM - [FBAAddDevInstanceId] ROOT\LEGACY_TDPIPE\0000
> >> > 10:20:11 AM - [FBAInstallNullDriver] ROOT\LEGACY_TDPIPE\0000
> >> > 10:20:11 AM - [FBAAddDevInstanceId] ROOT\LEGACY_TDTCP\0000
> >> > 10:20:11 AM - [FBAInstallNullDriver] ROOT\LEGACY_TDTCP\0000
> >> > 10:20:11 AM - [FBAAddDevInstanceId] ROOT\SYSTEM\0001
> >> > 10:20:15 AM - [FBAAddDevInstanceId] ROOT\PCI_HAL\0000
> >> > 10:20:18 AM - [FBAAddDevInstanceId] ROOT\RDPDR\0000
> >> > 10:20:21 AM - [FBAAddDevInstanceId] ROOT\RDP_KBD\0000
> >> > 10:20:26 AM - [FBAAddDevInstanceId] ROOT\FTDISK\0000
> >> > 10:20:29 AM - [FBAAddDevInstanceId] ROOT\DMIO\0000
> >> > 10:20:33 AM - [FBAAddDevInstanceId] ROOT\*PNP0F03\1_0_21_0_31_0
> >> > 10:20:38 AM - [FBAAddDevInstanceId] ROOT\*PNP0C04\PNPBIOS_6
> >> > 10:20:41 AM - [FBAAddDevInstanceId] ROOT\*PNP0C02\PNPBIOS_8
> >> > 10:20:44 AM - [FBAAddDevInstanceId] ROOT\*PNP0C01\PNPBIOS_7
> >> > 10:20:47 AM - [FBAAddDevInstanceId] ROOT\*PNP0B00\PNPBIOS_3
> >> > 10:20:50 AM - [FBAAddDevInstanceId] ROOT\*PNP0800\PNPBIOS_5
> >> > 10:20:52 AM - [FBAAddDevInstanceId] ROOT\*PNP0700\PNPBIOS_14
> >> > 10:20:56 AM - [FBAAddDevInstanceId] ROOT\*PNP0501\PNPBIOS_17
> >> > 10:21:00 AM - [FBAAddDevInstanceId] ROOT\*PNP0501\PNPBIOS_13
> >> > 10:21:04 AM - [FBAAddDevInstanceId] ROOT\RDP_MOU\0000
> >> > 10:21:08 AM - [FBASkipDevice] ROOT\SYSTEM\0000
> >> > 10:21:08 AM - [FBAAddDevInstanceId] ROOT\*PNP0401\PNPBIOS_16
> >> > 10:21:11 AM - [FBAAddDevInstanceId] ROOT\*PNP030B\1_0_22_0_32_0
> >> > 10:21:16 AM - [FBAAddDevInstanceId] ROOT\*PNP0200\PNPBIOS_1
> >> > 10:21:19 AM - [FBAAddDevInstanceId] ROOT\*PNP0100\PNPBIOS_2
> >> > 10:21:21 AM - [FBAAddDevInstanceId] ROOT\*PNP0000\PNPBIOS_0
> >> > 10:21:24 AM - [FBAAddDevInstanceId] PCI_HAL\PNP0A03\0
> >> > 10:21:28 AM - [FBAAddDevInstanceId]
> >> > PCI\VEN_125D&DEV_1969&SUBSYS_8898125D&REV_02\2&EBB567F&0&58
> >> > 10:21:33 AM - [FBAAddDevInstanceId]
> >> > PCI\VEN_8086&DEV_7110&SUBSYS_00000000&REV_02\2&EBB567F&0&38
> >> > 10:21:37 AM - [FBAAddDevInstanceId]
> >> > PCI\VEN_10EC&DEV_8139&SUBSYS_813910EC&REV_10\2&EBB567F&0&50
> >> > 10:21:43 AM - [FBAAddDevInstanceId]
> >> > PCI\VEN_8086&DEV_7191&SUBSYS_00000000&REV_03\2&EBB567F&0&08
> >> > 10:21:48 AM - [FBAAddDevInstanceId]
> >> > PCI\VEN_8086&DEV_7190&SUBSYS_00000000&REV_03\2&EBB567F&0&00
> >> > 10:21:51 AM - [FBAAddDevInstanceId]
> >> > PCI\VEN_8086&DEV_7112&SUBSYS_00000000&REV_01\2&EBB567F&0&3A
> >> > 10:21:55 AM - [FBAAddDevInstanceId]
> >> > PCI\VEN_8086&DEV_7111&SUBSYS_00000000&REV_01\2&EBB567F&0&39
> >> > 10:21:58 AM - [FBAAddDevInstanceId]
> >> > PCI\VEN_126F&DEV_0720&SUBSYS_0720126F&REV_B1\3&225B1D41&0&0008
> >> > 10:22:09 AM - [FBAAddDevInstanceId]
PCIIDE\IDECHANNEL\3&2A0E595E&0&1
> >> > 10:22:12 AM - [FBAAddDevInstanceId]
PCIIDE\IDECHANNEL\3&2A0E595E&0&0
> >> > 10:22:16 AM - [FBAAddDevInstanceId] ISAPNP\READDATAPORT\0
> >> > 10:22:19 AM - [FBAAddDevInstanceId]
> >> >
> >
IDE\DISKSANDISK_SDCFH-512_______________________HDX_2.27\4&13F4FBA2&0&0.1.0
> >> > 10:22:23 AM - [FBAAddDevInstanceId]
> > STORAGE\REMOVABLEMEDIA\5&18CD7740&0&RM
> >> > 10:22:40 AM - [FBAAddDevInstanceId]
> >> > LPTENUM\MICROSOFTRAWPORT\1&423D6E7&0&LPT1
> >> > 10:22:43 AM - [FBAAddDevInstanceId]
> >> > ESS_ES1969\CHILD0000\3&C1F3C2E&0&00000000
> >> > 10:22:47 AM - [FBAAddDevInstanceId] USB\ROOT_HUB\3&32C8BD93&0
> >> > 10:22:51 AM - [FBAAddDevInstanceId]
> >> > DISPLAY\PHL104B\4&25F8BC9&0&22334455&01&00
> >> > 10:22:52 AM - [FBAAddDevInstanceId]
> >> > DISPLAY\MS_0002\4&25F8BC9&0&11223344&01&00
> >> >
> >> > That's the end of log. FBALaunch is not executed at all! I've been
> > tortured
> >> > by this damned FBA for a week, and I am gonna crazy!
> >>
> >>
> >
> >
>
>


.

Relevant Pages

  • Re: Trouble booting and hibernating
    ... Any hang during the POST (Power On Self Test, where you see the BIOS info ... and drive detection) will most likely be hardware related, ... I hadn't considered a hardware fault. ... the page it hangs on is the American Megatrends page. ...
    (microsoft.public.windows.mediacenter)
  • Re: lockups with 2.4.2x
    ... there is a lot of hardware in this box. ... Your hangs may be related to an updatedb or slocate ... You may also have a defect in your RAM. ... send the line "unsubscribe linux-kernel" in ...
    (Linux-Kernel)
  • RE: btkrnl.sys and a stalled XP load
    ... i am currently experiencing this same problem on my desk top and have found ... subsequent boot normal hangs at windows logo and safemode hangs on ... > upon scanning the hardware configuration. ...
    (microsoft.public.windowsxp.help_and_support)
  • RE: btkrnl.sys and a stalled XP load
    ... i am currently experiencing this same problem on my desk top and have found ... subsequent boot normal hangs at windows logo and safemode hangs on ... > upon scanning the hardware configuration. ...
    (microsoft.public.windowsxp.general)
  • em network issues
    ... I think there may be a few different problems going on with the em driver ... on 6.2 that are being lumped under the general description of network ... hardware that can interfere on the network, ... change and see if it fixes hangs. ...
    (freebsd-net)