1. Welcome Guest! In order to create a new topic or reply to an existing one, you must register first. It is easy and free. Click here to sign up now!.
    Dismiss Notice

kd1394.dll instead of kdcom.dll

Discussion in 'Windows Vista' started by lettucewacker, Jun 17, 2009.

  1. I made this post a month ago in the windbg forum and didn't get any help.
    Does anyone here how about who to change the kernel debugging module that
    gets loaded by the HAL?

    I'm running Vista 32-bit SP1. I want to connect a windbg session using
    1394. I have correctly configured the boot to enable debugging using bcdedit
    and even verified it using the command "bcdedit.exe /dbgsettings" to read
    back my settings. I have even run msconfig to also verify that debugging is
    enabled for the 1394 port and the channel is set correctly.

    When I boot to safe mode with the debugging enabled, I see these modules
    loaded first:
    system32\config\system
    system32\config\ntkrnlpa.exe
    system32\config\hal.dll
    system32\config\kdcom.dll

    kdcom.dll is not supposed to load. I want to use kd1394.dll. I have also
    checked the registry HKLM\System\CurrentControlSet\Services\PCI\Debug and the
    key does not exist, which I understand is supposed to indicate the HAL has
    not correctly initialized the 1394 host controller. Does anyone know how to
    force the HAL to initialize the 1394 correctly?

    I have already tried 2 different 1394 PCIe cards, both of which I've
    verified on other OS installs. I've repeatedly scanned for hardware changes
    and the card seems to be detected just fine and the drivers are installed.
    It seems the HAL is just loading the wrong debugging DLL.
     
  2. JEWboy

    JEWboy Guest

    hard question.
    You may want to keep Googling for it, you may also submit an official
    request to Microsoft but they may charge $40.
     
  3. Peter Foldes

    Peter Foldes Guest

    Vista Home? Does not work with the Home version

    --
    Peter

    Please Reply to Newsgroup for the benefit of others
    Requests for assistance by email can not and will not be acknowledged.

    "lettucewacker" <lettucewacker@community.nospam> wrote in message
    news:AE6BD089-7BE7-47FC-AEA5-5955171D162C@microsoft.com...<!--coloro:blue--><span style="color:blue <!--/coloro-->
    >I made this post a month ago in the windbg forum and didn't get any help.
    > Does anyone here how about who to change the kernel debugging module that
    > gets loaded by the HAL?
    >
    > I'm running Vista 32-bit SP1. I want to connect a windbg session using
    > 1394. I have correctly configured the boot to enable debugging using bcdedit
    > and even verified it using the command "bcdedit.exe /dbgsettings" to read
    > back my settings. I have even run msconfig to also verify that debugging is
    > enabled for the 1394 port and the channel is set correctly.
    >
    > When I boot to safe mode with the debugging enabled, I see these modules
    > loaded first:
    > system32configsystem
    > system32configntkrnlpa.exe
    > system32confighal.dll
    > system32configkdcom.dll
    >
    > kdcom.dll is not supposed to load. I want to use kd1394.dll. I have also
    > checked the registry HKLMSystemCurrentControlSetServicesPCIDebug and the
    > key does not exist, which I understand is supposed to indicate the HAL has
    > not correctly initialized the 1394 host controller. Does anyone know how to
    > force the HAL to initialize the 1394 correctly?
    >
    > I have already tried 2 different 1394 PCIe cards, both of which I've
    > verified on other OS installs. I've repeatedly scanned for hardware changes
    > and the card seems to be detected just fine and the drivers are installed.
    > It seems the HAL is just loading the wrong debugging DLL. <!--colorc--><!--/colorc-->
     

Share This Page