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

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

RE: remote kernel debugging on windows vista home premium?

Ken_JohnsonKen_Johnson Member - All Emails Posts: 1,559
Is the serial port on the target a real onboard UART and not a USB to serial adapter (or other non-UART device)?

- S


-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of xxxxx@aol.com
Sent: Friday, June 17, 2011 8:10 PM
To: Kernel Debugging Interest List
Subject: [windbg] remote kernel debugging on windows vista home premium?

I am trying to set up remote kernel debugging, which involves Windows 2000 sp4 (host) and Vista home premium sp2 (64-bit) (target).
Target has two Pentium Dual-Core E5300 CPU's.
On the host I am using KD.exe 6.12.0002.633 x86 (the latest available 32-bit package) My host cannot connect to the target. When I press Ctrl-C it just sits there "waiting to reconnect"
I checked connectivity between two COM ports using putty.exe and it looks like two machines communicate without a problem.
I made changes to BCD using bcdedit as described in http://msdn.microsoft.com/en-us/windows/hardware/gg487520.
But if situation is reversed, kd on Vista machine (now host) connects to Win2000 (now target) without any problem.
Microsoft states:
The x64 Debugging Tools for Windows package is required only if you are debugging an application on an x64 processor.
In any other scenario, you should use the 32-bit package. For example, if performing kernel debugger debugging of an x64 target machine from an x86 host machine, you should install the 32-bit package."
Any help would be greatly appreciated!

---
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
«1

Comments

  • david__longtaildavid__longtail Member Posts: 22
    It is Native PCI express RS232 Serial adapter Card with 16550 UART chip.
  • david__longtaildavid__longtail Member Posts: 22
    BTW, I noticed that on W2000 when it is being debuggged (with debugging enabled) a COM port "disappears" from the list of devices because kernel debugger "ownes" it that point.
    On Vista, when it is being debugged (with debugging enabled) a COM port is still visible in Device Manager. Maybe it is just the way it is on vista, but I thought it may provide some extra clues...
    Just in case, here is the output of bcdedit /enum all: (I have added an entry "DebugEntry")
    Windows Boot Manager
    --------------------
    identifier {bootmgr}
    device partition=C:
    description Windows Boot Manager
    locale en-us
    inherit {globalsettings}
    default {current}
    displayorder {current}
    {c7e18f8d-97a1-11e0-a4d6-90e6ba320ad5}
    toolsdisplayorder {memdiag}
    timeout 30
    resume No
    customactions 0x1000085000001
    0x54000001
    custom:54000001 {863df33e-9817-11dc-b72e-001b24047e4e}

    Windows Boot Loader
    -------------------
    identifier {572bcd55-ffa7-11d9-aae0-0007e994107d}
    device ramdisk=[D:]\sources\boot.wim,{ad6c7bc8-fa0f-11da-8ddf-0013200354d8}
    path \windows\system32\boot\winload.exe
    description HP Recovery Manager
    osdevice ramdisk=[D:]\sources\boot.wim,{ad6c7bc8-fa0f-11da-8ddf-0013200354d8}
    systemroot \windows
    nx OptIn
    detecthal Yes
    winpe Yes

    Windows Boot Loader
    -------------------
    identifier {572bcd55-ffa7-11d9-aae2-0007e994107d}
    device ramdisk=[D:]\sources\boot.wim,{ramdiskoptions}
    path \windows\system32\boot\winload.exe
    description HP Recovery Manager
    osdevice ramdisk=[D:]\sources\boot.wim,{ramdiskoptions}
    systemroot \windows
    nx OptIn
    detecthal Yes
    winpe Yes

    Windows Boot Loader
    -------------------
    identifier {863df33e-9817-11dc-b72e-001b24047e4e}
    device ramdisk=[D:]\sources\boot.wim,{ramdiskoptions}
    path \windows\system32\boot\winload.exe
    description F11 Boot from BCD
    osdevice ramdisk=[D:]\sources\boot.wim,{ramdiskoptions}
    systemroot \windows
    nx OptIn
    detecthal Yes
    winpe Yes

    Windows Boot Loader
    -------------------
    identifier {current}
    device partition=C:
    path \Windows\system32\winload.exe
    description Microsoft Windows Vista
    locale en-us
    inherit {bootloadersettings}
    recoverysequence {572bcd55-ffa7-11d9-aae2-0007e994107d}
    recoveryenabled Yes
    osdevice partition=C:
    systemroot \Windows
    resumeobject {c5b62456-b827-11de-9bbe-90e6ba320ad5}
    nx OptIn
    debug Yes

    Windows Boot Loader
    -------------------
    identifier {c7e18f8d-97a1-11e0-a4d6-90e6ba320ad5}
    device partition=C:
    path \Windows\system32\winload.exe
    description DebugEntry
    locale en-us
    inherit {bootloadersettings}
    recoverysequence {572bcd55-ffa7-11d9-aae2-0007e994107d}
    recoveryenabled Yes
    osdevice partition=C:
    systemroot \Windows
    resumeobject {c5b62456-b827-11de-9bbe-90e6ba320ad5}
    nx OptIn
    debug Yes

    Resume from Hibernate
    ---------------------
    identifier {c5b62456-b827-11de-9bbe-90e6ba320ad5}
    device partition=C:
    path \Windows\system32\winresume.exe
    description Windows Resume Application
    locale en-US
    inherit {resumeloadersettings}
    filedevice partition=C:
    filepath \hiberfil.sys
    debugoptionenabled Yes

    Windows Memory Tester
    ---------------------
    identifier {memdiag}
    device partition=C:
    path \boot\memtest.exe
    description Windows Memory Diagnostic
    locale en-US
    inherit {globalsettings}
    badmemoryaccess Yes

    Windows Legacy OS Loader
    ------------------------
    identifier {ntldr}
    device partition=C:
    path \ntldr
    description Earlier Version of Windows

    EMS Settings
    ------------
    identifier {emssettings}
    bootems Yes

    Debugger Settings
    -----------------
    identifier {dbgsettings}
    debugtype Serial
    debugport 1
    baudrate 19200
    debugstart Active

    RAM Defects
    -----------
    identifier {badmemory}

    Global Settings
    ---------------
    identifier {globalsettings}
    inherit {dbgsettings}
    {emssettings}
    {badmemory}
    extendedinput Yes

    Boot Loader Settings
    --------------------
    identifier {bootloadersettings}
    inherit {globalsettings}

    Resume Loader Settings
    ----------------------
    identifier {resumeloadersettings}
    inherit {globalsettings}

    Device options
    --------------
    identifier {ad6c7bc8-fa0f-11da-8ddf-0013200354d8}
    description Ramdisk Device Options
    ramdisksdidevice partition=D:
    ramdisksdipath \boot\boot.sdi

    Setup Ramdisk Options
    ---------------------
    identifier {ramdiskoptions}
    description RAM Disk Settings
    ramdisksdidevice partition=D:
    ramdisksdipath \boot\boot.sdi
  • Jake_OshinsJake_Oshins Member Posts: 1,058
    PCI-attached UARTs aren't supported, only ISA- or LPC-attached UARTs.



    Jake Oshins
    Hyper-V I/O Architect
    Windows Kernel Group

    This post implies no warranties and confers no rights.

    --------------------------------------------------------------
    wrote in message news:xxxxx@windbg...

    It is Native PCI express RS232 Serial adapter Card with 16550 UART chip.
  • david__longtaildavid__longtail Member Posts: 22
    Jake, could you please be a bit more specific?
  • mmmm Member - All Emails Posts: 1,409
    Not speaking for Jakeo, Kernel debugger guy, of course, but I believe that
    he's just saying that serial ports implemented on an add in card - PCI,
    PCI-e, ISA, it doesn't matter - won't work with kernel debugging on the
    target.

    Windbg/kd only knows about the traditional BIOS serial ports - 3f8, et c. -
    and add in cards can't have those addresses.

    Good luck,

    Mm
    On Jun 19, 2011 3:25 PM, wrote:
  • OSR_Community_UserOSR_Community_User Member Posts: 110,217
    As stated previously, ISA doesn't apply any more, but just fyi I believe
    we used to use the old ISA DigiBoard Serial break-out cards with the
    kernel debugger which worked well but may also be related to the bus &
    port that debug data is output to for example, Bus 0x0 port 0x80h. I don't
    recall for sure but I believe the local serial ports (in servers for
    example that still have serial) reside on Bus 0x0. Perhaps someone else
    can clarify in more detail.

    Ron Arndt

    "Through small and simple things, are great things brought to pass"



    From: "Martin O'Brien"
    To: "Kernel Debugging Interest List"
    Date: 06/20/2011 12:25 AM
    Subject: RE:[windbg] RE: remote kernel debugging on windows vista
    home premium?
    Sent by: xxxxx@lists.osr.com



    Not speaking for Jakeo, Kernel debugger guy, of course, but I believe that
    he's just saying that serial ports implemented on an add in card - PCI,
    PCI-e, ISA, it doesn't matter - won't work with kernel debugging on the
    target.
    Windbg/kd only knows about the traditional BIOS serial ports - 3f8, et c.
    - and add in cards can't have those addresses.
    Good luck,
    Mm
    On Jun 19, 2011 3:25 PM, wrote:
    --- 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
  • david__longtaildavid__longtail Member Posts: 22
    I'd like to thank everybody, who replied to my post. Thank you very much, gentlemen!
    Now, my last attempt to make this thing work:
    Is it possible, at least in theory, to configure an add-in card to use traditional settings?
    I contacted the manufacturer of my card (StarTech) and he assured me that their cards cannot be reconfigured. I'd like second opinion.
    Or maybe somebody knows about a card, which can be reconfigured (through BIOS, programmatically, etc)
  • Paul_Sanders-1Paul_Sanders-1 Member Posts: 27
    I 'think' there are some PCMCIA cards that work, but others will know better.

    I have heard comments in the past that serial port signals exist on the motherboard, but not used. This varies from manufacturer to manufacturer. So crack the case and scan the motherboard. You might luck out.

    Paul
    ----- Original Message -----
    From: xxxxx@aol.com
    To: "Kernel Debugging Interest List" <xxxxx@lists.osr.com>
    Sent: Monday, June 20, 2011 5:01:12 PM
    Subject: RE:[windbg] RE: remote kernel debugging on windows vista home premium?

    I'd like to thank everybody, who replied to my post. Thank you very much, gentlemen!
    Now, my last attempt to make this thing work:
    Is it possible, at least in theory, to configure an add-in card to use traditional settings?
    I contacted the manufacturer of my card (StarTech) and he assured me that their cards cannot be reconfigured. I'd like second opinion.
    Or maybe somebody knows about a card, which can be reconfigured (through BIOS, programmatically, etc)


    ---
    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
  • Don_BurnDon_Burn Member - All Emails Posts: 1,649
    Actually there have been PCI, ISA and PCMCIA cards that did work, they
    typically had BIOS support on the card.


    Don Burn (MVP, Windows DKD)
    Windows Filesystem and Driver Consulting
    Website: http://www.windrvr.com
    Blog: http://msmvps.com/blogs/WinDrvr




    -----Original Message-----
    From: xxxxx@lists.osr.com
    [mailto:xxxxx@lists.osr.com] On Behalf Of Martin O'Brien
    Sent: Monday, June 20, 2011 3:25 AM
    To: Kernel Debugging Interest List
    Subject: RE:[windbg] RE: remote kernel debugging on windows vista home
    premium?

    Not speaking for Jakeo, Kernel debugger guy, of course, but I believe that
    he's just saying that serial ports implemented on an add in card - PCI,
    PCI-e, ISA, it doesn't matter - won't work with kernel debugging on the
    target.

    Windbg/kd only knows about the traditional BIOS serial ports - 3f8, et c. -
    and add in cards can't have those addresses.


    Good luck,

    Mm

    On Jun 19, 2011 3:25 PM, <xxxxx@aol.com> wrote:

    --- 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
  • david__longtaildavid__longtail Member Posts: 22
    Actually there have been PCI, ISA and PCMCIA cards that did work, they
    typically had BIOS support on the card.

    Don, can you recall manufacturers' names, model numbers?
    That would really help me.
    I found one card made by some company in Ireland, which, as they claim, could be configured to use any address or irq number, but they discontinued that one.
  • Tim_RobertsTim_Roberts Member - All Emails Posts: 12,914
    xxxxx@aol.com wrote:
    > Actually there have been PCI, ISA and PCMCIA cards that did work, they
    > typically had BIOS support on the card.
    >
    > Don, can you recall manufacturers' names, model numbers?
    > That would really help me.
    > I found one card made by some company in Ireland, which, as they claim, could be configured to use any address or irq number, but they discontinued that one.

    You would be much happier if you got a good 1394 board instead.

    --
    Tim Roberts, xxxxx@probo.com
    Providenza & Boekelheide, Inc.

    Tim Roberts, [email protected]
    Providenza & Boekelheide, Inc.

  • OSR_Community_UserOSR_Community_User Member Posts: 110,217
    Go to newegg and spend $10 on a 1394 PCI card, plug it in, and be done.

    Do you really WANT to have to wait for the debugger?

    Do you really WANT to potentially have further issues getting the debugger to recognize a plugged in serial card?

    Why?

    Just use 1394. It works, and it is about 1000 faster than serial.

    Joe.

    -----Original Message-----
    From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of xxxxx@aol.com
    Sent: Monday, June 20, 2011 2:25 PM
    To: Kernel Debugging Interest List
    Subject: RE:[windbg] RE: remote kernel debugging on windows vista home premium?

    Actually there have been PCI, ISA and PCMCIA cards that did work, they typically had BIOS support on the card.

    Don, can you recall manufacturers' names, model numbers?
    That would really help me.
    I found one card made by some company in Ireland, which, as they claim, could be configured to use any address or irq number, but they discontinued that one.

    ---
    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
  • david__longtaildavid__longtail Member Posts: 22
    Joe, my host machine is about 10 years old and I will just have troubles on the other side.
  • Jake_OshinsJake_Oshins Member Posts: 1,058
    No, it's not. If the add-in card is PCI-based, the only way you'll get
    debugging to work is if that card is 1394, not a UART.



    Jake Oshins
    Hyper-V I/O Architect
    Windows Kernel Group

    This post implies no warranties and confers no rights.

    --------------------------------------------------------------
    wrote in message news:xxxxx@windbg...

    I'd like to thank everybody, who replied to my post. Thank you very much,
    gentlemen!
    Now, my last attempt to make this thing work:
    Is it possible, at least in theory, to configure an add-in card to use
    traditional settings?
    I contacted the manufacturer of my card (StarTech) and he assured me that
    their cards cannot be reconfigured. I'd like second opinion.
    Or maybe somebody knows about a card, which can be reconfigured (through
    BIOS, programmatically, etc)
  • mmmm Member - All Emails Posts: 1,409
    My bad, all around.

    mm

    -----Original Message-----
    From: xxxxx@lists.osr.com
    [mailto:xxxxx@lists.osr.com] On Behalf Of Don Burn
    Sent: Monday, June 20, 2011 5:14 PM
    To: Kernel Debugging Interest List
    Subject: RE: [windbg] RE: remote kernel debugging on windows vista home
    premium?

    Actually there have been PCI, ISA and PCMCIA cards that did work, they
    typically had BIOS support on the card.


    Don Burn (MVP, Windows DKD)
    Windows Filesystem and Driver Consulting
    Website: http://www.windrvr.com
    Blog: http://msmvps.com/blogs/WinDrvr




    -----Original Message-----
    From: xxxxx@lists.osr.com
    [mailto:xxxxx@lists.osr.com] On Behalf Of Martin O'Brien
    Sent: Monday, June 20, 2011 3:25 AM
    To: Kernel Debugging Interest List
    Subject: RE:[windbg] RE: remote kernel debugging on windows vista home
    premium?

    Not speaking for Jakeo, Kernel debugger guy, of course, but I believe that
    he's just saying that serial ports implemented on an add in card - PCI,
    PCI-e, ISA, it doesn't matter - won't work with kernel debugging on the
    target.

    Windbg/kd only knows about the traditional BIOS serial ports - 3f8, et c. -
    and add in cards can't have those addresses.


    Good luck,

    Mm

    On Jun 19, 2011 3:25 PM, <xxxxx@aol.com> wrote:

    --- 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
    Check both your machines for 1394. If both have it, then just turn it on and try it. Make sure you use the latest released public debugger.

    If one is missing a 1394 controller, then buy 1 controller.

    If neither have 1394 (and please make ABSOLUTELY SURE they don't have it), then buy 2 cards. Plug 1 in host, and 1 in target, and get on with your work.

    The $25 it will cost you to do this, will pay for itself in a week or 2 in time not wasted - either trying to get serial to work, or in waiting for the debugger.

    I suspect you have never used 1394 debugging in your life. You don't know what you are missing.

    I'm done.

    Joe.

    -----Original Message-----
    From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of xxxxx@aol.com
    Sent: Monday, June 20, 2011 2:51 PM
    To: Kernel Debugging Interest List
    Subject: RE:[windbg] RE: remote kernel debugging on windows vista home premium?

    Joe, my host machine is about 10 years old and I will just have troubles on the other side.

    ---
    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
    Let me try to redeem myself.

    If for some reason you can't connect via a direct transport, you could setup
    a kd server on third computer that can connect via 1394 (or serial, or usb)
    to the target; your host then could connect to the kd server via tcp/ip,
    names pipes.

    http://msdn.microsoft.com/en-us/library/ff554390(v=VS.85).aspx

    It's a little wonky at times, but it's also very useful/powerful/flexibile
    in some situations.

    That being said, I concur that if it's possible, just use 1394, unless you
    can use VMWare, in which case I'd DEFINITELY use VirtualKd.


    Good luck,

    mm

    -----Original Message-----
    From: xxxxx@lists.osr.com
    [mailto:xxxxx@lists.osr.com] On Behalf Of xxxxx@aol.com
    Sent: Monday, June 20, 2011 5:51 PM
    To: Kernel Debugging Interest List
    Subject: RE:[windbg] RE: remote kernel debugging on windows vista home
    premium?

    Joe, my host machine is about 10 years old and I will just have troubles on
    the other side.

    ---
    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
  • Tim_RobertsTim_Roberts Member - All Emails Posts: 12,914
    xxxxx@aol.com wrote:
    > Joe, my host machine is about 10 years old and I will just have troubles on the other side.

    That's irrelevant. As long as the host has an OHCI 1394 port, or a free
    PCI slot, it will work. I keep a 10-year-old laptop around here for
    just those cases.

    --
    Tim Roberts, xxxxx@probo.com
    Providenza & Boekelheide, Inc.

    Tim Roberts, [email protected]
    Providenza & Boekelheide, Inc.

  • Don_BurnDon_Burn Member - All Emails Posts: 1,649
    I can't it was years ago, note as verification see
    http://www.osronline.com/showThread.cfm?link=97086 On the serial card it
    was pretty nice before 1394 showed up since it had a jumper to make
    everything 4 times faster, so instead of 115200 the actual baud rate was
    460800 note 1394 speeds but good at the time. I suspect none of the cards
    are still made, this is a lost art.


    Don Burn (MVP, Windows DKD)
    Windows Filesystem and Driver Consulting
    Website: http://www.windrvr.com
    Blog: http://msmvps.com/blogs/WinDrvr




    -----Original Message-----
    From: xxxxx@lists.osr.com
    [mailto:xxxxx@lists.osr.com] On Behalf Of xxxxx@aol.com
    Sent: Monday, June 20, 2011 5:25 PM
    To: Kernel Debugging Interest List
    Subject: RE:[windbg] RE: remote kernel debugging on windows vista home
    premium?

    Actually there have been PCI, ISA and PCMCIA cards that did work, they
    typically had BIOS support on the card.

    Don, can you recall manufacturers' names, model numbers?
    That would really help me.
    I found one card made by some company in Ireland, which, as they claim,
    could be configured to use any address or irq number, but they discontinued
    that one.

    ---
    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
  • david__longtaildavid__longtail Member Posts: 22
    "I suspect you have never used 1394 debugging in your life."
    Joe, you are absolutely right! As ashamed as I am I must admit it...
    But I am anxious to try!
    Since this thing is all Greek to me at the moment, I beg Joe to land me a hand and specify steps I need to follow.
    Literally SPECIFY step by step, as you would do for a man who has no clue.
    How do I check for 1394 controller presense, what should I see if it is there, etc.
    And possibly what cards should i buy (brand name you could recommend, etc).
    I am pretty sure I will be fine on HP pavillion s5150t, but and old guy Compaq Pressario is another story...
    I know for a fact that it has an old modem pluged in PCI slot. So if I remove the modem I should have what I need, correct? And buying 2 or even 3 cards is not a problem.
    So, Joe, I am awaiting your commands!
    Thank you in advance, Joe!
  • Tim_RobertsTim_Roberts Member - All Emails Posts: 12,914
    xxxxx@aol.com wrote:
    > "I suspect you have never used 1394 debugging in your life."
    > Joe, you are absolutely right! As ashamed as I am I must admit it...
    > But I am anxious to try!
    > Since this thing is all Greek to me at the moment, I beg Joe to land me a hand and specify steps I need to follow.
    > Literally SPECIFY step by step, as you would do for a man who has no clue.

    There are good references on the web for this, as well as in the Windbg
    help file.

    > How do I check for 1394 controller presense, what should I see if it is there, etc.

    Device Manager. Look under "IEEE 1394 Bus host controllers". If the
    category isn't present, then you don't have one already.

    > And possibly what cards should i buy (brand name you could recommend, etc).
    > I am pretty sure I will be fine on HP pavillion s5150t, but and old guy Compaq Pressario is another story...

    The s5150t does not have 1394 on the motherboard, but it has PCIExpress
    slots where you can insert one.

    > I know for a fact that it has an old modem pluged in PCI slot. So if I remove the modem I should have what I need, correct? And buying 2 or even 3 cards is not a problem.

    If you have an open PCI slot, then you should be fine. If you do get a
    pair, remember that you need one PCI and one PCIExpress -- they are very
    different.

    --
    Tim Roberts, xxxxx@probo.com
    Providenza & Boekelheide, Inc.

    Tim Roberts, [email protected]
    Providenza & Boekelheide, Inc.

  • Paul_Sanders-1Paul_Sanders-1 Member Posts: 27
    You need to read the Help file. It doesn't take that long to read the first quarter of it, which will answer all of your questions about connecting two machines for kernel debugging.


    ----- Original Message -----
    From: xxxxx@aol.com
    To: "Kernel Debugging Interest List" <xxxxx@lists.osr.com>
    Sent: Monday, June 20, 2011 7:06:29 PM
    Subject: RE:[windbg] RE: remote kernel debugging on windows vista home premium?

    "I suspect you have never used 1394 debugging in your life."
    Joe, you are absolutely right! As ashamed as I am I must admit it...
    But I am anxious to try!
    Since this thing is all Greek to me at the moment, I beg Joe to land me a hand and specify steps I need to follow.
    Literally SPECIFY step by step, as you would do for a man who has no clue.
    How do I check for 1394 controller presense, what should I see if it is there, etc.
    And possibly what cards should i buy (brand name you could recommend, etc).
    I am pretty sure I will be fine on HP pavillion s5150t, but and old guy Compaq Pressario is another story...
    I know for a fact that it has an old modem pluged in PCI slot. So if I remove the modem I should have what I need, correct? And buying 2 or even 3 cards is not a problem.
    So, Joe, I am awaiting your commands!
    Thank you in advance, Joe!

    ---
    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
  • Don_BurnDon_Burn Member - All Emails Posts: 1,649
    First get a couple of 1394 PCI cards from OSR, second take a look at the
    instructions in ]
    http://msdn.microsoft.com/en-us/windows/hardware/gg463002


    Don Burn (MVP, Windows DKD)
    Windows Filesystem and Driver Consulting
    Website: http://www.windrvr.com
    Blog: http://msmvps.com/blogs/WinDrvr




    -----Original Message-----
    From: xxxxx@lists.osr.com
    [mailto:xxxxx@lists.osr.com] On Behalf Of xxxxx@aol.com
    Sent: Monday, June 20, 2011 7:06 PM
    To: Kernel Debugging Interest List
    Subject: RE:[windbg] RE: remote kernel debugging on windows vista home
    premium?

    "I suspect you have never used 1394 debugging in your life."
    Joe, you are absolutely right! As ashamed as I am I must admit it...
    But I am anxious to try!
    Since this thing is all Greek to me at the moment, I beg Joe to land me a
    hand and specify steps I need to follow.
    Literally SPECIFY step by step, as you would do for a man who has no clue.
    How do I check for 1394 controller presense, what should I see if it is
    there, etc.
    And possibly what cards should i buy (brand name you could recommend, etc).
    I am pretty sure I will be fine on HP pavillion s5150t, but and old guy
    Compaq Pressario is another story...
    I know for a fact that it has an old modem pluged in PCI slot. So if I
    remove the modem I should have what I need, correct? And buying 2 or even 3
    cards is not a problem.
    So, Joe, I am awaiting your commands!
    Thank you in advance, Joe!

    ---
    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
  • david__longtaildavid__longtail Member Posts: 22
    "Device Manager. Look under "IEEE 1394 Bus host controllers". If the
    category isn't present, then you don't have one already."
    No, I do not see it in Device Manager". So, where do I get one? Or it comes with a card?
    Do I need 1394 controller on host and target or target only?

    Paul mentioned "Help file" : You need to read the Help file.
    Which one? Windbg?
  • mmmm Member - All Emails Posts: 1,409
    Yes, the windbg help file.

    I think Don may have already mentioned this, but you might try reading the
    'kernel_debugging_tutorial.doc' file that can be found in the root of your
    windbg installation. It details how to setup a 1394 kd session.

    You need to read this and reference the windbg docs when you are lost.



    Good luck,

    mm
    -----Original Message-----
    From: xxxxx@lists.osr.com
    [mailto:xxxxx@lists.osr.com] On Behalf Of xxxxx@aol.com
    Sent: Monday, June 20, 2011 7:31 PM
    To: Kernel Debugging Interest List
    Subject: RE:[windbg] RE: remote kernel debugging on windows vista home
    premium?

    "Device Manager. Look under "IEEE 1394 Bus host controllers". If the
    category isn't present, then you don't have one already."
    No, I do not see it in Device Manager". So, where do I get one? Or it comes
    with a card?
    Do I need 1394 controller on host and target or target only?

    Paul mentioned "Help file" : You need to read the Help file.
    Which one? Windbg?

    ---
    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
  • Tim_RobertsTim_Roberts Member - All Emails Posts: 12,914
    xxxxx@aol.com wrote:
    > "Device Manager. Look under "IEEE 1394 Bus host controllers". If the
    > category isn't present, then you don't have one already."
    > No, I do not see it in Device Manager". So, where do I get one? Or it comes with a card?
    > Do I need 1394 controller on host and target or target only?

    1394 (also called Firewire) is a bus, rather similar to USB. It should
    be clear that, for two computers to talk over a 1394 bus, you will need
    a 1394 bus controller in each computer.

    What are you hoping to debug? I'm wondering if you're really prepared
    for what you're getting into.

    --
    Tim Roberts, xxxxx@probo.com
    Providenza & Boekelheide, Inc.

    Tim Roberts, [email protected]
    Providenza & Boekelheide, Inc.

  • david__longtaildavid__longtail Member Posts: 22
    Setting up a session after I have all hardware in place is not a problem.
    But so far I used only null-modem cable that is why I am asking so many questions.
    To summarize:
    I need two 1394 PCI cards (one regular, one express), a cable, and two available PCI slots.
    Anything else?
    KD and WinDbg will be able to use the cards.
    That's should be all, correct?
  • david__longtaildavid__longtail Member Posts: 22
    I think I got it now!
    Gentlemen, thank you all for your time and input!
    Your help is really appreciated!
  • OSR_Community_UserOSR_Community_User Member Posts: 110,217
    You don't have to buy OSR's TI cards. You can, and probably should given the amount of support you are getting from the site, but ~$10 cards from www.newegg.com should work just fine as long as you use the latest debugger. Furthermore TI cards are not ideal for x64 machines with 4GB or more of RAM given that they do not support the PhysicalUpperBound register that LSI hardware (523 chips and later) supports.

    If I were you I would just get the cheapest Rosewill 1394a cards I could find on Newegg. As long as you use the latest debugger release (specified below), it should work with any OHCI 1394 card in the target machine.

    If you don't have any PCI slots in the newer of your machines, only PCI express, and the machine doesn't already have 1394, then you will need 1 PCI and 1 PCI express card. The PCI express cards cost more $, but if your machine only has PCI express slots available, then you have no choice.


    Read this:

    http://en.wikipedia.org/wiki/1394a

    Make SURE that neither of you computers has a plug that looks like the plug in the picture of the addin card.

    If either do, then you actually already have a 1394 controller, it is just disabled in the BIOS, and you need to go into the BIOS and enable it.

    (F2, or Del usually get you into the BIOS configuration.)


    DO NOT PUT A 1394 CARD IN YOUR MACHINE, IF IT ALREADY HAS A 1394 CONTROLLER. If either of your machines has a plug anywhere on it that matches the picture of the plug of the addin 1394 card on Wikipedia, then it HAS a 1394 controller, just figure out how to enable it so it shows up in Windows device manager.


    Make sure your debugger is at least 6.12.2.633. If not, then go get it from the Microsoft website.

    Read this:

    http://en.wikipedia.org/wiki/WinDbg

    The link to the Microsoft website to get the debugger is on the RHS in the box.


    In windbg, click on the help menu, then click on search.

    Type 1394 in the search box and press enter. You should get lots of hits. Read them.
    Bcdedit also gives lots of hits;

    Read them.


    To enable 1394 debugging on a vista target machine:

    Run an elevated (admin privileges) command prompt then type

    Bcdedit -dbgsettings 1394 channel:1
    Bcdedit -debug on


    Then in the host machine open an elevated command prompt, and run

    Windbg -k 1394:channel=1

    Press ctrl-alt-k twice. (should say will breakin at first symbol load)

    Then reboot the target machine.

    (shutdown -r -t 0 in the command prompt)

    You should connect at boot and the debugger will breakin.

    Press g to let the machine boot.

    Joe.

    -----Original Message-----
    From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of xxxxx@aol.com
    Sent: Monday, June 20, 2011 4:46 PM
    To: Kernel Debugging Interest List
    Subject: RE:[windbg] RE: remote kernel debugging on windows vista home premium?

    Setting up a session after I have all hardware in place is not a problem.
    But so far I used only null-modem cable that is why I am asking so many questions.
    To summarize:
    I need two 1394 PCI cards (one regular, one express), a cable, and two available PCI slots.
    Anything else?
    KD and WinDbg will be able to use the cards.
    That's should be all, correct?

    ---
    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
    One last thing.

    Make sure you actually shutdown your machines before you open them up and plug in the cards.

    You will also need a 1394 cable with which you plug the 2 cards together. Some of the Rosewill cards come with a cable.

    Joe.

    -----Original Message-----
    From: Joe Ballantyne
    Sent: Monday, June 20, 2011 5:10 PM
    To: 'Kernel Debugging Interest List'
    Subject: RE: RE:[windbg] RE: remote kernel debugging on windows vista home premium?

    You don't have to buy OSR's TI cards. You can, and probably should given the amount of support you are getting from the site, but ~$10 cards from www.newegg.com should work just fine as long as you use the latest debugger. Furthermore TI cards are not ideal for x64 machines with 4GB or more of RAM given that they do not support the PhysicalUpperBound register that LSI hardware (523 chips and later) supports.

    If I were you I would just get the cheapest Rosewill 1394a cards I could find on Newegg. As long as you use the latest debugger release (specified below), it should work with any OHCI 1394 card in the target machine.

    If you don't have any PCI slots in the newer of your machines, only PCI express, and the machine doesn't already have 1394, then you will need 1 PCI and 1 PCI express card. The PCI express cards cost more $, but if your machine only has PCI express slots available, then you have no choice.


    Read this:

    http://en.wikipedia.org/wiki/1394a

    Make SURE that neither of you computers has a plug that looks like the plug in the picture of the addin card.

    If either do, then you actually already have a 1394 controller, it is just disabled in the BIOS, and you need to go into the BIOS and enable it.

    (F2, or Del usually get you into the BIOS configuration.)


    DO NOT PUT A 1394 CARD IN YOUR MACHINE, IF IT ALREADY HAS A 1394 CONTROLLER. If either of your machines has a plug anywhere on it that matches the picture of the plug of the addin 1394 card on Wikipedia, then it HAS a 1394 controller, just figure out how to enable it so it shows up in Windows device manager.


    Make sure your debugger is at least 6.12.2.633. If not, then go get it from the Microsoft website.

    Read this:

    http://en.wikipedia.org/wiki/WinDbg

    The link to the Microsoft website to get the debugger is on the RHS in the box.


    In windbg, click on the help menu, then click on search.

    Type 1394 in the search box and press enter. You should get lots of hits. Read them.
    Bcdedit also gives lots of hits;

    Read them.


    To enable 1394 debugging on a vista target machine:

    Run an elevated (admin privileges) command prompt then type

    Bcdedit -dbgsettings 1394 channel:1
    Bcdedit -debug on


    Then in the host machine open an elevated command prompt, and run

    Windbg -k 1394:channel=1

    Press ctrl-alt-k twice. (should say will breakin at first symbol load)

    Then reboot the target machine.

    (shutdown -r -t 0 in the command prompt)

    You should connect at boot and the debugger will breakin.

    Press g to let the machine boot.

    Joe.

    -----Original Message-----
    From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of xxxxx@aol.com
    Sent: Monday, June 20, 2011 4:46 PM
    To: Kernel Debugging Interest List
    Subject: RE:[windbg] RE: remote kernel debugging on windows vista home premium?

    Setting up a session after I have all hardware in place is not a problem.
    But so far I used only null-modem cable that is why I am asking so many questions.
    To summarize:
    I need two 1394 PCI cards (one regular, one express), a cable, and two available PCI slots.
    Anything else?
    KD and WinDbg will be able to use the cards.
    That's should be all, correct?

    ---
    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