RE: windbg digest: September 19, 2005

Hello:
I am finally going to try switching from serial to 1394 for my debugging
connection. Perhaps I am the last one to try it:) Does 1394 require a
special cable like a null modem for serial debugging does? I don’t want to
damage my equipment by using the wrong cable and cannot find documentation
on this issue.
Thanks
Sanford Hayes
www.vwaresys.com

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Kernel Debugging
Interest List digest
Sent: Tuesday, September 20, 2005 1:00 AM
To: windbg digest recipients
Subject: windbg digest: September 19, 2005

WINDBG Digest for Monday, September 19, 2005.

  1. RE: Windbg not getting source from code premium site
  2. RE: Windbg not getting source from code premium site

Subject: RE: Windbg not getting source from code premium site
From: “Daniel Grund”
Date: Mon, 19 Sep 2005 10:41:43 +0200
X-Message-Number: 1

Hi Jason,
Did that, no such document found
Can you send it to me?

Daniel

>From: “Jason Shay”
>Reply-To: “Kernel Debugging Interest List”
>To: “Kernel Debugging Interest List”
>Subject: RE: [windbg] Windbg not getting source from code premium site
>Date: Thu, 8 Sep 2005 09:06:12 -0700
>
>I would think it shows the source from the first path available, which
>may still be a completely different line than you’re looking for.
>
>There is no good solution when just using a string of paths to find your
>source files. However there is a way to source-index your own PDB
>files. Essentially, this tells the PDB how to look up the exact version
>of source code from your version control system. You can get the
>srcsrv.doc file by doing a customer install of the debugger and enabling
>the SDK component.
>
>Jason
>
>-----Original Message-----
>From: xxxxx@lists.osr.com
>[mailto:xxxxx@lists.osr.com] On Behalf Of Daniel Grund
>Sent: Thursday, September 08, 2005 12:18 AM
>To: Kernel Debugging Interest List
>Subject: RE: [windbg] Windbg not getting source from code premium site
>
>HI Jason,
>
>Yes, that does it.
>As a remark, if you have multiple paths in the source paths and in there
>
>diferent versions of the same source, it will mess up. It will show the
>source from the last path available and point to a completely different
>line
>in the source.
>
>anything that can be fixed?
>
>Daniel
>
> >From: “Jason Shay”
> >Reply-To: “Kernel Debugging Interest List”
> >To: “Kernel Debugging Interest List”
> >Subject: RE: [windbg] Windbg not getting source from code premium site
> >Date: Wed, 7 Sep 2005 18:51:20 -0700
> >
> >There was a bug where the http path must be the last entry in your
> >srcpath. Can you make this change and see if it resolves your issue?
> >If so, we’ll have it fixed in the next debugger release.
> >
> >Jason
> >
> >-----Original Message-----
> >From: Daniel Grund [mailto:xxxxx@hotmail.com]
> >Sent: Saturday, August 13, 2005 4:10 AM
> >To: Jason Shay
> >Subject: RE: [windbg] Windbg not getting source from code premium site
> >
> >Hi Jay,
> >
> >I’ve got a mixed path.
> >1: kd> .srcpath
> >Source search path is:
> >https://codepremium.msdn.microsoft.com/Source/windows%20server%202003/r
>t
> >m;D:\src\SP40cSP2\SP2_Rd37540\Raidisk
> >
> >
> >When I step to the frame containing local sources, there is no problem,
> >it opens.
> >When I step into a frame containing HTTPS sources, it doesn’t show.
> >
> >It finds the math to the source but just doesn’t open the source window
> >for it.
> >DBGENG: Scan paths for partial path match:
> >DBGENG: prefix ‘d:\srvrtm\drivers\input\pnpi8042’
> >DBGENG: suffix ‘kbddep.c’
> >DBGENG: match
> >‘https://codepremium.msdn.microsoft.com/Source/windows%20server%202003/
>r
> >tm’
> >against ‘d:\srvrtm\drivers\input\pnpi8042’: 31 (match ‘’)
> >DBGENG: match ‘D:\src\SP40cSP2\SP2_Rd37540\Raidisk’ against
> >‘d:\srvrtm\drivers\input\pnpi8042’: 31 (match ‘’)
> >DBGENG: Scan paths for partial path match:
> >DBGENG: prefix ‘d:\srvrtm\drivers\input’
> >DBGENG: suffix ‘pnpi8042\kbddep.c’
> >DBGENG: match
> >‘https://codepremium.msdn.microsoft.com/Source/windows%20server%202003/
>r
> >tm’
> >against ‘d:\srvrtm\drivers\input’: 22 (match ‘’)
> >DBGENG: match ‘D:\src\SP40cSP2\SP2_Rd37540\Raidisk’ against
> >‘d:\srvrtm\drivers\input’: 22 (match ‘’)
> >DBGENG: Scan paths for partial path match:
> >DBGENG: prefix ‘d:\srvrtm\drivers’
> >DBGENG: suffix ‘input\pnpi8042\kbddep.c’
> >DBGENG: match
> >‘https://codepremium.msdn.microsoft.com/Source/windows%20server%202003/
>r
> >tm’
> >against ‘d:\srvrtm\drivers’: 16 (match ‘’)
> >DBGENG: match ‘D:\src\SP40cSP2\SP2_Rd37540\Raidisk’ against
> >‘d:\srvrtm\drivers’: 16 (match ‘’)
> >DBGENG: Scan paths for partial path match:
> >DBGENG: prefix ‘d:\srvrtm’
> >DBGENG: suffix ‘drivers\input\pnpi8042\kbddep.c’
> >DBGENG: match
> >‘https://codepremium.msdn.microsoft.com/Source/windows%20server%202003/
>r
> >tm’
> >against ‘d:\srvrtm’: 8 (match ‘’)
> >DBGENG: match ‘D:\src\SP40cSP2\SP2_Rd37540\Raidisk’ against
> >‘d:\srvrtm’: 8 (match ‘’)
> >DBGENG: Scan paths for partial path match:
> >DBGENG: prefix ‘d:’
> >DBGENG: suffix ‘srvrtm\drivers\input\pnpi8042\kbddep.c’
> >DBGENG: match
> >‘https://codepremium.msdn.microsoft.com/Source/windows%20server%202003/
>r
> >tm’
> >against ‘d:’: 1 (match ‘’)
> >DBGENG: match ‘D:\src\SP40cSP2\SP2_Rd37540\Raidisk’ against ‘d:’:
>1
> >
> >(match ‘’)
> >DBGENG: Scan all paths for:
> >DBGENG: ‘d:\srvrtm\drivers\input\pnpi8042\kbddep.c’
> >DBGENG: check
> >‘https://codepremium.msdn.microsoft.com/Source/windows%20server%202003/
>r
> >tm/d:/srvrtm/drivers/input/pnpi8042/kbddep.c’
> >DBGENG: check
> >‘D:\src\SP40cSP2\SP2_Rd37540\Raidisk\d:\srvrtm\drivers\input\pnpi8042\k
>b
> >ddep.c’
> >DBGENG: Scan all paths for:
> >DBGENG: ‘srvrtm\drivers\input\pnpi8042\kbddep.c’
> >DBGENG: check
> >‘https://codepremium.msdn.microsoft.com/Source/windows%20server%202003/
>r
> >tm/srvrtm/drivers/input/pnpi8042/kbddep.c’
> >DBGENG: check
> >‘D:\src\SP40cSP2\SP2_Rd37540\Raidisk\srvrtm\drivers\input\pnpi8042\kbdd
>e
> >p.c’
> >DBGENG: Scan all paths for:
> >DBGENG: ‘drivers\input\pnpi8042\kbddep.c’
> >DBGENG: check
> >‘https://codepremium.msdn.microsoft.com/Source/windows%20server%202003/
>r
> >tm/drivers/input/pnpi8042/kbddep.c’
> >DBGENG: check
> >‘D:\src\SP40cSP2\SP2_Rd37540\Raidisk\drivers\input\pnpi8042\kbddep.c’
> >DBGENG: Scan all paths for:
> >DBGENG: ‘input\pnpi8042\kbddep.c’
> >DBGENG: check
> >‘https://codepremium.msdn.microsoft.com/Source/windows%20server%202003/
>r
> >tm/input/pnpi8042/kbddep.c’
> >DBGENG: check
> >‘D:\src\SP40cSP2\SP2_Rd37540\Raidisk\input\pnpi8042\kbddep.c’
> >DBGENG: Scan all paths for:
> >DBGENG: ‘pnpi8042\kbddep.c’
> >DBGENG: check
> >‘https://codepremium.msdn.microsoft.com/Source/windows%20server%202003/
>r
> >tm/pnpi8042/kbddep.c’
> >DBGENG: check
> >‘D:\src\SP40cSP2\SP2_Rd37540\Raidisk\pnpi8042\kbddep.c’
> >DBGENG: Scan all paths for:
> >DBGENG: ‘kbddep.c’
> >DBGENG: check
> >‘https://codepremium.msdn.microsoft.com/Source/windows%20server%202003/
>r
> >tm/kbddep.c’
> >DBGENG: check ‘D:\src\SP40cSP2\SP2_Rd37540\Raidisk\kbddep.c’
> >DBGENG: Check plain file:
> >DBGENG: ‘d:\srvrtm\drivers\input\pnpi8042\kbddep.c’ - not found
> >
> >When I then delete the localpath from the .srcpath it opens fine
> >
> >Daniel
> >
> >
> > >From: “Jason Shay”
> > >Reply-To: “Kernel Debugging Interest List”
> > >To: “Kernel Debugging Interest List”
> > >Subject: RE: [windbg] Windbg not getting source from code premium
>site
> > >Date: Fri, 12 Aug 2005 08:50:46 -0700
> > >
> > >I’ll need more info than that to help. What exactly is your
>.srcpath?
> > >Are each element of the source path http sites? What’s the !sym
>noisy
> > >output? If that’s empty, what’s the ‘!srcnoisy 1’ output?
> > >
> > >But in general, it should work. I use it all the time…
> > >
> > >Jason
> > >
> > >-----Original Message-----
> > >From: xxxxx@lists.osr.com
> > >[mailto:xxxxx@lists.osr.com] On Behalf Of Daniel Grund
> > >Sent: Friday, August 12, 2005 6:58 AM
> > >To: Kernel Debugging Interest List
> > >Subject: RE: [windbg] Windbg not getting source from code premium
>site
> > >
> > >Thanks Jason,
> > >That helped.
> > >And now that we are speaking off this subject…
> > >
> > >Multiple source path’s seperated with ; doesn’t work as well.
> > >Also not in the new version.
> > >Something that can be fixed as well?
> > >
> > >Daniel
> > >
> > > >From: “Jason Shay”
> > > >Reply-To: “Kernel Debugging Interest List”
> > > >To: “Kernel Debugging Interest List”
> > > >Subject: RE: [windbg] Windbg not getting source from code premium
> > > >site
> > > >Date: Wed, 10 Aug 2005 20:28:09 -0700
> > > >
> > > >I was getting curious about why nobody external seems to have
>noticed
> >
> > > >this yet. We’re in the process of hotfixing the 6.5.3.7 release
>for
> > > >just this bug. The web pages are not yet updated. But since it’s
> > > >blocking you, here’s a sneak preview :slight_smile:
> > > >
> > >
> >http://msdl.microsoft.com/download/symbols/debuggers/dbg_x86_6.5.3.8.
> > > >ex
> > >e
> > >
> >
> >http://msdl.microsoft.com/download/symbols/debuggers/dbg_amd64_6.5.3.8.
> > >e
> > > >xe
> > >
> >http://msdl.microsoft.com/download/symbols/debuggers/dbg_ia64_6.5.3.8
> > > >.e
> > >x
> > > >e
> > > >
> > > >I’ll send a more official mail when the web site is updated.
> > > >
> > > >Jason
> > > >
> > > >-----Original Message-----
> > > >From: xxxxx@lists.osr.com
> > > >[mailto:xxxxx@lists.osr.com] On Behalf Of Daniel
>Grund
> > > >Sent: Wednesday, August 10, 2005 5:21 AM
> > > >To: Kernel Debugging Interest List
> > > >Subject: [windbg] Windbg not getting source from code premium site
> > > >
> > > >Hi All,
> > > >Why does Windbg 6.5.3.7 doesn’t work anymore with the code premium
> > > >site in source mode?
> > > >Is there a way to track what is going on?
> > > >
> > > >Regards,
> > > >
> > > >Daniel
> > > >
> > > >
> > > >Play online games with your friends with MSN Messenger
> > > >http://messenger.msn.nl/
> > > >
> > > >
> > > >—
> > > >You are currently subscribed to windbg as:
>xxxxx@winse.microsoft.com
> > > >To unsubscribe send a blank email to
> > > >xxxxx@lists.osr.com
> > > >
> > > >—
> > > >You are currently subscribed to windbg as: unknown lmsubst tag
> > >argument: ‘’
> > > >To unsubscribe send a blank email to
> > > >xxxxx@lists.osr.com
> > >
> > >

> > >Talk with your online friends with MSN Messenger
> > >http://messenger.msn.nl/
> > >
> > >
> > >—
> > >You are currently subscribed to windbg as: xxxxx@winse.microsoft.com
>To
> >
> > >unsubscribe send a blank email to xxxxx@lists.osr.com
> > >
> > >—
> > >You are currently subscribed to windbg as: unknown lmsubst tag
> >argument: ‘’
> > >To unsubscribe send a blank email to
>xxxxx@lists.osr.com
> >
> >
> >Play online games with your friends with MSN Messenger
> >http://messenger.msn.nl/
> >
> >
> >—
> >You are currently subscribed to windbg as: unknown lmsubst tag
>argument: ‘’
> >To unsubscribe send a blank email to xxxxx@lists.osr.com
>
>

>MSN Search, for accurate results! http://search.msn.nl
>
>
>—
>You are currently subscribed to windbg as: xxxxx@winse.microsoft.com
>To unsubscribe send a blank email to xxxxx@lists.osr.com
>
>—
>You are currently subscribed to windbg as: unknown lmsubst tag argument: ‘’
>To unsubscribe send a blank email to xxxxx@lists.osr.com


Play online games with your friends with MSN Messenger
http://messenger.msn.nl/

----------------------------------------------------------------------

Subject: RE: Windbg not getting source from code premium site
From: “Jason Shay”
Date: Mon, 19 Sep 2005 08:30:46 -0700
X-Message-Number: 2

It should exist here:
D:\Program Files\Debugging Tools for
Windows\sdk\srcsrv\srcsrv.doc

Relatively speaking. The srcsrv subdirectory has a bunch of pre-baked
scripts that you’ll need, too.

Jason

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Daniel Grund
Sent: Monday, September 19, 2005 1:42 AM
To: Kernel Debugging Interest List
Subject: RE: [windbg] Windbg not getting source from code premium site

Hi Jason,
Did that, no such document found
Can you send it to me?

Daniel

>From: “Jason Shay”
>Reply-To: “Kernel Debugging Interest List”
>To: “Kernel Debugging Interest List”
>Subject: RE: [windbg] Windbg not getting source from code premium site
>Date: Thu, 8 Sep 2005 09:06:12 -0700
>
>I would think it shows the source from the first path available, which
>may still be a completely different line than you’re looking for.
>
>There is no good solution when just using a string of paths to find
your
>source files. However there is a way to source-index your own PDB
>files. Essentially, this tells the PDB how to look up the exact
version
>of source code from your version control system. You can get the
>srcsrv.doc file by doing a customer install of the debugger and
enabling
>the SDK component.
>
>Jason
>
>-----Original Message-----
>From: xxxxx@lists.osr.com
>[mailto:xxxxx@lists.osr.com] On Behalf Of Daniel Grund
>Sent: Thursday, September 08, 2005 12:18 AM
>To: Kernel Debugging Interest List
>Subject: RE: [windbg] Windbg not getting source from code premium site
>
>HI Jason,
>
>Yes, that does it.
>As a remark, if you have multiple paths in the source paths and in
there
>
>diferent versions of the same source, it will mess up. It will show the
>source from the last path available and point to a completely different
>line
>in the source.
>
>anything that can be fixed?
>
>Daniel
>
> >From: “Jason Shay”
> >Reply-To: “Kernel Debugging Interest List”
> >To: “Kernel Debugging Interest List”
> >Subject: RE: [windbg] Windbg not getting source from code premium
site
> >Date: Wed, 7 Sep 2005 18:51:20 -0700
> >
> >There was a bug where the http path must be the last entry in your
> >srcpath. Can you make this change and see if it resolves your issue?
> >If so, we’ll have it fixed in the next debugger release.
> >
> >Jason
> >
> >-----Original Message-----
> >From: Daniel Grund [mailto:xxxxx@hotmail.com]
> >Sent: Saturday, August 13, 2005 4:10 AM
> >To: Jason Shay
> >Subject: RE: [windbg] Windbg not getting source from code premium
site
> >
> >Hi Jay,
> >
> >I’ve got a mixed path.
> >1: kd> .srcpath
> >Source search path is:
>
>https://codepremium.msdn.microsoft.com/Source/windows%20server%202003/r
>t
> >m;D:\src\SP40cSP2\SP2_Rd37540\Raidisk
> >
> >
> >When I step to the frame containing local sources, there is no
problem,
> >it opens.
> >When I step into a frame containing HTTPS sources, it doesn’t show.
> >
> >It finds the math to the source but just doesn’t open the source
window
> >for it.
> >DBGENG: Scan paths for partial path match:
> >DBGENG: prefix ‘d:\srvrtm\drivers\input\pnpi8042’
> >DBGENG: suffix ‘kbddep.c’
> >DBGENG: match
>
>‘https://codepremium.msdn.microsoft.com/Source/windows%20server%202003/
>r
> >tm’
> >against ‘d:\srvrtm\drivers\input\pnpi8042’: 31 (match ‘’)
> >DBGENG: match ‘D:\src\SP40cSP2\SP2_Rd37540\Raidisk’ against
> >‘d:\srvrtm\drivers\input\pnpi8042’: 31 (match ‘’)
> >DBGENG: Scan paths for partial path match:
> >DBGENG: prefix ‘d:\srvrtm\drivers\input’
> >DBGENG: suffix ‘pnpi8042\kbddep.c’
> >DBGENG: match
>
>‘https://codepremium.msdn.microsoft.com/Source/windows%20server%202003/
>r
> >tm’
> >against ‘d:\srvrtm\drivers\input’: 22 (match ‘’)
> >DBGENG: match ‘D:\src\SP40cSP2\SP2_Rd37540\Raidisk’ against
> >‘d:\srvrtm\drivers\input’: 22 (match ‘’)
> >DBGENG: Scan paths for partial path match:
> >DBGENG: prefix ‘d:\srvrtm\drivers’
> >DBGENG: suffix ‘input\pnpi8042\kbddep.c’
> >DBGENG: match
>
>‘https://codepremium.msdn.microsoft.com/Source/windows%20server%202003/
>r
> >tm’
> >against ‘d:\srvrtm\drivers’: 16 (match ‘’)
> >DBGENG: match ‘D:\src\SP40cSP2\SP2_Rd37540\Raidisk’ against
> >‘d:\srvrtm\drivers’: 16 (match ‘’)
> >DBGENG: Scan paths for partial path match:
> >DBGENG: prefix ‘d:\srvrtm’
> >DBGENG: suffix ‘drivers\input\pnpi8042\kbddep.c’
> >DBGENG: match
>
>‘https://codepremium.msdn.microsoft.com/Source/windows%20server%202003/
>r
> >tm’
> >against ‘d:\srvrtm’: 8 (match ‘’)
> >DBGENG: match ‘D:\src\SP40cSP2\SP2_Rd37540\Raidisk’ against
> >‘d:\srvrtm’: 8 (match ‘’)
> >DBGENG: Scan paths for partial path match:
> >DBGENG: prefix ‘d:’
> >DBGENG: suffix ‘srvrtm\drivers\input\pnpi8042\kbddep.c’
> >DBGENG: match
>
>‘https://codepremium.msdn.microsoft.com/Source/windows%20server%202003/
>r
> >tm’
> >against ‘d:’: 1 (match ‘’)
> >DBGENG: match ‘D:\src\SP40cSP2\SP2_Rd37540\Raidisk’ against
‘d:’:
>1
> >
> >(match ‘’)
> >DBGENG: Scan all paths for:
> >DBGENG: ‘d:\srvrtm\drivers\input\pnpi8042\kbddep.c’
> >DBGENG: check
>
>‘https://codepremium.msdn.microsoft.com/Source/windows%20server%202003/
>r
> >tm/d:/srvrtm/drivers/input/pnpi8042/kbddep.c’
> >DBGENG: check
>
>‘D:\src\SP40cSP2\SP2_Rd37540\Raidisk\d:\srvrtm\drivers\input\pnpi8042\k
>b
> >ddep.c’
> >DBGENG: Scan all paths for:
> >DBGENG: ‘srvrtm\drivers\input\pnpi8042\kbddep.c’
> >DBGENG: check
>
>‘https://codepremium.msdn.microsoft.com/Source/windows%20server%202003/
>r
> >tm/srvrtm/drivers/input/pnpi8042/kbddep.c’
> >DBGENG: check
>
>‘D:\src\SP40cSP2\SP2_Rd37540\Raidisk\srvrtm\drivers\input\pnpi8042\kbdd
>e
> >p.c’
> >DBGENG: Scan all paths for:
> >DBGENG: ‘drivers\input\pnpi8042\kbddep.c’
> >DBGENG: check
>
>‘https://codepremium.msdn.microsoft.com/Source/windows%20server%202003/
>r
> >tm/drivers/input/pnpi8042/kbddep.c’
> >DBGENG: check
> >‘D:\src\SP40cSP2\SP2_Rd37540\Raidisk\drivers\input\pnpi8042\kbddep.c’
> >DBGENG: Scan all paths for:
> >DBGENG: ‘input\pnpi8042\kbddep.c’
> >DBGENG: check
>
>‘https://codepremium.msdn.microsoft.com/Source/windows%20server%202003/
>r
> >tm/input/pnpi8042/kbddep.c’
> >DBGENG: check
> >‘D:\src\SP40cSP2\SP2_Rd37540\Raidisk\input\pnpi8042\kbddep.c’
> >DBGENG: Scan all paths for:
> >DBGENG: ‘pnpi8042\kbddep.c’
> >DBGENG: check
>
>‘https://codepremium.msdn.microsoft.com/Source/windows%20server%202003/
>r
> >tm/pnpi8042/kbddep.c’
> >DBGENG: check
> >‘D:\src\SP40cSP2\SP2_Rd37540\Raidisk\pnpi8042\kbddep.c’
> >DBGENG: Scan all paths for:
> >DBGENG: ‘kbddep.c’
> >DBGENG: check
>
>‘https://codepremium.msdn.microsoft.com/Source/windows%20server%202003/
>r
> >tm/kbddep.c’
> >DBGENG: check ‘D:\src\SP40cSP2\SP2_Rd37540\Raidisk\kbddep.c’
> >DBGENG: Check plain file:
> >DBGENG: ‘d:\srvrtm\drivers\input\pnpi8042\kbddep.c’ - not found
> >
> >When I then delete the localpath from the .srcpath it opens fine
> >
> >Daniel
> >
> >
> > >From: “Jason Shay”
> > >Reply-To: “Kernel Debugging Interest List”
> > >To: “Kernel Debugging Interest List”
> > >Subject: RE: [windbg] Windbg not getting source from code premium
>site
> > >Date: Fri, 12 Aug 2005 08:50:46 -0700
> > >
> > >I’ll need more info than that to help. What exactly is your
>.srcpath?
> > >Are each element of the source path http sites? What’s the !sym
>noisy
> > >output? If that’s empty, what’s the ‘!srcnoisy 1’ output?
> > >
> > >But in general, it should work. I use it all the time…
> > >
> > >Jason
> > >
> > >-----Original Message-----
> > >From: xxxxx@lists.osr.com
> > >[mailto:xxxxx@lists.osr.com] On Behalf Of Daniel
Grund
> > >Sent: Friday, August 12, 2005 6:58 AM
> > >To: Kernel Debugging Interest List
> > >Subject: RE: [windbg] Windbg not getting source from code premium
>site
> > >
> > >Thanks Jason,
> > >That helped.
> > >And now that we are speaking off this subject…
> > >
> > >Multiple source path’s seperated with ; doesn’t work as well.
> > >Also not in the new version.
> > >Something that can be fixed as well?
> > >
> > >Daniel
> > >
> > > >From: “Jason Shay”
> > > >Reply-To: “Kernel Debugging Interest List”
> > > >To: “Kernel Debugging Interest List”
> > > >Subject: RE: [windbg] Windbg not getting source from code premium
> > > >site
> > > >Date: Wed, 10 Aug 2005 20:28:09 -0700
> > > >
> > > >I was getting curious about why nobody external seems to have
>noticed
> >
> > > >this yet. We’re in the process of hotfixing the 6.5.3.7 release
>for
> > > >just this bug. The web pages are not yet updated. But since
it’s
> > > >blocking you, here’s a sneak preview :slight_smile:
> > > >
> > >
> >http://msdl.microsoft.com/download/symbols/debuggers/dbg_x86_6.5.3.8.
> > > >ex
> > >e
> > >
> >
>
>http://msdl.microsoft.com/download/symbols/debuggers/dbg_amd64_6.5.3.8.
> > >e
> > > >xe
> > >
> >http://msdl.microsoft.com/download/symbols/debuggers/dbg_ia64_6.5.3.8
> > > >.e
> > >x
> > > >e
> > > >
> > > >I’ll send a more official mail when the web site is updated.
> > > >
> > > >Jason
> > > >
> > > >-----Original Message-----
> > > >From: xxxxx@lists.osr.com
> > > >[mailto:xxxxx@lists.osr.com] On Behalf Of Daniel
>Grund
> > > >Sent: Wednesday, August 10, 2005 5:21 AM
> > > >To: Kernel Debugging Interest List
> > > >Subject: [windbg] Windbg not getting source from code premium
site
> > > >
> > > >Hi All,
> > > >Why does Windbg 6.5.3.7 doesn’t work anymore with the code
premium
> > > >site in source mode?
> > > >Is there a way to track what is going on?
> > > >
> > > >Regards,
> > > >
> > > >Daniel
> > > >
> > > >

> > > >Play online games with your friends with MSN Messenger
> > > >http://messenger.msn.nl/
> > > >
> > > >
> > > >—
> > > >You are currently subscribed to windbg as:
>xxxxx@winse.microsoft.com
> > > >To unsubscribe send a blank email to
> > > >xxxxx@lists.osr.com
> > > >
> > > >—
> > > >You are currently subscribed to windbg as: unknown lmsubst tag
> > >argument: ‘’
> > > >To unsubscribe send a blank email to
> > > >xxxxx@lists.osr.com
> > >
> > >
> > >Talk with your online friends with MSN Messenger
> > >http://messenger.msn.nl/
> > >
> > >
> > >—
> > >You are currently subscribed to windbg as:
xxxxx@winse.microsoft.com
>To
> >
> > >unsubscribe send a blank email to xxxxx@lists.osr.com
> > >
> > >—
> > >You are currently subscribed to windbg as: unknown lmsubst tag
> >argument: ‘’
> > >To unsubscribe send a blank email to
>xxxxx@lists.osr.com
> >
> >

> >Play online games with your friends with MSN Messenger
> >http://messenger.msn.nl/
> >
> >
> >—
> >You are currently subscribed to windbg as: unknown lmsubst tag
>argument: ‘’
> >To unsubscribe send a blank email to
xxxxx@lists.osr.com
>
>
>MSN Search, for accurate results! http://search.msn.nl
>
>
>—
>You are currently subscribed to windbg as: xxxxx@winse.microsoft.com
>To unsubscribe send a blank email to xxxxx@lists.osr.com
>
>—
>You are currently subscribed to windbg as: unknown lmsubst tag
argument: ‘’
>To unsubscribe send a blank email to xxxxx@lists.osr.com


Play online games with your friends with MSN Messenger=20
http://messenger.msn.nl/


You are currently subscribed to windbg as: xxxxx@winse.microsoft.com
To unsubscribe send a blank email to xxxxx@lists.osr.com



END OF DIGEST


You are currently subscribed to windbg as: xxxxx@sover.net
To unsubscribe send a blank email to xxxxx@lists.osr.com

Nope just a standard cable. Be sure to disable 1394 networking on the host
system, and the 1394 controllers driver on the test system.


Don Burn (MVP, Windows DDK)
Windows 2k/XP/2k3 Filesystem and Driver Consulting
Remove StopSpam from the email to reply

“Sanford Hayes” wrote in message news:xxxxx@windbg…
> Hello:
> I am finally going to try switching from serial to 1394 for my debugging
> connection. Perhaps I am the last one to try it:) Does 1394 require a
> special cable like a null modem for serial debugging does? I don’t want to
> damage my equipment by using the wrong cable and cannot find documentation
> on this issue.
> Thanks
> Sanford Hayes
> www.vwaresys.com
>
>
>
> -----Original Message-----
> From: xxxxx@lists.osr.com
> [mailto:xxxxx@lists.osr.com] On Behalf Of Kernel Debugging
> Interest List digest
> Sent: Tuesday, September 20, 2005 1:00 AM
> To: windbg digest recipients
> Subject: windbg digest: September 19, 2005
>
> WINDBG Digest for Monday, September 19, 2005.
>
> 1. RE: Windbg not getting source from code premium site
> 2. RE: Windbg not getting source from code premium site
>
> ----------------------------------------------------------------------
>
> Subject: RE: Windbg not getting source from code premium site
> From: “Daniel Grund”
> Date: Mon, 19 Sep 2005 10:41:43 +0200
> X-Message-Number: 1
>
> Hi Jason,
> Did that, no such document found
> Can you send it to me?
>
> Daniel
>
>>From: “Jason Shay”
>>Reply-To: “Kernel Debugging Interest List”
>>To: “Kernel Debugging Interest List”
>>Subject: RE: [windbg] Windbg not getting source from code premium site
>>Date: Thu, 8 Sep 2005 09:06:12 -0700
>>
>>I would think it shows the source from the first path available, which
>>may still be a completely different line than you’re looking for.
>>
>>There is no good solution when just using a string of paths to find your
>>source files. However there is a way to source-index your own PDB
>>files. Essentially, this tells the PDB how to look up the exact version
>>of source code from your version control system. You can get the
>>srcsrv.doc file by doing a customer install of the debugger and enabling
>>the SDK component.
>>
>>Jason
>>
>>-----Original Message-----
>>From: xxxxx@lists.osr.com
>>[mailto:xxxxx@lists.osr.com] On Behalf Of Daniel Grund
>>Sent: Thursday, September 08, 2005 12:18 AM
>>To: Kernel Debugging Interest List
>>Subject: RE: [windbg] Windbg not getting source from code premium site
>>
>>HI Jason,
>>
>>Yes, that does it.
>>As a remark, if you have multiple paths in the source paths and in there
>>
>>diferent versions of the same source, it will mess up. It will show the
>>source from the last path available and point to a completely different
>>line
>>in the source.
>>
>>anything that can be fixed?
>>
>>Daniel
>>
>> >From: “Jason Shay”
>> >Reply-To: “Kernel Debugging Interest List”
>> >To: “Kernel Debugging Interest List”
>> >Subject: RE: [windbg] Windbg not getting source from code premium site
>> >Date: Wed, 7 Sep 2005 18:51:20 -0700
>> >
>> >There was a bug where the http path must be the last entry in your
>> >srcpath. Can you make this change and see if it resolves your issue?
>> >If so, we’ll have it fixed in the next debugger release.
>> >
>> >Jason
>> >
>> >-----Original Message-----
>> >From: Daniel Grund [mailto:xxxxx@hotmail.com]
>> >Sent: Saturday, August 13, 2005 4:10 AM
>> >To: Jason Shay
>> >Subject: RE: [windbg] Windbg not getting source from code premium site
>> >
>> >Hi Jay,
>> >
>> >I’ve got a mixed path.
>> >1: kd> .srcpath
>> >Source search path is:
>> >https://codepremium.msdn.microsoft.com/Source/windows%20server%202003/r
>>t
>> >m;D:\src\SP40cSP2\SP2_Rd37540\Raidisk
>> >
>> >
>> >When I step to the frame containing local sources, there is no problem,
>> >it opens.
>> >When I step into a frame containing HTTPS sources, it doesn’t show.
>> >
>> >It finds the math to the source but just doesn’t open the source window
>> >for it.
>> >DBGENG: Scan paths for partial path match:
>> >DBGENG: prefix ‘d:\srvrtm\drivers\input\pnpi8042’
>> >DBGENG: suffix ‘kbddep.c’
>> >DBGENG: match
>> >‘https://codepremium.msdn.microsoft.com/Source/windows%20server%202003/
>>r
>> >tm’
>> >against ‘d:\srvrtm\drivers\input\pnpi8042’: 31 (match ‘’)
>> >DBGENG: match ‘D:\src\SP40cSP2\SP2_Rd37540\Raidisk’ against
>> >‘d:\srvrtm\drivers\input\pnpi8042’: 31 (match ‘’)
>> >DBGENG: Scan paths for partial path match:
>> >DBGENG: prefix ‘d:\srvrtm\drivers\input’
>> >DBGENG: suffix ‘pnpi8042\kbddep.c’
>> >DBGENG: match
>> >‘https://codepremium.msdn.microsoft.com/Source/windows%20server%202003/
>>r
>> >tm’
>> >against ‘d:\srvrtm\drivers\input’: 22 (match ‘’)
>> >DBGENG: match ‘D:\src\SP40cSP2\SP2_Rd37540\Raidisk’ against
>> >‘d:\srvrtm\drivers\input’: 22 (match ‘’)
>> >DBGENG: Scan paths for partial path match:
>> >DBGENG: prefix ‘d:\srvrtm\drivers’
>> >DBGENG: suffix ‘input\pnpi8042\kbddep.c’
>> >DBGENG: match
>> >‘https://codepremium.msdn.microsoft.com/Source/windows%20server%202003/
>>r
>> >tm’
>> >against ‘d:\srvrtm\drivers’: 16 (match ‘’)
>> >DBGENG: match ‘D:\src\SP40cSP2\SP2_Rd37540\Raidisk’ against
>> >‘d:\srvrtm\drivers’: 16 (match ‘’)
>> >DBGENG: Scan paths for partial path match:
>> >DBGENG: prefix ‘d:\srvrtm’
>> >DBGENG: suffix ‘drivers\input\pnpi8042\kbddep.c’
>> >DBGENG: match
>> >‘https://codepremium.msdn.microsoft.com/Source/windows%20server%202003/
>>r
>> >tm’
>> >against ‘d:\srvrtm’: 8 (match ‘’)
>> >DBGENG: match ‘D:\src\SP40cSP2\SP2_Rd37540\Raidisk’ against
>> >‘d:\srvrtm’: 8 (match ‘’)
>> >DBGENG: Scan paths for partial path match:
>> >DBGENG: prefix ‘d:’
>> >DBGENG: suffix ‘srvrtm\drivers\input\pnpi8042\kbddep.c’
>> >DBGENG: match
>> >‘https://codepremium.msdn.microsoft.com/Source/windows%20server%202003/
>>r
>> >tm’
>> >against ‘d:’: 1 (match ‘’)
>> >DBGENG: match ‘D:\src\SP40cSP2\SP2_Rd37540\Raidisk’ against ‘d:’:
>>1
>> >
>> >(match ‘’)
>> >DBGENG: Scan all paths for:
>> >DBGENG: ‘d:\srvrtm\drivers\input\pnpi8042\kbddep.c’
>> >DBGENG: check
>> >‘https://codepremium.msdn.microsoft.com/Source/windows%20server%202003/
>>r
>> >tm/d:/srvrtm/drivers/input/pnpi8042/kbddep.c’
>> >DBGENG: check
>> >‘D:\src\SP40cSP2\SP2_Rd37540\Raidisk\d:\srvrtm\drivers\input\pnpi8042\k
>>b
>> >ddep.c’
>> >DBGENG: Scan all paths for:
>> >DBGENG: ‘srvrtm\drivers\input\pnpi8042\kbddep.c’
>> >DBGENG: check
>> >‘https://codepremium.msdn.microsoft.com/Source/windows%20server%202003/
>>r
>> >tm/srvrtm/drivers/input/pnpi8042/kbddep.c’
>> >DBGENG: check
>> >‘D:\src\SP40cSP2\SP2_Rd37540\Raidisk\srvrtm\drivers\input\pnpi8042\kbdd
>>e
>> >p.c’
>> >DBGENG: Scan all paths for:
>> >DBGENG: ‘drivers\input\pnpi8042\kbddep.c’
>> >DBGENG: check
>> >‘https://codepremium.msdn.microsoft.com/Source/windows%20server%202003/
>>r
>> >tm/drivers/input/pnpi8042/kbddep.c’
>> >DBGENG: check
>> >‘D:\src\SP40cSP2\SP2_Rd37540\Raidisk\drivers\input\pnpi8042\kbddep.c’
>> >DBGENG: Scan all paths for:
>> >DBGENG: ‘input\pnpi8042\kbddep.c’
>> >DBGENG: check
>> >‘https://codepremium.msdn.microsoft.com/Source/windows%20server%202003/
>>r
>> >tm/input/pnpi8042/kbddep.c’
>> >DBGENG: check
>> >‘D:\src\SP40cSP2\SP2_Rd37540\Raidisk\input\pnpi8042\kbddep.c’
>> >DBGENG: Scan all paths for:
>> >DBGENG: ‘pnpi8042\kbddep.c’
>> >DBGENG: check
>> >‘https://codepremium.msdn.microsoft.com/Source/windows%20server%202003/
>>r
>> >tm/pnpi8042/kbddep.c’
>> >DBGENG: check
>> >‘D:\src\SP40cSP2\SP2_Rd37540\Raidisk\pnpi8042\kbddep.c’
>> >DBGENG: Scan all paths for:
>> >DBGENG: ‘kbddep.c’
>> >DBGENG: check
>> >‘https://codepremium.msdn.microsoft.com/Source/windows%20server%202003/
>>r
>> >tm/kbddep.c’
>> >DBGENG: check ‘D:\src\SP40cSP2\SP2_Rd37540\Raidisk\kbddep.c’
>> >DBGENG: Check plain file:
>> >DBGENG: ‘d:\srvrtm\drivers\input\pnpi8042\kbddep.c’ - not found
>> >
>> >When I then delete the localpath from the .srcpath it opens fine
>> >
>> >Daniel
>> >
>> >
>> > >From: “Jason Shay”
>> > >Reply-To: “Kernel Debugging Interest List”
>> > >To: “Kernel Debugging Interest List”
>> > >Subject: RE: [windbg] Windbg not getting source from code premium
>>site
>> > >Date: Fri, 12 Aug 2005 08:50:46 -0700
>> > >
>> > >I’ll need more info than that to help. What exactly is your
>>.srcpath?
>> > >Are each element of the source path http sites? What’s the !sym
>>noisy
>> > >output? If that’s empty, what’s the ‘!srcnoisy 1’ output?
>> > >
>> > >But in general, it should work. I use it all the time…
>> > >
>> > >Jason
>> > >
>> > >-----Original Message-----
>> > >From: xxxxx@lists.osr.com
>> > >[mailto:xxxxx@lists.osr.com] On Behalf Of Daniel Grund
>> > >Sent: Friday, August 12, 2005 6:58 AM
>> > >To: Kernel Debugging Interest List
>> > >Subject: RE: [windbg] Windbg not getting source from code premium
>>site
>> > >
>> > >Thanks Jason,
>> > >That helped.
>> > >And now that we are speaking off this subject…
>> > >
>> > >Multiple source path’s seperated with ; doesn’t work as well.
>> > >Also not in the new version.
>> > >Something that can be fixed as well?
>> > >
>> > >Daniel
>> > >
>> > > >From: “Jason Shay”
>> > > >Reply-To: “Kernel Debugging Interest List”
>> > > >To: “Kernel Debugging Interest List”
>> > > >Subject: RE: [windbg] Windbg not getting source from code premium
>> > > >site
>> > > >Date: Wed, 10 Aug 2005 20:28:09 -0700
>> > > >
>> > > >I was getting curious about why nobody external seems to have
>>noticed
>> >
>> > > >this yet. We’re in the process of hotfixing the 6.5.3.7 release
>>for
>> > > >just this bug. The web pages are not yet updated. But since it’s
>> > > >blocking you, here’s a sneak preview :slight_smile:
>> > > >
>> > >
>> >http://msdl.microsoft.com/download/symbols/debuggers/dbg_x86_6.5.3.8.
>> > > >ex
>> > >e
>> > >
>> >
>> >http://msdl.microsoft.com/download/symbols/debuggers/dbg_amd64_6.5.3.8.
>> > >e
>> > > >xe
>> > >
>> >http://msdl.microsoft.com/download/symbols/debuggers/dbg_ia64_6.5.3.8
>> > > >.e
>> > >x
>> > > >e
>> > > >
>> > > >I’ll send a more official mail when the web site is updated.
>> > > >
>> > > >Jason
>> > > >
>> > > >-----Original Message-----
>> > > >From: xxxxx@lists.osr.com
>> > > >[mailto:xxxxx@lists.osr.com] On Behalf Of Daniel
>>Grund
>> > > >Sent: Wednesday, August 10, 2005 5:21 AM
>> > > >To: Kernel Debugging Interest List
>> > > >Subject: [windbg] Windbg not getting source from code premium site
>> > > >
>> > > >Hi All,
>> > > >Why does Windbg 6.5.3.7 doesn’t work anymore with the code premium
>> > > >site in source mode?
>> > > >Is there a way to track what is going on?
>> > > >
>> > > >Regards,
>> > > >
>> > > >Daniel
>> > > >
>> > > >
>> > > >Play online games with your friends with MSN Messenger
>> > > >http://messenger.msn.nl/
>> > > >
>> > > >
>> > > >—
>> > > >You are currently subscribed to windbg as:
>>xxxxx@winse.microsoft.com
>> > > >To unsubscribe send a blank email to
>> > > >xxxxx@lists.osr.com
>> > > >
>> > > >—
>> > > >You are currently subscribed to windbg as: unknown lmsubst tag
>> > >argument: ‘’
>> > > >To unsubscribe send a blank email to
>> > > >xxxxx@lists.osr.com
>> > >
>> > >

>> > >Talk with your online friends with MSN Messenger
>> > >http://messenger.msn.nl/
>> > >
>> > >
>> > >—
>> > >You are currently subscribed to windbg as: xxxxx@winse.microsoft.com
>>To
>> >
>> > >unsubscribe send a blank email to xxxxx@lists.osr.com
>> > >
>> > >—
>> > >You are currently subscribed to windbg as: unknown lmsubst tag
>> >argument: ‘’
>> > >To unsubscribe send a blank email to
>>xxxxx@lists.osr.com
>> >
>> >
>> >Play online games with your friends with MSN Messenger
>> >http://messenger.msn.nl/
>> >
>> >
>> >—
>> >You are currently subscribed to windbg as: unknown lmsubst tag
>>argument: ‘’
>> >To unsubscribe send a blank email to xxxxx@lists.osr.com
>>
>>

>>MSN Search, for accurate results! http://search.msn.nl
>>
>>
>>—
>>You are currently subscribed to windbg as: xxxxx@winse.microsoft.com
>>To unsubscribe send a blank email to xxxxx@lists.osr.com
>>
>>—
>>You are currently subscribed to windbg as: unknown lmsubst tag argument:
>>‘’
>>To unsubscribe send a blank email to xxxxx@lists.osr.com
>
>
> Play online games with your friends with MSN Messenger
> http://messenger.msn.nl/
>
>
> ----------------------------------------------------------------------
>
> Subject: RE: Windbg not getting source from code premium site
> From: “Jason Shay”
> Date: Mon, 19 Sep 2005 08:30:46 -0700
> X-Message-Number: 2
>
> It should exist here:
> D:\Program Files\Debugging Tools for
> Windows\sdk\srcsrv\srcsrv.doc
>
> Relatively speaking. The srcsrv subdirectory has a bunch of pre-baked
> scripts that you’ll need, too.
>
> Jason
>
> -----Original Message-----
> From: xxxxx@lists.osr.com
> [mailto:xxxxx@lists.osr.com] On Behalf Of Daniel Grund
> Sent: Monday, September 19, 2005 1:42 AM
> To: Kernel Debugging Interest List
> Subject: RE: [windbg] Windbg not getting source from code premium site
>
> Hi Jason,
> Did that, no such document found
> Can you send it to me?
>
> Daniel
>
>>From: “Jason Shay”
>>Reply-To: “Kernel Debugging Interest List”
>>To: “Kernel Debugging Interest List”
>>Subject: RE: [windbg] Windbg not getting source from code premium site
>>Date: Thu, 8 Sep 2005 09:06:12 -0700
>>
>>I would think it shows the source from the first path available, which
>>may still be a completely different line than you’re looking for.
>>
>>There is no good solution when just using a string of paths to find
> your
>>source files. However there is a way to source-index your own PDB
>>files. Essentially, this tells the PDB how to look up the exact
> version
>>of source code from your version control system. You can get the
>>srcsrv.doc file by doing a customer install of the debugger and
> enabling
>>the SDK component.
>>
>>Jason
>>
>>-----Original Message-----
>>From: xxxxx@lists.osr.com
>>[mailto:xxxxx@lists.osr.com] On Behalf Of Daniel Grund
>>Sent: Thursday, September 08, 2005 12:18 AM
>>To: Kernel Debugging Interest List
>>Subject: RE: [windbg] Windbg not getting source from code premium site
>>
>>HI Jason,
>>
>>Yes, that does it.
>>As a remark, if you have multiple paths in the source paths and in
> there
>>
>>diferent versions of the same source, it will mess up. It will show the
>>source from the last path available and point to a completely different
>>line
>>in the source.
>>
>>anything that can be fixed?
>>
>>Daniel
>>
>> >From: “Jason Shay”
>> >Reply-To: “Kernel Debugging Interest List”
>> >To: “Kernel Debugging Interest List”
>> >Subject: RE: [windbg] Windbg not getting source from code premium
> site
>> >Date: Wed, 7 Sep 2005 18:51:20 -0700
>> >
>> >There was a bug where the http path must be the last entry in your
>> >srcpath. Can you make this change and see if it resolves your issue?
>> >If so, we’ll have it fixed in the next debugger release.
>> >
>> >Jason
>> >
>> >-----Original Message-----
>> >From: Daniel Grund [mailto:xxxxx@hotmail.com]
>> >Sent: Saturday, August 13, 2005 4:10 AM
>> >To: Jason Shay
>> >Subject: RE: [windbg] Windbg not getting source from code premium
> site
>> >
>> >Hi Jay,
>> >
>> >I’ve got a mixed path.
>> >1: kd> .srcpath
>> >Source search path is:
>>
>>https://codepremium.msdn.microsoft.com/Source/windows%20server%202003/r
>>t
>> >m;D:\src\SP40cSP2\SP2_Rd37540\Raidisk
>> >
>> >
>> >When I step to the frame containing local sources, there is no
> problem,
>> >it opens.
>> >When I step into a frame containing HTTPS sources, it doesn’t show.
>> >
>> >It finds the math to the source but just doesn’t open the source
> window
>> >for it.
>> >DBGENG: Scan paths for partial path match:
>> >DBGENG: prefix ‘d:\srvrtm\drivers\input\pnpi8042’
>> >DBGENG: suffix ‘kbddep.c’
>> >DBGENG: match
>>
>>‘https://codepremium.msdn.microsoft.com/Source/windows%20server%202003/
>>r
>> >tm’
>> >against ‘d:\srvrtm\drivers\input\pnpi8042’: 31 (match ‘’)
>> >DBGENG: match ‘D:\src\SP40cSP2\SP2_Rd37540\Raidisk’ against
>> >‘d:\srvrtm\drivers\input\pnpi8042’: 31 (match ‘’)
>> >DBGENG: Scan paths for partial path match:
>> >DBGENG: prefix ‘d:\srvrtm\drivers\input’
>> >DBGENG: suffix ‘pnpi8042\kbddep.c’
>> >DBGENG: match
>>
>>‘https://codepremium.msdn.microsoft.com/Source/windows%20server%202003/
>>r
>> >tm’
>> >against ‘d:\srvrtm\drivers\input’: 22 (match ‘’)
>> >DBGENG: match ‘D:\src\SP40cSP2\SP2_Rd37540\Raidisk’ against
>> >‘d:\srvrtm\drivers\input’: 22 (match ‘’)
>> >DBGENG: Scan paths for partial path match:
>> >DBGENG: prefix ‘d:\srvrtm\drivers’
>> >DBGENG: suffix ‘input\pnpi8042\kbddep.c’
>> >DBGENG: match
>>
>>‘https://codepremium.msdn.microsoft.com/Source/windows%20server%202003/
>>r
>> >tm’
>> >against ‘d:\srvrtm\drivers’: 16 (match ‘’)
>> >DBGENG: match ‘D:\src\SP40cSP2\SP2_Rd37540\Raidisk’ against
>> >‘d:\srvrtm\drivers’: 16 (match ‘’)
>> >DBGENG: Scan paths for partial path match:
>> >DBGENG: prefix ‘d:\srvrtm’
>> >DBGENG: suffix ‘drivers\input\pnpi8042\kbddep.c’
>> >DBGENG: match
>>
>>‘https://codepremium.msdn.microsoft.com/Source/windows%20server%202003/
>>r
>> >tm’
>> >against ‘d:\srvrtm’: 8 (match ‘’)
>> >DBGENG: match ‘D:\src\SP40cSP2\SP2_Rd37540\Raidisk’ against
>> >‘d:\srvrtm’: 8 (match ‘’)
>> >DBGENG: Scan paths for partial path match:
>> >DBGENG: prefix ‘d:’
>> >DBGENG: suffix ‘srvrtm\drivers\input\pnpi8042\kbddep.c’
>> >DBGENG: match
>>
>>‘https://codepremium.msdn.microsoft.com/Source/windows%20server%202003/
>>r
>> >tm’
>> >against ‘d:’: 1 (match ‘’)
>> >DBGENG: match ‘D:\src\SP40cSP2\SP2_Rd37540\Raidisk’ against
> ‘d:’:
>>1
>> >
>> >(match ‘’)
>> >DBGENG: Scan all paths for:
>> >DBGENG: ‘d:\srvrtm\drivers\input\pnpi8042\kbddep.c’
>> >DBGENG: check
>>
>>‘https://codepremium.msdn.microsoft.com/Source/windows%20server%202003/
>>r
>> >tm/d:/srvrtm/drivers/input/pnpi8042/kbddep.c’
>> >DBGENG: check
>>
>>‘D:\src\SP40cSP2\SP2_Rd37540\Raidisk\d:\srvrtm\drivers\input\pnpi8042\k
>>b
>> >ddep.c’
>> >DBGENG: Scan all paths for:
>> >DBGENG: ‘srvrtm\drivers\input\pnpi8042\kbddep.c’
>> >DBGENG: check
>>
>>‘https://codepremium.msdn.microsoft.com/Source/windows%20server%202003/
>>r
>> >tm/srvrtm/drivers/input/pnpi8042/kbddep.c’
>> >DBGENG: check
>>
>>‘D:\src\SP40cSP2\SP2_Rd37540\Raidisk\srvrtm\drivers\input\pnpi8042\kbdd
>>e
>> >p.c’
>> >DBGENG: Scan all paths for:
>> >DBGENG: ‘drivers\input\pnpi8042\kbddep.c’
>> >DBGENG: check
>>
>>‘https://codepremium.msdn.microsoft.com/Source/windows%20server%202003/
>>r
>> >tm/drivers/input/pnpi8042/kbddep.c’
>> >DBGENG: check
>> >‘D:\src\SP40cSP2\SP2_Rd37540\Raidisk\drivers\input\pnpi8042\kbddep.c’
>> >DBGENG: Scan all paths for:
>> >DBGENG: ‘input\pnpi8042\kbddep.c’
>> >DBGENG: check
>>
>>‘https://codepremium.msdn.microsoft.com/Source/windows%20server%202003/
>>r
>> >tm/input/pnpi8042/kbddep.c’
>> >DBGENG: check
>> >‘D:\src\SP40cSP2\SP2_Rd37540\Raidisk\input\pnpi8042\kbddep.c’
>> >DBGENG: Scan all paths for:
>> >DBGENG: ‘pnpi8042\kbddep.c’
>> >DBGENG: check
>>
>>‘https://codepremium.msdn.microsoft.com/Source/windows%20server%202003/
>>r
>> >tm/pnpi8042/kbddep.c’
>> >DBGENG: check
>> >‘D:\src\SP40cSP2\SP2_Rd37540\Raidisk\pnpi8042\kbddep.c’
>> >DBGENG: Scan all paths for:
>> >DBGENG: ‘kbddep.c’
>> >DBGENG: check
>>
>>‘https://codepremium.msdn.microsoft.com/Source/windows%20server%202003/
>>r
>> >tm/kbddep.c’
>> >DBGENG: check ‘D:\src\SP40cSP2\SP2_Rd37540\Raidisk\kbddep.c’
>> >DBGENG: Check plain file:
>> >DBGENG: ‘d:\srvrtm\drivers\input\pnpi8042\kbddep.c’ - not found
>> >
>> >When I then delete the localpath from the .srcpath it opens fine
>> >
>> >Daniel
>> >
>> >
>> > >From: “Jason Shay”
>> > >Reply-To: “Kernel Debugging Interest List”
>> > >To: “Kernel Debugging Interest List”
>> > >Subject: RE: [windbg] Windbg not getting source from code premium
>>site
>> > >Date: Fri, 12 Aug 2005 08:50:46 -0700
>> > >
>> > >I’ll need more info than that to help. What exactly is your
>>.srcpath?
>> > >Are each element of the source path http sites? What’s the !sym
>>noisy
>> > >output? If that’s empty, what’s the ‘!srcnoisy 1’ output?
>> > >
>> > >But in general, it should work. I use it all the time…
>> > >
>> > >Jason
>> > >
>> > >-----Original Message-----
>> > >From: xxxxx@lists.osr.com
>> > >[mailto:xxxxx@lists.osr.com] On Behalf Of Daniel
> Grund
>> > >Sent: Friday, August 12, 2005 6:58 AM
>> > >To: Kernel Debugging Interest List
>> > >Subject: RE: [windbg] Windbg not getting source from code premium
>>site
>> > >
>> > >Thanks Jason,
>> > >That helped.
>> > >And now that we are speaking off this subject…
>> > >
>> > >Multiple source path’s seperated with ; doesn’t work as well.
>> > >Also not in the new version.
>> > >Something that can be fixed as well?
>> > >
>> > >Daniel
>> > >
>> > > >From: “Jason Shay”
>> > > >Reply-To: “Kernel Debugging Interest List”
>> > > >To: “Kernel Debugging Interest List”
>> > > >Subject: RE: [windbg] Windbg not getting source from code premium
>> > > >site
>> > > >Date: Wed, 10 Aug 2005 20:28:09 -0700
>> > > >
>> > > >I was getting curious about why nobody external seems to have
>>noticed
>> >
>> > > >this yet. We’re in the process of hotfixing the 6.5.3.7 release
>>for
>> > > >just this bug. The web pages are not yet updated. But since
> it’s
>> > > >blocking you, here’s a sneak preview :slight_smile:
>> > > >
>> > >
>> >http://msdl.microsoft.com/download/symbols/debuggers/dbg_x86_6.5.3.8.
>> > > >ex
>> > >e
>> > >
>> >
>>
>>http://msdl.microsoft.com/download/symbols/debuggers/dbg_amd64_6.5.3.8.
>> > >e
>> > > >xe
>> > >
>> >http://msdl.microsoft.com/download/symbols/debuggers/dbg_ia64_6.5.3.8
>> > > >.e
>> > >x
>> > > >e
>> > > >
>> > > >I’ll send a more official mail when the web site is updated.
>> > > >
>> > > >Jason
>> > > >
>> > > >-----Original Message-----
>> > > >From: xxxxx@lists.osr.com
>> > > >[mailto:xxxxx@lists.osr.com] On Behalf Of Daniel
>>Grund
>> > > >Sent: Wednesday, August 10, 2005 5:21 AM
>> > > >To: Kernel Debugging Interest List
>> > > >Subject: [windbg] Windbg not getting source from code premium
> site
>> > > >
>> > > >Hi All,
>> > > >Why does Windbg 6.5.3.7 doesn’t work anymore with the code
> premium
>> > > >site in source mode?
>> > > >Is there a way to track what is going on?
>> > > >
>> > > >Regards,
>> > > >
>> > > >Daniel
>> > > >
>> > > >

>> > > >Play online games with your friends with MSN Messenger
>> > > >http://messenger.msn.nl/
>> > > >
>> > > >
>> > > >—
>> > > >You are currently subscribed to windbg as:
>>xxxxx@winse.microsoft.com
>> > > >To unsubscribe send a blank email to
>> > > >xxxxx@lists.osr.com
>> > > >
>> > > >—
>> > > >You are currently subscribed to windbg as: unknown lmsubst tag
>> > >argument: ‘’
>> > > >To unsubscribe send a blank email to
>> > > >xxxxx@lists.osr.com
>> > >
>> > >
>> > >Talk with your online friends with MSN Messenger
>> > >http://messenger.msn.nl/
>> > >
>> > >
>> > >—
>> > >You are currently subscribed to windbg as:
> xxxxx@winse.microsoft.com
>>To
>> >
>> > >unsubscribe send a blank email to xxxxx@lists.osr.com
>> > >
>> > >—
>> > >You are currently subscribed to windbg as: unknown lmsubst tag
>> >argument: ‘’
>> > >To unsubscribe send a blank email to
>>xxxxx@lists.osr.com
>> >
>> >

>> >Play online games with your friends with MSN Messenger
>> >http://messenger.msn.nl/
>> >
>> >
>> >—
>> >You are currently subscribed to windbg as: unknown lmsubst tag
>>argument: ‘’
>> >To unsubscribe send a blank email to
> xxxxx@lists.osr.com
>>
>>
>>MSN Search, for accurate results! http://search.msn.nl
>>
>>
>>—
>>You are currently subscribed to windbg as: xxxxx@winse.microsoft.com
>>To unsubscribe send a blank email to xxxxx@lists.osr.com
>>
>>—
>>You are currently subscribed to windbg as: unknown lmsubst tag
> argument: ‘’
>>To unsubscribe send a blank email to xxxxx@lists.osr.com
>
>

> Play online games with your friends with MSN Messenger=20
> http://messenger.msn.nl/
>
>
> —
> You are currently subscribed to windbg as: xxxxx@winse.microsoft.com
> To unsubscribe send a blank email to xxxxx@lists.osr.com
>
>
>
> —
>
> END OF DIGEST
>
> —
> You are currently subscribed to windbg as: xxxxx@sover.net
> To unsubscribe send a blank email to xxxxx@lists.osr.com
>
>

Note that disabling the 1394 controller on the target system should not
be done on xpsp2, Server 2003 SP1, or Vista. The controller should be
yellowed-out in device manager for you automatically.

Jason

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Don Burn
Sent: Tuesday, September 20, 2005 8:36 AM
To: Kernel Debugging Interest List
Subject: Re:[windbg] windbg digest: September 19, 2005

Nope just a standard cable. Be sure to disable 1394 networking on the
host
system, and the 1394 controllers driver on the test system.


Don Burn (MVP, Windows DDK)
Windows 2k/XP/2k3 Filesystem and Driver Consulting
Remove StopSpam from the email to reply

“Sanford Hayes” wrote in message news:xxxxx@windbg…
> Hello:
> I am finally going to try switching from serial to 1394 for my
debugging
> connection. Perhaps I am the last one to try it:) Does 1394 require a
> special cable like a null modem for serial debugging does? I don’t
want to
> damage my equipment by using the wrong cable and cannot find
documentation
> on this issue.
> Thanks
> Sanford Hayes
> www.vwaresys.com
>
>
>
> -----Original Message-----
> From: xxxxx@lists.osr.com
> [mailto:xxxxx@lists.osr.com] On Behalf Of Kernel
Debugging
> Interest List digest
> Sent: Tuesday, September 20, 2005 1:00 AM
> To: windbg digest recipients
> Subject: windbg digest: September 19, 2005
>
> WINDBG Digest for Monday, September 19, 2005.
>
> 1. RE: Windbg not getting source from code premium site
> 2. RE: Windbg not getting source from code premium site
>
> ----------------------------------------------------------------------
>
> Subject: RE: Windbg not getting source from code premium site
> From: “Daniel Grund”
> Date: Mon, 19 Sep 2005 10:41:43 +0200
> X-Message-Number: 1
>
> Hi Jason,
> Did that, no such document found
> Can you send it to me?
>
> Daniel
>
>>From: “Jason Shay”
>>Reply-To: “Kernel Debugging Interest List”
>>To: “Kernel Debugging Interest List”
>>Subject: RE: [windbg] Windbg not getting source from code premium site
>>Date: Thu, 8 Sep 2005 09:06:12 -0700
>>
>>I would think it shows the source from the first path available, which
>>may still be a completely different line than you’re looking for.
>>
>>There is no good solution when just using a string of paths to find
your
>>source files. However there is a way to source-index your own PDB
>>files. Essentially, this tells the PDB how to look up the exact
version
>>of source code from your version control system. You can get the
>>srcsrv.doc file by doing a customer install of the debugger and
enabling
>>the SDK component.
>>
>>Jason
>>
>>-----Original Message-----
>>From: xxxxx@lists.osr.com
>>[mailto:xxxxx@lists.osr.com] On Behalf Of Daniel Grund
>>Sent: Thursday, September 08, 2005 12:18 AM
>>To: Kernel Debugging Interest List
>>Subject: RE: [windbg] Windbg not getting source from code premium site
>>
>>HI Jason,
>>
>>Yes, that does it.
>>As a remark, if you have multiple paths in the source paths and in
there
>>
>>diferent versions of the same source, it will mess up. It will show
the
>>source from the last path available and point to a completely
different
>>line
>>in the source.
>>
>>anything that can be fixed?
>>
>>Daniel
>>
>> >From: “Jason Shay”
>> >Reply-To: “Kernel Debugging Interest List”
>> >To: “Kernel Debugging Interest List”
>> >Subject: RE: [windbg] Windbg not getting source from code premium
site
>> >Date: Wed, 7 Sep 2005 18:51:20 -0700
>> >
>> >There was a bug where the http path must be the last entry in your
>> >srcpath. Can you make this change and see if it resolves your
issue?
>> >If so, we’ll have it fixed in the next debugger release.
>> >
>> >Jason
>> >
>> >-----Original Message-----
>> >From: Daniel Grund [mailto:xxxxx@hotmail.com]
>> >Sent: Saturday, August 13, 2005 4:10 AM
>> >To: Jason Shay
>> >Subject: RE: [windbg] Windbg not getting source from code premium
site
>> >
>> >Hi Jay,
>> >
>> >I’ve got a mixed path.
>> >1: kd> .srcpath
>> >Source search path is:
>>
>https://codepremium.msdn.microsoft.com/Source/windows%20server%202003/r
>>t
>> >m;D:\src\SP40cSP2\SP2_Rd37540\Raidisk
>> >
>> >
>> >When I step to the frame containing local sources, there is no
problem,
>> >it opens.
>> >When I step into a frame containing HTTPS sources, it doesn’t show.
>> >
>> >It finds the math to the source but just doesn’t open the source
window
>> >for it.
>> >DBGENG: Scan paths for partial path match:
>> >DBGENG: prefix ‘d:\srvrtm\drivers\input\pnpi8042’
>> >DBGENG: suffix ‘kbddep.c’
>> >DBGENG: match
>>
>‘https://codepremium.msdn.microsoft.com/Source/windows%20server%202003/
>>r
>> >tm’
>> >against ‘d:\srvrtm\drivers\input\pnpi8042’: 31 (match ‘’)
>> >DBGENG: match ‘D:\src\SP40cSP2\SP2_Rd37540\Raidisk’ against
>> >‘d:\srvrtm\drivers\input\pnpi8042’: 31 (match ‘’)
>> >DBGENG: Scan paths for partial path match:
>> >DBGENG: prefix ‘d:\srvrtm\drivers\input’
>> >DBGENG: suffix ‘pnpi8042\kbddep.c’
>> >DBGENG: match
>>
>‘https://codepremium.msdn.microsoft.com/Source/windows%20server%202003/
>>r
>> >tm’
>> >against ‘d:\srvrtm\drivers\input’: 22 (match ‘’)
>> >DBGENG: match ‘D:\src\SP40cSP2\SP2_Rd37540\Raidisk’ against
>> >‘d:\srvrtm\drivers\input’: 22 (match ‘’)
>> >DBGENG: Scan paths for partial path match:
>> >DBGENG: prefix ‘d:\srvrtm\drivers’
>> >DBGENG: suffix ‘input\pnpi8042\kbddep.c’
>> >DBGENG: match
>>
>‘https://codepremium.msdn.microsoft.com/Source/windows%20server%202003/
>>r
>> >tm’
>> >against ‘d:\srvrtm\drivers’: 16 (match ‘’)
>> >DBGENG: match ‘D:\src\SP40cSP2\SP2_Rd37540\Raidisk’ against
>> >‘d:\srvrtm\drivers’: 16 (match ‘’)
>> >DBGENG: Scan paths for partial path match:
>> >DBGENG: prefix ‘d:\srvrtm’
>> >DBGENG: suffix ‘drivers\input\pnpi8042\kbddep.c’
>> >DBGENG: match
>>
>‘https://codepremium.msdn.microsoft.com/Source/windows%20server%202003/
>>r
>> >tm’
>> >against ‘d:\srvrtm’: 8 (match ‘’)
>> >DBGENG: match ‘D:\src\SP40cSP2\SP2_Rd37540\Raidisk’ against
>> >‘d:\srvrtm’: 8 (match ‘’)
>> >DBGENG: Scan paths for partial path match:
>> >DBGENG: prefix ‘d:’
>> >DBGENG: suffix ‘srvrtm\drivers\input\pnpi8042\kbddep.c’
>> >DBGENG: match
>>
>‘https://codepremium.msdn.microsoft.com/Source/windows%20server%202003/
>>r
>> >tm’
>> >against ‘d:’: 1 (match ‘’)
>> >DBGENG: match ‘D:\src\SP40cSP2\SP2_Rd37540\Raidisk’ against
‘d:’:
>>1
>> >
>> >(match ‘’)
>> >DBGENG: Scan all paths for:
>> >DBGENG: ‘d:\srvrtm\drivers\input\pnpi8042\kbddep.c’
>> >DBGENG: check
>>
>‘https://codepremium.msdn.microsoft.com/Source/windows%20server%202003/
>>r
>> >tm/d:/srvrtm/drivers/input/pnpi8042/kbddep.c’
>> >DBGENG: check
>>
>‘D:\src\SP40cSP2\SP2_Rd37540\Raidisk\d:\srvrtm\drivers\input\pnpi8042\k
>>b
>> >ddep.c’
>> >DBGENG: Scan all paths for:
>> >DBGENG: ‘srvrtm\drivers\input\pnpi8042\kbddep.c’
>> >DBGENG: check
>>
>‘https://codepremium.msdn.microsoft.com/Source/windows%20server%202003/
>>r
>> >tm/srvrtm/drivers/input/pnpi8042/kbddep.c’
>> >DBGENG: check
>>
>‘D:\src\SP40cSP2\SP2_Rd37540\Raidisk\srvrtm\drivers\input\pnpi8042\kbdd
>>e
>> >p.c’
>> >DBGENG: Scan all paths for:
>> >DBGENG: ‘drivers\input\pnpi8042\kbddep.c’
>> >DBGENG: check
>>
>‘https://codepremium.msdn.microsoft.com/Source/windows%20server%202003/
>>r
>> >tm/drivers/input/pnpi8042/kbddep.c’
>> >DBGENG: check
>>
>‘D:\src\SP40cSP2\SP2_Rd37540\Raidisk\drivers\input\pnpi8042\kbddep.c’
>> >DBGENG: Scan all paths for:
>> >DBGENG: ‘input\pnpi8042\kbddep.c’
>> >DBGENG: check
>>
>‘https://codepremium.msdn.microsoft.com/Source/windows%20server%202003/
>>r
>> >tm/input/pnpi8042/kbddep.c’
>> >DBGENG: check
>> >‘D:\src\SP40cSP2\SP2_Rd37540\Raidisk\input\pnpi8042\kbddep.c’
>> >DBGENG: Scan all paths for:
>> >DBGENG: ‘pnpi8042\kbddep.c’
>> >DBGENG: check
>>
>‘https://codepremium.msdn.microsoft.com/Source/windows%20server%202003/
>>r
>> >tm/pnpi8042/kbddep.c’
>> >DBGENG: check
>> >‘D:\src\SP40cSP2\SP2_Rd37540\Raidisk\pnpi8042\kbddep.c’
>> >DBGENG: Scan all paths for:
>> >DBGENG: ‘kbddep.c’
>> >DBGENG: check
>>
>‘https://codepremium.msdn.microsoft.com/Source/windows%20server%202003/
>>r
>> >tm/kbddep.c’
>> >DBGENG: check ‘D:\src\SP40cSP2\SP2_Rd37540\Raidisk\kbddep.c’
>> >DBGENG: Check plain file:
>> >DBGENG: ‘d:\srvrtm\drivers\input\pnpi8042\kbddep.c’ - not found
>> >
>> >When I then delete the localpath from the .srcpath it opens fine
>> >
>> >Daniel
>> >
>> >
>> > >From: “Jason Shay”
>> > >Reply-To: “Kernel Debugging Interest List”
>> > >To: “Kernel Debugging Interest List”
>> > >Subject: RE: [windbg] Windbg not getting source from code premium
>>site
>> > >Date: Fri, 12 Aug 2005 08:50:46 -0700
>> > >
>> > >I’ll need more info than that to help. What exactly is your
>>.srcpath?
>> > >Are each element of the source path http sites? What’s the !sym
>>noisy
>> > >output? If that’s empty, what’s the ‘!srcnoisy 1’ output?
>> > >
>> > >But in general, it should work. I use it all the time…
>> > >
>> > >Jason
>> > >
>> > >-----Original Message-----
>> > >From: xxxxx@lists.osr.com
>> > >[mailto:xxxxx@lists.osr.com] On Behalf Of Daniel
Grund
>> > >Sent: Friday, August 12, 2005 6:58 AM
>> > >To: Kernel Debugging Interest List
>> > >Subject: RE: [windbg] Windbg not getting source from code premium
>>site
>> > >
>> > >Thanks Jason,
>> > >That helped.
>> > >And now that we are speaking off this subject…
>> > >
>> > >Multiple source path’s seperated with ; doesn’t work as well.
>> > >Also not in the new version.
>> > >Something that can be fixed as well?
>> > >
>> > >Daniel
>> > >
>> > > >From: “Jason Shay”
>> > > >Reply-To: “Kernel Debugging Interest List”

>> > > >To: “Kernel Debugging Interest List”
>> > > >Subject: RE: [windbg] Windbg not getting source from code
premium
>> > > >site
>> > > >Date: Wed, 10 Aug 2005 20:28:09 -0700
>> > > >
>> > > >I was getting curious about why nobody external seems to have
>>noticed
>> >
>> > > >this yet. We’re in the process of hotfixing the 6.5.3.7 release
>>for
>> > > >just this bug. The web pages are not yet updated. But since
it’s
>> > > >blocking you, here’s a sneak preview :slight_smile:
>> > > >
>> > >
>>
>http://msdl.microsoft.com/download/symbols/debuggers/dbg_x86_6.5.3.8.
>> > > >ex
>> > >e
>> > >
>> >
>>
>http://msdl.microsoft.com/download/symbols/debuggers/dbg_amd64_6.5.3.8.
>> > >e
>> > > >xe
>> > >
>>
>http://msdl.microsoft.com/download/symbols/debuggers/dbg_ia64_6.5.3.8
>> > > >.e
>> > >x
>> > > >e
>> > > >
>> > > >I’ll send a more official mail when the web site is updated.
>> > > >
>> > > >Jason
>> > > >
>> > > >-----Original Message-----
>> > > >From: xxxxx@lists.osr.com
>> > > >[mailto:xxxxx@lists.osr.com] On Behalf Of Daniel
>>Grund
>> > > >Sent: Wednesday, August 10, 2005 5:21 AM
>> > > >To: Kernel Debugging Interest List
>> > > >Subject: [windbg] Windbg not getting source from code premium
site
>> > > >
>> > > >Hi All,
>> > > >Why does Windbg 6.5.3.7 doesn’t work anymore with the code
premium
>> > > >site in source mode?
>> > > >Is there a way to track what is going on?
>> > > >
>> > > >Regards,
>> > > >
>> > > >Daniel
>> > > >
>> > >
>
>> > > >Play online games with your friends with MSN Messenger
>> > > >http://messenger.msn.nl/
>> > > >
>> > > >
>> > > >—
>> > > >You are currently subscribed to windbg as:
>>xxxxx@winse.microsoft.com
>> > > >To unsubscribe send a blank email to
>> > > >xxxxx@lists.osr.com
>> > > >
>> > > >—
>> > > >You are currently subscribed to windbg as: unknown lmsubst tag
>> > >argument: ‘’
>> > > >To unsubscribe send a blank email to
>> > > >xxxxx@lists.osr.com
>> > >
>> > >

>> > >Talk with your online friends with MSN Messenger
>> > >http://messenger.msn.nl/
>> > >
>> > >
>> > >—
>> > >You are currently subscribed to windbg as:
xxxxx@winse.microsoft.com
>>To
>> >
>> > >unsubscribe send a blank email to
xxxxx@lists.osr.com
>> > >
>> > >—
>> > >You are currently subscribed to windbg as: unknown lmsubst tag
>> >argument: ‘’
>> > >To unsubscribe send a blank email to
>>xxxxx@lists.osr.com
>> >
>> >
>> >Play online games with your friends with MSN Messenger
>> >http://messenger.msn.nl/
>> >
>> >
>> >—
>> >You are currently subscribed to windbg as: unknown lmsubst tag
>>argument: ‘’
>> >To unsubscribe send a blank email to
xxxxx@lists.osr.com
>>
>>

>>MSN Search, for accurate results! http://search.msn.nl
>>
>>
>>—
>>You are currently subscribed to windbg as: xxxxx@winse.microsoft.com
>>To unsubscribe send a blank email to xxxxx@lists.osr.com
>>
>>—
>>You are currently subscribed to windbg as: unknown lmsubst tag
argument:
>>‘’
>>To unsubscribe send a blank email to xxxxx@lists.osr.com
>
>
> Play online games with your friends with MSN Messenger
> http://messenger.msn.nl/
>
>
> ----------------------------------------------------------------------
>
> Subject: RE: Windbg not getting source from code premium site
> From: “Jason Shay”
> Date: Mon, 19 Sep 2005 08:30:46 -0700
> X-Message-Number: 2
>
> It should exist here:
> D:\Program Files\Debugging Tools for
> Windows\sdk\srcsrv\srcsrv.doc
>
> Relatively speaking. The srcsrv subdirectory has a bunch of pre-baked
> scripts that you’ll need, too.
>
> Jason
>
> -----Original Message-----
> From: xxxxx@lists.osr.com
> [mailto:xxxxx@lists.osr.com] On Behalf Of Daniel Grund
> Sent: Monday, September 19, 2005 1:42 AM
> To: Kernel Debugging Interest List
> Subject: RE: [windbg] Windbg not getting source from code premium site
>
> Hi Jason,
> Did that, no such document found
> Can you send it to me?
>
> Daniel
>
>>From: “Jason Shay”
>>Reply-To: “Kernel Debugging Interest List”
>>To: “Kernel Debugging Interest List”
>>Subject: RE: [windbg] Windbg not getting source from code premium site
>>Date: Thu, 8 Sep 2005 09:06:12 -0700
>>
>>I would think it shows the source from the first path available, which
>>may still be a completely different line than you’re looking for.
>>
>>There is no good solution when just using a string of paths to find
> your
>>source files. However there is a way to source-index your own PDB
>>files. Essentially, this tells the PDB how to look up the exact
> version
>>of source code from your version control system. You can get the
>>srcsrv.doc file by doing a customer install of the debugger and
> enabling
>>the SDK component.
>>
>>Jason
>>
>>-----Original Message-----
>>From: xxxxx@lists.osr.com
>>[mailto:xxxxx@lists.osr.com] On Behalf Of Daniel Grund
>>Sent: Thursday, September 08, 2005 12:18 AM
>>To: Kernel Debugging Interest List
>>Subject: RE: [windbg] Windbg not getting source from code premium site
>>
>>HI Jason,
>>
>>Yes, that does it.
>>As a remark, if you have multiple paths in the source paths and in
> there
>>
>>diferent versions of the same source, it will mess up. It will show
the
>>source from the last path available and point to a completely
different
>>line
>>in the source.
>>
>>anything that can be fixed?
>>
>>Daniel
>>
>> >From: “Jason Shay”
>> >Reply-To: “Kernel Debugging Interest List”
>> >To: “Kernel Debugging Interest List”
>> >Subject: RE: [windbg] Windbg not getting source from code premium
> site
>> >Date: Wed, 7 Sep 2005 18:51:20 -0700
>> >
>> >There was a bug where the http path must be the last entry in your
>> >srcpath. Can you make this change and see if it resolves your
issue?
>> >If so, we’ll have it fixed in the next debugger release.
>> >
>> >Jason
>> >
>> >-----Original Message-----
>> >From: Daniel Grund [mailto:xxxxx@hotmail.com]
>> >Sent: Saturday, August 13, 2005 4:10 AM
>> >To: Jason Shay
>> >Subject: RE: [windbg] Windbg not getting source from code premium
> site
>> >
>> >Hi Jay,
>> >
>> >I’ve got a mixed path.
>> >1: kd> .srcpath
>> >Source search path is:
>>
>>https://codepremium.msdn.microsoft.com/Source/windows%20server%202003/
r
>>t
>> >m;D:\src\SP40cSP2\SP2_Rd37540\Raidisk
>> >
>> >
>> >When I step to the frame containing local sources, there is no
> problem,
>> >it opens.
>> >When I step into a frame containing HTTPS sources, it doesn’t show.
>> >
>> >It finds the math to the source but just doesn’t open the source
> window
>> >for it.
>> >DBGENG: Scan paths for partial path match:
>> >DBGENG: prefix ‘d:\srvrtm\drivers\input\pnpi8042’
>> >DBGENG: suffix ‘kbddep.c’
>> >DBGENG: match
>>
>>‘https://codepremium.msdn.microsoft.com/Source/windows%20server%202003
/
>>r
>> >tm’
>> >against ‘d:\srvrtm\drivers\input\pnpi8042’: 31 (match ‘’)
>> >DBGENG: match ‘D:\src\SP40cSP2\SP2_Rd37540\Raidisk’ against
>> >‘d:\srvrtm\drivers\input\pnpi8042’: 31 (match ‘’)
>> >DBGENG: Scan paths for partial path match:
>> >DBGENG: prefix ‘d:\srvrtm\drivers\input’
>> >DBGENG: suffix ‘pnpi8042\kbddep.c’
>> >DBGENG: match
>>
>>‘https://codepremium.msdn.microsoft.com/Source/windows%20server%202003
/
>>r
>> >tm’
>> >against ‘d:\srvrtm\drivers\input’: 22 (match ‘’)
>> >DBGENG: match ‘D:\src\SP40cSP2\SP2_Rd37540\Raidisk’ against
>> >‘d:\srvrtm\drivers\input’: 22 (match ‘’)
>> >DBGENG: Scan paths for partial path match:
>> >DBGENG: prefix ‘d:\srvrtm\drivers’
>> >DBGENG: suffix ‘input\pnpi8042\kbddep.c’
>> >DBGENG: match
>>
>>‘https://codepremium.msdn.microsoft.com/Source/windows%20server%202003
/
>>r
>> >tm’
>> >against ‘d:\srvrtm\drivers’: 16 (match ‘’)
>> >DBGENG: match ‘D:\src\SP40cSP2\SP2_Rd37540\Raidisk’ against
>> >‘d:\srvrtm\drivers’: 16 (match ‘’)
>> >DBGENG: Scan paths for partial path match:
>> >DBGENG: prefix ‘d:\srvrtm’
>> >DBGENG: suffix ‘drivers\input\pnpi8042\kbddep.c’
>> >DBGENG: match
>>
>>‘https://codepremium.msdn.microsoft.com/Source/windows%20server%202003
/
>>r
>> >tm’
>> >against ‘d:\srvrtm’: 8 (match ‘’)
>> >DBGENG: match ‘D:\src\SP40cSP2\SP2_Rd37540\Raidisk’ against
>> >‘d:\srvrtm’: 8 (match ‘’)
>> >DBGENG: Scan paths for partial path match:
>> >DBGENG: prefix ‘d:’
>> >DBGENG: suffix ‘srvrtm\drivers\input\pnpi8042\kbddep.c’
>> >DBGENG: match
>>
>>‘https://codepremium.msdn.microsoft.com/Source/windows%20server%202003
/
>>r
>> >tm’
>> >against ‘d:’: 1 (match ‘’)
>> >DBGENG: match ‘D:\src\SP40cSP2\SP2_Rd37540\Raidisk’ against
> ‘d:’:
>>1
>> >
>> >(match ‘’)
>> >DBGENG: Scan all paths for:
>> >DBGENG: ‘d:\srvrtm\drivers\input\pnpi8042\kbddep.c’
>> >DBGENG: check
>>
>>‘https://codepremium.msdn.microsoft.com/Source/windows%20server%202003
/
>>r
>> >tm/d:/srvrtm/drivers/input/pnpi8042/kbddep.c’
>> >DBGENG: check
>>
>>‘D:\src\SP40cSP2\SP2_Rd37540\Raidisk\d:\srvrtm\drivers\input\pnpi8042<br>k
>>b
>> >ddep.c’
>> >DBGENG: Scan all paths for:
>> >DBGENG: ‘srvrtm\drivers\input\pnpi8042\kbddep.c’
>> >DBGENG: check
>>
>>‘https://codepremium.msdn.microsoft.com/Source/windows%20server%202003
/
>>r
>> >tm/srvrtm/drivers/input/pnpi8042/kbddep.c’
>> >DBGENG: check
>>
>>‘D:\src\SP40cSP2\SP2_Rd37540\Raidisk\srvrtm\drivers\input\pnpi8042\kbd
d
>>e
>> >p.c’
>> >DBGENG: Scan all paths for:
>> >DBGENG: ‘drivers\input\pnpi8042\kbddep.c’
>> >DBGENG: check
>>
>>‘https://codepremium.msdn.microsoft.com/Source/windows%20server%202003
/
>>r
>> >tm/drivers/input/pnpi8042/kbddep.c’
>> >DBGENG: check
>>
>‘D:\src\SP40cSP2\SP2_Rd37540\Raidisk\drivers\input\pnpi8042\kbddep.c’
>> >DBGENG: Scan all paths for:
>> >DBGENG: ‘input\pnpi8042\kbddep.c’
>> >DBGENG: check
>>
>>‘https://codepremium.msdn.microsoft.com/Source/windows%20server%202003
/
>>r
>> >tm/input/pnpi8042/kbddep.c’
>> >DBGENG: check
>> >‘D:\src\SP40cSP2\SP2_Rd37540\Raidisk\input\pnpi8042\kbddep.c’
>> >DBGENG: Scan all paths for:
>> >DBGENG: ‘pnpi8042\kbddep.c’
>> >DBGENG: check
>>
>>‘https://codepremium.msdn.microsoft.com/Source/windows%20server%202003
/
>>r
>> >tm/pnpi8042/kbddep.c’
>> >DBGENG: check
>> >‘D:\src\SP40cSP2\SP2_Rd37540\Raidisk\pnpi8042\kbddep.c’
>> >DBGENG: Scan all paths for:
>> >DBGENG: ‘kbddep.c’
>> >DBGENG: check
>>
>>‘https://codepremium.msdn.microsoft.com/Source/windows%20server%202003
/
>>r
>> >tm/kbddep.c’
>> >DBGENG: check ‘D:\src\SP40cSP2\SP2_Rd37540\Raidisk\kbddep.c’
>> >DBGENG: Check plain file:
>> >DBGENG: ‘d:\srvrtm\drivers\input\pnpi8042\kbddep.c’ - not found
>> >
>> >When I then delete the localpath from the .srcpath it opens fine
>> >
>> >Daniel
>> >
>> >
>> > >From: “Jason Shay”
>> > >Reply-To: “Kernel Debugging Interest List”
>> > >To: “Kernel Debugging Interest List”
>> > >Subject: RE: [windbg] Windbg not getting source from code premium
>>site
>> > >Date: Fri, 12 Aug 2005 08:50:46 -0700
>> > >
>> > >I’ll need more info than that to help. What exactly is your
>>.srcpath?
>> > >Are each element of the source path http sites? What’s the !sym
>>noisy
>> > >output? If that’s empty, what’s the ‘!srcnoisy 1’ output?
>> > >
>> > >But in general, it should work. I use it all the time…
>> > >
>> > >Jason
>> > >
>> > >-----Original Message-----
>> > >From: xxxxx@lists.osr.com
>> > >[mailto:xxxxx@lists.osr.com] On Behalf Of Daniel
> Grund
>> > >Sent: Friday, August 12, 2005 6:58 AM
>> > >To: Kernel Debugging Interest List
>> > >Subject: RE: [windbg] Windbg not getting source from code premium
>>site
>> > >
>> > >Thanks Jason,
>> > >That helped.
>> > >And now that we are speaking off this subject…
>> > >
>> > >Multiple source path’s seperated with ; doesn’t work as well.
>> > >Also not in the new version.
>> > >Something that can be fixed as well?
>> > >
>> > >Daniel
>> > >
>> > > >From: “Jason Shay”
>> > > >Reply-To: “Kernel Debugging Interest List”

>> > > >To: “Kernel Debugging Interest List”
>> > > >Subject: RE: [windbg] Windbg not getting source from code
premium
>> > > >site
>> > > >Date: Wed, 10 Aug 2005 20:28:09 -0700
>> > > >
>> > > >I was getting curious about why nobody external seems to have
>>noticed
>> >
>> > > >this yet. We’re in the process of hotfixing the 6.5.3.7 release
>>for
>> > > >just this bug. The web pages are not yet updated. But since
> it’s
>> > > >blocking you, here’s a sneak preview :slight_smile:
>> > > >
>> > >
>>
>http://msdl.microsoft.com/download/symbols/debuggers/dbg_x86_6.5.3.8.
>> > > >ex
>> > >e
>> > >
>> >
>>
>>http://msdl.microsoft.com/download/symbols/debuggers/dbg_amd64_6.5.3.8
.
>> > >e
>> > > >xe
>> > >
>>
>http://msdl.microsoft.com/download/symbols/debuggers/dbg_ia64_6.5.3.8
>> > > >.e
>> > >x
>> > > >e
>> > > >
>> > > >I’ll send a more official mail when the web site is updated.
>> > > >
>> > > >Jason
>> > > >
>> > > >-----Original Message-----
>> > > >From: xxxxx@lists.osr.com
>> > > >[mailto:xxxxx@lists.osr.com] On Behalf Of Daniel
>>Grund
>> > > >Sent: Wednesday, August 10, 2005 5:21 AM
>> > > >To: Kernel Debugging Interest List
>> > > >Subject: [windbg] Windbg not getting source from code premium
> site
>> > > >
>> > > >Hi All,
>> > > >Why does Windbg 6.5.3.7 doesn’t work anymore with the code
> premium
>> > > >site in source mode?
>> > > >Is there a way to track what is going on?
>> > > >
>> > > >Regards,
>> > > >
>> > > >Daniel
>> > > >
>> > >
>

>> > > >Play online games with your friends with MSN Messenger
>> > > >http://messenger.msn.nl/
>> > > >
>> > > >
>> > > >—
>> > > >You are currently subscribed to windbg as:
>>xxxxx@winse.microsoft.com
>> > > >To unsubscribe send a blank email to
>> > > >xxxxx@lists.osr.com
>> > > >
>> > > >—
>> > > >You are currently subscribed to windbg as: unknown lmsubst tag
>> > >argument: ‘’
>> > > >To unsubscribe send a blank email to
>> > > >xxxxx@lists.osr.com
>> > >
>> > >
>> > >Talk with your online friends with MSN Messenger
>> > >http://messenger.msn.nl/
>> > >
>> > >
>> > >—
>> > >You are currently subscribed to windbg as:
> xxxxx@winse.microsoft.com
>>To
>> >
>> > >unsubscribe send a blank email to
xxxxx@lists.osr.com
>> > >
>> > >—
>> > >You are currently subscribed to windbg as: unknown lmsubst tag
>> >argument: ‘’
>> > >To unsubscribe send a blank email to
>>xxxxx@lists.osr.com
>> >
>> >

>> >Play online games with your friends with MSN Messenger
>> >http://messenger.msn.nl/
>> >
>> >
>> >—
>> >You are currently subscribed to windbg as: unknown lmsubst tag
>>argument: ‘’
>> >To unsubscribe send a blank email to
> xxxxx@lists.osr.com
>>
>>
>>MSN Search, for accurate results! http://search.msn.nl
>>
>>
>>—
>>You are currently subscribed to windbg as: xxxxx@winse.microsoft.com
>>To unsubscribe send a blank email to xxxxx@lists.osr.com
>>
>>—
>>You are currently subscribed to windbg as: unknown lmsubst tag
> argument: ‘’
>>To unsubscribe send a blank email to xxxxx@lists.osr.com
>
>

> Play online games with your friends with MSN Messenger=20
> http://messenger.msn.nl/
>
>
> —
> You are currently subscribed to windbg as: xxxxx@winse.microsoft.com
> To unsubscribe send a blank email to xxxxx@lists.osr.com
>
>
>
> —
>
> END OF DIGEST
>
> —
> You are currently subscribed to windbg as: xxxxx@sover.net
> To unsubscribe send a blank email to xxxxx@lists.osr.com
>
>


You are currently subscribed to windbg as: xxxxx@winse.microsoft.com
To unsubscribe send a blank email to xxxxx@lists.osr.com

Never has worked for me on XPSP2 or 2003SP1. I cannot get a stable
connection if I do not disable it myself.


Don Burn (MVP, Windows DDK)
Windows 2k/XP/2k3 Filesystem and Driver Consulting
Remove StopSpam from the email to reply

“Jason Shay” wrote in message
news:xxxxx@windbg…
Note that disabling the 1394 controller on the target system should not
be done on xpsp2, Server 2003 SP1, or Vista. The controller should be
yellowed-out in device manager for you automatically.

Jason

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Don Burn
Sent: Tuesday, September 20, 2005 8:36 AM
To: Kernel Debugging Interest List
Subject: Re:[windbg] windbg digest: September 19, 2005

Nope just a standard cable. Be sure to disable 1394 networking on the
host
system, and the 1394 controllers driver on the test system.


Don Burn (MVP, Windows DDK)
Windows 2k/XP/2k3 Filesystem and Driver Consulting
Remove StopSpam from the email to reply

“Sanford Hayes” wrote in message news:xxxxx@windbg…
> Hello:
> I am finally going to try switching from serial to 1394 for my
debugging
> connection. Perhaps I am the last one to try it:) Does 1394 require a
> special cable like a null modem for serial debugging does? I don’t
want to
> damage my equipment by using the wrong cable and cannot find
documentation
> on this issue.
> Thanks
> Sanford Hayes
> www.vwaresys.com
>
>
>
> -----Original Message-----
> From: xxxxx@lists.osr.com
> [mailto:xxxxx@lists.osr.com] On Behalf Of Kernel
Debugging
> Interest List digest
> Sent: Tuesday, September 20, 2005 1:00 AM
> To: windbg digest recipients
> Subject: windbg digest: September 19, 2005
>
> WINDBG Digest for Monday, September 19, 2005.
>
> 1. RE: Windbg not getting source from code premium site
> 2. RE: Windbg not getting source from code premium site
>
> ----------------------------------------------------------------------
>
> Subject: RE: Windbg not getting source from code premium site
> From: “Daniel Grund”
> Date: Mon, 19 Sep 2005 10:41:43 +0200
> X-Message-Number: 1
>
> Hi Jason,
> Did that, no such document found
> Can you send it to me?
>
> Daniel
>
>>From: “Jason Shay”
>>Reply-To: “Kernel Debugging Interest List”
>>To: “Kernel Debugging Interest List”
>>Subject: RE: [windbg] Windbg not getting source from code premium site
>>Date: Thu, 8 Sep 2005 09:06:12 -0700
>>
>>I would think it shows the source from the first path available, which
>>may still be a completely different line than you’re looking for.
>>
>>There is no good solution when just using a string of paths to find
your
>>source files. However there is a way to source-index your own PDB
>>files. Essentially, this tells the PDB how to look up the exact
version
>>of source code from your version control system. You can get the
>>srcsrv.doc file by doing a customer install of the debugger and
enabling
>>the SDK component.
>>
>>Jason
>>
>>-----Original Message-----
>>From: xxxxx@lists.osr.com
>>[mailto:xxxxx@lists.osr.com] On Behalf Of Daniel Grund
>>Sent: Thursday, September 08, 2005 12:18 AM
>>To: Kernel Debugging Interest List
>>Subject: RE: [windbg] Windbg not getting source from code premium site
>>
>>HI Jason,
>>
>>Yes, that does it.
>>As a remark, if you have multiple paths in the source paths and in
there
>>
>>diferent versions of the same source, it will mess up. It will show
the
>>source from the last path available and point to a completely
different
>>line
>>in the source.
>>
>>anything that can be fixed?
>>
>>Daniel
>>
>> >From: “Jason Shay”
>> >Reply-To: “Kernel Debugging Interest List”
>> >To: “Kernel Debugging Interest List”
>> >Subject: RE: [windbg] Windbg not getting source from code premium
site
>> >Date: Wed, 7 Sep 2005 18:51:20 -0700
>> >
>> >There was a bug where the http path must be the last entry in your
>> >srcpath. Can you make this change and see if it resolves your
issue?
>> >If so, we’ll have it fixed in the next debugger release.
>> >
>> >Jason
>> >
>> >-----Original Message-----
>> >From: Daniel Grund [mailto:xxxxx@hotmail.com]
>> >Sent: Saturday, August 13, 2005 4:10 AM
>> >To: Jason Shay
>> >Subject: RE: [windbg] Windbg not getting source from code premium
site
>> >
>> >Hi Jay,
>> >
>> >I’ve got a mixed path.
>> >1: kd> .srcpath
>> >Source search path is:
>>
>https://codepremium.msdn.microsoft.com/Source/windows%20server%202003/r
>>t
>> >m;D:\src\SP40cSP2\SP2_Rd37540\Raidisk
>> >
>> >
>> >When I step to the frame containing local sources, there is no
problem,
>> >it opens.
>> >When I step into a frame containing HTTPS sources, it doesn’t show.
>> >
>> >It finds the math to the source but just doesn’t open the source
window
>> >for it.
>> >DBGENG: Scan paths for partial path match:
>> >DBGENG: prefix ‘d:\srvrtm\drivers\input\pnpi8042’
>> >DBGENG: suffix ‘kbddep.c’
>> >DBGENG: match
>>
>‘https://codepremium.msdn.microsoft.com/Source/windows%20server%202003/
>>r
>> >tm’
>> >against ‘d:\srvrtm\drivers\input\pnpi8042’: 31 (match ‘’)
>> >DBGENG: match ‘D:\src\SP40cSP2\SP2_Rd37540\Raidisk’ against
>> >‘d:\srvrtm\drivers\input\pnpi8042’: 31 (match ‘’)
>> >DBGENG: Scan paths for partial path match:
>> >DBGENG: prefix ‘d:\srvrtm\drivers\input’
>> >DBGENG: suffix ‘pnpi8042\kbddep.c’
>> >DBGENG: match
>>
>‘https://codepremium.msdn.microsoft.com/Source/windows%20server%202003/
>>r
>> >tm’
>> >against ‘d:\srvrtm\drivers\input’: 22 (match ‘’)
>> >DBGENG: match ‘D:\src\SP40cSP2\SP2_Rd37540\Raidisk’ against
>> >‘d:\srvrtm\drivers\input’: 22 (match ‘’)
>> >DBGENG: Scan paths for partial path match:
>> >DBGENG: prefix ‘d:\srvrtm\drivers’
>> >DBGENG: suffix ‘input\pnpi8042\kbddep.c’
>> >DBGENG: match
>>
>‘https://codepremium.msdn.microsoft.com/Source/windows%20server%202003/
>>r
>> >tm’
>> >against ‘d:\srvrtm\drivers’: 16 (match ‘’)
>> >DBGENG: match ‘D:\src\SP40cSP2\SP2_Rd37540\Raidisk’ against
>> >‘d:\srvrtm\drivers’: 16 (match ‘’)
>> >DBGENG: Scan paths for partial path match:
>> >DBGENG: prefix ‘d:\srvrtm’
>> >DBGENG: suffix ‘drivers\input\pnpi8042\kbddep.c’
>> >DBGENG: match
>>
>‘https://codepremium.msdn.microsoft.com/Source/windows%20server%202003/
>>r
>> >tm’
>> >against ‘d:\srvrtm’: 8 (match ‘’)
>> >DBGENG: match ‘D:\src\SP40cSP2\SP2_Rd37540\Raidisk’ against
>> >‘d:\srvrtm’: 8 (match ‘’)
>> >DBGENG: Scan paths for partial path match:
>> >DBGENG: prefix ‘d:’
>> >DBGENG: suffix ‘srvrtm\drivers\input\pnpi8042\kbddep.c’
>> >DBGENG: match
>>
>‘https://codepremium.msdn.microsoft.com/Source/windows%20server%202003/
>>r
>> >tm’
>> >against ‘d:’: 1 (match ‘’)
>> >DBGENG: match ‘D:\src\SP40cSP2\SP2_Rd37540\Raidisk’ against
‘d:’:
>>1
>> >
>> >(match ‘’)
>> >DBGENG: Scan all paths for:
>> >DBGENG: ‘d:\srvrtm\drivers\input\pnpi8042\kbddep.c’
>> >DBGENG: check
>>
>‘https://codepremium.msdn.microsoft.com/Source/windows%20server%202003/
>>r
>> >tm/d:/srvrtm/drivers/input/pnpi8042/kbddep.c’
>> >DBGENG: check
>>
>‘D:\src\SP40cSP2\SP2_Rd37540\Raidisk\d:\srvrtm\drivers\input\pnpi8042\k
>>b
>> >ddep.c’
>> >DBGENG: Scan all paths for:
>> >DBGENG: ‘srvrtm\drivers\input\pnpi8042\kbddep.c’
>> >DBGENG: check
>>
>‘https://codepremium.msdn.microsoft.com/Source/windows%20server%202003/
>>r
>> >tm/srvrtm/drivers/input/pnpi8042/kbddep.c’
>> >DBGENG: check
>>
>‘D:\src\SP40cSP2\SP2_Rd37540\Raidisk\srvrtm\drivers\input\pnpi8042\kbdd
>>e
>> >p.c’
>> >DBGENG: Scan all paths for:
>> >DBGENG: ‘drivers\input\pnpi8042\kbddep.c’
>> >DBGENG: check
>>
>‘https://codepremium.msdn.microsoft.com/Source/windows%20server%202003/
>>r
>> >tm/drivers/input/pnpi8042/kbddep.c’
>> >DBGENG: check
>>
>‘D:\src\SP40cSP2\SP2_Rd37540\Raidisk\drivers\input\pnpi8042\kbddep.c’
>> >DBGENG: Scan all paths for:
>> >DBGENG: ‘input\pnpi8042\kbddep.c’
>> >DBGENG: check
>>
>‘https://codepremium.msdn.microsoft.com/Source/windows%20server%202003/
>>r
>> >tm/input/pnpi8042/kbddep.c’
>> >DBGENG: check
>> >‘D:\src\SP40cSP2\SP2_Rd37540\Raidisk\input\pnpi8042\kbddep.c’
>> >DBGENG: Scan all paths for:
>> >DBGENG: ‘pnpi8042\kbddep.c’
>> >DBGENG: check
>>
>‘https://codepremium.msdn.microsoft.com/Source/windows%20server%202003/
>>r
>> >tm/pnpi8042/kbddep.c’
>> >DBGENG: check
>> >‘D:\src\SP40cSP2\SP2_Rd37540\Raidisk\pnpi8042\kbddep.c’
>> >DBGENG: Scan all paths for:
>> >DBGENG: ‘kbddep.c’
>> >DBGENG: check
>>
>‘https://codepremium.msdn.microsoft.com/Source/windows%20server%202003/
>>r
>> >tm/kbddep.c’
>> >DBGENG: check ‘D:\src\SP40cSP2\SP2_Rd37540\Raidisk\kbddep.c’
>> >DBGENG: Check plain file:
>> >DBGENG: ‘d:\srvrtm\drivers\input\pnpi8042\kbddep.c’ - not found
>> >
>> >When I then delete the localpath from the .srcpath it opens fine
>> >
>> >Daniel
>> >
>> >
>> > >From: “Jason Shay”
>> > >Reply-To: “Kernel Debugging Interest List”
>> > >To: “Kernel Debugging Interest List”
>> > >Subject: RE: [windbg] Windbg not getting source from code premium
>>site
>> > >Date: Fri, 12 Aug 2005 08:50:46 -0700
>> > >
>> > >I’ll need more info than that to help. What exactly is your
>>.srcpath?
>> > >Are each element of the source path http sites? What’s the !sym
>>noisy
>> > >output? If that’s empty, what’s the ‘!srcnoisy 1’ output?
>> > >
>> > >But in general, it should work. I use it all the time…
>> > >
>> > >Jason
>> > >
>> > >-----Original Message-----
>> > >From: xxxxx@lists.osr.com
>> > >[mailto:xxxxx@lists.osr.com] On Behalf Of Daniel
Grund
>> > >Sent: Friday, August 12, 2005 6:58 AM
>> > >To: Kernel Debugging Interest List
>> > >Subject: RE: [windbg] Windbg not getting source from code premium
>>site
>> > >
>> > >Thanks Jason,
>> > >That helped.
>> > >And now that we are speaking off this subject…
>> > >
>> > >Multiple source path’s seperated with ; doesn’t work as well.
>> > >Also not in the new version.
>> > >Something that can be fixed as well?
>> > >
>> > >Daniel
>> > >
>> > > >From: “Jason Shay”
>> > > >Reply-To: “Kernel Debugging Interest List”

>> > > >To: “Kernel Debugging Interest List”
>> > > >Subject: RE: [windbg] Windbg not getting source from code
premium
>> > > >site
>> > > >Date: Wed, 10 Aug 2005 20:28:09 -0700
>> > > >
>> > > >I was getting curious about why nobody external seems to have
>>noticed
>> >
>> > > >this yet. We’re in the process of hotfixing the 6.5.3.7 release
>>for
>> > > >just this bug. The web pages are not yet updated. But since
it’s
>> > > >blocking you, here’s a sneak preview :slight_smile:
>> > > >
>> > >
>>
>http://msdl.microsoft.com/download/symbols/debuggers/dbg_x86_6.5.3.8.
>> > > >ex
>> > >e
>> > >
>> >
>>
>http://msdl.microsoft.com/download/symbols/debuggers/dbg_amd64_6.5.3.8.
>> > >e
>> > > >xe
>> > >
>>
>http://msdl.microsoft.com/download/symbols/debuggers/dbg_ia64_6.5.3.8
>> > > >.e
>> > >x
>> > > >e
>> > > >
>> > > >I’ll send a more official mail when the web site is updated.
>> > > >
>> > > >Jason
>> > > >
>> > > >-----Original Message-----
>> > > >From: xxxxx@lists.osr.com
>> > > >[mailto:xxxxx@lists.osr.com] On Behalf Of Daniel
>>Grund
>> > > >Sent: Wednesday, August 10, 2005 5:21 AM
>> > > >To: Kernel Debugging Interest List
>> > > >Subject: [windbg] Windbg not getting source from code premium
site
>> > > >
>> > > >Hi All,
>> > > >Why does Windbg 6.5.3.7 doesn’t work anymore with the code
premium
>> > > >site in source mode?
>> > > >Is there a way to track what is going on?
>> > > >
>> > > >Regards,
>> > > >
>> > > >Daniel
>> > > >
>> > >
>
>> > > >Play online games with your friends with MSN Messenger
>> > > >http://messenger.msn.nl/
>> > > >
>> > > >
>> > > >—
>> > > >You are currently subscribed to windbg as:
>>xxxxx@winse.microsoft.com
>> > > >To unsubscribe send a blank email to
>> > > >xxxxx@lists.osr.com
>> > > >
>> > > >—
>> > > >You are currently subscribed to windbg as: unknown lmsubst tag
>> > >argument: ‘’
>> > > >To unsubscribe send a blank email to
>> > > >xxxxx@lists.osr.com
>> > >
>> > >

>> > >Talk with your online friends with MSN Messenger
>> > >http://messenger.msn.nl/
>> > >
>> > >
>> > >—
>> > >You are currently subscribed to windbg as:
xxxxx@winse.microsoft.com
>>To
>> >
>> > >unsubscribe send a blank email to
xxxxx@lists.osr.com
>> > >
>> > >—
>> > >You are currently subscribed to windbg as: unknown lmsubst tag
>> >argument: ‘’
>> > >To unsubscribe send a blank email to
>>xxxxx@lists.osr.com
>> >
>> >
>> >Play online games with your friends with MSN Messenger
>> >http://messenger.msn.nl/
>> >
>> >
>> >—
>> >You are currently subscribed to windbg as: unknown lmsubst tag
>>argument: ‘’
>> >To unsubscribe send a blank email to
xxxxx@lists.osr.com
>>
>>

>>MSN Search, for accurate results! http://search.msn.nl
>>
>>
>>—
>>You are currently subscribed to windbg as: xxxxx@winse.microsoft.com
>>To unsubscribe send a blank email to xxxxx@lists.osr.com
>>
>>—
>>You are currently subscribed to windbg as: unknown lmsubst tag
argument:
>>‘’
>>To unsubscribe send a blank email to xxxxx@lists.osr.com
>
>
> Play online games with your friends with MSN Messenger
> http://messenger.msn.nl/
>
>
> ----------------------------------------------------------------------
>
> Subject: RE: Windbg not getting source from code premium site
> From: “Jason Shay”
> Date: Mon, 19 Sep 2005 08:30:46 -0700
> X-Message-Number: 2
>
> It should exist here:
> D:\Program Files\Debugging Tools for
> Windows\sdk\srcsrv\srcsrv.doc
>
> Relatively speaking. The srcsrv subdirectory has a bunch of pre-baked
> scripts that you’ll need, too.
>
> Jason
>
> -----Original Message-----
> From: xxxxx@lists.osr.com
> [mailto:xxxxx@lists.osr.com] On Behalf Of Daniel Grund
> Sent: Monday, September 19, 2005 1:42 AM
> To: Kernel Debugging Interest List
> Subject: RE: [windbg] Windbg not getting source from code premium site
>
> Hi Jason,
> Did that, no such document found
> Can you send it to me?
>
> Daniel
>
>>From: “Jason Shay”
>>Reply-To: “Kernel Debugging Interest List”
>>To: “Kernel Debugging Interest List”
>>Subject: RE: [windbg] Windbg not getting source from code premium site
>>Date: Thu, 8 Sep 2005 09:06:12 -0700
>>
>>I would think it shows the source from the first path available, which
>>may still be a completely different line than you’re looking for.
>>
>>There is no good solution when just using a string of paths to find
> your
>>source files. However there is a way to source-index your own PDB
>>files. Essentially, this tells the PDB how to look up the exact
> version
>>of source code from your version control system. You can get the
>>srcsrv.doc file by doing a customer install of the debugger and
> enabling
>>the SDK component.
>>
>>Jason
>>
>>-----Original Message-----
>>From: xxxxx@lists.osr.com
>>[mailto:xxxxx@lists.osr.com] On Behalf Of Daniel Grund
>>Sent: Thursday, September 08, 2005 12:18 AM
>>To: Kernel Debugging Interest List
>>Subject: RE: [windbg] Windbg not getting source from code premium site
>>
>>HI Jason,
>>
>>Yes, that does it.
>>As a remark, if you have multiple paths in the source paths and in
> there
>>
>>diferent versions of the same source, it will mess up. It will show
the
>>source from the last path available and point to a completely
different
>>line
>>in the source.
>>
>>anything that can be fixed?
>>
>>Daniel
>>
>> >From: “Jason Shay”
>> >Reply-To: “Kernel Debugging Interest List”
>> >To: “Kernel Debugging Interest List”
>> >Subject: RE: [windbg] Windbg not getting source from code premium
> site
>> >Date: Wed, 7 Sep 2005 18:51:20 -0700
>> >
>> >There was a bug where the http path must be the last entry in your
>> >srcpath. Can you make this change and see if it resolves your
issue?
>> >If so, we’ll have it fixed in the next debugger release.
>> >
>> >Jason
>> >
>> >-----Original Message-----
>> >From: Daniel Grund [mailto:xxxxx@hotmail.com]
>> >Sent: Saturday, August 13, 2005 4:10 AM
>> >To: Jason Shay
>> >Subject: RE: [windbg] Windbg not getting source from code premium
> site
>> >
>> >Hi Jay,
>> >
>> >I’ve got a mixed path.
>> >1: kd> .srcpath
>> >Source search path is:
>>
>>https://codepremium.msdn.microsoft.com/Source/windows%20server%202003/
r
>>t
>> >m;D:\src\SP40cSP2\SP2_Rd37540\Raidisk
>> >
>> >
>> >When I step to the frame containing local sources, there is no
> problem,
>> >it opens.
>> >When I step into a frame containing HTTPS sources, it doesn’t show.
>> >
>> >It finds the math to the source but just doesn’t open the source
> window
>> >for it.
>> >DBGENG: Scan paths for partial path match:
>> >DBGENG: prefix ‘d:\srvrtm\drivers\input\pnpi8042’
>> >DBGENG: suffix ‘kbddep.c’
>> >DBGENG: match
>>
>>‘https://codepremium.msdn.microsoft.com/Source/windows%20server%202003
/
>>r
>> >tm’
>> >against ‘d:\srvrtm\drivers\input\pnpi8042’: 31 (match ‘’)
>> >DBGENG: match ‘D:\src\SP40cSP2\SP2_Rd37540\Raidisk’ against
>> >‘d:\srvrtm\drivers\input\pnpi8042’: 31 (match ‘’)
>> >DBGENG: Scan paths for partial path match:
>> >DBGENG: prefix ‘d:\srvrtm\drivers\input’
>> >DBGENG: suffix ‘pnpi8042\kbddep.c’
>> >DBGENG: match
>>
>>‘https://codepremium.msdn.microsoft.com/Source/windows%20server%202003
/
>>r
>> >tm’
>> >against ‘d:\srvrtm\drivers\input’: 22 (match ‘’)
>> >DBGENG: match ‘D:\src\SP40cSP2\SP2_Rd37540\Raidisk’ against
>> >‘d:\srvrtm\drivers\input’: 22 (match ‘’)
>> >DBGENG: Scan paths for partial path match:
>> >DBGENG: prefix ‘d:\srvrtm\drivers’
>> >DBGENG: suffix ‘input\pnpi8042\kbddep.c’
>> >DBGENG: match
>>
>>‘https://codepremium.msdn.microsoft.com/Source/windows%20server%202003
/
>>r
>> >tm’
>> >against ‘d:\srvrtm\drivers’: 16 (match ‘’)
>> >DBGENG: match ‘D:\src\SP40cSP2\SP2_Rd37540\Raidisk’ against
>> >‘d:\srvrtm\drivers’: 16 (match ‘’)
>> >DBGENG: Scan paths for partial path match:
>> >DBGENG: prefix ‘d:\srvrtm’
>> >DBGENG: suffix ‘drivers\input\pnpi8042\kbddep.c’
>> >DBGENG: match
>>
>>‘https://codepremium.msdn.microsoft.com/Source/windows%20server%202003
/
>>r
>> >tm’
>> >against ‘d:\srvrtm’: 8 (match ‘’)
>> >DBGENG: match ‘D:\src\SP40cSP2\SP2_Rd37540\Raidisk’ against
>> >‘d:\srvrtm’: 8 (match ‘’)
>> >DBGENG: Scan paths for partial path match:
>> >DBGENG: prefix ‘d:’
>> >DBGENG: suffix ‘srvrtm\drivers\input\pnpi8042\kbddep.c’
>> >DBGENG: match
>>
>>‘https://codepremium.msdn.microsoft.com/Source/windows%20server%202003
/
>>r
>> >tm’
>> >against ‘d:’: 1 (match ‘’)
>> >DBGENG: match ‘D:\src\SP40cSP2\SP2_Rd37540\Raidisk’ against
> ‘d:’:
>>1
>> >
>> >(match ‘’)
>> >DBGENG: Scan all paths for:
>> >DBGENG: ‘d:\srvrtm\drivers\input\pnpi8042\kbddep.c’
>> >DBGENG: check
>>
>>‘https://codepremium.msdn.microsoft.com/Source/windows%20server%202003
/
>>r
>> >tm/d:/srvrtm/drivers/input/pnpi8042/kbddep.c’
>> >DBGENG: check
>>
>>‘D:\src\SP40cSP2\SP2_Rd37540\Raidisk\d:\srvrtm\drivers\input\pnpi8042<br>k
>>b
>> >ddep.c’
>> >DBGENG: Scan all paths for:
>> >DBGENG: ‘srvrtm\drivers\input\pnpi8042\kbddep.c’
>> >DBGENG: check
>>
>>‘https://codepremium.msdn.microsoft.com/Source/windows%20server%202003
/
>>r
>> >tm/srvrtm/drivers/input/pnpi8042/kbddep.c’
>> >DBGENG: check
>>
>>‘D:\src\SP40cSP2\SP2_Rd37540\Raidisk\srvrtm\drivers\input\pnpi8042\kbd
d
>>e
>> >p.c’
>> >DBGENG: Scan all paths for:
>> >DBGENG: ‘drivers\input\pnpi8042\kbddep.c’
>> >DBGENG: check
>>
>>‘https://codepremium.msdn.microsoft.com/Source/windows%20server%202003
/
>>r
>> >tm/drivers/input/pnpi8042/kbddep.c’
>> >DBGENG: check
>>
>‘D:\src\SP40cSP2\SP2_Rd37540\Raidisk\drivers\input\pnpi8042\kbddep.c’
>> >DBGENG: Scan all paths for:
>> >DBGENG: ‘input\pnpi8042\kbddep.c’
>> >DBGENG: check
>>
>>‘https://codepremium.msdn.microsoft.com/Source/windows%20server%202003
/
>>r
>> >tm/input/pnpi8042/kbddep.c’
>> >DBGENG: check
>> >‘D:\src\SP40cSP2\SP2_Rd37540\Raidisk\input\pnpi8042\kbddep.c’
>> >DBGENG: Scan all paths for:
>> >DBGENG: ‘pnpi8042\kbddep.c’
>> >DBGENG: check
>>
>>‘https://codepremium.msdn.microsoft.com/Source/windows%20server%202003
/
>>r
>> >tm/pnpi8042/kbddep.c’
>> >DBGENG: check
>> >‘D:\src\SP40cSP2\SP2_Rd37540\Raidisk\pnpi8042\kbddep.c’
>> >DBGENG: Scan all paths for:
>> >DBGENG: ‘kbddep.c’
>> >DBGENG: check
>>
>>‘https://codepremium.msdn.microsoft.com/Source/windows%20server%202003
/
>>r
>> >tm/kbddep.c’
>> >DBGENG: check ‘D:\src\SP40cSP2\SP2_Rd37540\Raidisk\kbddep.c’
>> >DBGENG: Check plain file:
>> >DBGENG: ‘d:\srvrtm\drivers\input\pnpi8042\kbddep.c’ - not found
>> >
>> >When I then delete the localpath from the .srcpath it opens fine
>> >
>> >Daniel
>> >
>> >
>> > >From: “Jason Shay”
>> > >Reply-To: “Kernel Debugging Interest List”
>> > >To: “Kernel Debugging Interest List”
>> > >Subject: RE: [windbg] Windbg not getting source from code premium
>>site
>> > >Date: Fri, 12 Aug 2005 08:50:46 -0700
>> > >
>> > >I’ll need more info than that to help. What exactly is your
>>.srcpath?
>> > >Are each element of the source path http sites? What’s the !sym
>>noisy
>> > >output? If that’s empty, what’s the ‘!srcnoisy 1’ output?
>> > >
>> > >But in general, it should work. I use it all the time…
>> > >
>> > >Jason
>> > >
>> > >-----Original Message-----
>> > >From: xxxxx@lists.osr.com
>> > >[mailto:xxxxx@lists.osr.com] On Behalf Of Daniel
> Grund
>> > >Sent: Friday, August 12, 2005 6:58 AM
>> > >To: Kernel Debugging Interest List
>> > >Subject: RE: [windbg] Windbg not getting source from code premium
>>site
>> > >
>> > >Thanks Jason,
>> > >That helped.
>> > >And now that we are speaking off this subject…
>> > >
>> > >Multiple source path’s seperated with ; doesn’t work as well.
>> > >Also not in the new version.
>> > >Something that can be fixed as well?
>> > >
>> > >Daniel
>> > >
>> > > >From: “Jason Shay”
>> > > >Reply-To: “Kernel Debugging Interest List”

>> > > >To: “Kernel Debugging Interest List”
>> > > >Subject: RE: [windbg] Windbg not getting source from code
premium
>> > > >site
>> > > >Date: Wed, 10 Aug 2005 20:28:09 -0700
>> > > >
>> > > >I was getting curious about why nobody external seems to have
>>noticed
>> >
>> > > >this yet. We’re in the process of hotfixing the 6.5.3.7 release
>>for
>> > > >just this bug. The web pages are not yet updated. But since
> it’s
>> > > >blocking you, here’s a sneak preview :slight_smile:
>> > > >
>> > >
>>
>http://msdl.microsoft.com/download/symbols/debuggers/dbg_x86_6.5.3.8.
>> > > >ex
>> > >e
>> > >
>> >
>>
>>http://msdl.microsoft.com/download/symbols/debuggers/dbg_amd64_6.5.3.8
.
>> > >e
>> > > >xe
>> > >
>>
>http://msdl.microsoft.com/download/symbols/debuggers/dbg_ia64_6.5.3.8
>> > > >.e
>> > >x
>> > > >e
>> > > >
>> > > >I’ll send a more official mail when the web site is updated.
>> > > >
>> > > >Jason
>> > > >
>> > > >-----Original Message-----
>> > > >From: xxxxx@lists.osr.com
>> > > >[mailto:xxxxx@lists.osr.com] On Behalf Of Daniel
>>Grund
>> > > >Sent: Wednesday, August 10, 2005 5:21 AM
>> > > >To: Kernel Debugging Interest List
>> > > >Subject: [windbg] Windbg not getting source from code premium
> site
>> > > >
>> > > >Hi All,
>> > > >Why does Windbg 6.5.3.7 doesn’t work anymore with the code
> premium
>> > > >site in source mode?
>> > > >Is there a way to track what is going on?
>> > > >
>> > > >Regards,
>> > > >
>> > > >Daniel
>> > > >
>> > >
>

>> > > >Play online games with your friends with MSN Messenger
>> > > >http://messenger.msn.nl/
>> > > >
>> > > >
>> > > >—
>> > > >You are currently subscribed to windbg as:
>>xxxxx@winse.microsoft.com
>> > > >To unsubscribe send a blank email to
>> > > >xxxxx@lists.osr.com
>> > > >
>> > > >—
>> > > >You are currently subscribed to windbg as: unknown lmsubst tag
>> > >argument: ‘’
>> > > >To unsubscribe send a blank email to
>> > > >xxxxx@lists.osr.com
>> > >
>> > >
>> > >Talk with your online friends with MSN Messenger
>> > >http://messenger.msn.nl/
>> > >
>> > >
>> > >—
>> > >You are currently subscribed to windbg as:
> xxxxx@winse.microsoft.com
>>To
>> >
>> > >unsubscribe send a blank email to
xxxxx@lists.osr.com
>> > >
>> > >—
>> > >You are currently subscribed to windbg as: unknown lmsubst tag
>> >argument: ‘’
>> > >To unsubscribe send a blank email to
>>xxxxx@lists.osr.com
>> >
>> >

>> >Play online games with your friends with MSN Messenger
>> >http://messenger.msn.nl/
>> >
>> >
>> >—
>> >You are currently subscribed to windbg as: unknown lmsubst tag
>>argument: ‘’
>> >To unsubscribe send a blank email to
> xxxxx@lists.osr.com
>>
>>
>>MSN Search, for accurate results! http://search.msn.nl
>>
>>
>>—
>>You are currently subscribed to windbg as: xxxxx@winse.microsoft.com
>>To unsubscribe send a blank email to xxxxx@lists.osr.com
>>
>>—
>>You are currently subscribed to windbg as: unknown lmsubst tag
> argument: ‘’
>>To unsubscribe send a blank email to xxxxx@lists.osr.com
>
>

> Play online games with your friends with MSN Messenger=20
> http://messenger.msn.nl/
>
>
> —
> You are currently subscribed to windbg as: xxxxx@winse.microsoft.com
> To unsubscribe send a blank email to xxxxx@lists.osr.com
>
>
>
> —
>
> END OF DIGEST
>
> —
> You are currently subscribed to windbg as: xxxxx@sover.net
> To unsubscribe send a blank email to xxxxx@lists.osr.com
>
>


You are currently subscribed to windbg as: xxxxx@winse.microsoft.com
To unsubscribe send a blank email to xxxxx@lists.osr.com

Thanks for your response Don.
One more Question about 1394.
There appear to be three flavors of 1394 cables available.
6 wire 4 wire and 6 to 4 wire.
Which is appropriate for windbg?
Thanks
Sanford Hayes
vwaresys.com

That depends on your hardware. All you need is to cable them together. In
my setup, I use the “big” FireWire plugs, not the “small” 4-pin or 6-pin
connectors, which I believe were designed for small digital video cameras.

The 6-pin “small” connector has power leads, and so you probably don’t want
to have the power output from two different supplies connected.

– arlie

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Sanford Hayes
Sent: Wednesday, September 21, 2005 11:23 AM
To: Kernel Debugging Interest List
Subject: RE:[windbg] windbg digest: September 19, 2005

Thanks for your response Don.
One more Question about 1394.
There appear to be three flavors of 1394 cables available.
6 wire 4 wire and 6 to 4 wire.
Which is appropriate for windbg?
Thanks
Sanford Hayes
vwaresys.com


You are currently subscribed to windbg as: xxxxx@stonestreetone.com
To unsubscribe send a blank email to xxxxx@lists.osr.com

> There appear to be three flavors of 1394 cables available.

6 wire 4 wire and 6 to 4 wire.
Which is appropriate for windbg?

The kinds that actually fit your hardware. They are electrically
compatible, although the bus power is only available when both ends have
6 wires. (Bus power is not relevant to self-powered devices like computers)

Cheers,

/ h+

Sanford Hayes wrote:

Thanks for your response Don.
One more Question about 1394.
There appear to be three flavors of 1394 cables available.
6 wire 4 wire and 6 to 4 wire.
Which is appropriate for windbg?

The 6-wire and 4-wire connectors are different sizes. The 6-wire
connector is the size of a USB host connector, and the 4-wire is a tiny
little thing commonly found on video cameras.

You need to use the cable that matches your host adapters. Desktop 1394
host adapters use the larger 6-wire connector, although many laptops use
the 4-wire. If you are going desktop to desktop, you almost certainly
need a 6-wire to 6-wire cable.


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