Windows System Software -- Consulting, Training, Development -- Unique Expertise, Guaranteed Results

Before Posting...
Please check out the Community Guidelines in the Announcements and Administration Category.

New laptop and trouble attaching to a 1394 target

Gary_Little-3Gary_Little-3 Member Posts: 1,208
On this one I am holding my breath. I recently received a new Dell Precision
M4500 laptop, loaded, and attempted to run WinDbg for the first time. An
attempt was made to install the driver but that attempt failed, and after a
reboot I cannot attach to the target. Device manager says the laptop is
using a RICOH 1394 OHCI compliant host controller. Foolishly I ran WinDbg
un-elevated the first time, which probably why the install of the driver
failed. I then updated the 1394 driver to the drivers in the WinDbg
directory, but that still did not connect. Finally, I did system restore to
a time before the first aborted run of WinDbg, then a system update followed
by removing and installing WinDbg. All of that done I elevated WinDbg and
let'r rip. Samething.



"Wrote 0 of 1 bytes of the breakin packet.

Failed to write breakin packet to target. Win32 error 0n2

WARNING: The HOST cannot communicate with the TARGET!"



It is well known that 1394 and WinDbg are very sensitive to each other and
I've got a sick feeling this may be the case. Has anyone else run across
this?



Gary G. Little

H (952) 223-1349

C (952) 454-4629

xxxxx@comcast.net

Comments

  • mmmm Member - All Emails Posts: 1,409
    Have you tried enabling protocol debugging (CTRL+ALT+D) to see what's going
    on?


    Good afternoon,

    mm



    On Jun 8, 2010 3:15 PM, "Gary G. Little" wrote:

    On this one I am holding my breath. I recently received a new Dell
    Precision M4500 laptop, loaded, and attempted to run WinDbg for the first
    time. An attempt was made to install the driver but that attempt failed, and
    after a reboot I cannot attach to the target. Device manager says the laptop
    is using a RICOH 1394 OHCI compliant host controller. Foolishly I ran WinDbg
    un-elevated the first time, which probably why the install of the driver
    failed. I then updated the 1394 driver to the drivers in the WinDbg
    directory, but that still did not connect. Finally, I did system restore to
    a time before the first aborted run of WinDbg, then a system update followed
    by removing and installing WinDbg. All of that done I elevated WinDbg and
    let?r rip. Samething.



    ?Wrote 0 of 1 bytes of the breakin packet.

    Failed to write breakin packet to target. Win32 error 0n2

    WARNING: The HOST cannot communicate with the TARGET!?



    It is well known that 1394 and WinDbg are very sensitive to each other and
    I've got a sick feeling this may be the case. Has anyone else run across
    this?



    Gary G. Little

    H (952) 223-1349

    C (952) 454-4629

    xxxxx@comcast.net



    ---
    WINDBG is sponsored by OSR

    For our schedule of WDF, WDM, debugging and other seminars visit:
    http://www.osr.com/seminars

    To unsubscribe, visit the List Server section of OSR Online at
    http://www.osronline.com/page.cfm?name=ListServer
  • Gary_Little-3Gary_Little-3 Member Posts: 1,208
    Good point and I just did. It just keeps repeating the Synchronize:80070002
    . SYNCTARGET:Timeout. Both target and host are set to channel 10.



    Here is what I get:



    Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64

    Copyright (c) Microsoft Corporation. All rights reserved.



    Using 1394 for debugging

    Checking 1394 debug driver version.

    Opened \\.\DBG1394_INSTANCE10

    Timer Resolution set to 1000 usec.

    Waiting to reconnect...

    ...Synchronize: 80070002

    Synchronize:

    ...Synchronize: 80070002

    Synchronize:

    ...Synchronize: 80070002

    Synchronize:

    ...Synchronize: 80070002

    SYNCTARGET: Timeout.



    Gary G. Little

    H (952) 223-1349

    C (952) 454-4629

    xxxxx@comcast.net







    From: xxxxx@lists.osr.com
    [mailto:xxxxx@lists.osr.com] On Behalf Of MARTIN OBRIEN
    Sent: Tuesday, June 08, 2010 2:23 PM
    To: Kernel Debugging Interest List
    Subject: Re: [windbg] New laptop and trouble attaching to a 1394 target



    Have you tried enabling protocol debugging (CTRL+ALT+D) to see what's going
    on?





    Good afternoon,



    mm







    On Jun 8, 2010 3:15 PM, "Gary G. Little" wrote:

    On this one I am holding my breath. I recently received a new Dell Precision
    M4500 laptop, loaded, and attempted to run WinDbg for the first time. An
    attempt was made to install the driver but that attempt failed, and after a
    reboot I cannot attach to the target. Device manager says the laptop is
    using a RICOH 1394 OHCI compliant host controller. Foolishly I ran WinDbg
    un-elevated the first time, which probably why the install of the driver
    failed. I then updated the 1394 driver to the drivers in the WinDbg
    directory, but that still did not connect. Finally, I did system restore to
    a time before the first aborted run of WinDbg, then a system update followed
    by removing and installing WinDbg. All of that done I elevated WinDbg and
    let'r rip. Samething.



    "Wrote 0 of 1 bytes of the breakin packet.

    Failed to write breakin packet to target. Win32 error 0n2

    WARNING: The HOST cannot communicate with the TARGET!"



    It is well known that 1394 and WinDbg are very sensitive to each other and
    I've got a sick feeling this may be the case. Has anyone else run across
    this?



    Gary G. Little

    H (952) 223-1349

    C (952) 454-4629

    xxxxx@comcast.net




    ---
    WINDBG is sponsored by OSR

    For our schedule of WDF, WDM, debugging and other seminars visit:
    http://www.osr.com/seminars

    To unsubscribe, visit the List Server section of OSR Online at
    http://www.osronline.com/page.cfm?name=ListServer

    --- WINDBG is sponsored by OSR For our schedule of WDF, WDM, debugging and
    other seminars visit: http://www.osr.com/seminars To unsubscribe, visit the
    List Server section of OSR Online at
    http://www.osronline.com/page.cfm?name=ListServer
  • jimdjimd Member Posts: 248
    FWIW - My laptop has the same chip and it worked great, providing the target
    has the right chip.


    On Tue, Jun 8, 2010 at 3:13 PM, Gary G. Little wrote:

    > On this one I am holding my breath. I recently received a new Dell
    > Precision M4500 laptop, loaded, and attempted to run WinDbg for the first
    > time. An attempt was made to install the driver but that attempt failed, and
    > after a reboot I cannot attach to the target. Device manager says the laptop
    > is using a RICOH 1394 OHCI compliant host controller. Foolishly I ran WinDbg
    > un-elevated the first time, which probably why the install of the driver
    > failed. I then updated the 1394 driver to the drivers in the WinDbg
    > directory, but that still did not connect. Finally, I did system restore to
    > a time before the first aborted run of WinDbg, then a system update followed
    > by removing and installing WinDbg. All of that done I elevated WinDbg and
    > let?r rip. Samething.
    >
    >
    >
    > ?Wrote 0 of 1 bytes of the breakin packet.
    >
    > Failed to write breakin packet to target. Win32 error 0n2
    >
    > WARNING: The HOST cannot communicate with the TARGET!?
    >
    >
    >
    > It is well known that 1394 and WinDbg are very sensitive to each other and
    > I've got a sick feeling this may be the case. Has anyone else run across
    > this?
    >
    >
    >
    > Gary G. Little
    >
    > H (952) 223-1349
    >
    > C (952) 454-4629
    >
    > xxxxx@comcast.net
    >
    >
    >
    > ---
    > WINDBG is sponsored by OSR
    >
    > For our schedule of WDF, WDM, debugging and other seminars visit:
    > http://www.osr.com/seminars
    >
    > To unsubscribe, visit the List Server section of OSR Online at
    > http://www.osronline.com/page.cfm?name=ListServer
    >
  • Gary_Little-3Gary_Little-3 Member Posts: 1,208
    I've been using the same target for several months with a 2 year old Dell
    Latitude D530. The lease is up on the Dell in August so I decided to step up
    to newer technology for the development machine. I did make sure it had
    1394, but not the chipset used. Oh well, looks like OSR may get some shekels
    for one of their cards.



    One thing . AV or the firewall has no affect on this connection does it,
    requiring special permission? I just plugged the target back into the
    Latitude and had ESET pop up a window asking for permission.



    Gary G. Little

    H (952) 223-1349

    C (952) 454-4629

    xxxxx@comcast.net







    From: xxxxx@lists.osr.com
    [mailto:xxxxx@lists.osr.com] On Behalf Of Jim Donelson
    Sent: Tuesday, June 08, 2010 2:32 PM
    To: Kernel Debugging Interest List
    Subject: Re: [windbg] New laptop and trouble attaching to a 1394 target



    FWIW - My laptop has the same chip and it worked great, providing the target
    has the right chip.



    On Tue, Jun 8, 2010 at 3:13 PM, Gary G. Little wrote:

    On this one I am holding my breath. I recently received a new Dell Precision
    M4500 laptop, loaded, and attempted to run WinDbg for the first time. An
    attempt was made to install the driver but that attempt failed, and after a
    reboot I cannot attach to the target. Device manager says the laptop is
    using a RICOH 1394 OHCI compliant host controller. Foolishly I ran WinDbg
    un-elevated the first time, which probably why the install of the driver
    failed. I then updated the 1394 driver to the drivers in the WinDbg
    directory, but that still did not connect. Finally, I did system restore to
    a time before the first aborted run of WinDbg, then a system update followed
    by removing and installing WinDbg. All of that done I elevated WinDbg and
    let'r rip. Samething.



    "Wrote 0 of 1 bytes of the breakin packet.

    Failed to write breakin packet to target. Win32 error 0n2

    WARNING: The HOST cannot communicate with the TARGET!"



    It is well known that 1394 and WinDbg are very sensitive to each other and
    I've got a sick feeling this may be the case. Has anyone else run across
    this?



    Gary G. Little

    H (952) 223-1349

    C (952) 454-4629

    xxxxx@comcast.net




    ---
    WINDBG is sponsored by OSR

    For our schedule of WDF, WDM, debugging and other seminars visit:
    http://www.osr.com/seminars

    To unsubscribe, visit the List Server section of OSR Online at
    http://www.osronline.com/page.cfm?name=ListServer


    --- WINDBG is sponsored by OSR For our schedule of WDF, WDM, debugging and
    other seminars visit: http://www.osr.com/seminars To unsubscribe, visit the
    List Server section of OSR Online at
    http://www.osronline.com/page.cfm?name=ListServer
  • Gary_Little-3Gary_Little-3 Member Posts: 1,208
    Thanks Jim. That's indicative of operator headspace problems, J.



    Gary G. Little

    H (952) 223-1349

    C (952) 454-4629

    xxxxx@comcast.net







    From: xxxxx@lists.osr.com
    [mailto:xxxxx@lists.osr.com] On Behalf Of Jim Donelson
    Sent: Tuesday, June 08, 2010 2:32 PM
    To: Kernel Debugging Interest List
    Subject: Re: [windbg] New laptop and trouble attaching to a 1394 target



    FWIW - My laptop has the same chip and it worked great, providing the target
    has the right chip.



    On Tue, Jun 8, 2010 at 3:13 PM, Gary G. Little wrote:

    On this one I am holding my breath. I recently received a new Dell Precision
    M4500 laptop, loaded, and attempted to run WinDbg for the first time. An
    attempt was made to install the driver but that attempt failed, and after a
    reboot I cannot attach to the target. Device manager says the laptop is
    using a RICOH 1394 OHCI compliant host controller. Foolishly I ran WinDbg
    un-elevated the first time, which probably why the install of the driver
    failed. I then updated the 1394 driver to the drivers in the WinDbg
    directory, but that still did not connect. Finally, I did system restore to
    a time before the first aborted run of WinDbg, then a system update followed
    by removing and installing WinDbg. All of that done I elevated WinDbg and
    let'r rip. Samething.



    "Wrote 0 of 1 bytes of the breakin packet.

    Failed to write breakin packet to target. Win32 error 0n2

    WARNING: The HOST cannot communicate with the TARGET!"



    It is well known that 1394 and WinDbg are very sensitive to each other and
    I've got a sick feeling this may be the case. Has anyone else run across
    this?



    Gary G. Little

    H (952) 223-1349

    C (952) 454-4629

    xxxxx@comcast.net




    ---
    WINDBG is sponsored by OSR

    For our schedule of WDF, WDM, debugging and other seminars visit:
    http://www.osr.com/seminars

    To unsubscribe, visit the List Server section of OSR Online at
    http://www.osronline.com/page.cfm?name=ListServer


    --- WINDBG is sponsored by OSR For our schedule of WDF, WDM, debugging and
    other seminars visit: http://www.osr.com/seminars To unsubscribe, visit the
    List Server section of OSR Online at
    http://www.osronline.com/page.cfm?name=ListServer
  • OSR_Community_UserOSR_Community_User Member Posts: 110,217
    The host doesn't see the target machine on the 1394 bus.

    This is either because kd1394.dll does not support the 1394 controller in the target machine, or because either the target machine or the host machine have more than 1 1394 controller in them.

    Are you using this laptop as a target or as a host?

    Joe.

    From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of Gary G. Little
    Sent: Tuesday, June 08, 2010 12:31 PM
    To: Kernel Debugging Interest List
    Subject: RE: [windbg] New laptop and trouble attaching to a 1394 target

    Good point and I just did. It just keeps repeating the Synchronize:80070002 ... SYNCTARGET:Timeout. Both target and host are set to channel 10.

    Here is what I get:

    Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.

    Using 1394 for debugging
    Checking 1394 debug driver version.
    Opened \\.\DBG1394_INSTANCE10
    Timer Resolution set to 1000 usec.
    Waiting to reconnect...
    ...Synchronize: 80070002
    Synchronize:
    ...Synchronize: 80070002
    Synchronize:
    ...Synchronize: 80070002
    Synchronize:
    ...Synchronize: 80070002
    SYNCTARGET: Timeout.

    Gary G. Little
    H (952) 223-1349
    C (952) 454-4629
    xxxxx@comcast.net



    From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of MARTIN OBRIEN
    Sent: Tuesday, June 08, 2010 2:23 PM
    To: Kernel Debugging Interest List
    Subject: Re: [windbg] New laptop and trouble attaching to a 1394 target

    Have you tried enabling protocol debugging (CTRL+ALT+D) to see what's going on?


    Good afternoon,

    mm



    On Jun 8, 2010 3:15 PM, "Gary G. Little" > wrote:

    On this one I am holding my breath. I recently received a new Dell Precision M4500 laptop, loaded, and attempted to run WinDbg for the first time. An attempt was made to install the driver but that attempt failed, and after a reboot I cannot attach to the target. Device manager says the laptop is using a RICOH 1394 OHCI compliant host controller. Foolishly I ran WinDbg un-elevated the first time, which probably why the install of the driver failed. I then updated the 1394 driver to the drivers in the WinDbg directory, but that still did not connect. Finally, I did system restore to a time before the first aborted run of WinDbg, then a system update followed by removing and installing WinDbg. All of that done I elevated WinDbg and let'r rip. Samething.



    "Wrote 0 of 1 bytes of the breakin packet.

    Failed to write breakin packet to target. Win32 error 0n2

    WARNING: The HOST cannot communicate with the TARGET!"



    It is well known that 1394 and WinDbg are very sensitive to each other and I've got a sick feeling this may be the case. Has anyone else run across this?

    Gary G. Little
    H (952) 223-1349
    C (952) 454-4629
    xxxxx@comcast.net


    ---
    WINDBG is sponsored by OSR

    For our schedule of WDF, WDM, debugging and other seminars visit:
    http://www.osr.com/seminars

    To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer
    --- WINDBG is sponsored by OSR For our schedule of WDF, WDM, debugging and other seminars visit: http://www.osr.com/seminars To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer

    ---
    WINDBG is sponsored by OSR

    For our schedule of WDF, WDM, debugging and other seminars visit:
    http://www.osr.com/seminars

    To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer
  • Gary_Little-3Gary_Little-3 Member Posts: 1,208
    Joe,



    The laptop is a host. I went to device manager and updated the Dell
    installed device driver to the kd driver(s) after the last install of
    WinDbg, but no joy in Mudville. The target is currently working fine
    connected to another system.



    Gary G. Little

    H (952) 223-1349

    C (952) 454-4629

    xxxxx@comcast.net



    From: xxxxx@lists.osr.com
    [mailto:xxxxx@lists.osr.com] On Behalf Of Joe Ballantyne
    Sent: Tuesday, June 08, 2010 3:48 PM
    To: Kernel Debugging Interest List
    Subject: RE: [windbg] New laptop and trouble attaching to a 1394 target



    The host doesn't see the target machine on the 1394 bus.



    This is either because kd1394.dll does not support the 1394 controller in
    the target machine, or because either the target machine or the host machine
    have more than 1 1394 controller in them.



    Are you using this laptop as a target or as a host?



    Joe.



    From: xxxxx@lists.osr.com
    [mailto:xxxxx@lists.osr.com] On Behalf Of Gary G. Little
    Sent: Tuesday, June 08, 2010 12:31 PM
    To: Kernel Debugging Interest List
    Subject: RE: [windbg] New laptop and trouble attaching to a 1394 target



    Good point and I just did. It just keeps repeating the Synchronize:80070002
    . SYNCTARGET:Timeout. Both target and host are set to channel 10.



    Here is what I get:



    Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64

    Copyright (c) Microsoft Corporation. All rights reserved.



    Using 1394 for debugging

    Checking 1394 debug driver version.

    Opened \\.\DBG1394_INSTANCE10

    Timer Resolution set to 1000 usec.

    Waiting to reconnect...

    ...Synchronize: 80070002

    Synchronize:

    ...Synchronize: 80070002

    Synchronize:

    ...Synchronize: 80070002

    Synchronize:

    ...Synchronize: 80070002

    SYNCTARGET: Timeout.



    Gary G. Little

    H (952) 223-1349

    C (952) 454-4629

    xxxxx@comcast.net







    From: xxxxx@lists.osr.com
    [mailto:xxxxx@lists.osr.com] On Behalf Of MARTIN OBRIEN
    Sent: Tuesday, June 08, 2010 2:23 PM
    To: Kernel Debugging Interest List
    Subject: Re: [windbg] New laptop and trouble attaching to a 1394 target



    Have you tried enabling protocol debugging (CTRL+ALT+D) to see what's going
    on?





    Good afternoon,



    mm







    On Jun 8, 2010 3:15 PM, "Gary G. Little" wrote:

    On this one I am holding my breath. I recently received a new Dell Precision
    M4500 laptop, loaded, and attempted to run WinDbg for the first time. An
    attempt was made to install the driver but that attempt failed, and after a
    reboot I cannot attach to the target. Device manager says the laptop is
    using a RICOH 1394 OHCI compliant host controller. Foolishly I ran WinDbg
    un-elevated the first time, which probably why the install of the driver
    failed. I then updated the 1394 driver to the drivers in the WinDbg
    directory, but that still did not connect. Finally, I did system restore to
    a time before the first aborted run of WinDbg, then a system update followed
    by removing and installing WinDbg. All of that done I elevated WinDbg and
    let'r rip. Samething.



    "Wrote 0 of 1 bytes of the breakin packet.

    Failed to write breakin packet to target. Win32 error 0n2

    WARNING: The HOST cannot communicate with the TARGET!"



    It is well known that 1394 and WinDbg are very sensitive to each other and
    I've got a sick feeling this may be the case. Has anyone else run across
    this?



    Gary G. Little

    H (952) 223-1349

    C (952) 454-4629

    xxxxx@comcast.net




    ---
    WINDBG is sponsored by OSR

    For our schedule of WDF, WDM, debugging and other seminars visit:
    http://www.osr.com/seminars

    To unsubscribe, visit the List Server section of OSR Online at
    http://www.osronline.com/page.cfm?name=ListServer

    --- WINDBG is sponsored by OSR For our schedule of WDF, WDM, debugging and
    other seminars visit: http://www.osr.com/seminars To unsubscribe, visit the
    List Server section of OSR Online at
    http://www.osronline.com/page.cfm?name=ListServer


    ---
    WINDBG is sponsored by OSR

    For our schedule of WDF, WDM, debugging and other seminars visit:
    http://www.osr.com/seminars

    To unsubscribe, visit the List Server section of OSR Online at
    http://www.osronline.com/page.cfm?name=ListServer


    ---
    WINDBG is sponsored by OSR

    For our schedule of WDF, WDM, debugging and other seminars visit:
    http://www.osr.com/seminars

    To unsubscribe, visit the List Server section of OSR Online at
    http://www.osronline.com/page.cfm?name=ListServer
  • Gary_Little-3Gary_Little-3 Member Posts: 1,208
    Joe,



    I tried 1394 device, a Seagate external driver, and that connected on the
    1394 bus, installed the driver and provided access. Thanks for the help.



    Gary G. Little

    H (952) 223-1349

    C (952) 454-4629

    xxxxx@comcast.net



    From: xxxxx@lists.osr.com
    [mailto:xxxxx@lists.osr.com] On Behalf Of Joe Ballantyne
    Sent: Tuesday, June 08, 2010 3:48 PM
    To: Kernel Debugging Interest List
    Subject: RE: [windbg] New laptop and trouble attaching to a 1394 target



    The host doesn't see the target machine on the 1394 bus.



    This is either because kd1394.dll does not support the 1394 controller in
    the target machine, or because either the target machine or the host machine
    have more than 1 1394 controller in them.



    Are you using this laptop as a target or as a host?



    Joe.



    From: xxxxx@lists.osr.com
    [mailto:xxxxx@lists.osr.com] On Behalf Of Gary G. Little
    Sent: Tuesday, June 08, 2010 12:31 PM
    To: Kernel Debugging Interest List
    Subject: RE: [windbg] New laptop and trouble attaching to a 1394 target



    Good point and I just did. It just keeps repeating the Synchronize:80070002
    . SYNCTARGET:Timeout. Both target and host are set to channel 10.



    Here is what I get:



    Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64

    Copyright (c) Microsoft Corporation. All rights reserved.



    Using 1394 for debugging

    Checking 1394 debug driver version.

    Opened \\.\DBG1394_INSTANCE10

    Timer Resolution set to 1000 usec.

    Waiting to reconnect...

    ...Synchronize: 80070002

    Synchronize:

    ...Synchronize: 80070002

    Synchronize:

    ...Synchronize: 80070002

    Synchronize:

    ...Synchronize: 80070002

    SYNCTARGET: Timeout.



    Gary G. Little

    H (952) 223-1349

    C (952) 454-4629

    xxxxx@comcast.net







    From: xxxxx@lists.osr.com
    [mailto:xxxxx@lists.osr.com] On Behalf Of MARTIN OBRIEN
    Sent: Tuesday, June 08, 2010 2:23 PM
    To: Kernel Debugging Interest List
    Subject: Re: [windbg] New laptop and trouble attaching to a 1394 target



    Have you tried enabling protocol debugging (CTRL+ALT+D) to see what's going
    on?





    Good afternoon,



    mm







    On Jun 8, 2010 3:15 PM, "Gary G. Little" wrote:

    On this one I am holding my breath. I recently received a new Dell Precision
    M4500 laptop, loaded, and attempted to run WinDbg for the first time. An
    attempt was made to install the driver but that attempt failed, and after a
    reboot I cannot attach to the target. Device manager says the laptop is
    using a RICOH 1394 OHCI compliant host controller. Foolishly I ran WinDbg
    un-elevated the first time, which probably why the install of the driver
    failed. I then updated the 1394 driver to the drivers in the WinDbg
    directory, but that still did not connect. Finally, I did system restore to
    a time before the first aborted run of WinDbg, then a system update followed
    by removing and installing WinDbg. All of that done I elevated WinDbg and
    let'r rip. Samething.



    "Wrote 0 of 1 bytes of the breakin packet.

    Failed to write breakin packet to target. Win32 error 0n2

    WARNING: The HOST cannot communicate with the TARGET!"



    It is well known that 1394 and WinDbg are very sensitive to each other and
    I've got a sick feeling this may be the case. Has anyone else run across
    this?



    Gary G. Little

    H (952) 223-1349

    C (952) 454-4629

    xxxxx@comcast.net




    ---
    WINDBG is sponsored by OSR

    For our schedule of WDF, WDM, debugging and other seminars visit:
    http://www.osr.com/seminars

    To unsubscribe, visit the List Server section of OSR Online at
    http://www.osronline.com/page.cfm?name=ListServer

    --- WINDBG is sponsored by OSR For our schedule of WDF, WDM, debugging and
    other seminars visit: http://www.osr.com/seminars To unsubscribe, visit the
    List Server section of OSR Online at
    http://www.osronline.com/page.cfm?name=ListServer


    ---
    WINDBG is sponsored by OSR

    For our schedule of WDF, WDM, debugging and other seminars visit:
    http://www.osr.com/seminars

    To unsubscribe, visit the List Server section of OSR Online at
    http://www.osronline.com/page.cfm?name=ListServer


    ---
    WINDBG is sponsored by OSR

    For our schedule of WDF, WDM, debugging and other seminars visit:
    http://www.osr.com/seminars

    To unsubscribe, visit the List Server section of OSR Online at
    http://www.osronline.com/page.cfm?name=ListServer
  • Gary_Little-3Gary_Little-3 Member Posts: 1,208
    Joe,



    As a follow up, I tried a few more things. I entered the BIOS and disabled
    as much of the Media/PC card/1394 as possible to leave only the 1394 card,
    but that did not work. I also force installed the Windows debugger drivers
    but that did not work either. So, at this point it's go to Dell tech support
    who will most likely shrug their shoulders and mumble "Wulll it works on the
    external drive." I probably should do that if nothing else to get a history
    started.



    I also ordered the OSR board and was shocked to find they did not offer a
    seniors discount!?!?!? J



    Gary G. Little

    H (952) 223-1349

    C (952) 454-4629

    xxxxx@comcast.net



    From: xxxxx@lists.osr.com
    [mailto:xxxxx@lists.osr.com] On Behalf Of Gary G. Little
    Sent: Tuesday, June 08, 2010 4:54 PM
    To: Kernel Debugging Interest List
    Subject: RE: [windbg] New laptop and trouble attaching to a 1394 target



    Joe,



    I tried 1394 device, a Seagate external driver, and that connected on the
    1394 bus, installed the driver and provided access. Thanks for the help.



    Gary G. Little

    H (952) 223-1349

    C (952) 454-4629

    xxxxx@comcast.net



    From: xxxxx@lists.osr.com
    [mailto:xxxxx@lists.osr.com] On Behalf Of Joe Ballantyne
    Sent: Tuesday, June 08, 2010 3:48 PM
    To: Kernel Debugging Interest List
    Subject: RE: [windbg] New laptop and trouble attaching to a 1394 target



    The host doesn't see the target machine on the 1394 bus.



    This is either because kd1394.dll does not support the 1394 controller in
    the target machine, or because either the target machine or the host machine
    have more than 1 1394 controller in them.



    Are you using this laptop as a target or as a host?



    Joe.



    From: xxxxx@lists.osr.com
    [mailto:xxxxx@lists.osr.com] On Behalf Of Gary G. Little
    Sent: Tuesday, June 08, 2010 12:31 PM
    To: Kernel Debugging Interest List
    Subject: RE: [windbg] New laptop and trouble attaching to a 1394 target



    Good point and I just did. It just keeps repeating the Synchronize:80070002
    . SYNCTARGET:Timeout. Both target and host are set to channel 10.



    Here is what I get:



    Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64

    Copyright (c) Microsoft Corporation. All rights reserved.



    Using 1394 for debugging

    Checking 1394 debug driver version.

    Opened \\.\DBG1394_INSTANCE10

    Timer Resolution set to 1000 usec.

    Waiting to reconnect...

    ...Synchronize: 80070002

    Synchronize:

    ...Synchronize: 80070002

    Synchronize:

    ...Synchronize: 80070002

    Synchronize:

    ...Synchronize: 80070002

    SYNCTARGET: Timeout.



    Gary G. Little

    H (952) 223-1349

    C (952) 454-4629

    xxxxx@comcast.net







    From: xxxxx@lists.osr.com
    [mailto:xxxxx@lists.osr.com] On Behalf Of MARTIN OBRIEN
    Sent: Tuesday, June 08, 2010 2:23 PM
    To: Kernel Debugging Interest List
    Subject: Re: [windbg] New laptop and trouble attaching to a 1394 target



    Have you tried enabling protocol debugging (CTRL+ALT+D) to see what's going
    on?





    Good afternoon,



    mm







    On Jun 8, 2010 3:15 PM, "Gary G. Little" wrote:

    On this one I am holding my breath. I recently received a new Dell Precision
    M4500 laptop, loaded, and attempted to run WinDbg for the first time. An
    attempt was made to install the driver but that attempt failed, and after a
    reboot I cannot attach to the target. Device manager says the laptop is
    using a RICOH 1394 OHCI compliant host controller. Foolishly I ran WinDbg
    un-elevated the first time, which probably why the install of the driver
    failed. I then updated the 1394 driver to the drivers in the WinDbg
    directory, but that still did not connect. Finally, I did system restore to
    a time before the first aborted run of WinDbg, then a system update followed
    by removing and installing WinDbg. All of that done I elevated WinDbg and
    let'r rip. Samething.



    "Wrote 0 of 1 bytes of the breakin packet.

    Failed to write breakin packet to target. Win32 error 0n2

    WARNING: The HOST cannot communicate with the TARGET!"



    It is well known that 1394 and WinDbg are very sensitive to each other and
    I've got a sick feeling this may be the case. Has anyone else run across
    this?



    Gary G. Little

    H (952) 223-1349

    C (952) 454-4629

    xxxxx@comcast.net




    ---
    WINDBG is sponsored by OSR

    For our schedule of WDF, WDM, debugging and other seminars visit:
    http://www.osr.com/seminars

    To unsubscribe, visit the List Server section of OSR Online at
    http://www.osronline.com/page.cfm?name=ListServer

    --- WINDBG is sponsored by OSR For our schedule of WDF, WDM, debugging and
    other seminars visit: http://www.osr.com/seminars To unsubscribe, visit the
    List Server section of OSR Online at
    http://www.osronline.com/page.cfm?name=ListServer


    ---
    WINDBG is sponsored by OSR

    For our schedule of WDF, WDM, debugging and other seminars visit:
    http://www.osr.com/seminars

    To unsubscribe, visit the List Server section of OSR Online at
    http://www.osronline.com/page.cfm?name=ListServer


    ---
    WINDBG is sponsored by OSR

    For our schedule of WDF, WDM, debugging and other seminars visit:
    http://www.osr.com/seminars

    To unsubscribe, visit the List Server section of OSR Online at
    http://www.osronline.com/page.cfm?name=ListServer


    ---
    WINDBG is sponsored by OSR

    For our schedule of WDF, WDM, debugging and other seminars visit:
    http://www.osr.com/seminars

    To unsubscribe, visit the List Server section of OSR Online at
    http://www.osronline.com/page.cfm?name=ListServer
  • mmmm Member - All Emails Posts: 1,409
    One last thing that I can think of - if there's a BIOS setting named
    something like 'PNP OS,' make sure that it is disabled.





    Good luck,



    mm



    From: xxxxx@lists.osr.com
    [mailto:xxxxx@lists.osr.com] On Behalf Of Gary G. Little
    Sent: Thursday, June 10, 2010 10:18 AM
    To: Kernel Debugging Interest List
    Subject: RE: [windbg] New laptop and trouble attaching to a 1394 target



    Joe,



    As a follow up, I tried a few more things. I entered the BIOS and disabled
    as much of the Media/PC card/1394 as possible to leave only the 1394 card,
    but that did not work. I also force installed the Windows debugger drivers
    but that did not work either. So, at this point it's go to Dell tech support
    who will most likely shrug their shoulders and mumble "Wulll it works on the
    external drive." I probably should do that if nothing else to get a history
    started.



    I also ordered the OSR board and was shocked to find they did not offer a
    seniors discount!?!?!? J



    Gary G. Little

    H (952) 223-1349

    C (952) 454-4629

    xxxxx@comcast.net



    From: xxxxx@lists.osr.com
    [mailto:xxxxx@lists.osr.com] On Behalf Of Gary G. Little
    Sent: Tuesday, June 08, 2010 4:54 PM
    To: Kernel Debugging Interest List
    Subject: RE: [windbg] New laptop and trouble attaching to a 1394 target



    Joe,



    I tried 1394 device, a Seagate external driver, and that connected on the
    1394 bus, installed the driver and provided access. Thanks for the help.



    Gary G. Little

    H (952) 223-1349

    C (952) 454-4629

    xxxxx@comcast.net



    From: xxxxx@lists.osr.com
    [mailto:xxxxx@lists.osr.com] On Behalf Of Joe Ballantyne
    Sent: Tuesday, June 08, 2010 3:48 PM
    To: Kernel Debugging Interest List
    Subject: RE: [windbg] New laptop and trouble attaching to a 1394 target



    The host doesn't see the target machine on the 1394 bus.



    This is either because kd1394.dll does not support the 1394 controller in
    the target machine, or because either the target machine or the host machine
    have more than 1 1394 controller in them.



    Are you using this laptop as a target or as a host?



    Joe.



    From: xxxxx@lists.osr.com
    [mailto:xxxxx@lists.osr.com] On Behalf Of Gary G. Little
    Sent: Tuesday, June 08, 2010 12:31 PM
    To: Kernel Debugging Interest List
    Subject: RE: [windbg] New laptop and trouble attaching to a 1394 target



    Good point and I just did. It just keeps repeating the Synchronize:80070002
    . SYNCTARGET:Timeout. Both target and host are set to channel 10.



    Here is what I get:



    Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64

    Copyright (c) Microsoft Corporation. All rights reserved.



    Using 1394 for debugging

    Checking 1394 debug driver version.

    Opened \\.\DBG1394_INSTANCE10

    Timer Resolution set to 1000 usec.

    Waiting to reconnect...

    ...Synchronize: 80070002

    Synchronize:

    ...Synchronize: 80070002

    Synchronize:

    ...Synchronize: 80070002

    Synchronize:

    ...Synchronize: 80070002

    SYNCTARGET: Timeout.



    Gary G. Little

    H (952) 223-1349

    C (952) 454-4629

    xxxxx@comcast.net







    From: xxxxx@lists.osr.com
    [mailto:xxxxx@lists.osr.com] On Behalf Of MARTIN OBRIEN
    Sent: Tuesday, June 08, 2010 2:23 PM
    To: Kernel Debugging Interest List
    Subject: Re: [windbg] New laptop and trouble attaching to a 1394 target



    Have you tried enabling protocol debugging (CTRL+ALT+D) to see what's going
    on?





    Good afternoon,



    mm







    On Jun 8, 2010 3:15 PM, "Gary G. Little" wrote:

    On this one I am holding my breath. I recently received a new Dell Precision
    M4500 laptop, loaded, and attempted to run WinDbg for the first time. An
    attempt was made to install the driver but that attempt failed, and after a
    reboot I cannot attach to the target. Device manager says the laptop is
    using a RICOH 1394 OHCI compliant host controller. Foolishly I ran WinDbg
    un-elevated the first time, which probably why the install of the driver
    failed. I then updated the 1394 driver to the drivers in the WinDbg
    directory, but that still did not connect. Finally, I did system restore to
    a time before the first aborted run of WinDbg, then a system update followed
    by removing and installing WinDbg. All of that done I elevated WinDbg and
    let'r rip. Samething.



    "Wrote 0 of 1 bytes of the breakin packet.

    Failed to write breakin packet to target. Win32 error 0n2

    WARNING: The HOST cannot communicate with the TARGET!"



    It is well known that 1394 and WinDbg are very sensitive to each other and
    I've got a sick feeling this may be the case. Has anyone else run across
    this?



    Gary G. Little

    H (952) 223-1349

    C (952) 454-4629

    xxxxx@comcast.net




    ---
    WINDBG is sponsored by OSR

    For our schedule of WDF, WDM, debugging and other seminars visit:
    http://www.osr.com/seminars

    To unsubscribe, visit the List Server section of OSR Online at
    http://www.osronline.com/page.cfm?name=ListServer

    --- WINDBG is sponsored by OSR For our schedule of WDF, WDM, debugging and
    other seminars visit: http://www.osr.com/seminars To unsubscribe, visit the
    List Server section of OSR Online at
    http://www.osronline.com/page.cfm?name=ListServer


    ---
    WINDBG is sponsored by OSR

    For our schedule of WDF, WDM, debugging and other seminars visit:
    http://www.osr.com/seminars

    To unsubscribe, visit the List Server section of OSR Online at
    http://www.osronline.com/page.cfm?name=ListServer


    ---
    WINDBG is sponsored by OSR

    For our schedule of WDF, WDM, debugging and other seminars visit:
    http://www.osr.com/seminars

    To unsubscribe, visit the List Server section of OSR Online at
    http://www.osronline.com/page.cfm?name=ListServer


    ---
    WINDBG is sponsored by OSR

    For our schedule of WDF, WDM, debugging and other seminars visit:
    http://www.osr.com/seminars

    To unsubscribe, visit the List Server section of OSR Online at
    http://www.osronline.com/page.cfm?name=ListServer


    ---
    WINDBG is sponsored by OSR

    For our schedule of WDF, WDM, debugging and other seminars visit:
    http://www.osr.com/seminars

    To unsubscribe, visit the List Server section of OSR Online at
    http://www.osronline.com/page.cfm?name=ListServer
  • Mark_RodriquezMark_Rodriquez Member Posts: 31
    Gary, sadly we are all getting up there in age.



    --Mark Cariddi

    OSR, "OLD" consulting associate...



    From: xxxxx@lists.osr.com
    [mailto:xxxxx@lists.osr.com] On Behalf Of Gary G. Little
    Sent: Thursday, June 10, 2010 10:18 AM
    To: Kernel Debugging Interest List
    Subject: RE: [windbg] New laptop and trouble attaching to a 1394 target



    Joe,



    As a follow up, I tried a few more things. I entered the BIOS and disabled
    as much of the Media/PC card/1394 as possible to leave only the 1394 card,
    but that did not work. I also force installed the Windows debugger drivers
    but that did not work either. So, at this point it's go to Dell tech support
    who will most likely shrug their shoulders and mumble "Wulll it works on the
    external drive." I probably should do that if nothing else to get a history
    started.



    I also ordered the OSR board and was shocked to find they did not offer a
    seniors discount!?!?!? J



    Gary G. Little

    H (952) 223-1349

    C (952) 454-4629

    xxxxx@comcast.net



    From: xxxxx@lists.osr.com
    [mailto:xxxxx@lists.osr.com] On Behalf Of Gary G. Little
    Sent: Tuesday, June 08, 2010 4:54 PM
    To: Kernel Debugging Interest List
    Subject: RE: [windbg] New laptop and trouble attaching to a 1394 target



    Joe,



    I tried 1394 device, a Seagate external driver, and that connected on the
    1394 bus, installed the driver and provided access. Thanks for the help.



    Gary G. Little

    H (952) 223-1349

    C (952) 454-4629

    xxxxx@comcast.net



    From: xxxxx@lists.osr.com
    [mailto:xxxxx@lists.osr.com] On Behalf Of Joe Ballantyne
    Sent: Tuesday, June 08, 2010 3:48 PM
    To: Kernel Debugging Interest List
    Subject: RE: [windbg] New laptop and trouble attaching to a 1394 target



    The host doesn't see the target machine on the 1394 bus.



    This is either because kd1394.dll does not support the 1394 controller in
    the target machine, or because either the target machine or the host machine
    have more than 1 1394 controller in them.



    Are you using this laptop as a target or as a host?



    Joe.



    From: xxxxx@lists.osr.com
    [mailto:xxxxx@lists.osr.com] On Behalf Of Gary G. Little
    Sent: Tuesday, June 08, 2010 12:31 PM
    To: Kernel Debugging Interest List
    Subject: RE: [windbg] New laptop and trouble attaching to a 1394 target



    Good point and I just did. It just keeps repeating the Synchronize:80070002
    . SYNCTARGET:Timeout. Both target and host are set to channel 10.



    Here is what I get:



    Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64

    Copyright (c) Microsoft Corporation. All rights reserved.



    Using 1394 for debugging

    Checking 1394 debug driver version.

    Opened \\.\DBG1394_INSTANCE10

    Timer Resolution set to 1000 usec.

    Waiting to reconnect...

    ...Synchronize: 80070002

    Synchronize:

    ...Synchronize: 80070002

    Synchronize:

    ...Synchronize: 80070002

    Synchronize:

    ...Synchronize: 80070002

    SYNCTARGET: Timeout.



    Gary G. Little

    H (952) 223-1349

    C (952) 454-4629

    xxxxx@comcast.net







    From: xxxxx@lists.osr.com
    [mailto:xxxxx@lists.osr.com] On Behalf Of MARTIN OBRIEN
    Sent: Tuesday, June 08, 2010 2:23 PM
    To: Kernel Debugging Interest List
    Subject: Re: [windbg] New laptop and trouble attaching to a 1394 target



    Have you tried enabling protocol debugging (CTRL+ALT+D) to see what's going
    on?





    Good afternoon,



    mm







    On Jun 8, 2010 3:15 PM, "Gary G. Little" wrote:

    On this one I am holding my breath. I recently received a new Dell Precision
    M4500 laptop, loaded, and attempted to run WinDbg for the first time. An
    attempt was made to install the driver but that attempt failed, and after a
    reboot I cannot attach to the target. Device manager says the laptop is
    using a RICOH 1394 OHCI compliant host controller. Foolishly I ran WinDbg
    un-elevated the first time, which probably why the install of the driver
    failed. I then updated the 1394 driver to the drivers in the WinDbg
    directory, but that still did not connect. Finally, I did system restore to
    a time before the first aborted run of WinDbg, then a system update followed
    by removing and installing WinDbg. All of that done I elevated WinDbg and
    let'r rip. Samething.



    "Wrote 0 of 1 bytes of the breakin packet.

    Failed to write breakin packet to target. Win32 error 0n2

    WARNING: The HOST cannot communicate with the TARGET!"



    It is well known that 1394 and WinDbg are very sensitive to each other and
    I've got a sick feeling this may be the case. Has anyone else run across
    this?



    Gary G. Little

    H (952) 223-1349

    C (952) 454-4629

    xxxxx@comcast.net




    ---
    WINDBG is sponsored by OSR

    For our schedule of WDF, WDM, debugging and other seminars visit:
    http://www.osr.com/seminars

    To unsubscribe, visit the List Server section of OSR Online at
    http://www.osronline.com/page.cfm?name=ListServer

    --- WINDBG is sponsored by OSR For our schedule of WDF, WDM, debugging and
    other seminars visit: http://www.osr.com/seminars To unsubscribe, visit the
    List Server section of OSR Online at
    http://www.osronline.com/page.cfm?name=ListServer


    ---
    WINDBG is sponsored by OSR

    For our schedule of WDF, WDM, debugging and other seminars visit:
    http://www.osr.com/seminars

    To unsubscribe, visit the List Server section of OSR Online at
    http://www.osronline.com/page.cfm?name=ListServer


    ---
    WINDBG is sponsored by OSR

    For our schedule of WDF, WDM, debugging and other seminars visit:
    http://www.osr.com/seminars

    To unsubscribe, visit the List Server section of OSR Online at
    http://www.osronline.com/page.cfm?name=ListServer


    ---
    WINDBG is sponsored by OSR

    For our schedule of WDF, WDM, debugging and other seminars visit:
    http://www.osr.com/seminars

    To unsubscribe, visit the List Server section of OSR Online at
    http://www.osronline.com/page.cfm?name=ListServer


    ---
    WINDBG is sponsored by OSR

    For our schedule of WDF, WDM, debugging and other seminars visit:
    http://www.osr.com/seminars

    To unsubscribe, visit the List Server section of OSR Online at
    http://www.osronline.com/page.cfm?name=ListServer
  • Gary_Little-3Gary_Little-3 Member Posts: 1,208
    Thanks for the hint. I did look but saw nothing even close to that.



    Gary G. Little

    H (952) 223-1349

    C (952) 454-4629

    xxxxx@comcast.net



    From: xxxxx@lists.osr.com
    [mailto:xxxxx@lists.osr.com] On Behalf Of M. M. O'Brien
    Sent: Thursday, June 10, 2010 9:32 AM
    To: Kernel Debugging Interest List
    Subject: RE: [windbg] New laptop and trouble attaching to a 1394 target



    One last thing that I can think of - if there's a BIOS setting named
    something like 'PNP OS,' make sure that it is disabled.





    Good luck,



    mm



    From: xxxxx@lists.osr.com
    [mailto:xxxxx@lists.osr.com] On Behalf Of Gary G. Little
    Sent: Thursday, June 10, 2010 10:18 AM
    To: Kernel Debugging Interest List
    Subject: RE: [windbg] New laptop and trouble attaching to a 1394 target



    Joe,



    As a follow up, I tried a few more things. I entered the BIOS and disabled
    as much of the Media/PC card/1394 as possible to leave only the 1394 card,
    but that did not work. I also force installed the Windows debugger drivers
    but that did not work either. So, at this point it's go to Dell tech support
    who will most likely shrug their shoulders and mumble "Wulll it works on the
    external drive." I probably should do that if nothing else to get a history
    started.



    I also ordered the OSR board and was shocked to find they did not offer a
    seniors discount!?!?!? J



    Gary G. Little

    H (952) 223-1349

    C (952) 454-4629

    xxxxx@comcast.net



    From: xxxxx@lists.osr.com
    [mailto:xxxxx@lists.osr.com] On Behalf Of Gary G. Little
    Sent: Tuesday, June 08, 2010 4:54 PM
    To: Kernel Debugging Interest List
    Subject: RE: [windbg] New laptop and trouble attaching to a 1394 target



    Joe,



    I tried 1394 device, a Seagate external driver, and that connected on the
    1394 bus, installed the driver and provided access. Thanks for the help.



    Gary G. Little

    H (952) 223-1349

    C (952) 454-4629

    xxxxx@comcast.net



    From: xxxxx@lists.osr.com
    [mailto:xxxxx@lists.osr.com] On Behalf Of Joe Ballantyne
    Sent: Tuesday, June 08, 2010 3:48 PM
    To: Kernel Debugging Interest List
    Subject: RE: [windbg] New laptop and trouble attaching to a 1394 target



    The host doesn't see the target machine on the 1394 bus.



    This is either because kd1394.dll does not support the 1394 controller in
    the target machine, or because either the target machine or the host machine
    have more than 1 1394 controller in them.



    Are you using this laptop as a target or as a host?



    Joe.



    From: xxxxx@lists.osr.com
    [mailto:xxxxx@lists.osr.com] On Behalf Of Gary G. Little
    Sent: Tuesday, June 08, 2010 12:31 PM
    To: Kernel Debugging Interest List
    Subject: RE: [windbg] New laptop and trouble attaching to a 1394 target



    Good point and I just did. It just keeps repeating the Synchronize:80070002
    . SYNCTARGET:Timeout. Both target and host are set to channel 10.



    Here is what I get:



    Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64

    Copyright (c) Microsoft Corporation. All rights reserved.



    Using 1394 for debugging

    Checking 1394 debug driver version.

    Opened \\.\DBG1394_INSTANCE10

    Timer Resolution set to 1000 usec.

    Waiting to reconnect...

    ...Synchronize: 80070002

    Synchronize:

    ...Synchronize: 80070002

    Synchronize:

    ...Synchronize: 80070002

    Synchronize:

    ...Synchronize: 80070002

    SYNCTARGET: Timeout.



    Gary G. Little

    H (952) 223-1349

    C (952) 454-4629

    xxxxx@comcast.net







    From: xxxxx@lists.osr.com
    [mailto:xxxxx@lists.osr.com] On Behalf Of MARTIN OBRIEN
    Sent: Tuesday, June 08, 2010 2:23 PM
    To: Kernel Debugging Interest List
    Subject: Re: [windbg] New laptop and trouble attaching to a 1394 target



    Have you tried enabling protocol debugging (CTRL+ALT+D) to see what's going
    on?





    Good afternoon,



    mm







    On Jun 8, 2010 3:15 PM, "Gary G. Little" wrote:

    On this one I am holding my breath. I recently received a new Dell Precision
    M4500 laptop, loaded, and attempted to run WinDbg for the first time. An
    attempt was made to install the driver but that attempt failed, and after a
    reboot I cannot attach to the target. Device manager says the laptop is
    using a RICOH 1394 OHCI compliant host controller. Foolishly I ran WinDbg
    un-elevated the first time, which probably why the install of the driver
    failed. I then updated the 1394 driver to the drivers in the WinDbg
    directory, but that still did not connect. Finally, I did system restore to
    a time before the first aborted run of WinDbg, then a system update followed
    by removing and installing WinDbg. All of that done I elevated WinDbg and
    let'r rip. Samething.



    "Wrote 0 of 1 bytes of the breakin packet.

    Failed to write breakin packet to target. Win32 error 0n2

    WARNING: The HOST cannot communicate with the TARGET!"



    It is well known that 1394 and WinDbg are very sensitive to each other and
    I've got a sick feeling this may be the case. Has anyone else run across
    this?



    Gary G. Little

    H (952) 223-1349

    C (952) 454-4629

    xxxxx@comcast.net




    ---
    WINDBG is sponsored by OSR

    For our schedule of WDF, WDM, debugging and other seminars visit:
    http://www.osr.com/seminars

    To unsubscribe, visit the List Server section of OSR Online at
    http://www.osronline.com/page.cfm?name=ListServer

    --- WINDBG is sponsored by OSR For our schedule of WDF, WDM, debugging and
    other seminars visit: http://www.osr.com/seminars To unsubscribe, visit the
    List Server section of OSR Online at
    http://www.osronline.com/page.cfm?name=ListServer


    ---
    WINDBG is sponsored by OSR

    For our schedule of WDF, WDM, debugging and other seminars visit:
    http://www.osr.com/seminars

    To unsubscribe, visit the List Server section of OSR Online at
    http://www.osronline.com/page.cfm?name=ListServer


    ---
    WINDBG is sponsored by OSR

    For our schedule of WDF, WDM, debugging and other seminars visit:
    http://www.osr.com/seminars

    To unsubscribe, visit the List Server section of OSR Online at
    http://www.osronline.com/page.cfm?name=ListServer


    ---
    WINDBG is sponsored by OSR

    For our schedule of WDF, WDM, debugging and other seminars visit:
    http://www.osr.com/seminars

    To unsubscribe, visit the List Server section of OSR Online at
    http://www.osronline.com/page.cfm?name=ListServer


    ---
    WINDBG is sponsored by OSR

    For our schedule of WDF, WDM, debugging and other seminars visit:
    http://www.osr.com/seminars

    To unsubscribe, visit the List Server section of OSR Online at
    http://www.osronline.com/page.cfm?name=ListServer


    ---
    WINDBG is sponsored by OSR

    For our schedule of WDF, WDM, debugging and other seminars visit:
    http://www.osr.com/seminars

    To unsubscribe, visit the List Server section of OSR Online at
    http://www.osronline.com/page.cfm?name=ListServer
  • Calvin_Guan-3Calvin_Guan-3 Member Posts: 441
    Gary,



    Have you tried enable 1394 Network adapter on both Host and target, plug and
    unplug the cable, see if you are getting cable connect and disconnect
    events? You may need to disable all kd stuff on both sides for this test.



    Once upon a time, there was a cable with a bad connector didn't fully mate
    into **one** of my Dell D830 laptop, but worked fine with other laptops. It
    was on my suspect list because of that.



    Good luck with your M4500.



    Calvin

    P.S. I was struggling between whether I should buy a fully loaded M4500 or a
    MacBook Pro. I like the power of M4500 but I hate it doesn't have
    WUXGA(1920x1200). I'm currently using 2 Latitude D830 and 1 D820 all of them
    are with 15.4" WUXGA. And I can't find any new 15" laptop with WUXGA,
    bummer.





    From: xxxxx@lists.osr.com
    [mailto:xxxxx@lists.osr.com] On Behalf Of Gary G. Little
    Sent: Thursday, June 10, 2010 8:40 AM
    To: Kernel Debugging Interest List
    Subject: RE: [windbg] New laptop and trouble attaching to a 1394 target



    Thanks for the hint. I did look but saw nothing even close to that.



    Gary G. Little

    H (952) 223-1349

    C (952) 454-4629

    xxxxx@comcast.net



    From: xxxxx@lists.osr.com
    [mailto:xxxxx@lists.osr.com] On Behalf Of M. M. O'Brien
    Sent: Thursday, June 10, 2010 9:32 AM
    To: Kernel Debugging Interest List
    Subject: RE: [windbg] New laptop and trouble attaching to a 1394 target



    One last thing that I can think of - if there's a BIOS setting named
    something like 'PNP OS,' make sure that it is disabled.





    Good luck,



    mm



    From: xxxxx@lists.osr.com
    [mailto:xxxxx@lists.osr.com] On Behalf Of Gary G. Little
    Sent: Thursday, June 10, 2010 10:18 AM
    To: Kernel Debugging Interest List
    Subject: RE: [windbg] New laptop and trouble attaching to a 1394 target



    Joe,



    As a follow up, I tried a few more things. I entered the BIOS and disabled
    as much of the Media/PC card/1394 as possible to leave only the 1394 card,
    but that did not work. I also force installed the Windows debugger drivers
    but that did not work either. So, at this point it's go to Dell tech support
    who will most likely shrug their shoulders and mumble "Wulll it works on the
    external drive." I probably should do that if nothing else to get a history
    started.



    I also ordered the OSR board and was shocked to find they did not offer a
    seniors discount!?!?!? J



    Gary G. Little

    H (952) 223-1349

    C (952) 454-4629

    xxxxx@comcast.net



    From: xxxxx@lists.osr.com
    [mailto:xxxxx@lists.osr.com] On Behalf Of Gary G. Little
    Sent: Tuesday, June 08, 2010 4:54 PM
    To: Kernel Debugging Interest List
    Subject: RE: [windbg] New laptop and trouble attaching to a 1394 target



    Joe,



    I tried 1394 device, a Seagate external driver, and that connected on the
    1394 bus, installed the driver and provided access. Thanks for the help.



    Gary G. Little

    H (952) 223-1349

    C (952) 454-4629

    xxxxx@comcast.net



    From: xxxxx@lists.osr.com
    [mailto:xxxxx@lists.osr.com] On Behalf Of Joe Ballantyne
    Sent: Tuesday, June 08, 2010 3:48 PM
    To: Kernel Debugging Interest List
    Subject: RE: [windbg] New laptop and trouble attaching to a 1394 target



    The host doesn't see the target machine on the 1394 bus.



    This is either because kd1394.dll does not support the 1394 controller in
    the target machine, or because either the target machine or the host machine
    have more than 1 1394 controller in them.



    Are you using this laptop as a target or as a host?



    Joe.



    From: xxxxx@lists.osr.com
    [mailto:xxxxx@lists.osr.com] On Behalf Of Gary G. Little
    Sent: Tuesday, June 08, 2010 12:31 PM
    To: Kernel Debugging Interest List
    Subject: RE: [windbg] New laptop and trouble attaching to a 1394 target



    Good point and I just did. It just keeps repeating the Synchronize:80070002
    . SYNCTARGET:Timeout. Both target and host are set to channel 10.



    Here is what I get:



    Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64

    Copyright (c) Microsoft Corporation. All rights reserved.



    Using 1394 for debugging

    Checking 1394 debug driver version.

    Opened \\.\DBG1394_INSTANCE10

    Timer Resolution set to 1000 usec.

    Waiting to reconnect...

    ...Synchronize: 80070002

    Synchronize:

    ...Synchronize: 80070002

    Synchronize:

    ...Synchronize: 80070002

    Synchronize:

    ...Synchronize: 80070002

    SYNCTARGET: Timeout.



    Gary G. Little

    H (952) 223-1349

    C (952) 454-4629

    xxxxx@comcast.net







    From: xxxxx@lists.osr.com
    [mailto:xxxxx@lists.osr.com] On Behalf Of MARTIN OBRIEN
    Sent: Tuesday, June 08, 2010 2:23 PM
    To: Kernel Debugging Interest List
    Subject: Re: [windbg] New laptop and trouble attaching to a 1394 target



    Have you tried enabling protocol debugging (CTRL+ALT+D) to see what's going
    on?





    Good afternoon,



    mm







    On Jun 8, 2010 3:15 PM, "Gary G. Little" wrote:

    On this one I am holding my breath. I recently received a new Dell Precision
    M4500 laptop, loaded, and attempted to run WinDbg for the first time. An
    attempt was made to install the driver but that attempt failed, and after a
    reboot I cannot attach to the target. Device manager says the laptop is
    using a RICOH 1394 OHCI compliant host controller. Foolishly I ran WinDbg
    un-elevated the first time, which probably why the install of the driver
    failed. I then updated the 1394 driver to the drivers in the WinDbg
    directory, but that still did not connect. Finally, I did system restore to
    a time before the first aborted run of WinDbg, then a system update followed
    by removing and installing WinDbg. All of that done I elevated WinDbg and
    let'r rip. Samething.



    "Wrote 0 of 1 bytes of the breakin packet.

    Failed to write breakin packet to target. Win32 error 0n2

    WARNING: The HOST cannot communicate with the TARGET!"



    It is well known that 1394 and WinDbg are very sensitive to each other and
    I've got a sick feeling this may be the case. Has anyone else run across
    this?



    Gary G. Little

    H (952) 223-1349

    C (952) 454-4629

    xxxxx@comcast.net




    ---
    WINDBG is sponsored by OSR

    For our schedule of WDF, WDM, debugging and other seminars visit:
    http://www.osr.com/seminars

    To unsubscribe, visit the List Server section of OSR Online at
    http://www.osronline.com/page.cfm?name=ListServer

    --- WINDBG is sponsored by OSR For our schedule of WDF, WDM, debugging and
    other seminars visit: http://www.osr.com/seminars To unsubscribe, visit the
    List Server section of OSR Online at
    http://www.osronline.com/page.cfm?name=ListServer


    ---
    WINDBG is sponsored by OSR

    For our schedule of WDF, WDM, debugging and other seminars visit:
    http://www.osr.com/seminars

    To unsubscribe, visit the List Server section of OSR Online at
    http://www.osronline.com/page.cfm?name=ListServer


    ---
    WINDBG is sponsored by OSR

    For our schedule of WDF, WDM, debugging and other seminars visit:
    http://www.osr.com/seminars

    To unsubscribe, visit the List Server section of OSR Online at
    http://www.osronline.com/page.cfm?name=ListServer


    ---
    WINDBG is sponsored by OSR

    For our schedule of WDF, WDM, debugging and other seminars visit:
    http://www.osr.com/seminars

    To unsubscribe, visit the List Server section of OSR Online at
    http://www.osronline.com/page.cfm?name=ListServer


    ---
    WINDBG is sponsored by OSR

    For our schedule of WDF, WDM, debugging and other seminars visit:
    http://www.osr.com/seminars

    To unsubscribe, visit the List Server section of OSR Online at
    http://www.osronline.com/page.cfm?name=ListServer


    ---
    WINDBG is sponsored by OSR

    For our schedule of WDF, WDM, debugging and other seminars visit:
    http://www.osr.com/seminars

    To unsubscribe, visit the List Server section of OSR Online at
    http://www.osronline.com/page.cfm?name=ListServer


    ---
    WINDBG is sponsored by OSR

    For our schedule of WDF, WDM, debugging and other seminars visit:
    http://www.osr.com/seminars

    To unsubscribe, visit the List Server section of OSR Online at
    http://www.osronline.com/page.cfm?name=ListServer
  • Gary_Little-3Gary_Little-3 Member Posts: 1,208
    Calvin,



    I've tried just about everything. The cable I use is the same one as is used
    between the target and the laptop this one is replacing and it works fine
    there. I've jiggled the cable, even tried standing on my head in the corner
    and braying like a jackass - that my dogs loved by the way. As far as
    connect/disconnect, the only thing I have to check that is the external
    driver, which requires a different cable, and that worked fine.



    I've owned Dells now for about 15 years and have always been well served by
    them. Problems have always been rapidly taken care of, and with this last
    set of laptops I get the next business day service. I've had technicians
    walk in to replace touch pads and case tops and have only the downtime of
    the technician in the house. That's kind of critical when you're a one horse
    operation and can't work if you have to send your laptop somewhere to get it
    fixed. Other than the 1394 problem, the 4500 is sweet, and I still have not
    ruled out operator headspace on the debugger connection.



    Gary G. Little

    H (952) 223-1349

    C (952) 454-4629

    xxxxx@comcast.net



    From: xxxxx@lists.osr.com
    [mailto:xxxxx@lists.osr.com] On Behalf Of Calvin Guan
    Sent: Thursday, June 10, 2010 11:38 AM
    To: Kernel Debugging Interest List
    Subject: RE: [windbg] New laptop and trouble attaching to a 1394 target



    Gary,



    Have you tried enable 1394 Network adapter on both Host and target, plug and
    unplug the cable, see if you are getting cable connect and disconnect
    events? You may need to disable all kd stuff on both sides for this test.



    Once upon a time, there was a cable with a bad connector didn't fully mate
    into **one** of my Dell D830 laptop, but worked fine with other laptops. It
    was on my suspect list because of that.



    Good luck with your M4500.



    Calvin

    P.S. I was struggling between whether I should buy a fully loaded M4500 or a
    MacBook Pro. I like the power of M4500 but I hate it doesn't have
    WUXGA(1920x1200). I'm currently using 2 Latitude D830 and 1 D820 all of them
    are with 15.4" WUXGA. And I can't find any new 15" laptop with WUXGA,
    bummer.





    From: xxxxx@lists.osr.com
    [mailto:xxxxx@lists.osr.com] On Behalf Of Gary G. Little
    Sent: Thursday, June 10, 2010 8:40 AM
    To: Kernel Debugging Interest List
    Subject: RE: [windbg] New laptop and trouble attaching to a 1394 target



    Thanks for the hint. I did look but saw nothing even close to that.



    Gary G. Little

    H (952) 223-1349

    C (952) 454-4629

    xxxxx@comcast.net



    From: xxxxx@lists.osr.com
    [mailto:xxxxx@lists.osr.com] On Behalf Of M. M. O'Brien
    Sent: Thursday, June 10, 2010 9:32 AM
    To: Kernel Debugging Interest List
    Subject: RE: [windbg] New laptop and trouble attaching to a 1394 target



    One last thing that I can think of - if there's a BIOS setting named
    something like 'PNP OS,' make sure that it is disabled.





    Good luck,



    mm



    From: xxxxx@lists.osr.com
    [mailto:xxxxx@lists.osr.com] On Behalf Of Gary G. Little
    Sent: Thursday, June 10, 2010 10:18 AM
    To: Kernel Debugging Interest List
    Subject: RE: [windbg] New laptop and trouble attaching to a 1394 target



    Joe,



    As a follow up, I tried a few more things. I entered the BIOS and disabled
    as much of the Media/PC card/1394 as possible to leave only the 1394 card,
    but that did not work. I also force installed the Windows debugger drivers
    but that did not work either. So, at this point it's go to Dell tech support
    who will most likely shrug their shoulders and mumble "Wulll it works on the
    external drive." I probably should do that if nothing else to get a history
    started.



    I also ordered the OSR board and was shocked to find they did not offer a
    seniors discount!?!?!? J



    Gary G. Little

    H (952) 223-1349

    C (952) 454-4629

    xxxxx@comcast.net



    From: xxxxx@lists.osr.com
    [mailto:xxxxx@lists.osr.com] On Behalf Of Gary G. Little
    Sent: Tuesday, June 08, 2010 4:54 PM
    To: Kernel Debugging Interest List
    Subject: RE: [windbg] New laptop and trouble attaching to a 1394 target



    Joe,



    I tried 1394 device, a Seagate external driver, and that connected on the
    1394 bus, installed the driver and provided access. Thanks for the help.



    Gary G. Little

    H (952) 223-1349

    C (952) 454-4629

    xxxxx@comcast.net



    From: xxxxx@lists.osr.com
    [mailto:xxxxx@lists.osr.com] On Behalf Of Joe Ballantyne
    Sent: Tuesday, June 08, 2010 3:48 PM
    To: Kernel Debugging Interest List
    Subject: RE: [windbg] New laptop and trouble attaching to a 1394 target



    The host doesn't see the target machine on the 1394 bus.



    This is either because kd1394.dll does not support the 1394 controller in
    the target machine, or because either the target machine or the host machine
    have more than 1 1394 controller in them.



    Are you using this laptop as a target or as a host?



    Joe.



    From: xxxxx@lists.osr.com
    [mailto:xxxxx@lists.osr.com] On Behalf Of Gary G. Little
    Sent: Tuesday, June 08, 2010 12:31 PM
    To: Kernel Debugging Interest List
    Subject: RE: [windbg] New laptop and trouble attaching to a 1394 target



    Good point and I just did. It just keeps repeating the Synchronize:80070002
    . SYNCTARGET:Timeout. Both target and host are set to channel 10.



    Here is what I get:



    Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64

    Copyright (c) Microsoft Corporation. All rights reserved.



    Using 1394 for debugging

    Checking 1394 debug driver version.

    Opened \\.\DBG1394_INSTANCE10

    Timer Resolution set to 1000 usec.

    Waiting to reconnect...

    ...Synchronize: 80070002

    Synchronize:

    ...Synchronize: 80070002

    Synchronize:

    ...Synchronize: 80070002

    Synchronize:

    ...Synchronize: 80070002

    SYNCTARGET: Timeout.



    Gary G. Little

    H (952) 223-1349

    C (952) 454-4629

    xxxxx@comcast.net







    From: xxxxx@lists.osr.com
    [mailto:xxxxx@lists.osr.com] On Behalf Of MARTIN OBRIEN
    Sent: Tuesday, June 08, 2010 2:23 PM
    To: Kernel Debugging Interest List
    Subject: Re: [windbg] New laptop and trouble attaching to a 1394 target



    Have you tried enabling protocol debugging (CTRL+ALT+D) to see what's going
    on?





    Good afternoon,



    mm







    On Jun 8, 2010 3:15 PM, "Gary G. Little" wrote:

    On this one I am holding my breath. I recently received a new Dell Precision
    M4500 laptop, loaded, and attempted to run WinDbg for the first time. An
    attempt was made to install the driver but that attempt failed, and after a
    reboot I cannot attach to the target. Device manager says the laptop is
    using a RICOH 1394 OHCI compliant host controller. Foolishly I ran WinDbg
    un-elevated the first time, which probably why the install of the driver
    failed. I then updated the 1394 driver to the drivers in the WinDbg
    directory, but that still did not connect. Finally, I did system restore to
    a time before the first aborted run of WinDbg, then a system update followed
    by removing and installing WinDbg. All of that done I elevated WinDbg and
    let'r rip. Samething.



    "Wrote 0 of 1 bytes of the breakin packet.

    Failed to write breakin packet to target. Win32 error 0n2

    WARNING: The HOST cannot communicate with the TARGET!"



    It is well known that 1394 and WinDbg are very sensitive to each other and
    I've got a sick feeling this may be the case. Has anyone else run across
    this?



    Gary G. Little

    H (952) 223-1349

    C (952) 454-4629

    xxxxx@comcast.net




    ---
    WINDBG is sponsored by OSR

    For our schedule of WDF, WDM, debugging and other seminars visit:
    http://www.osr.com/seminars

    To unsubscribe, visit the List Server section of OSR Online at
    http://www.osronline.com/page.cfm?name=ListServer

    --- WINDBG is sponsored by OSR For our schedule of WDF, WDM, debugging and
    other seminars visit: http://www.osr.com/seminars To unsubscribe, visit the
    List Server section of OSR Online at
    http://www.osronline.com/page.cfm?name=ListServer


    ---
    WINDBG is sponsored by OSR

    For our schedule of WDF, WDM, debugging and other seminars visit:
    http://www.osr.com/seminars

    To unsubscribe, visit the List Server section of OSR Online at
    http://www.osronline.com/page.cfm?name=ListServer


    ---
    WINDBG is sponsored by OSR

    For our schedule of WDF, WDM, debugging and other seminars visit:
    http://www.osr.com/seminars

    To unsubscribe, visit the List Server section of OSR Online at
    http://www.osronline.com/page.cfm?name=ListServer


    ---
    WINDBG is sponsored by OSR

    For our schedule of WDF, WDM, debugging and other seminars visit:
    http://www.osr.com/seminars

    To unsubscribe, visit the List Server section of OSR Online at
    http://www.osronline.com/page.cfm?name=ListServer


    ---
    WINDBG is sponsored by OSR

    For our schedule of WDF, WDM, debugging and other seminars visit:
    http://www.osr.com/seminars

    To unsubscribe, visit the List Server section of OSR Online at
    http://www.osronline.com/page.cfm?name=ListServer


    ---
    WINDBG is sponsored by OSR

    For our schedule of WDF, WDM, debugging and other seminars visit:
    http://www.osr.com/seminars

    To unsubscribe, visit the List Server section of OSR Online at
    http://www.osronline.com/page.cfm?name=ListServer


    ---
    WINDBG is sponsored by OSR

    For our schedule of WDF, WDM, debugging and other seminars visit:
    http://www.osr.com/seminars

    To unsubscribe, visit the List Server section of OSR Online at
    http://www.osronline.com/page.cfm?name=ListServer


    ---
    WINDBG is sponsored by OSR

    For our schedule of WDF, WDM, debugging and other seminars visit:
    http://www.osr.com/seminars

    To unsubscribe, visit the List Server section of OSR Online at
    http://www.osronline.com/page.cfm?name=ListServer
  • mmmm Member - All Emails Posts: 1,409
    Not a problem, Gary. Too bad it didn't help.





    mm



    From: xxxxx@lists.osr.com
    [mailto:xxxxx@lists.osr.com] On Behalf Of Gary G. Little
    Sent: Thursday, June 10, 2010 11:40 AM
    To: Kernel Debugging Interest List
    Subject: RE: [windbg] New laptop and trouble attaching to a 1394 target



    Thanks for the hint. I did look but saw nothing even close to that.



    Gary G. Little

    H (952) 223-1349

    C (952) 454-4629

    xxxxx@comcast.net



    From: xxxxx@lists.osr.com
    [mailto:xxxxx@lists.osr.com] On Behalf Of M. M. O'Brien
    Sent: Thursday, June 10, 2010 9:32 AM
    To: Kernel Debugging Interest List
    Subject: RE: [windbg] New laptop and trouble attaching to a 1394 target



    One last thing that I can think of - if there's a BIOS setting named
    something like 'PNP OS,' make sure that it is disabled.





    Good luck,



    mm



    From: xxxxx@lists.osr.com
    [mailto:xxxxx@lists.osr.com] On Behalf Of Gary G. Little
    Sent: Thursday, June 10, 2010 10:18 AM
    To: Kernel Debugging Interest List
    Subject: RE: [windbg] New laptop and trouble attaching to a 1394 target



    Joe,



    As a follow up, I tried a few more things. I entered the BIOS and disabled
    as much of the Media/PC card/1394 as possible to leave only the 1394 card,
    but that did not work. I also force installed the Windows debugger drivers
    but that did not work either. So, at this point it's go to Dell tech support
    who will most likely shrug their shoulders and mumble "Wulll it works on the
    external drive." I probably should do that if nothing else to get a history
    started.



    I also ordered the OSR board and was shocked to find they did not offer a
    seniors discount!?!?!? J



    Gary G. Little

    H (952) 223-1349

    C (952) 454-4629

    xxxxx@comcast.net



    From: xxxxx@lists.osr.com
    [mailto:xxxxx@lists.osr.com] On Behalf Of Gary G. Little
    Sent: Tuesday, June 08, 2010 4:54 PM
    To: Kernel Debugging Interest List
    Subject: RE: [windbg] New laptop and trouble attaching to a 1394 target



    Joe,



    I tried 1394 device, a Seagate external driver, and that connected on the
    1394 bus, installed the driver and provided access. Thanks for the help.



    Gary G. Little

    H (952) 223-1349

    C (952) 454-4629

    xxxxx@comcast.net



    From: xxxxx@lists.osr.com
    [mailto:xxxxx@lists.osr.com] On Behalf Of Joe Ballantyne
    Sent: Tuesday, June 08, 2010 3:48 PM
    To: Kernel Debugging Interest List
    Subject: RE: [windbg] New laptop and trouble attaching to a 1394 target



    The host doesn't see the target machine on the 1394 bus.



    This is either because kd1394.dll does not support the 1394 controller in
    the target machine, or because either the target machine or the host machine
    have more than 1 1394 controller in them.



    Are you using this laptop as a target or as a host?



    Joe.



    From: xxxxx@lists.osr.com
    [mailto:xxxxx@lists.osr.com] On Behalf Of Gary G. Little
    Sent: Tuesday, June 08, 2010 12:31 PM
    To: Kernel Debugging Interest List
    Subject: RE: [windbg] New laptop and trouble attaching to a 1394 target



    Good point and I just did. It just keeps repeating the Synchronize:80070002
    . SYNCTARGET:Timeout. Both target and host are set to channel 10.



    Here is what I get:



    Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64

    Copyright (c) Microsoft Corporation. All rights reserved.



    Using 1394 for debugging

    Checking 1394 debug driver version.

    Opened \\.\DBG1394_INSTANCE10

    Timer Resolution set to 1000 usec.

    Waiting to reconnect...

    ...Synchronize: 80070002

    Synchronize:

    ...Synchronize: 80070002

    Synchronize:

    ...Synchronize: 80070002

    Synchronize:

    ...Synchronize: 80070002

    SYNCTARGET: Timeout.



    Gary G. Little

    H (952) 223-1349

    C (952) 454-4629

    xxxxx@comcast.net







    From: xxxxx@lists.osr.com
    [mailto:xxxxx@lists.osr.com] On Behalf Of MARTIN OBRIEN
    Sent: Tuesday, June 08, 2010 2:23 PM
    To: Kernel Debugging Interest List
    Subject: Re: [windbg] New laptop and trouble attaching to a 1394 target



    Have you tried enabling protocol debugging (CTRL+ALT+D) to see what's going
    on?





    Good afternoon,



    mm







    On Jun 8, 2010 3:15 PM, "Gary G. Little" wrote:

    On this one I am holding my breath. I recently received a new Dell Precision
    M4500 laptop, loaded, and attempted to run WinDbg for the first time. An
    attempt was made to install the driver but that attempt failed, and after a
    reboot I cannot attach to the target. Device manager says the laptop is
    using a RICOH 1394 OHCI compliant host controller. Foolishly I ran WinDbg
    un-elevated the first time, which probably why the install of the driver
    failed. I then updated the 1394 driver to the drivers in the WinDbg
    directory, but that still did not connect. Finally, I did system restore to
    a time before the first aborted run of WinDbg, then a system update followed
    by removing and installing WinDbg. All of that done I elevated WinDbg and
    let'r rip. Samething.



    "Wrote 0 of 1 bytes of the breakin packet.

    Failed to write breakin packet to target. Win32 error 0n2

    WARNING: The HOST cannot communicate with the TARGET!"



    It is well known that 1394 and WinDbg are very sensitive to each other and
    I've got a sick feeling this may be the case. Has anyone else run across
    this?



    Gary G. Little

    H (952) 223-1349

    C (952) 454-4629

    xxxxx@comcast.net




    ---
    WINDBG is sponsored by OSR

    For our schedule of WDF, WDM, debugging and other seminars visit:
    http://www.osr.com/seminars

    To unsubscribe, visit the List Server section of OSR Online at
    http://www.osronline.com/page.cfm?name=ListServer

    --- WINDBG is sponsored by OSR For our schedule of WDF, WDM, debugging and
    other seminars visit: http://www.osr.com/seminars To unsubscribe, visit the
    List Server section of OSR Online at
    http://www.osronline.com/page.cfm?name=ListServer


    ---
    WINDBG is sponsored by OSR

    For our schedule of WDF, WDM, debugging and other seminars visit:
    http://www.osr.com/seminars

    To unsubscribe, visit the List Server section of OSR Online at
    http://www.osronline.com/page.cfm?name=ListServer


    ---
    WINDBG is sponsored by OSR

    For our schedule of WDF, WDM, debugging and other seminars visit:
    http://www.osr.com/seminars

    To unsubscribe, visit the List Server section of OSR Online at
    http://www.osronline.com/page.cfm?name=ListServer


    ---
    WINDBG is sponsored by OSR

    For our schedule of WDF, WDM, debugging and other seminars visit:
    http://www.osr.com/seminars

    To unsubscribe, visit the List Server section of OSR Online at
    http://www.osronline.com/page.cfm?name=ListServer


    ---
    WINDBG is sponsored by OSR

    For our schedule of WDF, WDM, debugging and other seminars visit:
    http://www.osr.com/seminars

    To unsubscribe, visit the List Server section of OSR Online at
    http://www.osronline.com/page.cfm?name=ListServer


    ---
    WINDBG is sponsored by OSR

    For our schedule of WDF, WDM, debugging and other seminars visit:
    http://www.osr.com/seminars

    To unsubscribe, visit the List Server section of OSR Online at
    http://www.osronline.com/page.cfm?name=ListServer


    ---
    WINDBG is sponsored by OSR

    For our schedule of WDF, WDM, debugging and other seminars visit:
    http://www.osr.com/seminars

    To unsubscribe, visit the List Server section of OSR Online at
    http://www.osronline.com/page.cfm?name=ListServer
  • OSR_Community_UserOSR_Community_User Member Posts: 110,217
    I have one system here (win 7 64, 1394 chip VEN_197B&DEV_2380) that you have
    to use the legacy 1394 driver on the windbg machine. You can go into device
    manager and manually pick the legacy driver over the new and improved one.
    If you don't do this, .kdfiles will not work correctly (gets errors).



    I have another Dell laptop with a Richoh 1394 chipset that works
    terrifically for kernel debugging (both as a target and debugger).



    Jan



    p.s. Calvin must have way better eyesight than me if he can read 1920x1200
    on a 15" screen



    From: xxxxx@lists.osr.com
    [mailto:xxxxx@lists.osr.com] On Behalf Of Gary G. Little
    Sent: Thursday, June 10, 2010 10:29 AM
    To: Kernel Debugging Interest List
    Subject: RE: [windbg] New laptop and trouble attaching to a 1394 target



    Calvin,



    I've tried just about everything. The cable I use is the same one as is used
    between the target and the laptop this one is replacing and it works fine
    there. I've jiggled the cable, even tried standing on my head in the corner
    and braying like a jackass - that my dogs loved by the way. As far as
    connect/disconnect, the only thing I have to check that is the external
    driver, which requires a different cable, and that worked fine.



    I've owned Dells now for about 15 years and have always been well served by
    them. Problems have always been rapidly taken care of, and with this last
    set of laptops I get the next business day service. I've had technicians
    walk in to replace touch pads and case tops and have only the downtime of
    the technician in the house. That's kind of critical when you're a one horse
    operation and can't work if you have to send your laptop somewhere to get it
    fixed. Other than the 1394 problem, the 4500 is sweet, and I still have not
    ruled out operator headspace on the debugger connection.



    Gary G. Little

    H (952) 223-1349

    C (952) 454-4629

    xxxxx@comcast.net



    From: xxxxx@lists.osr.com
    [mailto:xxxxx@lists.osr.com] On Behalf Of Calvin Guan
    Sent: Thursday, June 10, 2010 11:38 AM
    To: Kernel Debugging Interest List
    Subject: RE: [windbg] New laptop and trouble attaching to a 1394 target



    Gary,



    Have you tried enable 1394 Network adapter on both Host and target, plug and
    unplug the cable, see if you are getting cable connect and disconnect
    events? You may need to disable all kd stuff on both sides for this test.



    Once upon a time, there was a cable with a bad connector didn't fully mate
    into **one** of my Dell D830 laptop, but worked fine with other laptops. It
    was on my suspect list because of that.



    Good luck with your M4500.



    Calvin

    P.S. I was struggling between whether I should buy a fully loaded M4500 or a
    MacBook Pro. I like the power of M4500 but I hate it doesn't have
    WUXGA(1920x1200). I'm currently using 2 Latitude D830 and 1 D820 all of them
    are with 15.4" WUXGA. And I can't find any new 15" laptop with WUXGA,
    bummer.





    From: xxxxx@lists.osr.com
    [mailto:xxxxx@lists.osr.com] On Behalf Of Gary G. Little
    Sent: Thursday, June 10, 2010 8:40 AM
    To: Kernel Debugging Interest List
    Subject: RE: [windbg] New laptop and trouble attaching to a 1394 target



    Thanks for the hint. I did look but saw nothing even close to that.



    Gary G. Little

    H (952) 223-1349

    C (952) 454-4629

    xxxxx@comcast.net



    From: xxxxx@lists.osr.com
    [mailto:xxxxx@lists.osr.com] On Behalf Of M. M. O'Brien
    Sent: Thursday, June 10, 2010 9:32 AM
    To: Kernel Debugging Interest List
    Subject: RE: [windbg] New laptop and trouble attaching to a 1394 target



    One last thing that I can think of - if there's a BIOS setting named
    something like 'PNP OS,' make sure that it is disabled.





    Good luck,



    mm



    From: xxxxx@lists.osr.com
    [mailto:xxxxx@lists.osr.com] On Behalf Of Gary G. Little
    Sent: Thursday, June 10, 2010 10:18 AM
    To: Kernel Debugging Interest List
    Subject: RE: [windbg] New laptop and trouble attaching to a 1394 target



    Joe,



    As a follow up, I tried a few more things. I entered the BIOS and disabled
    as much of the Media/PC card/1394 as possible to leave only the 1394 card,
    but that did not work. I also force installed the Windows debugger drivers
    but that did not work either. So, at this point it's go to Dell tech support
    who will most likely shrug their shoulders and mumble "Wulll it works on the
    external drive." I probably should do that if nothing else to get a history
    started.



    I also ordered the OSR board and was shocked to find they did not offer a
    seniors discount!?!?!? J



    Gary G. Little

    H (952) 223-1349

    C (952) 454-4629

    xxxxx@comcast.net



    From: xxxxx@lists.osr.com
    [mailto:xxxxx@lists.osr.com] On Behalf Of Gary G. Little
    Sent: Tuesday, June 08, 2010 4:54 PM
    To: Kernel Debugging Interest List
    Subject: RE: [windbg] New laptop and trouble attaching to a 1394 target



    Joe,



    I tried 1394 device, a Seagate external driver, and that connected on the
    1394 bus, installed the driver and provided access. Thanks for the help.



    Gary G. Little

    H (952) 223-1349

    C (952) 454-4629

    xxxxx@comcast.net



    From: xxxxx@lists.osr.com
    [mailto:xxxxx@lists.osr.com] On Behalf Of Joe Ballantyne
    Sent: Tuesday, June 08, 2010 3:48 PM
    To: Kernel Debugging Interest List
    Subject: RE: [windbg] New laptop and trouble attaching to a 1394 target



    The host doesn't see the target machine on the 1394 bus.



    This is either because kd1394.dll does not support the 1394 controller in
    the target machine, or because either the target machine or the host machine
    have more than 1 1394 controller in them.



    Are you using this laptop as a target or as a host?



    Joe.



    From: xxxxx@lists.osr.com
    [mailto:xxxxx@lists.osr.com] On Behalf Of Gary G. Little
    Sent: Tuesday, June 08, 2010 12:31 PM
    To: Kernel Debugging Interest List
    Subject: RE: [windbg] New laptop and trouble attaching to a 1394 target



    Good point and I just did. It just keeps repeating the Synchronize:80070002
    . SYNCTARGET:Timeout. Both target and host are set to channel 10.



    Here is what I get:



    Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64

    Copyright (c) Microsoft Corporation. All rights reserved.



    Using 1394 for debugging

    Checking 1394 debug driver version.

    Opened \\.\DBG1394_INSTANCE10

    Timer Resolution set to 1000 usec.

    Waiting to reconnect...

    ...Synchronize: 80070002

    Synchronize:

    ...Synchronize: 80070002

    Synchronize:

    ...Synchronize: 80070002

    Synchronize:

    ...Synchronize: 80070002

    SYNCTARGET: Timeout.



    Gary G. Little

    H (952) 223-1349

    C (952) 454-4629

    xxxxx@comcast.net







    From: xxxxx@lists.osr.com
    [mailto:xxxxx@lists.osr.com] On Behalf Of MARTIN OBRIEN
    Sent: Tuesday, June 08, 2010 2:23 PM
    To: Kernel Debugging Interest List
    Subject: Re: [windbg] New laptop and trouble attaching to a 1394 target



    Have you tried enabling protocol debugging (CTRL+ALT+D) to see what's going
    on?





    Good afternoon,



    mm







    On Jun 8, 2010 3:15 PM, "Gary G. Little" wrote:

    On this one I am holding my breath. I recently received a new Dell Precision
    M4500 laptop, loaded, and attempted to run WinDbg for the first time. An
    attempt was made to install the driver but that attempt failed, and after a
    reboot I cannot attach to the target. Device manager says the laptop is
    using a RICOH 1394 OHCI compliant host controller. Foolishly I ran WinDbg
    un-elevated the first time, which probably why the install of the driver
    failed. I then updated the 1394 driver to the drivers in the WinDbg
    directory, but that still did not connect. Finally, I did system restore to
    a time before the first aborted run of WinDbg, then a system update followed
    by removing and installing WinDbg. All of that done I elevated WinDbg and
    let'r rip. Samething.



    "Wrote 0 of 1 bytes of the breakin packet.

    Failed to write breakin packet to target. Win32 error 0n2

    WARNING: The HOST cannot communicate with the TARGET!"



    It is well known that 1394 and WinDbg are very sensitive to each other and
    I've got a sick feeling this may be the case. Has anyone else run across
    this?



    Gary G. Little

    H (952) 223-1349

    C (952) 454-4629

    xxxxx@comcast.net




    ---
    WINDBG is sponsored by OSR

    For our schedule of WDF, WDM, debugging and other seminars visit:
    http://www.osr.com/seminars

    To unsubscribe, visit the List Server section of OSR Online at
    http://www.osronline.com/page.cfm?name=ListServer

    --- WINDBG is sponsored by OSR For our schedule of WDF, WDM, debugging and
    other seminars visit: http://www.osr.com/seminars To unsubscribe, visit the
    List Server section of OSR Online at
    http://www.osronline.com/page.cfm?name=ListServer


    ---
    WINDBG is sponsored by OSR

    For our schedule of WDF, WDM, debugging and other seminars visit:
    http://www.osr.com/seminars

    To unsubscribe, visit the List Server section of OSR Online at
    http://www.osronline.com/page.cfm?name=ListServer


    ---
    WINDBG is sponsored by OSR

    For our schedule of WDF, WDM, debugging and other seminars visit:
    http://www.osr.com/seminars

    To unsubscribe, visit the List Server section of OSR Online at
    http://www.osronline.com/page.cfm?name=ListServer


    ---
    WINDBG is sponsored by OSR

    For our schedule of WDF, WDM, debugging and other seminars visit:
    http://www.osr.com/seminars

    To unsubscribe, visit the List Server section of OSR Online at
    http://www.osronline.com/page.cfm?name=ListServer


    ---
    WINDBG is sponsored by OSR

    For our schedule of WDF, WDM, debugging and other seminars visit:
    http://www.osr.com/seminars

    To unsubscribe, visit the List Server section of OSR Online at
    http://www.osronline.com/page.cfm?name=ListServer


    ---
    WINDBG is sponsored by OSR

    For our schedule of WDF, WDM, debugging and other seminars visit:
    http://www.osr.com/seminars

    To unsubscribe, visit the List Server section of OSR Online at
    http://www.osronline.com/page.cfm?name=ListServer


    ---
    WINDBG is sponsored by OSR

    For our schedule of WDF, WDM, debugging and other seminars visit:
    http://www.osr.com/seminars

    To unsubscribe, visit the List Server section of OSR Online at
    http://www.osronline.com/page.cfm?name=ListServer


    ---
    WINDBG is sponsored by OSR

    For our schedule of WDF, WDM, debugging and other seminars visit:
    http://www.osr.com/seminars

    To unsubscribe, visit the List Server section of OSR Online at
    http://www.osronline.com/page.cfm?name=ListServer


    ---
    WINDBG is sponsored by OSR

    For our schedule of WDF, WDM, debugging and other seminars visit:
    http://www.osr.com/seminars

    To unsubscribe, visit the List Server section of OSR Online at
    http://www.osronline.com/page.cfm?name=ListServer
  • Gary_Little-3Gary_Little-3 Member Posts: 1,208
    Thanks Jan.



    I tried the legacy drivers, but the drivers did not load, so I switched back
    to the newer drivers or the Ricoh drivers delivered with the Dell. I got the
    OSR board PCMCIA 1394 on Friday and have disabled the on-board 1394 support
    on the laptop. I'll see tomorrow if the card works, now that I have the 1394
    debugger on top of the Texas Instruments 1394 drivers. That is supposed to
    be the "magic" combination.



    I think a lot of it is what you get used to, what you like, and with what
    you will put up. I've always liked as much screen real-estate as possible,
    so generally I max-out the resolution and keep the text at the default which
    used to be 96pt, now it is "Medium". I'm 63, wear variable focus lenses and
    have had younger folks walk up behind me and exclaim "How do read that!!".



    Gary G. Little

    H (952) 223-1349

    C (952) 454-4629

    xxxxx@comcast.net



    From: xxxxx@lists.osr.com
    [mailto:xxxxx@lists.osr.com] On Behalf Of Jan Bottorff
    Sent: Sunday, June 13, 2010 7:18 PM
    To: Kernel Debugging Interest List
    Subject: RE: [windbg] New laptop and trouble attaching to a 1394 target



    I have one system here (win 7 64, 1394 chip VEN_197B&DEV_2380) that you have
    to use the legacy 1394 driver on the windbg machine. You can go into device
    manager and manually pick the legacy driver over the new and improved one.
    If you don't do this, .kdfiles will not work correctly (gets errors).



    I have another Dell laptop with a Richoh 1394 chipset that works
    terrifically for kernel debugging (both as a target and debugger).



    Jan



    p.s. Calvin must have way better eyesight than me if he can read 1920x1200
    on a 15" screen



    From: xxxxx@lists.osr.com
    [mailto:xxxxx@lists.osr.com] On Behalf Of Gary G. Little
    Sent: Thursday, June 10, 2010 10:29 AM
    To: Kernel Debugging Interest List
    Subject: RE: [windbg] New laptop and trouble attaching to a 1394 target



    Calvin,



    I've tried just about everything. The cable I use is the same one as is used
    between the target and the laptop this one is replacing and it works fine
    there. I've jiggled the cable, even tried standing on my head in the corner
    and braying like a jackass - that my dogs loved by the way. As far as
    connect/disconnect, the only thing I have to check that is the external
    driver, which requires a different cable, and that worked fine.



    I've owned Dells now for about 15 years and have always been well served by
    them. Problems have always been rapidly taken care of, and with this last
    set of laptops I get the next business day service. I've had technicians
    walk in to replace touch pads and case tops and have only the downtime of
    the technician in the house. That's kind of critical when you're a one horse
    operation and can't work if you have to send your laptop somewhere to get it
    fixed. Other than the 1394 problem, the 4500 is sweet, and I still have not
    ruled out operator headspace on the debugger connection.



    Gary G. Little

    H (952) 223-1349

    C (952) 454-4629

    xxxxx@comcast.net



    From: xxxxx@lists.osr.com
    [mailto:xxxxx@lists.osr.com] On Behalf Of Calvin Guan
    Sent: Thursday, June 10, 2010 11:38 AM
    To: Kernel Debugging Interest List
    Subject: RE: [windbg] New laptop and trouble attaching to a 1394 target



    Gary,



    Have you tried enable 1394 Network adapter on both Host and target, plug and
    unplug the cable, see if you are getting cable connect and disconnect
    events? You may need to disable all kd stuff on both sides for this test.



    Once upon a time, there was a cable with a bad connector didn't fully mate
    into **one** of my Dell D830 laptop, but worked fine with other laptops. It
    was on my suspect list because of that.



    Good luck with your M4500.



    Calvin

    P.S. I was struggling between whether I should buy a fully loaded M4500 or a
    MacBook Pro. I like the power of M4500 but I hate it doesn't have
    WUXGA(1920x1200). I'm currently using 2 Latitude D830 and 1 D820 all of them
    are with 15.4" WUXGA. And I can't find any new 15" laptop with WUXGA,
    bummer.





    From: xxxxx@lists.osr.com
    [mailto:xxxxx@lists.osr.com] On Behalf Of Gary G. Little
    Sent: Thursday, June 10, 2010 8:40 AM
    To: Kernel Debugging Interest List
    Subject: RE: [windbg] New laptop and trouble attaching to a 1394 target



    Thanks for the hint. I did look but saw nothing even close to that.



    Gary G. Little

    H (952) 223-1349

    C (952) 454-4629

    xxxxx@comcast.net



    From: xxxxx@lists.osr.com
    [mailto:xxxxx@lists.osr.com] On Behalf Of M. M. O'Brien
    Sent: Thursday, June 10, 2010 9:32 AM
    To: Kernel Debugging Interest List
    Subject: RE: [windbg] New laptop and trouble attaching to a 1394 target



    One last thing that I can think of - if there's a BIOS setting named
    something like 'PNP OS,' make sure that it is disabled.





    Good luck,



    mm



    From: xxxxx@lists.osr.com
    [mailto:xxxxx@lists.osr.com] On Behalf Of Gary G. Little
    Sent: Thursday, June 10, 2010 10:18 AM
    To: Kernel Debugging Interest List
    Subject: RE: [windbg] New laptop and trouble attaching to a 1394 target



    Joe,



    As a follow up, I tried a few more things. I entered the BIOS and disabled
    as much of the Media/PC card/1394 as possible to leave only the 1394 card,
    but that did not work. I also force installed the Windows debugger drivers
    but that did not work either. So, at this point it's go to Dell tech support
    who will most likely shrug their shoulders and mumble "Wulll it works on the
    external drive." I probably should do that if nothing else to get a history
    started.



    I also ordered the OSR board and was shocked to find they did not offer a
    seniors discount!?!?!? J



    Gary G. Little

    H (952) 223-1349

    C (952) 454-4629

    xxxxx@comcast.net



    From: xxxxx@lists.osr.com
    [mailto:xxxxx@lists.osr.com] On Behalf Of Gary G. Little
    Sent: Tuesday, June 08, 2010 4:54 PM
    To: Kernel Debugging Interest List
    Subject: RE: [windbg] New laptop and trouble attaching to a 1394 target



    Joe,



    I tried 1394 device, a Seagate external driver, and that connected on the
    1394 bus, installed the driver and provided access. Thanks for the help.



    Gary G. Little

    H (952) 223-1349

    C (952) 454-4629

    xxxxx@comcast.net



    From: xxxxx@lists.osr.com
    [mailto:xxxxx@lists.osr.com] On Behalf Of Joe Ballantyne
    Sent: Tuesday, June 08, 2010 3:48 PM
    To: Kernel Debugging Interest List
    Subject: RE: [windbg] New laptop and trouble attaching to a 1394 target



    The host doesn't see the target machine on the 1394 bus.



    This is either because kd1394.dll does not support the 1394 controller in
    the target machine, or because either the target machine or the host machine
    have more than 1 1394 controller in them.



    Are you using this laptop as a target or as a host?



    Joe.



    From: xxxxx@lists.osr.com
    [mailto:xxxxx@lists.osr.com] On Behalf Of Gary G. Little
    Sent: Tuesday, June 08, 2010 12:31 PM
    To: Kernel Debugging Interest List
    Subject: RE: [windbg] New laptop and trouble attaching to a 1394 target



    Good point and I just did. It just keeps repeating the Synchronize:80070002
    . SYNCTARGET:Timeout. Both target and host are set to channel 10.



    Here is what I get:



    Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64

    Copyright (c) Microsoft Corporation. All rights reserved.



    Using 1394 for debugging

    Checking 1394 debug driver version.

    Opened \\.\DBG1394_INSTANCE10

    Timer Resolution set to 1000 usec.

    Waiting to reconnect...

    ...Synchronize: 80070002

    Synchronize:

    ...Synchronize: 80070002

    Synchronize:

    ...Synchronize: 80070002

    Synchronize:

    ...Synchronize: 80070002

    SYNCTARGET: Timeout.



    Gary G. Little

    H (952) 223-1349

    C (952) 454-4629

    xxxxx@comcast.net







    From: xxxxx@lists.osr.com
    [mailto:xxxxx@lists.osr.com] On Behalf Of MARTIN OBRIEN
    Sent: Tuesday, June 08, 2010 2:23 PM
    To: Kernel Debugging Interest List
    Subject: Re: [windbg] New laptop and trouble attaching to a 1394 target



    Have you tried enabling protocol debugging (CTRL+ALT+D) to see what's going
    on?





    Good afternoon,



    mm







    On Jun 8, 2010 3:15 PM, "Gary G. Little" wrote:

    On this one I am holding my breath. I recently received a new Dell Precision
    M4500 laptop, loaded, and attempted to run WinDbg for the first time. An
    attempt was made to install the driver but that attempt failed, and after a
    reboot I cannot attach to the target. Device manager says the laptop is
    using a RICOH 1394 OHCI compliant host controller. Foolishly I ran WinDbg
    un-elevated the first time, which probably why the install of the driver
    failed. I then updated the 1394 driver to the drivers in the WinDbg
    directory, but that still did not connect. Finally, I did system restore to
    a time before the first aborted run of WinDbg, then a system update followed
    by removing and installing WinDbg. All of that done I elevated WinDbg and
    let'r rip. Samething.



    "Wrote 0 of 1 bytes of the breakin packet.

    Failed to write breakin packet to target. Win32 error 0n2

    WARNING: The HOST cannot communicate with the TARGET!"



    It is well known that 1394 and WinDbg are very sensitive to each other and
    I've got a sick feeling this may be the case. Has anyone else run across
    this?



    Gary G. Little

    H (952) 223-1349

    C (952) 454-4629

    xxxxx@comcast.net




    ---
    WINDBG is sponsored by OSR

    For our schedule of WDF, WDM, debugging and other seminars visit:
    http://www.osr.com/seminars

    To unsubscribe, visit the List Server section of OSR Online at
    http://www.osronline.com/page.cfm?name=ListServer

    --- WINDBG is sponsored by OSR For our schedule of WDF, WDM, debugging and
    other seminars visit: http://www.osr.com/seminars To unsubscribe, visit the
    List Server section of OSR Online at
    http://www.osronline.com/page.cfm?name=ListServer


    ---
    WINDBG is sponsored by OSR

    For our schedule of WDF, WDM, debugging and other seminars visit:
    http://www.osr.com/seminars

    To unsubscribe, visit the List Server section of OSR Online at
    http://www.osronline.com/page.cfm?name=ListServer


    ---
    WINDBG is sponsored by OSR

    For our schedule of WDF, WDM, debugging and other seminars visit:
    http://www.osr.com/seminars

    To unsubscribe, visit the List Server section of OSR Online at
    http://www.osronline.com/page.cfm?name=ListServer


    ---
    WINDBG is sponsored by OSR

    For our schedule of WDF, WDM, debugging and other seminars visit:
    http://www.osr.com/seminars

    To unsubscribe, visit the List Server section of OSR Online at
    http://www.osronline.com/page.cfm?name=ListServer


    ---
    WINDBG is sponsored by OSR

    For our schedule of WDF, WDM, debugging and other seminars visit:
    http://www.osr.com/seminars

    To unsubscribe, visit the List Server section of OSR Online at
    http://www.osronline.com/page.cfm?name=ListServer


    ---
    WINDBG is sponsored by OSR

    For our schedule of WDF, WDM, debugging and other seminars visit:
    http://www.osr.com/seminars

    To unsubscribe, visit the List Server section of OSR Online at
    http://www.osronline.com/page.cfm?name=ListServer


    ---
    WINDBG is sponsored by OSR

    For our schedule of WDF, WDM, debugging and other seminars visit:
    http://www.osr.com/seminars

    To unsubscribe, visit the List Server section of OSR Online at
    http://www.osronline.com/page.cfm?name=ListServer


    ---
    WINDBG is sponsored by OSR

    For our schedule of WDF, WDM, debugging and other seminars visit:
    http://www.osr.com/seminars

    To unsubscribe, visit the List Server section of OSR Online at
    http://www.osronline.com/page.cfm?name=ListServer


    ---
    WINDBG is sponsored by OSR

    For our schedule of WDF, WDM, debugging and other seminars visit:
    http://www.osr.com/seminars

    To unsubscribe, visit the List Server section of OSR Online at
    http://www.osronline.com/page.cfm?name=ListServer


    ---
    WINDBG is sponsored by OSR

    For our schedule of WDF, WDM, debugging and other seminars visit:
    http://www.osr.com/seminars

    To unsubscribe, visit the List Server section of OSR Online at
    http://www.osronline.com/page.cfm?name=ListServer
Sign In or Register to comment.

Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

Upcoming OSR Seminars
Writing WDF Drivers 25 Feb 2019 OSR Seminar Space
Developing Minifilters 8 April 2019 OSR Seminar Space